[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
?
Solved

VMware Guest Server 2008 BSOD STOP Error with MDT Deployment

Posted on 2009-02-24
9
Medium Priority
?
1,233 Views
Last Modified: 2013-12-12
Hi,
I am having a problem with my LiteTouch Deployment using MDT when Deploying Server 2008.  My install works fine on Physical hardware workstation but when deploying in VMware via litetouch ISO the deployment fails after installing the OS.  as soon as it starts to boot up after the apply it BSOD with a STOP Error.  If i deploy from  Server 2008 original DVD media i do not have this problem>?  I am thinking this is a Mass Storage Driver issue with the SCSI Driver but why would it work from original media and not my build?

Any help would be much appreciated as i am lost right now...
0
Comment
Question by:balinton
  • 4
  • 4
9 Comments
 
LVL 15

Assisted Solution

by:HayesJupe
HayesJupe earned 80 total points
ID: 23729790
ran into this yesterday, there is a bug with vmware esx 3.5 drivers for 2008..
take the drivers out of your drivers area (or at least off the DP) - rebuild, it will be fine
then wait for vmware to fix!
0
 

Author Comment

by:balinton
ID: 23730026
Hmm... What do I use for winpe? Or shouldvi just manually  inject into the wim?
0
 
LVL 15

Expert Comment

by:HayesJupe
ID: 23732343
if you remove the drivers from the DP, they will still be injected into PE (based on the PE options associated with the DP)
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

 

Author Comment

by:balinton
ID: 23733386
Yes i realize this... If they are not in the DP then WInPE wont recognize the HDD since its SCSI.  So i need to have those in the wim to format the drive and apply the image but if i leave them in the DP then they also get injected into the build during deployment so how would i stop this and only apply them to the PE Disk?  SHould i just manually inject them into the Litetouch ISO after the build completes?
0
 
LVL 15

Expert Comment

by:HayesJupe
ID: 23738614
ummm ok.
So go into the properties of your DP.
Go into the drivers tab, untick all the driver catagories
In the the WinPE tab, the option to inject mass-storage and network drivers will still be ticked (if it was before)
When PE is compiled, the drivers will still be injected, ut when the build occurs the DP will not have drivers to be installed available as part of the build.
i dont know how much simplier i can say it.
0
 

Accepted Solution

by:
balinton earned 0 total points
ID: 23744456
ok that will not fix the problem... It will get WinPE to boot but the corrupt driver from VMware will still cause a BSOD.  The workaround for now is to find and old WIndows 2000 Disc and copy the Symmpi.inf driver from the cd and add it to OOBD.  It will boot WInPE recognize the drives and apply the image and reboot without a BSOD.  I am going to try and submit a case to VMware to try and get this fixed.

Thanks,
Brandon
0
 
LVL 15

Expert Comment

by:HayesJupe
ID: 23749201
ok, it does fix the problem.. but good luck with that.
0
 

Author Comment

by:balinton
ID: 23749628
Look dude if it worked i wouldnt of kept looking for a solution...  i posted the solution to my problem for others to view so they dont have to go through the same problems i faced.  Maybe you should just be reviewing questions instead of answering them k... Great!!!
0
 

Expert Comment

by:chdtech
ID: 23979240
Change your SCSI adapter in Virtual Center to LSI & boot off the LSI.  After MDT lays down the image, change the adapter back to Bus Logic.  I'm trying to figure out how to get the bus logic drivers injected into the LiteTouch.ISO
0

Featured Post

VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Steps to fix “Unable to mount database. (hr=0x80004005, ec=1108)”.
MSSQL DB-maintenance also needs implementation of multiple activities. However, unprecedented errors can hamper the database management. In that case, deploying Stellar SQL Database Toolkit ensures fast and accurate database and backup repair as wel…
The viewer will learn how to successfully download and install the SARDU utility on Windows 8, without downloading adware.
Monitoring a network: why having a policy is the best policy? Michael Kulchisky, MCSE, MCSA, MCP, VTSP, VSP, CCSP outlines the enormous benefits of having a policy-based approach when monitoring medium and large networks. Software utilized in this v…
Suggested Courses

834 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question