Wsus3 via WSUS2 "not needed". Massimo Rosen <mrosenno[ at ]spamcfc-it.de> 5/23/2007 10:26:10 PM Hi. As announced, WSUS3 is available through WSUS as of today. However, it shows as "not needed" on my WSUS server (Wsus 2.01 on Windows 2003R2 SP1). Anybody else? On a side-note. TOday I also approved the WSUS 2.01 SP1 Client Update. After it installed itelf to my WSUS server via selfupdate (so not the install into WSUS, but the real update of the WSUS client), all my (manually configured via gpedit.msc) WUAU policies on the machine were unset. CU, Massimo

Re: Wsus3 via WSUS2 "not needed". "Siva Shanmugam [MSFT]" <sivsha[ at ]online.microsoft.com> 5/24/2007 12:15:01 AM The update should be offered to Windows Server 2003 SP1 and SP2. Can you please send us the Windowsupdate.log on the WSUS server machine? "Massimo Rosen" <mrosenno[ at ]spamcfc-it.de> wrote in message news:4654BF82.B0C72B2C[ at ]spamcfc-it.de... [Quoted Text] > Hi. > > As announced, WSUS3 is available through WSUS as of today. However, it > shows as "not needed" on my WSUS server (Wsus 2.01 on Windows 2003R2 > SP1). > > Anybody else? > > On a side-note. TOday I also approved the WSUS 2.01 SP1 Client Update. > After it installed itelf to my WSUS server via selfupdate (so not the > install into WSUS, but the real update of the WSUS client), all my > (manually configured via gpedit.msc) WUAU policies on the machine were > unset. > > CU, > Massimo

