Freigeben über

Windows Server Code Name 'Longhorn' - Configuring Core

  • Artikel

I've just been building my demo machines for an event I have tomorrow.  One of my demos is configuring a Core Server installation - so I figured I'd share the effort.

When the Core installation is finished, you have a server with an unknown name, with a blank administrator's password in a workgroup.

To get it configured you'll need these commands:

net user administrator *
hostname
netdom renamecomputer <ComputerName> /NewName:<NewComputerName>
netsh interface ipv4 show interfaces
netsh interface ipv4 set address name="<ID>" source=static address=<StaticIP> mask=<SubnetMask> gateway=<DefaultGateway>
netsh interface ipv4 add dnsserver name="<ID>" address=<DNSIP>index=1
netdom join <ComputerName> /domain:<DomainName> /userd:<UserName> /passwordd:*

And a few optional ones:

Cscript C:\Windows\System32\Scregedit.wsf /ar 0
WinRM quickconfigcontrol timedate.cpl
control intl.cpl
Slmgr.vbs -ato
start /w ocsetup /?

Have fun, Dave.

Comments

  • Anonymous
    January 01, 2003
    The comment has been removed

  • Anonymous
    January 01, 2003
    Excellent!  Thank you for taking the time to share that!  It's working fine now, remote access, everything. Many thanks, Dave. Do you know if MS has any betas available for running Core for the new virtual hosting? I don't see it as a role, but in our summit, as a premier partner, MS presented it....which is one reason why we're prototyping this thing.  Otherwise, we're off buying more VMWare... Oh, thanks again for your help! Len

  • Anonymous
    January 01, 2003
    So this is a "feature" (read - bug). It is a firewall issue - but just stopping the firewall doesn't fix it.  The way I have gotten around it (as a quick and dirty fix) is to disable the advanced firewall on all profiles: netsh advfirewall set allprofiles state off Once you've joined a domain, you can manage all this from group policy. Hope this helps (it will - I've been there before). Dave.