Re: SBS 2003 - Move Profiles, Etc. from 2000 Server

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Karl Burrows (karlspam_at_spam.yourbeacon.com)
Date: 03/07/05 

Date: Mon, 7 Mar 2005 02:35:00 -0500

Whew!

Figured out the profile copying. There are several reboots in between that
are needed to get the profiles to populate, however, I do have one
additional question. Shouldn't I be able to delete the old profiles once I
get it moved to the new one? I tried it on one and the new profile was
still pointing to the old profile folder, so it dropped the favs, etc.
Luckily the pst files were open, so it locked those. Hmmm...

I did just copy files between the servers. It was pretty fast, so it wasn't
a big deal. I had the same folder hierarchy on the new one, so it was just
copy, paste.

As far as small profiles, I couldn't agree more after spending 18 hours
moving 12 profiles. At this point, no matter how much I tell them, they
will not keep small profiles. The owner had a profile that took 2 hours to
copy and I had to do it twice since I had to create a local account to copy
it to from the old domain first for it to be available in the new domain.
His profile had to be 6GB! I guess he decided along time ago it was worth
whatever for him to have it his way and not have to fool with it. He
crashed his Outlook 2000 pst a few years ago and with 2003 has about 4GB of
data. So, I doubt roaming will work in this network, although it sure would
be nice. I manage a few other networks and since I built them, they are
nice and clean.

On roaming profiles, I have had a hard time getting the local settings
folder to copy to the server. Is there a specific permission you have to
set when you change it in AD?

Thanks for all the help!!

"Lanwench [MVP - Exchange]"
<lanwench@heybuddy.donotsendme.unsolicitedmail.atyahoo.com> wrote in message
news:ezxySanIFHA.2852@TK2MSFTNGP09.phx.gbl...
Karl Burrows wrote:
> We have a really old server running Server 2000 (old HP NetServer PII
> 400), so we purchased a new SBS 2003 thinking we could use it to
> migrate to Exchange, etc. at some point. Our office has grown from
> about 6 people to about 12 in less than a year and we have added
> several database programs including Timberline, etc., so it was time
> to upgrade.
>
> I created a new domain with the SBS as Domain Controller and was
> going to just add the workstations to the new domain and copy local
> profiles to get everyone up and running. We do not use Exchange,
> just basically a file sharing server running DHCP, DNS and WINS.
>
> Problems:
>
> 1. First, I found out I can not create a Trust to move files and
> settings between the two. Not a big deal, I guess, since I can copy
> them to a local workstation, just a pain to copy many folders twice.
> Is there no way for the new server to see the old server?

Sure, but you can't create trusts. Don't know what you mean by "settings",
but you can authenticate & map drives, etc., from the SBS box to the old
server. Just as you'd do if you had, say, an XP Home computer on you wanted
to access domain resources.

net use x: \\server\share /user:DOMAIN\user <enter>

> 2. All workstations are using XP SP2. It will not let me copy the
> Local Settings folder in the profiles, which the only folder that I
> really need in the copied profile anyway.

Why? What's in there?

> I tried to workaround it
> by just copying the Local Settings folder to the new profile, which
> did bring in things like email, but none of the user settings moved.

Such as?

> Everything is as with a new default profile. How can I get all of
> the profile copied to the new domain? I would really prefer not to
> backup the pst file, favorites, desktop settings, toolbar settings,
> Macros, etc. for 12 workstations. I found this to be true even with
> 2000 Server and Local Settings folders (I tried Roaming Profiles and
> it did not move the folder either).
> 3. Is there any way to demote the current 2000 Server in the current
> domain, add the new SBS in the current domain as controller

Only temporarily (see below)

> and keep
> the current local profiles on the workstations?

Not really. Profiles are a huge PITA no matter how you slice it. You can try
copying the old user domain profile to the new one if you log in as an
admin - control panel | system, etc.

> I know the security
> settings are different, but would this work keeping all current
> domain profiles on local workstations? Is there another way to keep
> the same domain name on the new server?
>
> I am just not sure why MS has made this so hard. It seems the only
> way to use SBS is to either upgrade a current server or have a brand
> new network. Did they not think anyone would want to replace an
> existing server in a existing domain/network?

You can - there are migration tools, and I believe that w/SBS2003 you can
install it as a member server in your existing domain for X days to give you
time to migrate.

Also take a look at www.sbsmigration.com

Re profiles, well, if you have a tiny network, you could recreate them. With
12 PCs, I'm not sure this would be a terribly daunting task.

I store virtually nothing in profiles that I'd need to migrate over to
another domain - maybe favorites. All other data is on the server, period -
including copying PST files, etc., to the users' home directories before
beginning this. And if you use roaming profiles from now on as I suggest,
keep the profiles TINY.

Also - not sure if the /connectcomputer wizard will allow you to migrate
your profiles to the new domain given that your existing machines are in a
domain already - but I believe it does work if they were in a workgroup.
Check in the SBS group (mentioned below). As with everything SBS - do *not*
make the common rookie mistake of trying to set anything up the non-SBS way
or you will be in heaps of trouble. You absolutely must use the dreaded
wizards - all of them. Take it from someone who has learned the hard way.
;-)

>
> Does anyone have experience in this type of move and can anyone offer
> any assistance to get this domain move without recreating the wheel?
> My biggest issue is the profiles. I guess I can work around the
> other.
>
> As a note, why can I login as an admin to a local workstation on the
> old domain and browse the new domain network with no trusts
> established? I can copy and delete files, etc. just as if it were on
> the network.

If your admin credentials are the same, that might explain it (see
authentication info above)

I seriously suggest you post in microsoft.public.windows.server.sbs before
proceeding with *anything at all* - you will get a ton of help planning
this, and won't end up painting yourself into a corner. Hope this helps.

>
> Thanks!

Relevant Pages

  • Re: GPO Settings
    ... EXISTING SETTINGS: ... Enabled - Terminate session when time limits are reached ... disconnected from the Terminal Server. ... I have roaming user profiles set for my local domain environment ...
    (microsoft.public.windows.terminal_services)
  • Re: Roaming Profiles Issue - Windows Server 2003
    ... I understand that you like Folder Redirection and suggest ... copied over due to the roaming profiles ie. desktop and my documents ... they're looking at the server. ...
    (microsoft.public.windows.server.general)
  • Re: Roaming Profiles Issue - Windows Server 2003
    ... I'm still considering redirecting their My Documents folders to be sure that their profiles remain small. ... I would like to implement redirecting the My Documents folder to their home drives but be able to fall back if necessary. ... I understand that you like Folder Redirection and suggest ... And My Documents redirection to the server ensures that when a user saves or opens files, ...
    (microsoft.public.windows.server.general)
  • Re: Default Administrator account as roaming profile?
    ... Server not compatible with SBS 2008. ... You set up shares on the server, and redirect the user profile My ... Documents folder ... roaming *profiles* but I think ...
    (microsoft.public.windowsxp.network_web)
  • Re: Migrate "Documents and Settings" folder from one drive to another
    ... I would strongly recommend to test this on a test server first. ... If you are roaming profiles, why change the location of the ... Documents and settings folder at all? ...
    (microsoft.public.windows.terminal_services)