Re: Wsus3 via WSUS2 "not needed". Massimo Rosen <mrosenno[ at ]spamcfc-it.de> 5/24/2007 7:07:43 AM Hi, "Siva Shanmugam [MSFT]" wrote: [Quoted Text] > > The update should be offered to Windows Server 2003 SP1 and SP2. Can you > please send us the Windowsupdate.log on the WSUS server machine? Here's the last detection cycle: And yes, WSUS3.0 *is* approved for installation. <g> 2007-05-24 06:49:10:890 1540 117c AU ############# 2007-05-24 06:49:10:890 1540 117c AU ## START ## AU: Search for updates 2007-05-24 06:49:10:890 1540 117c AU ######### 2007-05-24 06:49:10:890 1540 117c AU <<## SUBMITTED ## AU: Search for updates [CallId = {E79625B5-0504-4A4F-92AA-BACF3D6EB917}] 2007-05-24 06:49:10:906 1540 11d8 Agent ************* 2007-05-24 06:49:10:906 1540 11d8 Agent ** START ** Agent: Finding updates [CallerId = AutomaticUpdates] 2007-05-24 06:49:10:906 1540 11d8 Agent ********* 2007-05-24 06:49:10:906 1540 11d8 Agent * Online = Yes; Ignore download priority = No 2007-05-24 06:49:10:906 1540 11d8 Agent * Criteria = "IsHidden=0 and IsInstalled=0 and DeploymentAction='Installation' and IsAssigned=1 or IsHidden=0 and IsPresent=1 and DeploymentAction='Uninstallation' and IsAssigned=1 or IsHidden=0 and IsInstalled=1 and DeploymentAction='Installation' and IsAssigned=1 and RebootRequired=1 or IsHidden=0 and IsInstalled=0 and DeploymentAction='Uninstallation' and IsAssigned=1 and RebootRequired=1" 2007-05-24 06:49:10:906 1540 11d8 Agent * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} 2007-05-24 06:49:10:906 1540 11d8 Misc Validating signature for C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wuident.cab: 2007-05-24 06:49:10:906 1540 11d8 Misc Microsoft signed: Yes 2007-05-24 06:49:11:203 1540 11d8 Misc Validating signature for C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wuident.cab: 2007-05-24 06:49:11:218 1540 11d8 Misc Microsoft signed: Yes 2007-05-24 06:49:11:234 1540 11d8 Misc Validating signature for C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wsus3setup.cab: 2007-05-24 06:49:11:250 1540 11d8 Misc Microsoft signed: Yes 2007-05-24 06:49:11:265 1540 11d8 Setup *********** Setup: Checking whether self-update is required *********** 2007-05-24 06:49:11:265 1540 11d8 Setup * Inf file: C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wsus3setup.inf 2007-05-24 06:49:11:265 1540 11d8 Setup Update NOT required for C:\WINDOWS\system32\cdm.dll: target version = 7.0.6000.374, required version = 7.0.6000.374 2007-05-24 06:49:11:265 1540 11d8 Setup Update NOT required for C:\WINDOWS\system32\wuapi.dll: target version = 7.0.6000.374, required version = 7.0.6000.374 2007-05-24 06:49:11:265 1540 11d8 Setup Update NOT required for C:\WINDOWS\system32\wuapi.dll.mui: target version = 7.0.6000.374, required version = 7.0.6000.374 2007-05-24 06:49:11:265 1540 11d8 Setup Update NOT required for C:\WINDOWS\system32\wuauclt.exe: target version = 7.0.6000.374, required version = 7.0.6000.374 2007-05-24 06:49:11:265 1540 11d8 Setup Update NOT required for C:\WINDOWS\system32\wuaucpl.cpl: target version = 7.0.6000.374, required version = 7.0.6000.374 2007-05-24 06:49:11:265 1540 11d8 Setup Update NOT required for C:\WINDOWS\system32\wuaucpl.cpl.mui: target version = 7.0.6000.374, required version = 7.0.6000.374 2007-05-24 06:49:11:265 1540 11d8 Setup Update NOT required for C:\WINDOWS\system32\wuaueng.dll: target version = 7.0.6000.374, required version = 7.0.6000.374 2007-05-24 06:49:11:265 1540 11d8 Setup Update NOT required for C:\WINDOWS\system32\wuaueng.dll.mui: target version = 7.0.6000.374, required version = 7.0.6000.374 2007-05-24 06:49:11:265 1540 11d8 Setup Update NOT required for C:\WINDOWS\system32\wucltui.dll: target version = 7.0.6000.374, required version = 7.0.6000.374 2007-05-24 06:49:11:281 1540 11d8 Setup Update NOT required for C:\WINDOWS\system32\wucltui.dll.mui: target version = 7.0.6000.374, required version = 7.0.6000.374 2007-05-24 06:49:11:281 1540 11d8 Setup Update NOT required for C:\WINDOWS\system32\wups.dll: target version = 7.0.6000.374, required version = 7.0.6000.374 2007-05-24 06:49:11:281 1540 11d8 Setup Update NOT required for C:\WINDOWS\system32\wups2.dll: target version = 7.0.6000.374, required version = 7.0.6000.374 2007-05-24 06:49:11:281 1540 11d8 Setup Update NOT required for C:\WINDOWS\system32\wuweb.dll: target version = 7.0.6000.374, required version = 7.0.6000.374 2007-05-24 06:49:11:281 1540 11d8 Setup * IsUpdateRequired = No 2007-05-24 06:49:13:218 1540 11d8 PT +++++++++++ PT: Synchronizing server updates +++++++++++ 2007-05-24 06:49:13:218 1540 11d8 PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://194.180.198.96/ClientWebService/client.asmx 2007-05-24 06:49:13:515 1540 11d8 PT WARNING: Cached cookie has expired or new PID is available 2007-05-24 06:49:13:515 1540 11d8 PT Initializing simple targeting cookie, clientId = cd79f5c3-25f1-41c8-9418-c42f15c17bd4, target group = , DNS name = woc-piwexa2y6vn 2007-05-24 06:49:13:515 1540 11d8 PT Server URL = http://194.180.198.96/SimpleAuthWebService/SimpleAuth.asmx 2007-05-24 06:49:22:421 1540 11d8 PT +++++++++++ PT: Synchronizing extended update info +++++++++++ 2007-05-24 06:49:22:421 1540 11d8 PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://194.180.198.96/ClientWebService/client.asmx 2007-05-24 06:49:24:218 1540 11d8 Agent * Found 0 updates and 12 categories in search; evaluated appl. rules of 320 out of 456 deployed entities 2007-05-24 06:49:24:468 1540 11d8 Agent ********* 2007-05-24 06:49:24:468 1540 11d8 Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates] 2007-05-24 06:49:24:468 1540 11d8 Agent ************* 2007-05-24 06:49:24:484 1540 dbc AU >>## RESUMED ## AU: Search for updates [CallId = {E79625B5-0504-4A4F-92AA-BACF3D6EB917}] 2007-05-24 06:49:24:484 1540 dbc AU # 0 updates detected 2007-05-24 06:49:24:484 1540 dbc AU ######### 2007-05-24 06:49:24:484 1540 dbc AU ## END ## AU: Search for updates [CallId = {E79625B5-0504-4A4F-92AA-BACF3D6EB917}] 2007-05-24 06:49:24:484 1540 dbc AU ############# 2007-05-24 06:49:24:484 1540 dbc AU AU setting next detection timeout to 2007-05-24 11:25:09 2007-05-24 06:49:29:468 1540 11d8 Report REPORT EVENT: {CB40166D-D275-4843-96D9-4605C99A28F0} 2007-05-24 06:49:24:468+0200 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Windows Update Client successfully detected 0 updates. 2007-05-24 06:49:29:468 1540 11d8 Report REPORT EVENT: {6C756CC4-51D9-4734-8D59-15244BC1DE2E} 2007-05-24 06:49:24:468+0200 1 153 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status. 2007-05-24 06:55:21:265 1540 11d8 Report Uploading 2 events using cached cookie, reporting URL = http://194.180.198.96/ReportingWebService/ReportingWebService.asmx 2007-05-24 06:55:21:281 1540 11d8 Report Reporter successfully uploaded 2 events. CU, Massimo

