Help with installing Remote Manage.

Ron

When trying to install Remote Manage on a Windows 7 SP1 machine that has the SCCM 2012 R2 console installed, the installer encounters an error and does a rollback. I created a verbose msi log and found this error right before the rollback:


Error altering 'Cireson_Remote_Manage_App.xml'. Could not find file 'C:\Program Files (x86)\Microsoft Configuration Manager\AdminConsole\XmlStorage\Extensions\Actions\0770186d-ea57-4276-a46b-7344ae081b58\Cireson_Remote_Manage_App.xml'.


CustomAction Action1_SetRemoteManageAppPath returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)

The Remote Manage msi installs fine on a machine with no SCCM console present. We love the tool but would like to integrate it with the console. Any help is appreciated.

F_Christiansen

Hi Ron,

Yes, you are right, we discovered a problem with the installer when integrating to the ConfigMgr Console.
We have resolved the issue and produced a new installer.
Could you please download the latest installer from this url:
https://support.cireson.com/software
- scroll down to "Free Community Solutions", find "Cireson ConfigMgr Remote Manage v1.1.1606.45" and download and then retry the installation?

Best regards
Flemming Appelon Christiansen

F_Christiansen

Hi Ron,

Yes, you are right, we discovered a problem with the installer when integrating to the ConfigMgr Console.
We have resolved the issue and produced a new installer.
Could you please download the latest installer from this url:
https://support.cireson.com/software
- scroll down to "Free Community Solutions", find "Cireson ConfigMgr Remote Manage v1.1.1606.45" and download and then retry the installation?

Best regards
Flemming Appelon Christiansen

Ron

Thank you, the new installer works now with the console. I look forward to testing all the functions.

wally_mead

Glad to hear that it is working now for you Ron. Let us know if you have any further questions. And thanks for remembering to mark the answer so that others know.

And just for everyone's info, we decided to change our versioning to be more inline with what Microsoft is doing with Configuration Manager now - two digits for the year (16), two digits for the month (06), and then the version of the app (46). Those obviously are for this specific app release.