locked
WHS2011 - Various + Workgroup name? RRS feed

  • Question

  • I have just installed WHS2011 to VMWare Workstation VM - a nice and easy install :-) As an aside, I will definitely be upgrading to WHS2011 - DE removal isn't a deal-breaker for me, in fact in a way I am glad it has gone because I think it will make the OS more reliable - I always found DE in WHS V1 somewhat problematic ;-) I have just done a test back up of WHS2011 via iSCSI to my QNAP TS-419P+ - looks like that solution will work well :-) Now to the question, I don't seem to be able to change the Workgroup name from 'WORKGROUP' as the 'Change...' button is disabled (greyed out) in System Properties - is there anyway to do this or maybe it isn't even necessary? I was just trying to set it up to use the same name as the rest of my network.
    Friday, February 4, 2011 3:30 PM

Answers

All replies

  • Not necessary.
    Friday, February 4, 2011 10:28 PM
  • I have the same problem as you have. This means that my Win7 will see the server but de server does not seen my whs v1. My Xtreamer does not see WHS V2. That problem needs fixing.

    I do like de DE. Wantede the copy 300 gb from Win7 to WHS V2. Did not succeed. Dirve to small. I had a 250 and 2 Tb installed. WHS1 would not give me that problem. Now I have to thing were to put my data.


    Klaas
    Sunday, February 6, 2011 5:56 PM
  • Not necessary.

    Indeed if you use the default workgroup name in all machines. But I do not do that. Wrong answer I think
    Klaas
    Sunday, February 6, 2011 5:57 PM
  • Try Smart-X CoreConfig...quick fix to change your Server workgroup name.

    I have tried the open source CoreConfigurator but can't get it to work on WHS 2011.


    Hutch
    Sunday, February 6, 2011 11:24 PM
  • See this post to change Workgropu name, worked for me with 2011 Release Candidate

    http://social.microsoft.com/Forums/en/whsvailbeta/thread/9562b42c-a252-4c96-8e3d-c2ebbef35275?prof=required

    ittech-xp

    You can... Only during setup...

    When the setup gets to the part where you are asked to name it, simply hit SHIFT-F10

    you'll get a command prompt.

    Type "control system" and press enter

    use the system control panel that pops up to change the workgroup name but leave the server name and everything else alone.

    close the window, don't reboot the system.  Continue with the setup, and once it's all going you'll have that workgroup name and the certificates in certificate services will be named properly too so you don't have to re-build that junk after the fact, which is possible as well but a real PITA.

     


    Texas
    Monday, February 7, 2011 12:49 AM
  • On Sun, 6 Feb 2011 23:24:02 +0000, Big Honcho wrote:

    Try Smart-X CoreConfig...quick fix to change your Server workgroup name.

    I have tried the open source CoreConfigurator but can't get it to work on WHS 2011.

    WHS 2011 is not based on Server Core. Also, changing the workgroup name is
    blocked post setup because Active Directory Certificate Services is
    installed and configured during setup. Changing either the computer name or
    the workgroup name post setup will break Certificate Services.


    Paul Adare
    MVP - Identity Lifecycle Manager
    http://www.identit.ca
    Binary:  Possessing the ability to have friends of both sexes.

    Monday, February 7, 2011 7:04 AM
  • On Sun, 6 Feb 2011 23:24:02 +0000, Big Honcho wrote:

    Try Smart-X CoreConfig...quick fix to change your Server workgroup name.

    I have tried the open source CoreConfigurator but can't get it to work on WHS 2011.

    WHS 2011 is not based on Server Core. Also, changing the workgroup name is
    blocked post setup because Active Directory Certificate Services is
    installed and configured during setup. Changing either the computer name or
    the workgroup name post setup will break Certificate Services.


    Paul Adare
    MVP - Identity Lifecycle Manager
    http://www.identit.ca
    Binary:  Possessing the ability to have friends of both sexes.


    Thanks for this insight Paul...It is absolutely true that I did experience Certificate problems post-install.
    Hutch
    Monday, February 7, 2011 3:12 PM