RE: Netware -> MS2003 migration --- MSDSS / FMU log file manipulat
- From: v-jasont@xxxxxxxxxxxxxxxxxxxx (Jason Tan (MSFT))
- Date: Tue, 10 May 2005 10:44:05 GMT
Hi Ken,
Thanks for update!
FMU is integrated with MSDSS and enables the migration of large amounts of
file data from supported versions of NetWare over to Windows Server 2003,
Before you use FMU to translate the NDS, eDirectory, or Bindery file system
rights and permissions to the equivalent rights and permissions in the NTFS
file system, you must run a one-time migration of NDS or Bindery directory
objects to Active Directory. After you have performed the one-time
migration and selected the option to migrate files, a migration log will be
created that can be used later by FMU.
Without the log, FMU cannot sucessfully run. Therefore, he need to stop the
xml he is using to replicate the info between netware and the AD. use MSDSS
to migrate all account, MSDSS should have the ability to deal ith the
conflict account. then use FMU to mgirate files.
For more detailed information, please refer to the following article:
http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/TechR
ef/978715be-6170-4e40-99ae-96681142fe84.mspx
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.
--------------------
| Thread-Topic: Netware -> MS2003 migration --- MSDSS / FMU log file
manipulat
| thread-index: AcVUuLAs7sqB2I5pS1S/No96koJ/Vg==
| X-WBNR-Posting-Host: 155.188.191.5
| From: "=?Utf-8?B?S2VuIFQ=?=" <KenT@xxxxxxxxxxxxxxxxxxxxxxxxx>
| References: <339852AA-78DE-45B3-B5E3-245395CDC7C0@xxxxxxxxxxxxx>
<C13yffHVFHA.388@xxxxxxxxxxxxxxxxxxxxx>
| Subject: RE: Netware -> MS2003 migration --- MSDSS / FMU log file
manipulat
| Date: Mon, 9 May 2005 10:01:05 -0700
| Lines: 115
| Message-ID: <B1D023E7-A393-470A-AB66-47C8FF028512@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!TK2MSFTNGXA03.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.windows.server.migration:10080
| X-Tomcat-NG: microsoft.public.windows.server.migration
|
| Jason,
|
| Thank you for your response. Unfortunately, all of the articles you
| reference all refer to the same strategy for migrating off of Netware.
The
| problem is that they all assume a 'blank slate' migration where there are
no
| existing AD objects that are synced with Netware.
|
| In our situation -all- objects already exist in both AD and Netware, I
| simply need a way to map them together for the File Migration. If I do
the
| DirSync as reccommented, I am afraid it will interfere with our existing
| syncronization process. In addition it requires schema extensions that
are
| unneeded for our situation.
|
| What I am trying to find out is specifically, if there is a way to
generate
| a compatible log file for the File Migration utility without using the
| Directory Sync tool.
|
|
|
|
| "Jason Tan (MSFT)" wrote:
|
| > Hi Ken,
| >
| > Thanks for posting!
| >
| > Based on the situation, I would like to provide you with following
| > information for your reference:
| >
| > Solution for Migrating File, Print, and Directory Services from Novell
| > NetWare to Windows Server 2003
| > http://www.microsoft.com/windowsserver2003/migrate/novell/novellmg.mspx
| >
| > NetWare to Windows Server 2003 Migration Planning Guide
| > http://www.microsoft.com/windowsserver2003/techinfo/overview/sfnmig.mspx
| >
| > TNT1-130: Novell NetWare and Microsoft Windows Server 2003 Migration
and
| > Interoperability
| >
http://www.microsoft.com/technet/community/events/windows2003srv/tnt1-130.ms
| > px
| >
| > The below article should hold good for the migrating to Windows 2003
too.
| >
| > How to Migrate Users from NetWare to Windows 2000 with the MSDSS Tool
and
| > One-Time Migration
| > http://support.microsoft.com/default.aspx?scid=kb;en-us;301542
| >
| > Utilities for Integrating Windows NT Server with Novell NetWare Server
| >
http://www.microsoft.com/ntserver/techresources/interop/netware/netwareserve
| > r.asp?bPrint=True
| >
| > I hope my 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.
| >
| > --------------------
| > | Thread-Topic: Netware -> MS2003 migration --- MSDSS / FMU log file
| > manipulation
| > | thread-index: AcVShq/Dn3uZLdWCTi232Bq/6q8UnA==
| > | X-WBNR-Posting-Host: 155.188.255.5
| > | From: "=?Utf-8?B?S2VuIFQ=?=" <Ken T@xxxxxxxxxxxxxxxxxxxxxxxxx>
| > | Subject: Netware -> MS2003 migration --- MSDSS / FMU log file
manipulation
| > | Date: Fri, 6 May 2005 14:58:07 -0700
| > | Lines: 14
| > | Message-ID: <339852AA-78DE-45B3-B5E3-245395CDC7C0@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:10055
| > | X-Tomcat-NG: microsoft.public.windows.server.migration
| > |
| > |
| > |
| > | Our company is going through a Netware to AD conversion, however we
have
| > | been using DirXML for about a yearto sync E-Dir and AD. Because of
this,
| > I
| > | am hesitant to use the MSDSS product for fear of interfering with the
XML
| > | process. In addition, I can't easily install the MSDSS because I
cannot
| > | extend schema in the AD envorinment since we are a domain within a
larger
| > | forest.
| > |
| > | Is there a way to use FMU without ever fully installing MSDSS into
the
| > | production environment? I have mimicked the file structure of the
| > migration
| > | log, but when I try to load a modified log file into the FMU tool, I
| > always
| > | get an "Invalid ADS Class name in mapping Entry". The syntax of the
DN
| > | reference is correct on the line that
| > |
| >
| >
|
.
- References:
- Prev by Date: RE: Upgrading NT to 2003
- Next by Date: Two Domains - Best Practice
- Previous by thread: RE: Netware -> MS2003 migration --- MSDSS / FMU log file manipulat
- Next by thread: nt4 current users
- Index(es):
Relevant Pages
|
Loading
