Why Use Win App as a Service?
The CFP Windows App runs as an application by default. In the Windows environment, when a given user starts an application and then logs out, the application shuts down. When the Windows app shuts down, data transferred by it also stops. A solution to this is running the Windows App as a service (WaaS) rather than as an application; services continue to run after the user logs out, meaning data transfer continues as well.
Whether it is running as an app or a service, for obvious reasons the Win App will stop transferring files if the computer on which it is installed powers down.
The major difference in running the Win App as a service is that while it can access networked drives, it does not access those drives by mapped drive letters (e.g., C:/, X:/, Y:/ drive). Instead, the drives will display as they would if you were to access them off the network – typically in the format \\servername\folder. Therefore, you will need to:
- Map your drives while the Win app is running as an app
- Create the systems for those mapped drives
- Convert your Win app to running as a service. CFP will convert the mapped drives to UNC paths automatically.
Configuring the Windows App as a Service
1: Download the Windows App .msi file by clicking on the Download App button on the CFP dashboard. Click on the .msi file to install it.
2: When installation completes, register the Windows App as an app. You should see a POP display in the dashboard and turn blue. Click on the POP, click View, and confirm that the mapped drives are all listed as systems at the bottom of the screen for that POP. Building the systems may make a minute or two.
3: Right click the cloud icon in your system tray, usually in the lower right corner of your desktop, and select Settings…
4: Launch on Login should already be checked; also check the box for Run Windows as a Service.
5: The default user for running Win App as a Service is LocalSystem, which works for most systems. Select Save.
NOTE: If you have a system where you must select a different user to run the service, that user must have access to the mapped drives for the migration. This is due to the way Windows permissions work.
If you get a dialog box saying that the service started, you are all set and the Win app is running as a service.
If you get a dialog box that says the service user cannot be LocalSystem, close the error dialog and then select the Change button from the system tray pop-up.
The Services window will display. Find the Cloud FastPath Service in the list, right click and select Properties.
- In the General tab, select Automatic for Startup type.
- In the Log On tab, deselect Local System account and enter an admin-level Windows user and Windows password for the current computer.
- Click OK.
- Right click Cloud FastPath Service again and select Start to start the service.
6: Click Save on the Windows system tray pop-up and your configuration is complete.