Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Task failing after PXE boot

Created: 28 Jul 2012 | 4 comments

I am working in a mixed OS enviroment.

1 domain controller not hardened runnning W2K8 R2, 1 Altiris server running DS 7.1 SP1 MR1a

I am PXE boot an RHEL 5.8 box and it gets a DHCP address fine and waits for intructions. I then give it a task to reboot to production to test.

Then I look in the aex-client.log and notice the POST to my server failed. Another error shows failed to contact the task server.

When I review the audit logs on windows 2008, I see that there is a windows security failure event ID 4625 logon type 3 in the logfile.

Source is my admin account using a null sid

The reason is unknown username or bad password. The account I am using is a domain account and does have admin rights on the altiris DS 7.1 machine.

the source network address is the linux box running RHEL 5.8

Any ideas?

Any help would be greatly appreciated.

After a few minutes, the attempts to run the task, locks out my admin account

Comments 4 CommentsJump to latest comment

shailesh_mali@symantec.com's picture

Could you see ClientRebootTo.log file on client machine...

If this file has been generated then it might be DS plugin specific issue.... and if not then we need to troubleshoot this issue for ULMAgent.

I am not sure what do you mean by ... After a few minutes, the attempts to run the task, locks out my admin account

Are you not able to run task on any client now ?  or it specific to RHEL5.8 client ?

DerekWarner's picture

The redhat machine PXE boots, then ULM agent registers and gets a machine GUID.

I then create a simple task to reboot to production to test the communication from client to server.

When I do so, and execute the task. The redhat machine's aex-client.log shows that it failed to POST http://name of server:80/name of server/ClientTaskServer/Gettasks.apx

It appears it cannot get its task from the altiris machine.

When I look at the windows logs I see that there is a windows security failure event ID 4625 logon type 3 in the logfile.

Source is my admin account using a null sid

The reason is unknown username or bad password. The account I am using is a domain account and does have admin rights on the altiris DS 7.1 machine.

If I retry this task multiple times, then the account used for this process gets locked out. I have set a policy on the domain to lockout after 3 invalid attempts.

V/R

DerekWarner's picture

It appears from the windows logs that the username the redhat client is using is ok but the password is incorrect. Is there a way to refresh the username and password ALTIRIS is using ? maybe somehow the password was changed but altiris is still using an old password?

shailesh_mali@symantec.com's picture

If you are running task in PXE then you need not have to enter RHEL username or password to run task.

One you are in PXE you are in complete different environment than it's base OS which  doesn't need username/password ( you can imagine a bare metal booted into PXE... you cannot set password for it ! )

I guess you are going in wrong direction.

It could not be about RHEL password... Make sure you have not changed NS password recently if so then try creating new preboot for Linux PXE.