Re: Migrationn from Exch 5.5 on NT to Exch 2003 on 2003



Hi Jason,

My understanding of the File and Printer migration tools is that they copy the settings from one server to another, that is, the same ACL and Share permissions exist. Now what i am doing is migrating from an NT domain (NTDOMAIN) to a Windows 2003 Domain (W2K3DOMAIN). So if I have a share with NTFS permissions \\NTDOMAIN\USERS and use the FSMT, it would simply transfer the shares with the permissions \\NTDOMAIN\USERS. What i need is to transfer the shares with the new permissions \\W2K3DOMAIN\USERS.

Correct me if i am wrong in saying that FSMT does not do that. I don't believe that the Printer Migration tool does that as well.

Sachin

Jason Tan (MSFT) wrote:
Hi Sachin,

Thanks for posting!

It appears that you have 3 questions at present. Regarding the first two questions related to exchange, please open a new post in microsoft.public.exchange.general newsgroup. That newsgroup is primarily for issues involving Exchange, So that the dedicated MS engineer can help you on it in a more efficient manner.

With respect to the third question, Can I assume that you want to migrate file and printer server to Windows 2k3 domain?
Based on my understanding, I recommend you migrate file with FSMT and migrate printer with Print Migrator 3.1.


Overview of the Microsoft File Server Migration Toolkit white paper of FSMT http://www.microsoft.com/windowsserver2003/upgrading/nt4/tooldocs/msfst_over
view.mspx


FAQ on FSMT:
http://www.microsoft.com/windowsserver2003/upgrading/nt4/tooldocs/msfst_faqs
.mspx

White Paper: http://www.microsoft.com/windowsserver2003/upgrading/nt4/tooldocs/msfst_over
view.mspx


Print Migrator 3.1
http://www.microsoft.com/WindowsServer2003/techinfo/overview/printmigrator3.
1.mspx

Print Migrator 3.1 Download
http://www.microsoft.com/downloads/details.aspx?FamilyID=9b9f2925-cbc9-44da-
b2c9-ffdbc46b0b17&displaylang=en

Microsoft Print Migrator Document
http://www.microsoft.com/windows2000/docs/PrintMigrator3.doc

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

Thanks & 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.










--------------------
| Message-ID: <42BABB2E.3050609@xxxxxxxxx>
| Date: Thu, 23 Jun 2005 09:37:50 -0400
| From: PAZMAN <pmpmailbox-news@xxxxxxxxx>
| User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
| X-Accept-Language: en-us, en
| MIME-Version: 1.0
| CC: pmpmailbox-news@xxxxxxxxx
| Subject: Migrationn from Exch 5.5 on NT to Exch 2003 on 2003
| Content-Type: text/plain; charset=ISO-8859-1; format=flowed
| Content-Transfer-Encoding: 7bit
| Newsgroups: microsoft.public.windows.server.migration,microsoft.public.exchange.setup
| NNTP-Posting-Host: mail.commnett.com 200.108.21.245
| Lines: 1 | Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP09.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.exchange.setup:20650 microsoft.public.windows.server.migration:10832
| X-Tomcat-NG: microsoft.public.windows.server.migration
| | Hi All,
| | We are planning a migration from Exchange 5.5 on Windows NT to Exchange | 2003 on 2003. There are five NT Domains that are bing consolidated to a | single domain and five exchange sites that will remain the same. The new | domains are being installed on new hardware so we are doing a parallel | install and migration (not an in-place).
| | We have read tons of material and came up with the following:
| | 1) Install Windows 2003 with AD.
| 2) Create trust between new domain and NT domain.
| 3) Move DNS and WINS to new servers.
| 4) Use ADMT to copy users to new domain with SID History.
| 5) Install Exchange 2003 on Windows 2003.
| 6) Install and configure ADC.
| 7) Move mailboxes to Exchange 2003 servers.
| 8) Move workstations to new domain.
| 9) Move DHCP to new Servers.
| 10) Move Print and File servers to new domain.
| 11) Decommission old NT servers.
| | Am i missing anything?
| | But i do have a few questions.
| | 1) Do I move workstations to the new domain before or after installing | exchange and moving mailboxes? Or does it matter?
| | 2) Will ADC copy user settings such as rules and out-of-office settings? | If not, what will?
| | 3) How can i redo the ACL settings on file and printer to automatically | point to the new domain?
| | | Thanks for your assistance,
| | Sachin
|


.



Relevant Pages

  • RE: NT4 upgrade to 2k3 Server with WAN
    ... However, in order to keep the thread clean, please open up a new thread and ... Our NT4.0 servers are very outdated ... I have new exchange 2k3 ready to be installed and will ... >> You can use the migration or upgrade method to win2k3 domain. ...
    (microsoft.public.windows.server.migration)
  • Problem sending mail from Exchange 5.5 to Exchange 2003
    ... Exchange 5.5 server. ... The difference between this migration ... Exchange 5.5 mailbox servers are placed in the users ... When migrating mailboxes home- and commonareas are ...
    (microsoft.public.exchange.misc)
  • Re: Migrating NT4 domain and 5.5 exchange to EX2003 and AD
    ... and have that running and replicating smoothly befor the migration. ... domain prep to get the schema ready for exchange ... remove the ADC and shutdown the NT and 5.5 servers ...
    (microsoft.public.exchange.admin)
  • Exchange 5.5 > 2003 Migration
    ... Currently I am in the Pilot phase of a migration to 2003 from Exchange 5.5. ... OWA is currently being used by 5.5 users on a dedicated OWA server. ... the process of 'Swingbox' migration of the backend servers will OWA continue ...
    (microsoft.public.exchange.setup)
  • Re: Moving NT4 based PDC and BDC to Win2k
    ... How to Migrate Your Windows NT 4.0 Directory Services to Windows 2000 Active ... Domain Migration Strategies and Windows 2000: ... > - create several DC's on other existing Win2k servers so ... > necessary (nothing runs on the existing NT4 servers except ...
    (microsoft.public.win2000.active_directory)