Video Screencast Help

Managed computer receives image task, but it disappears quickly.

Created: 01 Feb 2013 • Updated: 01 Feb 2013 | 9 comments

If I send a Reboot to PXE task to a managed computer, it goes into our x64 WinPE environment as it should.  I then have a deploy image task sent to the machine using rdeploy.  On the managed computer, the rdeploy prompt shows for two seconds at best, and disappears.  Checking the console then shows that the task fails.  This is a sysprepped image of Windows 7 x64.

However, if I run another deploy image task with an image of Windows XP, the image starts and runs fine. 

What could be the difference?

Comments 9 CommentsJump to latest comment

boonet's picture

NS report:
Task Failed, Return Code: 1

From PECTAgent.log:

<event date='Feb 01 08:50:59' severity='4' hostname='MININT-B5430PB' source='Client Task Agent' module='Client Task Agent.dll' process='PECTAgent.exe' pid='564' thread='1036' tickCount='87625'>
<![DATA[Task: Windows 7 x64 SP1 has started]]>
</event>

<event date='Feb 01 08:51:05' severity='4' hostname='MININT-B5430PB' source='Client Task Agent' module='Client Task Agent.dll' process='PECTAgent.exe' pid='564' thread='1036' tickCount='93538'>
<![DATA[Task: Windows 7 x64 SP1 has finished]]>
</event>

From ClientImageDeploy.log:

[2013/02/01 08:51:05.788 564:1128 0]
apps\DeploymentClient\ClientImageDeploy\Tcube_ClientImageDeploy.cpp@134 Child Process returned an error value=60 error=183
[2013/02/01 08:51:05.788 564:1128 2]
apps\DeploymentClient\ClientImageDeploy\Tcube_ClientImageDeploy.cpp@1105 Output
@errorMessage=Child Process returned an error
[2013/02/01 08:51:05.788 564:1128 2]
apps\DeploymentClient\ClientImageDeploy\Tcube_ClientImageDeploy.cpp@1114 Imaging Completed.  Failure return!!

 

mclemson's picture

Error 183 usually means it likely doesn't have a file it needs.  You should make sure that the computer's subnet is assigned to a site, and that the site has a site server running task, package, and deployment services/handlers are assigned to it.  It could be booting to a task server in automation that isn't its PXE server, at which point the RDeploy file is not found.  

Perhaps also confirm that the site server being used has the image file the client wants to load.  If it's invalid or download pending, the client of course will fail the RDeploy task.

You flagged this as DS 6.x but do you mean 7.x based on the logs referenced in your second post?  I hope so, as I'm responding as though this were DS 7.1.

Mike Clemson, Senior Systems Engineer, ASC
Intuitive Technology Group -- Symantec Platinum Partner
intuitivetech.com

boonet's picture

I have verified that the computer's subnet is assigned to a site.  Our NS handles our deployment.  I can see that it is running:
Altiris Base Task Handlers
Altiris Client Task Server Agent
Deployment Task Server Handlers
Package Server

The NS holds all of the images, so that shouldn't be the problem.

And yes, apologies.  I did mean to mark it 7.1  I have edited the original post.  Thank you!

mclemson's picture

Are other tasks successful?  What does your job and your RDeploy task look like?

Mike Clemson, Senior Systems Engineer, ASC
Intuitive Technology Group -- Symantec Platinum Partner
intuitivetech.com

boonet's picture

Well this is interesting...

I have two different Windows 7 x64 images

I have one Windows 7 x86 image

I have one Windows XP image

The XP and 7 x86 images will apparently push through.  However, netiher of the Windows 7 x64 will.  There was a point in time where one of the x64 images worked.  The second one was newly made.

The Windows 7 x64 and x86 should have been sysprepped nearly identically.  I am not sure what the difference is...

mclemson's picture

My above point -- that error 183 means a file is not found as referenced -- is still valid and hasn't been addressed.  Are all of your site servers running task service, package service, and deployment task handlers?  If not, then you must make sure that a computer booting to PXE is registering to the task server that has the image resource.  You can do this with a script that does a dir pause so that you have time to open a command prompt and confirm the file is present on whatever server you booted to.  (Or record the IP before WinPE loads and check the server separately.)  

If all site servers are running all services and handlers, then confirm that all have a healthy package status and have all packages replicated.  If the image resource isn't present, your job will fail.

Mike Clemson, Senior Systems Engineer, ASC
Intuitive Technology Group -- Symantec Platinum Partner
intuitivetech.com

boonet's picture

Just a note...

The image that is failing in 7.1 is running in 6.9 without a hitch.  I can't explain it.

mclemson's picture

Explanation: 7.1 is completely and totally separate from 6.9.  This is like saying something works in VBScript but not PowerShell, or the patch deploys fine in Altiris but not in SCCM.  That being said, if the file used is identical, this tells you that it's the delivery of the file that's failing.  Which leads you to the steps I and Thomas have recommended.

Mike Clemson, Senior Systems Engineer, ASC
Intuitive Technology Group -- Symantec Platinum Partner
intuitivetech.com

Thomas Baird's picture

How many site servers do you have, besides the NS itself?

Do you know what site server your client is connecting to while in automation?

IF, as you say, the images are on the NS, and IF the clients are not connecting to the NS for Task services, and IF the task server the clients are connecting to does not have the images replicated to them for any reason, then the image task will fail.  RDeploy will launch, attempt to find the image, fail, and exit.  Not because the image doesn't exist on the network, but because it's looking for it on the site server and it doesn't exist THERE.

Thus the two above questions make sense.

Thomas Baird
Private Consultant