Re: Wsus3 via WSUS2 "not needed". "Siva Shanmugam [MSFT]" <sivsha[ at ]online.microsoft.com> 5/24/2007 5:51:08 PM Can you please do the following? 1. Cut and paste the following in notepad window, save it as trace.reg. <cut> Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Trace] "Flags"=dword:00000016 "level"=dword:00000004 </cut> 2. Then double click on it to save the values in registry. 3. Open a cmd window (Click on Start->Run->Type cmd and click Ok) 4. Type "net stop wuauserv" 5. Type "net start wuauserv" 6. Type "wuauclt /detectnow" Send me the windowsupdate.log with the extended trace info. I will try to see why this is not getting offered to the client. Also, I would like to know if you have SUS 1.0 installed (side by side) on the same machine? "Massimo Rosen" <mrosenno[ at ]spamcfc-it.de> wrote in message news:465539BF.176C5AE3[ at ]spamcfc-it.de... [Quoted Text] > Hi, > > "Siva Shanmugam [MSFT]" wrote: >> >> The update should be offered to Windows Server 2003 SP1 and SP2. Can you >> please send us the Windowsupdate.log on the WSUS server machine? > > Here's the last detection cycle: And yes, WSUS3.0 *is* approved for > installation. <g> > > 2007-05-24 06:49:10:890 1540 117c AU ############# > 2007-05-24 06:49:10:890 1540 117c AU ## START ## AU: Search for updates > 2007-05-24 06:49:10:890 1540 117c AU ######### > 2007-05-24 06:49:10:890 1540 117c AU <<## SUBMITTED ## AU: Search for > updates [CallId = {E79625B5-0504-4A4F-92AA-BACF3D6EB917}] > 2007-05-24 06:49:10:906 1540 11d8 Agent ************* > 2007-05-24 06:49:10:906 1540 11d8 Agent ** START ** Agent: Finding > updates [CallerId = AutomaticUpdates] > 2007-05-24 06:49:10:906 1540 11d8 Agent ********* > 2007-05-24 06:49:10:906 1540 11d8 Agent * Online = Yes; Ignore > download priority = No > 2007-05-24 06:49:10:906 1540 11d8 Agent * Criteria = "IsHidden=0 and > IsInstalled=0 and DeploymentAction='Installation' and IsAssigned=1 or > IsHidden=0 and IsPresent=1 and DeploymentAction='Uninstallation' and > IsAssigned=1 or IsHidden=0 and IsInstalled=1 and > DeploymentAction='Installation' and IsAssigned=1 and RebootRequired=1 or > IsHidden=0 and IsInstalled=0 and DeploymentAction='Uninstallation' and > IsAssigned=1 and RebootRequired=1" > 2007-05-24 06:49:10:906 1540 11d8 Agent * ServiceID = > {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} > 2007-05-24 06:49:10:906 1540 11d8 Misc Validating signature for > C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wuident.cab: > 2007-05-24 06:49:10:906 1540 11d8 Misc Microsoft signed: Yes > 2007-05-24 06:49:11:203 1540 11d8 Misc Validating signature for > C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wuident.cab: > 2007-05-24 06:49:11:218 1540 11d8 Misc Microsoft signed: Yes > 2007-05-24 06:49:11:234 1540 11d8 Misc Validating signature for > C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wsus3setup.cab: > 2007-05-24 06:49:11:250 1540 11d8 Misc Microsoft signed: Yes > 2007-05-24 06:49:11:265 1540 11d8 Setup *********** Setup: Checking > whether self-update is required *********** > 2007-05-24 06:49:11:265 1540 11d8 Setup * Inf file: > C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wsus3setup.inf > 2007-05-24 06:49:11:265 1540 11d8 Setup Update NOT required for > C:\WINDOWS\system32\cdm.dll: target version = 7.0.6000.374, required > version = 7.0.6000.374 > 2007-05-24 06:49:11:265 1540 11d8 Setup Update NOT required for > C:\WINDOWS\system32\wuapi.dll: target version = 7.0.6000.374, required > version = 7.0.6000.374 > 2007-05-24 06:49:11:265 1540 11d8 Setup Update NOT required for > C:\WINDOWS\system32\wuapi.dll.mui: target version = 7.0.6000.374, > required version = 7.0.6000.374 > 2007-05-24 06:49:11:265 1540 11d8 Setup Update NOT required for > C:\WINDOWS\system32\wuauclt.exe: target version = 7.0.6000.374, required > version = 7.0.6000.374 > 2007-05-24 06:49:11:265 1540 11d8 Setup Update NOT required for > C:\WINDOWS\system32\wuaucpl.cpl: target version = 7.0.6000.374, required > version = 7.0.6000.374 > 2007-05-24 06:49:11:265 1540 11d8 Setup Update NOT required for > C:\WINDOWS\system32\wuaucpl.cpl.mui: target version = 7.0.6000.374, > required version = 7.0.6000.374 > 2007-05-24 06:49:11:265 1540 11d8 Setup Update NOT required for > C:\WINDOWS\system32\wuaueng.dll: target version = 7.0.6000.374, required > version = 7.0.6000.374 > 2007-05-24 06:49:11:265 1540 11d8 Setup Update NOT required for > C:\WINDOWS\system32\wuaueng.dll.mui: target version = 7.0.6000.374, > required version = 7.0.6000.374 > 2007-05-24 06:49:11:265 1540 11d8 Setup Update NOT required for > C:\WINDOWS\system32\wucltui.dll: target version = 7.0.6000.374, required > version = 7.0.6000.374 > 2007-05-24 06:49:11:281 1540 11d8 Setup Update NOT required for > C:\WINDOWS\system32\wucltui.dll.mui: target version = 7.0.6000.374, > required version = 7.0.6000.374 > 2007-05-24 06:49:11:281 1540 11d8 Setup Update NOT required for > C:\WINDOWS\system32\wups.dll: target version = 7.0.6000.374, required > version = 7.0.6000.374 > 2007-05-24 06:49:11:281 1540 11d8 Setup Update NOT required for > C:\WINDOWS\system32\wups2.dll: target version = 7.0.6000.374, required > version = 7.0.6000.374 > 2007-05-24 06:49:11:281 1540 11d8 Setup Update NOT required for > C:\WINDOWS\system32\wuweb.dll: target version = 7.0.6000.374, required > version = 7.0.6000.374 > 2007-05-24 06:49:11:281 1540 11d8 Setup * IsUpdateRequired = No > 2007-05-24 06:49:13:218 1540 11d8 PT +++++++++++ PT: Synchronizing > server updates +++++++++++ > 2007-05-24 06:49:13:218 1540 11d8 PT + ServiceId = > {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = > http://194.180.198.96/ClientWebService/client.asmx > 2007-05-24 06:49:13:515 1540 11d8 PT WARNING: Cached cookie has expired > or new PID is available > 2007-05-24 06:49:13:515 1540 11d8 PT Initializing simple targeting > cookie, clientId = cd79f5c3-25f1-41c8-9418-c42f15c17bd4, target group = > , DNS name = woc-piwexa2y6vn > 2007-05-24 06:49:13:515 1540 11d8 PT Server URL = > http://194.180.198.96/SimpleAuthWebService/SimpleAuth.asmx > 2007-05-24 06:49:22:421 1540 11d8 PT +++++++++++ PT: Synchronizing > extended update info +++++++++++ > 2007-05-24 06:49:22:421 1540 11d8 PT + ServiceId = > {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = > http://194.180.198.96/ClientWebService/client.asmx > 2007-05-24 06:49:24:218 1540 11d8 Agent * Found 0 updates and 12 > categories in search; evaluated appl. rules of 320 out of 456 deployed > entities > 2007-05-24 06:49:24:468 1540 11d8 Agent ********* > 2007-05-24 06:49:24:468 1540 11d8 Agent ** END ** Agent: Finding > updates [CallerId = AutomaticUpdates] > 2007-05-24 06:49:24:468 1540 11d8 Agent ************* > 2007-05-24 06:49:24:484 1540 dbc AU >>## RESUMED ## AU: Search for > updates [CallId = {E79625B5-0504-4A4F-92AA-BACF3D6EB917}] > 2007-05-24 06:49:24:484 1540 dbc AU # 0 updates detected > 2007-05-24 06:49:24:484 1540 dbc AU ######### > 2007-05-24 06:49:24:484 1540 dbc AU ## END ## AU: Search for updates > [CallId = {E79625B5-0504-4A4F-92AA-BACF3D6EB917}] > 2007-05-24 06:49:24:484 1540 dbc AU ############# > 2007-05-24 06:49:24:484 1540 dbc AU AU setting next detection timeout to > 2007-05-24 11:25:09 > 2007-05-24 06:49:29:468 1540 11d8 Report REPORT EVENT: > {CB40166D-D275-4843-96D9-4605C99A28F0} 2007-05-24 06:49:24:468+0200 1 > 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates > Success Software Synchronization Windows Update Client successfully > detected 0 updates. > 2007-05-24 06:49:29:468 1540 11d8 Report REPORT EVENT: > {6C756CC4-51D9-4734-8D59-15244BC1DE2E} 2007-05-24 06:49:24:468+0200 1 > 153 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates > Success Pre-Deployment Check Reporting client status. > 2007-05-24 06:55:21:265 1540 11d8 Report Uploading 2 events using cached > cookie, reporting URL = > http://194.180.198.96/ReportingWebService/ReportingWebService.asmx > 2007-05-24 06:55:21:281 1540 11d8 Report Reporter successfully uploaded > 2 events. > > > > CU, > Massimo

