oh, the reinstall worked - but now...migrating user profiles.

[Child]

The reinstall went beautifully. Everything appears to be working great.
Sharepoint, which i formerly hated, installed without a hitch. Amazing.
Nice work SBS team! This is going to be perfect for our small office.

I was able to create myself an account on the server and an account for my
computer. But when I try to use the URL for the automatic configurator on my
workstation it tells me that I need to check MS's website first to find out
how to move my profile over since i am a part of a domain already. I have
been searching for at least a half hour -where do i find this info?

Thanks in advance!

[SuperGumby [SBS MVP]]

XP on that workstation?

First, logon to the machine as if it was in the old domain, it should use
cached credentials and load the old profile.
Then use the files and settings wizard to park profile information to a
folder which is NOT part of the current profile (C:\oldprofile works for me)
Ensure you know the local administrator account's password.
Swing the PC to a workgroup.
Join the new domain.
Files and settings wizard to recover most profile related stuff.

"Child" <be...@NOT-SO-bad-dawgs-in-ak.com> wrote in message
news:10cl90k...@corp.supernews.com...

[Peter Gallagher [MSFT]]

Hello,

Harry Brelsford has some examples in this month's newsletter.

</plagiarism on>

The Old Fashioned Way

Call it a lesson learned late on a Saturday night. This method was used in
late January during the heat of a conversion battle by yours truly! For this
procedure, I assume that you are using a Windows XP Professional
workstation.

While the XP Pro workstation is still attached to the legacy SBS 2000
network, copy the network profile down to the local hard disk. So assuming
you are logged on to said SBS 2000 network, proceed to the next step.

Click Start>Control Panel>System>Advanced>User Profiles>Settings.

Highlight the network profile for the user. For example, NormH.

Select Copy To and direct the profile to copy to the local hard disk. For
example, C:\Temp. Click OK>OK.

From the Control Panel, launch Administrative Tools>Computer Management.

Select System Tools>Local Users and Groups.

Select Users.

Right-click in the right-pane and select New User to add a user named "Foo."

Double-click the user object and select the Profile tab to view the
properties for Foo.

In the Profile path field, point to the exact profile you copied to C:\Temp
in Step 4. Click OK.

Close all open applications, shut down the Windows XP Pro machine, and move
it physically to the new SBS 2003 network. Reboot and relaunch the SBS
Network Configuration Wizard.

Back on the screen to Assign users to this computer and migrate their
profiles, in the lower section, under the user name (for example, NormH),
click Current User Settings and select Foo. Complete the steps for joining
the workstation to the SBS 2003 domain. The profile WILL be migrated!

User Profile Registry

This method came in from M.J. Shoer (MSh...@jenaly.com), who attended the
SMB Nation Summit in Boston in May. He writes:

This method has worked for us without fail. We can retain the complete
profile customizations for a PC that was logged into one domain and must now
be logged into a new one.

The method works for both Win2K and WinXP. It has also worked for upgrading
SBS 2000 to SBS 2003, where it is happening on the same server, meaning that
you have to reformat the SBS 2000 server and load "freshie," as you would
say, with SBS 2003. Here's how it works.

Once the SBS 2003 server is set up and the computers are set up on the
server side, log into the client PC and run the connectcomputer URL. When
that step is completed, log in as the user. Then immediately log off and log
on as the domain administrator.

Be sure the domain user account is in the local administrator's group. Then
open Registry Editor and navigate to
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsNT\CurrentVersion\ProfileList.
You will see a listing for each SID. Within each SID key, you will see an
entry for ProfileImagePath with a path to the users profile in the form of
%SystemDrive%\Documents and Settings\UserName.

The trick is to find the new key that was set up at logon to the SBS 2003
server and edit the path to refer back to the original profile path. So, for
example, if you are migrating and changing domains, you want to have a path
like %SystemDrive%\Documents and Settings\UserName.OldDomain. You then have
a new SID key with a path like %SystemDrive%\Documents and
Settings\UserName.NewDomain. You can edit this key and replace NewDomain
with OldDomain to point to the old profile.

In the case of a server migration within the same domain, you have a path to
the effect of %SystemDrive%\Documents and Settings\UserName.Domain and
%SystemDrive%\Documents and Settings\UserName.Domain.000. In this instance,
you delete the .000 to point back to the original profile.

The MCSE Way

Then there are the grizzled MCSEs amongst us who pointedly highlight using
the Active Directory Migration Tool (ADMT). Details at
http://www.microsoft.com/technet/prodtechnol/windows2000serv/downloads/admtool.mspx).
Enough said!

BEST PRACTICE: This article was written by popular demand. Many SMB Nation
Summit attendees are asking this question and noted that this information
was missing from Windows Small Business Server 2003 Best Practices (Volume
One: Introduction\Intermediate). You can bet it will be in the advanced
book!

<plagiarism off>

Thanks for posting!!

Regards,
Peter Gallagher
Microsoft Product Support
Small Business Server Team

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

"SuperGumby [SBS MVP]" <n...@your.nellie> wrote in message
news:eHZhuxFU...@tk2msftngp13.phx.gbl...

[Les Connor [SBS MVP]]

This deserves a thread of it's own - Thanks Peter.

--
Les Connor [SBS MVP]
-------------------------------------
SBS Rocks !

"Peter Gallagher [MSFT]" <pete...@online.microsoft.com> wrote in message
news:uZNND3IU...@TK2MSFTNGP12.phx.gbl...

[Mike R]

Couldn't this be made even easier by taking that user and giving them a
roaming profile before the old system is taken down then saving the shared
folder where the roaming profiles were created somwehere SAFE. Then bring
the new system up and create your shared folder for roaming profiles where
you want it, assign the path to the users (newly created) and log in? It
worked with my system on a rebuild although I had to clean up a few
shortcuts that were no longer relevant but I think you would have to do that
nomatter what method you choose if paths had been altered.
Very curious here because if it isn't supposed to work...why did it?

"Les Connor [SBS MVP]" <les.c...@DEL.cfive.ca> wrote in message
news:u7ZFBjJ...@tk2msftngp13.phx.gbl...

[Child]

"Peter Gallagher [MSFT]" <pete...@online.microsoft.com> wrote in message
news:uZNND3IU...@TK2MSFTNGP12.phx.gbl...

Hi Peter and Thank you!
I was able to use the profile hack below, and it worked beautifully. All
of my PC's are happily on the new domain!