WSUS experiences

[Geoff]

I'm sure you all know the replacement for SUS was released by microsoft last week. If you don't here's the relevant page:

 

http://www.microsoft.com/windowsserversystem/updateservices/default.mspx

 

I'm just wondering how everyones got on with the migration? I've transfered to WSUS ok and it seems to work ok. It took a very long time to detect all the machines and to download the updates though. One minor problem I do have is that some of the office updates refuse to download correctly. Has anyone else got that problem? and fixed it?

[Slartibartfast]

I'm not having any luck with it at all. It's doesn't seem to like our Equiinet proxy/cache. SUS works perfectly.

[Dos_Box]

I think that we here in Lancashire (especially Geoff) can help you with that!!

[Geoff]

It's doesn't seem to like our Equiinet proxy/cache.

 

Presumably you've entered the proxy information in the settings?

 

What errors are you getting?

[Slartibartfast]

In the application event log...

 

Event ID: 329

 

"Synchronization failed. Reason: The underlying connection was closed: Unable to connect to the remote server.."

 

In WSUS itself:

 

"There was an error communicating with the upstream server. Please check your update source and proxy server settings on the Synchronization Options page."

 

Proxy settings are all configured correctly. SUS and everything else works perfectly. The proxy logs are showing attempted SSL connections to update.microsoft.com on port 443.

[Geoff]

And your proxy allows SSL connections correctly?

[Slartibartfast]

Yup.

[Geoff]

Is your proxy a sibling of another web proxy? run by your network provider for example?

[mrtechsystems]

I am interested in this subject I am looking into the WSUS services and how to setup on a Windows 2000 Server Network I would appericate any feeback or any traps not to fall into

 

Thanks

Lee

Senior Tech

[Dos_Box]

I am interested in this subject I am looking into the WSUS services and how to setup on a Windows 2000 Server Network I would appericate any feeback or any traps not to fall into

 

Thanks

Lee

Senior Tech

 

Considering that Win 2k is officially dead (as far as support for you and I goes) on the 30th of this month I would start at 2K3, which is a lovely fluffy server system. My advice would be to start playing with active directory now, immedietly, straight away, as this will be the main way you will administer your network. Getting to grips with how OU's and policies work and learning where all of the components are should be your main priority, closely followed by DNS. 95% of active directory problems will proberbly be traced to DNS and it is a major stumbling block for newcomers, especially as how you configure your clients and replication options. If you have any specific problems then please don't hesitate to post them here.

[tarquel]

Had a play with WSUS today - seems to be really good. Just need some HD space on the server *uh oh*

 

Should be a decent way on keeping tabs on the client pc's and whether they have been updating hotfixes ...or not

 

The new MBSA tool (ver 2) should be a decent addition to helping with this too The current ver aint bad, and I'm beta testing the new version at the moment, tho i had to remove it the other day - think it was making the system behave "oddly"

 

Regards,

N.

[russdev]

Had a play with WSUS today - seems to be really good. Just need some HD space on the server *uh oh*

 

Should be a decent way on keeping tabs on the client pc's and whether they have been updating hotfixes ...or not

 

The new MBSA tool (ver 2) should be a decent addition to helping with this too The current ver aint bad, and I'm beta testing the new version at the moment, tho i had to remove it the other day - think it was making the system behave "oddly"

 

Regards,

N.

 

yes got that as well just need to work out how to export to csv

 

russ

[Geoff]

The new MBSA tool (ver 2) should be a decent addition to helping with this too

 

I also use Nessus for security scanning.

[russdev]

has anyne tried putting wus on a w/s..

 

sounds daft but not happy about putting wus on our sims server so would be easier and safer to install on a w/s might even use dedicated w/s not sure..

 

Russ

[Geoff]

Wont install. You need a server OS.

[russdev]

ok anyone installed it on sims server any problems etc

[mrtechsystems]

Thanks for the info DOS_Box yeah the school is running Windows 2000 Servers and upgrading in the near furture I think it will be next summer just so busy at the moment.

[tarquel]

@russ:

 

Not yet...

 