Re: Wsus3 via WSUS2 "not needed". Massimo Rosen <mrosenno[ at ]spamcfc-it.de> 5/24/2007 7:00:07 PM Hi, "Siva Shanmugam [MSFT]" wrote: [Quoted Text] > > Can you please do the following? > > 1. Cut and paste the following in notepad window, save it as > trace.reg. > > <cut> > > Windows Registry Editor Version 5.00 > > [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Trace] > > "Flags"=dword:00000016 > > "level"=dword:00000004 I'll get that for you, but it might take a while. > > Also, I would like to know if you have SUS 1.0 installed (side by side) on > the same machine? Not side by side, no, but that same machine indeed used to have SUS 1.0 installed, it was updated to WSUS2 follwing the then current docs. Are you onto something? CU, Massimo

Re: Wsus3 via WSUS2 "not needed". "Lawrence Garvin \(MVP\)" <onsitech[ at ]community.nospam> 5/28/2007 5:12:30 AM "Massimo Rosen" <mrosenno[ at ]spamcfc-it.de> wrote in message news:465539BF.176C5AE3[ at ]spamcfc-it.de... Please note that this WSUS server has no target group information. Most likely reason it's not detecting is because it's querying "Unassigned Computers" for the approval. [Quoted Text] > 2007-05-24 06:49:13:515 1540 11d8 PT Initializing simple targeting > cookie, > clientId = cd79f5c3-25f1-41c8-9418-c42f15c17bd4, > target group = , > DNS name = woc-piwexa2y6vn > 2007-05-24 06:49:13:515 1540 11d8 PT Server URL = > http://194.180.198.96/SimpleAuthWebService/SimpleAuth.asmx And, as I always do when I make these observations.. I'll note the use of a *public* IP Address for your WSUS server. -- Lawrence Garvin, M.S., MCTS, MCP Independent WSUS Evangelist MVP-Software Distribution (2005-2007) https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E Everything you need for WSUS is at http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx And, almost everything else is at http://wsusinfo.onsitechsolutions.com .....

