Announcement

Collapse
No announcement yet.

Server Core Hyper-V Access with RSAT Tools

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Server Core Hyper-V Access with RSAT Tools

    So I am putting together a couple of servers that are running Server 2008 Core. They are dedicated Virtual Machine Hosts and I am having difficulty administering them. These are not in a domain and neither is the client that I am using to access them.

    First off, I have had to do a lot of work just to be able to manage these machines remotely and Disk Management in the Computer Management MMC still does not work. I looked at the blog by John Howard and followed the steps to get it working but that seems too involved for it to be the actual way to set this up. Is this the only solution? Shouldn't it just work? I am fine if it is the only way but I just want to know if there is another way.

    I have installed Hyper-V on the server core machine and now I am trying to access it from my workstation. I try to do a direct ip connect (there are no records in the DNS server of this machine) and i get an error saying that the computer could not be resolved. However, when I add the hostname and the ip address to the hosts file I can access it just fine. Is there something that I am missing? I try to ping the hostname and it does not resolve (i allowed pings to go through the windows firewall). I just feel like I am missing something.

  • #2
    Re: Server Core Hyper-V Access with RSAT Tools

    For The Hyper V Server

    Disconnect all external USB devices and Ethernet cables.
    Only the screen, keyboard and mouse should be plugged in.
    Install Hyper V Server on Physical server in a fixed 50GB partition.
    On first boot log into Hyper V server administrator and blank password now you will be prompted to change it.
    Using the Hyper V server configurator (Blue Box).
    Change Hyper V server name to “HYPER-V” and reboot.
    Never add the Hyper V server to a Domain leave it in the default workgroup.
    Using the Hyper V server configurator (Blue Box).
    Configure it to use a static IP of “192.168.16.1” gateway and dns1 should be router address i.e. “192.168.16.254”.
    Host file location “C:\Windows\System32\drivers\etc\hosts”
    Edit your laptops hosts file using notepad and add this line “192.168.16.1 HYPER-V”
    Command line type “notepad.exe hosts” in the etc directory.
    Edit Hyper V server hosts file using notepad and add this line “192.168.16.200 Senan-Laptop”
    From Hyper V server ping “Senan-Laptop” and make sure you get a reply.
    The Firewall will prevent you from pinging “Hyper-V” from your laptop.
    Using the Hyper V server configurator (Blue Box).
    Check Regional settings and Date and Time are correct.
    Using the Hyper V server configurator (Blue Box).
    Add “senan.finucane” to the local administrators group with same password as your domain account.
    Run the following command as an administrative user on the Hyper V server:
    'netsh advfirewall firewall set rule group=”Windows Management Instrumentation (WMI)” new enable=yes'
    Run the following command as an administrative user on the Hyper V server:
    ‘net localgroup “Distributed COM Users” senan.finucane /add’
    Run the following commands as an administrative user on the Hyper V server:
    ‘netsh advfirewall set allprofiles settings remotemanagement enable ‘
    Run the following commands as an administrative user on the Hyper V server:
    ‘netsh advfirewall firewall set rule group="Remote Administration" new enable=yes’
    Run the following commands as an administrative user on the Hyper V server:
    'netsh advfirewall firewall set rule group="Remote Desktop" new enable=yes’
    Run the following commands as an administrative user on the Hyper V server:
    ‘cscript %windir%\system32\scregedit.wsf /AR 0’
    Run the following commands as an administrative user on the Hyper V server:
    ‘cscript %windir%\system32\scregedit.wsf /CS 0’
    Run the following commands as an administrative user on the Hyper V server:
    ‘winrm quickconfig –q’
    Run the following command as an administrative user on the Hyper V server:
    ‘net start VDS’
    This starts the Virtual Disk Service, so through computer management you can administer the disks.
    Run the following command as an administrative user on the Hyper V server:
    ‘sc config VDS start= auto’
    This sets the Virtual Disk Service to auto start.
    Run the following command as an administrative user on the Hyper V server:
    ‘‘netsh advfirewall firewall set rule group="Remote Volume Management" new enable=yes’’
    Reboot Hyper V Server
    Note – Its good practice to move the swap file to another volume or disk if possible.
    See this how too, http://blog.mpecsinc.ca/2008/04/serv...-file-wmi.html

    For the remote access management machine ( Vista SP1 or Server 2008 )

    Run the following command as an administrative user on the remote access management machine:
    ‘netsh advfirewall firewall set rule group="Windows Management Instrumentation (WMI)" new enable=yes’
    Run the following command as an administrative user on the remote access management machine:
    ‘netsh firewall add allowedprogram program=%windir%\system32\mmc.exe name="Microsoft Management Console"’
    Run the following command as an administrative user on the remote management machine:
    ‘‘netsh advfirewall firewall set rule group="Remote Volume Management" new enable=yes’’
    At a run prompt type “Dcomcnfg”
    When the Component Services MMC opens click Component Services\Computers\My Computer
    Right click my computer then properties, them com security tab.
    Click “Edit Limits” under Access Permissions, the click “Anonymous Logon”
    Verify that Allow is clicked for “Local Access” and “Remote Access”
    Install RSAT tools and Hyper V Manager MMC if on a Vista SP1 remote machine.
    Install Hyper V tools from add features in Server 2008 if remote machine is Server 2008.
    If your remote access machine is Server 2008 make sure and apply KB950050, it updates the Hyper V tools.
    You can also use Computer Management in Administrative Tools on your remote management machine to manage the Hyper V server just right click and connect to a different computer.
    Always used fixed size disks for both boot and data virtual hard disks for far better performance.
    Only use IDE controllers for boot VHD’s and SCSI for data VHD’s.
    Create fixed size disk first then install OS then attach VHD’s to OS.

    EDIT NOTE BY MOD: Personal information and advertising links to personal website removed by mod.
    Last edited by danielp; 17th December 2008, 23:50.

    Comment


    • #3
      Re: Server Core Hyper-V Access with RSAT Tools

      Originally posted by brycejlowe View Post
      So I am putting together a couple of servers that are running Server 2008 Core. They are dedicated Virtual Machine Hosts and I am having difficulty administering them. These are not in a domain and neither is the client that I am using to access them.

      First off, I have had to do a lot of work just to be able to manage these machines remotely and Disk Management in the Computer Management MMC still does not work. I looked at the blog by John Howard and followed the steps to get it working but that seems too involved for it to be the actual way to set this up. Is this the only solution? Shouldn't it just work? I am fine if it is the only way but I just want to know if there is another way.

      I have installed Hyper-V on the server core machine and now I am trying to access it from my workstation. I try to do a direct ip connect (there are no records in the DNS server of this machine) and i get an error saying that the computer could not be resolved. However, when I add the hostname and the ip address to the hosts file I can access it just fine. Is there something that I am missing? I try to ping the hostname and it does not resolve (i allowed pings to go through the windows firewall). I just feel like I am missing something.

      Here is an alternative instruction set: MPECS Inc. Blog: Server Core - From Scratch to Hyper-V Production

      Once you have run the various commands on the Hyper-V box, you will be able to manage it via RSAT.

      Philip

      Comment

      Working...
      X