A few clients in the recent past have reported difficulty deploying Rightfax Client version 184.108.40.20670 on Windows 7 using SCCM 2012. After trying multiple methods found via web searches and using the application documentation, I had little success. I reached out to the vendor support team and found that installing the application as part of the OS task sequence will not work, as the application requires a user profile to be present on the workstation.
The next question was: how do I deploy the application as the Local System account, since I try to leverage this for all application installs? I started to look at deployment properties in SCCM 2012 and came across the following settings which installed the application as the Local System account post-deployment. Note that since we could not deploy the application via the Task Sequence; I needed to install this application post-OS deployment.
Disclaimer: I leveraged this method on Rightfax Client version 220.127.116.1170 and have NOT tested this on any other versions.
In essence, I had the application install using the following command line with the following SCCM properties and as a Required Deployment. The expected behavior was that the first time a user logged into a workstation the application would install once and be done.
Command Line = setup.exe /unattended=true /allowShutdown=true /add=”FaxUtil,FaxCtrl” /rightFaxServer=”SERVERNAME”
- Install for System as this was a install required once per workstation.
- Only when a user is logged on, this met the application criteria to have a user profile present.
- Allow users to view and interact with the program installation.