Some good user migration tool/software to recommend? (W2K -> WXP)

  • Thread starter Thread starter Zorpetus
  • Start date Start date
Z

Zorpetus

In our organization we are about to receive new workstations for all
users (approx. 120 workstations).

Currently we are using Windows 2000 SP4 but with the rollout of the new
workstations we would like to move to Windows XP SP2.

All current workstations are networked into a single AD (domain) and we
currently use MS Outlook in corporate mode (all mail is on the Exchange
Servers).


Problem:
======

Of course, problem is how to time-efficiently migrate 120 users to new
workstations and to keep:

a) all their files (MS Office related) that they have locally stored on
workstation (there is C: partition reserved for "system" use, and users
are not supposed to write on it, but nothing is preventing them storing
files on C: drive... and D: drive - reserved for their private data. ).
MyDocuments is redirected to a folder with the same name on the D:
drive in case we need to re-Ghost the C: partition - but, for example
we managed to find .PST files on C: drive (very long path...) as a
result of users playing with "auto archive" in MS Outlook. :(

b) all settings like Desktop, icons, shortcuts, mapped drives etc.

c) Cookies, Favorites etc.

d) regional settings / keyboard settings (additional keyboards)

e) optionally drivers for their currently installed "not of box"
printer and scanner drivers (as those in most cases are compatible with
Windows XP).

f) Sorting rules (and all other rules in MS Outlook), signature in MS
Outlook etc.

g)... probably I also forgot something :-)


Anyway, I've seen Microsoft UserState Migration Tool (USMT) whic is
designed for IT administrators in performing large deployments of
Windows XP Professional in a corporate environment - it looks great
(and its free) - but it can not copy everything that I need (it seems).
For example it can not search (or I haven't seen it) the entire HDD (or
C: drive, as entire D: drive would be copied anyway) for "lost", yet
important .doc, .xls, .ppt, .PST... files...
(by the way, does USMT has problems running in user mode?)

Finally, if there is some other third party (commercial) solution that
is better than USMT - it would be great to know about it! :)

Also, what is best scenario to perform such volume migration? Bring a
new workstation next to users old worstation, copy everything to some
external USB HDD, perform USMT (or alternative), save settings, connect
monitor, keyborad, mouse and peripherals to a new workstation, start
it, load USMT (or alternative) settings from USB HDD, and copy all
other data back? Or?

Any real-life experience tip is more than appreciated!


Thank you very much in advance!
 
In
Zorpetus said:
In our organization we are about to receive new workstations for all
users (approx. 120 workstations).

Currently we are using Windows 2000 SP4 but with the rollout of the
new workstations we would like to move to Windows XP SP2.

All current workstations are networked into a single AD (domain) and
we currently use MS Outlook in corporate mode (all mail is on the
Exchange Servers).


Problem:
======

Of course, problem is how to time-efficiently migrate 120 users to new
workstations and to keep:

a) all their files (MS Office related) that they have locally stored
on workstation (there is C: partition reserved for "system" use, and
users are not supposed to write on it, but nothing is preventing them
storing files on C: drive... and D: drive - reserved for their
private data. ). MyDocuments is redirected to a folder with the same
name on the D: drive in case we need to re-Ghost the C: partition -
but, for example we managed to find .PST files on C: drive (very long
path...) as a result of users playing with "auto archive" in MS
Outlook. :(

b) all settings like Desktop, icons, shortcuts, mapped drives etc.

c) Cookies, Favorites etc.

d) regional settings / keyboard settings (additional keyboards)

e) optionally drivers for their currently installed "not of box"
printer and scanner drivers (as those in most cases are compatible
with Windows XP).

f) Sorting rules (and all other rules in MS Outlook), signature in MS
Outlook etc.

g)... probably I also forgot something :-)


Anyway, I've seen Microsoft UserState Migration Tool (USMT) whic is
designed for IT administrators in performing large deployments of
Windows XP Professional in a corporate environment - it looks great
(and its free) - but it can not copy everything that I need (it
seems). For example it can not search (or I haven't seen it) the
entire HDD (or C: drive, as entire D: drive would be copied anyway)
for "lost", yet important .doc, .xls, .ppt, .PST... files...
(by the way, does USMT has problems running in user mode?)

Finally, if there is some other third party (commercial) solution that
is better than USMT - it would be great to know about it! :)

