esSJae's Virtualization Blog

Virtualization and other IT topics

Posts Tagged ‘Microsoft’

VMGuest.iso for older Windows OSes in Win10/2016

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: , , , , | Leave a Comment »

Easy (lazy) way to get your serial number for your Dell, or other OEM system?

Posted by essjae on November 15, 2016

Need your serial number?  Laptop’s docked, or workstation not easily accessible?

Here’s an easy way to get your vendor serial number:

  1. Start a command prompt, click start, type “cmd”, hit enter
  2. type “wmic bios get serialnumber”

This will return your Dell, Lenovo, etc serial number.

Note: If you have a custom or home built system, you’re not likely to get an serial number, you’ll probably see something like  “system serial number” or “to be filled in by o.e.m”

wmic

Posted in Computers, Windows | Tagged: , , , , , , | 1 Comment »

Adding NAT to Hyper-V in Windows 10 and higher

Posted by essjae on March 10, 2016

I found about this new way to create a NAT virtual switch in Hyper-V, it’s a lot less work than my previously documented method here: https://smudj.wordpress.com/2015/05/14/windows-10-hyper-v-setting-up-networking-shared-and-bridged-options/

https://technet.microsoft.com/en-us/library/hh848455.aspx?f=255&MSPPError=-2147217396

New-VMSwitch

Creates a new virtual switch on one or more virtual machine hosts.

Syntax

Copy
Parameter Set: NetAdapterName
New-VMSwitch [-Name] <String> -NetAdapterName <String[]> [-AllowManagementOS <Boolean> ] [-CimSession <Microsoft.Management.Infrastructure.CimSession[]> ] [-ComputerName <String[]> ] [-Credential <System.Management.Automation.PSCredential[]> ] [-EnableEmbeddedTeaming <Nullable [System.Boolean]> ] [-EnableIov <Boolean]> ] [-EnablePacketDirect <Nullable [System.Boolean]> ] [-MinimumBandwidthMode <VMSwitchBandwidthMode> {Default | Weight | Absolute | None} ] [-NATSubnetAddress <System.String> ] [-Notes <String> ] [-Confirm] [-WhatIf] [ <CommonParameters>]

Parameter Set: NetAdapterInterfaceDescription
New-VMSwitch [-Name] <String> -NetAdapterInterfaceDescription <String[]> [-AllowManagementOS <Boolean> ] [-CimSession <Microsoft.Management.Infrastructure.CimSession[]> ] [-ComputerName <String[]> ] [-Credential <System.Management.Automation.PSCredential[]> ] [-EnableEmbeddedTeaming <Nullable [System.Boolean]> ] [-EnableIov <Boolean]> ] [-EnablePacketDirect <Nullable [System.Boolean]> ] [-MinimumBandwidthMode <VMSwitchBandwidthMode> {Default | Weight | Absolute | None} ] [-NATSubnetAddress <System.String> ] [-Notes <String> ] [-Confirm] [-WhatIf] [ <CommonParameters>]

Parameter Set: SwitchType
New-VMSwitch [-Name] <String> -SwitchType <VMSwitchType> {Private | Internal | External} [-CimSession <Microsoft.Management.Infrastructure.CimSession[]> ] [-ComputerName <String[]> ] [-Credential <System.Management.Automation.PSCredential[]> ] [-EnableEmbeddedTeaming <Nullable [System.Boolean]> ] [-EnableIov <Boolean]> ] [-EnablePacketDirect <Nullable [System.Boolean]> ] [-MinimumBandwidthMode <VMSwitchBandwidthMode> {Default | Weight | Absolute | None} ] [-NATSubnetAddress <System.String> ] [-Notes <String> ] [-Confirm] [-WhatIf] [ <CommonParameters>]

Example

New-VMSwitch -SwitchName "Virtual Switch" -SwitchType NAT -NATSubnetAddress "172.16.0.0/12"

Posted in Hyper-V, Uncategorized, Windows 10 | Tagged: , , , | 1 Comment »

Running Hyper-V Manager as a different user in Windows 10 (Runas)

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.

On Two:

I opened an administrator PowerShell window and ran

winrm quickconfig

and followed the wizard and was able to start the winrm service and open the firewall.

On One:

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:

%ProgramFiles%\Hyper-V\SnapInAbout.dll
...
*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.

 

**http://serverfault.com/questions/374342/run-active-directory-admin-center-as-another-user

Posted in Hyper-V, Uncategorized, Virtualization, Windows 10, Windows 2012 | Tagged: , , , , , , , | 1 Comment »

