Thursday, 7 February 2013

Environment Manager Personalization Server Microsoft Office Configurations

Over the past few weeks I've been asked by a number of people to share my Personalization Server Application Configurations to speed up deployment particularly into Pilot or PoC environments. In this blog post I will share my configurations for the following products:
  • Microsoft Office 2003
  • Microsoft Office 2007
  • Microsoft Office 2010
  • Microsoft Office 2013
Now before I share anything I will say that these configurations come with no warranty and I strongly advise you test these in a non production environment to ensure they satisfy your requirements. In addition, I would highly recommend that you read my post about Global Inclusions and Exclusions before you even open these configurations.

The configurations have been created using Environment Manager 8 Feature Release 4 ( build of the console. 

The configurations can be found here...

The first step is to create your AppSense Personalization Database. Steps on how to do this are in the various product guides shipped with AppSense DesktopNow. Once you've created the database connect to the Personalization Server using the AppSense Environment Manager Console and cancel the Quick Setup wizard. 

Now using the ribbon click on the tools menu and then Import

Browse to the location that you've extracted my configuration files to and select the base configuration and click open.

At this point a summary page will be displayed. If you've already created Personalization Groups deselect this item but leave settings enabled.

If any items conflict you will be provided options. 
  • Replace will simply rip and replace the settings you had configured
  • Merge will simply add the settings after the items already configured

At this point make a note of the items configured within the FileTypeExclusions global setting which can be found in the Global menu on the ribbon bar.

By default the list should be; dll;exe;sys;pst;ost. If any additional items are added make a note of these because you will need to manually re-add them once the import completes. 

Now perform the import of the required version(s) of Microsoft Office by performing the same import steps described above. 

At this point you will receive the following warning:

The reason for this warning is because I have manually edited the global settings list to ensure only FileTypeExclusions are imported. The reason for this is because within the environment I created the configuration I am leveraging SQL replication which adds an additional item to the Global Settings which may cause instability within a non replicated environment. 

The last step is to verify the new application groups have been created and to add these to the whitelist for a Personalization group as seen in the screenshot below:

Any questions or suggestions on the templates please contact me on twitter...