Migration from the "N" word...

Migration from the "N" word...

Post by SmVmZiBTbW » Wed, 29 Mar 2006 23:55:02


I've installed and configured a new Windows Server 2003 Enterprise Edition
and am ready to move away from the "N" word and standardize on Microsoft.

Here's my problem...I currently have 125 workstations that each have their
own unique logins, desktop settings, wallpaper, screensavers, software, etc.

Every time one of the users of the aforementioned machines logs into the new
domain, they lose the "personalization" of their workstation (as mentioned
above).

Is their any way to "copy" their existing profile from the workstation to
the server, so that when they log into the domain, they will not "see" any
difference from what they're used to?

Thanx.
 
 
 

Migration from the "N" word...

Post by Herb Marti » Thu, 30 Mar 2006 02:11:54


Yes. You can JUST COPY it and get most of the stuff.

Or you can use USMT (User State Migration Tool -- free from
MS site) to get pretty much everything.

Only problem with these solutions is that they are somewhat
labor intensive, but you could write a batch file (or two.)

--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.yqcomputer.com/
[phone number on web site]

 
 
 

Migration from the "N" word...

Post by SmVmZiBTbW » Thu, 30 Mar 2006 05:47:03

Okay.

Got the hang of the USMT tool and how it works as far as creating the file
from the workstation in question. However, now that that is done, how do I
implement that file (created by usmt) on the server?

Thanx again.
 
 
 

Migration from the "N" word...

Post by Herb Marti » Thu, 30 Mar 2006 07:00:05


You "scanstate" on the source machine (you
seem to have figured that out) and you "LoadState"
on the target-destination machine.


--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.yqcomputer.com/
[phone number on web site]
 
 
 

Migration from the "N" word...

Post by v-jason » Thu, 30 Mar 2006 11:49:06

ello,

Thank you for your post!

You may refer to the following method.

How to use the same local profile when the workstation joins the new domain
and have the same user ID in the new domain.

1. Log on to the workstation as an admin in the old domain.
2. Create a new empty folder under the %systemroot%\profiles with any name
other than that particular user who's profile we are migrating.
2. Right click on my computer and go to properties.
3. Go under the 'User profiles' tab and highlight the profile with that
user name.
4. Then click on 'Copy to' and copy it to the new empty folder that you
created in step # 2.
5. Click on 'Permitted to use' and give everyone permission.
6. In the %systemroot%\profiles folder rename that user's folder to
something different.
7. Then rename the new folder to the username for the new domain.
8. Join the new domain and log in as that user. The first time you log on
it will create a new default profile.
9. Then you need to log out and log back in as Administrator in the new
domain and open up registry and go to the following
key "HKLM\Software\Microsoft\WindowsNT\CurrentVersion\ProfileList."
Under this key you will see folders with all the sids of the users that
have logged in before.
10. If you highlight one of the folder under the ProfileList, on the right
hand side you will see the user name associated with that on the end of
line that says ProfileImagePath.
11. On the one that is for the user that you are working with, double click
on the ProfileImagePath and change the path to point to the right folder
under the %systemroot%\profiles.
12. Log out and log back in with the user account and you will have the
same profile as you had before in the old domain.
13. If you want, at this point you can change the permitted to use back to
this user only.

Hope the information helps.

Best Regards,

Jason Tan

Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security

=====================================================

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.




--------------------
| Thread-Topic: Migration from the "N" word...
| thread-index: AcZSd5fdHaUKfqDcRGW3qeNrWz/JxA==
| X-WBNR-Posting-Host: 216.110.204.126
| From: =?Utf-8?B?SmVmZiBTbWl0aA==?= < XXXX@XXXXX.COM >
| Subject: Migration from the "N" word...
| Date: Tue, 28 Mar 2006 06:55:02 -0800
| Lines: 15
| Message-ID: < XXXX@XXXXX.COM >
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
| Newsgroups: microsoft.public.windows.server.migration
| Path: TK2MSFTNGXA01.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.windows.server.migration:23113
| NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
| X-Tomcat-NG: microsoft.public.windows.server.migration
|
| I've installed and configured a new Windows Server 2003 Enterprise
Edition
| and am ready to move away from the "N" word and standardize on Microsoft.
|
| Here's my problem...I currently have 125 work