Post installation task stop rebooting

Thread needs solution
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Beiträge: 2
Kommentare: 0

Hello we're deploying a bunch of PC's (windows 7) with acronis snapdeploy 4.
To activate windows and office we have create a script that does the job (VL with internal separate server).
The distribution task has as parameter to execute that script after the deploying. She script is local to the client computer and is a shell script that invoke the slmgr (for windows) and OSPP (for office) command through the cscript command.
What is happening is that at the end of the deployment, after the ssid change phase, all the computer get stucked to the ctrl-alt-canc request with a couple of windows on , waiting for a user that click on an "ok" (see attached image).
the translation of the texts are:
1) Acronis Sanp Deploy: the system will be reconfigured based on the options specified on the distribution task. at the end of the procedure the machine will be rebooted
2) Acronis OS patcher: Impossible to reboot while an operation is running
When I click on Ok, the pc's reboot a couple of times and everything finish.
What I get is a client where office is activated but windows is not. If I rerun the script everything goes fine.
How can I:
1) avoid the the warning (impossible to reboot)
2) activate windows (slmgr /skms + slmgr /ipk + slmgr /ato

thanx

davide

Anhang Größe
04122013009.jpg 801.49 KB
Mi, 12/04/2013 - 11:22
0 Users found this helpful
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Forum Member
Beiträge: 0
Kommentare: 69

Hello Davide,

The problem that we can see on the picture is a known one. There are 2 ways to treat it:
1. Contact our support and one of the SPs will provide you a build with a fix for this message.
2. Use a workaround instead of using inbuilt SnapDeploy "Applications to run".
-On master image machine before creating master image use:
schtasks ONSTART to schedule your script on next startup.
The script will do your desired operations: slmgr /skms + slmgr /ipk + slmgr /ato. The script has to also "unschedule" the above task.
Make sure it uses userlevel SYSTEM or HIGHEST to schedule it.
-Create master image.
-Unschedule the script on master machine.
Now you will have an image that once deployed will run your scripts once.

As for you second question about activating the machine on KMS:
If your master image machine was rearmed before creating the Master Image, then you won't have any problems.
If your master machine was not rearmed then once deployed your new machine will come to KMS under the same CMID (Client Machine ID) and won't take one more Microsoft License.
To make it work you will have to have more complicated scripts:
After deployment you will have to have a script rearm.bat that will do the following:
1. slmgr /rearm
2. Schedule activation script on next startup. (because you must restart after rearm)
3. Initiate reboot
And activation script that will:
1. slmgr /ipk /ato and so on.
2. Unschedule itself.

Di, 12/10/2013 - 20:32
  • Anmelden, um Kommentare verfassen zu können