Some variables can be overwritten, some cannot. You can tell by looking at the
ZTIGather.xml file:
PS C:\> ((get-content C:\PSDeploymentShare\Scripts\ZTIGather.xml) -as
[xml]).properties.property |
?{ $_.overwrite -eq "true" }
id type overwrite description
-- ---- --------- -----------
DeployRoot string true The UNC path to the deployment share
ResourceRoot string true The UNC path to resources (drivers,
packages) kept se...
DeployDrive string true The drive letter mapped to the
deployment share (Lite...
ResourceDrive string true The drive letter mapped to resources
(drivers, packag...
DeploymentMethod string true The method being used for the
deployment (NETWORK, ME...
DeploymentType string true The type of deployment (NEWCOMPUTER,
REFRESH, REPLACE...
Phase string true The current phase of the deployment
(NEWCOMPUTER, STA...
DestinationDisk string true Disk Number that the image will be
deployed to
DestinationPartition string true Disk Partition that the image will be
deployed to
DestinationOSInstallType string true Mechanism Apply OS step should use to
determine where...
DestinationOSVariable string true Drive letter to deploy OS to (e.g.
G:) when Destinati...
They are mostly properties that can change throughout the lifecycle of a Task
Sequence, but mostly most variables, once read by CS.ini stay the same
throughout your TS.
This only applies to ZTIGather.wsf, you can change a variable at any time
within a script.
From: [email protected] [mailto:[email protected]] On
Behalf Of Wilcox, Kyle
Sent: Monday, May 23, 2016 8:52 PM
To: [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 ( <mailto:[email protected]> [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>
<http://www.projectleadership.net/> www.projectleadership.net
<http://www.linkedin.com/in/philschwan> <https://twitter.com/philschwan>
<http://lab-geek.com/>
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
