Windows cannot access the specified device

Michael — Mon, 27 Sep 2010 15:23:57 +0000

This is an old problem, but I still see it from time to time. You are trying to run and executable that you downloaded, and you are on a Windows 2003 system. You double click and get:

As you can see here, I am simply trying to install the windirstat utility to figure out what is taking up all the disk space. If you have drive space issues, and we seem to always have drive space issues, this is a great utility.

The problem is this:

Notice the Security section at the bottom. if you click on Unblock, then it looks like this:

Apply the change and the security section at the bottom goes away, and you can then run the program.

SCVMM and P2V Adventures

Michael — Thu, 17 Jun 2010 19:11:08 +0000

Where I work, we have been using Microsoft Virtualization since Virtual Server was in Beta. Of course, we don’t necessarily use all of the functions and features of all the software we have, but one feature that I have used a good bit is the “Convert physical server” action in System Center Virtual Machine Manager. Until recently, I have used this with great success. We run IBM xSeries servers and I have converted something like 50 of them to virtual machines running on Hyper-V over the past several years.

In late 2007, we bought our first IBM Blade Center (which I am very happy with) and with that move we also decided to do “boot from SAN” for all of our blades. Just seemed to make sense that we wouldn’t put moving parts in a device that was designed to run so well without moving parts.

At the time, we were implementing a new ERP system and several “hanger on” type applications, and Hyper-V (virtualization in general) wasn’t something that was supported by a lot of the software we were deploying. So we have a lot of powerful blade servers, running a lot of low use applications. I have managed to eradicate several of those wasteful installations, but there are a set that I am only now getting buy-in to virtualize.

And today’s adventure begins with a Windows Server 2003 SP2 machine installed Boot from SAN on an IBM HS21-XM Blade server.

First attempt:

1. Convert physical server

2. Virtual machine name

3. Scan System

Looks good..

4. Conversion options

we can try the defaults..

5. Specify the processor and memory…

6. Select the host, path, network, start options, etc..

7. The job starts, the machine gets copied over, and …

That try resulted in a blue screen loop..

Ok… time to try the Offline conversion:

1. Proceed as above but select the Offline conversion option at step 4.

2. hmm.. conversion warnings… must correct to proceed..

Warning (13246)
No compatible drivers were identified for the device: Broadcom BCM5708S NetXtreme II GigE (NDIS VBD Client). The offline physical-to-virtual conversion requires a driver for this device.

Device Type: network adapter
Device Description: Broadcom BCM5708S NetXtreme II GigE (NDIS VBD Client)
Device Manufacturer: Broadcom Corporation
Hardware IDs (listed in order of preference):
B06BDRV\L2ND&PCI_16AC14E4&SUBSYS_03271014&REV_12

Compatible IDs (listed in order of preference):
B06BDRV\L2ND&PCI_16AC14E4&SUBSYS_03271014
B06BDRV\L2ND&PCI_16AC14E4
B06BDRV\L2ND

Recommended Action
Create a new folder under C:\Program Files\Microsoft System Center Virtual Machine Manager 2008 R2\Driver Import on the Virtual Machine Manager server and then copy the necessary 32-bit Windows Vista driver package files for this device to the new folder. The driver package files include the driver (.sys) and installation (.inf and .cat) files. Check the device manufacturer’s website for the necessary drivers.

We don’t really need to do that right…

Had some trouble with that part… finally figured out that the drivers that need to be placed in that folder are the “RIS” drivers.

Try number 3 (or 30, I lost count)…

1. Proceed as try number 2, ignore warning because we did put the driver in there, and

Blue screen loop…

Hmm… maybe this is just not meant to be. Did some more searching and found this article:

http://blogs.msdn.com/b/robertvi/archive/2009/10/07/after-installing-hyper-v-integration-services-on-the-next-reboot-the-vm-displays-bsod-0x0000007b.aspx

Basically, there are some people seeing the exact same blue screen that I was seeing, except this was after the install of updated integration components. But I wasn’t installing integration components yet… or was I?

Ok so maybe it was getting that far and just “blowing up” after the install of the components. Good thing about this being a P2V, I can go back to the source machine pretty easy and check the registry:

Looks like we may have an answer here. Change the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Wdf01000\Group entry to be WdfLoadGroup instead of base.

It is my guess, that this would have worked even with the online conversion option.

Preinstall DPM Client

Michael — Wed, 25 Mar 2009 19:11:12 +0000

If you deploy servers from an image, and you would like to install DPM prior to imaging, you can’t just use the install option from the DPM server. You CAN install the agent manually, and then configure it later.

Copy the latest agent files from C:\Program Files\Microsoft DPM\DPM\Agents\RA and put them somewhere you can get to them.
Run the DPMAgentInstaller from the appropriate directory, amd64\1033 or i386\1033 depending on if you have a x64 or x86 system.
On the Production server (the machine you want to protect) run %PROGRAMFILES%Microsoft data protection manager\dpm\bin\setdpmserver -dpmservername
On the DPM server, open the DPM Management Shell (the PowerShell interface for DPM) and run attach-productionserver.ps1. This will ask you for the DPMServer, PSName (the production machine that you want to protect), UserName (an administrator on the client machine), Password, and Domain.
Refresh the view in the DPM administrator console.

You should see your production servers listed in the Managemt\Agents view.

Michael Phillips Blog » How to

Windows cannot access the specified device

SCVMM and P2V Adventures

Preinstall DPM Client