Missing PC's after upgrading to WSUS Ver3 "Simon Gronow" <srg[ at ]babcom.net.au> 5/6/2007 8:34:10 AM I have justed noticed that approx 21 Computers from the list after upgrading to WSUS3. And a few others in wrong groups. Anyone seen this? We did also upgrade to Windows SQL 2005 SP1 as apart of the ugprade. Should we have used the Internal database? Is it just a case of waiting for Pc's to report in? Thanks Rgds SImon.

Re: Missing PC's after upgrading to WSUS Ver3 "Simon Gronow" <srg[ at ]babcom.net.au> 5/7/2007 10:17:27 AM More Info I have 3 remote systems (all with the same computer name) all syncing to one WSUS ver 3 server. I noticed that it seems to take the last machines name as the index after syncing. We did not have this issue with ver 2. I suspect that it was SUSID index as per WSUS ver 2 These machines/site are all not connecting via a Domain Controller. (ie. they are in a workgroup only) "Simon Gronow" <srg[ at ]babcom.net.au> wrote in message news:unmxul7jHHA.596[ at ]TK2MSFTNGP06.phx.gbl... [Quoted Text] >I have justed noticed that approx 21 Computers from the list after >upgrading to WSUS3. And a few others in wrong groups. Anyone seen this? > > > We did also upgrade to Windows SQL 2005 SP1 as apart of the ugprade. > Should we have used the Internal database? > > > Is it just a case of waiting for Pc's to report in? > > Thanks > > > Rgds > SImon. >

Re: Missing PC's after upgrading to WSUS Ver3 "Cecils\(MSFT\)" <cecils[ at ]online.microsoft.com> 5/7/2007 6:18:03 PM There was new logic implemented to remove duplicate computer names in WSUS 3.0. We had a lot of feedback around non-syspreped machines showing up multiple time in the 2.0 UI. Now we key off of FQDN, and clientID's. If there is already an FQDN, then we just change the underlying information about the computer, so that only one entry appears in the UI. We also remove the duplicate machine names during the Upgrade process as well -- -- Cecil [MSFT] Deployment, WSUS Microsoft This posting is provided "As Is" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm "Simon Gronow" <srg[ at ]babcom.net.au> wrote in message news:ez4bHEJkHHA.596[ at ]TK2MSFTNGP06.phx.gbl... [Quoted Text] > More Info > > > I have 3 remote systems (all with the same computer name) all syncing to > one WSUS ver 3 server. I noticed that it seems to take the last machines > name as the index after syncing. We did not have this issue with ver 2. I > suspect that it was SUSID index as per WSUS ver 2 > > > These machines/site are all not connecting via a Domain Controller. (ie. > they are in a workgroup only) > > > > > > "Simon Gronow" <srg[ at ]babcom.net.au> wrote in message > news:unmxul7jHHA.596[ at ]TK2MSFTNGP06.phx.gbl... >>I have justed noticed that approx 21 Computers from the list after >>upgrading to WSUS3. And a few others in wrong groups. Anyone seen this? >> >> >> We did also upgrade to Windows SQL 2005 SP1 as apart of the ugprade. >> Should we have used the Internal database? >> >> >> Is it just a case of waiting for Pc's to report in? >> >> Thanks >> >> >> Rgds >> SImon. >> > >

Re: Missing PC's after upgrading to WSUS Ver3 "Simon Gronow" <srg[ at ]babcom.net.au> 5/8/2007 7:55:22 AM Ahhhhh righto. Thanks "Cecils(MSFT)" <cecils[ at ]online.microsoft.com> wrote in message news:uu3MPQNkHHA.3816[ at ]TK2MSFTNGP02.phx.gbl... [Quoted Text] > There was new logic implemented to remove duplicate computer names in WSUS > 3.0. We had a lot of feedback around non-syspreped machines showing up > multiple time in the 2.0 UI. Now we key off of FQDN, and clientID's. If > there is already an FQDN, then we just change the underlying information > about the computer, so that only one entry appears in the UI. > > We also remove the duplicate machine names during the Upgrade process as > well > > -- > -- > Cecil [MSFT] > Deployment, WSUS > Microsoft > > This posting is provided "As Is" with no warranties, and confers no > rights. > Use of included script samples are subject to the terms specified at > http://www.microsoft.com/info/cpyright.htm > > "Simon Gronow" <srg[ at ]babcom.net.au> wrote in message > news:ez4bHEJkHHA.596[ at ]TK2MSFTNGP06.phx.gbl... >> More Info >> >> >> I have 3 remote systems (all with the same computer name) all syncing to >> one WSUS ver 3 server. I noticed that it seems to take the last machines >> name as the index after syncing. We did not have this issue with ver 2. I >> suspect that it was SUSID index as per WSUS ver 2 >> >> >> These machines/site are all not connecting via a Domain Controller. (ie. >> they are in a workgroup only) >> >> >> >> >> >> "Simon Gronow" <srg[ at ]babcom.net.au> wrote in message >> news:unmxul7jHHA.596[ at ]TK2MSFTNGP06.phx.gbl... >>>I have justed noticed that approx 21 Computers from the list after >>>upgrading to WSUS3. And a few others in wrong groups. Anyone seen this? >>> >>> >>> We did also upgrade to Windows SQL 2005 SP1 as apart of the ugprade. >>> Should we have used the Internal database? >>> >>> >>> Is it just a case of waiting for Pc's to report in? >>> >>> Thanks >>> >>> >>> Rgds >>> SImon. >>> >> >> >