As I have two domains on seperate IP ranges (admin & curriculum), I was thinking about setting up two WSUS servers i.e. so that the admin systems using sims .net dont get all the updates from MS - only critical ones (to prevent supposed sims' problems etc).

 

The DC on the admin domain is the only "server" running the domain, and has the server-side stuff of SIMS .net setup up on it. Not a problem as there are only 6-8 workstations connected to it.

 

I might give it a whirl to see what happens (*gulps*) but not sure whether I will as I notice in WSUS that you can setup groups of computers so I could assign the admin workstations to the curriculum WSUS and limit the updates that way

 

At least, if I setup two WSUS servers, at least there's less of a load on the curriculum DC (which is where WSUS is setup at the moment - will be on the Exchange server that I'll be setting up in the summer hols).

 

Not sure that any of this ranting helps but I hope to get into the WSUS server as much as poss so will be able to help better in the future, tho it seems a pretty simple setup - tho at the moment, if I put the server name into the web browser, I get the IIS error message (thought that WSUS's install sets it up for me? answers on a postcard pls... )

 

Cheers,

N.

[tarquel]

 

Anyone know what this is and how to fix it? I just noticed it and its probably the cause of why the client pc's aren't updating....

 

Event Type: Error

Event Source: Windows Server Update Services

Event Category: Update Services Service

Event ID: 506

Date: 27/06/2005

Time: 06:13:02

User: N/A

Computer:

Description:

The SelfUpdate Tree is not working. Clients may not be able to update to the latest WUA client software and communicate with the WSUS Server.

 

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

 

I cant browse to the location of it either - via webbrowser that is, so although IIS is installed, maybe its to do with that.

 

Any thoughts?

 

Cheers,

Nath

[Geoff]

Your using a SBS server. Go make the changes detailed here.

 

http://wsus.editme.com/WSUSonSBS

[tarquel]

LMAO

 

Naa tis 100% Windows Server 2003 Std

 

def not SBS.

 

[will take a look at the link anyhow ta - may still be relevent]

 

EDIT:

Even installed to the alt. port - option during WSUS setup but alas, no joy

 

(yes, used port address in the manually typed i.e. http://servername:8530 but no good )

 

Nath

[ajbritton]

I've only tried WSUS twice.

 

Attempt 1

Freshly built Win2K3 SP1 server (from slipstreamed CD). WSUS went on OK, but would not download anything.

 

Attempt 2

Rebuilt the server (with RTM CD), applied SP1 then installed WSUS. Seemed to work OK, but I had to fix permissions on some folders before clients could download updates.

 

I'm installing it again on a production server in a week or so. This will be a 2K3 server with SP1 applied so fingers crossed. It will also have full SQL Server rather than MSDE - If anyone knows of any issues, I'd be glad to hear from you

[E1uSiV3]

Tarquel, did u type http://servername:8530 or just servername:8530, seems daft but ie wont accept it without the http:// and u will get a page cannot be displayed.

 

EDIT: ahh nevermind just realised the board parsed the tag and dropped the h t t p : / / from the start

[tarquel]

Attempt 1

Freshly built Win2K3 SP1 server (from slipstreamed CD). WSUS went on OK, but would not download anything.

 

Attempt 2

Rebuilt the server (with RTM CD), applied SP1 then installed WSUS. Seemed to work OK, but I had to fix permissions on some folders before clients could download updates.

 

I assume you do know that (apparently) the firewall included with 2k3 SP1 is on by default if you install 2003 with SP1 slipstreamed, where-as it isnt enabled after installing SP1 on a existing 2003 install..?

 

Just a thought to why Attempt 1 didnt work

 

Cheers

N.

[tosca925]

I upgraded our SUS server to WSUS about 2 weeks after the release of WSUS. Around 75% of our 730 XP clients picked up the updates without any problems

 

The other 25% failed due to the clients being installed from a RIS image. Some of the clients had the same Autoupdate client ID in the registry. Once i deleted it and rebooted it picked up fine.

 

I use a script now through GPO that checks for 3 reg entires, if they are there it deletes them and leaves a marker so it only does it once. After a couple of weeks i remove the script as al is well.

 

Just keep an eye open after you reimage a room fo r hte sam ething happening, if you do just pop the script in the room OU for a few days.

 

 

 

I have a script also that runs as a one off on a local machine if any one need it.

 

If your interested in the scripts let me know.

 

Also there is a issue (only had it on server 2003 so far) in renaming a machine. I found it corrupts a registry setting and stops updates from being installed. Even if you do a amnual install through windows updates instead of WSUS it still fails to install the updates. I can't remember the setting of the top of my head but ican find it out if any one needs any help.