RE: W2k dc migration to W2k3 dc (NEW HARDWARE)
- From: "tcarter" <tcarter@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 12 Aug 2005 08:28:04 -0700
Thanks i have another question of the subject but maybe you can help.
I have a window 2000 dc w/ SP4 installed.
When i go to Active Directory Users and Computers snap-in, and try to edit
the Default Domain Contrllers Policy or Edit Default Domain Policy From the
Domain controller organizational unit.
i double click Computer Configuration, Click Windows Settings, Double Click
Security Settings I get a blank page that says.
Windows Cannot open template file.
Any help with this would be appreciated, i also tried to edit my policy
using Group Policy Management MMC and i get the same error. Windows Cannot
open template file. No error logs show up in any of my event logs. Again any
help would be apprciated.
"Vincent Xu [MSFT]" wrote:
> Hello,
>
> I'm not sure what do you mean of "w2k3 with e2k3 supported by microsoft
> tech suppro". Of course we have professional support engineers for both
> Windows 2003 and Exchange 2003.
>
> Best regards,
>
> Vincent Xu
> Microsoft Online Partner Support
>
> Get Secure! - www.microsoft.com/security
>
>
> --------------------
> >>Thread-Topic: W2k dc migration to W2k3 dc (NEW HARDWARE)
> >>thread-index: AcWeiyxg8t4mvjCHTTikxunjETqJeQ==
> >>X-WBNR-Posting-Host: 64.169.192.186
> >>From: "=?Utf-8?B?dGNhcnRlcg==?=" <tcarter@xxxxxxxxxxxxxxxxxxxxxxxxx>
> >>References: <AD5763D3-63E2-4B30-9F6E-A09BA1A30E7D@xxxxxxxxxxxxx>
> <q#LBsuhnFHA.3120@xxxxxxxxxxxxxxxxxxxxx>
> >>Subject: RE: W2k dc migration to W2k3 dc (NEW HARDWARE)
> >>Date: Thu, 11 Aug 2005 08:41:43 -0700
> >>Lines: 112
> >>Message-ID: <A8908C97-B049-444B-8DD3-20B3D62E60AD@xxxxxxxxxxxxx>
> >>MIME-Version: 1.0
> >>Content-Type: text/plain;
> >> charset="Utf-8"
> >>Content-Transfer-Encoding: 7bit
> >>X-Newsreader: Microsoft CDO for Windows 2000
> >>Content-Class: urn:content-classes:message
> >>Importance: normal
> >>Priority: normal
> >>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
> >>Newsgroups: microsoft.public.windows.server.migration
> >>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
> >>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA03.phx.gbl
> >>Xref: TK2MSFTNGXA01.phx.gbl
> microsoft.public.windows.server.migration:11602
> >>X-Tomcat-NG: microsoft.public.windows.server.migration
> >>
> >>Is intalling w2k3 with e2k3 supported by microsoft tech supprot
> >>
> >>"Vincent Xu [MSFT]" wrote:
> >>
> >>> Hello,
> >>>
> >>> Based on my experience, your steps work. But for your special
> requirments,
> >>> it is realy hard to find any reference for your situation, please
> >>> understanding.But if you happen to any problem please feel free to let
> me
> >>> know. It is alwasy our pleasure to be of assistance.
> >>>
> >>> Again, we don't recommend install Exchange 2003 on DC. If possible,
> please
> >>> install it on a member server. Thanks.
> >>>
> >>> Best regards,
> >>>
> >>> Vincent Xu
> >>> Microsoft Online Partner Support
> >>>
> >>> Get Secure! - www.microsoft.com/security
> >>>
> >>>
> >>> --------------------
> >>> | Thread-Topic: W2k dc migration to W2k3 dc (NEW HARDWARE)
> >>> | thread-index: AcWd0z7zFp2PP2KFR3OQU/ugn/xVSg==
> >>> | X-WBNR-Posting-Host: 64.169.192.186
> >>> | From: "=?Utf-8?B?dGNhcnRlcg==?=" <tcarter@xxxxxxxxxxxxxxxxxxxxxxxxx>
> >>> | Subject: W2k dc migration to W2k3 dc (NEW HARDWARE)
> >>> | Date: Wed, 10 Aug 2005 10:45:06 -0700
> >>> | Lines: 51
> >>> | Message-ID: <AD5763D3-63E2-4B30-9F6E-A09BA1A30E7D@xxxxxxxxxxxxx>
> >>> | MIME-Version: 1.0
> >>> | Content-Type: text/plain;
> >>> | charset="Utf-8"
> >>> | Content-Transfer-Encoding: 7bit
> >>> | X-Newsreader: Microsoft CDO for Windows 2000
> >>> | Content-Class: urn:content-classes:message
> >>> | Importance: normal
> >>> | Priority: normal
> >>> | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
> >>> | Newsgroups: microsoft.public.windows.server.migration
> >>> | NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
> >>> | Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGXA03.phx.gbl
> >>> | Xref: TK2MSFTNGXA01.phx.gbl
> >>> microsoft.public.windows.server.migration:11581
> >>> | X-Tomcat-NG: microsoft.public.windows.server.migration
> >>> |
> >>> | I have 1 w2k dc SP4 with exchange server 2000 SP3 installed. I want
> to
> >>> | upgrade to W2k3 server and exchange server 2003 on new hardware
> acting as
> >>> DC
> >>> | (I know its not recommended to have exchange on DC but its a must).
> >>> advice
> >>> | needed.
> >>> |
> >>> | Do i need to run ADMT? if i install w2k3 on new hardware add it to
> the
> >>> | domain and then use "dcpromo" to promote the w2k3 server to be an
> >>> additional
> >>> | dc in the network. (NOT A BDC). or should i specify the w2k3 server
> to be
> >>> a
> >>> | BDC?
> >>> |
> >>> | Below are the steps i plan to take for this migration. Any advice
> would
> >>> be
> >>> | appreciated.
> >>> |
> >>> | I. Prepare network for Windows Server 2003.
> >>> | a.review article q314649 (Mangled Attributes)
> >>> | b. run adprep /forestprep
> >>> | c. run adprep /domainprep
> >>> | II. Install Windows Server 2003 on new hardware
> >>> | a. add to the domin
> >>> | b. use dcpromo to promote to dc.
> >>> | c. Install AD intergrated DNS
> >>> | Clear Error log (let servers run together for couple of days to
> insure
> >>> | replication)
> >>> | IV. Move GC role to w2k3 server i will refer to link
> >>> | http://msresource.net/content/view/25/47 published by Paul Williams.
> >>> | Clear Error logs
> >>> | V. Move FSMO roles (i will refer to articles q324801 & Q255504 to
> >>> complete
> >>> | this)
> >>> | Clear error logs
> >>> | VI. Add DHCP server role to w2k3 server {will all users be logging on
> to
> >>> new
> >>> | server at this point ?}
> >>> | Clear error logs
> >>> | VII. Install Exchange Server 2003 on W2k3 server box.
> >>> | Clear Error log
> >>> | VIII. Get familiar with Exchange Server 2003 (create SMTP connector
> move
> >>> | smart host configuration to this connector to prevent messages from
> >>> getting
> >>> | stuck in SMTP queue)
> >>> | VIIII. Configure Exchange 2003 server to Host public folder
> roles.(see
> >>> | article Q328287)
> >>> | Clear Error log
> >>> | X. Move the Mailboxes to Exchange Server 2k3
> >>> | Clear Error log
> >>> | XI. Final Clean up Move All files and Folders from w2k box to w2k3.
> >>> | {decommission w2k box and rebuild it}
> >>> |
> >>> | Any help with this process would be great. Its easy to find
> documentation
> >>> on
> >>> | inplace upgrades but impossible to find info on my situation any help
> >>> would
> >>> | be great. is the above process correct? feel free to add or remove
> form
> >>> it.
> >>> | Thanks.
> >>> |
> >>> |
> >>> |
> >>>
> >>>
> >>
>
>
.
- Follow-Ups:
- RE: W2k dc migration to W2k3 dc (NEW HARDWARE)
- From: Vincent Xu [MSFT]
- RE: W2k dc migration to W2k3 dc (NEW HARDWARE)
- References:
- W2k dc migration to W2k3 dc (NEW HARDWARE)
- From: tcarter
- RE: W2k dc migration to W2k3 dc (NEW HARDWARE)
- From: Vincent Xu [MSFT]
- RE: W2k dc migration to W2k3 dc (NEW HARDWARE)
- From: tcarter
- RE: W2k dc migration to W2k3 dc (NEW HARDWARE)
- From: Vincent Xu [MSFT]
- W2k dc migration to W2k3 dc (NEW HARDWARE)
- Prev by Date: RE: keeping the same user profiles and settings
- Next by Date: NT4 Print server on BDC
- Previous by thread: RE: W2k dc migration to W2k3 dc (NEW HARDWARE)
- Next by thread: RE: W2k dc migration to W2k3 dc (NEW HARDWARE)
- Index(es):
Relevant Pages
|