Yes... to all of your questions.  I re-created all new packages, Boot files, 
etc... after upgrade. Used the "Create MDT Task Sequence" wizard on ConfigMgr.

From: [email protected] [mailto:[email protected]] On 
Behalf Of Jimmy Martin
Sent: Friday, October 10, 2014 9:30 AM
To: [email protected]
Subject: RE: [MDT-OSD] OSD Task Sequences not processing CustomSettings.ini


*         Did you create a new task sequence or did you continue to use the 
updated one?

*         Do you use mdt integration?

o   Did you go through and update all the use toolkit lines to reference the 
new toolkit?


Jimmy Martin
(901) 227-8209

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Brian Marobella
Sent: Friday, October 10, 2014 8:19 AM
To: [email protected]<mailto:[email protected]>
Subject: [MDT-OSD] OSD Task Sequences not processing CustomSettings.ini

Hello,
ConfigMgr OSD (MDT) Task Sequences are not "Gathering" CustomSettings.ini 
during the deployment of the Task Sequence via ConfigMgr.  The 
CustomSettings.ini lives in the Custom Settings Package that gets created 
during the MDT Task Sequence creation wizard.  We've also tried adding the 
CustomSettings.ini to the Control folder in the MDT Files package to no avail.

Things to note:
-We recently upgraded to ConfigMgr 2012 R2 CU2
-We are unable reproduce this in an environment that is ConfigMgr 2012 SP1
-Logs show no errors at all and the TS finishes without issue except that it 
does not set any variable such as computer name, location etc..
-Task Sequence processes some generic settings. ZTIGather.log shows the 
following processing information which appears to be using some generic 
CustomSettings.ini

Using COMMAND LINE ARG: Ini file = CustomSettings.ini
Finished determining the INI file to use.
Added new custom property MYCUSTOMPROPERTY
Using from [Settings]: Rule Priority = DEFAULT
------ Processing the [DEFAULT] section ------
Property OSINSTALL is now = Y
Using from [DEFAULT]: OSINSTALL = Y
Property SKIPCAPTURE is now = YES
Using from [DEFAULT]: SKIPCAPTURE = YES
<Message containing password has been suppressed>
<Message containing password has been suppressed>
Property SKIPPRODUCTKEY is now = YES
Using from [DEFAULT]: SKIPPRODUCTKEY = YES
------ Done processing CustomSettings.ini ------

We've never had any issues with processing CustomSettings.ini in ConfigMgr OSD 
Task Sequences until upgrading to R2 CU2.

Any help or guidance would be great.

Thanks

This message and any files transmitted with it may contain legally privileged, 
confidential, or proprietary information. If you are not the intended recipient 
of this message, you are not permitted to use, copy, or forward it, in whole or 
in part without the express consent of the sender. Please notify the sender of 
the error by reply email, disregard the foregoing messages, and delete it 
immediately.


P Please consider the environment before printing this email...


Reply via email to