| Author |
Message |
manoa
Guest
|
 Posted:
Fri Jan 21, 2005 3:37 am Post subject:
magled attribute script did not work |
|
|
After running the inetorgpersonprevent.ldf to prevent mangled attribute on
the Schema Master with schema update enabled, I checked the LDAPDisplaynames:
CN=ms-Exch-Assistant-Name, CN=ms-Exch-LabeledURI,and
CN=ms-Exch-House-Identifier and it did not change even though the ldif.log
states
that it successfully modified the attributes. Below is the log:
Connecting to "servername.MYDOMAIN.ORG"
Logging in as current user using SSPI
Importing directory from file "inetorgpersonprevent.ldf"
Loading entries
1: CN=ms-Exch-Assistant-Name,CN=Schema,CN=Configuration,dc=Mydomain,dc=org
Entry DN:
CN=ms-Exch-Assistant-Name,CN=Schema,CN=Configuration,dc=Domain,dc=org
change: modify
Attribute 0) lDAPDisplayName:msExchAssistantName
Entry modified successfully.
2: CN=ms-Exch-LabeledURI,CN=Schema,CN=Configuration,dc=Mydomain,dc=org
Entry DN: CN=ms-Exch-LabeledURI,CN=Schema,CN=Configuration,dc=Mydomain,dc=org
change: modify
Attribute 0) lDAPDisplayName:msExchLabeledURI
Entry modified successfully.
3: CN=ms-Exch-House-Identifier,CN=Schema,CN=Configuration,dc=Mydomain,dc=org
Entry DN:
CN=ms-Exch-House-Identifier,CN=Schema,CN=Configuration,dc=Mydoomain,dc=org
change: modify
Attribute 0) lDAPDisplayName:msExchHouseIdentifier
Entry modified successfully.
4: (null)
Entry DN: (null)
change: modify
Attribute 0) schemaUpdateNow:1
Entry modified successfully.
4 entries modified successfully.
The command has completed successfully
What can I do to resolve this before running ADPREP?
|
|
| Back to top |
|
 |
Rui J.M. Silva
Guest
|
| Posted:
Fri Jan 21, 2005 5:52 pm Post subject:
Re: magled attribute script did not work |
|
|
I guess you followed article Q314649, right?
You must copy till the the last '-'. I remember there was an issue with a
final blank line. Try with one blank line at the end and without.
--
Blog "subject: exchange"
http://spaces.msn.com/members/ehlo/
"manoa" <manoa@discussions.microsoft.com> wrote in message
news:1CCC4303-1029-41E6-A704-82BFDFA91ED7@microsoft.com...
| Quote: | After running the inetorgpersonprevent.ldf to prevent mangled attribute on
the Schema Master with schema update enabled, I checked the
LDAPDisplaynames:
CN=ms-Exch-Assistant-Name, CN=ms-Exch-LabeledURI,and
CN=ms-Exch-House-Identifier and it did not change even though the ldif.log
states
that it successfully modified the attributes. Below is the log:
Connecting to "servername.MYDOMAIN.ORG"
Logging in as current user using SSPI
Importing directory from file "inetorgpersonprevent.ldf"
Loading entries
1: CN=ms-Exch-Assistant-Name,CN=Schema,CN=Configuration,dc=Mydomain,dc=org
Entry DN:
CN=ms-Exch-Assistant-Name,CN=Schema,CN=Configuration,dc=Domain,dc=org
change: modify
Attribute 0) lDAPDisplayName:msExchAssistantName
Entry modified successfully.
2: CN=ms-Exch-LabeledURI,CN=Schema,CN=Configuration,dc=Mydomain,dc=org
Entry DN:
CN=ms-Exch-LabeledURI,CN=Schema,CN=Configuration,dc=Mydomain,dc=org
change: modify
Attribute 0) lDAPDisplayName:msExchLabeledURI
Entry modified successfully.
3:
CN=ms-Exch-House-Identifier,CN=Schema,CN=Configuration,dc=Mydomain,dc=org
Entry DN:
CN=ms-Exch-House-Identifier,CN=Schema,CN=Configuration,dc=Mydoomain,dc=org
change: modify
Attribute 0) lDAPDisplayName:msExchHouseIdentifier
Entry modified successfully.
4: (null)
Entry DN: (null)
change: modify
Attribute 0) schemaUpdateNow:1
Entry modified successfully.
4 entries modified successfully.
The command has completed successfully
What can I do to resolve this before running ADPREP?
|
|
|
| Back to top |
|
|
manoa
Guest
|
| Posted:
Fri Jan 21, 2005 9:01 pm Post subject:
Re: magled attribute script did not work |
|
|
Will running the script numerious time cause any issues? Also, I was told
that you can make the same change through ASDI edit. Has anyone change the
attributes using t6his tool and if so, was there any problems?
"Rui J.M. Silva" wrote:
| Quote: | I guess you followed article Q314649, right?
You must copy till the the last '-'. I remember there was an issue with a
final blank line. Try with one blank line at the end and without.
--
Blog "subject: exchange"
http://spaces.msn.com/members/ehlo/
"manoa" <manoa@discussions.microsoft.com> wrote in message
news:1CCC4303-1029-41E6-A704-82BFDFA91ED7@microsoft.com...
After running the inetorgpersonprevent.ldf to prevent mangled attribute on
the Schema Master with schema update enabled, I checked the
LDAPDisplaynames:
CN=ms-Exch-Assistant-Name, CN=ms-Exch-LabeledURI,and
CN=ms-Exch-House-Identifier and it did not change even though the ldif.log
states
that it successfully modified the attributes. Below is the log:
Connecting to "servername.MYDOMAIN.ORG"
Logging in as current user using SSPI
Importing directory from file "inetorgpersonprevent.ldf"
Loading entries
1: CN=ms-Exch-Assistant-Name,CN=Schema,CN=Configuration,dc=Mydomain,dc=org
Entry DN:
CN=ms-Exch-Assistant-Name,CN=Schema,CN=Configuration,dc=Domain,dc=org
change: modify
Attribute 0) lDAPDisplayName:msExchAssistantName
Entry modified successfully.
2: CN=ms-Exch-LabeledURI,CN=Schema,CN=Configuration,dc=Mydomain,dc=org
Entry DN:
CN=ms-Exch-LabeledURI,CN=Schema,CN=Configuration,dc=Mydomain,dc=org
change: modify
Attribute 0) lDAPDisplayName:msExchLabeledURI
Entry modified successfully.
3:
CN=ms-Exch-House-Identifier,CN=Schema,CN=Configuration,dc=Mydomain,dc=org
Entry DN:
CN=ms-Exch-House-Identifier,CN=Schema,CN=Configuration,dc=Mydoomain,dc=org
change: modify
Attribute 0) lDAPDisplayName:msExchHouseIdentifier
Entry modified successfully.
4: (null)
Entry DN: (null)
change: modify
Attribute 0) schemaUpdateNow:1
Entry modified successfully.
4 entries modified successfully.
The command has completed successfully
What can I do to resolve this before running ADPREP?
|
|
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in