Re: Wsus3 via WSUS2 "not needed". "Siva Shanmugam [MSFT]" <sivsha[ at ]online.microsoft.com> 5/29/2007 5:40:17 PM WSUS 3.0 cannot be installed side by side with SUS 1.0. Can you please make sure SUS 1.0 is completely uninstalled on that machine? The windowsupdate.log will give us more insight on this. Thanks, Siva "Massimo Rosen" <mrosenno[ at ]spamcfc-it.de> wrote in message news:4655E0B7.719E6832[ at ]spamcfc-it.de... [Quoted Text] > Hi, > > "Siva Shanmugam [MSFT]" wrote: >> >> Can you please do the following? >> >> 1. Cut and paste the following in notepad window, save it as >> trace.reg. >> >> <cut> >> >> Windows Registry Editor Version 5.00 >> >> [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Trace] >> >> "Flags"=dword:00000016 >> >> "level"=dword:00000004 > > I'll get that for you, but it might take a while. > >> >> Also, I would like to know if you have SUS 1.0 installed (side by side) >> on >> the same machine? > > Not side by side, no, but that same machine indeed used to have SUS 1.0 > installed, it was updated to WSUS2 follwing the then current docs. Are > you onto something? > > CU, > Massimo

Re: Wsus3 via WSUS2 "not needed". Massimo Rosen <mrosenno[ at ]spamcfc-it.de> 6/11/2007 9:39:52 PM Hi, "Siva Shanmugam [MSFT]" wrote: [Quoted Text] > > WSUS 3.0 cannot be installed side by side with SUS 1.0. Can you please make > sure SUS 1.0 is completely uninstalled on that machine? ANd that was exactly the reason. There still was SUS1.0 listed in software. After removing that, wsus3.0 was offered. Thanks. At a side note: Why does the upgrade to 3.0 from 2.0 change the website port (in my case, from 80 to 8530) without warning? CU, Massimo

Re: Wsus3 via WSUS2 "not needed". Massimo Rosen <mrosenno[ at ]spamcfc-it.de> 6/11/2007 9:43:00 PM Lawrence, "Lawrence Garvin (MVP)" wrote: [Quoted Text] > > "Massimo Rosen" <mrosenno[ at ]spamcfc-it.de> wrote in message > news:465539BF.176C5AE3[ at ]spamcfc-it.de... > > Please note that this WSUS server has no target group information. Yes. And? > Most likely reason it's not detecting is because it's querying "Unassigned > Computers" for the approval. I don't think I understand what difference that should make. Anyways, Siva was right on track, it was the astray software entry for SUS1.0 which apparently the WSUS2.0 update didn't remove. > And, as I always do when I make these observations.. I'll note the use of a > *public* IP Address for your WSUS server. Well, not every IP is public just because in theory it *could* be. That IP isn't routed on the internet. CU, Massimo

