Skip to main content

 

Documentation & User Guides | FotoWare

Deployment of FotoStation for Windows

Step by step guide to deploying FotoStation for Windows using Group Policy.

Before you start

In addition to the FotoStation MSI package itself, the clients you distribute FotoStation to may need Apple QuickTime to correctly identify certain file formats. However, QuickTime is optional, and this procedure does not deal with QuickTime deployment.

Preparing the FotoStation installation package

Create a distribution point

This will need to be a shared folder on a server that the clients can access to run the installer. Make sure the users who need access to this distribution point have Read privileges on the share.

Download the latest version of FotoStation

It can be downloaded from https://downloads.fotoware.com/FotoStationProWindows

Run the setup program with the ‘/a’ startup parameter:

Example: FotoStation-Setup.exe /a
This will unpack the files from the installer to a location you specify, typically the distribution point you created above. 

Prepare the 'Logon to server' feature

If you don't have a centralized configuration, you can skip this step.

To do this, you must modify the locationdata.xml file located at <DistributionPoint>\CommonAppData\FotoWare\FotoStation\locationdata.xml.

Note: FotoStation uses the FWP protocol to upload, manage and download configurations to an Index Manager server. Legacy systems where configurations are stored on a regular server share are still supported. See the Legacy section below for information on how to control this type of deployment. We strongly recommend deploying using the new scheme where configurations are managed on an Index Manager server via FWP.

locationData.xml - contents and legend:
<?xml version="1.0" encoding="utf-8"?>
<FotoWare_Settings>
    <Group name="ConfigLocation">
        <String name="locationType">FwpLogon</String>
        <Int name="showOffline">0</Int>
        <String name="logonPath"></String>
        <String name="serverUrl">IMSERVER</String>
    </Group>
</FotoWare_Settings>
locationData.xml properties and values
Property Possible values Explanation
locationType User, FwpLogon

User specifies that each FotoStation user has an individual configuration stored in his/her user profile. In this mode, leave the logonPath and serverUrl properties blank.

FwpLogon specifies that FotoStation retrieves its configuration from an Index Manager server via the FWP protocol. This value must be coupled with a valid serverURL value.

serverURL IP address or host name of
the Index Manager server where
the configurations are stored
Examples: 127.0.0.1, IMSERVER, www.mydomain.com
showOffline 0, 1

0 means that users cannot choose to work offline, and are required to log on to the server

1 means that users can choose the Work Offline option in the login dialog.
Users must first have saved a config for offline use.

For an explanation of legacy properties for logon to a configuration folder stored on an SMB share, see below.
Legacy locationData.xml - contents and legend
<?xml version="1.0" encoding="utf-8"?>
<FotoWare_Settings>
    <Group name="ConfigLocation">
        <String name="locationType">Logon</String>
        <Int name="showOffline">0</Int>
        <String name="logonPath">\\MYSERVER\Shared Data\FotoStation Logon</String>
    </Group>
</FotoWare_Settings>
Legacy locationData.xml properties and values
Property Possible values Explanation
locationType User, Logon

User specifies that each FotoStation user has an individual configuration stored in his/her user profile. In this mode, leave the logonPath and serverUrl properties blank.

Logon specifies FotoStation retrieves its configuration from an SMB file share. This property must be coupled with a valid LogonPath value.

logonPath

UNC path to the share with the configurations

Windows clients: \\servername\sharename\folder

Mac clients: /Volumes/volumename/sharename/folder)

Remember that the share has to be mounted for the Mac to find the logon folder.

If using per-user configs, leave this property blank
showOffline 0, 1

0 means that users cannot choose to work offline, and are required to log on to the server

1 means that users can choose the Work Offline option in the login dialog.
Users must first have saved a config for offline use.

Edit the FotoWare FotoStation.msi file with an MSI editor 

Change the following values in the Property table of the FotoWare FotoStation.msi file:

 

use_location_file.jpg


Set the USE_LOCATION_FILE parameter to 1 to distribute the locationdata.xml file. This way the FotoStation clients will get their configuration from the location specified in the locationdata file. 

Configure licensing

Alternative 1: If you are using a single product key with several activations. (If you are using a license server, skip this step.)

In the Property table in the msi file, locate the FWLICENSEKEY property and paste your license key there:

 

use_license_key.jpg


Alternative 2: If you are using a license server.

In the Property table in the msi file, locate the FWLICENSESERVER property and type in your host name preceded by an @ character, like this:@licenseserver. If the license server is configured to use another port, use this format: 2000@licenseserver. (Replace 2000 with whatever port number you have configured in your license file.)

Learn more about activation with a license server.

use_license_server.jpg

 

Save the msi file before continuing to configure Group Policy

Configuring Group Policy (Windows Server 2008)

Note: The below procedure describes configuration of the FotoStation. Although the screenshots depict FotoWeb Desktop deployment, the steps involved are completely identical.

 

1. In Administrative Tools on the server, open the Group Policy Management

 

2. Right-click Group Policy Objects and click on New

 

3. Type in a name - e.g. FotoStation Deployment (screenshot below)

 

fsgp1.jpg

 

4. Now, decide whether the policy applies to computers or users. In this example we will use Computer mode:

 

5. Click on the Group Policy Object you just created. In the right bottom panel, click on Add and then click on Object Types and select Computers. Then choose the domain computers the package should by distributed to. (Screenshot below)

 

fsgp2.jpg

 

6. Next, right-click on the GPO you just created and select Edit. This will open the Group Policy Management Editor

 

7. Now, expand the Computer Configuration node, then expand Policies, then the Software Settings node. (Screenshot below)

 

fsgp3.jpg

 

8. Right-click on Software installation and select New Package

 

9. Select the FotoWare FotoStation.msi file from the distribution point (the share where you stored the files expanded from the installer package).

Important: Make sure you access the file through its share path (typically \\servername\sharename)

 

10. Choose Assigned deployment method.

 

11. Highlight the Software installation node and right-click the deployment object you just created. Then select Properties

 

12. On the Security tab, add the groups / users that should be granted permission to install FotoStation. (They will need read access)

 

13. Go to the Deployment tab and make sure to check Uninstall this application when it falls out of the scope of management. This way, the software will be uninstalled from computers that are taken out of the management scope. (Screenshot below)

 

fsgp4.jpg

 

14. Finally, close the Group Policy Management Editor window. Now, it's time to link the Group Policy Object to a group of computers:

a. In the Group Policy Management window, right-click the computer or OU that you want to apply the GPO to and choose Link an Existing GPO, then choose the deployment package that you would like to distribute.

 

fsgp5.jpg

 

b. Now you should open the Active Directory Users and Computers program from Administrative tools and move any computers that you want to distribute the software package to, into this group. (Drag them from the Computers node into the group that you created in Group Policy Management.)

 

15. Force a Group Policy update:

Run gpupdate on clients to force update. This will refresh local and Active Directory-based Group Policy settings. Normally, it should not require additional options - just run gpupdate from the command prompt.

Command syntax:

gpupdate [/target:{computer|user}][/force][/wait:value][/logoff][/boot]

More information can be had at http://technet.microsoft.com/en-us/l.../bb490983.aspx

Note: gpupdate will run automatically roughly every 120 minutes on domain clients. Hence, the software will typically be installed on the next working day when users restart their computers.