porkchopexpress
IS-IT--Management
Does anyone know when WSUS 3.0 final is set for our WSUS is acting up and i can't quite get to the bottom of it so i was planning on a reinstall but seeing this makes me this i'l wait if we're talking weeks.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
WSUS 3.0 3
- Thread starter porkchopexpress
- Start date
- Status
-
2
- #2
-
1
- Thread starter
- #3
porkchopexpress
IS-IT--Management
Yep same here i nearly cried at the thought of them chugging through the 17 updates that are required this month.
From what I've seen & read, I don't think it's going to be terribly soon. Although I can't wait till it's out, since it will be MMC based.
Pat Richard, MCSE MCSA:Messaging CNA
Microsoft Exchange MVP
Want to know how email works? Read for yourself -
Pat Richard, MCSE MCSA:Messaging CNA
Microsoft Exchange MVP
Want to know how email works? Read for yourself -
- Thread starter
- #6
porkchopexpress
IS-IT--Management
Yes the MMC looks to be a big improvement over the web interface Pat fingers crossed it won't be too long.
Nice one RoadKi11 lets hope there is an improvement with the scanning.
Cheers.
Nice one RoadKi11 lets hope there is an improvement with the scanning.
Cheers.
Thanks, porkchopexpress! Kinda funny as I just deployed WSUS on a new SQL 2005 box the day before I read about the new beta..... I might have used that instead.
Pat Richard, MCSE MCSA:Messaging CNA
Microsoft Exchange MVP
Want to know how email works? Read for yourself -
Pat Richard, MCSE MCSA:Messaging CNA
Microsoft Exchange MVP
Want to know how email works? Read for yourself -
- Thread starter
- #8
porkchopexpress
IS-IT--Management
It's always the same. I was rescently told that a product we run wouldn't support SQL 2005 so we licenced 2000 only for the company to email me two months later to inform me that they now support 2005.
Greetings,
Just wanted to give an update of my testing of WSUS 3. I must say so far ive had good results with it correcting the catalog scanning issue. Ive been testing it on 3 workstations 2 XP's and 1 2K that have been my most serious problem children with the run away svchost process. WSUS 3 seems to have completely resolved this issue, thankfully. Some added notes about WSUS 3, seems they have completely removed the web interface which i guess is ok because the mmc snapin is pretty robust. I am having problems connecting to the snapin remotely, this could be because of many reasons. My test server is not a member of my domain, i cant see why this would be a problem, it doesnt ask me to authenticate like i thought it would, just blows an error saying it cant connect. The mmc snapin works fine from the localhost however so im not wasting a lot time working out that issue yet. The mmc snapin is a bit different than you are use to with the web interface and takes a little getting use to. It still seems to sync stuff you tell it not to in the package info setup, like language packs and patches for for x64 systems and such. I plan on expanding my testing a bit but i will probably wait on a full production rollout until its RTM. One other thing, if you plan to use it you will need to install MMC 3, i thought i was running this but all my machines seem to be at MMC 2, guess this wasnt released as an update. There is a different version of MMC 3 for 2K3 and XP so pay attention to that. You will also need to install the Report Viewer Control, do a search on microsoft and it comes right up. You need both of those for the wsus snapin to work.
RoadKi11
Just wanted to give an update of my testing of WSUS 3. I must say so far ive had good results with it correcting the catalog scanning issue. Ive been testing it on 3 workstations 2 XP's and 1 2K that have been my most serious problem children with the run away svchost process. WSUS 3 seems to have completely resolved this issue, thankfully. Some added notes about WSUS 3, seems they have completely removed the web interface which i guess is ok because the mmc snapin is pretty robust. I am having problems connecting to the snapin remotely, this could be because of many reasons. My test server is not a member of my domain, i cant see why this would be a problem, it doesnt ask me to authenticate like i thought it would, just blows an error saying it cant connect. The mmc snapin works fine from the localhost however so im not wasting a lot time working out that issue yet. The mmc snapin is a bit different than you are use to with the web interface and takes a little getting use to. It still seems to sync stuff you tell it not to in the package info setup, like language packs and patches for for x64 systems and such. I plan on expanding my testing a bit but i will probably wait on a full production rollout until its RTM. One other thing, if you plan to use it you will need to install MMC 3, i thought i was running this but all my machines seem to be at MMC 2, guess this wasnt released as an update. There is a different version of MMC 3 for 2K3 and XP so pay attention to that. You will also need to install the Report Viewer Control, do a search on microsoft and it comes right up. You need both of those for the wsus snapin to work.
RoadKi11
- Thread starter
- #10
porkchopexpress
IS-IT--Management
Excellent news lets hope it doesn't take to long to reach RTM.
- Thread starter
- #11
porkchopexpress
IS-IT--Management
My current WSUS server is causing me a few headaches well i thought it was the server but it now appears to be the clients. If i delete the client it reappears with 'Not reported' next to it and then it never reports some clients on this switch work ok but others do not. They all worked untill a month ago but i can't think of any changes they all still connect to the same HP Procurve switch which runs straight to the server room.
If i force a detect i see the following error in the event log:
Event ID: 3019
Source: MRxSmb
The redirector failed to determine the connection type.
I can't think why this would affect the client i've only ever seen this error when the NetBIOS over TCP/IP attempts to query the loopback adapter for network speed when viewing a share on the same client as the share exists on.
I've reinstalled XP SP2 on one of them as well to rule out any wsus client issues. I might try swapping the ports on the switch.
Any other ideas?
If i force a detect i see the following error in the event log:
Event ID: 3019
Source: MRxSmb
The redirector failed to determine the connection type.
I can't think why this would affect the client i've only ever seen this error when the NetBIOS over TCP/IP attempts to query the loopback adapter for network speed when viewing a share on the same client as the share exists on.
I've reinstalled XP SP2 on one of them as well to rule out any wsus client issues. I might try swapping the ports on the switch.
Any other ideas?
- Thread starter
- #12
porkchopexpress
IS-IT--Management
I think i might of found an answer.
Known Client Issues:
1. Some clients have been impacted by a known issue in with Windows Server 2003 http.sys and IIS. In some cases, this transient issue will appear to prevent clients from checking in, because they receive invalid responses from the server after some attempts. It was previously believed to be an issue with IIS compression and there was a workaround suggested to disable compression, and then rename the %windir%\system32\inetsrv\suscomp.dll file and restart the IIS, and the Update Services service. Further Investigation shows the problem source to be a known condition with IIS and http.sys, which is not related to compression, and for which there is an available hotfix. It is not recommended to disable compression as this will not impact the problem source, and possibly increase network traffic & server load, while reducing the number of clients you can effectively serve. Further information about the issue and obtaining the hotfix can be found: . This hotfix does require Service Pack 1 be installed to the Windows Server 2003.
Known Client Issues:
1. Some clients have been impacted by a known issue in with Windows Server 2003 http.sys and IIS. In some cases, this transient issue will appear to prevent clients from checking in, because they receive invalid responses from the server after some attempts. It was previously believed to be an issue with IIS compression and there was a workaround suggested to disable compression, and then rename the %windir%\system32\inetsrv\suscomp.dll file and restart the IIS, and the Update Services service. Further Investigation shows the problem source to be a known condition with IIS and http.sys, which is not related to compression, and for which there is an available hotfix. It is not recommended to disable compression as this will not impact the problem source, and possibly increase network traffic & server load, while reducing the number of clients you can effectively serve. Further information about the issue and obtaining the hotfix can be found: . This hotfix does require Service Pack 1 be installed to the Windows Server 2003.
- Thread starter
- #13
porkchopexpress
IS-IT--Management
Yep that patch solved the issue. It's been an odd one that as some clients fail one day then work the next and others won't work at all but a couple of hours after that patch they all started checking in.
- Thread starter
- #14
porkchopexpress
IS-IT--Management
Hey RoadKi11
What happens with the scanning then does it just work in the background now and does it still run in the svchost process?
What happens with the scanning then does it just work in the background now and does it still run in the svchost process?
I didnt look that close, i would guess it still runs in the svchost but i dont know that for sure. I pushed 27 updates to the 3 clients in 3 different batches. None of the clients experienced any slow or sluggish behavior like they did on wsus2. I did this during business hours to ensure the users would notice if the updates caused issues. I informed the user to pay attention to the responsiveness of their workstations when i released the updates. None of the user noticed or experienced any problems with the updates. Its a huge difference because on wsus2 even 1 update would cripple those 3 workstations for up to 6-8 hours. This could be just a coincidence but im really hoping its not.
RoadKi11
RoadKi11
- Thread starter
- #16
porkchopexpress
IS-IT--Management
How is the testing going Roady are the clients still unaffected? Any issues with the release candidate version?
- Thread starter
- #18
porkchopexpress
IS-IT--Management
Sorry porkchop must have missed your last post. Was just going to update this one last time. I have nearly completed my rollout to production with WSUS 3. Yeah yeah yeah i know never rollout a beta or RC to production but WSUS 2 was completely worthless to me so desperate situations call for desperate solutions. Anyway, i have nothing but good things to say about WSUS 3 so far, i havent had any problems or seen any bugs with the RC im running. Other than it still synchronizes non-english language updates even though i only have english selected. I worked out the problem with connecting to the remote MMC snapin, it was because my test server was not part of my domain, once made it a member server i remotely connected fine. I am really warming up to the MMC snapin, i didnt like it at first but now that im more familiar with it, its easy to use and the reporting is really nice and quick. The new SQL eats up a little more RAM than the older msde did but nothing to freak out about i guess. My clients finally once again dont even notice the update process, updates slip right in without pegging the CPU for hours. I would recommend if you are experiencing the high CPU utilization with WSUS 2 to move to WSUS 3 you will be happy. You should obviously test before pushing it out as your experience may not be the same as mine.
RoadKi11
RoadKi11
- Thread starter
- #20
porkchopexpress
IS-IT--Management
What version does the client agent show as?
- Status
Similar threads
- Locked
- Question
- Locked
- Question