Deployment Solution

Since our upgrade to 7.5, the built-in Power Control shutdown task does not work when in WinPE.  Thoughts?

We are having the same issue with Boot to Production in WinPE.

Same here.  Not sure if a hotfix takes care of it (we're on hotfix 4).  If not, maybe SP1?

We are on HF5 and the kicker is that is an environment with an IP Helper address configuration the reboot to production works on the device and reports a failure within the console. However, at a site with ForcedPXE configuration the device does not even get the task and just times out after laying down the image and running other tasks.

Our systems reboot after the image and driver injection, but the Task Status never shows as complete, so the job stops there and we have to restart it from Production.

Wow, there are a lot of issues in here.

1) when you say the power control task doesn't work, that may be a known issue.  Call it in.  HOWEVER, you might try the reboot to task instead.

2) if you have an image with an old agent in it (e.g. captured in 7.1) and you attempt to use the Reboot To task to get back into production, it will fail.  Let me repeate, it WILL fail.  This is because the task does not actually complete until it gets into production and receives the task AGAIN from the task server.  At this point, an older agent version will not understand this rebuilt task and fail it because it doesn't know how to execute it.

2a) as a subnote, IF your production image is lacking the deployment agent, it will also fail.

3) the forced PXE mode and/or IP helper situation has absolutely nothing to do with whether or not the task is received.  That may be a common factor in the environment, but trust me, it has NOTHING to do with the error you're troubleshooting.  You'll need to look at the Task Server in that environment instead, not the PXE configuration.  If you need to proove this, take a thumb drive with the PreOS environment on it, and test in both environments.  You'll get the same results.

3a) UNLESS it's the preboot environment itself that is damaged in one of those places.  The thumb drive may root this issue out as well.  If the thumb drive image works in location A but not in location B, then you've learned something, right?  Not definitive, but it's a start.

So, everyone, take a look at YOUR situation, and let's get some answers!!  :D

Sean works with me - our ticket is 6622199

We are testing the USB boot method right now

On 2a -during the image build we have a script that copies the latest agent and installs it. Before reboot

we use a reboot to production command here

this works for us and has always worked for us. In fact it is working at two of our 6 sites right now.

This is the what we are trying to fix

I have already done a recreate boot enviroment and also copied the bootwiz folder from working site serer to broken site

Actually, our issues are with the Reboot To task, not Power Control.  And it could be related to a site server bug that we've run into that's supposed to be fixed in SP1.  Latest agents are captured, including the Deployment plugin (7.5).

Noticed this problem in our environment as well.

Found this KB article that was published back on 10/15/2013 and never updated:

DS 7.5 - Power Control tasks do not work properly while client machine is in Automation:

http://www.symantec.com/business/support/index?page=content&id=TECH211551