|
server
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
legacyExchangeDN - May I change it to a user?I have a Exchange2K3 server on a Windows2K3. It is an upgrade of Exchange5.5
on WinNT. The lay out was a bit different, and some mailboxes have inherited "unwanted" values in that "legacyExchangeDN" property: recipient containers which no longer exist, mailbox (hidden) names from a different naming policy, etcetera. May I change at will that property for several users? ... without having to reinstall my whole server, of course ;-) -- TIA RØ Why? Is it broken?
It *could* be changed, although I advise you be careful changing that. Test the heck out of it in your environment. http://support.microsoft.com/default.aspx?scid=kb;en-us;273863&Product=exch2003 Show quoteHide quote "RodeCa" <rod***@terra.BASURA.es> wrote in message news:%23ziEylAJGHA.3944@tk2msftngp13.phx.gbl... >I have a Exchange2K3 server on a Windows2K3. It is an upgrade of >Exchange5.5 > on WinNT. > > The lay out was a bit different, and some mailboxes have inherited > "unwanted" values in that "legacyExchangeDN" property: recipient > containers > which no longer exist, mailbox (hidden) names from a different naming > policy, etcetera. > > May I change at will that property for several users? ... without having > to > reinstall my whole server, of course ;-) > > -- > TIA > RØ > > > > > It was only a question of cosmetics. Nothing is broken.
I'll keep them as they are. -- Show quoteHide quoteThank you RØ "Al Mulnick" <amulnick_No_SPAM@ncDOTrr.com> escribió en el mensaje news:%23SLiCFBJGHA.2064@TK2MSFTNGP09.phx.gbl... > Why? Is it broken? > It *could* be changed, although I advise you be careful changing that. > Test the heck out of it in your environment. > > http://support.microsoft.com/default.aspx?scid=kb;en-us;273863&Product=exch2003 > > "RodeCa" <rod***@terra.BASURA.es> wrote in message > news:%23ziEylAJGHA.3944@tk2msftngp13.phx.gbl... >>I have a Exchange2K3 server on a Windows2K3. It is an upgrade of >>Exchange5.5 >> on WinNT. >> >> The lay out was a bit different, and some mailboxes have inherited >> "unwanted" values in that "legacyExchangeDN" property: recipient >> containers >> which no longer exist, mailbox (hidden) names from a different naming >> policy, etcetera. >> >> May I change at will that property for several users? ... without having >> to >> reinstall my whole server, of course ;-) >> >> -- >> TIA >> RØ >> >> >> >> >> > > At will? The short answer is no.
To change legacyexchangedn you need to export the affected users mail to pst, remove the exchange attribs from their account, delete the old mailbox, and then add the exchange attribs back (creating a new mailbox) and then exmerge the data back in. The reason for this is that the exchange store uses legacy exchangedn as a security ID. Show quoteHide quote "RodeCa" <rod***@terra.BASURA.es> wrote in message news:%23ziEylAJGHA.3944@tk2msftngp13.phx.gbl... > I have a Exchange2K3 server on a Windows2K3. It is an upgrade of Exchange5.5 > on WinNT. > > The lay out was a bit different, and some mailboxes have inherited > "unwanted" values in that "legacyExchangeDN" property: recipient containers > which no longer exist, mailbox (hidden) names from a different naming > policy, etcetera. > > May I change at will that property for several users? ... without having to > reinstall my whole server, of course ;-) > > -- > TIA > RØ > > > > > Excuse me?
That's just not true at all. If you change legacyExchangeDN, then replies to messages the user sent to others will fail [1], calendaring meetings may get disconnected [1], and free/busy will need to be re-published [2]. You'll also have to rebuild the offline address book and push it to any systems that use it (laptops). [1] This is solved by also adding an x500 type secondary proxy address to the mailbox using the old legacyExchangeDN value as the address. [3] [2] This is solved once the user logs on and schedules a meeting for themselves - Outlook will re-publish the free/busy. So, "at will" might be a little laissez faire, but it can certainly be changed. It's not in tue UI, so you'll need to use adsiedit or dsmod or ldifde or vbscript. You probably want to make it match the "alias" or mailNickname [4] value, and also make sure that at least one of the SMTP addresses on the mailbox uas the same value as it's user portion. [3] yes, footnote foul, I know. call them belly notes. [4] "alias" is the display name of the mailNickname AD property in ADUC Show quoteHide quote "Tom Felts" <tfelts@nospam.mckennalong.com> wrote in message news:uSZpaWDJGHA.1180@TK2MSFTNGP09.phx.gbl... > At will? The short answer is no. > To change legacyexchangedn you need to export the affected users mail to > pst, remove the exchange attribs from their account, delete the old > mailbox, > and then add the exchange attribs back (creating a new mailbox) and then > exmerge the data back in. The reason for this is that the exchange store > uses legacy exchangedn as a security > ID. > > > > > "RodeCa" <rod***@terra.BASURA.es> wrote in message > news:%23ziEylAJGHA.3944@tk2msftngp13.phx.gbl... >> I have a Exchange2K3 server on a Windows2K3. It is an upgrade of > Exchange5.5 >> on WinNT. >> >> The lay out was a bit different, and some mailboxes have inherited >> "unwanted" values in that "legacyExchangeDN" property: recipient > containers >> which no longer exist, mailbox (hidden) names from a different naming >> policy, etcetera. >> >> May I change at will that property for several users? ... without having > to >> reinstall my whole server, of course ;-) >> >> -- >> TIA >> RØ >> >> >> >> >> > > The distinction needs to be made as to whether the environment was migrated
from 5.5 to 2k and 2k3 via ADC. If that is the case, then what I stated is true. Otherwise your understanding is correct. Show quoteHide quote "andy webb" <awebb@swinc.com.spamsucks.com> wrote in message news:OyxOo1DJGHA.1388@TK2MSFTNGP11.phx.gbl... > Excuse me? > > That's just not true at all. > > If you change legacyExchangeDN, then replies to messages the user sent to > others will fail [1], calendaring meetings may get disconnected [1], and > free/busy will need to be re-published [2]. You'll also have to rebuild the > offline address book and push it to any systems that use it (laptops). > > [1] This is solved by also adding an x500 type secondary proxy address to > the mailbox using the old legacyExchangeDN value as the address. [3] > [2] This is solved once the user logs on and schedules a meeting for > themselves - Outlook will re-publish the free/busy. > > So, "at will" might be a little laissez faire, but it can certainly be > changed. It's not in tue UI, so you'll need to use adsiedit or dsmod or > ldifde or vbscript. You probably want to make it match the "alias" or > mailNickname [4] value, and also make sure that at least one of the SMTP > addresses on the mailbox uas the same value as it's user portion. > > [3] yes, footnote foul, I know. call them belly notes. > [4] "alias" is the display name of the mailNickname AD property in ADUC > > > "Tom Felts" <tfelts@nospam.mckennalong.com> wrote in message > news:uSZpaWDJGHA.1180@TK2MSFTNGP09.phx.gbl... > > At will? The short answer is no. > > To change legacyexchangedn you need to export the affected users mail to > > pst, remove the exchange attribs from their account, delete the old > > mailbox, > > and then add the exchange attribs back (creating a new mailbox) and then > > exmerge the data back in. The reason for this is that the exchange store > > uses legacy exchangedn as a security > > ID. > > > > > > > > > > "RodeCa" <rod***@terra.BASURA.es> wrote in message > > news:%23ziEylAJGHA.3944@tk2msftngp13.phx.gbl... > >> I have a Exchange2K3 server on a Windows2K3. It is an upgrade of > > Exchange5.5 > >> on WinNT. > >> > >> The lay out was a bit different, and some mailboxes have inherited > >> "unwanted" values in that "legacyExchangeDN" property: recipient > > containers > >> which no longer exist, mailbox (hidden) names from a different naming > >> policy, etcetera. > >> > >> May I change at will that property for several users? ... without having > > to > >> reinstall my whole server, of course ;-) > >> > >> -- > >> TIA > >> RØ > >> > >> > >> > >> > >> > > > > > > If it's E2K or E2K3, then what I stated is true.
I understood the question to be about an environment that is no longer on 5.5. On 5.5 the answer is different as you say (though there's no legacyExchangeDN property of course, only the directoryName property). don't think that's in play here though. Show quoteHide quote "Tom Felts" <tfelts@nospam.mckennalong.com> wrote in message news:uwGW6FEJGHA.524@TK2MSFTNGP09.phx.gbl... > The distinction needs to be made as to whether the environment was > migrated > from 5.5 to 2k and 2k3 via ADC. If that is the case, then what I stated > is > true. Otherwise your understanding is correct. > > "andy webb" <awebb@swinc.com.spamsucks.com> wrote in message > news:OyxOo1DJGHA.1388@TK2MSFTNGP11.phx.gbl... >> Excuse me? >> >> That's just not true at all. >> >> If you change legacyExchangeDN, then replies to messages the user sent to >> others will fail [1], calendaring meetings may get disconnected [1], and >> free/busy will need to be re-published [2]. You'll also have to rebuild > the >> offline address book and push it to any systems that use it (laptops). >> >> [1] This is solved by also adding an x500 type secondary proxy address to >> the mailbox using the old legacyExchangeDN value as the address. [3] >> [2] This is solved once the user logs on and schedules a meeting for >> themselves - Outlook will re-publish the free/busy. >> >> So, "at will" might be a little laissez faire, but it can certainly be >> changed. It's not in tue UI, so you'll need to use adsiedit or dsmod or >> ldifde or vbscript. You probably want to make it match the "alias" or >> mailNickname [4] value, and also make sure that at least one of the SMTP >> addresses on the mailbox uas the same value as it's user portion. >> >> [3] yes, footnote foul, I know. call them belly notes. >> [4] "alias" is the display name of the mailNickname AD property in ADUC >> >> >> "Tom Felts" <tfelts@nospam.mckennalong.com> wrote in message >> news:uSZpaWDJGHA.1180@TK2MSFTNGP09.phx.gbl... >> > At will? The short answer is no. >> > To change legacyexchangedn you need to export the affected users mail >> > to >> > pst, remove the exchange attribs from their account, delete the old >> > mailbox, >> > and then add the exchange attribs back (creating a new mailbox) and >> > then >> > exmerge the data back in. The reason for this is that the exchange > store >> > uses legacy exchangedn as a security >> > ID. >> > >> > >> > >> > >> > "RodeCa" <rod***@terra.BASURA.es> wrote in message >> > news:%23ziEylAJGHA.3944@tk2msftngp13.phx.gbl... >> >> I have a Exchange2K3 server on a Windows2K3. It is an upgrade of >> > Exchange5.5 >> >> on WinNT. >> >> >> >> The lay out was a bit different, and some mailboxes have inherited >> >> "unwanted" values in that "legacyExchangeDN" property: recipient >> > containers >> >> which no longer exist, mailbox (hidden) names from a different naming >> >> policy, etcetera. >> >> >> >> May I change at will that property for several users? ... without > having >> > to >> >> reinstall my whole server, of course ;-) >> >> >> >> -- >> >> TIA >> >> RØ >> >> >> >> >> >> >> >> >> >> >> > >> > >> >> > > So I must deduct that the term "legacy" is some way ambiguous. I thought it
was a matter of backward compatibility. As it was only a cosmetic wish :-) , I'll keep them as they are: not so important for so much danger ;-). -- Show quoteHide quoteThank to you all RØ P.S.: it is E2K3 migrated from 5.5 via ADC. That is why I thought it was truly "legacy". And it is no longer 5.5. "andy webb" <awebb@swinc.com.spamsucks.com> escribió en el mensaje news:OB9V8IEJGHA.1124@TK2MSFTNGP10.phx.gbl... > If it's E2K or E2K3, then what I stated is true. > > I understood the question to be about an environment that is no longer on > 5.5. > > On 5.5 the answer is different as you say (though there's no > legacyExchangeDN property of course, only the directoryName property). > don't think that's in play here though. > > "Tom Felts" <tfelts@nospam.mckennalong.com> wrote in message > news:uwGW6FEJGHA.524@TK2MSFTNGP09.phx.gbl... >> The distinction needs to be made as to whether the environment was >> migrated >> from 5.5 to 2k and 2k3 via ADC. If that is the case, then what I stated >> is >> true. Otherwise your understanding is correct. >> >> "andy webb" <awebb@swinc.com.spamsucks.com> wrote in message >> news:OyxOo1DJGHA.1388@TK2MSFTNGP11.phx.gbl... >>> Excuse me? >>> >>> That's just not true at all. >>> >>> If you change legacyExchangeDN, then replies to messages the user sent >>> to >>> others will fail [1], calendaring meetings may get disconnected [1], and >>> free/busy will need to be re-published [2]. You'll also have to rebuild >> the >>> offline address book and push it to any systems that use it (laptops). >>> >>> [1] This is solved by also adding an x500 type secondary proxy address >>> to >>> the mailbox using the old legacyExchangeDN value as the address. [3] >>> [2] This is solved once the user logs on and schedules a meeting for >>> themselves - Outlook will re-publish the free/busy. >>> >>> So, "at will" might be a little laissez faire, but it can certainly be >>> changed. It's not in tue UI, so you'll need to use adsiedit or dsmod or >>> ldifde or vbscript. You probably want to make it match the "alias" or >>> mailNickname [4] value, and also make sure that at least one of the SMTP >>> addresses on the mailbox uas the same value as it's user portion. >>> >>> [3] yes, footnote foul, I know. call them belly notes. >>> [4] "alias" is the display name of the mailNickname AD property in ADUC >>> >>> >>> "Tom Felts" <tfelts@nospam.mckennalong.com> wrote in message >>> news:uSZpaWDJGHA.1180@TK2MSFTNGP09.phx.gbl... >>> > At will? The short answer is no. >>> > To change legacyexchangedn you need to export the affected users mail >>> > to >>> > pst, remove the exchange attribs from their account, delete the old >>> > mailbox, >>> > and then add the exchange attribs back (creating a new mailbox) and >>> > then >>> > exmerge the data back in. The reason for this is that the exchange >> store >>> > uses legacy exchangedn as a security >>> > ID. >>> > >>> > >>> > >>> > >>> > "RodeCa" <rod***@terra.BASURA.es> wrote in message >>> > news:%23ziEylAJGHA.3944@tk2msftngp13.phx.gbl... >>> >> I have a Exchange2K3 server on a Windows2K3. It is an upgrade of >>> > Exchange5.5 >>> >> on WinNT. >>> >> >>> >> The lay out was a bit different, and some mailboxes have inherited >>> >> "unwanted" values in that "legacyExchangeDN" property: recipient >>> > containers >>> >> which no longer exist, mailbox (hidden) names from a different naming >>> >> policy, etcetera. >>> >> >>> >> May I change at will that property for several users? ... without >> having >>> > to >>> >> reinstall my whole server, of course ;-) >>> >> >>> >> -- >>> >> TIA >>> >> RØ >>> >> >>> >> >>> >> >>> >> >>> >> >>> > >>> > >>> >>> >> >> > > if you're still having problems try priasoft tools. they work great...
way better than exmerge for sure. http://www.priasoft.com. david it's the legacy DN in relation to the Active Directory DN.
But that doesn't mean it's not used. Quite to the contrary. In order for Exchange 2000 and 2003 to work in mixed mode 5.5 environments and in order for MAPI clients to work, that value is still important. Show quoteHide quote "RodeCa" <rod***@terra.BASURA.es> wrote in message news:ua2qjtbJGHA.3936@TK2MSFTNGP12.phx.gbl... > So I must deduct that the term "legacy" is some way ambiguous. I thought > it was a matter of backward compatibility. > > As it was only a cosmetic wish :-) , I'll keep them as they are: not so > important for so much danger ;-). > > -- > Thank to you all > RØ > > P.S.: it is E2K3 migrated from 5.5 via ADC. That is why I thought it was > truly "legacy". And it is no longer 5.5. > > > "andy webb" <awebb@swinc.com.spamsucks.com> escribió en el mensaje > news:OB9V8IEJGHA.1124@TK2MSFTNGP10.phx.gbl... >> If it's E2K or E2K3, then what I stated is true. >> >> I understood the question to be about an environment that is no longer on >> 5.5. >> >> On 5.5 the answer is different as you say (though there's no >> legacyExchangeDN property of course, only the directoryName property). >> don't think that's in play here though. >> >> "Tom Felts" <tfelts@nospam.mckennalong.com> wrote in message >> news:uwGW6FEJGHA.524@TK2MSFTNGP09.phx.gbl... >>> The distinction needs to be made as to whether the environment was >>> migrated >>> from 5.5 to 2k and 2k3 via ADC. If that is the case, then what I stated >>> is >>> true. Otherwise your understanding is correct. >>> >>> "andy webb" <awebb@swinc.com.spamsucks.com> wrote in message >>> news:OyxOo1DJGHA.1388@TK2MSFTNGP11.phx.gbl... >>>> Excuse me? >>>> >>>> That's just not true at all. >>>> >>>> If you change legacyExchangeDN, then replies to messages the user sent >>>> to >>>> others will fail [1], calendaring meetings may get disconnected [1], >>>> and >>>> free/busy will need to be re-published [2]. You'll also have to >>>> rebuild >>> the >>>> offline address book and push it to any systems that use it (laptops). >>>> >>>> [1] This is solved by also adding an x500 type secondary proxy address >>>> to >>>> the mailbox using the old legacyExchangeDN value as the address. [3] >>>> [2] This is solved once the user logs on and schedules a meeting for >>>> themselves - Outlook will re-publish the free/busy. >>>> >>>> So, "at will" might be a little laissez faire, but it can certainly be >>>> changed. It's not in tue UI, so you'll need to use adsiedit or dsmod >>>> or >>>> ldifde or vbscript. You probably want to make it match the "alias" or >>>> mailNickname [4] value, and also make sure that at least one of the >>>> SMTP >>>> addresses on the mailbox uas the same value as it's user portion. >>>> >>>> [3] yes, footnote foul, I know. call them belly notes. >>>> [4] "alias" is the display name of the mailNickname AD property in ADUC >>>> >>>> >>>> "Tom Felts" <tfelts@nospam.mckennalong.com> wrote in message >>>> news:uSZpaWDJGHA.1180@TK2MSFTNGP09.phx.gbl... >>>> > At will? The short answer is no. >>>> > To change legacyexchangedn you need to export the affected users mail >>>> > to >>>> > pst, remove the exchange attribs from their account, delete the old >>>> > mailbox, >>>> > and then add the exchange attribs back (creating a new mailbox) and >>>> > then >>>> > exmerge the data back in. The reason for this is that the exchange >>> store >>>> > uses legacy exchangedn as a security >>>> > ID. >>>> > >>>> > >>>> > >>>> > >>>> > "RodeCa" <rod***@terra.BASURA.es> wrote in message >>>> > news:%23ziEylAJGHA.3944@tk2msftngp13.phx.gbl... >>>> >> I have a Exchange2K3 server on a Windows2K3. It is an upgrade of >>>> > Exchange5.5 >>>> >> on WinNT. >>>> >> >>>> >> The lay out was a bit different, and some mailboxes have inherited >>>> >> "unwanted" values in that "legacyExchangeDN" property: recipient >>>> > containers >>>> >> which no longer exist, mailbox (hidden) names from a different >>>> >> naming >>>> >> policy, etcetera. >>>> >> >>>> >> May I change at will that property for several users? ... without >>> having >>>> > to >>>> >> reinstall my whole server, of course ;-) >>>> >> >>>> >> -- >>>> >> TIA >>>> >> RØ >>>> >> >>>> >> >>>> >> >>>> >> >>>> >> >>>> > >>>> > >>>> >>>> >>> >>> >> >> > > It's also useful to know that they can be changed - occasionally odd things
happen and it needs to be adjusted even in a pure 2003 environment (not often, but occasionally). Show quoteHide quote "RodeCa" <rod***@terra.BASURA.es> wrote in message news:ua2qjtbJGHA.3936@TK2MSFTNGP12.phx.gbl... > So I must deduct that the term "legacy" is some way ambiguous. I thought > it was a matter of backward compatibility. > > As it was only a cosmetic wish :-) , I'll keep them as they are: not so > important for so much danger ;-). > > -- > Thank to you all > RØ > > P.S.: it is E2K3 migrated from 5.5 via ADC. That is why I thought it was > truly "legacy". And it is no longer 5.5. > > > "andy webb" <awebb@swinc.com.spamsucks.com> escribió en el mensaje > news:OB9V8IEJGHA.1124@TK2MSFTNGP10.phx.gbl... >> If it's E2K or E2K3, then what I stated is true. >> >> I understood the question to be about an environment that is no longer on >> 5.5. >> >> On 5.5 the answer is different as you say (though there's no >> legacyExchangeDN property of course, only the directoryName property). >> don't think that's in play here though. >> >> "Tom Felts" <tfelts@nospam.mckennalong.com> wrote in message >> news:uwGW6FEJGHA.524@TK2MSFTNGP09.phx.gbl... >>> The distinction needs to be made as to whether the environment was >>> migrated >>> from 5.5 to 2k and 2k3 via ADC. If that is the case, then what I stated >>> is >>> true. Otherwise your understanding is correct. >>> >>> "andy webb" <awebb@swinc.com.spamsucks.com> wrote in message >>> news:OyxOo1DJGHA.1388@TK2MSFTNGP11.phx.gbl... >>>> Excuse me? >>>> >>>> That's just not true at all. >>>> >>>> If you change legacyExchangeDN, then replies to messages the user sent >>>> to >>>> others will fail [1], calendaring meetings may get disconnected [1], >>>> and >>>> free/busy will need to be re-published [2]. You'll also have to >>>> rebuild >>> the >>>> offline address book and push it to any systems that use it (laptops). >>>> >>>> [1] This is solved by also adding an x500 type secondary proxy address >>>> to >>>> the mailbox using the old legacyExchangeDN value as the address. [3] >>>> [2] This is solved once the user logs on and schedules a meeting for >>>> themselves - Outlook will re-publish the free/busy. >>>> >>>> So, "at will" might be a little laissez faire, but it can certainly be >>>> changed. It's not in tue UI, so you'll need to use adsiedit or dsmod >>>> or >>>> ldifde or vbscript. You probably want to make it match the "alias" or >>>> mailNickname [4] value, and also make sure that at least one of the >>>> SMTP >>>> addresses on the mailbox uas the same value as it's user portion. >>>> >>>> [3] yes, footnote foul, I know. call them belly notes. >>>> [4] "alias" is the display name of the mailNickname AD property in ADUC >>>> >>>> >>>> "Tom Felts" <tfelts@nospam.mckennalong.com> wrote in message >>>> news:uSZpaWDJGHA.1180@TK2MSFTNGP09.phx.gbl... >>>> > At will? The short answer is no. >>>> > To change legacyexchangedn you need to export the affected users mail >>>> > to >>>> > pst, remove the exchange attribs from their account, delete the old >>>> > mailbox, >>>> > and then add the exchange attribs back (creating a new mailbox) and >>>> > then >>>> > exmerge the data back in. The reason for this is that the exchange >>> store >>>> > uses legacy exchangedn as a security >>>> > ID. >>>> > >>>> > >>>> > >>>> > >>>> > "RodeCa" <rod***@terra.BASURA.es> wrote in message >>>> > news:%23ziEylAJGHA.3944@tk2msftngp13.phx.gbl... >>>> >> I have a Exchange2K3 server on a Windows2K3. It is an upgrade of >>>> > Exchange5.5 >>>> >> on WinNT. >>>> >> >>>> >> The lay out was a bit different, and some mailboxes have inherited >>>> >> "unwanted" values in that "legacyExchangeDN" property: recipient >>>> > containers >>>> >> which no longer exist, mailbox (hidden) names from a different >>>> >> naming >>>> >> policy, etcetera. >>>> >> >>>> >> May I change at will that property for several users? ... without >>> having >>>> > to >>>> >> reinstall my whole server, of course ;-) >>>> >> >>>> >> -- >>>> >> TIA >>>> >> RØ >>>> >> >>>> >> >>>> >> >>>> >> >>>> >> >>>> > >>>> > >>>> >>>> >>> >>> >> >> > > This thread has been very educational to me and it explains some odd things
happening in our exchange environment. Our current organization has many exchange servers and several administrative groups. Some of those admin groups are now empty because they were only used for the migration from Exchange 5.5. (Don’t ask, it is a unique environment.) One of the empty admin groups is the “First Administrative Groupâ€. We have been afraid to remove the old administrative groups because of our migration from 5.5. The “First Administrative Group†is still listed in our legacyExchangeDN. The one odd, annoying problem that we have seen with this is that we have many mail-enabled groups that list the “First Administrative Group†as their administrative group. Our current exchange organization does not include any 5.5 servers and is in the “Native Mode (no pre-Exchange 2000 servers)†operating mode. We are currently getting ready to deploy a more centralized exchange solution and we would like to clean up some of the exchange organization. I would like to change the legacyExchangeDN and remove the empty administrative groups. I want to know how changing the legacyExchangeDN and removing the “First Administrative Group†would affect us since the only exchange objects associated with the “First Administrative Group†are mail-enabled groups? Thanks, --Nick Show quoteHide quote "andy webb" wrote: > It's also useful to know that they can be changed - occasionally odd things > happen and it needs to be adjusted even in a pure 2003 environment (not > often, but occasionally). > > > "RodeCa" <rod***@terra.BASURA.es> wrote in message > news:ua2qjtbJGHA.3936@TK2MSFTNGP12.phx.gbl... > > So I must deduct that the term "legacy" is some way ambiguous. I thought > > it was a matter of backward compatibility. > > > > As it was only a cosmetic wish :-) , I'll keep them as they are: not so > > important for so much danger ;-). > > > > -- > > Thank to you all > > RØ > > > > P.S.: it is E2K3 migrated from 5.5 via ADC. That is why I thought it was > > truly "legacy". And it is no longer 5.5. > > > > > > "andy webb" <awebb@swinc.com.spamsucks.com> escribió en el mensaje > > news:OB9V8IEJGHA.1124@TK2MSFTNGP10.phx.gbl... > >> If it's E2K or E2K3, then what I stated is true. > >> > >> I understood the question to be about an environment that is no longer on > >> 5.5. > >> > >> On 5.5 the answer is different as you say (though there's no > >> legacyExchangeDN property of course, only the directoryName property). > >> don't think that's in play here though. > >> > >> "Tom Felts" <tfelts@nospam.mckennalong.com> wrote in message > >> news:uwGW6FEJGHA.524@TK2MSFTNGP09.phx.gbl... > >>> The distinction needs to be made as to whether the environment was > >>> migrated > >>> from 5.5 to 2k and 2k3 via ADC. If that is the case, then what I stated > >>> is > >>> true. Otherwise your understanding is correct. > >>> > >>> "andy webb" <awebb@swinc.com.spamsucks.com> wrote in message > >>> news:OyxOo1DJGHA.1388@TK2MSFTNGP11.phx.gbl... > >>>> Excuse me? > >>>> > >>>> That's just not true at all. > >>>> > >>>> If you change legacyExchangeDN, then replies to messages the user sent > >>>> to > >>>> others will fail [1], calendaring meetings may get disconnected [1], > >>>> and > >>>> free/busy will need to be re-published [2]. You'll also have to > >>>> rebuild > >>> the > >>>> offline address book and push it to any systems that use it (laptops). > >>>> > >>>> [1] This is solved by also adding an x500 type secondary proxy address > >>>> to > >>>> the mailbox using the old legacyExchangeDN value as the address. [3] > >>>> [2] This is solved once the user logs on and schedules a meeting for > >>>> themselves - Outlook will re-publish the free/busy. > >>>> > >>>> So, "at will" might be a little laissez faire, but it can certainly be > >>>> changed. It's not in tue UI, so you'll need to use adsiedit or dsmod > >>>> or > >>>> ldifde or vbscript. You probably want to make it match the "alias" or > >>>> mailNickname [4] value, and also make sure that at least one of the > >>>> SMTP > >>>> addresses on the mailbox uas the same value as it's user portion. > >>>> > >>>> [3] yes, footnote foul, I know. call them belly notes. > >>>> [4] "alias" is the display name of the mailNickname AD property in ADUC > >>>> > >>>> > >>>> "Tom Felts" <tfelts@nospam.mckennalong.com> wrote in message > >>>> news:uSZpaWDJGHA.1180@TK2MSFTNGP09.phx.gbl... > >>>> > At will? The short answer is no. > >>>> > To change legacyexchangedn you need to export the affected users mail > >>>> > to > >>>> > pst, remove the exchange attribs from their account, delete the old > >>>> > mailbox, > >>>> > and then add the exchange attribs back (creating a new mailbox) and > >>>> > then > >>>> > exmerge the data back in. The reason for this is that the exchange > >>> store > >>>> > uses legacy exchangedn as a security > >>>> > ID. > >>>> > > >>>> > > >>>> > > >>>> > > >>>> > "RodeCa" <rod***@terra.BASURA.es> wrote in message > >>>> > news:%23ziEylAJGHA.3944@tk2msftngp13.phx.gbl... > >>>> >> I have a Exchange2K3 server on a Windows2K3. It is an upgrade of > >>>> > Exchange5.5 > >>>> >> on WinNT. > >>>> >> > >>>> >> The lay out was a bit different, and some mailboxes have inherited > >>>> >> "unwanted" values in that "legacyExchangeDN" property: recipient > >>>> > containers > >>>> >> which no longer exist, mailbox (hidden) names from a different > >>>> >> naming > >>>> >> policy, etcetera. > >>>> >> > >>>> >> May I change at will that property for several users? ... without > >>> having > >>>> > to > >>>> >> reinstall my whole server, of course ;-) > >>>> >> > >>>> >> -- > >>>> >> TIA > >>>> >> RØ > >>>> >> > >>>> >> > >>>> >> > >>>> >> > >>>> >> > >>>> > > >>>> > > >>>> > >>>> > >>> > >>> > >> > >> > > > > > > > Are you saying that there are no folders associated with the first
administrative group as well? You *can* change that information but if I recall correctly, it can be a bit hairy if you change it after you have already installed the first server. Been a while though, so your mileage may vary. There are encouraging kb's that point to directions for this: http://support.microsoft.com/kb/273863/EN-US/ http://support.microsoft.com/kb/271882/EN-US/ is another. Keep in mind that if you get it wrong, it would be similar to a server not being in the right site when it was restored. Since some of your information for a first server is going to be based on that AG, I suggest a slow approach and reassociation of the groups to a different AG (if it comes to it, you could always migrate them using ADMT or ldifde (or any ldap tool) export and import; groups are not a big deal unless they're used for permissions.) I also think you'd be better off, based on the information of your post - I don't know your environment, that you stabilize your environment prior to centralization and then worry about this type of clean-up. I say that because you'll have plenty of other issues to contend with and you want to keep things as simple and as easy to troubleshoot as you can without muddying the waters with changes. Al Show quoteHide quote "Nick" <N***@discussions.microsoft.com> wrote in message news:C8CC9E1F-0E43-449D-900F-8A2912FE216B@microsoft.com... > This thread has been very educational to me and it explains some odd > things > happening in our exchange environment. > > Our current organization has many exchange servers and several > administrative groups. Some of those admin groups are now empty because > they > were only used for the migration from Exchange 5.5. (Don't ask, it is a > unique environment.) One of the empty admin groups is the "First > Administrative Group". We have been afraid to remove the old > administrative > groups because of our migration from 5.5. The "First Administrative > Group" > is still listed in our legacyExchangeDN. The one odd, annoying problem > that > we have seen with this is that we have many mail-enabled groups that list > the > "First Administrative Group" as their administrative group. Our current > exchange organization does not include any 5.5 servers and is in the > "Native > Mode (no pre-Exchange 2000 servers)" operating mode. > > We are currently getting ready to deploy a more centralized exchange > solution and we would like to clean up some of the exchange organization. > I > would like to change the legacyExchangeDN and remove the empty > administrative > groups. I want to know how changing the legacyExchangeDN and removing the > "First Administrative Group" would affect us since the only exchange > objects > associated with the "First Administrative Group" are mail-enabled groups? > > Thanks, > > --Nick > > "andy webb" wrote: > >> It's also useful to know that they can be changed - occasionally odd >> things >> happen and it needs to be adjusted even in a pure 2003 environment (not >> often, but occasionally). >> >> >> "RodeCa" <rod***@terra.BASURA.es> wrote in message >> news:ua2qjtbJGHA.3936@TK2MSFTNGP12.phx.gbl... >> > So I must deduct that the term "legacy" is some way ambiguous. I >> > thought >> > it was a matter of backward compatibility. >> > >> > As it was only a cosmetic wish :-) , I'll keep them as they are: not so >> > important for so much danger ;-). >> > >> > -- >> > Thank to you all >> > RØ >> > >> > P.S.: it is E2K3 migrated from 5.5 via ADC. That is why I thought it >> > was >> > truly "legacy". And it is no longer 5.5. >> > >> > >> > "andy webb" <awebb@swinc.com.spamsucks.com> escribió en el mensaje >> > news:OB9V8IEJGHA.1124@TK2MSFTNGP10.phx.gbl... >> >> If it's E2K or E2K3, then what I stated is true. >> >> >> >> I understood the question to be about an environment that is no longer >> >> on >> >> 5.5. >> >> >> >> On 5.5 the answer is different as you say (though there's no >> >> legacyExchangeDN property of course, only the directoryName property). >> >> don't think that's in play here though. >> >> >> >> "Tom Felts" <tfelts@nospam.mckennalong.com> wrote in message >> >> news:uwGW6FEJGHA.524@TK2MSFTNGP09.phx.gbl... >> >>> The distinction needs to be made as to whether the environment was >> >>> migrated >> >>> from 5.5 to 2k and 2k3 via ADC. If that is the case, then what I >> >>> stated >> >>> is >> >>> true. Otherwise your understanding is correct. >> >>> >> >>> "andy webb" <awebb@swinc.com.spamsucks.com> wrote in message >> >>> news:OyxOo1DJGHA.1388@TK2MSFTNGP11.phx.gbl... >> >>>> Excuse me? >> >>>> >> >>>> That's just not true at all. >> >>>> >> >>>> If you change legacyExchangeDN, then replies to messages the user >> >>>> sent >> >>>> to >> >>>> others will fail [1], calendaring meetings may get disconnected [1], >> >>>> and >> >>>> free/busy will need to be re-published [2]. You'll also have to >> >>>> rebuild >> >>> the >> >>>> offline address book and push it to any systems that use it >> >>>> (laptops). >> >>>> >> >>>> [1] This is solved by also adding an x500 type secondary proxy >> >>>> address >> >>>> to >> >>>> the mailbox using the old legacyExchangeDN value as the address. [3] >> >>>> [2] This is solved once the user logs on and schedules a meeting for >> >>>> themselves - Outlook will re-publish the free/busy. >> >>>> >> >>>> So, "at will" might be a little laissez faire, but it can certainly >> >>>> be >> >>>> changed. It's not in tue UI, so you'll need to use adsiedit or >> >>>> dsmod >> >>>> or >> >>>> ldifde or vbscript. You probably want to make it match the "alias" >> >>>> or >> >>>> mailNickname [4] value, and also make sure that at least one of the >> >>>> SMTP >> >>>> addresses on the mailbox uas the same value as it's user portion. >> >>>> >> >>>> [3] yes, footnote foul, I know. call them belly notes. >> >>>> [4] "alias" is the display name of the mailNickname AD property in >> >>>> ADUC >> >>>> >> >>>> >> >>>> "Tom Felts" <tfelts@nospam.mckennalong.com> wrote in message >> >>>> news:uSZpaWDJGHA.1180@TK2MSFTNGP09.phx.gbl... >> >>>> > At will? The short answer is no. >> >>>> > To change legacyexchangedn you need to export the affected users >> >>>> > to >> >>>> > pst, remove the exchange attribs from their account, delete the >> >>>> > old >> >>>> > mailbox, >> >>>> > and then add the exchange attribs back (creating a new mailbox) >> >>>> > and >> >>>> > then >> >>>> > exmerge the data back in. The reason for this is that the >> >>>> > exchange >> >>> store >> >>>> > uses legacy exchangedn as a security >> >>>> > ID. >> >>>> > >> >>>> > >> >>>> > >> >>>> > >> >>>> > "RodeCa" <rod***@terra.BASURA.es> wrote in message >> >>>> > news:%23ziEylAJGHA.3944@tk2msftngp13.phx.gbl... >> >>>> >> I have a Exchange2K3 server on a Windows2K3. It is an upgrade of >> >>>> > Exchange5.5 >> >>>> >> on WinNT. >> >>>> >> >> >>>> >> The lay out was a bit different, and some mailboxes have >> >>>> >> inherited >> >>>> >> "unwanted" values in that "legacyExchangeDN" property: recipient >> >>>> > containers >> >>>> >> which no longer exist, mailbox (hidden) names from a different >> >>>> >> naming >> >>>> >> policy, etcetera. >> >>>> >> >> >>>> >> May I change at will that property for several users? ... without >> >>> having >> >>>> > to >> >>>> >> reinstall my whole server, of course ;-) >> >>>> >> >> >>>> >> -- >> >>>> >> TIA >> >>>> >> RØ >> >>>> >> >> >>>> >> >> >>>> >> >> >>>> >> >> >>>> >> >> >>>> > >> >>>> > >> >>>> >> >>>> >> >>> >> >>> >> >> >> >> >> > >> > >> >> >>  
Thread options
Other interesting topics
Changing name or IP address on Domain Controller
Group Policy - Shutdown/Startup Scripts Question Remove Dirty Boxes [WildPacket] Need help with global AD DNS server placement Is there ~1000 value limit for multi-valued attributes is ADAM? User logon connection dropped overnight. Slow logon when appying personal settings Complex Passwords change hardware what's the difference between a connect, bind and authentication? |
|||||||||||||||||||||||
