• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1569
  • Last Modified:

Windows 7 MDT 2013 issue

Hi Experts!

I have an issue with MDT 2013 and Windows 7 but let me first explain how our environment is setup.

We have MDT 2013 installed in our environment and we are currently in the early stages of deployment, the work done so far inside MDT is:

1. Windows 7 x64 Base image imported with basic apps like MS office etc etc
2. Unattend.xml imported
3. Task sequence created
4. Out of box drivers and folder structure created with drivers imported in an .inf format.
5. Applications imported into MDT with correct install commands.

THE ISSUE:

Now what happens is when we image our Lenovo x240 MDT will deploy the base image and then add the drivers for the x240 and then add the applications relevant to the laptop which are the VPN client and dock driver,

Whats happening is after MDT has imaged the laptop at the first part where it states Starting Windows it BSOD's and then reboots, I have then booted to WinPE and copied the .log logs from C:\windows\inf and then opened this on my machine and nothing in there suggests what could be causing it to BSOD. There also isnt a Memory.dmp present in C:\Windows or C:\Windows\Mini Dump

When the BSOD happens it states its something to do with intelpcc.sys

I need help to determine what is causing the BSOD :( i'm very new to MDT so go easy on me :(
0
Rizzle
Asked:
Rizzle
  • 4
  • 2
  • 2
  • +1
1 Solution
 
Adam LeinssSenior Desktop EngineerCommented:
It's best to break out the drivers using Johan's variable method so that each model only looks at a subset of drivers and not the whole database:

http://www.deploymentresearch.com/Research/tabid/62/EntryId/112/MDT-2013-Lite-Touch-Driver-Management.aspx

You should be able to tap the F8 key and pick "Disable automatic failure on restart".  That should give you the BSOD error message, but I'm guessing it's picking the wrong driver.  That is why using the "total chaos" mode is dangerous.
0
 
Don S.Commented:
It is likely a driver issue.  If you can't find/fix the offending driver(s), then the easiest way to resolve it is simple create a new OS image from a new Lenovo with the OS that was preinstalled on it.  You know that should work.  If it does, then compare what drivers it uses and make sure that is what you have injected into the generic image - or just use the working OEM image.
0
 
David Johnson, CD, MVPOwnerCommented:
another key item is to ALWAYS create your master image in a virtual machine NEVER a physical machine
0
Cloud Class® Course: CompTIA Cloud+

The CompTIA Cloud+ Basic training course will teach you about cloud concepts and models, data storage, networking, and network infrastructure.

 
RizzleAuthor Commented:
Hi all

@adam - The drivers are split out by their hardware model which is detailed in "Total Control" I then believe in the customsettings.ini and its set to inject drivers using

[Windows7 Base image]
DriverInjectionMode=ALL
DriverSelectionProfile=Nothing
DriverGroup001=Windows 7 x64\%Make%\%Model%
_SMSTSOrgName=Deploying Orbit %Model%
0
 
Adam LeinssSenior Desktop EngineerCommented:
That is perfect then.  This is what I would do:

1. Boot to WinRE and do a "dir intelpcc.sys /s /a" and rename any files it finds
2. Restart into Windows and see if it boots
3. If it boots, go back to MDT and try to locate intelpcc.sys in the driver store and either update or remove it and re-image the laptop.
4. If it doesn't boot, try taking all the drivers out of the driver database and just add the critical boot drivers and then image it.  It will be missing drivers, but if you can get it to boot, start adding them back one by one until you hit a snag.
0
 
David Johnson, CD, MVPOwnerCommented:
creating your base image using a virtual machine will remove this problem and it is the best practice for creating a deployment. Using a physical machine and you are introducing hardware dependencies.. You should be able to use your base image on ANY hardware.
0
 
RizzleAuthor Commented:
Hi David,

The base image was created on a vm.

Still looking for the culprit drivers/apps at this point.
0
 
RizzleAuthor Commented:
Issue was our VPN Client. issue resolved by removing it from the deployed apps and then replacing with a Windows 7 and Windows 8 compatible version.
0
 
RizzleAuthor Commented:
VPN Client at fault.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: Microsoft Azure 2017

Azure has a changed a lot since it was originally introduce by adding new services and features. Do you know everything you need to about Azure? This course will teach you about the Azure App Service, monitoring and application insights, DevOps, and Team Services.

  • 4
  • 2
  • 2
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now