Also, what is best scenario to perform such volume migration? Bring a
new workstation next to users old worstation, copy everything to some
external USB HDD, perform USMT (or alternative), save settings,
connect monitor, keyborad, mouse and peripherals to a new
workstation, start it, load USMT (or alternative) settings from USB
HDD, and copy all other data back? Or?

Any real-life experience tip is more than appreciated!


Thank you very much in advance!
Click to expand...

I'd implement roaming profiles (before moving workstations). My boilerplate
is below.
If your company has a policy stating that all mail is to be kept in the
Exchange mailbox, and no PST files are to be supported, don't move them at
all. And that's a good policy to have in place, btw.

For the drivers - you'll need to reinstall them, most likely.

General tips:

1. Set up a share on the server. For example - d:\profiles, shared as
profiles$ to make it hidden from browsing. Make sure this share is not set
to allow offline files/caching!
2. Make sure the share permissions on profiles$ indicate everyone=full
control. Set the NTFS security to administrators, system, and users=full
control.
3. In the users' ADUC properties, specify \\server\profiles$\%username% in
the profiles field
4. Have each user log into the domain once from their usual workstation
(where their existing profile lives) and log out. The profile is now
roaming.
5. If you want the administrators group to automatically have permissions to
the profiles folders, you'll need to make the appropriate change in group
policy. Look in computer configuration/administrative templates/system/user
profiles - there's an option to add administrators group to the roaming
profiles permissions.

Notes:

* Make sure users understand that they should never log into multiple
computers at the same time when they have roaming profiles (unless you make
the profiles mandatory by renaming ntuser.dat to ntuser.man so they can't
change them). Explain that the
last one out
wins, when it comes to uploading the final, changed copy of the profile.

* Keep your profiles TINY. Redirect My Documents; usually best done to the
user's home directory on the server - either via
group policy (folder redirection) or manually (far less advisable). If you
aren't going to also redirect the desktop using policies, tell users that
they are not to store any files on the desktop or you will beat them with a
stick. Big profile=slow login/logout, and possible profile corruption.

* Note that user profiles are not compatible between different OS versions,
even between W2k/XP. Keep all your computers. Keep your workstations as
identical as possible - meaning, OS version is the same, SP level is the
same, app load is (as much as possible) the same.

* Do not let people store any data locally - all data belongs on the server.

* The User Profile Hive Cleanup Utility should be running on all your
computers. You can download it here:
http://www.microsoft.com/downloads/...6D-8912-4E18-B570-42470E2F3582&displaylang=en
 
I'd implement roaming profiles (before moving workstations). My boilerplate
is below.
Click to expand...

Unfortunatelly, my organization is spread among 3 different buildings
in the city, and we use frame relay for interconnection.

And users do have tendency (need) to work in one building in the
morning and in the other on in the afternoon. In order to fight against
slow frame relay links we are using OWA internally for those "roaming"
users, but I am afraid that implementation of roaming profiles in our
enviroment, atlough it could be done, would be too complicated for
users (mostly older people who don't like any change, even for the
better!) and real night-mare (for me :-)
 
In
Zorpetus said:
Unfortunatelly, my organization is spread among 3 different buildings
in the city, and we use frame relay for interconnection.
Owie.

And users do have tendency (need) to work in one building in the
morning and in the other on in the afternoon. In order to fight
against slow frame relay links we are using OWA internally for those
"roaming" users, but I am afraid that implementation of roaming
profiles in our enviroment, atlough it could be done, would be too
complicated for users (mostly older people who don't like any change,
even for the better!) and real night-mare (for me :-)
Click to expand...

I think you're right....but you're going to have problems anyway, to be
honest. I'm presuming you have local DCs in each location - make each one a
GC as well, and use Outlook 2003 in cached mode using RPC over HTTP if at
all possible, for your clients. Use Folder Redirection (to the server), and
perhaps also DFS.

Better still, look into Terminal Services or Citrix (hosted in the main
office) instead of a local login in each office. This is a lot more
efficient in terms of centralization, bandwidth, and administration.
 
Back
Top