Couple more questions > Deployment Forum Community Forums

Friday, January 09, 2009

Library

Resources

Community

About

Community » Forums

Member Login

StandardLiveID

User Name:

Password:

Remember Login

Forgot Password ?


Guests can view and read messages in the community forums, but you must register and log in to Deployment Forum before you can post messages. Click Register at the top of this page. Before posting messages, please read the forum guidelines at the bottom of this page.

Unanswered Active Topics

Forums Search

Forums > Deployment Solutions > MDT 2008

Subject: Couple more questions

Prev Next

You are not authorized to post a reply.

Author

Messages

Paul M. Hibbert User is Offline

Posts:27

07/24/2008 9:08 AM
If I do not have a driver respository defined on the MDT server will that pooch any capturing/deploying Xp images? Does the driver repository need to be on the %SYSTEMROOT%\Drivers or in the $OEM$ folder with individual drivers folders broken down by specific hardware? Is there a way to edit the sysprep.inf file to accommodate different processor types? From research that I have done most people recommend that I change the computer driver in system manger to acpi pc.

mla1

Posts:50

08/15/2008 10:34 AM
If you are performing your capture on a multiprocessor add the following line to your sysprep.inf. [Unattended] UpdateUPHAL = "ACPIAPIC_UP,%WINDIR%\Inf\Hal.inf" this will then deploy to a uniprocessor and multiprocessor. IF your capturing your image on a uniprocessor machine add the following line. UpdateHAL = "ACPIAPIC_MP,%WINDIR%\Inf\Hal.inf" Did I answer you question or were you referrring to amd processors, what different hardware are you deploying to processors are you using amd ?

JCadavid

Posts:64

08/15/2008 3:25 PM
Paul, I think this will help. Q1 - While it might not pooch the build, you will need to figure out how to get the drivers in there one way or another. Your best bet would be to build a driver repository with your newest first and then build backwards to your oldest model. That way you are running the latest drivers for all of your builds. Also, you generally should only do this for one chip set. Simply stated, don't mix Intel and AMD chipset drivers together, they don't mix. You will probably need to craft two separate LiteTouch CD's and section the drivers that you want to inject into separate groups. One for Intel chipset driver and MSD, and another for AMD Drivers and MSD. But this is all simply assuming that you are using mixed hardware Q2 - The process automatically detects what drivers you need by the PNP ID's the process enumerates while in the PE environment and the drivers that were included on the WinPE CD when it was generated and injects only the ones you need on the fly. The only way that will work is if you properly establish a driver repository for all your hardware and group them if needed. Q3 - As mla1 said, you will need to custom edit your sysprep.inf file. To do this easily in the Deployment Workbench, go to your task sequence and then open it up. Click on the OS Info tab and then click on "Edit Sysprep.inf". Once open, edit it as needed. As a tip, if you are having trouble with the 7B stop error when deploying your image, place your mass storage device drivers PNP ID's in here as well. Then you will need to build out a directory path to have the drivers placed onto the C: drive when the image is deployed. That is where you will use $OEM$\$1\Drivers\MSD in your task sequence folder out on the distribution share under Control to place the files automatically in the process. Also, disable the Inject Mass Storage Device Drivers Task in the Capture leg of your sequence to stop the process from overwriting your changes. There are tutorials on how to do this if you are stuck. I hope I didn't insult your intelligence. I hope this may clear some things up for you. If you have any questions, please feel free to ask.

You are not authorized to post a reply.

Forums > Deployment Solutions > MDT 2008 > Couple more questions

ActiveForums 3.7

Forum Policies

These forums are a user-supported community for IT professionals to exchange deployment tips, solutions, and techniques. For the benefit of all Deployment Forum members, please observe the following guidelines when posting to these forums:

We reserve the right to remove any message. Our moderators will remove all messages that are not respectful or productive. Profanity, racism, prejudice, and flaming are not tolerated.
Do not advertise products or services. Our moderators will remove all advertisements or service announcements. Product and service recommendations from active Deployment Forum members are encouraged, however.
Make sure your question isn't already answered. Before posting questions, search the forums. After ensuring that your questions are unique, post them to the most appropriate forum. This will help reduce noise in the forums.
Help make the most of each thread. Do not post unrelated messages to a thread. Also, if you've resolved a question outside of these forums, please share the solution with other members by posting it back to the thread.
Do not share confidential information. Confidential information includes product keys and addresses. Our moderators will edit any message containing confidential information, so double-check messages and their attachments before posting them.
Post messages using only the English language. For the benefit of all Deployment Forum members, please post your messages using the English language.

We hope that you enjoy using this community. Please submit your comments and feedback on the Comments and Feedback page or post them to the Comments, Feedback forum.

Privacy Statement | Terms Of Use