Video Screencast Help

DS 7.1 Jobs not running from Initial Deployment

Created: 23 Apr 2013 | 4 comments

I setup a new Site Server on a Vm that was given to me. I pxe boot machines and I get the intial deployment window. I select a deploy image job and nothing happens. I have 4 tasks in my Job, partition, lay image down, install updates using dism and reboot. The partition and deploy image tasks fail with error 1. The other two succeed.

 

Any ideas why this could happen? Imaging through other pxe servers is fine. I tried on 2 out of box machines and failed on both.

Operating Systems:

Comments 4 CommentsJump to latest comment

Thomas Baird's picture

First, I need to understand - does "nothing happen" or does the job run and fails during the partition step?

We do have a known issue with partitioning that may require you to reboot to recognize the partition.

However, if you're laying down an image, that blows away partitions anyway, so why have a partition task?  Perhaps what you need to do is select an advanced option in imaging and only use part of the disk?

Please explain a bit more so we can better help, like WHY you need to partition the disk.  IF you are using scripted OS installs, that makes a lot more sense for instance.

Thanks!

PS.  I'm not sure I understand what you mean when you say "imaging on 2 other PXE servers is fine."  Imaging has nothing at all to do with PXE, and happens on the task server to which you are connected while in automation.  If another task server is working better than this one, with the same job exactly then we need to look at what may be wrong in WinPE.  You could grab the automation logs and look at that as well for instance.  Maybe the systems are not connecting?  This goes back to the first question - does nothing happen, or does the task actually fail (not with a time-out, but actually fail)?

Thomas Baird
Private Consultant & open to full-time opportunities.
That means I CAN help beyond the forum (directly).

 

huseinm's picture

I looked into the agents logs and I see the issue. I ran a simple disk wipe and I see mapping to DS share is failing. Here are the logs

 

[2013/04/24 15:47:16.725 2032:1384 2] Log File Created. Version 7.01.2316
[2013/04/24 15:47:37.770 2032:1384 2] apps\DeploymentClient\DeploymentSolutionAgent\DeploymentSolutionAgent_Task.cpp@83::Run()
[2013/04/24 15:47:37.770 2032:1384 2] t3.cpp@46::Run()
[2013/04/24 15:47:37.770 2032:1384 2] t3.cpp@50 Load ClientWipe.dll ep ClientWipe
[2013/04/24 15:47:37.770 2032:1384 2] t3.cpp:69 found Task Handler dll @ x:\program files\altiris\altiris agent\agents\agent tasks\DeploymentSolutionAgent.dll
[2013/04/24 15:47:37.770 2032:1384 2] t3.cpp@146 x:\program files\altiris\altiris agent\agents\agent tasks\ClientWipe.dll File Found
[2013/04/24 15:47:37.770 2032:1384 2] We are in automation.
[2013/04/24 15:47:37.770 2032:1384 2] apps\DeploymentClient\ClientWipe\Tcube_ClientWipe.cpp@113 ClientWipe::Run()
[2013/04/24 15:47:37.770 2032:1384 2] apps\DeploymentClient\ClientWipe\Tcube_ClientWipe.cpp@181 ClientWipe::RunDoDWipe()
[2013/04/24 15:47:37.770 2032:1384 2]  apps\DeploymentClient\ClientWipe\Tcube_ClientWipe.cpp: 196:  Parsing task XML
[2013/04/24 15:47:37.770 2032:1384 2] apps\DeploymentClient\ClientWipe\Tcube_ClientWipe.cpp@207 <EraseDisk><Options value="DeletePartition"><Disk Number="All" /><IsEraseData>True</IsEraseData></Options><ExeName>GDisk32.exe</ExeName></EraseDisk>
[2013/04/24 15:47:37.770 2032:1384 2] apps\DeploymentClient\ClientWipe\Tcube_ClientWipe.cpp@215 LoadXML Success
 
[2013/04/24 15:47:37.770 2032:1384 2]  apps\DeploymentClient\ClientWipe\Tcube_ClientWipe.cpp: 234: Input @EraseDiskToolPath=\Deployment\Task Handler\ghost\
[2013/04/24 15:47:37.770 2032:1384 2]  apps\DeploymentClient\ClientWipe\Tcube_ClientWipe.cpp: 244: Input @serverName=PP-BP-NSIR-01.CPEX.com
[2013/04/24 15:47:37.770 2032:1384 2]  apps\DeploymentClient\ClientWipe\Tcube_ClientWipe.cpp: 254: Input @authenticationPoint=\Deployment
[2013/04/24 15:47:37.770 2032:1384 2]  apps\DeploymentClient\ClientWipe\Tcube_ClientWipe.cpp: 262: Calling ClientWipe::MapDrive()
 strServerAndShare=\\SERVER FQDN\Deployment
