+ Post New Thread
Results 1 to 4 of 4
Enterprise Software Thread, WSUS console & duplicate (workgroup) computer names in Technical; Scenario: Multiple machines in different places with different IPs, different Sus IDs, but same NETBIOS name e.g. "Alice" and the ...
  1. #1

    Join Date
    Jan 2006
    Location
    Surburbia
    Posts
    2,178
    Thank Post
    74
    Thanked 307 Times in 243 Posts
    Rep Power
    116

    WSUS console & duplicate (workgroup) computer names

    Scenario: Multiple machines in different places with different IPs, different Sus IDs, but same NETBIOS name e.g. "Alice" and the name can NOT changed. You only get one entry for Alice in the WSUS console, and the info probably relates to the last Alice that reported (don't know).

    Couple of questions then:

    1) Can anything be (easily) done in this scenario e.g. persuade MS client-side to report the client with a FQDN? Would fiddling with the Primary DNS Suffix help?

    2) If not, then will all the Alices's still get (approved) updates OK i.e. is this essentially just WSUS console issue?

  2. #2

    AngryTechnician's Avatar
    Join Date
    Oct 2008
    Posts
    3,730
    Thank Post
    698
    Thanked 1,214 Times in 761 Posts
    Rep Power
    395
    I haven't ever tested it myself, but yes, this scenario should be possible if you specify the primary DNS suffix on the machines so that every client knows its own distinct FQDN. To my knowledge the NETBIOS name is not important to WSUS, but WSUS doesn't do its own DNS lookups, and relies on the client to tell it what its FQDN actually is.

  3. Thanks to AngryTechnician from:

    PiqueABoo (26th June 2011)

  4. #3

    Join Date
    Jan 2006
    Location
    Surburbia
    Posts
    2,178
    Thank Post
    74
    Thanked 307 Times in 243 Posts
    Rep Power
    116
    I've just finished testing that: If you set the Primary DNS Suffix it does get used with WSUS e.g. set that to "example.local" and a standalone box DOES now show in WSUS console as "alice.example.local". Or at least it did for me fairly quickly after a wuauclt /ResetAuthorization /DetectNow.

    Next trick I need then, is how to set a Primary DNS Suffix from the command line. Still working on it, but it looks like it might be a case of setting the tcpip\parameters registry values "Domain" and "NV Domain" & restarting. Unless anyone knows of an 'official' MS util that can do it?

  5. #4

    AngryTechnician's Avatar
    Join Date
    Oct 2008
    Posts
    3,730
    Thank Post
    698
    Thanked 1,214 Times in 761 Posts
    Rep Power
    395
    Give these options a whirl: Change Primary DNS Suffix



SHARE:
+ Post New Thread

Similar Threads

  1. Replies: 7
    Last Post: 28th April 2011, 10:09 PM
  2. Replies: 2
    Last Post: 18th May 2010, 03:46 PM
  3. Replies: 13
    Last Post: 30th June 2009, 05:23 PM
  4. Replies: 7
    Last Post: 3rd October 2007, 02:30 PM
  5. Workgroup PC on WSUS
    By mattx in forum Windows
    Replies: 4
    Last Post: 25th June 2007, 01:44 PM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •