BOSWELL’S Q&A: Ghost in the Machine<\/p>\n
Bill: I’m trying to deploy desktop images in my small
\ncompany. I’m using Sysprep on the source desktop prior to imaging
\nwith Ghost. When I apply the image to another desktop from a
\ndifferent manufacturer, I get a blue screen of death.
\n<\/p>\n
BOSWELL’S Q&A: Ghost in the Machine<\/p>\n
Bill: I’m trying to deploy desktop images in my small
\ncompany. I’m using Sysprep on the source desktop prior to imaging
\nwith Ghost. When I apply the image to another desktop from a
\ndifferent manufacturer, I get a blue screen of death. These are
\nstandard PC desktops without any special peripherals. What gives?
\n–Ed<\/p>\n
Ed: Ed: I’m betting that your bugcheck (Blue Screen of Death)
\nproblem is a result of a difference in the IDE interface used
\nby the different machines in your organization.<\/p>\n
When you run Sysprep on one platform and deploy the image to
\nanother platform, you would ordinarily expect Plug-and-Play to
\nhandle any hardware differences (assuming that the machines use
\nthe same version of Ntoskrnl.exe and Hal.dll). However, mass
\nstorage drivers represent a special case. The boot loader needs
\nto load the mass storage devices prior to initializing the
\noperating system, so there’s no opportunity to let the
\nPlug-and-Play Manager shuffle around drivers. For this reason,
\nit’s fairly common to get a 0x0000007b bugcheck following the
\ndeployment of a Sysprep image to a machine from a different
\nvendor, or different models from the same vendor, even though
\nyou’re using what appears to be a vanilla IDE controller in
\nboth cases.<\/p>\n
One way to avoid this problem is to include all the mass
\nstorage drivers in the Sysprep image, not just the drivers
\nused by the source machine. The version of Sysprep.exe that
\ncomes with Windows Server 2003 has a special switch for doing
\njust this. It’s called -bmsd. Here’s how it works.<\/p>\n
On the source desktop, create a folder called Sysprep at the
\nroot of the C drive (C:\\Sysprep). Put a copy of the Windows
\nServer 2003 version of Sysprep.exe and Setupcl.exe in this
\nfolder. Extract them from the Deploy.cab file on the Setup CD.
\nYou’ll find Deploy.com under \\Support\\Tools.<\/p>\n
Put your Sysprep.inf file in the same C:\\Sysprep folder. You
\nprobably prepared this file using Setup Manager.<\/p>\n
Edit the Sysprep.inf file with Notepad. Add these entries to
\nthe bottom of the file: <\/p>\n
[Sysprep]
\n BuildMassStorageSection=yes <\/p>\n
[SysprepMassStorage] <\/p>\n
Sysprep.exe uses these entries to provision the file with
\nthe mass storage drivers.<\/p>\n
Now, open a command prompt and navigate to C:\\Sysprep.<\/p>\n
Run sysprep -bmsd. You’ll see a pop-up window with a large
\nhourglass open for a few seconds, then close. There will be
\nno other graphical indication that the process has succeeded.<\/p>\n
Open the Sysprep.inf file and look under the
\n[SysprepMassStorage] section. You’ll see dozens and dozens
\nof entries.<\/p>\n
Now run Sysprep -quiet -reseal -reboot. This will take
\nquite a bit longer because Sysprep has to collect the
\nspecified mass storage drivers.<\/p>\n
When you apply this image to the other desktops, the
\ndeployment should go smoothly with no bugchecks.<\/p>\n
Hope this helps!
\n–Bill Boswell<\/p>\n","protected":false},"excerpt":{"rendered":"
BOSWELL’S Q&A: Ghost in the Machine Bill: I’m trying to deploy desktop images in my small company. I’m using Sysprep on the source desktop prior to imaging with Ghost. When I apply the image to another desktop from a different … Read More »<\/a><\/p>\n","protected":false},"author":4,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-148","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"http:\/\/www.wildow.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/148","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/www.wildow.com\/blog\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.wildow.com\/blog\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.wildow.com\/blog\/index.php?rest_route=\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"http:\/\/www.wildow.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=148"}],"version-history":[{"count":0,"href":"http:\/\/www.wildow.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/148\/revisions"}],"wp:attachment":[{"href":"http:\/\/www.wildow.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=148"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.wildow.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=148"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.wildow.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=148"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}