none
MDT 2013 Udate 1 (new 8298) Windows 10 Upgrade TS Error - Unable to find rules INI file, ZTIGather, rc = 8000 RRS feed

  • Question

  • Hello,

    After updating to the newer 8298 Update 1 for MDT 2013, I'm getting the following error in my Win 10 Upgrade Task Sequence:

    Unable to find rules INI file, rc = 1

    ZTI ERROR - Non-zero return code by ZTIGather, rc = 8000

    After poking around I found this in the BDD log:

    <![LOG[Determining the INI file to use.]LOG]!><time="10:33:00.000+000" date="10-01-2015" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
    <![LOG[FindFile: The file Bootstrap.ini could not be found in any standard locations.]LOG]!><time="10:33:00.000+000" date="10-01-2015" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
    <![LOG[Unable to locate Bootstrap.ini]LOG]!><time="10:33:00.000+000" date="10-01-2015" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
    <![LOG[Finished determining the INI file to use.]LOG]!><time="10:33:01.000+000" date="10-01-2015" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
    <![LOG[Unable to find rules INI file, rc = 1]LOG]!><time="10:33:01.000+000" date="10-01-2015" component="ZTIGather" context="" type="3" thread="" file="ZTIGather">
    <![LOG[ZTI ERROR - Non-zero return code by ZTIGather, rc = 8000]LOG]!><time="10:33:01.000+000" date="10-01-2015" component="ZTIGather" context="" type="3" thread="" file="ZTIGather">
    <![LOG[Event 41002 sent: ZTI ERROR - Non-zero return code by ZTIGather, rc = 8000]LOG]!><time="10:33:01.000+000" date="10-01-2015" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
    <![LOG[Command completed, return code = 8000]LOG]!><time="10:33:01.000+000" date="10-01-2015" component="UpgradeSummary" context="" type="1" thread="" file="UpgradeSummary">
    <![LOG[sUpgradeResult = SUCCESS]LOG]!><time="10:33:01.000+000" date="10-01-2015" component="UpgradeSummary" context="" type="1" thread="" file="UpgradeSummary">

    I've checked both the boostrap.ini file and my customsettings.ini to ensure that DeployRoot and ResourceRoot were correct.

    Any thoughts?

    Monday, October 5, 2015 3:02 PM

Answers

  • I think the reason is that during UpgardeSummary run, the deployment share is not yet connected and therefore ZTIGather can not find and copy the bootstrap.ini.

    Try add this at the beginning of the Main function of upgradesummary.wsf:

    oUtility.ValidateConnectionEx oEnvironment.Item("DeployRoot"), True

    • Marked as answer by Matt Topo Saturday, October 10, 2015 5:52 PM
    Wednesday, October 7, 2015 8:27 AM

All replies

  • Check that the share permissions and if necessary make them less restrictive then rebuild your boot image.

    Most important details are logs. If you are unsure how to post logs or where to find them then reference https://keithga.wordpress.com/2014/10/24/video-mdt-2013-log-files-basics-bdd-log-and-smsts-log/

    • Proposed as answer by Ty GlanderModerator Monday, October 5, 2015 8:46 PM
    • Unproposed as answer by Matt Topo Monday, October 5, 2015 11:58 PM
    Monday, October 5, 2015 8:27 PM
    Moderator
  • I checked the share permissions; admins have full control and everyone has rwx.

    Here is the log file associated with one of these Upgrade deployments:

    https://onedrive.live.com/redir?resid=DD22E4E9894DBBC8!111&authkey=!AMhLv9NF3K2k5N8&ithint=file%2cLOG

    Thank you

    Tuesday, October 6, 2015 12:09 AM
  • For some reason Post Win10 Upgrade gather is looking for BootStrap.ini.  Can you file a bug on Connect for this and include the full set of logs as well as the TS.xml and Unattend.xml from your WIN10-UPGRADE Task sequence?


    Most important details are logs. If you are unsure how to post logs or where to find them then reference https://keithga.wordpress.com/2014/10/24/video-mdt-2013-log-files-basics-bdd-log-and-smsts-log/

    Tuesday, October 6, 2015 1:12 AM
    Moderator
  • I'll submit a bug, however I'm using the default base Upgrade TS along with the base Win 10 x64 Enterprise WIM, and an unmodified unattend.

    Tuesday, October 6, 2015 4:22 PM
  • I think ultimately it will be an issue with the share/file permissions.  In previous versions of MDT the share permissions were set to Everyone Full Control and file permissions are where things would be locked down if necessary.

    https://keithga.wordpress.com/2015/10/02/mdt-uberbug11-security-vs-usability/

    https://keithga.wordpress.com/2015/01/06/security-week-locking-down-your-deployment/

    I should have clarified.  Keith looks to have seen this also.  The first link is the his observations.  The second is a suggested permissions (suggested is used loosely,).


    Most important details are logs. If you are unsure how to post logs or where to find them then reference https://keithga.wordpress.com/2014/10/24/video-mdt-2013-log-files-basics-bdd-log-and-smsts-log/




    Tuesday, October 6, 2015 5:17 PM
    Moderator
  • Ty,

    Interestingly enough, on a whim I edited LTICopyScripts and included Bootstrap.ini in it.

    The next upgrade using the same TS completed without any errors and/or warnings..

    Tuesday, October 6, 2015 7:26 PM
  • It still boggles me. Is it possible that the gather step post install is set to bootstrap.ini?

    Most important details are logs. If you are unsure how to post logs or where to find them then reference https://keithga.wordpress.com/2014/10/24/video-mdt-2013-log-files-basics-bdd-log-and-smsts-log/

    Tuesday, October 6, 2015 7:49 PM
    Moderator
  • Nope, it's set to customsettings.ini (I've also tried removing this to the default value of gather settings locally and do not process rules with the same results).

    Tuesday, October 6, 2015 9:05 PM
  • I am glad you were able to figure out a work around. I suspect the connect bug will continue to be interesting.

    Most important details are logs. If you are unsure how to post logs or where to find them then reference https://keithga.wordpress.com/2014/10/24/video-mdt-2013-log-files-basics-bdd-log-and-smsts-log/


    Tuesday, October 6, 2015 9:41 PM
    Moderator
  • I think the reason is that during UpgardeSummary run, the deployment share is not yet connected and therefore ZTIGather can not find and copy the bootstrap.ini.

    Try add this at the beginning of the Main function of upgradesummary.wsf:

    oUtility.ValidateConnectionEx oEnvironment.Item("DeployRoot"), True

    • Marked as answer by Matt Topo Saturday, October 10, 2015 5:52 PM
    Wednesday, October 7, 2015 8:27 AM
  • Alan,

    That worked flawlessly!

    Now the only other things I've noticed are that the MININT folder and the Windows.old folder remain.

    I tried adding a variable to my customsettings, RemoveWinOldSuccess=YES however this doesn't seem to work. I did however add a TS step to forcibly remove the directory upon the reg key HKLM\Software\Microsoft\Windows NT\CurrentVersion\Windows\Win10UpgradeStatusCode = SUCCESS and that worked for Windows.old however it kills the TS early for the MININT folder....

    Saturday, October 10, 2015 5:57 PM
  • I think this is a software bug. I met the same problem. I solved by installing the preview release, and then install the full version.
    Monday, November 9, 2015 4:55 PM