Re: Missing PC's after upgrading to WSUS Ver3 ip-rob <ip-rob.2sr2vg[ at ]DoNotSpam.com> 6/25/2007 8:09:14 PM We manage many small networks and to productize the networks we have standardized machine names and domain names. The result has been a dramatic decrease in management expense of the independent networks. We have not had any issues with any software (including consolidated reporting using remote monitoring software by IBM) until WSUS 3.0. So for those of us that understand the issues associated with identical FQDN's and have engineered solutions to handle it, with it working for us, what are we supposed to use for update management without deploying another 175 WSUS servers? -- ip-rob ------------------------------------------------------------------------ ip-rob's Profile: http://forums.techarena.in/member.php?userid=27135 View this thread: http://forums.techarena.in/showthread.php?t=741919 http://forums.techarena.in

Re: Missing PC's after upgrading to WSUS Ver3 Harry Johnston <harry[ at ]scms.waikato.ac.nz> 6/25/2007 9:48:14 PM ip-rob wrote: [Quoted Text] > We manage many small networks and to productize the networks we have > standardized machine names and domain names. The result has been a > dramatic decrease in management expense of the independent networks. How come? I'm not trying to be sarcastic, I just for the life of me can't see what computer names have to do with management expenses. (It suggests to me that you were doing something rather weird beforehand, and that there was probably a much better solution to your problems than to duplicate machine names.) > We have not had any issues with any software (including consolidated > reporting using remote monitoring software by IBM) until WSUS 3.0. That's really quite surprising. This is hardly likely to be a scenario that software developers are going to take into account. To be honest, you were bound to run into trouble sooner or later. > So for those of us that understand the issues associated with identical > FQDN's and have engineered solutions to handle it, with it working for > us, what are we supposed to use for update management without deploying > another 175 WSUS servers? I expect that your only realistic options are (1) stick with WSUS 2 until it is withdrawn; (2) deploy one WSUS server per network; (3) use a third-party or Microsoft commercial product instead of WSUS; (4) reengineer to avoid duplicate FQDN's. Harry.

Re: Missing PC's after upgrading to WSUS Ver3 ip-rob <ip-rob.2ssjng[ at ]DoNotSpam.com> 6/26/2007 2:33:24 PM The same computer names simplifies configuration of many packages such as Outlook (mail server fqdn) to file backups and restores. Scripts used to manage the networks can be standardized yielding a very high-level of automation. We only have one system administrator per 110 servers, a very low ratio, accomplished through automation and standardization. The packages we use without issue assign GUID's to machines and manage the GUID (similar to the SSID in the old WSUS). This allows the package to deal with things from public IP changes to machine name changes. You say that we were bound to run into issues at some point but the ONLY issue we have had is with WSUS 3.0. Of the 100's of servers and all the packages that our customers use this is the sole software package that is a problem. When looking at this as the sole exception I think the WSUS re-engineering missed something. I really think you have the right answer, move to a product created by some other vendor. That is where we will start! Thanks... -- ip-rob ------------------------------------------------------------------------ ip-rob's Profile: http://forums.techarena.in/member.php?userid=27135 View this thread: http://forums.techarena.in/showthread.php?t=741919 http://forums.techarena.in

Re: Missing PC's after upgrading to WSUS Ver3 Harry Johnston <harry[ at ]scms.waikato.ac.nz> 6/26/2007 6:28:43 PM ip-rob wrote: [Quoted Text] > You say that we were bound to run into issues at some point but the > ONLY issue we have had is with WSUS 3.0. Of the 100's of servers and > all the packages that our customers use this is the sole software > package that is a problem. I would assume that most of those packages don't communicate or share data between the different networks, though. It should be noted that if these machines are owned by your customers (I think technically if the operating system is licensed to them) you aren't allowed to use your WSUS server to update them anyway, unless you have a special license with Microsoft to do so. Harry.

Re: Missing PC's after upgrading to WSUS Ver3 ip-rob <ip-rob.2ssxjg[ at ]DoNotSpam.com> 6/26/2007 7:34:15 PM The primary tool we use in the backend that has to deal with the duplicate FQDN's is monitoring and remote management. These tools will share data between the various servers but do so using an agent on the machine. The agent is identified to the server using a GUID for identification. WSUS 3.0, however, doesn't share data between the networks...it's sole purpose is for managing and monitoring updates for Microsoft products only. I guess the real question is why was the feature which worked in WSUS 2.0 was removed? The reason in Cecil's (MSFT) post was to deal with non-sysprepped clones. Microsoft doesn't support the deployment of Windows to clones without using sysprep, so why modify their product to accommodate it? The logic doesn't make sense since they say they won't support clones deployed a certain way and then modify a critical update distribution server to accommodate the unsupported deployment. No need to worry, we own the hardware and software for the products. -- ip-rob ------------------------------------------------------------------------ ip-rob's Profile: http://forums.techarena.in/member.php?userid=27135 View this thread: http://forums.techarena.in/showthread.php?t=741919 http://forums.techarena.in

Re: Missing PC's after upgrading to WSUS Ver3 Harry Johnston <harry[ at ]scms.waikato.ac.nz> 6/26/2007 8:34:29 PM ip-rob wrote: [Quoted Text] > WSUS 3.0, however, doesn't share data between the networks It collates data from the multiple networks into one place, and sends data from a single point out to the multiple networks. Sorry if my choice of wording was unclear. > ...it's sole > purpose is for managing and monitoring updates for Microsoft products > only. I guess the real question is why was the feature which worked in > WSUS 2.0 was removed? Because for most people it was a pain, and nobody thought anyone would ever want to do anything like your setup. The new logic will certainly be a big improvement for me; it should save me having to manually delete the old computer entries from WSUS every time I reinstall a computer. Harry.