Posted by essjae on March 2, 2017
If you’re playing around with older OSes in the latest versions of Hyper-V, you’re missing one thing, the Integration Components (IC).
With Win10/Server2016 they no longer include this ISO as the current “supported” OSes all get their IC viaWindows Update.
You can get the IC from Hyper-V 2012/2012R2 Server, a free download, here:
https://www.microsoft.com/en-us/evalcenter/evaluate-hyper-v-server-2012-r2 (you’ll need to either find a way to extract it or install Hyper-V Server in a VM to get the vmguest.iso)
Or, if you’ve got a Windows 8/8.1/2012/2012R2 VM/system available with Hyper-V installed you’ll find it in the C:\windows\system32\ folder.
I’ve got a copy from Hyper-V 2012 R2 here: https://1drv.ms/u/s!AnbqFQxI6C6pidtRrLfIRLDSHKeYmw
No guarantees how long MS will allow it will stay up here, though it’s freely distributed with Hyper-V Server.
Posted in Hyper-V, Virtualization, W2012, Windows 10, Windows 2012, Windows 2012 r2, Windows 2016, Windows 8, Windows 8.1 | Tagged: Hyper-V, Hyper-V 10, Hyper-V 3.0, Microsoft, Virtualization | Leave a Comment »
Posted by essjae on March 7, 2016
Note: This assumes you’ve already got the RSAT tools installed. RSAT for Windows 10
Building on my post here for Hyper-V manager:
You can use the same method to get Active Directory Users and Computers (ADUC) and DNS MMC admin consoles working if you’re logged in with your Microsoft account versus your domain account:
C:\Windows\System32\runas.exe /savecred /user:domain\username "cmd /c Start /B %SystemRoot%\system32\mmc.exe %SystemRoot%\system32\dnsmgmt.msc""
C:\Windows\System32\runas.exe /savecred /user:domain\username "cmd /c Start /B %SystemRoot%\system32\dsa.msc""
When you double-click, you’ll get prompted for the password (if you haven’t already) and also for UAC
DHCP is a little more involved as the RSAT doesn’t include the DHCP manager. NOTE: this is not currently supported by MS
- 1. copy dhcpmgmt.msc and dhcpsnap.dll.mui from %windir%\system32\system32\en-us on the 2012 server to the same location on the w10 pc
- copy dhcpsnap.dll from %windir%\system32\ on the 2012 server to the w10 pc
- From an admin cmd prompt run: regsvr32.exe dhcpsnap.dll
- Create the short-cut: C:\Windows\System32\runas.exe /savecred /user:domain\username “cmd /c Start /B %SystemRoot%\system32\mmc.exe %SystemRoot%\system32\dhcpmgmt.msc””
- Change Icon path: %SystemRoot%\System32\dhcpsnap.dll
You’ll need to manually add your DHCP server each time you run this. I haven’t found a way to save the config.
*This was done with Windows 10 Build 1511 and Windows Server 2012.
For additional snap-ins, just modify the last part of the short-cut with the correct mmc path for the add-in you want.
Posted in Sysadmin, Windows, Windows 10, Windows 2012 | Tagged: ADUC, DHCP, DNS, RSAT, Windows, Windows 10, Windows Server 2012 R2 | Leave a Comment »
Posted by essjae on February 11, 2016
Here’s a quick way to get rid of the “public” network on Windows and switch it to a more usable private network type.
- Open a PowerShell Window.
- Get the list of network profiles on the system. Note the InterfaceIndex number listed, you’ll need it for the final step.
- Change the network interface to private, use the network interface index number from the previous command.
Set-NetConnectionProfile -InterfaceIndex xx -NetworkCategory Private
Posted in Networking, Windows 2012 | Tagged: Networking, powershell, Windows, Windows Server 2012 | Leave a Comment »
Posted by essjae on February 10, 2016
I hit a small issue while working on building up a test SCCM/SCVMM lab in Hyper-V.
My primary system (call it One) has Windows 10 and is domain joined, but I’ve been doing the “Microsoft” thing and logging in with my “Microsoft” account instead of my local domain account.
I’ve got two Hyper-V hosts, one on Windows Server 2012 R2 and another running on Windows 10* (call it Two). I’ve been able to launch my Hyper-V Manager on One and connect and manage the Hyper-V VMs on Server 2012.
However, I hit a roadblock trying to connect to Two. The first thing I tried after failing and getting some error messages was to configure winrm.
I opened an administrator PowerShell window and ran
and followed the wizard and was able to start the winrm service and open the firewall.
Again in a administrator PowerShell window, I ran:
Enable-WSManCredSSP -role client -delegatecomputer two.mydomain.com
Failure! I got a big text message in red that said to run winrm quickconfig.
This is odd, since I did none of this to connect to the Server 2012 Hyper-V instance.
I then shift+right-clicked on Hyper-V Manager and ran it with my domain credentials and it ran! Ah ha! No problem, just create a runas shortcut for Hyper-V Manager.
C:\Windows\System32\runas.exe /user:mydomain\myusername /savecreds "%windir%\System32\mmc.exe "%windir%\System32\virtmgmt.msc""
Again, no joy. Launching my new short-cut from a command prompt showed the error:
740: The requested operation requires elevation.
The command needs ADUC elevation, with some Googling** I finally found a solution, first launch a cmd prompt and then the command. This allows you to receive the ADUC prompt and accept it.
C:\WINDOWS\system32\runas.exe /savecred /user:mydomain\myusername "cmd /c Start /B %windir%\System32\mmc.exe "%windir%\System32\virtmgmt.msc""
The path to the Hyper-V Manager icon is here:
*I don’t recall my logic in installing Windows 10 here instead of Server 2012…it may have just been laziness, an upgrade to Win10 from the previous Windows 8.1 OS that was installed.
Posted in Hyper-V, Uncategorized, Virtualization, Windows 10, Windows 2012 | Tagged: Hyper-V, Microsoft, powershell, RunAs, Virtualization, Windows 10, Windows 2012 r2, winrm | 1 Comment »
Posted by essjae on June 24, 2015
The default password policies are pretty strict for a lab or demo environment. If you’re not in a domain, it’s easy to modify these settings from the Local Security Policies:
- Run gpedit.msc
- Under Computer Configuration–>Windows Settings–>Security Settings–>Account Policies–Password Policy
- Change the Policy Security Settings you want.
Under a domain controller, you can do this via the Active Directory Administrative Center
- Run dsac.exe, or via the GUI it’s under Administrative Tools–>Active Directory Administrative Center
- Go to YourDomain(local)–>System–>Password Settings Container
- Click New from the Tasks menu
- Create your Password Settings
Here’s the window, note that I’ve already created a password policy. A new forest/domain will not have anything populated in it.
I don’t recommend disabling all these settings if you’re in a production environment.
Posted in Sysadmin, Windows 2012 | Tagged: Windows, Windows Server 2012 | Leave a Comment »
Posted by essjae on May 25, 2015
I posted a while back about a nice little utility I use on all my Windows 8.x systems to reclaim those lost pixels from Win 8’s giant, padded borders.
It’s recently been replaced with a new tool, Winaero Tweaker, link: http://winaero.com/comment.php?comment.news.1836
A new feature with Winaero Tweaker allows you to change colors, which is nice when working with Windows Server 2012 R2.
If you try to change the color you’ll see this:
Winaero Tweaker launches with an error in Windows Server 2012 R2, but it doesn’t seem to affect the programs ability to change border size or color.
As you can see, I changed the color from cyan to a light purple, shown in the Winaero Tweaker page
Posted in Computers, Utility, Windows 2012, Windows 8, Windows 8.1 | Tagged: Utilities, Windows, Windows 2012 r2, Windows 8, Windows 8.1 | Leave a Comment »
Posted by essjae on February 21, 2014
Microsoft KB 947821 (http://support.microsoft.com/kb/947821)
If you’ve gotten one of those cryptic 0x800xxxxxx Windows Update errors, Microsoft finally has a fix for Vista and higher, no XP solution.
Fix Windows Update corruption errors such as 0x80070002 and 0x80070057
Windows Update corruption errors prevent Windows updates and service packs from installing. For example, an update might not install if a system file is damaged. If the error you see is in the following list, try the solution in this article.
0x80070002 | 0x8007000D | 0x800F081F | 0x80073712 | 0x800736CC | 0x800705B9 | 0x80070246 | 0x8007370D | 0x8007370B | 0x8007370A | 0x80070057 | 0x800B0100 | 0x80092003 | 0x800B0101 | 0x8007371B | 0x80070490
Windows 8.x and Server 2012 Rx
To resolve this problem, use the inbox Deployment Image Servicing and Management (DISM) tool. Then, install the Windows update or service pack again.
- Open an elevated command prompt. To do this, swipe in from the right edge of the screen, and then tap Search. Or, if you are using a mouse, point to the lower-right corner of the screen, and then click Search. Type Command Prompt in the Search box, right-click Command Prompt, and then click Run as administrator. If you are prompted for an administrator password or for a confirmation, type the password, or click Allow.
- Type the following commands. Press Enter after each command.
Note It may take several minutes for each command operation to be completed.
- DISM.exe /Online /Cleanup-image /Scanhealth
- DISM.exe /Online /Cleanup-image /Restorehealth
- Close the command prompt, and then run Windows Update again.
DISM creates a log file (%windir%/Logs/CBS/CBS.log) that captures any issues that the tool found or fixed. %windir% is the folder in which Windows is installed. For example, the %windir% folder is C:\Windows.
Windows 7, Windows Vista, Windows Server 2008 R2 or Windows Server 2008
See the KB link for the download you need. http://support.microsoft.com/kb/947821
Posted in Vista, W2K8R2, Win7, Windows, Windows 2012, Windows 8, Windows 8.1 | Tagged: Microsoft, Vista, Win7, Windows, windows 2008 r2, Windows 8, Windows 8.1, Windows Server 2008 | Leave a Comment »
Posted by essjae on January 8, 2014
Ben Armstrong has a little blurb about a fix included in the latest rollup for Windows Server 2012 R2
Hyper-V guest OS does not shut down when you restart the host computer that is running Windows Server 2012 R2 or Windows 8.1
Consider the following scenario:
- You set up a Hyper-V virtual machine on a host computer that is running Windows Server 2012 R2 or Windows 8.1.
- You set the Automatic Stop Action setting of the virtual machine to Shut down the guest operating system.
- You restart the host computer.
In this scenario, the guest operating system (OS) on the virtual machine does not shut down. Additionally, after you restart the virtual machine, the following event is logged on the guest OS:Event ID: 6008
Message: The previous system shutdown at time on date was unexpected.
Note If the computer is part of a cluster, this issue does not occur.
This issue occurs because the Virtual Machine Management Service tries to shut down the virtual machine by using the Virtual Machine Worker process. However, the process encounters a logic failure that causes the shutdown operation to fail and reverts the shutdown operation. Therefore, power cycling occurs instead of a clean shutdown.
To resolve this issue, install update rollup 2887595. For more information about how to obtain this update rollup package, click the following article number to go to the article in the Microsoft Knowledge Base:
Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 update rollup: November 2013
Posted in Hyper-V, Virtualization, W2012, Windows, Windows 2012, Windows 8, Windows 8.1 | 3 Comments »
Posted by essjae on September 25, 2013
HVRemote has been updated for Hyper-V v.3 for supported use with Windows 8.x and Windows Server 2012 and R2.
HVRemote reduces the manual configuration steps needed for Hyper-V Remote Management down to a few simple commands, and can diagnose common configuration errors.
- Windows Server 2008 SP1 with Hyper-V RTM update applied (KB950050), Core & Full installations
- Windows Server 2008 SP2, Core & Full installations
- Microsoft Hyper-V Server 2008 SP1 (already contains Hyper-V RTM update)
- Microsoft Hyper-V Server 2008 SP2
- Windows Server 2008 R2, Core & Full installations
- Windows Server 2008 R2 SP1, Core & Full installations
- Microsoft Hyper-V Server 2008 R2
- Microsoft Hyper-V Server 2008 R2 SP1
- Windows Server 2012 Core & Full installations (Version 1.x or later)
- Microsoft Hyper-V Server 2012 (Version 1.x or later)
- Windows 8 Pro & Enterprise x64 with Hyper-V enabled (Version 1.x or later)
- Windows Server 2012 R2 Core & Full installations (Version 1.08 or later)
- Microsoft Hyper-V Server 2012 R2 (Version 1.08 or later)
- Windows 8.1 x64 Client Hyper-V (Version 1.08 or later)
Posted in Hyper-V, Virtualization, W2012, W2K8R2, Windows, Windows 2012, Windows 8 | Tagged: Hyper-V, Hyper-V 3.0, Microsoft, Virtualization, windows 2008 r2, Windows 8 | 3 Comments »
Posted by essjae on July 15, 2013
Ben’s got the hot news again. Need to configure your Hyper-V Machine for widescreen: http://blogs.msdn.com/b/virtual_pc_guy/archive/2013/07/09/configuring-wide-screen-resolutions-in-a-hyper-v-virtual-machine.aspx
- Right click on the desktop of the virtual machine and select Screen Resolution
- Select Advanced Settings
- Click List All Modes
- Choose the screen resolution that you want and click OK
Hit Ben’s blog for screen shots
Posted in Hyper-V, Virtualization, Windows 2012 | Tagged: Hyper-V, Hyper-V 3.0, Microsoft, Virtualization | 2 Comments »