Jump to content

Securing personal files and setting, some brainstorming


Mr.John_Doe

Recommended Posts

Hello,

we have experimentet with the new imagex-technology from Microsoft. So we thought about a way to transfer most of user-specified settings and files from one system to another.

We often has the problem, that some of our employees become new notebooks or pc. They want to take their own settings from the old system to the new. Now we search a way how we can easily and almost automatic can collect and transfer all userdata from one host to another.

Unfortunatly we don't have an active directory or so. the most work in some novell-supportet peer-to-peer-network.

Does anyone have an idea how we can do this.

One thinking is to secure the profilefolder with imagex and transfer them to the new pc in a precreatet profile with the same name. But how is it with the ntfs-rights?

So maybe we can do some brainstorming here...

Link to comment
Share on other sites


This is what the User State Migration Tool was designed to do. :)

Microsoft® Windows® User State Migration Tool (USMT) version 3.0.1 migrates user files and settings during deployments of Microsoft Windows XP and Windows Vista. You can use USMT to perform unattended migrations and to migrate files and settings for computers with multiple users. Also, with USMT you have the ability to encrypt and compress the store. USMT 3.0.1 is intended for administrators who are performing automated deployments.

This tool includes two command-line tools named ScanState and LoadState. ScanState creates an intermediate store that contains the user files and settings from the source computer. LoadState restores these files and settings to the destination computer. USMT 3.0.1 also has three default migration rule (.xml) files named MigApp.xml, MigUser.xml, and MigSys.xml. You can alter the default .xml files and you can also create customized .xml files. Depending on what you want to migrate, you can specify all or none of the default .xml files on the command line. The entire migration process is controlled by the .xml rules, which you can modify, and logic that is built into the tool. When using USMT for automated migration, in almost all cases, you should modify the migration .xml files for your unique situation.

Edited by nmX.Memnoch
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...