I have found, from time to time, removing the step "gather", saving the TS, and then re-adding the step, solved a similar issue for me.
> On Oct 14, 2014, at 9:51 AM, Michael Niehaus <[email protected]> > wrote: > > MDT will process the CustomSettings.ini file from the “settings” package that > you referenced. Are you sure it contains the expected file? > > If that looks good, the complete BDD.LOG could provide more clues. > > Thanks, > -Michael > > From: [email protected] [mailto:[email protected]] > On Behalf Of Brian Marobella > Sent: Tuesday, October 14, 2014 7:54 AM > To: [email protected] > Subject: [mssms] [MDT-SMS] 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 > >
