In the last 2 months I passed my first two MCITP (Microsoft Certified IT Professional) Certifications. The first was the new MCITP: Windows Server 2008 R2, Virtualization Administrator and the second was the MCITP: Enterprise Administrator. I am really happy it was hard work but I think it was worth it.
Now copy the extracted folder to the Hyper-V Core Server. In my case i copied in the C:\ root of the Core Server via the administrative network share. If you have easy physical access to the server, you could also use a USB stick or something like that.
Now connect to the Core Server and use the cmd.exe to navigate to the folder with the HP Support Pack
Run the “hpsum.exe” to start the HP Smart Update Manager
When the HP Smart Update Manager is started you can use it like on a Full Server installation of Windows Server 2008
You could also try to run the HP Smart Update Manager on another machine and use the remote connection feature.
This is a simple Powershell script which deletes Files older than some days. You can use it to cleanup old logfiles or other things. If you run the script the first time you can add the “-WhatIf” parameter after Remove-Item command.
Quest released PowerGUI Pro and PowerGUI 2.3. Both get really cool new features. In the Pro version the most changes are done in the MobileShell. In the free version the most changes are done in the support for snippets. And they now support virtualization now with the VMware Powerpack right build in.
If you wanna know more about the changes of PowerGUI visit poshoholic.com.
If you have a Windows Server 2008 R2 Core Server or a Hyper-V R2 Server, which is also managed like a Core Server, you are really happy if you can use the Server Manager for this Remote Machine. Basiclly I had the the Remote Setup done. I could connect to the remote Machine with the Server Manager but when I tried to use the Disk Management on a remote Server and I got the following error “RPC server is unavailable”. After checking it I found the solution. The Problem is that the Firewall blocks the remote communication to virtual disk service. So you have to open the Firewall on the Management Machine
First make sure you activated all the Remote Management options on the Remote Machine. I had all done this but its good to check that.
Now you can run the following Command in cmd on the Management Machine to add the a new firewall rule
netsh advfirewall firewall set rule group="Remote Volume Management" new enable=yes