inetorgpersonprevt.ldf on windows 2000 domain for windows 2003 upg

[Guest]

I am preparing a windows 2k domain with Exchange 2k for a windows 2003 sever
upgrade. The plan is to keep exchange at 2000 for now and upgrade the domain
servers to 2003.

In the process I am following MS article 325379 rev 21.3 . In the section
relating to Exch 2k in Win 2K forests(pages 5 and 6) it states to run the
inetorgpersonprevent.ldf script to prevent mangled attribs later (basically
remove the dashes in the name) for objects:
ms-Exch-assistant-name, ms-exch-labeleduri, and ms-exch-house-identifier.

I ran the script and it ran successfully! However, when I use AdSIedit to
view the objects the have not changed at all. Am I looking at the right
objects? Do I need to use a different tool/location to view the changes?

I appreciate your help and info. Thank you.

 

[Meinolf Weber]

Hello Mike,

Here is the path to check for CN=ms-Exch-Assistant-Name, the CN=ms-Exch-LabeledURI,
and the CN=ms-Exch-House-Identifier

a. Start ADSI Edit.
b. Expand Schema [Your_Domain].
c. Expand Cn=Schema, CN=Configuration, CN=your internal names.
d. In the right pane, locate an attribute to verify.
e. Right-click the attribute, and then click Properties.
f. In the Select which properties to view list, click Both.
g. In the Select a property to view list, click LDAPDisplayName.
h. Verify that the LDAPDisplayName value is correct.
i. Repeat steps e through h for each attribute you want to verify.


Think you are talking about Scenario 2? Can you post the logfile from the
scrip? And are you really sure that you copy the script complete and do not
forget the last hyphen?

Anyway, you can also change them by hand with ADSIEdit.

But make sure, that you have backup, if something goes wrong!!!!!!!!!!!!!!!

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.dts-l.org/goodpost.htm

 

[Guest]

That was it!!! I was looking in the wrong place. All three are ok. Thanks
for the detailed info.
Yes, I had performed my latest backup prior to my work...you never know.
Thank you for the advice.

Hello Mike,

Here is the path to check for CN=ms-Exch-Assistant-Name, the CN=ms-Exch-LabeledURI,
and the CN=ms-Exch-House-Identifier

a. Start ADSI Edit.
b. Expand Schema [Your_Domain].
c. Expand Cn=Schema, CN=Configuration, CN=your internal names.
d. In the right pane, locate an attribute to verify.
e. Right-click the attribute, and then click Properties.
f. In the Select which properties to view list, click Both.
g. In the Select a property to view list, click LDAPDisplayName.
h. Verify that the LDAPDisplayName value is correct.
i. Repeat steps e through h for each attribute you want to verify.


Think you are talking about Scenario 2? Can you post the logfile from the
scrip? And are you really sure that you copy the script complete and do not
forget the last hyphen?

Anyway, you can also change them by hand with ADSIEdit.

But make sure, that you have backup, if something goes wrong!!!!!!!!!!!!!!!

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.dts-l.org/goodpost.htm

I am preparing a windows 2k domain with Exchange 2k for a windows 2003
sever upgrade. The plan is to keep exchange at 2000 for now and
upgrade the domain servers to 2003.

In the process I am following MS article 325379 rev 21.3 . In the
section relating to Exch 2k in Win 2K forests(pages 5 and 6) it states
to run the inetorgpersonprevent.ldf script to prevent mangled attribs
later (basically remove the dashes in the name) for objects:
ms-Exch-assistant-name, ms-exch-labeleduri, and
ms-exch-house-identifier.

I ran the script and it ran successfully! However, when I use
AdSIedit to view the objects the have not changed at all. Am I looking
at the right objects? Do I need to use a different tool/location to
view the changes?

I appreciate your help and info. Thank you.