Re: Final step?

"El Marko" <threegtrz@xxxxxxxxxxx> wrote in message
news:eI2q67ygFHA.1412@xxxxxxxxxxxxxxxxxxxxxxx
> OK, then does making the machine join the domain mess up the user
profiles?
>

Technically no, but the effect may be terrible if you don't take
actions.

Old profiles will still be there from when the use logged onto
a machine specific account.

What 'messes up' the profiles is that the user is now expect to
logon through a (new) domain account which even with the same
name is NOT the same user.

There are several ways to fix it but my favorites are these:

1) Just copy the old profile, e.g., HerbM over the new one, e.g.,
HerbM.LearnQuick (or whatever it turns out to be.)

2) Use the much more capable USMT (User State Migration Tool)
to migrate not only the Profile but also the "hidden" user stuff
for many programs like Outlook, OE, etc.

#1 is quick and easy but incomplete -- e.g., try getting the users
Newsgroups that way.

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

> mm
>
> "Herb Martin" <news@xxxxxxxxxxxxxx> wrote in message
> news:eEqha5xgFHA.2156@xxxxxxxxxxxxxxxxxxxxxxx
> > "El Marko" <threegtrz@xxxxxxxxxxx> wrote in message
> > news:e$o8x9wgFHA.572@xxxxxxxxxxxxxxxxxxxxxxx
> >> I've run ADMT to add our computers in the currnet NT domain to our new
> >> 2k3
> >> domain. The agent has been installed and profiles are being copied.
> >>
> >> However, our 2kpro and XP workstations still think of themselves as
> >> member
> >> of the old NT domain when looking on the My Computer property ***. Do
I
> >> still have to join these machines to the new domain AT the machine?
> >
> > Yes, the migration concerned the ACCOUNTS - the machines still have
> > to be informed of the change.
> >
> >> Also, when doing a test run logging onto the new domain after
migration,
> >> most users are experiencing v e r y slow login performance. What can I
> >> do
> >> to improve this?
> >
> > Usually it is a DNS problem. For older clients (NT/9x) a NetBIOS issue.
> >
> > If you used WINS server in NT then you likely still need it and need ALL
> > of your machines to be WINS clients --- especially your DCs (so they
will
> > register themselves and therefore be found by clients...)
> >
> > Here's a sketch of DNS items to check:
> >
> > DNS for AD
> > 1) Dynamic for the zone supporting AD
> > 2) All internal DNS clients NIC\IP properties must specify SOLELY
> > that internal, dynamic DNS server (set.)
> > 3) DCs and even DNS servers are DNS clients too -- see #2
> > 4) If you have more than one Domain, every DNS server must
> > be able to resolve ALL domains (either directly or
indirectly)
> >
> > netdiag /fix
> >
> > ...or maybe:
> >
> > dcdiag /fix
> >
> > (Win2003 can do this from Support tools):
> > nltest /dsregdns /server:DC-ServerNameGoesHere
> > http://support.microsoft.com/kb/q260371/
> >
> > Ensure that DNS zones/domains are fully replicated to all DNS
> > servers for that (internal) zone/domain.
> >
> > Also useful may be running DCDiag on each DC, sending the
> > output to a text file, and searching for FAIL, ERROR, WARN.
> >
> > Single Label domain zone names are a problem Google:
> > [ "SINGLE LABEL" domain names DNS 2000 | 2003 microsoft: ]
> >
> > --
> > Herb Martin, MCSE, MVP
> > Accelerated MCSE
> > http://www.LearnQuick.Com
> > [phone number on web site]
> >
> >>
> >> m
> >>
> >>
> >
> >
>
>


.

Loading