Setting Up Server 2008 Core

Configuring IPv4 on the Local network interface:

http://www.petri.co.il/configure_tcp_ip_from_cmd.htmand

http://www.markwilson.co.uk/blog/2005/10/using-netsh-to-set-multiple-dns-server.htm

  • To set your IP address:
    netsh interface ip set address name=”Local Area Connection” static <ip address> <netmask> <default gateway>
    (Note:  If you are using netsh on a platform earlier than Server 2008 (i.e. Server 2003) you may nned to provide more explicit parameters such as:
    netsh interface ip set address name”Local Area Connection” source=”static” addr=”<addr>” mask=”<mask>” gateway=”<gateway>” gwmetric=”1″)
  • To set your first DNS server:
    netsh interface ip set dns “Local Area Connection” static <DNSServerIP>
    (NOTE:  You may want to set DNS info first if you need your interface to be functional as soon as the IP address comes online.)
  • To set your first WINS server:
    netsh interface ip set wins “Local Area Connection” static <WINSServerIP>
  • Setting up additional WINS and DNS servers:
    • run “netsh”
    • go to the context “interface ip”
    • run:
      add dns "Local Area Connection" <DNSServerIP> index=2
      then
      add wins "Local Area Connection" <WINSServerIP> index=2
    • Verify settings with:
      "ipconfig /all" or "netsh interface ip show config"

Installing VMWare Tools:

http://www.flickr.com/photos/jimboy/sets/72157602876493918

  • In the ESX console, initiate “Install VMWare Tools”
  • At the server console, switch to D:, run setup.exe with typical options, wait wait wait wait, affirm that you want to install the updated help files, reboot.

Changing the console resolution:

http://www.netometer.com/video/tutorials/core-server-change-resolution/index.php

  • use regedit.exe
  • navigate to:
    HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlVideo{BBF118A6-4C44-4FE4-A8A3-965A9A577F98}000
    (or whichever GUID key have the subkey of “0000” named “VolatileSettings”)
  • Change “DefaultSettings.XResolution” and “DefaultSettings.YResolution” to your desired values in decimal format.

Enabling remote desktop:slmgr

http://www.petri.co.il/managing-windows-2008-server-core-rdp.htm

  • cscript C:WindowsSystem32Scregedit.wsf /ar 0
  • netsh advfirewall firewall set rule group=”Remote Desktop” new enable=yes

Activating a KMS:

  • After networking is configured, use SLMGR.vbs to activate your KMS
  • For you sanity, you may wish to perform “cscript //H:cscript” to set the command line script interpreter as the default script handler.
  • run “slmgr.vbs -ipk <KMS product key>”
  • run “slmgr.vbs -ato” to activate the KMS
  • run “Netsh advfirewall firewall set rule group=“Key Management Server” new enable=yes” to allow KMS client traffic through the firewall (more on this below)
  • run “slmgr.vbs -dlv” to monitor KMS activity.

Allowing Remote Administration:

http://blogs.technet.com/server_core/archive/2008/01/14/configuring-the-firewall-for-remote-management-of-a-workgroup-server-core-installation.aspx

  • Netsh advfirewall firewall set rule group=“<rule group>” new enable=yes
  • <rule group> can include:
  • Remote Event Log Management
  • Remote Service Management
  • File and Printer Sharing
  • Remote Scheduled Tasks Management
  • Performance Logs and Alerts
  • Remote Volume Management
  • Windows Firewall Remote Management
  • Now that I have remote access via MMC, I see that the group “Key Management Service” is also available.  Also see the “Remote Desktop” group, above.
  • Advertisements

    Leave a Reply

    Fill in your details below or click an icon to log in:

    WordPress.com Logo

    You are commenting using your WordPress.com account. Log Out / Change )

    Twitter picture

    You are commenting using your Twitter account. Log Out / Change )

    Facebook photo

    You are commenting using your Facebook account. Log Out / Change )

    Google+ photo

    You are commenting using your Google+ account. Log Out / Change )

    Connecting to %s