Dear All, Lately I've been using PsExec. I use it to copy some NSIS exe installers to remote machines and execute them. The default remote path of these installers seems to be %windir%\system32. Is there a parameter available to change this to something else? I ask because on 64bit Windows systems you can't execute NSIS installers from the system32 directory, it will throw an error. Any advice would be greatly appreciated! Thanks a bunch.

Hi, Based on my research, PsExec works on 64bit Operating Systems. NSIS 2.26 or above supports for installation on Windows x64. Please ensure that you are executing NSIS 2.26 version or higher. BTW, you can post in NSIS forums for a better assistance. Please Note: Since the website is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information. Best Regards Dale Qiao TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.comPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi, As this thread has been quiet for a while, we assume that the issue has been resolved. At this time, we will mark it as ‘Answered’ as the previous steps should be helpful for many similar scenarios. If the issue still persists, please feel free to reply this post directly so we will be notified to follow it up. You can also choose to unmark the answer as you wish. BTW, we’d love to hear your feedback about the solution. By sharing your experience you can help other community members facing similar problems. Thanks for your understanding and efforts. Best Regards Dale Qiao TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.comPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

hi, please note thai helped me in order to solve my problem. Bye Carlo If you use the -c option, the file will always be copied into the real system32 folder, as the PsExec service runs in native mode (i.e. 64bit). You need to run a script, checking if running on x64, and then changing the working dir before copying and running anything else: @echo off if exist %WinDir%\Sysnative cd /d %WinDir%\SysWow64 copy \\server\share\NSIS.exe . NSIS.exe Start this script without copying: psexec \\remotePC cmd -c \\server\share\instNSIS.cmd

hi, please note thai helped me in order to solve my problem. Bye Carlo If you use the -c option, the file will always be copied into the real system32 folder, as the PsExec service runs in native mode (i.e. 64bit). You need to run a script, checking if running on x64, and then changing the working dir before copying and running anything else: @echo off if exist %WinDir%\Sysnative cd /d %WinDir%\SysWow64 copy \\server\share\NSIS.exe . NSIS.exe Start this script without copying: psexec \\remotePC cmd -c \\server\share\instNSIS.cmd Thanks for your update. Best Regards Dale Qiao TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.comPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi this issue doesnt just occur with the NSIS driver. I'm having the same issue running any 32 bit app on a 64 bit server. For instance Im pushing the FEPInstaller with PSEXEC but since it is landing in System32 it cannot execute. Ive tried using the -w switch thinking that might help but without success. A work around would be great. The only other thing I have been able to do is use Winrar to create a 64bit self extracting rar and install it that way but I would prefer to keep things simple.