Unable to install AClient via Remote Agent Installer
Last Updated April 18, 2006
When trying to install AClient using the Remote Agent Installer utility, one of the following errors are returned:
1) An error occurred launching AClient.exe. Windows reported "Logon failure: unknown user name or bad password."
2) The interface is unknown.
3) No network provider accepted the given network path.
The Remote Agent Installer requires Registry access on computers it installs AClient to. In order to have access to the registry of those computers, the Remote Registry Service must be enabled and the LOCAL SERVICE user account must have read access to the
HKLM\System\CurrentControlSet\Control\SecurePipeServers\winreg registry key.
Possible causes for error messages:
1) The domain name is case sensitive.
2) Port 402 is being blocked.
3) Simple File Sharing is enabled.
4) Firewall enabled on client machine. Virus protection software can also cause similar problems.
1) Try specifying the domain name in all capital letters.
If not on the Domain:
It should then authenticate correctly.
2) Layer 3 switches and routers can block or close port 402. Verify that this port is open with a utility such as TCPView from
3) Open My Computer and click on Folder options > View from the Tools pull-down menu. Scroll to the bottom of the list and uncheck the option Use simple file sharing (for Windows* XP clients).
4) Disable client computer Firewall and Virus Protection.
For ALL problems with Remote Agent Installer, test the following:
A. Test For Network Accessability
Use the Ping command from a DOS command window by using the "ping -a <client IP address> /402 from the Deployment Server. If DNS is working properly, the "-a" should resolve the Computer Name to be returned as follows:
Pinging <Computer Name> [ip address] with 32 bytes of data.
[Failure indicates a DNS issue. For information on how to flush out old DNS entries on your computer, see article 22374.]
B. Local Security Policy
On a target client computer, open the Local Security Policy editor from the Windows Control Panel | Administrative Tools.
Navigate to Local Policies\Security Options.
Change "Network Access: Sharing and Security Model for local accounts" to Classic.
C. Test For Local C$ Access
From a client computer, go to Start > Run, type in \\Computername\C$ and press ENTER.
This will then prompt the user for the credentials to access the drive. Enter in the credentials that are being used to push out the AClient.
If the credentials do not access the C$ drive, then use the token "%COMPUTERNAME% \Administrator" to access the C$ drive.
The next step is to use the "%COMPUTERNAME% \Administrator" to push out the AClient.
D. Test For Remote C$ Access
From the Deployment Server, go to Start > Run, type in " \\ClientComputerName\C$" and press Enter.
This will then prompt the user for the credentials to access the drive. Enter in the credentials that are being used to push out the AClient. [If this results in an error, then this account does not have Remote Registry rights to this computer or the Remote Registry service is not running.]
E. Test For Registry Entry Creation Rights
From the Deployment Server, go to Start > Run, type in "Regedit" and press return to launch the Registry editor.
From the File pull-down menu, choose "Connect Network Registry..." and choose the target client computer. [If this action fails, the Remote Registry Service is probably not enabled on the client machine.]
In the registry of the target client computer, navigate to HKEY_LOCAL_MACHINE | SOFTWARE and right-click on Altiris.
Choose New > Key. [If this action fails, there is no rights to the registry.]
F. Test for Remote Services Access
From the Deployment Server, go to Start > Run and type in "services.msc" to launch the Services management utility.
Right click on "Services(Local)" and choose "Connect to another computer...".
Choose the target client computer to connect to.
Restart a service on the client computer. [If this action fails, the Remote Services are not running or functioning.]
If all tests complete without errors, the Remote Agent Installer should have no problems pushing the aclient the remote client computer.
Applies To Deployment Solution 6.1 through 6.9
Imported Document ID: TECH10968
Subscribing will provide email updates when this Article is updated. Login is required to Subscribe