Re: ad 2003 upgrade

Tech-Archive recommends: Fix windows errors by optimizing your registry

"" wrote:
> For a AD2003 upgrade ms article 3225379 warns that an adprep
> /forestprep
> mangles exchange 2000 schema. Does this still occur if you
> are running both
> Exchange 2000 and Exchange 2003?

What the inetorgfix does is correcting the ldapdisplayname of three
attributes. Use ADSIEDIT, connect to the schema container, open the
properties of the attributes mentioned and check if the
ldapdisplayname is correct defined as mentioned in the article.

--
Posted using the http://www.windowsforumz.com interface, at author's request
Articles individually checked for conformance to usenet standards
Topic URL: http://www.windowsforumz.com/ad-2003-upgrade-ftopict446261.html
Visit Topic URL to contact author (reg. req'd). Report abuse: http://www.windowsforumz.com/eform.php?p=1510417
.

Relevant Pages

  • Re: 2003 Domain Upgrade - InetOrgPerson Expected Failure didnt happen!
    ... >> the Schema MMC snapin, but this doesnt allow you to look at properties ... The Exchange 2000 introduced an attributeSchema ... > that had an lDAPDisplayName of secretary this would have conflicted with ... > changetype: ntdsSchemaModify ...
    (microsoft.public.windows.server.active_directory)
  • Re: 2003 Domain Upgrade - InetOrgPerson Expected Failure didnt happen!
    ... > the Schema MMC snapin, but this doesnt allow you to look at properties ... The Exchange 2000 introduced an attributeSchema ... that had an lDAPDisplayName of secretary this would have conflicted with the ... changetype: ntdsSchemaModify ...
    (microsoft.public.windows.server.active_directory)
  • Re: extend permissions
    ... fixed - had to remove the ldapdisplayname. ... >> Remove governsId, CARs are not schema objects, they don't have or need ... >> Finally, no need to refresh the schema, the CAR is not a part of the schema. ... >> Dmitri Gavrilov ...
    (microsoft.public.windows.server.active_directory)
  • Re: 2003 Domain Upgrade - InetOrgPerson Expected Failure didnt happen!
    ... is lDAPDisplayName msExchAssistantName or secretary ... > InetOrgPerson schema naming conflicts, ... > I've set up a development domain that exactly mirrors our production ...
    (microsoft.public.windows.server.active_directory)