Remove hidden NIC from device manager of Windows Server 2008.

Recently, I setup VM in Hyper-Vof Windows Server 2008 R2 for classroom training use.
I created a base hard disk image and a lot of differencing disks for difference VMs.
However, I discover sometimes, when the differencing VM turn on, It will create another  NIC to use and hide the previous NIC.
(Maybe it detect the new setup VM as difference hardware)

Thus, the NIC name will be changed to “xxxxxxxx #2″.
So, I decided to remove the hidden NIC so that the NIC will not be named to “xxxxxxxxx #2″ or “xxxxxxxx #3″…etc.


The following is the steps required before moving the VM:


  1. Click Start, click Run, type cmd.exe, and then press ENTER.
  2. Type set devmgr_show_nonpresent_devices=1, and then press ENTER.
  3. Type Start DEVMGMT.MSC, and then press ENTER.
  4. Click View, and then click Show Hidden Devices.
  5. Expand the Network Adapters tree.
  6. Right-click the dimmed network adapter, and then click Uninstall.

Free Microsoft iSCSI Target

The iSCSI Target solution from MS is now free! We can use it to setup a environment to test fail-over clustering!
http://www.microsoft.com/download/en/details.aspx?id=19867

Here are more information about this:
http://blogs.technet.com/b/josebda/archive/2011/04/04/microsoft-iscsi-software-target-3-3-for-windows-server-2008-r2-available-for-public-download.aspx


More info:


The Microsoft iSCSI Software Target has been available for production use as part of Windows Storage Server since early 2007. It has also been available for development and test use by MSDN and TechNet subscribers starting in May 2009. However, until now, there was no way to use the Microsoft iSCSI Software Target in production on a regular server running Windows Server 2008 R2. This new download offers exactly that.

Now available as a public download, the software is essentially the same software that ships with Windows Storage Server 2008 R2. Windows Storage Server 2008 R2 and the public download package will be refreshed (kept in sync) with any software fixes and updates. Those updates are described at http://technet.microsoft.com/en-us/library/gg232597.aspx.

This release was preceded by intense testing by the Microsoft iSCSI Target team, especially in scenarios where the iSCSI Target is used with Hyper-V and with Windows Server Failover Clusters. We do imagine these to be amongst the most commons deployment scenarios.

Testing included running the Microsoft iSCSI Software Target in a two-node Failover Cluster and configuring 92 individual Hyper-V VMs, each running a data intensive application and storing data on a single node of that iSCSI Target cluster. The exciting part of the test was to force an unplanned failure of the iSCSI Target node being used by all the VMs and verify that we had a successful failover to the other node with all 92 VMs continuing to run the application without any interruption.

 

Multiple partitions hard drive for imaging

There is no straight way to capture the whole disk, including C:, D:, E:,etc., to an image file in one time, and you cannot deploy an image including multiple partitions in one time.

However, you can try the following steps and see if can work for you:

Step 1.
======
Sysprep your machine and then reboot into Windows PE. Capture the offline Sysprep image into .wim format and then upload the image to the WDS server. Or you can do this by a Capture Image.


Step 2.
======
Create a unattend answer file to automatically create and configure new volumes when you deploy the image onto computers.


For more details about this, please refer to the “Unattended Windows Setup Reference” help document included in the Windows AIK.


Step 3.
======
On the WDS server, in the folder “RemoteInstall\Images\<ImageGroupName>”, create a new folder with the same name as your install image. In the new created folder, create a folder named “$OEM$” (without the quotation marks). Then, in the $OEM$ folder, create subfolders with the name of drive letter.


The whole path should look like:


RemoteInstall

Images

< ImageGroupName>

< ImageName>

$OEM$

D

E

F

Put all the files into the appropriate folder, such as put files in the volume D: into folder “$OEM$\D”.