[2013/04/24 15:47:37.770 2032:1384 0]  apps\DeploymentClient\ClientWipe\Tcube_ClientWipe.cpp: 479:  Calling Command to get N/W Credentials
[2013/04/24 15:47:37.770 2032:1384 1] FacadeStrategy::Command() called.
[2013/04/24 15:50:53.598 2032:1384 2] Command to get N/W Credentials failed.
[2013/04/24 15:50:53.598 2032:1384 2] apps\DeploymentClient\ClientWipe\Tcube_ClientWipe.cpp:268 OS Architecture is 32-bit, Using 32-bit Gdisk Tool...
[2013/04/24 15:50:53.598 2032:1384 2] apps\DeploymentClient\ClientWipe\Tcube_ClientWipe.cpp@280 Exe path = \\PP-BP-NSIR-01.CPEX.com\Deployment\Task Handler\ghost\gdisk32.exe  
[2013/04/24 15:50:53.598 2032:1384 2]  apps\DeploymentClient\ClientWipe\Tcube_ClientWipe.cpp: 282: Checking Options...
[2013/04/24 15:50:53.598 2032:1384 2]  apps\DeploymentClient\ClientWipe\Tcube_ClientWipe.cpp: 320: Do Remove Partition(s)
[2013/04/24 15:50:53.598 2032:1384 2]  apps\DeploymentClient\ClientWipe\Tcube_ClientWipe.cpp: 331: Retriving number of fixed disk attached..
 
[2013/04/24 15:50:53.598 2032:1384 2] apps\DeploymentClient\ClientWipe\Tcube_ClientWipe.cpp@588 ClientWipe::GetNumberOfDisks()
[2013/04/24 15:50:53.598 2032:1384 2] apps\DeploymentClient\ClientWipe\Tcube_ClientWipe.cpp@666 ClientWipe::CreateBatchFile()
[2013/04/24 15:50:53.598 2032:1384 2] apps\DeploymentClient\ClientWipe\Tcube_ClientWipe.cpp@669: Opening for write+: X:\GetNumberOfDisks.bat
[2013/04/24 15:50:53.598 2032:1384 2] apps\DeploymentClient\ClientWipe\Tcube_ClientWipe.cpp@682: Output from fwrite: 1
 
[2013/04/24 15:50:53.598 2032:1384 2] apps\DeploymentClient\ClientWipe\Tcube_ClientWipe.cpp@510 ClientWipe::ExecuteCommand()
[2013/04/24 15:50:53.598 2032:1384 1] ****** ExecuteClass:: In ExecuteCommandNoUser ******
 
[2013/04/24 15:50:53.598 2032:1384 1] ExecuteClass::Module Name = X:\GetNumberOfDisks.bat
 
[2013/04/24 15:50:53.598 2032:1384 1] ExecuteClass::Commandline = X:\GetNumberOfDisks.bat
 
[2013/04/24 15:50:53.598 2032:1384 2] ExecuteCommand.cpp@128 calling ExecuteClass::ExecuteCommandNoUser(). 
 
[2013/04/24 15:50:53.598 2032:1384 2] ExecuteClass::@161 Application Name is NOT NULL.
 
[2013/04/24 15:50:53.598 2032:1384 2] ExecuteClass::@174 Command line is NOT NULL.
 
[2013/04/24 15:50:53.598 2032:1384 1] ExecuteCommandNoUser()Successfully created process. nResult =1 
 
[2013/04/24 15:50:53.598 2032:1384 1]  Calling ExecuteClass::ProcessAfterCreate() 
 
[2013/04/24 15:50:53.691 2032:1384 2] ExecuteCommand.cpp@272 ProcessAfterCreate:: dwExitCode=1
 
[2013/04/24 15:50:53.691 2032:1384 2]  apps\DeploymentClient\ClientWipe\Tcube_ClientWipe.cpp: 520: ClientWipe ClientWipeException error=Error returned while executing file! value=1, error=183
[2013/04/24 15:50:53.691 2032:1384 2] apps\DeploymentClient\ClientWipe\Tcube_ClientWipe.cpp@547 ClientWipe::SetResult()
[2013/04/24 15:50:53.691 2032:1384 2]  apps\DeploymentClient\ClientWipe\Tcube_ClientWipe.cpp: 570: ClientWipe task completed. Failure return!!

 

huseinm's picture

Issues resolved, turned to be Infosec team were blocking rpc calls to DC.

Thomas Baird's picture

oh nice.  Thanks for the update.

 

For anyone else reading this, note the "command to get NW Credentials failed" message, and remember the resolution in this case.

Thomas Baird
Private Consultant & open to full-time opportunities.
That means I CAN help beyond the forum (directly).