Now run the FAXCTRL.exe as the current user (psadt has a function for this)Įxecute-ProcessAsUser -Path "C:\program files (x86)\RightFax\Client\faxctrl.exe" -RunLevel "LeastPrivilege"Īfter doing this we finally got the new client to install, launch, and successfully connect to new server. HKCU\Software\Rightax Client\Collective_*YourRfServerName* HKCU\Software\Rightax Client\PrintDriver\Name HKCU\Software\Rightax Client\FUW32\Server0Name HKCU\Software\Rightax Client\FUW32\StartingServerName I used powershell to loop through and load/unload the registry hives while making the changes. Msiexec.exe /i "RightFax Product Suite - Client圆4.msi" /qn REBOOT=ReallySuppress RFSERVERNAME=*yourservername* RUNBYRIGHTFAXSETUP=2 CONFIGUREFAXCTRL=1 CONFIGUREFAXUTIL=1 NETID=2 NAMESPACE=RFAX ADDLOCAL="FaxUtil,FaxCtrl" /log "c:\logfile_path"Īfter install, kill the FAXCTRL process because it will start as System and will not work.Ĭhange these registry keys for every user profile on the device.
#RIGHTFAX DOWNLOAD FOR WINDOWS 10 INSTALL#
Install print driver with this command (I used PSADT for this package btw)Įxecute-Process -Path "rundll32.exe" -Arguments "printui.dll PrintUIEntry /ia /m "RightFax PostScript" /f $dirFiles\Prereqs\Drivers\rfps.inf /q"įinally run the Rightfax install with this command line If client was using the outlookaddin, install vstor_redist HKLM\Software\Wow6432node\RightFax Client\PrintDriver\NameĪfter uninstall completed, install prereqs before installing the new version using the MSI HKLM\Software\Wow6432node\RightFax Client\FUW32\Server0Name HKLM\Software\Wow6432node\RightFax\Install\Settings\RightFaxServername Set the new RightFax Server name in the following registry keys, BEFORE uninstall AND AFTER the new install. When the new version got installed, it was pulling information from these keys and was causing issues. Uninstalling with setup.exe left behind a random number of registry keys scattered between HKLM, HKU, HKCU and god knows elsewhere. We had to include PsExec in our wrapper script to execute the above command. However, when attempting to execute this command with MECM under the System context, it would fail. "C:\Program Files (x86)\Rightfax\setup\setup.exe" /remove /unattended=true /quiet=true/allowShutdown=true (the allowshutdown=true switch refers to shutting the rightfax services down, not the computer)
You can find the uninstallstring for Rightfax in the registry, it will say either setup.exe or msiexec /x blah blah. They had to be uninstalled using the same method in which they were installed. (newer Rightfax versions allow you to bypass the setup.exe and use the msi with RUNBYRIGHTFAXSETUP=2 switch, but not these old versions) These are the steps I had to take to get it to work-īefore older versions are uninstalled, determine if they were installed using the Setup.exe bootstrapper or the MSI. I will add my steps incase it helps somebody in the future. Update: It has been a nightmare but I believe we have it working.
#RIGHTFAX DOWNLOAD FOR WINDOWS 10 UPDATE#
Has anyone here gone through a RightFax upgrade? Any ideas or suggestions? Is it possible to programmatically update the server path for Rightfax? I have tried wrapping psexec into the package and using that to execute the commands, and it seems to uninstall the old version, but when new version is installed the server path is not updated and the application crashes until you manually update the server path. However, it does not work when running through MECM under the System context. The old clients are removed and the new one is installed and server path is updated correctly. When running my script manually it runs just fine. We have to uninstall the old versions before installing the new and it needs to be done completely silent. We are upgrading our Rightfax Clients from very old versions (9.4 and 10.6) to version 20r2.
0 kommentar(er)
