Altiris 7.1 - PC's boot to WinPE but tasks fail while in WinPE
Created: 22 Oct 2012 | 6 comments
We have just set up a Altiris 7.1 environment for our company, the begining of last week we had all our 2 sites set up and imaging was working perfectly fine. We ran a batch of 15 computers imaged just fine. Today at both our NS server site and our Site Server site PC's will boot to WinPE and the last line says "startup completed" but from there all tasks fail to run.
We have restarted all 4 of the PXE services at both our site and NS servers.
We can ping the servers from the PC's
Here is what we get in the console
| Status: | Failed |
| Return code: | 1 |
Any ideas?
Thanks,
Jim
Discussion Filed Under:
Comments 6 Comments • Jump to latest comment
You should find logs for the PreBoot Client task agent (PECTAgent) in the WinPE client window. Browse to c:\program files\altiris\logs or similar, or maybe x:
Authorised Symantec Consultant (ASC) with Endpoint Management Limited, an Authorised Symantec Delivery Provider based in the UK.
Connect Etiquette: "Mark as Solution" posts that fix your problem, thumbs up for useful
The only error I am seeing is
command n/w credentials failed
We double checked all our credentials and its working
I did some checking around the forums on this error and nothing I could find helped
We didn't install any intrusion software over the past week
We checked and made sure DNS has FQDN entry
We were able to map the deployment server share just fine
Try and find the Domain Controller that's failing the network credentials login, see if there's a useful error message there.
Authorised Symantec Consultant (ASC) with Endpoint Management Limited, an Authorised Symantec Delivery Provider based in the UK.
Connect Etiquette: "Mark as Solution" posts that fix your problem, thumbs up for useful
Anothing item to check regarding n/w credentials is the format that it is being used. If you are only using a username, this can be a problem. You may need to change it to use "DOMAIN\username" or the UPN model of "username@UPNDOMAIN".
Also, for testing purposes, if you have a complex password on that account, you might try simplifying it to see if that is what is causing it. Make sure that the account isn't being locked out and that the password isn't set to expire or to be changed on the next logon.
Brian Hawver
Systems Engineer
Yaskawa America, Inc.
Connect Etiquette: "Mark as Solution" those posts which resolve your problem, and give a thumbs up to useful comments, articles and downloads.
I saw some similar problems when using passwords that contains "@" character, since most of those are used as tokens in XML files.
As bhawver said, try a simpler password for it :)
Regards,
Daniel Lopes de Oliveira
Endpoint Management & Mobility Architect
We recently experienced this same problem after applying the SP2 MP1 update to Altiris 7.1. Whenever we initiated a Windows deploy task, the system would boot into automation, Ghost would launch and the PC would image however any tasks after that would fail (IE the run of sysprep). I am unsure if this is the same issue you are experiencing, however here is the fix that worked for us from a Symantec support call:
Copy firm.exe from:
\Program Files\Altiris\Altiris Agent\Agents\Deployment\Task Handler\rdeploy
to
\Program Files\Altiris\Altiris Agent\Agents\Deployment\Task Handler
Once this is done, do a complete update schedule from Notification Server \ Resource Membership Update.
Here is the support article
http://www.symantec.com/business/support/index?page=content&id=TECH198111
Would you like to reply?
Login or Register to post your comment.