Re: MSDSS question
- From: "JP Breton" <jpbreton@xxxxxxxxxxxx>
- Date: Thu, 9 Feb 2006 14:21:27 -0500
Thanks Jason,
This is exactly what I want ot do.
Last question.
Will the user still need the Netware Client on their XP machine?
Their will still be a Netware file server for a while , so I am not sure if
the user will need the Novell client.
If the Novell client is still needed, should I change the binding order so
that the Microsoft Network is first?
Then the credential will be pass to the Novell client by MSDSS?
Regards
JP
"Jason Tan (MSFT)" <v-jasont@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:4uDr6tTLGHA.3052@xxxxxxxxxxxxxxxxxxxxxxxx
Hello,
Thanks for posting!
Please refer to the following recommended method.
We can use Microsoft Directory Synchronization Services (MSDSS) to
synchronize user accounts between a NetWare Directory Services (NDS) tree
and Active Directory. You may review the following URL:
316226 HOW TO: Configure Two-Way Account Synchronization with Microsoft
Directory Synchronization Services
<http://support.microsoft.com/?id=316226>
There is limitation on synchronizing the password between Windows 2003 AD
and NDS. This is mainly caused by that we do not know how NetWare encrypt
their password. if you use MSDSS to synchronize NDS and Windows 2003 AD,
the password changing on the Windows 2003 AD will reflect on NDS (We will
send the password to NDS with clear Text). However if you change the
Password in NDS, it will not reflect on the Windows 2003 AD because we are
not able to read the password from the NDS database without knowing how it
is encrypted.
Here is more information of Netware and Windows 2003 you can take a look
for more information:
Microsoft Windows Services for NetWare 5.02
<http://www.microsoft.com/windowsserver2003/sfn/default.mspx>
NetWare to Windows Server 2003 Migration Planning Guide
<http://www.microsoft.com/windowsserver2003/techinfo/overview/sfnmig.mspx>
Hope the information helps.
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: "JP Breton" <jpbreton@xxxxxxxxxxxx>
| Subject: MSDSS question
| Date: Wed, 8 Feb 2006 13:13:38 -0500
| Lines: 20
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2900.2670
| X-RFC2646: Format=Flowed; Original
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670
| Message-ID: <eZstdtNLGHA.3272@xxxxxxxxxxxxxxxxxxxx>
| Newsgroups: microsoft.public.windows.server.migration
| NNTP-Posting-Host: modemcable002.34-70-69.static.videotron.ca 69.70.34.2
| Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!tk2msftngp13.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.windows.server.migration:22383
| X-Tomcat-NG: microsoft.public.windows.server.migration
|
| I have a client that is running NDS 4.11 and Windows 2003 AD.
| The XP client log on with Novell Client to NDS.
|
| The client has already manually created the AD account.
|
| Since the account (NDS and AD) are not synchronized, when the user
access
a
| ressource in Windows 2003, he gets prompted to enter his password.
| Same thing when the user's password expire in NDS.
|
| Now, since the account are already created in AD, how can I use MSDSS to
| "synchronize" Novell and AD?
|
| After reading the MSDSSWhite paper, looks like you need to do an actual
| NDS-AD sync first.
|
| Regards
|
| JP
|
|
|
.
- Follow-Ups:
- Re: MSDSS question
- From: Jason Tan (MSFT)
- Re: MSDSS question
- References:
- MSDSS question
- From: JP Breton
- RE: MSDSS question
- From: Jason Tan (MSFT)
- MSDSS question
- Prev by Date: ADMT profiles question - NT 4.0 to WIN 2003
- Next by Date: moving mailboxes moving to a new domain
- Previous by thread: RE: MSDSS question
- Next by thread: Re: MSDSS question
- Index(es):
Relevant Pages
|