Duplicate names Con1_uk 5/23/2007 2:29:02 PM I have setup WSUS 3 on Win2k3 Sevrer Web Edition The pcs this server will update are in 100's of locations and in each location there are about 4 or 5 pcs all called the same Example Location1 comp1 comp2 comp3 Location2 Comp1 Comp2 Comp3 Now this is causing problems once the pcs report in and jump into their correct group they disapear once another pc with the same name reports from their own group. It definatley dont like the same names but I thought it would use the IP addresses which are definately different. The SIDS are different because Sysprep was run on all the pcs before deployment. Can anybody see a work around other than last resort change the pc names? Thanks.

Re: Duplicate names "Cecils\(MSFT\)" <cecils[ at ]online.microsoft.com> 5/23/2007 11:29:24 PM Not for WSUS 3. The logic for determining duplicate names has changed significantly from WSUS 2.0. Now if there is an FQDN with an existing ClientID, the ClientID will be overwritten in the database, therefore only one computer with a given FQDN will be visible to the Admin UI. At this point I think your only option is to rename the computers -- 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 "Con1_uk" <Con1uk[ at ]discussions.microsoft.com> wrote in message news:CF1C532F-975E-44DE-8881-DE88092E38BD[ at ]microsoft.com... [Quoted Text] >I have setup WSUS 3 on Win2k3 Sevrer Web Edition > > The pcs this server will update are in 100's of locations and in each > location there are about 4 or 5 pcs all called the same > > Example > > Location1 > > comp1 > comp2 > comp3 > > Location2 > > Comp1 > Comp2 > Comp3 > > > Now this is causing problems once the pcs report in and jump into their > correct group they disapear once another pc with the same name reports > from > their own group. It definatley dont like the same names but I thought it > would use the IP addresses which are definately different. The SIDS are > different because Sysprep was run on all the pcs before deployment. > > Can anybody see a work around other than last resort change the pc names? > > > Thanks.

Re: Duplicate names Con1_uk 5/24/2007 8:45:01 AM Thanks for your reply. Does it matter that these pcs are not in a domain? Could I change the workgroup name? Would this work? Thanks. "Cecils(MSFT)" wrote: [Quoted Text] > Not for WSUS 3. The logic for determining duplicate names has changed > significantly from WSUS 2.0. Now if there is an FQDN with an existing > ClientID, the ClientID will be overwritten in the database, therefore only > one computer with a given FQDN will be visible to the Admin UI. > > At this point I think your only option is to rename the computers > > -- > 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 > > "Con1_uk" <Con1uk[ at ]discussions.microsoft.com> wrote in message > news:CF1C532F-975E-44DE-8881-DE88092E38BD[ at ]microsoft.com... > >I have setup WSUS 3 on Win2k3 Sevrer Web Edition > > > > The pcs this server will update are in 100's of locations and in each > > location there are about 4 or 5 pcs all called the same > > > > Example > > > > Location1 > > > > comp1 > > comp2 > > comp3 > > > > Location2 > > > > Comp1 > > Comp2 > > Comp3 > > > > > > Now this is causing problems once the pcs report in and jump into their > > correct group they disapear once another pc with the same name reports > > from > > their own group. It definatley dont like the same names but I thought it > > would use the IP addresses which are definately different. The SIDS are > > different because Sysprep was run on all the pcs before deployment. > > > > Can anybody see a work around other than last resort change the pc names? > > > > > > Thanks. > >

Re: Duplicate names "Lawrence Garvin \(MVP\)" <onsitech[ at ]community.nospam> 5/28/2007 4:57:23 AM "Con1_uk" <Con1uk[ at ]discussions.microsoft.com> wrote in message news:CF1C532F-975E-44DE-8881-DE88092E38BD[ at ]microsoft.com... [Quoted Text] >I have setup WSUS 3 on Win2k3 Sevrer Web Edition That sounds problematic... > The pcs this server will update are in 100's of locations and in each > location there are about 4 or 5 pcs all called the same I guess that depends on whether you're using subdomains in your AD, or you're not using AD at all, in which case you've got more complex problems than worrying about how they're going to report to a WSUS 3 server. > Can anybody see a work around other than last resort change the pc names? That should have been your *first* resort. PC names need to be unique within any LAN environment, either by virtue of different domain memberships (e.g. subdomains), or by some other methodology. I'm quite surprised this hasn't been an issue prior to now. -- 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: Duplicate names "Lawrence Garvin \(MVP\)" <onsitech[ at ]community.nospam> 5/28/2007 4:58:21 AM "Con1_uk" <Con1uk[ at ]discussions.microsoft.com> wrote in message news:DABCC0CB-3CC2-4084-B6C6-86E32374F9B3[ at ]microsoft.com... [Quoted Text] > Does it matter that these pcs are not in a domain? Could I change the > workgroup name? Would this work? No, WSUS is oblivious to your workgroups. -- 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 ..... > > Thanks. > > "Cecils(MSFT)" wrote: > >> Not for WSUS 3. The logic for determining duplicate names has changed >> significantly from WSUS 2.0. Now if there is an FQDN with an existing >> ClientID, the ClientID will be overwritten in the database, therefore >> only >> one computer with a given FQDN will be visible to the Admin UI. >> >> At this point I think your only option is to rename the computers >> >> -- >> 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 >> >> "Con1_uk" <Con1uk[ at ]discussions.microsoft.com> wrote in message >> news:CF1C532F-975E-44DE-8881-DE88092E38BD[ at ]microsoft.com... >> >I have setup WSUS 3 on Win2k3 Sevrer Web Edition >> > >> > The pcs this server will update are in 100's of locations and in each >> > location there are about 4 or 5 pcs all called the same >> > >> > Example >> > >> > Location1 >> > >> > comp1 >> > comp2 >> > comp3 >> > >> > Location2 >> > >> > Comp1 >> > Comp2 >> > Comp3 >> > >> > >> > Now this is causing problems once the pcs report in and jump into their >> > correct group they disapear once another pc with the same name reports >> > from >> > their own group. It definatley dont like the same names but I thought >> > it >> > would use the IP addresses which are definately different. The SIDS are >> > different because Sysprep was run on all the pcs before deployment. >> > >> > Can anybody see a work around other than last resort change the pc >> > names? >> > >> > >> > Thanks. >> >>