Restoring the Quick Launch Menu (and Windows Explorer) for Windows 7 and 10

Posted by essjae on January 10, 2016

(this is an updated repost of an article I have on my deprecated http://www.essjae.com website)

One thing I really had grown accustomed to is the Quick Launch menu and easily opening multiple Windows Explorer windows across my 2 and 3 monitor setups and seeing the Drives view.

Both of these have been noticeably missing since Win 7.

Step 1: Get back the Quick Launch menu

  • Right-click the Taskbar, select Toolbars–>New Toolbar.
  • In Folder text box copy and paste the following:     %userprofile%\AppData\Roaming\Microsoft\Internet Explorer\Quick Launch
  • Right-click the Taskbar, uncheck Lock the Taskbar, and right-click on the new Quick Launch toolbar. Uncheck Show Text and Show Title, click View–>Small Icons
  • Drag the toolbar divider all the way to the left of the taskbar to position it next to the Windows Orb, adjust the spacing on the taskbar as necessary
  • End result: quicklaunchicons  (minus the Explorer icon)
  • Step 2:
  • Add Windows Explorer in Win 7
    •  Click the Orb, then All Programs–>Accessories
    • Right-click to select and drag Windows Explorer () to the Quick Launch toolbar, then release
    • Select Copy Here from the pop-up menu
    • Right-click the Windows Explorer icon (), then click Properties
  • In Windows 10
    •  select and copy %SystemRoot%\
    • Click the Win icon or press the Win key and then paste %SystemRoot%\
    • Press Enter
    • Find explorer.exe, right-click and drag it to the Quick Launch bar
    • Right-click the Windows Explorer icon (), then click Properties
  • Add the following to the end of the command in Target:     /e,
  • The command should look like this:  %SystemRoot%\explorer.exe /e,

we-props

  • Click OK
  • Now, when you click on the Windows Explorer icon you’ll see this:
    • display

Posted in Win7, Windows, Windows 10 | Tagged: , , , , , | Leave a Comment »

Windows 10 Hyper-V: Installing Linux in Gen2 VMs

Posted by essjae on May 15, 2015

Important Notes:

Firmware:

Disable Secure Boot

settings-firmware

SCSI Controller:

Add a DVD drive for your ISO file

settings-scsi

Posted in Hyper-V, Virtualization, Windows 10 | Tagged: , , , , | Leave a Comment »

Windows 10 Hyper-V: Setting up Networking Shared and Bridged Options

Posted by essjae on May 14, 2015

Update:  It’s now a lot easier to create networks (using PowerShell) in Windows 10 Hyper-V:  https://smudj.wordpress.com/2016/03/10/adding-nat-to-hyper-v-in-windows-10-and-higher/

Update: Build 10586.3–Loopback adapter was missing, added back, and checked Hyper-V Extensible Virtual Switch.  This seems to happen with each build update.  A reboot may also be required.

This procedure shows you how to set up bridged and shared (NAT) networking with a single physical network card.

Standard Bridged Networking

  1. Start the Hyper-V Manager and click Virtual Switch Manager
  2. Select External and click Create Virtual Switch
  3. Enter Bridged or similar to identify this network as being on your physical network
  4. Select the correct network adapter under External network, this should be an active network card, i.e. one that is connected to your network and your host is using.
    1. If you only have one network card, verify that Allow management operating system to share this network adapter.
    2. If you have multiple network cards, and want to use this card exclusively for VMs, uncheck Allow management operating system to share this network adapter.
  5. Click OK and the new virtual switch will be created.
  6. Verify that you don’t have any ongoing network tasks before clicking yes, as your network connection will likely be disrupted when the virtual switch is created.
  7. This will create a network adapter under Network Connections called vEthernet (name_used), in this case, vEthernet (Bridged)

Shared Networking

Manually add a loopback adapter

  1. Open a cmd prompt with Administrator privileges.
    1. Type cmd, right-click on the search result and click Run as administrator
  2. Type hdwwiz and press enter
  3. add-new-hardware-wizard
  4. Click Next to start the wizard.
  5. Select Install the hardware that I manually select from a list (Advanced), and click
  6. Highlight Network Adapters, and click Next.
  7. Select Microsoft from the Manufacturer column and Microsoft KM-TEST Loopback Adapter from the Model column and click Next.
  8. ms-loopback
    1. Click Finish to complete the wizard.
    2. Open Network Connections (CTRL+X and select Network Connections), locate the newly created loopback adapter, right-click it and click Rename, and rename it from Ethernet 2 or Ethernet 3 to Loopback.

Create the Shared Virtual Network Switch in Hyper-V

  1. Open the Hyper-V Manager and click Virtual Switch Manager
  2. Select External and click Create Virtual Switch
  3. Enter a descriptive name, like Shared or NAT. This will create a network adapter under Network Connections called vEthernet (name_used), in this case, vEthernet (Shared)
  4. Select the Loopback adapter under the External Network selection box, click OK, then click Yes, this operation will not disrupt your host networking.

Connect the Loopback Adapter and Virtual Switch to the Network

  1. Open Network Connections (CTRL+X and select Network Connections)
  2. Click Change adapter settings
  3. Right-click and select Properties on the vEthernet (Bridged) network adapter created under Standard Bridged Networking.
  4. Click the Sharing
  5. Click Allow other network users to connect through this computer’s Internet connection.
  6. vEthernet(bridged)
  7. Select the Shared network connection, it should be listed as vEthernet (Shared), or whatever name was used in place of Bridged.
  8. Click Ok.

Note:  The Hyper-V networking is very fragile here, and you may need to reboot if you get errors when trying to connect and share the connections.

Here’s the completed Network Connections Window, note the Bridged and Shared Hyper-V adapters. Apologies for the pixelation, the Hyper-V Manager is not 4K screen friendly.

virtual_switches

Here’s two VMs using the Shared networking, note, the 192.168.137.x network, the default used by ICS.  Also shown is a third VM using the host network and the host’s IP.

IPconfigs-4

Posted in Computers, Hyper-V, Windows 10 | Tagged: , , , , | 2 Comments »

Windows Update fix for corruption errors like 0x80070002

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.

  1. 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.
  2. 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
  3. 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: , , , , , , , | Leave a Comment »

“Not enough memory” error message and Windows Phone 8 Emulator does not start in Windows 8.1

Posted by essjae on December 5, 2013

There is a recent KB that addresses some issues that have appeared every so often on the TechNet forums.  Since the WP8 emulator uses Hyper-V any related memory issues with running Hyper-V VMs on 8.1 should also be covered by this.

“Not enough memory” error message and Windows Phone 8 Emulator does not start in Windows 8.1

http://support.microsoft.com/kb/2911380

The Windows Phone 8 Emulator does not start on a computer that is running Windows 8.1 and that has fewer than 8 gigabytes (GB) of RAM if many programs are running at the same time. Additionally, you receive the following error message:
“The Windows Phone Emulator wasn’t able to ensure the virtual machine was running:

Something happened while starting a virtual machine: ‘Emulator Name’ could not initialize. (Virtual machine ID GUID)
Not enough memory in the system to start the virtual machine Emulator Name with ram size 1024 megabytes. (Virtual machine ID GUID)”

Additional troubleshooting can be found here:  https://smudj.wordpress.com/2013/02/22/troubleshooting-windows-8-and-hyper-vwindows-phone-8-emulator/

Posted in Hyper-V, Virtualization, Windows 8, Windows 8.1 | Tagged: , , , , , | 2 Comments »

Updated Surface Pro Wacom Driver

Posted by essjae on October 25, 2013

Just saw the Facebook posting of how great the Surface Pro 2’s pen is, and I thought that I must really have a really poor digitizer on my original Surface Pro.  I followed the link to the Wacom site and found a new driver.  Installed it and my pen is much more accurate now than it was.  There’s a new calibration process as well.  If your Surface Pro pen experience is lacking, give this a try!

http://us.Wacom.com/en/feeldriver

TABLET PC – Enhanced Tablet Driver 7.1.2

Expand the capabilities of your Windows 8 and Windows 8.1 tablet computer. Installing this driver will provide many advanced pressure-sensitive features that Wacom pen tablet users have come to enjoy. The driver supports advanced features such as pressure-sensitivity in graphics applications such as Adobe Photoshop and Corel Painter. It also allows you to adjust the pen tip pressure sensitivity and to program the side switch of the pen for a wide range of alternative settings and functions.

This driver should be installed on tablets that have Wacom feel IT technologies or Wacom Pen based technologies. This driver will also support older Penabled Tablet PCs running Windows 7, Windows Vista, and Windows XP Tablet Edition.

Driver installation

  1. Click on the Download link and save the file to your computer. If you are upgrading from a previous Wacom driver version, uninstall that driver first for best results. Restart the system prior to installing the new driver.
  2. Double-click on the downloaded file to launch the installer and follow the prompts.
  3. If prompted, restart the system by clicking the Ok button.

View the Driver Read Me information

>>Download Driver<<

Posted in Computers, Surface Pro, Windows 8 | Tagged: , , | Leave a Comment »