Re: UPGRADE SMALL NETWORK

<drhopkins@xxxxxxx> wrote in message
news:1114111482.691417.74220@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
>I have a new client that is replacing their W2K DC(WalMart Box) with a
> new W2003 DC. This is a small network of 12 users. I plan on
> configuring the new server (new user accounts, shares, permissions,
> etc), transfering the data by way of an external hard drive, unplugging
> the old server and bringing the new one online. Has anyone
> successfully performed this operation? If the new domain controller
> has the same domain name, will I need to make any changes to users'
> workstations?
> I'm not into running adprep /forestprep; adprep /domainprep on the
> WalMart box and upgrading the domain like Microsoft suggests. I
> appreciate any suggestions, Thanks, Dave.
>

DC implies they are domain based. If you want to do things properly there
are no shortcuts. You have to build the 2k3 DC, prep the domain, add the new
DC, transfer the FSMO roles, then demote the old DC. This is a very
abbreviated version. Not doing this will cause all sorts of problems with
SIDs, permissions, etc. Just using the same domain name will not work in any
way, shape or form. You would have to recreate all the users, they will get
new user profiles on all 2000/XP workstations, they will have to take
ownership of all the old files. All the share and file permissions will have
to be recreated. It will be a nightmare.

Here is a start:

http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/DepKit/3f4b9633-234e-465a-b9c4-0e08fe703d1c.mspx

You should have a check list or something will be missed for sure. Make sure
you have good backups before starting.

They only way I can think of without going through all the steps would be to
copy all the shared data files on the old server to a FAT32 partition, then
restore them to the new DC. You would still run into problems with user
profiles and files local to the workstations.

Kerry


.

Relevant Pages

  • Re: Configuration Error for User Accounts
    ... Check the folder installation, or you can also donwload from sysinternals the Filemon tool runas administrator to check where the permissions are beeing denied, you can also check it with regmon. ... I think it is more than just this one program, since we have another program that uses a shared database on the server that everyone has full access to and when I load that program up I get Path / File Access Error 75. ... with the delete profile at logoff to keep the workstations clean. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Windows 2003 Server and User Profiles
    ... Can I ask about joining the workstations to the domain? ... And then how do I move the users profile over to the server? ... Now you can have folder redirection and roaming user profiles ...
    (microsoft.public.windows.server.general)
  • Re: win2k3 profiles
    ... include having all data on the server for centralized backup, ... install software at will, data is saved on workstations, anti virus is not ... and am confused about the user profiles. ... Others do log on to the domain but seem to have local profiles. ...
    (microsoft.public.windows.server.networking)
  • Re: Question re: Active Directory & User Profiles
    ... > Or more specifically, user profiles. ... That server is the Domain Controller. ... > workstations are joined to the domain. ... Microsoft MVP - Windows Server Directory Services ...
    (microsoft.public.windows.server.active_directory)
  • Re: network place help
    ... Next you need to turn off simple file sharing on the server pro machine. ... skim the checklist for simple file sharing and permissions. ... Now if you want a folder for just certain users, maybe each user needs different permisiions, then just add each user to the permission list and check the needed permissions for each user. ... I may want to know if the workstations can use ...
    (microsoft.public.windowsxp.network_web)