This is an old revision of the document!
http://stephanco.blogspot.com/2013/07/preview-of-new-pshvm-all-powershell-all.html
This is a checklist to:
There is no need to install .Net 4.0 as it is already part of the base install.
In the black CMD/DOS window that is opened by default, enter the following to configure some standard settings (these are useful and recommended):
:Disable TCPChimney netsh int tcp set global chimney=disabled :Disable Firewall netsh advfirewall set allprofiles state off
This will disable the firewall and allow all traffic. The firewall is on by default and will prevent you from doing anything remotely until you either turn it off or put in exceptions. This will be updated to just allow necessary traffic for better security.
:Install SNMP-Services (only needed if you plan on monitoring your virtualization host with SNMP monitoring software) powershell.exe -command "Add-WindowsFeature SNMP-Service"
Choose Option 2 to configure Server Hostname a. Enter the VHOST hostname and press Enter. b. You will be prompted to Reboot the server. Click Yes.
ADD THE VHOST TO THE DOMAIN Not really Needed, but I will show you how. 1. Form the console use the SConfig window. 2. Select Option 1 to Join the VHOST to a Domain. a. Press D for (D)omain b. Type the Full Domain and press Enter. c. Type the Domain Administrator User Name and press Enter. d. Type the Domain Administrator Password and press Enter. i. You will be prompted if you want to change the hostname. Click No. ii. You will be prompted to Restart the machine. Click Yes.
Now you can map a drive to your vhost\\VHOSTname\C$ to get the download and unzipped files to your vhost that we are about to install.
Make a directory on the root of called C:\ISO and copy your installation OS -iso file into it Make a directory on C:\virtualservers (if you setup a datastore dirve for the VM's just change the C: to D: Copy the folder “PSHVM” that unzipped to C:\pshvm
RDP to the new VHOST
Now Use your DOS prompt and type C:\PSHVM\m.bat to load the Hyper-v Manger menu, choose OK next to the A43 File Manager. A43 if a file manager and has shortcuts in the bottom pane.
Browse to C:\PSHVM and then run the file named vcredist_x86.exe to install the runtime code so you can use the “VMConnect (RDP to VM's) Next you will need to choose the Powershell shortcut. When it opens you will need to type Set-ExecutionPolicy unrestricted and press Enter, answer Yes to allow the change. If you do not do either of these your RDP will not work and you will not be able to use the Hyper-v Manager …which is why you are following this process.
To get the file manager to open at login you will need to use the regedit edit shortcut and add a string value to HKLM\software\microsoft\windows\current version\run called file manager that points to c:\PSHVM\a43\a43.exe. If you want a quick status report each time you login you can also add a string value called welcome that points to C:\PSHVM\welcome.bat.
Choose the shortcut called Hyper-v Manager
Once this opens you will notice a powershell window at the upper left. Leave this open you can minimize it if you want but do not close it unless you want hyper-v manager to close. To close hype-v manager you can press the ESC key, use the X or clikc close.
To use it you just click the ok next to the item you want to perform. A Powershell script will open in a new powershell prompt. read and follow the instructions. Some items will open a GUI file explorer pop-up window, just use it like any other program that tou have installed. If unsure read the title of the pop-up window. Each of the scripts will pause then close and return to the menu above.
Now you have built athe vhost you need to configure it, using PS Hyper-V Manager Set the Virtual Machine and HardDisk paths for the VHost Create a vSwitch Create a new VM via questions and answers (I am assuming it is a windows OS) Start RDP to a VM, answer OS installation questions. set password, turn off firewall, set the IP address and enable RDP Manage VM's DVD/ISO.. Insert MS tools and then install them, reboot Now you can RDP to the server once it comes up and continue setting it upa as needed. Run and Inventory Report of the VHost and VM's to see if it is setup to your specs. RAM vCPU etc. You know have a hyper-v server and a VM running on it.