What are some general DAgent troubleshooting techniques?
GSS 3.x
You may need to navigate to the directory where AClient was installed or put the AClient into the Run dialogue by dragging and dropping the AClient.exe into the Run dialogue. The command is:
DAgent -remove
To remove an DAgent that has a password, please contact Altiris Support Services.
B. You can also do run the following command in the Run prompt:
DAgent -admin
This command will bring up the administrative properties of the AClient. It is possible to unhide the AClient with this switch as well. The user will be prompted for the password if one is enabled. While in the AClient properties check the Transport tab. Verify that the correct TCP/IP address of the Deployment Solution server is in there. Try changing it to the NetBIOS name of the Deployment Solution server instead. Try using multicasting as a last resort if the customer has DHCP enabled.(Typically not recommended using multicasting vs. a specific IP address.)
Problem lies with server
If all DAgent are disconnected then most likely the problem lies with the server. Usually the problem is with the Altiris DB Management Service and/or the Altiris eXpress Server. These services are located under the services area in the operating system.
You need to be able to stop and then restart the services easily. This means that if you stop either services and it takes 60 seconds to simply stop the service then this is a problem. It should normally not take over 10 seconds to stop and another 10 seconds to restart the either service.
Problem is with the services
Try using a different account to run the service under. Usually a Domain Admin account is sufficient to run the Altiris DB Management Service and a local admin account is sufficient for the Altiris Express server.
Article 172343, "Service 'Altiris Deployment Server DB Management' crashing in Ghost Solution Suite
" will help with the Altiris Deployment DB Management Service troubleshooting.
Enabling logging in the 6.x DAgent
This is a simple task. Double-click on the DAgent in the system tray and then click on the Log File tab and then enable logging. DAgent build 6.X
Usually, you will want to increase the amount of space that the log can take up, as the default amount is very small. A good amount would be 1 MB (1000 KB) to get a complete detail of any issue that might happen. Enabling logging in 5.x clients is a little tougher, as we need to modify the registry to enable logging.
The name of the registry and the key are both case-sensitive. Ensure they are named exactly as listed above. If you have multiple computers, then it is usually best to create a RIP of this registry key. The name of the log file is C:\Trace.log and will always be at the root of C drive. This log file will grow until the registry debug value is changed to 0 or deleted and the machine rebooted, so only use during the troubleshooting process.
It is generally good practice to make sure that the DAgentt connects to the Ghost Solution Suite Solution Server by MAC address vs. asset tag, serial number, or asset tag. This setting is located in the Console > tools > Options > 'Global' tab > Primary lookup key(s)
Important: Verify the AClient and Ghost Solution Suite have open port communication. Connection Closed Status on AClient.
Copmmand prompt from Ghost Solution Suite server to client and vice versa
ipconfig /flushdns
Verifying that the TCP port 402 is established and listening:
Netstat -an
The DAgent is not able to connect to GSSS\Login Failed.
Reset the "Log On As" to Admin login account instead of Local System account in the "Altiris Deployment Server DB Management DB" service