locked
MIgrating office customizations from local install to virtual version

    Question

  •  

    We are evaluating the prospect of giving our users a fully virtual office suite.  However one of the stumbling blocks is how do we move our users existing customizations (templates, signatures, etc..) from their local computers, into the virtual office, so that the transition is 'transparent' to them..or as close to it as possible? 

     

     

    Monday, November 17, 2008 5:51 PM

Answers

  • If you exclude a registry key or file from the App-V package, as Kalle suggested, and the application requires them to do it's job correctly, the settings would need to exist locally... because it would goto the native registry on the device if the files/keys are not found in the package.
    Next to that, the custom settings would only be available on that specific device... not on any other.

    If you mean migrating existing custom settings from a local installed application to an App-V package, then the anwser is: No, not possible.
    When the user gets the App-V package after the local application has been uninstalled, the custom settings would have to be re-configured by the user.

    If you mean virtualizing custom settings from the application (App-V or local) then a solution like Immidio Flex Profiles, AppSense Application Manager or RES Workspace Manager would be a great help for this. This is also enable the user to get the custom settings when he/she logs on to another device (roaming users).

    Tuesday, April 12, 2011 8:56 AM
  • Also see this blog post: http://blogs.technet.com/b/deploymentguys/archive/2011/06/10/migrating-user-settings-from-office-2003-to-a-sequenced-version-of-office-2010-running-under-app-v.aspx

    This forum post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.
    Friday, July 08, 2011 9:21 AM

All replies

  • You might be able to use pre-launch scripts to migrate a users current settings to the virtual environment.

    Be aware though that a fully virtualized office suite might give you some issues when your applications are integrating into the Office suite.

    Sunday, November 23, 2008 8:00 PM
  • As I think Office stores those customizations into user's profile, maybe you could try to make sure virtualized Office doesn't have same directories as VFS virtualized in the package (masking local ones)?

     

    br,

    Kalle

    Wednesday, December 10, 2008 7:27 AM
  • If you exclude a registry key or file from the App-V package, as Kalle suggested, and the application requires them to do it's job correctly, the settings would need to exist locally... because it would goto the native registry on the device if the files/keys are not found in the package.
    Next to that, the custom settings would only be available on that specific device... not on any other.

    If you mean migrating existing custom settings from a local installed application to an App-V package, then the anwser is: No, not possible.
    When the user gets the App-V package after the local application has been uninstalled, the custom settings would have to be re-configured by the user.

    If you mean virtualizing custom settings from the application (App-V or local) then a solution like Immidio Flex Profiles, AppSense Application Manager or RES Workspace Manager would be a great help for this. This is also enable the user to get the custom settings when he/she logs on to another device (roaming users).

    Tuesday, April 12, 2011 8:56 AM
  • Also see this blog post: http://blogs.technet.com/b/deploymentguys/archive/2011/06/10/migrating-user-settings-from-office-2003-to-a-sequenced-version-of-office-2010-running-under-app-v.aspx

    This forum post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.
    Friday, July 08, 2011 9:21 AM