Hi my friends!
This guide has been tested on W7/8 & 8.1 Systems
Maybe You’re familiar to this kind of error on SCCM2012 Deployments :
“The task sequence execution engine failed to install (program) package () for action (Install Software) in the group () with exit code 2. The operating system reported error 2: The system cannot find the file specified.”
The cause? In my case -> This happens when a machine suspends in “downloading phase moment ” on MDT 2013 of the “Install software” step in MDT (sccm integrated) this makes the app to fail 😦 with error code 2
So …Today we gonna create our own energy plan and deploy to our machines this plan never gonna suspend the machine and we can solve this issue … This method works on the phase when the operating system image deployed runs on the machine when you usually deploy the online updates & software 🙂 , you must apply the option in the right place ( after “Use Toolkit Package” and “Set status4”
I had to make this because in our company we are deploying Surface 3 systems and other computers that gives to us problems with the “Install software phase” because sometimes the machine suspends during the process due to energy default plan included on WIMS of Windows 8.1 /7
Creating the solution
1. First Step ( Creating our desired energy plan )
Personalize and create your plan and name it if you want .. in control panel -> energy & power options

2. Export the plan with the powrcfg tool (MSDOS CONSOLE)
First we gonna need the GUID of the power plan :
Run : powercfg /list on the console to catch the GUID of our personalized plan
Next step y export this conf with the next command
Syntax :
powercfg /export <> <>
Example:
powercfg /export d:\test.pow 1e2a1ba5-9c72-4eda-8aed-0430d23339b3
You will store a *pow file on the route specified
3. Create Powershell Script (PS1) on SCCM with the pow FIle and import into a task sequence or deploy to machines
Like this
xcopy “.\*.pow” “C:\windows” /D /E /C /I /Q /H /R /Y /S # <- copy the plan on Windows Folder
powercfg -import “C:\windows\plan.pow” # <- Import the plan
$p = gwmi -NS root\cimv2\power -Class win32_PowerPlan -Filter “ElementName =’faunos’” # <-This is the name of the plan
$p.Activate() # activate the plan
Create the package using option “Run Powershell Script” on MDT
4. Enjoy IT , now your machines will deploy all your software without problem with energy plans !!



