RE: windows NT to Win2K3 with Exchange 5.5 to Exchang 2K3

From: shakerfrank (shakerfrank_at_discussions.microsoft.com)
Date: 03/01/05 

Date: Tue, 1 Mar 2005 12:13:04 -0800

We are in the process of a similar upgrade. Additionally, we will be
eliminating Novell environment. In our test environment we have run into an
issue where Win 98 clients get an error "You do not have permission to access
this file. Contact and administrator..." If the same user logs in from a
Windows XP PC there is not problem. The files are in a share on a Win 2003
member server. To further complicate debugging, if the files are copied to
the new AD shared directory from the NT domain using the Win 98 client, then
98 clients have access. If the file copy is initiated from an XP system, the
98 clients are restricted.

While we cannot open the file when restricted, we are able to delete the
files.

We've looked everywhere for migration issue and only find the suggestion to
install the AD client. That was done, but does not resolve the issue. We have
converted most of the desktops to XP, but will not be migrating all before
this is implemented. I'm posting here to fshguo something else to think
about and in hopes that someone may have an idea for us.

"Frances [MSFT]" wrote:

> Hello Fshguo,
>
> Good to hear from you.
>
> According to your message, I understand that you now have a NT domain and a
> win2k domain. You goal is to migrate the NT domain to a win2kd domain. Is
> this correct?
>
> I notice you have Exchange 5.5 on your BDC, and you plan to migrate
> Exchange 5.5 to Exchange 2k3. Regarding this part, pease post it in the
> microsoft.public.exchange.setup newsgroup since they are the experts in
> Exchange and will provide the most accurate information on this issue.
>
>
> As for migrating NT to win2k3 domain, I suggest you follow the two steps
> below to achieve your goal.
>
> 1. Upgrade your win2k domain to win2k3 domain.
>
> 2. Migrate from NT to win2k3 using ADMT.
>
>
> Upgrading to win2k3 domain
> ===================
> 1. Backup your win2k DC before you take any action.
>
> 2. Run "adprep" to extend the schema.
> Run "ADPREP /FORESTPREP" and "ADPREP /DOMAINPREP") to upgrade the existing
> Windows 2000 forest and domain to ensure that they contain the additional
> objects, attributes and permissions necessary to support the Windows Server
> 2003 Active Directory environment.
>
> Refer to the following articles for more information.
>
> Please pay more attention in the part "Overview: Upgrading Windows 2000
> domain controllers to Windows Server 2003", which contains the information
> about "adprep":
> 325379 How to Upgrade Windows 2000 Domain Controllers to Windows Server 2003
> http://support.microsoft.com/?id=325379
>
> Upgrading Windows 2000 Domains to Windows Server 2003 Domains
> http://www.microsoft.com/technet/treeview/default.asp?url=/technet/prodtechn
> ol/windowsserver2003/proddocs/deployguide/dssbf_upwn_overview.asp
>
> 3. Decide whether to directly upgrade a win2k DC depending on the hardware.
> (Optional)
>
> 3.1 If the hardware supports win2k3, upgrade the win2k DC to win2k3 DC by
> using Winnt32.exe.
>
> 3.2 If the hardware doesn't support win2k3, promote a win2k3 member server
> to DC by dcpromo.
>
>
> Step 3 is optional because after step 2, you have already had a win2k3
> domain. You can upgrade your win2k DC to win2k3 DC as you like.
>
>
> Migrating from NT domain to win2k3 domain:
> ================================
> 1. Set up trusts between NT and win2k3 domain.
> In your scenario, you have already had dual trusts established with NT and
> win2k. When win2k domain is upgraded, the trusts will remain. You may
> verify the trusts and then go on.
>
> Use NetDom or Active Directory Domains and Trusts to verify the trusts.
>
> Please refer to the articles below.
>
> NetDom Examples
> http://www.microsoft.com/resources/documentation/WindowsServ/2003/all/techre
> f/en-us/Default.asp?url=/Resources/Documentation/windowsserv/2003/all/techre
> f/en-us/NetDom_examples.asp
>
> Pay extra attention to the snippet "verify a trust":
> How to establish trusts with a Windows NT-based domain in Windows Server
> 2003
> http://support.microsoft.com/default.aspx?scid=kb;en-us;325874
>
> 2. Use ADMT to migrate from NT to win2k3.
>
> I would like to suggest that you migrate the groups and users separately
> (do not migrate the associated members when migrating groups).
>
> You can download ADMT from the link below:
> Windows 2000 Active Directory Migration Tool
> http://www.microsoft.com/windows2000/downloads/tools/admt/default.asp
>
>
> More information:
>
> Active Directory Migration Tool Overview
> http://www.microsoft.com/windows2000/techinfo/planning/activedirectory/admt.
> asp
>
> Migrating Windows NT to Windows Server 2003 using the Active Directory
> Migration Tool
>
> http://techupdate.zdnet.com/techupdate/stories/main/Migrating_Windows_NT_to_
> Windows_Server_2003.html
>
> This response contains a reference to a third-party World Wide Web site.
> Microsoft is providing this information as a convenience to you. Microsoft
> does not control these sites and has not tested any software or information
> found on these sites; therefore, Microsoft cannot make any representations
> regarding the quality, safety, or suitability of any software or
> information found there. There are inherent dangers in the use of any
> software found on the Internet, and Microsoft cautions you to make sure
> that you completely understand the risk before retrieving any software from
> the Internet.
>
>
> Hope this helps. If you have any further questions, don't hesitate to get
> in touch!
>
>
> Best regards,
>
> Frances He
>
>
> 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.
>
>

Relevant Pages
Quantcast