RE: Address Book Question
Yup...gonna be a bumpy ride... Larry From: KevinM [mailto:kev...@wlkmmas.org] Sent: Tuesday, June 21, 2011 3:07 PM To: MS-Exchange Admin Issues Subject: RE: Address Book Question Companies that do a lot of buying of other companies have teams, and processes dedicated to this. I've seen a number of companies that go for a full scorched earth process where they replace everything in the bought company regardless of price, or age. Sounds like you have a bit of a fun mess on your hands!! From: Brown, Larry [mailto:lc.br...@dplinc.com] Sent: Tuesday, June 21, 2011 6:06 AM To: MS-Exchange Admin Issues Subject: RE: Address Book Question Kevin, It's not a question of how. It's that I don't see the sense to this if we are to remain a separate entity. Company A is regulated by the state we are in, so we can be owned by a holding company, but not be absorbed by it or any other company of the same type that operates out of state. The money wasted alone is enough of a reason to me (scrapping a functional Exchange system that is already paid for and covered under our Enterprise license) and having to pay a vender to provide what we already have. I'm just trying to figure out a way to make company B happy without incurring costs to company A. Oh...and I found out this morning that the Free/Busy issue isn't that high of a concern... Larry From: KevinM [mailto:kev...@wlkmmas.org] Sent: Monday, June 20, 2011 2:51 PM To: MS-Exchange Admin Issues Cc: McCready, Rob Subject: RE: Address Book Question I just did the last month for a company who bought 2 other companies. We used the Quest Migration (QMM) tools to create disabled AD Accounts in all 3 domains. The hard part with three was routing email for a single name space. With 2 the shares name space is pretty simple. We used the QMM to set targetaddress for all of the disabled users, and setup a messed receive and send connector thing based on the targetaddress name spaces. 1. The bought company has a throw away AD at this point. Anything you do in the source domain will make routing for a single name space a bit harder to do. You don't want Exchange to try to deliver locally for users who are in another domain. Contacts might be simpler, but I've always done disabled AD accounts. 2. Yes this is feasible. 3. Best way to do this is with Quest Migration tools. If you use Quest then 1 and 2 are done for as part of the setup of QMM From: Brown, Larry [mailto:lc.br...@dplinc.com] Sent: Monday, June 20, 2011 11:29 AM To: MS-Exchange Admin Issues Cc: McCready, Rob Subject: Address Book Question Company A (companyA.com) is being bought by Company B (companyB.com). Company A has an established Exchange 2007 environment. Company B is a multi-national holding company with many sub companies. They use a hosted Exchange 2007 environment. Company B wants everyone from Company A to be on their exchange servers for ease of use, ( everyone in Company B wants to be able to look up Company A employees in the Global Address Book) and for setting up meetings/sharing free/busy data. Company A in all other aspects will keep their domain and local network services. To do this, they are proposing creating AD accounts on companyB.com. Users will log in to CompanyA.com, then have to authenticate Outlook with CompanyB.com to get their email. Also, Company A will have to dispose of their Exchange environment and sign a contract to use the hosted Exchange environment, thus wasting the dollars already spent to create Company A's Exchange environment while running up a new cost to Company A. Question: Isn't there a better way to do this? * Since somebody has to create the AD accounts anyway, why not just create Contacts in the Company B GAL for all users of Company A? * Is it feasible to export our GAL and have them import a copy, to be listed under their GAL? * ? I have no ideas for how to share the free/busy data. This is very much at the is this feasible/does it make sense stage. I'd appreciate any input. Larry C. Brown LAN/WAN CS Support --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.commailto:listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.commailto:listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.commailto:listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana
RE: Address Book Question
Kevin, It's not a question of how. It's that I don't see the sense to this if we are to remain a separate entity. Company A is regulated by the state we are in, so we can be owned by a holding company, but not be absorbed by it or any other company of the same type that operates out of state. The money wasted alone is enough of a reason to me (scrapping a functional Exchange system that is already paid for and covered under our Enterprise license) and having to pay a vender to provide what we already have. I'm just trying to figure out a way to make company B happy without incurring costs to company A. Oh...and I found out this morning that the Free/Busy issue isn't that high of a concern... Larry From: KevinM [mailto:kev...@wlkmmas.org] Sent: Monday, June 20, 2011 2:51 PM To: MS-Exchange Admin Issues Cc: McCready, Rob Subject: RE: Address Book Question I just did the last month for a company who bought 2 other companies. We used the Quest Migration (QMM) tools to create disabled AD Accounts in all 3 domains. The hard part with three was routing email for a single name space. With 2 the shares name space is pretty simple. We used the QMM to set targetaddress for all of the disabled users, and setup a messed receive and send connector thing based on the targetaddress name spaces. 1. The bought company has a throw away AD at this point. Anything you do in the source domain will make routing for a single name space a bit harder to do. You don't want Exchange to try to deliver locally for users who are in another domain. Contacts might be simpler, but I've always done disabled AD accounts. 2. Yes this is feasible. 3. Best way to do this is with Quest Migration tools. If you use Quest then 1 and 2 are done for as part of the setup of QMM From: Brown, Larry [mailto:lc.br...@dplinc.com] Sent: Monday, June 20, 2011 11:29 AM To: MS-Exchange Admin Issues Cc: McCready, Rob Subject: Address Book Question Company A (companyA.com) is being bought by Company B (companyB.com). Company A has an established Exchange 2007 environment. Company B is a multi-national holding company with many sub companies. They use a hosted Exchange 2007 environment. Company B wants everyone from Company A to be on their exchange servers for ease of use, ( everyone in Company B wants to be able to look up Company A employees in the Global Address Book) and for setting up meetings/sharing free/busy data. Company A in all other aspects will keep their domain and local network services. To do this, they are proposing creating AD accounts on companyB.com. Users will log in to CompanyA.com, then have to authenticate Outlook with CompanyB.com to get their email. Also, Company A will have to dispose of their Exchange environment and sign a contract to use the hosted Exchange environment, thus wasting the dollars already spent to create Company A's Exchange environment while running up a new cost to Company A. Question: Isn't there a better way to do this? * Since somebody has to create the AD accounts anyway, why not just create Contacts in the Company B GAL for all users of Company A? * Is it feasible to export our GAL and have them import a copy, to be listed under their GAL? * ? I have no ideas for how to share the free/busy data. This is very much at the is this feasible/does it make sense stage. I'd appreciate any input. Larry C. Brown LAN/WAN CS Support --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.commailto:listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.commailto:listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist
Re: Address Book Question
Hi Larry, I am a customer :) As for takeovers, my experience has been that resistance is usually futile (and frustrating). They usually have processes for this type of thing. On Tue, Jun 21, 2011 at 9:05 AM, Brown, Larry lc.br...@dplinc.com wrote: Kevin, It’s not a question of how. It’s that I don’t see the sense to this if we are to remain a separate entity. Company A is regulated by the state we are in, so we can be owned by a holding company, but not be absorbed by it or any other company of the same type that operates out of state. ** ** The money wasted alone is enough of a reason to me (scrapping a functional Exchange system that is already paid for and covered under our Enterprise license) and having to pay a vender to provide what we already have. ** ** I’m just trying to figure out a way to make company B happy without incurring costs to company A. ** ** Oh…and I found out this morning that the Free/Busy issue isn’t that high of a concern… ** ** *Larry* ** ** *From:* KevinM [mailto:kev...@wlkmmas.org] *Sent:* Monday, June 20, 2011 2:51 PM *To:* MS-Exchange Admin Issues *Cc:* McCready, Rob *Subject:* RE: Address Book Question ** ** I just did the last month for a company who bought 2 other companies. We used the Quest Migration (QMM) tools to create disabled AD Accounts in all 3 domains. The hard part with three was routing email for a single name space. With 2 the shares name space is pretty simple. We used the QMM to set targetaddress for all of the disabled users, and setup a messed receive and send connector thing based on the targetaddress name spaces. ** ** **1. **The bought company has a throw away AD at this point. Anything you do in the source domain will make routing for a single name space a bit harder to do. You don’t want Exchange to try to deliver locally for users who are in another domain. Contacts might be simpler, but I’ve always done disabled AD accounts. **2. **Yes this is feasible. **3. **Best way to do this is with Quest Migration tools. If you use Quest then 1 and 2 are done for as part of the setup of QMM ** ** *From:* Brown, Larry [mailto:lc.br...@dplinc.com] *Sent:* Monday, June 20, 2011 11:29 AM *To:* MS-Exchange Admin Issues *Cc:* McCready, Rob *Subject:* Address Book Question ** ** Company A (companyA.com) is being bought by Company B (companyB.com). ** ** Company A has an established Exchange 2007 environment. ** ** Company B is a multi-national holding company with many sub companies. They use a hosted Exchange 2007 environment. ** ** Company B wants everyone from Company A to be on their exchange servers for ease of use, ( everyone in Company B wants to be able to look up Company A employees in the Global Address Book) and for setting up meetings/sharing free/busy data. ** ** Company A in all other aspects will keep their domain and local network services. ** ** To do this, they are proposing creating AD accounts on companyB.com. Users will log in to CompanyA.com, then have to authenticate Outlook with CompanyB.com to get their email. ** ** Also, Company A will have to dispose of their Exchange environment and sign a contract to use the hosted Exchange environment, thus wasting the dollars already spent to create Company A’s Exchange environment while running up a new cost to Company A. ** ** ** ** Question: Isn’t there a better way to do this? **· **Since somebody has to create the AD accounts anyway, why not just create Contacts in the Company B GAL for all users of Company A? **· **Is it feasible to export our GAL and have them import a copy, to be listed under their GAL? **· **? I have no ideas for how to share the free/busy data. ** ** This is very much at the “is this feasible/does it make sense” stage. I’d appreciate any input. ** ** * Larry C. Brown* LAN/WAN CS Support --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist -- smsadm --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist
RE: Address Book Question
Companies that do a lot of buying of other companies have teams, and processes dedicated to this. I've seen a number of companies that go for a full scorched earth process where they replace everything in the bought company regardless of price, or age. Sounds like you have a bit of a fun mess on your hands!! From: Brown, Larry [mailto:lc.br...@dplinc.com] Sent: Tuesday, June 21, 2011 6:06 AM To: MS-Exchange Admin Issues Subject: RE: Address Book Question Kevin, It's not a question of how. It's that I don't see the sense to this if we are to remain a separate entity. Company A is regulated by the state we are in, so we can be owned by a holding company, but not be absorbed by it or any other company of the same type that operates out of state. The money wasted alone is enough of a reason to me (scrapping a functional Exchange system that is already paid for and covered under our Enterprise license) and having to pay a vender to provide what we already have. I'm just trying to figure out a way to make company B happy without incurring costs to company A. Oh...and I found out this morning that the Free/Busy issue isn't that high of a concern... Larry From: KevinM [mailto:kev...@wlkmmas.org] Sent: Monday, June 20, 2011 2:51 PM To: MS-Exchange Admin Issues Cc: McCready, Rob Subject: RE: Address Book Question I just did the last month for a company who bought 2 other companies. We used the Quest Migration (QMM) tools to create disabled AD Accounts in all 3 domains. The hard part with three was routing email for a single name space. With 2 the shares name space is pretty simple. We used the QMM to set targetaddress for all of the disabled users, and setup a messed receive and send connector thing based on the targetaddress name spaces. 1. The bought company has a throw away AD at this point. Anything you do in the source domain will make routing for a single name space a bit harder to do. You don't want Exchange to try to deliver locally for users who are in another domain. Contacts might be simpler, but I've always done disabled AD accounts. 2. Yes this is feasible. 3. Best way to do this is with Quest Migration tools. If you use Quest then 1 and 2 are done for as part of the setup of QMM From: Brown, Larry [mailto:lc.br...@dplinc.com] Sent: Monday, June 20, 2011 11:29 AM To: MS-Exchange Admin Issues Cc: McCready, Rob Subject: Address Book Question Company A (companyA.com) is being bought by Company B (companyB.com). Company A has an established Exchange 2007 environment. Company B is a multi-national holding company with many sub companies. They use a hosted Exchange 2007 environment. Company B wants everyone from Company A to be on their exchange servers for ease of use, ( everyone in Company B wants to be able to look up Company A employees in the Global Address Book) and for setting up meetings/sharing free/busy data. Company A in all other aspects will keep their domain and local network services. To do this, they are proposing creating AD accounts on companyB.com. Users will log in to CompanyA.com, then have to authenticate Outlook with CompanyB.com to get their email. Also, Company A will have to dispose of their Exchange environment and sign a contract to use the hosted Exchange environment, thus wasting the dollars already spent to create Company A's Exchange environment while running up a new cost to Company A. Question: Isn't there a better way to do this? * Since somebody has to create the AD accounts anyway, why not just create Contacts in the Company B GAL for all users of Company A? * Is it feasible to export our GAL and have them import a copy, to be listed under their GAL? * ? I have no ideas for how to share the free/busy data. This is very much at the is this feasible/does it make sense stage. I'd appreciate any input. Larry C. Brown LAN/WAN CS Support --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.commailto:listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.commailto:listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.commailto:listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist
Address Book Question
Company A (companyA.com) is being bought by Company B (companyB.com). Company A has an established Exchange 2007 environment. Company B is a multi-national holding company with many sub companies. They use a hosted Exchange 2007 environment. Company B wants everyone from Company A to be on their exchange servers for ease of use, ( everyone in Company B wants to be able to look up Company A employees in the Global Address Book) and for setting up meetings/sharing free/busy data. Company A in all other aspects will keep their domain and local network services. To do this, they are proposing creating AD accounts on companyB.com. Users will log in to CompanyA.com, then have to authenticate Outlook with CompanyB.com to get their email. Also, Company A will have to dispose of their Exchange environment and sign a contract to use the hosted Exchange environment, thus wasting the dollars already spent to create Company A's Exchange environment while running up a new cost to Company A. Question: Isn't there a better way to do this? * Since somebody has to create the AD accounts anyway, why not just create Contacts in the Company B GAL for all users of Company A? * Is it feasible to export our GAL and have them import a copy, to be listed under their GAL? * ? I have no ideas for how to share the free/busy data. This is very much at the is this feasible/does it make sense stage. I'd appreciate any input. Larry C. Brown LAN/WAN CS Support --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist
RE: Address Book Question
I just did the last month for a company who bought 2 other companies. We used the Quest Migration (QMM) tools to create disabled AD Accounts in all 3 domains. The hard part with three was routing email for a single name space. With 2 the shares name space is pretty simple. We used the QMM to set targetaddress for all of the disabled users, and setup a messed receive and send connector thing based on the targetaddress name spaces. 1. The bought company has a throw away AD at this point. Anything you do in the source domain will make routing for a single name space a bit harder to do. You don't want Exchange to try to deliver locally for users who are in another domain. Contacts might be simpler, but I've always done disabled AD accounts. 2. Yes this is feasible. 3. Best way to do this is with Quest Migration tools. If you use Quest then 1 and 2 are done for as part of the setup of QMM From: Brown, Larry [mailto:lc.br...@dplinc.com] Sent: Monday, June 20, 2011 11:29 AM To: MS-Exchange Admin Issues Cc: McCready, Rob Subject: Address Book Question Company A (companyA.com) is being bought by Company B (companyB.com). Company A has an established Exchange 2007 environment. Company B is a multi-national holding company with many sub companies. They use a hosted Exchange 2007 environment. Company B wants everyone from Company A to be on their exchange servers for ease of use, ( everyone in Company B wants to be able to look up Company A employees in the Global Address Book) and for setting up meetings/sharing free/busy data. Company A in all other aspects will keep their domain and local network services. To do this, they are proposing creating AD accounts on companyB.com. Users will log in to CompanyA.com, then have to authenticate Outlook with CompanyB.com to get their email. Also, Company A will have to dispose of their Exchange environment and sign a contract to use the hosted Exchange environment, thus wasting the dollars already spent to create Company A's Exchange environment while running up a new cost to Company A. Question: Isn't there a better way to do this? * Since somebody has to create the AD accounts anyway, why not just create Contacts in the Company B GAL for all users of Company A? * Is it feasible to export our GAL and have them import a copy, to be listed under their GAL? * ? I have no ideas for how to share the free/busy data. This is very much at the is this feasible/does it make sense stage. I'd appreciate any input. Larry C. Brown LAN/WAN CS Support --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.commailto:listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist
Address Book Question
Hello Everyone, I have noticed that when I address an e-mail, hit the TO... button and then the drop down list I can not only see my GAL but also a listing for my Organization, Site and Recipients containers. Does anyone know why this is, because I would really like it just to show the GAL and any personal contacts folders that they have added? Regards, Shawn Leblanc List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