Re: Wsus3 via WSUS2 "not needed". "Lawrence Garvin \(MVP\)" <onsitech[ at ]community.nospam> 6/12/2007 12:27:41 AM "Massimo Rosen" <mrosenno[ at ]spamcfc-it.de> wrote in message news:466DC128.BFB557C2[ at ]spamcfc-it.de... [Quoted Text] > At a side note: Why does the upgrade to 3.0 from 2.0 change the website > port (in my case, from 80 to 8530) without warning? It's not entirely "without warning". If you read the dialogs during the installation, they pretty explicitly identify the port that WSUS *will be* installed on, if you proceed with the installation. -- Lawrence Garvin, M.S., MCTS, MCP Independent WSUS Evangelist MVP-Software Distribution (2005-2007) https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E Everything you need for WSUS is at http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx And, almost everything else is at http://wsusinfo.onsitechsolutions.com .....

Re: Wsus3 via WSUS2 "not needed". "Lawrence Garvin \(MVP\)" <onsitech[ at ]community.nospam> 6/12/2007 12:53:50 AM "Massimo Rosen" <mrosenno[ at ]spamcfc-it.de> wrote in message news:466DC1E4.1655D0F2[ at ]spamcfc-it.de... [Quoted Text] >> Please note that this WSUS server has no target group information. > > Yes. And? Then unless you're approving updates for "Unassigned Computers" or "All Computers" nothing will be able to detect any updates. >> Most likely reason it's not detecting is because it's querying >> "Unassigned >> Computers" for the approval. > > I don't think I understand what difference that should make. It won't make any if you are intentionally managing *every* computer in your organization via "Unassigned Computers". But the purpose of "Unassigned Computers" is exactly what the name suggests. It's for computers that register with the WSUS Server, and have not been assigned to another target group. It's also generally only functional when using server-side targeting, or when client-side targeting has not been properly configured. The more likely scenario is that you have assigned target groups, you've approved updates for specific target groups, and this system isn't seeing any of those approvals. > Anyways, > Siva was right on track, it was the astray software entry for SUS1.0 > which apparently the WSUS2.0 update didn't remove. While that certainly would affect your ability to detect/install the WSUS 3.0 upgrade, it doesn't eliminate the basic issue that the cited system still isn't going to see *any* updates until it gets the right target group information. > Well, not every IP is public just because in theory it *could* be. That > IP isn't routed on the internet. Ahem.... somewhere.. someplace.. in the world, that IP Address *IS* routed on the internet, unless you happen to own the entire Class C network. Is this you?: 194.180.198.0 (WCRAFT) wolfcraft GmbH, Kempenich; DE More significantly, if you do not own that Class C network, your use of it as an internal network means you will *never* be able to access any Internet based resources legitimately assigned to that network. The simple fact is that almost *every* Class C network is assigned. The exceptions may include the range: 217.0.0.0 - 223.255.255.0 Not yet allocated See here for details: http://www.flumps.org/ip/c/indexc.html -- Lawrence Garvin, M.S., MCTS, MCP Independent WSUS Evangelist MVP-Software Distribution (2005-2007) https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E Everything you need for WSUS is at http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx And, almost everything else is at http://wsusinfo.onsitechsolutions.com .....

Re: Wsus3 via WSUS2 "not needed". Massimo Rosen <mrosenno[ at ]spamcfc-it.de> 6/12/2007 7:00:40 AM Lawrence, "Lawrence Garvin (MVP)" wrote: [Quoted Text] > > "Massimo Rosen" <mrosenno[ at ]spamcfc-it.de> wrote in message > news:466DC1E4.1655D0F2[ at ]spamcfc-it.de... > > >> Please note that this WSUS server has no target group information. > > > > Yes. And? > > Then unless you're approving updates for "Unassigned Computers" or "All > Computers" nothing will be able to detect any updates. Oh come on, I'm not *that* stupid. > >> Most likely reason it's not detecting is because it's querying > >> "Unassigned > >> Computers" for the approval. > > > > I don't think I understand what difference that should make. > > It won't make any if you are intentionally managing *every* computer in your > organization via "Unassigned Computers". That's exactly what I'm (and actually, *many* WSUS admins are) doing. I don't need groups. > > > Well, not every IP is public just because in theory it *could* be. That > > IP isn't routed on the internet. > > Ahem.... somewhere.. someplace.. in the world, that IP Address *IS* routed > on the internet, unless you happen to own the entire Class C network. You got it. <g> > Is this you?: Not me, but my customer, yes. > More significantly, if you do not own that Class C network, your use of it > as an internal network means you will *never* be able to access any Internet > based resources legitimately assigned to that network. You don't say... Lawrence, really. You should stop believing everybody besides you is stupid and doesn't know how the internet or computer networks work. You're a good guy with a wealth of knowledge about WSUS, but you're not the only one who knows IP. CU, Massimo

Re: Wsus3 via WSUS2 "not needed". Harry Johnston <harry[ at ]scms.waikato.ac.nz> 6/12/2007 10:44:35 PM Massimo Rosen wrote: [Quoted Text] > You don't say... Lawrence, really. You should stop believing everybody > besides you is stupid and doesn't know how the internet or computer > networks work. No, not everybody is stupid. But it's usually worth checking. :-) Harry.

