Home > Altiris Error > Altiris Error Installing Remote Installer Service

Altiris Error Installing Remote Installer Service

On the NS console, on the Configuration tab on the "Altiris Agent INstallation" page, I have "Starting 'Altiris Agent install service'" message for the status - which does not change. Sample log errors: Process: aexsvc.exe (280) Thread ID: XXXX Module: AltirisNativeHelper.dll Source: Altiris.NS.Utilities.RemoteServiceMgr Description: Failed to copy the eXpress Client service to \\XX.XX.XX.XX\ADMIN$\AeXSWDInstSvc.exe. If you feel you are in need of support for a Microsoft product, please go to our technical support site at support.microsoft.com.   Error codeValueDescription ERROR_SUCCESS0The action completed successfully. Contact your support personnel. check over here

ERROR_ROLLBACK_DISABLED 1653Could not perform a multiple-package transaction because rollback has been disabled. Troubleshooting 1603 MSI Error As discussed, The 1603 error code is mostly returned when any action fails during an installation on Windows, and most commonly it indicates that one of the Retrieved 2012-07-03. ^ Unable to Create Windows 2000 Server Image on RIS Server prior to SP3 ^ Service overview and network port requirements for the Windows Server system Microsoft Inc. ^ Wikipedia® is a registered trademark of the Wikimedia Foundation, Inc., a non-profit organization. http://www.symantec.com/connect/forums/altiris-agent-not-installing

Exit Safe Mode and try again or try using System Restore to return your computer to a previous state. KakashiYP, Apr 16, 2007 #6 Asset Guy New Member Problems installing Altiris Agent (push) over SSL I see this is an old post but I'm having a fairly similar issue. Contact your support personnel. Remote Installation Service utilizes UDP port 4011[3] to provide clients the contents of each page the OS Chooser displays.

This is because the DNS guy here is just now correcting the DNS entry for \\Altiris1 (it use to point to a different IP address - if I go to a I built it, so I know best how to fix it. 3. This indicates that short file name creation is enabled. RIS is used to create installation images of operating systems or computer configurations, which can be used to demonstrate the installation process to users whose machines have been granted access to

See ifDNS is working properly by pinging the client computer. The primary benefit of remote replication is reduced cost and complexity of managing multi-site organizations. [4] See also[edit] Windows Deployment Services Disk Image List of Microsoft Windows components References[edit] ^ "Remote Create a SymAccount now!' Altiris Agent push errors TECH13407 January 20th, 2014 http://www.symantec.com/docs/TECH13407 Support / Altiris Agent push errors Did this article resolve your issue? https://support.symantec.com/en_US/article.TECH13407.html Newer Than: Search this thread only Search this forum only Display results as threads Useful Searches Recent Threads More...

This type of change works great when the custom action is doing "unnecessary checks" for desktops in your environments. A RIPrep image can contain the operating system and applications. ERROR_UNKNOWN_PATCH1647The patch is not applied to this product. The Remote Installation Server doubles as a proxy DHCP server to provide Boot Server and File name instructions to clients.

Contact the application vendor to verify that this is a valid Windows Installer package. this Translated Content This is machine translated content Login to Subscribe Please login to set up your subscription. History[edit] Remote Installation Services was introduced with Windows 2000 as an optional component when installed on Windows 2000 Server. ERROR_INSTALL_REMOTE_PROHIBITED1645Windows Installer does not permit installation from a Remote Desktop Connection.

Installation of this version cannot continue. check my blog I am attempting to push the Agent from NS installed with SSL. The following is the probable list of known causes for this error to occur: Short file name creation is disabled on the target machine. This problem can typically be solved by rebooting the computer Process: aexsvc.exe (280) Thread ID: XXXX Module: AltirisNativeHelper.dll Source: Altiris.NS.Utilities.RemoteServiceMgr Description: Failed to copy the eXpress Client service to \\XX.XX.XX.XX\ADMIN$\AeXSWDInstSvc.exe.

This documentation is archived and is not being maintained. ERROR_INSTALL_SOURCE_ABSENT1612The installation source for this product is not available. The computer does not have a status of "active" in the console. this content I then made sure the agent on the NS got the updated policy.

I'm using a Domain Admin account as the account that runs the deployment and we don't have any routers between the client and server - all the same subnet.... ERROR_INSTALL_SUSPEND1604Installation suspended, incomplete. I once again attempted the install on the remote machine and in the console, I get the message Starting 'Altiris agent install service' and it does nothing after that The agent

Available beginning with Windows Installer version 3.0.

This error code is returned if the user chooses not to try the installation. Verify that the package exists and is accessible, or contact the application vendor to verify that this is a valid Windows Installer package. Thanks! ERROR_INSTALL_PACKAGE_OPEN_FAILED1619This installation package could not be opened.

Style Altirigos Contact Us Home Top RSS Forum software by XenForo™ ©2011 XenForo Ltd. Note the values listed for TEMP and TMP, and delete all files in those locations. ERROR_UNKNOWN_PRODUCT1605This action is only valid for products that are currently installed. have a peek at these guys Solution At the computer where you want to install the Altiris Agent: Verify that the Admin$ share defined and accessible.Right-click the My Computer icon andclick Manage.

ERROR_PATCH_REMOVAL_UNSUPPORTED1646The patch package is not a removable patch package. Sometimes, I would get lucky and even "work around" the msi defect by leaving the custom action commented out. I have a PC with about 10 of them. Step 1: Generate a verbose log file named msi*.log in the %temp% directory the next time the setup package is executed. (Click here to know more ways to generate log).