Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
appnotes:port_winnt_sanboot [2009/02/19 12:25] mcb30 Moved from :port_winnt_sanboot and added page title |
appnotes:port_winnt_sanboot [2009/12/22 15:26] (current) tronner |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Porting Windows XP to New Target Hardware via SAN-Booting ====== | + | ====== Porting Windows XP, Windows 7 and Windows 2008 to New Target Hardware via SAN-Booting ====== |
| ==== Introduction ==== | ==== Introduction ==== | ||
| Line 126: | Line 126: | ||
| Save the modified ''**.REG**'' with its ''**Driver**'' value deleted. Close your editor. | Save the modified ''**.REG**'' with its ''**Driver**'' value deleted. Close your editor. | ||
| + | ===Get a SYSTEM shell on Windows XP=== | ||
| Then run the following commands: | Then run the following commands: | ||
| C:\>time /t | C:\>time /t | ||
| Line 133: | Line 134: | ||
| but replace 16:55 with the 24-hour-format time for the very next minute according to the time. This will schedule a command-line interface to open up that will have SYSTEM account privileges. Please note that if you are using Remote Desktop to connect to computer model "A", you must use the ''**mstsc.exe /console**'' command-line for Remote Desktop, as the ''**cmd**'' window will only display that way. | but replace 16:55 with the 24-hour-format time for the very next minute according to the time. This will schedule a command-line interface to open up that will have SYSTEM account privileges. Please note that if you are using Remote Desktop to connect to computer model "A", you must use the ''**mstsc.exe /console**'' command-line for Remote Desktop, as the ''**cmd**'' window will only display that way. | ||
| - | A CLI will open with ''**svchost**'' in the title. Close any running RegEdit (should you have one) and then run the following command from the ''**svchost**'' CLI: | + | A CLI will open with ''**svchost**'' in the title. |
| + | |||
| + | ===Get a SYSTEM shell on Windows 7 and 2008=== | ||
| + | From: http://blogs.technet.com/askds/archive/2008/10/22/getting-a-cmd-prompt-as-system-in-windows-vista-and-windows-server-2008.aspx | ||
| + | - Download [[http://technet.microsoft.com/en-us/sysinternals/bb897553.aspx|PSEXEC]] and unzip it to some folder | ||
| + | - Open a command prompt as Administrator (click Start, type CMD in the search field and press Ctrl-Shift-Enter) | ||
| + | - navigate to the folder where you just unpacked PSEXEC | ||
| + | - run | ||
| + | |||
| + | psexec -i -s -d cmd | ||
| + | |||
| + | - check whether you really are the SYSTEM user | ||
| + | |||
| + | whoami /user | ||
| + | |||
| + | |||
| + | ===Import REG file=== | ||
| + | Close any running RegEdit (should you have one) and then run the following command from the ''**svchost**'' CLI: | ||
| C:\Windows\System32>regedit | C:\Windows\System32>regedit | ||
| RegEdit will start with the same SYSTEM account privileges. Import the ''**.REG**'' file from wherever it is. Since you are running as the SYSTEM account, don't expect your Desktop or My Documents directories to be the same as your regular account. Close RegEdit. Close the ''**svchost**'' CLI window. | RegEdit will start with the same SYSTEM account privileges. Import the ''**.REG**'' file from wherever it is. Since you are running as the SYSTEM account, don't expect your Desktop or My Documents directories to be the same as your regular account. Close RegEdit. Close the ''**svchost**'' CLI window. | ||
| Line 147: | Line 165: | ||
| C:\>devmgmt.msc | C:\>devmgmt.msc | ||
| Choose **View** -> **Show hidden devices**. Expand the Network Adapters section and search for the target NIC from computer model "B". It should appear with a //faint// icon, because that device is obviously not currently attached to computer model "A". Now choose **Action** -> **Update Driver...** and go through the installation process for the NIC, choosing the correct driver. Windows will automatically install the partner Packet Scheduler Miniport for the NIC. | Choose **View** -> **Show hidden devices**. Expand the Network Adapters section and search for the target NIC from computer model "B". It should appear with a //faint// icon, because that device is obviously not currently attached to computer model "A". Now choose **Action** -> **Update Driver...** and go through the installation process for the NIC, choosing the correct driver. Windows will automatically install the partner Packet Scheduler Miniport for the NIC. | ||
| + | |||
| + | If the NIC in computer model "B" is a variation (older or newer version with different PCI ID) of the one in computer model "A" Windows won't show an additional device in the device manager. In this case you'll have to tell Windows it can use the same driver. To do this find the registry key belonging to the NIC in model "B", double click on the "Driver" value and copy it. Then go to the key for the NIC in computer model "A" and create a new string value called "Driver" with this value. | ||
| + | |||
| ==== Conclusion ==== | ==== Conclusion ==== | ||
