This post may be for my benefit only, but I needed to use keyboard shortcuts to remove software and drivers in order for Hyper-V Virtual Guest Services to install successfully on a server that was P2Ved using SCVMM. Figure it may happen again...
The following keyboard shortcuts, taken from MS KB126449, provided the greatest benefits:
General keyboard-only commands
* F1: Starts Windows Help
* F10: Activates menu bar options
* SHIFT+F10: Opens a shortcut menu for the selected item (this is the same as right-clicking an object
* CTRL+ESC: Opens the Start menu (use the ARROW keys to select an item)
* CTRL+ESC or ESC: Selects the Start button (press TAB to select the taskbar, or press SHIFT+F10 for a context menu)
* CTRL+SHIFT+ESC: Opens Windows Task Manager
* ALT+DOWN ARROW: Opens a drop-down list box
* ALT+TAB: Switch to another running program (hold down the ALT key and then press the TAB key to view the task-switching window)
* SHIFT: Press and hold down the SHIFT key while you insert a CD-ROM to bypass the automatic-run feature
* ALT+SPACE: Displays the main window's System menu (from the System menu, you can restore, move, resize, minimize, maximize, or close the window)
* ALT+- (ALT+hyphen): Displays the Multiple Document Interface (MDI) child window's System menu (from the MDI child window's System menu, you can restore, move, resize, minimize, maximize, or close the child window)
* CTRL+TAB: Switch to the next child window of a Multiple Document Interface (MDI) program
* ALT+underlined letter in menu: Opens the menu
* ALT+F4: Closes the current window
* CTRL+F4: Closes the current Multiple Document Interface (MDI) window
* ALT+F6: Switch between multiple windows in the same program (for example, when the Notepad Find dialog box is displayed, ALT+F6 switches between the Find dialog box and the main Notepad window)
Wednesday, July 29, 2009
Migrate IAS from Windows 2003 to Windows 2008
I recently had to migrate IAS running on a Windows Server 2003 to 2008 and was fortunate enough to run across this post: http://blogs.technet.com/nap/archive/2009/01/15/tool-for-migrating-ias-configuration-settings-to-nps-is-now-available.aspx
In a nutshell, using netsh aaa show config to export the IAS settings from 2003 does not put it into the proper import format for Server 2008, thus the import will fail. The link above leads you to Microsoft Hotfix 955995 providing you with the utility IASMigReader.exe which is used to create a properly formatted IAS import file for Server 2008.
Basic steps are to:
1. Install the Network Policy Server Role on the 2008 Server
2. Install the 955995 Hotfix on the 2008 Server and reboot
3. Copy the IASMigReader.exe file from the 2008 to the 2003 Server
4. On the 2003 server, open a command prompt and execute IASMigReader
5. Copy the resulting ias.txt file from the 2003 to the 2008 Server
6. From the 2008 NPS, open a command prompt and execute netsh nps import path\ias.txt
7. Launch the Network Policy Server MMC and verify the settings have been imported and test the new configuration
In a nutshell, using netsh aaa show config to export the IAS settings from 2003 does not put it into the proper import format for Server 2008, thus the import will fail. The link above leads you to Microsoft Hotfix 955995 providing you with the utility IASMigReader.exe which is used to create a properly formatted IAS import file for Server 2008.
Basic steps are to:
1. Install the Network Policy Server Role on the 2008 Server
2. Install the 955995 Hotfix on the 2008 Server and reboot
3. Copy the IASMigReader.exe file from the 2008 to the 2003 Server
4. On the 2003 server, open a command prompt and execute IASMigReader
5. Copy the resulting ias.txt file from the 2003 to the 2008 Server
6. From the 2008 NPS, open a command prompt and execute netsh nps import path\ias.txt
7. Launch the Network Policy Server MMC and verify the settings have been imported and test the new configuration
Thursday, July 16, 2009
UPDATE: managementObject error when enabling HA for Hyper-V VM
Just an update to the previous post:
I installed the KB951308 hotfix onto another server and this time a reboot was required. Go figure....
I installed the KB951308 hotfix onto another server and this time a reboot was required. Go figure....
Tuesday, July 14, 2009
managementObject error when enabling HA for Hyper-V VM
To start a Hyper-V project, I installed an virtual SCVMM server to local storage until I could get the SAN configured. After doing so, I shutdown the SCVMM server and copied it to an iSCSI LUN. When trying to use the Failover Cluster Management MMC on another server to make it "highly available", I received the following managementObject error:
Turns out, all I had to do was install the following hotfix on the server from which I was running the Failover Cluster Management MMC. Once it was installed, I was able to run the HA Wizard and add the SCVMM server to the failover cluster.
This hotfix did not require a reboot.
Turns out, all I had to do was install the following hotfix on the server from which I was running the Failover Cluster Management MMC. Once it was installed, I was able to run the HA Wizard and add the SCVMM server to the failover cluster.
This hotfix did not require a reboot.
Thursday, July 9, 2009
P2V to Hyper-V - Winload.exe Error
After P2Ving a 2008 Server to Hyper-V, I received the following Winload.exe error (shown below) upon boot. It is Winload.exe's job to load the OS Kernel...
To resolve, I used the steps found here, but since I love screenshots, I thought I'd share them so you can see the process/commands.
1. Boot the VM from the Server 2008 DVD and on the Install Now screen, select Repair your computer
2. On the Systems Recovery Options window, highlight the OS install to repair and then select Next.
3. When prompted to choose a recovery tool, select the Command Prompt.
4. Enter the commands below and reboot the server:
c:
cd windows\system32
bcdedit /set {bootmgr} device boot
bcdedit /set {default} device boot
bcdedit /set {default} osdevice boot
To resolve, I used the steps found here, but since I love screenshots, I thought I'd share them so you can see the process/commands.
1. Boot the VM from the Server 2008 DVD and on the Install Now screen, select Repair your computer
2. On the Systems Recovery Options window, highlight the OS install to repair and then select Next.
3. When prompted to choose a recovery tool, select the Command Prompt.
4. Enter the commands below and reboot the server:
c:
cd windows\system32
bcdedit /set {bootmgr} device boot
bcdedit /set {default} device boot
bcdedit /set {default} osdevice boot
Friday, July 3, 2009
Part 2 - Creating a Windows Server 2008 R2 Hyper-V Failover Cluster: Configuring iSCSI Connectivity
In this post, we'll configure the iSCSI connectivity to the back-end storage on the EMC SAN. I'm sure there are several, and potentially better, methods to configure iSCSI on Server Core 2008 R2, but these are the steps I took and I have not had any problems with back-end storage connectivity. If the process can be improved, please let me know.
Here is the link to the previous post:
Part 1 - Creating a Windows Server 2008 R2 Hyper-V Failover Cluster: Install Hyper-V and Failover Clustering
Configuring connectivity to iSCSI LUNs on Server 2008 R2:
1. Login to the server and configure an IP Address on the NIC attached to the iSCSI network and ping the iSCSI target.
2. Execute the command iscsicpl.exe. When prompted to start the iSCSI Service, click Yes.
3. When the iSCSI Initiator Properties window appears, click the Target tab, and within the Quick Connect section, enter the IP address of this iSCSI target and click Quick Connect.
4. On the Quick Connect window, the discovered iSCSI target will be displayed, click Done.
5. When returned to the iSCSI Initiator Properties window, click the Discovery tab. Ensure all iSCSI targets are listed.
6. Click the Volumes and Devices tab and then click Auto Configure. Any iSCSI LUNs to which the Hyper-V hosts have access should be displayed.
Next, we need to use diskpart to bring the disks online and create partitions. On the back-end storage, I created two 300GB LUNs for my Cluster Shared Volumes.
7. At the command prompt,execute the command diskpart and then list disks.
8. To bring a disk online, enter the commands:
select disk <disk number>
online disk
Repeat for each disk
9. To ensure the disks are not in a "read-only" state, execute the command attributes disk clear readonly. Enter the following commands to create and format an NTFS partition:
create partition primary align=64
format fs=ntfs quick
10. Verify the disks can be accessed by the remaining Hyper-V hosts.
Here is the link to the previous post:
Part 1 - Creating a Windows Server 2008 R2 Hyper-V Failover Cluster: Install Hyper-V and Failover Clustering
Configuring connectivity to iSCSI LUNs on Server 2008 R2:
1. Login to the server and configure an IP Address on the NIC attached to the iSCSI network and ping the iSCSI target.
2. Execute the command iscsicpl.exe. When prompted to start the iSCSI Service, click Yes.
3. When the iSCSI Initiator Properties window appears, click the Target tab, and within the Quick Connect section, enter the IP address of this iSCSI target and click Quick Connect.
4. On the Quick Connect window, the discovered iSCSI target will be displayed, click Done.
5. When returned to the iSCSI Initiator Properties window, click the Discovery tab. Ensure all iSCSI targets are listed.
6. Click the Volumes and Devices tab and then click Auto Configure. Any iSCSI LUNs to which the Hyper-V hosts have access should be displayed.
Next, we need to use diskpart to bring the disks online and create partitions. On the back-end storage, I created two 300GB LUNs for my Cluster Shared Volumes.
7. At the command prompt,execute the command diskpart and then list disks.
8. To bring a disk online, enter the commands:
select disk <disk number>
online disk
Repeat for each disk
9. To ensure the disks are not in a "read-only" state, execute the command attributes disk clear readonly. Enter the following commands to create and format an NTFS partition:
create partition primary align=64
format fs=ntfs quick
10. Verify the disks can be accessed by the remaining Hyper-V hosts.
Subscribe to:
Posts (Atom)