RE: NT4 to 2003 problem w/ Mandatory profiles

Hello,

Thanks for posting!

Please make sure you move a GC to the new Windows 2003 R2 DC. I suggest you
take the original DC online and move the GC. Please wait for a period time
to ensure the replication is in place. You may refer to the following
aritlce:

313994 How to create or move a Global Catalog in Windows 2000
<http://support.microsoft.com/default.aspx?scid=kb;EN-US;313994>

Hope the information helps. If there is anything that is unclear, please
feel free to let me know.

Best Regards,

Jason Tan

Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security

=====================================================

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

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






--------------------
| From: "Thorin Rehkopf" <thorinr@xxxxxxxxxxxxx>
| Subject: NT4 to 2003 problem w/ Mandatory profiles
| Date: Mon, 20 Mar 2006 13:35:30 -0700
| Lines: 37
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2900.2670
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670
| X-RFC2646: Format=Flowed; Original
| Message-ID: <OSCA32FTGHA.4132@xxxxxxxxxxxxxxxxxxxx>
| Newsgroups: microsoft.public.windows.server.migration
| NNTP-Posting-Host: ip68-0-190-211.tc.ph.cox.net 68.0.190.211
| Path: TK2MSFTNGXA03.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP11.phx.gbl
| Xref: TK2MSFTNGXA03.phx.gbl
microsoft.public.windows.server.migration:22997
| X-Tomcat-NG: microsoft.public.windows.server.migration
|
| I recently performed an in-place NT4-to-2003 migration. The NT4 domain
had
| just a single PDC and like 10 Windows XP clients. I backed up all the
data
| and added a (virtual) BDC for redundancy and then upgraded the PDC to
| Windows Server 2003. Before I upgraded I made sure to follow the steps
| outlined in the Windows Server 2003 Migration Guide (mostly).
|
| The upgrade went smoothly and I brought the new AD domain up with no
| problems. I then added a brand new Windows Server 20003 R2 computer with
| more up to date hardware. The schema needed to be extended for the R2 DC
so
| I did that and then removed the BDC and brought several more client
| workstation (WinXP) into the domain.
|
| The Windows XP client machines are operator stations for a phone
answering
| service and they are very much like a kiosk station so as part of their
new
| lockdown I implemented mandatory profiles. After some tinkering the
profiles
| are working correctly and everyone gets a consistent desktop if they
logon
| with the opstation accounts.
|
| The original PDC which is now running Windows Server 2003 needs to be
| repurposed and so I removed the FSMO roles (Schema Master, Domain naming
| master, Infrastructure master, RID master, and PDC emulator) and moved
them
| to the new R2 computer. I then reset the client workstations to use the
R2
| computer for their primary DNS and made sure that the mandatory profiles
| were located on the R2 server.
|
| As a test I turned off the PDC/Windows Server 2003 computer and
discovered
| that if clients try to logon they can authenticate (eventually) but they
do
| not locate the mandatory profiles and throw an error message. (Can't find
| roaming profiles will load a default profile etc...) I flushed the DNS
on
| the client computers and tried again with the same results. I am also
unable
| to move the w32time service off of the former PDC as when I try and do
that
| it gives me an error message in DCDIAG and says it isn't able to
replicate.
|
| Did I forget something from the migration guide or is this some DNS or
FSMO
| issue that I'm just not thinking through clearly.
|
|
|

.

Relevant Pages

  • NT4 to 2003 problem w/ Mandatory profiles
    ... just a single PDC and like 10 Windows XP clients. ... The Windows XP client machines are operator stations for a phone answering ... computer for their primary DNS and made sure that the mandatory profiles ...
    (microsoft.public.windows.server.migration)
  • Re: Directory Services Client for Windows 95
    ... >> In the help files for Windows Server 2003, ... >> active directory supports Windows 95 if the Directory ... >> disk and couldn't find the ds client. ...
    (microsoft.public.win2000.active_directory)
  • Re: Windows 2003 Server Client Setup
    ... you should install Active Directory to promote the Windows Server ... You must add related computer accounts for each client computer that need to ... then follow the Network Identification Wizard ...
    (microsoft.public.windows.server.general)
  • Directory Services Client for Windows 95
    ... In the help files for Windows Server 2003, ... active directory supports Windows 95 if the Directory ... Services client is installed. ...
    (microsoft.public.win2000.active_directory)
  • want NT client to see server share
    ... I want a machine running NT client under DOS to be able to connect to shares ... on a Windows server 2003 machine. ... I can connect to this share from windows 98 machines that are ... also, for some reason, when i take tcp/ip off ...
    (microsoft.public.windows.server.networking)
Loading