Table of Contents
Deployment of FotoWeb Desktop using Group Policy
Table of Contents
Overview
This how-to explains the steps involved in preparing the Group Policy Deployment of the FotoWeb Desktop client software.
Before you start
In addition to the FotoWeb Desktop MSI package, the clients you distribute FotoWeb Desktop to will need Visual Studio 2010 Tools for Office Runtime and .NET Framework 4 Client Profile.
The Visual Studio Tools can be extracted and prepared for Group Policy deployment in precisely the same way as the FotoWeb Desktop package. However, the .NET Framework cannot be deployed with Group Policy and must be deployed using Windows Server Update Services (WSUS).
Preparing the FotoWeb Desktop 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. Ensure users who need access to this distribution point have Read privileges on the share.
- Download the latest version of FotoWeb Desktop. It can be downloaded by logging on to your Fotoware tenant and choosing Download Fotoware Plugins from the Tools menu (cogwheel icon).
- Run the setup program with the ‘/a’ startup parameter:
Example: FotoWebDesktop-7.0.452.3881-Setup.exe /a - This will extract the installer files to a location you specify (your distribution point).
- At the extraction point, open the CommonAppData\Fotoware\FotoWeb Desktop folder and modify the defaultSitePreferences file in a text editor or an XML-compliant editor.
This file lets you set the default host name of the FotoWeb server in the <HostName> node.
You can also define a proxy type (system, user, or none) and an optional proxy name, port, and username and password for authentication if you choose the user option.
Save the file when you've made your choices. - Using Orca (part of the Windows SDK Components for Windows Installer Developers package) or another MSI editor, change the following values in the Property table of the ‘FotoWeb Desktop.msi’ file:
FotoWebHostName: Your site name, for example, fotoweb.fotoware.com.
FWDT_INSTALLDEFAULTPREFERENCES: Set to 1 to use the connection settings you prepared in the defaultSitePreferences file. Note that http:// and any path information is omitted. - Place the package on a network share accessible to all your clients.
- Use Group Policy to install the package on client machines (see below).
Note
The Adobe Extensions are installed alongside the other components in the FotoWeb Desktop package. However, they are not enabled on the client computers, i.e. they're not added to the Adobe Extensions Manager automatically. To enable the Adobe Extensions on the client machines, you will have to manually right-click the FotoWeb Desktop tray icon and choose "Install Fotoware Extensions for Adobe CC". You may need administrative rights on the client computer to complete this task.
Preparing the Visual Studio 2010 Tools for Office package
Download Visual Studio 2010 Tools for Office Runtime. Note that there are two packages available: one for 32-bit client operating systems and one for 64-bit client operating systems. Make sure you choose the correct one.
Run the setup program with the ‘/a’ startup parameter:
Example: vstor40_x32.exe /a
This will extract the installer files to a location you specify.
Unlike the FotoWeb Desktop package, there is no need to modify the Visual Studio Tools MSI package before setting up Group Policy.
Configuring Group Policy
Note
The following procedure describes the configuration of the FotoWeb Desktop package, but the exact same procedure can be used when creating a deployment package for Visual Studio Tools for Office.
- In Administrative Tools on the server, open the Group Policy Management
- Right-click Group Policy Objects and select New.
- Enter a name, for example, FotoWeb Desktop Deployment.
- Decide whether the policy applies to computers or users. In this example, we will use Computer mode:
- Select the Group Policy Object you just created. In the bottom right panel, select Add, then click on Object Types and select Computers. Choose the domain computers to which the package should be distributed.
- Right-click on the GPO you just created and select Edit. This will open the Group Policy Management Editor.
- Expand the Computer Configuration node, then Policies, and then the Software Settings node.
- Right-click Software installation, then select New Package.
- Select the FotoWeb Desktop.msi file from the distribution point (the share where you stored the files expanded from the installer package). Make sure you access the file through its share path (typically \\servername\sharename)
- Choose the assigned deployment method.
- Highlight the Software installation node and right-click the deployment object you just created. Then select Properties.
- On the Security tab, add the groups/users that should be granted permission to install FotoWeb Desktop. They will need Read access.
- 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 no longer within the management scope.
- Finally, close the Group Policy Management Editor window. Now, it's time to link the Group Policy Object to a group of computers:
- 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.
- 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.)
- Force a Group Policy update:
- Run gpupdate on clients to force an 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]
- Run gpupdate on clients to force an 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.
For more information, see http://technet.microsoft.com/en-us/library/bb490983.aspx
Note
gpupdate will run automatically roughly every 120 minutes on domain clients. Therefore, the software will typically be installed on the next working day when users restart their computers.