Thursday, 12 June 2014

AppSense University 2014 Collateral

AppSense University 2014 Collateral

This blog post contains links to the collateral used during my AppSense University 2014 presentation on Profile Migrations.

Slides

Slide deck

Sample Configurations

Migration Configuration Examples

DataNow ADMX

DataNow ADMX

Any questions please feel free to contact myself of your account manager and I will get back to you as soon as I can.

Richard

Tuesday, 3 June 2014

Simplifying Windows Migrations using ImportData

AppSenseSpecial, Helper Applications, Migrate Mode, EMPFileUtil and EMPRegUtil are names of a few of the tools / techniques available to AppSense Engineers looking to configure migrations from a local or roaming user profile into AppSense Environment Manager.

Each of the techniques above has its pro's and con's and use cases on where you would want to implement this. For example, if a customer wasn't looking to deploy the Environment Manager Agent to a legacy estate but still wanted to import crucial file and registry settings for applications like Office or Internet Explorer I would simply create a logoff script to export the data and use the helper applications method (described in a previous post - http://uvarchitect.blogspot.co.uk/2013/01/using-appsense-environment-manager-to.html) to migrate these settings.  If a customer was deploying the Environment Manager Agent I could use AppSenseSpecial or even Migrate Mode to import these settings into the AppSense Environment Manager Database. 

Each of these methods took time to identify the settings required, configure the necessary actions and then perform the migration. That was until recently... Landon Winburn has created an even easier and painless way of performing migrations... Enter ImportData.  

Sunday, 1 June 2014

Exporting Registry and Folder Items from the Personalization Server Database

Update (03/06/2014): A third method for exporting settings has been added to the article below

AppSense are often described by competitors as locking you in to their technology because of their reliance on the Microsoft SQL Server platform. A data jail for lack of a better term. I've lost count of the number of times I've heard this from prospective customers and frankly this is not true.

Before I get into the detail we need to take a step back in time...

AppSense launched the Personalization Server back in 2008 when it released AppSense Environment Manager 8.0. The reasons for introducing this Microsoft IIS based service include the fact that a properly designed 3-tier solution will almost always be more scalable than a legacy 2-tier solution and having user settings stored within a database meant searching and reporting on the data was significantly quicker. It also meant that archives (or snapshots to some) could be taken easily on demand by simply called a stored procedure either from the AppSense Personalization Server GUI or through Microsoft SQL Server Management Studio.

Before the release of the Personalization Server, AppSense were however providing user personalization capabilities to a number of customers around the globe through the use of registry hiving and folder copy actions using Environment Manager 7.