Deployment Solution

Why do I get these random time outs on my reboot to production task :

The registration period is set to 60 minutes. The job that ran next was fine!

Hi JannasTo,

Probably if client performs refresh policy after each 1 hour to receive SMA/CTA settings, then it doesn't fall in in all filters/resource targets per this time range (time to time) to successfully register with TS and proceed with job execution?

• Check SMP Server side logs for this period
• Open "Resource Manager" of this client PC and check when was last config request/basic inventory sent/CTA registered.

This happens time after time with random client(s) or with exact client(s)?

Thanks,

IP.

Just happens now and again with some clients. The next job on another machine (same type/model) completed OK with no error. Will check the logs and see if I can see anything

Thanks

I am still having problesm with machine not rebooting to production. As soon  as it times out it continues. surely this must be a bug!

What am I looking for int he logs ?

hi,

this is a known issue in some versions of the product. Can you please provide the full version of DS installed? (including SP and HF)

Also, if the image includes an old SMA(agent), it is possible that it will not report back correctly to the console:

https://support.symantec.com/en_US/article.TECH223609.html

Mauro

What we ended up having to do in our environment to get past the reboot to production issue is just run a standard script job.

Command Script:

wpeutil reboot
exit 0

Thanks,

Clay

Thanks - will give this a try.

Its 7.5 SP1 HF3 - that link is different error. My reboot to production just times out! The image was created through 7.5 SP HF3.

OK, script was working now getting lots of machine timing out at this task. When it times out the next task works fine. This is a pain in da a55!