Re: Wsus3 via WSUS2 "not needed". "Lawrence Garvin \(MVP\)" <onsitech[ at ]community.nospam> 6/13/2007 12:53:31 AM "Harry Johnston" <harry[ at ]scms.waikato.ac.nz> wrote in message news:eROIBNUrHHA.1380[ at ]TK2MSFTNGP04.phx.gbl... [Quoted Text] > Massimo Rosen wrote: > >> You don't say... Lawrence, really. You should stop believing everybody >> besides you is stupid and doesn't know how the internet or computer >> networks work. > > No, not everybody is stupid. But it's usually worth checking. :-) And.. shucks... all I did was make an *observation*. It certainly would have been acceptable for a calm, polite, response to the effect of: "Yep, you're right, but since we own the Class C segment, it's a non-issue." So far, in all the uses of routable (public) IP Addresses I've seen assigned to WSUS Servers, this is the *first* that's been actually traced to, and acknowledged to be, owned by the licensee of the WSUS Server. -- Lawrence Garvin, M.S., MCTS, MCP Independent WSUS Evangelist MVP-Software Distribution (2005-2007) https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E Everything you need for WSUS is at http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx And, almost everything else is at http://wsusinfo.onsitechsolutions.com .....

Re: Wsus3 via WSUS2 "not needed". Massimo Rosen <mrosenno[ at ]spamcfc-it.de> 6/13/2007 10:23:37 AM Lawrence, "Lawrence Garvin (MVP)" wrote: [Quoted Text] > > And.. shucks... all I did was make an *observation*. Upps: Me: "That IP isn't routed on the internet. You: "Ahem.... somewhere.. someplace.. in the world, that IP Address *IS* routed on the internet, unless you happen to own the entire Class C network." So which part of my statement was unclear to you so you had to doubt it (which you did)? And that is *not* an observation, but it's a clear statement of you that you do not believe what I said, because otherwise your comment would have been (and it was anyways) entirely superfluous. Oh, and BTW, there could be lots of other reasons why that IP possibly wouldn't be routed besides us owning the netblock, but not routing it. And yet another hint: Instead of publicy belittling posters here (which I may note you do somewhat regularly), a simple traceroute to that IP would have shown you that it's unrouted. > It certainly would have been acceptable for a calm, polite, response to the > effect of: > "Yep, you're right, but since we own the Class C segment, it's a > non-issue." No. You did *not* accept a calm and polite "That IP isn't routed on the internet", despite this statement being very simple and very clear. Anyways, we're getting OT here. CU, Massimo

Re: Wsus3 via WSUS2 "not needed". Harry Johnston <harry[ at ]scms.waikato.ac.nz> 6/13/2007 8:36:00 PM Lawrence Garvin (MVP) wrote: [Quoted Text] > So far, in all the uses of routable (public) IP Addresses I've seen assigned > to WSUS Servers, this is the *first* that's been actually traced to, and > acknowledged to be, owned by the licensee of the WSUS Server. For the record, my WSUS server uses a public IP address which we own, though of course it isn't reachable from outside our LAN. (We own a class B subnet, as do many mid-sized organisations whose internet presence predates the current address shortage. I believe our wireless network uses a private address space, as does some of the networking equipment, but pretty much all our wired computers use public addresses. That's just the way we've always done it.) Harry.

Re: Wsus3 via WSUS2 "not needed". "Asher_N" <ashernat[ at ]gmail.com> 6/14/2007 1:10:28 PM Massimo Rosen <mrosenno[ at ]spamcfc-it.de> wrote in news:466FC5A9.5149A844[ at ]spamcfc-it.de: [Quoted Text] > Lawrence, > > "Lawrence Garvin (MVP)" wrote: >> >> And.. shucks... all I did was make an *observation*. > > Upps: > > Me: "That IP isn't routed on the internet. > > You: "Ahem.... somewhere.. someplace.. in the world, that IP Address > *IS* routed > on the internet, unless you happen to own the entire Class C network." > > So which part of my statement was unclear to you so you had to doubt > it (which you did)? And that is *not* an observation, but it's a > clear statement of you that you do not believe what I said, because > otherwise your comment would have been (and it was anyways) entirely > superfluous. > > Oh, and BTW, there could be lots of other reasons why that IP possibly > wouldn't be routed besides us owning the netblock, but not routing it. > And yet another hint: Instead of publicy belittling posters here > (which I may note you do somewhat regularly), a simple traceroute to > that IP would have shown you that it's unrouted. > >> It certainly would have been acceptable for a calm, polite, response >> to the effect of: >> "Yep, you're right, but since we own the Class C segment, it's a >> non-issue." > > No. You did *not* accept a calm and polite "That IP isn't routed on > the internet", despite this statement being very simple and very > clear. > > Anyways, we're getting OT here. > > CU, > Massimo My, my, aren't we bit pissy today. The way public IPs are used as private IPs inside network, unless you specify that you actually *own* the range, the safe assumption is that you just picked a range of addresses you liked to use inside your network. If you spend enought time here and in the ISA groups, you will see enough screwed up network designs to assume that the design being discussed is bad unless otherwise justified.

