Xmanager Forum

Silent Deployment impossible on 64bit-Windows

Last post: Saturday, December 3, 2011 3:57 PM by Support, 3 reply

 
Monday, May 3, 2010 5:36 AM - NetZwerg

Silent Deployment impossible on 64bit-Windows

 
I'm trying to get XManager (and XShell) to play well with an install-management solution (WPKG in my case).

X-Manager installer cannot be run as user SYSTEM (which is the user, WPKG-Service runs as). This is a known incompatibility with InstallShield and 64bit Windows ->

The Installer .EXE unpacks the contained MSI-File to a temp directory indicated by %TEMP% - which for SYSTEM-User is below c:\Windows\system32\config\systemprofile. But on 64-bit windows the (32bit) installer gets diverted by some compatibilty layer to c:\Windows\sysWOW6432\config\systemprofile. Then the installer invokes MSI with the "original" path under system32 and fails, because the file was unpacked somewhere else.

Most installshield installers can be tamed by using the /b switch, which tells Installshield to extract the MSI somewhere else - but XManager's (and XShell's) Installer don't support this switch.

Will an Installation under SYSTEM context be supported at some time in the future? Or would it be possible to allow the /b switch and specify the Temp directory? Or is there some other solution I could try?

Program Ver. : Xmanager 3.0
Connection Method : Other
Thursday, May 6, 2010 3:39 AM - Support

Re: Silent Deployment impossible on 64bit-Windows

 
Thank you for the kind explanation about WPKG.

Currently our products are not test with WPKG. But, we will get back to you after trying out the solution.

Thank you for your patience.

---
Technical Support
Friday, December 2, 2011 7:19 AM - Prashanth

Re: Silent Deployment impossible on 64bit-Windows

 
Any update on this? I am still having problem. The log file says error code 3.
Saturday, December 3, 2011 3:57 PM - Support

Re: Silent Deployment impossible on 64bit-Windows

 
Could you attach the full log file? Please attach the reponse file and log file for that as well.

errorcode 3 means Required data not found in the Setup.iss file.


---
Technical Support