Sorry it took so long to get back to you.

If you want to have the machines auto assign to the computers OU, just leave 
the 2 DomainOU lines out.





From: [email protected] [mailto:[email protected]] On 
Behalf Of Wilcox, Kyle
Sent: Tuesday, May 24, 2016 2:12 PM
To: [email protected]
Subject: Re: [MDT-OSD] Customsettings.ini vs task sequence variables

Ok, I know I am getting of on a tangent here, but I see different OUs below. 
Our AD guy has requested that computers join the default computers container.  
When I put MachineObjectOU=CN=Computers,DC=DomainName,DC=local I get an error 
stating that it cannot start with CN.  How can I get computers to just go to 
the default computers container?

-Kyle

On Tue, May 24, 2016 at 11:09 AM, David Landry 
<[email protected]<mailto:[email protected]>> wrote:
You can add these settings to your CS.ini file:

OSDComputerName=<SiteCode>-%SerialNumber%
JoinDomain= <YourDomainName>
DomainOUs1=OU=Laptops,OU=<Site>,OU=North 
America,DC=<DomainName>,DC=<DomainName>,DC=com
DomainOUs2=OU=Desktops,OU=<Site>,OU=North 
America,DC=<DomainName>,DC=<DomainName>,DC=com
TimeZone=035
TimeZoneName=Eastern Standard Time
Home_page= http://<whatever<http://%3cwhatever> you want>


List of time zones: http://unattended.sourceforge.net/timezones.php

These settings will auto configure your Deployment Wizard.

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]<mailto:[email protected]>] 
On Behalf Of Marable, Mike
Sent: Tuesday, May 24, 2016 6:29 AM
To: [email protected]<mailto:[email protected]>
Subject: Re: [MDT-OSD] Customsettings.ini vs task sequence variables

If I remember correctly, once a variable has been set you cannot change it.  
So, if you have conflicting values (I believe) that the first one set is the 
winner.

Were are you instructing MDT to join the computer to the domain?  Is it through 
the GUI with the wizard, or elsewhere?

What exactly do you have in the BootStrap.ini?  There should only be a minimum 
of values set in that file, basically only what is needed to get the process 
started.  Once the MDT wizard CustomSettings.ini takes over.  Between the two, 
BootStrap is very minimal while CustomSettings does the heavy lifting.

Mike

From: <[email protected]<mailto:[email protected]>> 
on behalf of "Wilcox, Kyle" 
<[email protected]<mailto:[email protected]>>
Reply-To: "[email protected]<mailto:[email protected]>" 
<[email protected]<mailto:[email protected]>>
Date: Monday, May 23, 2016 at 11:52 PM
To: "[email protected]<mailto:[email protected]>" 
<[email protected]<mailto:[email protected]>>
Subject: RE: [MDT-OSD] Customsettings.ini vs task sequence variables


How can I determine whether a custom setting or a ts variable will have 
precedence?

Also, do any settings from bootstrap.ini carryover to either of these two?

I am using a local account in bootstrap.ini to access the deployment share and 
the variable of workgroup is set.

However I am trying to have the computer join the domain and I see in the log 
file that the join domain setting keeps getting changed back to workgroup. I am 
wondering if this could be coming from the bootstrap.ini?

-Kyle
On May 22, 2016 9:55 AM, "Phil Schwan" 
<[email protected]<mailto:[email protected]>> wrote:
The CS.ini file provides a set of extra rules for the Gather (ZTIGather.wsf) 
function to process.  This can include things like connecting to databases or 
providing logic around creating/combining new values.  ZTIGather ultimately 
ends up creating or modifying a number of Task Sequence variables that the TS 
can use throughout execution.  If you look at the ZTIGather.log file (or the 
section of smsts.log where it executes), you’ll see the variables being set in 
the TS environment.

-Phil
_________________________________________________________________
Phil Schwan | Technical Architect, Enterprise Windows Services
Microsoft VTSP ([email protected]<mailto:[email protected]>)
Project Leadership Associates | 2000 Town Center, Suite 1900, Southfield, MI 
48075
Lync: 312.756.1626<tel:312.756.1626>  Mobile: 419.262.5133<tel:419.262.5133>
www.projectleadership.net<http://www.projectleadership.net/> 
[inkedin_logo-19x20] <http://www.linkedin.com/in/philschwan> 
[witter-Logo1-20x20] <https://twitter.com/philschwan>  [ordpress-logo3] 
<http://lab-geek.com/>
[escription: Description: Description: Arrow email]Lead with Strategy. Leverage 
Technology. Deliver Results.



From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]<mailto:[email protected]>] 
On Behalf Of Wilcox, Kyle
Sent: Sunday, May 22, 2016 8:57 AM
To: [email protected]<mailto:[email protected]>
Subject: [MDT-OSD] Customsettings.ini vs task sequence variables


What is the difference between customsettings.ini and task sequence variables

I have been using customsettings.ini for over a year now but never really had 
any idea what a task sequence variable was.

As I learn more they seem to be the same. Pros and cons?

-Kyle

**********************************************************
Electronic Mail is not secure, may not be read every day, and should not be 
used for urgent or sensitive issues



--

Kyle Wilcox
Lead Technology Trainer for Westfield Washington Schools
317-519-4219

WWS Portal<http://portal.wws.k12.in.us/>
Create a Help Desk 
Ticket<http://helpdesk.wws.k12.in.us:8080/ehelpdesk/login.glml>
https://sites.google.com/a/wws.k12.in.us/wilcox-tech-tips/

Reply via email to