Re: Wsus3 via WSUS2 "not needed". "Siva Shanmugam [MSFT]" <sivsha[ at ]online.microsoft.com> 6/14/2007 9:19:28 PM Massimo, [Quoted Text] > At a side note: Why does the upgrade to 3.0 from 2.0 change the website > port (in my case, from 80 to 8530) without warning? Do you have SharePoint Services installed after installing WSUS 2.0? WSUS 3.0 upgrade will detect this and install the services on port 8530. Please let me know. Thanks, Siva "Massimo Rosen" <mrosenno[ at ]spamcfc-it.de> wrote in message news:466DC128.BFB557C2[ at ]spamcfc-it.de... > Hi, > > "Siva Shanmugam [MSFT]" wrote: >> >> WSUS 3.0 cannot be installed side by side with SUS 1.0. Can you please >> make >> sure SUS 1.0 is completely uninstalled on that machine? > > ANd that was exactly the reason. There still was SUS1.0 listed in > software. After removing that, wsus3.0 was offered. Thanks. > > At a side note: Why does the upgrade to 3.0 from 2.0 change the website > port (in my case, from 80 to 8530) without warning? > > CU, > Massimo

Re: Wsus3 via WSUS2 "not needed". "Lawrence Garvin \(MVP\)" <onsitech[ at ]community.nospam> 6/15/2007 2:52:50 AM "Siva Shanmugam [MSFT]" <sivsha[ at ]online.microsoft.com> wrote in message news:O77XymsrHHA.1404[ at ]TK2MSFTNGP03.phx.gbl... [Quoted Text] >> At a side note: Why does the upgrade to 3.0 from 2.0 change the website >> port (in my case, from 80 to 8530) without warning? > Do you have SharePoint Services installed after installing WSUS 2.0? WSUS > 3.0 upgrade will detect this and install the services on port 8530. Please > let me know. No, Siva, he had a catalog file from SUS 1.0 still present in the root of his Default Web Site. -- Lawrence Garvin, M.S., MCTS, MCP Independent WSUS Evangelist MVP-Software Distribution (2005-2007) https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E Everything you need for WSUS is at http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx And, almost everything else is at http://wsusinfo.onsitechsolutions.com .....

Re: Wsus3 via WSUS2 "not needed". Massimo Rosen <mrosenno[ at ]spamcfc-it.de> 6/15/2007 7:04:04 AM Siva, "Siva Shanmugam [MSFT]" wrote: [Quoted Text] > > Massimo, > > > At a side note: Why does the upgrade to 3.0 from 2.0 change the website > > port (in my case, from 80 to 8530) without warning? > Do you have SharePoint Services installed after installing WSUS 2.0? Not knowingly or purposefully, but there actually is a Sharepoint Administration website listed in IIS, on port 5334, which I never bothered about, so I don't know for certain when this was introduced and how. But Looking at the dates of it's files on disk, this seems to have been in place from the day of the installation of that server. Thanks, Massimo

Re: Wsus3 via WSUS2 "not needed". "Lawrence Garvin \(MVP\)" <onsitech[ at ]community.nospam> 6/16/2007 3:07:30 AM "Massimo Rosen" <mrosenno[ at ]spamcfc-it.de> wrote in message news:467239E4.5356C1EB[ at ]spamcfc-it.de... [Quoted Text] >> Do you have SharePoint Services installed after installing WSUS 2.0? > Not knowingly or purposefully, but there actually is a Sharepoint > Administration website listed in IIS, on port 5334, which I never > bothered about If the specific title is "Microsoft Sharepoint Administrator", that's the Frontpage 2003 Server Extensions administration site, which, btw, is *not* supposed to be installed on a WSUS server. (Documented in the Installation Guides.) Why they ever named it "Microsoft Sharepoint Administrator" I don't know. If the specific title is "Sharepoint Central Administration", then that's Windows Sharepoint Services, which opens up yet another long list of issues with WSUS co-existence. But I doubt that's the case, because if you had installed WSS on top of a WSUS server, you'd know it immediately because the WSS installation will break the selfupdate service of WSUS. > so I don't know for certain when this was introduced and how. > But Looking at the dates of it's files on disk, this seems to have > been in place from the day of the installation of that server. It probably was introduced when the machine was converted to an Application Server, and Frontpage Server Extensions was erroneously selected for installation. -- Lawrence Garvin, M.S., MCTS, MCP Independent WSUS Evangelist MVP-Software Distribution (2005-2007) https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E Everything you need for WSUS is at http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx And, almost everything else is at http://wsusinfo.onsitechsolutions.com .....