Friday, January 09, 2009
Deployment Forum HomeDeployment Forum ArticlesDeployment Forum Download LibraryDeployment Forum Member BlogsDeployment Forum Community Forums
Member Login
StandardLiveID


Register
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.

Subject: confusion on which settings will win?
Prev Next
You are not authorized to post a reply.

AuthorMessages
DavidUser is Offline

Posts:50

Send Message
08/08/2008 5:08 PM  

1) the task squence properties 'os info' tab has the edit sysprep.inf
button, there is also already a sysprep.inf file within the wim file I
captured via mdt, so which is used? both (merge)?

2) Here is my theory on the when/how the unattend.txt and sysprep.inf files
from the task squence properties 'os info' tab are used. *PLEASE* correct me
if I am wrong. The unattend.txt is used during initial unattended
installation of the OS by mdt, the sysprep.inf is copied to the target
machine before sysprep is run.... so *after* a wim is captured of this and
you make a new task sequence to deploy this custom wim the sysprep.inf file
that is already in the wim is used and so the unattend.txt and sysprep.inf
from the task squence properties 'os info' tab is simply not used?

generally confused on which settings where take precedence when they exist
in more than one place... like sysprep.inf in either the task sequence or
the wim, or the task sequence properties/variables that could be supplied
via the deployment wizard or set by your own scripts?

bpostiauUser is Offline

Posts:7

Send Message
08/10/2008 4:33 AM  
Hi
Unattend.txt is being used at first install (when you create your image)
sysprep.inf is created at the end of the image creation by mdt and inserted in the captured image with settings (new drivers path, etc that you define).
You can override specific settings at deployment by using a different sysprep file (this time the original will not be used)
Note that unattend.xml is the vista/win2008 sysprep file.

hope that it helps
mla1User is Offline

Posts:50

Send Message
08/11/2008 3:22 AM  

bpostiau,  I dont think you answered the question.   When you build and capture a windows xp WIM, the sysprep.inf in the capture task sequence is used and added to the wim. 

When you deploy the captured wim you have another sysprep.inf in the deploy task sequence.  (this is also used as if you start to change things like product key this is reflected on the machine that you are deploying to.  Can someone clarify this please. 

 

PyrosoftUser is Offline

Posts:48

Send Message
08/11/2008 6:33 AM  
If you have a Create and a Deploy then the sysprep file that will be used is in the Create structure.

I think thats what you are asking anyway
DavidUser is Offline

Posts:50

Send Message
08/11/2008 10:59 AM  

I posted this to an MS newsgroup also. Here is a copy/paste of the reply I got.

-----------------------

1) the task squence properties 'os info' tab has the edit sysprep.inf
button, there is also already a sysprep.inf file within the wim file
I
captured via mdt, so which is used? both (merge)?

Correct.  If no sysprep.inf is in the wim than the entire sysprep.inf
from distribution\Task Sequence directory is copied to machine.  If
they are in both places a merge happens.

2.)so the unattend.txt and sysprep.inf from the task squence
properties 'os info' tab is simply not used?
False

The script that makes the merge happens is "ZTIConfigure.wsf."  It
reads ZTIConfigure.xml and based on all the properties as defined
there a merge occurs.  Values which are present in the sysprep.inf
from the distribution directory win.

If you open the xml file look for "mapping id" to the the values
checked.  In this way you can manage the sysprep.inf from 1 central
location.  Ultimately, you could mount the captured wim with imagex
and remove the sysprep.inf from the image but this should not
generally be necessary.  XP needs sysprep.inf tp be present so that
MassStorage drivers will be included when that image is captured.

Dave Guenthner [MSFT]

-------------------------------

You are not authorized to post a reply.
Forums > Deployment Solutions > MDT 2008 > confusion on which settings will win?



ActiveForums 3.7
Forum Policies
Minimize

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
© 2007 Jerry Honeycutt