I thought for today’s post I would cover some of the top questions I get on how to do something on Server Core. In coming weeks I’ll expand this into some of my favorite command line tools.
First up is how to rename the box, since there isn’t a remoteable gui to let you do this. This is straightforward if you are domain joined:
Netdom renamecomputer %computername% /NewName:new-name /UserD:domain-username /PasswordD:*
But netdom doesn’t currently provide a way to rename a non-domain joined computer. It is a bit of a hassle to join and unjoin from a domain just to rename the computer. WMI is the solution to this one. Using WMIC you can rename the computer using:
wmic computersystem where name="%computername%" rename name="new-name"
The one limitation to this is that it must be run while logged on with the default administrator account.
Terminal Services is another common topic. A lot of people think that since there is no shell you can’t TS into Server Core. However, Server Core does include TS remote admin mode, when connected you just have the same experience as if you were logged on locally, a cmd.exe window. TS remote admin mode is not enabled by default and it is another one of those things that is only available in a non-remoteable gui. For this one, we included a script that can be used to turn it on and off, turning it on is done by running:
Cscript \windows\system32\scregedit.wsf /ar 0
Terminal Services by default in Longhorn Server uses a new higher security mode that only allows Vista and Longhorn Server clients to connect. If you want to TS to your Server Core box from a pre-Vista\Longhorn Server Terminal Services client, you need to turn off the higher security mode, which can be done by running:
Cscript \windows\system32\scregedit.wsf /cs 0
Once enabled you can then use the TS MMC snap-ins to remotely manage TS on the Server Core box, or use the TS command line tools. For example, since there is no Start menu to select logoff to end your TS session, you can use the logoff.exe command line tool.
If you are ever trying to find a command line tool to do something, check out the “Command-line reference A-Z” at: http://go.microsoft.com/fwlink/?LinkId=20331. This is from Windows XP/Windows Server 2003 help so doesn’t have any of the new Longhorn tools or switches, but it is a useful place to start.
My friend, netdom works like a charm renaming non-domain joined computers.
I realize this post is over 2 years old... but we just (finally) got our 2008 dvd and were thrilled to see a core option.
So we tried it out. On a machine destined to be a terminal server. Oops. It doesn't do that.
Ok, fine, we'll use core for our web server cluster! Oh, sorry, you can have IIS but no ASP.NET because that's managed code.
Then I read here that you can actually turn on terminal services, but only in admin mode (oh, thanks...) and even then you only get the CLI. Why would I use RDP for a CLI? Isn't that kind of the point of ssh and its precursor telnet?
Come on, Microsoft peoples! Give us a core os that we can actually use for something more than dns, dhcp, file/print, and ad! Those are the things that use the least amount of resources in the first place! :)
My 10 (binary) cents.