| Author |
Message |
manoa
Guest
|
 Posted:
Fri Jan 21, 2005 1:05 am Post subject:
mangled attribute |
|
|
I am following MS article 314649 because I have the E2K schema and I need to
upgrade my W2K to W2K3. It states to create and run a file call
inetorgpersonprevent.ldf to prevent mangled attribute before you run W2K3
adprep /forestprep. I ran the file and the log states that all the
ldapdisplayname attributes were successfully modified. How do I verify that
the LDAPDisplaynames: CN=ms-Exch-Assistant-Name, CN=ms-Exch-LabeledURI, and
CN=ms-Exch-House-Identifier changed to msExchAssistantName, msExchLabeledURI,
and msExchHouseIdentifier?
|
|
| Back to top |
|
 |
John Oliver, Jr. [MVP]
Guest
|
| Posted:
Fri Jan 21, 2005 2:02 am Post subject:
Re: mangled attribute |
|
|
You will need to run ADSI edit. You will need to install the Windows 2000 or
2003 Support Tools.
--
John Oliver, Jr.
MCSE, MCT, CCNA, Exchange MVP
Microsoft Certified Partner
"manoa" <manoa@discussions.microsoft.com> wrote in message
news:FFF65651-0639-4CA7-8176-DEF8FB70564D@microsoft.com...
| Quote: | I am following MS article 314649 because I have the E2K schema and I need
to
upgrade my W2K to W2K3. It states to create and run a file call
inetorgpersonprevent.ldf to prevent mangled attribute before you run W2K3
adprep /forestprep. I ran the file and the log states that all the
ldapdisplayname attributes were successfully modified. How do I verify
that
the LDAPDisplaynames: CN=ms-Exch-Assistant-Name, CN=ms-Exch-LabeledURI,
and
CN=ms-Exch-House-Identifier changed to msExchAssistantName,
msExchLabeledURI,
and msExchHouseIdentifier? |
|
|
| Back to top |
|
|
manoa
Guest
|
| Posted:
Fri Jan 21, 2005 2:23 am Post subject:
Re: mangled attribute |
|
|
Thats what I have done to verify and the the LDAPDisplaynames:
CN=ms-Exch-Assistant-Name, CN=ms-Exch-LabeledURI, and
CN=ms-Exch-House-Identifier 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
"John Oliver, Jr. [MVP]" wrote:
| Quote: | You will need to run ADSI edit. You will need to install the Windows 2000 or
2003 Support Tools.
--
John Oliver, Jr.
MCSE, MCT, CCNA, Exchange MVP
Microsoft Certified Partner
"manoa" <manoa@discussions.microsoft.com> wrote in message
news:FFF65651-0639-4CA7-8176-DEF8FB70564D@microsoft.com...
I am following MS article 314649 because I have the E2K schema and I need
to
upgrade my W2K to W2K3. It states to create and run a file call
inetorgpersonprevent.ldf to prevent mangled attribute before you run W2K3
adprep /forestprep. I ran the file and the log states that all the
ldapdisplayname attributes were successfully modified. How do I verify
that
the LDAPDisplaynames: CN=ms-Exch-Assistant-Name, CN=ms-Exch-LabeledURI,
and
CN=ms-Exch-House-Identifier changed to msExchAssistantName,
msExchLabeledURI,
and msExchHouseIdentifier?
|
|
|
| Back to top |
|
|
John Oliver, Jr. [MVP]
Guest
|
| Posted:
Fri Jan 21, 2005 8:10 am Post subject:
Re: mangled attribute |
|
|
You can change them within ADSI edit if they are not correct. I prefer to
change them within ADSI edit myself without running the script.
--
John Oliver, Jr.
MCSE, MCT, CCNA, Exchange MVP
Microsoft Certified Partner
"manoa" <manoa@discussions.microsoft.com> wrote in message
news:F4516FC1-9CDC-4D4E-85AD-98BB026391EA@microsoft.com...
| Quote: | Thats what I have done to verify and the the LDAPDisplaynames:
CN=ms-Exch-Assistant-Name, CN=ms-Exch-LabeledURI, and
CN=ms-Exch-House-Identifier 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
"John Oliver, Jr. [MVP]" wrote:
You will need to run ADSI edit. You will need to install the Windows 2000
or
2003 Support Tools.
--
John Oliver, Jr.
MCSE, MCT, CCNA, Exchange MVP
Microsoft Certified Partner
"manoa" <manoa@discussions.microsoft.com> wrote in message
news:FFF65651-0639-4CA7-8176-DEF8FB70564D@microsoft.com...
I am following MS article 314649 because I have the E2K schema and I
need
to
upgrade my W2K to W2K3. It states to create and run a file call
inetorgpersonprevent.ldf to prevent mangled attribute before you run
W2K3
adprep /forestprep. I ran the file and the log states that all the
ldapdisplayname attributes were successfully modified. How do I verify
that
the LDAPDisplaynames: CN=ms-Exch-Assistant-Name, CN=ms-Exch-LabeledURI,
and
CN=ms-Exch-House-Identifier changed to msExchAssistantName,
msExchLabeledURI,
and msExchHouseIdentifier?
|
|
|
| Back to top |
|
|
manoa
Guest
|
| Posted:
Fri Jan 21, 2005 8:59 pm Post subject:
Re: mangled attribute |
|
|
So, I can basically use ASDI edit and change the attribute of
CN=ms-Exch-Assistant-Name, CN=ms-Exch-LabeledURI, and
CN=ms-Exch-House-Identifier to msExchAssistantName, msExchLabeledURI, and
msExchHouseIdentifier? Why wouldn't MS offer this as a solution instead of
running those script? Is there any steps that needs to be taken when I use
ASDI to change these attributes?
"John Oliver, Jr. [MVP]" wrote:
| Quote: | You can change them within ADSI edit if they are not correct. I prefer to
change them within ADSI edit myself without running the script.
--
John Oliver, Jr.
MCSE, MCT, CCNA, Exchange MVP
Microsoft Certified Partner
"manoa" <manoa@discussions.microsoft.com> wrote in message
news:F4516FC1-9CDC-4D4E-85AD-98BB026391EA@microsoft.com...
Thats what I have done to verify and the the LDAPDisplaynames:
CN=ms-Exch-Assistant-Name, CN=ms-Exch-LabeledURI, and
CN=ms-Exch-House-Identifier 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
"John Oliver, Jr. [MVP]" wrote:
You will need to run ADSI edit. You will need to install the Windows 2000
or
2003 Support Tools.
--
John Oliver, Jr.
MCSE, MCT, CCNA, Exchange MVP
Microsoft Certified Partner
"manoa" <manoa@discussions.microsoft.com> wrote in message
news:FFF65651-0639-4CA7-8176-DEF8FB70564D@microsoft.com...
I am following MS article 314649 because I have the E2K schema and I
need
to
upgrade my W2K to W2K3. It states to create and run a file call
inetorgpersonprevent.ldf to prevent mangled attribute before you run
W2K3
adprep /forestprep. I ran the file and the log states that all the
ldapdisplayname attributes were successfully modified. How do I verify
that
the LDAPDisplaynames: CN=ms-Exch-Assistant-Name, CN=ms-Exch-LabeledURI,
and
CN=ms-Exch-House-Identifier changed to msExchAssistantName,
msExchLabeledURI,
and msExchHouseIdentifier?
|
|
|
| Back to top |
|
|
John Oliver, Jr. [MVP]
Guest
|
| Posted:
Sat Jan 22, 2005 4:02 am Post subject:
Re: mangled attribute |
|
|
Nope, that is basically what the script does. The reason Microsoft
recommends the script file is because most admins do not know how to use
ADSI edit and unless you know what you are doing, you should not be using
it. Bad things can happen if you change the wrong key.
--
John Oliver, Jr.
MCSE, MCT, CCNA, Exchange MVP
Microsoft Certified Partner
"manoa" <manoa@discussions.microsoft.com> wrote in message
news:AFE834A8-6A7D-42E9-9373-9202139B5D08@microsoft.com...
| Quote: | So, I can basically use ASDI edit and change the attribute of
CN=ms-Exch-Assistant-Name, CN=ms-Exch-LabeledURI, and
CN=ms-Exch-House-Identifier to msExchAssistantName, msExchLabeledURI, and
msExchHouseIdentifier? Why wouldn't MS offer this as a solution instead
of
running those script? Is there any steps that needs to be taken when I
use
ASDI to change these attributes?
"John Oliver, Jr. [MVP]" wrote:
You can change them within ADSI edit if they are not correct. I prefer
to
change them within ADSI edit myself without running the script.
--
John Oliver, Jr.
MCSE, MCT, CCNA, Exchange MVP
Microsoft Certified Partner
"manoa" <manoa@discussions.microsoft.com> wrote in message
news:F4516FC1-9CDC-4D4E-85AD-98BB026391EA@microsoft.com...
Thats what I have done to verify and the the LDAPDisplaynames:
CN=ms-Exch-Assistant-Name, CN=ms-Exch-LabeledURI, and
CN=ms-Exch-House-Identifier 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
"John Oliver, Jr. [MVP]" wrote:
You will need to run ADSI edit. You will need to install the Windows
2000
or
2003 Support Tools.
--
John Oliver, Jr.
MCSE, MCT, CCNA, Exchange MVP
Microsoft Certified Partner
"manoa" <manoa@discussions.microsoft.com> wrote in message
news:FFF65651-0639-4CA7-8176-DEF8FB70564D@microsoft.com...
I am following MS article 314649 because I have the E2K schema and I
need
to
upgrade my W2K to W2K3. It states to create and run a file call
inetorgpersonprevent.ldf to prevent mangled attribute before you run
W2K3
adprep /forestprep. I ran the file and the log states that all the
ldapdisplayname attributes were successfully modified. How do I
verify
that
the LDAPDisplaynames: CN=ms-Exch-Assistant-Name,
CN=ms-Exch-LabeledURI,
and
CN=ms-Exch-House-Identifier changed to msExchAssistantName,
msExchLabeledURI,
and msExchHouseIdentifier?
|
|
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in