I have set up a wsus 3.0 update server on a windows 2003 server... We run in a mixed server enviroment with NT 4.0/2000 and the majority of the workstations are 2000 Pro SP4 or XP pro SP2... I followed the instructions in the Microsoft guide on WSUS 3.0 to set it up on the server... I also followed the instructions from microsoft on setting up self update on clents in a non-active directory enviroment on a test PC running Windows XP sp2 ( we do not use active directory, so I modified the register on the PC to make the change) . The PC is not showing up on the WSUS as a connected PC... When I run the WSUS client diagnosis software on the XP machine, all pass until I get to the connection to WSUS server section and it failes with a "Verify WUServer URL<failed> with hr=0x80072ee6 error.
The URL doeesn't use a recognized protocol..." . When I do a port scan on the IP of the server, it shows me that port 80 is open ( I used the standard ports of 80 and 443 for the wsus site).. I can ping the IP of the server from the client just fine... Why is this client not connecting to self update? If i can configure one client to connect and self update, I am sure the next 70 or so will be easy.. Any help would be appreciated. Thanks
If you are a web developer, you would be aware of the <iframe> tag in HTML. The <iframe> stands for inline frame and is used to embed another document within the current HTML document. The embedded document could be even another website.
Michael from AdRem Software outlines event notifications and Automatic Corrective Actions in network monitoring. Automatic Corrective Actions are scripts, which can automatically run upon discovery of a certain undesirable condition in your network.…
In this video, Percona Solutions Engineer Barrett Chambers discusses some of the basic syntax differences between MySQL and MongoDB.
To learn more check out our webinar on MongoDB administration for MySQL DBA: https://www.percona.com/resources/we…