Issue
More recent versions of Windows 10 do not respect the "min power savings" setting used by Imaging Toolkit 10 to keep machines awake.
This means that during phase 3 Application Installation, machines may go to sleep if application installation takes a long time.
Ideally one would simply configure new power settings using a phase3-before script, however the build process alters the power settings after the phase scripts have run, therefore negating any settings applied.
|
Solution
Upgrade to Imaging Toolkit 11.0.
If upgrading is not possible create a script which is launched asynchronously by the phase3-before script and polls waiting for a point after the power settings have been configured to set the updated values.
Procedures
Done | Task | ||
---|---|---|---|
| |||
| |||
|
Add powerscheme.vbs to project Custom Files
- Download the attached powerscheme.vbs file
- Open the affected project in Build Console and add the powerscheme.vbs file to the Custom Files view
- Download the attached powerscheme.vbs file
Update phase3-before.vbs to launch powerscheme.vbs
- Right-click and Edit the phase3-before.vbs in the Custom Files view
- Add the following lines:
Utils.AppendLog "Launching powerscheme.vbs script" Utils.Run "wscript c:\ztoolkit\powerscheme.vbs", 0, false
- Save the file
- Validate the project and then use the Deployment Wizard to recreate the Build Process (ztoolkit) image
- Copy the updated ztoolkit image to your imaging server/share
- Right-click and Edit the phase3-before.vbs in the Custom Files view
Test
- Build a machine using the new ztoolkit image
- If the scripts have been correctly implemented the machine will not go to sleep during phase 3
If you have any problems or questions about the script or steps in this TID please contact the ENGL support team