NOTE: This issue should no longer apply to 9.6 installations
When installing the remote console you get a failure on the "Installing the Remote Console" step.
This can occasionally show up when upgrading a core server as well, but it will be on the "Upgrading the Core Server" step.
The resolution is the same.
In the log you will find something similar to the below
MSI (s) (0C:CC) [10:14:45:217]: Doing action: LDCopyApplyHotFixLocally
Action ended 10:14:45: LDWriteRemoteRegKey. Return value 1.
MSI (s) (0C:CC) [10:14:45:217]: Note: 1: 2235 2: 3: ExtendedType 4: SELECT `Action`,`Type`,`Source`,`Target`, NULL, `ExtendedType` FROM `CustomAction` WHERE `Action` = 'LDCopyApplyHotFixLocally'
MSI (s) (0C:E4) [10:14:45:218]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI8247.tmp, Entrypoint: LDCopyHotFixLocally
Action start 10:14:45: LDCopyApplyHotFixLocally.
HOTFIX: Failed to copy HotFix helper file D:\LANDeskSoftware950\landesk\\SetupFiles\ApplyHotFix.exe to C:\Users\<User>\AppData\Local\Temp\ApplyHotFix.exe
CustomAction LDCopyApplyHotFixLocally returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
Cause: This is caused when the install finds a Hotfix directory and trying to copy the ApplyHotFix.exe
Normally it will be found in either the user temp directory or on the root of c:\
You can do a search for hotfix and find where we may be seeing the folder.
You may need to do the search from command line as the windows search is not always reliable.
From a command prompt cd to the root of c:\
Run the command c:\> dir /s hotfix
Solution: Once you find the Hotfix directory, you can temporarily rename the folder, or delete it if it is no longer needed and run the install again.
This time the install should complete and you can name the folder back if needed.