Re: Big move...



I'd like to just be able to copy them over to the server and point each
user
to them within the ADUC properties, but some of the profiles are over 3GB
in
size and the login would literally take more than an hour just to
synchronize.

Is there any way I can join all these workstations to the domain and still
maintain all the local workstations desktops, applications installations,
and
other profile-related settings?

Yes, sort of but it's not trivial. (Script might help a LOT).

You can save those Profiles but you will have to manually
or through scripting address each one individually or lose
the settings.

If you just set them "to a server share" which is EASY to
do by selecting ALL the user accounts and specifying
something like:

\\ServerName\ProfileShareName\%username%

....you will end up with what are called ROAMING profiles,
stored on "ServerName" BUT your users will not have access
to their former profiles and files (easily.)

There is a USMT (User StateMigration Tool) free from MS
which can capture the profile (and many other things) and
let you load it on even a new machine but this is labor
intensive for 200 machines.

Best is something like the following but automated by a
script:

Xcopy all files in the old profile over the top of the NEW
profile after the machines JOIN the domain AND the users
logon AND off one time.

What will happen is that the old profile will be the new
one.

Problems: Identifying the old profile name SINCE you have
those weird "common name" users and they are not going to
match the NEW USER accounts you give each user individually.

As to 3 Gig profiles you probably do NOT want these stored
on the Servers as you have indicated you understand.

You could separate out the "big parts" from the other parts
by using folder redirection but that is likely a further
consideration for after you get it working.


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

"John Wright" <John Wright@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:10FF776F-B204-4C95-A823-830FF05E86FE@xxxxxxxxxxxxxxxx
I'm getting ready to move my entire company from Netware 5 to Windows
Server
2003 Enterprise Edition. Unfortunately, the IT individual before me left a
whole lot to be desired in the realm of system administration.

At the client level, I have 200+ Windows 2000 Professional workstations.
Approximately half of them were installed "user specific" (usr:jsmith /
pwd:blue987) and the other half were installed with a generic user name
and
password (usr:generic / pwd:{blank}). Unfortunately, again, all users
(specific and generic) were given administrative rights to their local
workstations. The "user specific" workstations have synchronized usernames
and passwords between the workstations and the Netware server...when the
user
logs into the local workstation, they are also logging into the Netware
tree
simultaneously. The generic workstations are automatically logged into the
local workstations at startup, then they're presented with a Netware login
at
which point they can login to Netware with user-specific credentials.
(welcome to my nightmare!)

At the server level, I have 1 Netware 5 server, one tree, one context and
all users and groups are located therein. The tree has a login script that
checks group membership and maps drives accordingly.

I've copied all the users and groups over to the Win2K3 server
successfully,
now I need to figure out how in cyberspace I'm going to handle 200+ local
user profiles.

Any ideas?

I'd like to just be able to copy them over to the server and point each
user
to them within the ADUC properties, but some of the profiles are over 3GB
in
size and the login would literally take more than an hour just to
synchronize.

Is there any way I can join all these workstations to the domain and still
maintain all the local workstations desktops, applications installations,
and
other profile-related settings?

Thank you.


.



Relevant Pages

  • 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: Windows 2003 Server and User Profiles
    ... of two things for copying profiles. ... Can I ask about joining the workstations to the domain? ... Business Server you run a script called connetcomputer that copies the local ... Now you can have folder redirection and roaming user profiles ...
    (microsoft.public.windows.server.general)
  • Re: win2k3 profiles
    ... Your observations about criteria that makes roaming profiles plausible is ... workstations and they are indeed different... ... joined to the server then the Antivirus software deployment is a snap. ...
    (microsoft.public.windows.server.networking)
  • Re: Migrating to SBS2003 R2
    ... > This is where it gets sortta tricky, user profiles and decomissioning of the ... >>> Since your workstations belong to the NT domain, and not the SBS domain, ... and create a new SBS domain with a new AD. ... >>> There is a tool to demote an nt dc to a plain vanilla nt server. ...
    (microsoft.public.windows.server.sbs)