Extending MSDSS and NDS schemas
- From: "chris" <chris@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 26 Apr 2005 12:42:47 -0700
Am currently configuring a Windows 2003 Server (AD domain controller) in a
test environment with a "test" Novell 6.5 Server (NDS/eDirectory). Am in
process of installing SFN5.03 on The "test" Novell server, which belongs to
"Test.AG" tree. When I place this Windows 2003 server into production, the
production Novell servers it will two-way synch with via MSDSS are in "AG"
tree.
In reading FSN5.03 white paper, MSDSS directory schema extension for AD is
required only once for each AD forest (I will have only ONE). Extension for
NDS schema is for specified tree (I have a "test" tree and a production tree).
Questions: If in test environment, I extend AD schema for forest (forest
will not change when this server is put into production), and NDS schema for
tree in "test" environment, can I look forward to any adverse affects when
this server is put into production and synch'd with NDS schema in production
encironment?
Thanks for reading this long-winded message... and for any "heads up"
information. Just trying to plan for surprises before they hit, so to speak.
.
- Follow-Ups:
- RE: Extending MSDSS and NDS schemas
- From: Jason Tan (MSFT)
- RE: Extending MSDSS and NDS schemas
- Prev by Date: RE: Windows Server 2003 in-place upgrade and driver locations?
- Next by Date: Re: upgrading/migrating 2000 domain to 2003
- Previous by thread: NT -> W2K3 DNS question
- Next by thread: RE: Extending MSDSS and NDS schemas
- Index(es):
Relevant Pages
|