Exchange 2007/Office 365 Merger Coexistence

Our company has a 2007 Exchange server. We are merging with a company using Office 365. The decision on premise/hosted email is months away, each organization needs to maintain it's own email identity including mail flow (we are using different external
archiving products)
We'd like to implement common address book and calendar sharing by deploying Exchange 2013 on premise and configuring a hybrid migration scenario, but not actually doing the migration.
A couple of questions I could not find in the documentation:
1) Is this a supported scenario?
2) Can we configure each unique email domain's routing individually? We like domain xyz.com to be centrally transported (go to and from premise connectors) and abc.com no to be (to and from cloud connector). Can't find this scenario explicitly stated as
being supported
3) Can we create unique address lists for each org? Management wants to have all users from both companies in the GAL but not have their groups be visible to each other.
Thanks
Jo

Hi psh8989,
According to your description, I know that you want to migrate public folder from Exchange 2007 to Office 365.
Since Office 365 is different from Exchange On-Premises, I suggest ask Office 365 Forum for help so that you can get more professional suggestions. For your convenience:
http://community.office365.com/en-us/default.aspx
However, I can also share some information for your reference : )
Based on my knowledge, Exchange supports moving your public folders to Office 365 and Exchange Online from Exchange 2007 SP3 RU10 or later. I notice that your Exchange server version is SP1, please upgrade to SP3 RU10 first and perform migration.
More detailed information to see:
Migrate legacy public folders to Office 365 and Exchange Online
http://technet.microsoft.com/en-us/library/jj983799(v=exchg.150).aspx
Thanks
Mavis Huang
TechNet Community Support

Similar Messages

Migrating Public Folders on Exchange Server 2007 SP1 to Exchange Online\Office 365

Hello,
Our company is looking to migrate from Exchange 2007 on premises to Exchange Online/Office 365. We have a number of public folders on our exchange server that function similarly to how the new shared mailboxes work in Exchange Online. That is to say that
we have many outside users (customers and wholesale dealers) emailing this public folder ([email protected]) and our end users are given permission to view and respond as themselves ([email protected]). I've been looking all over but haven't found a clean
way to migrate the current public folders directly into shared mailboxes. I'd just start from scratch, but we want to keep the records of the emails we've received at these public folders for customer support reasons. Can anyone help?

Hi psh8989,
According to your description, I know that you want to migrate public folder from Exchange 2007 to Office 365.
Since Office 365 is different from Exchange On-Premises, I suggest ask Office 365 Forum for help so that you can get more professional suggestions. For your convenience:
http://community.office365.com/en-us/default.aspx
However, I can also share some information for your reference : )
Based on my knowledge, Exchange supports moving your public folders to Office 365 and Exchange Online from Exchange 2007 SP3 RU10 or later. I notice that your Exchange server version is SP1, please upgrade to SP3 RU10 first and perform migration.
More detailed information to see:
Migrate legacy public folders to Office 365 and Exchange Online
http://technet.microsoft.com/en-us/library/jj983799(v=exchg.150).aspx
Thanks
Mavis Huang
TechNet Community Support

Exchange 2013 Office 365 Hybrid Cloud On-Premise Outlook Connection Problem

Hi Everyone,
We are required to migrate FROM the cloud TO an on-premise Exchange 2013 server. We set up a trial of Office365 and linked our test domain to that account. The test domain mimics our current domain, but ends in .net instead of .org.
We set up a test Exchange 2013 server with a few database servers. Internally, we can connect without issue (Outlook). We mapped our test CAS to face the Internet, and can access what we need without issue. We also set up the Hybrid
configuration on both the Exchange 2013 and Office365 servers. We have validated that DirSync works, and migration can occur up to the cloud and back down to the on-premise server.
Now, here is the issue:
We have our DNS records still pointing to Office365, so when we add an Office365 mailbox to Outlook (internal to the network or outside the network) we see absolutely no issues. We migrated a mailbox today to our on-premise server, but upon doing so,
can no longer connect to, or add, that mailbox to Outlook. When we put this integration in to effect for production, we want to be able to migrate mailboxes on-premise from the cloud, and we want to make sure users can still access their mailboxes. This
also goes for distribution groups, conference rooms, etc.
I see that most suggestions say to change your DNS record to point to the on-premise Exchange server, which is great, but after doing so Office365 accounts experience the same issue as above. We NEED to make sure that when we batch migrate, the users
DO NOT lose connectivity to their accounts. We need both Office365 accounts and Exchange on-premise accounts are accessible internally and externally. As an extra tid-bit, we HAVE configured Outlook Anywhere on Exchange 2013, but see no difference.
Any thoughts on this? Office365 and Exchange 2013 see eachother and recognize that the hybrid environment is set up good, but it appears we are missing some configurations. Currently, we have a CNAME record points our autodiscover to autodiscover.outlook.com.
Any help would be MUCH appreciated. Thanks!
Dan

Hi,
Here is an article on Move mailboxes between on-premises and Exchange Online organizations in 2013 hybrid deployments, for your reference:
http://technet.microsoft.com/en-us/library/jj906432(v=exchg.150).aspx
I want to make sure OWA works well with the moved mailbox.
To use CNAME based autodiscover method, we need to have all domain names present in a SAN certificate.
With Exchange 2013 CU1, we now have the option of adding multiple SMTP domains to Exchange Federation/Hybrid configuration and we can specify which of these domains should act the "autodiscover" domain.
To configure an SMTP domain as the autodiscover domain, you can run following command:
Set-HybridConfiguration -Domains "domain1.com, domain2.com, domain3.com", "autod:domain.com"
More details, please refer following blogs:
http://www.msexchange.org/articles-tutorials/office-365/exchange-online/configuring-exchange-2013-hybrid-deployment-and-migrating-office-365-exchange-online-part11.html
http://www.msexchange.org/articles-tutorials/office-365/exchange-online/configuring-exchange-2013-hybrid-deployment-and-migrating-office-365-exchange-online-part12.html
Disclaimer:
Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make sure
that you completely understand the risk before retrieving any suggestions from the above links.
Thanks
Mavis Huang
TechNet Community Support

Exchange 2013 (Office 365) shared mailbox not staying up to date.

We have created a new shared folder for multiple users to access in Office 365 and were having some issues. There are a few users where this mailbox works great, but others users aren't able to see any changes that are made in the shared mailbox.
Opening the mailbox in O365 shows all folders, emails, etc... but for some reason syncing stops working randomly after a bit of time. Removing and re-adding permissions to the mailbox does fix this issue, but that's not a feasable fix for us.
Users can add folders to the shared mailbox, and those added folders do show up in the mailbox when opened in O365, but the changes do not push down to multiple other clients.
Anyone else seen this or have any info? Thanks!

Hi,
Are the users using Cached Exchange Mode or Online Mode? When the issue comes next time, have the user switch to the other mode and test if this helps.
We can disable Cached Mode for Shared folders, check if this helps resolve the sync issue:
Go to FILE -> Account Settings -> Account Settings -> Double click on the Exchange account -> More Settings -> Advanced tab -> Uncheck "Use Cached Exchange Mode", and click Apply then OK.
In Cached Mode, it doesn't connect to Exchange Server all the time but keeps a cache of the mailbox locally to sync the local cache and mailbox according to a period, this may cause some items not sync immediately. By switching to Online Mode, it should
be immediate.
Regards,
Melon Chen
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs.

Exchange 2007/2010/2013 UM coexistence

We currently have an Exchange 2007/2010 environment in production along with Lync 2010 (UM provided).
I have installed a number of Exchange 2013 server and will be migrating ( over a LONG time ) to the new system.
In the meantime, I need to have all services co-existent across all three Exchange versions.
It looks like I have everything workign now except UM for Lync 2010.
I tried adding the Exchange 2013 server into the existing 2007/2010 dial plan and am having issues.
Here is what i did.
EAC
- Installed certificate on all Exchange 2013 servers
- Enabled Unified Messaging on all the servers
- Select server
- Set TLS
- Associated 2007/2010 Dial Plan
- Set UM service on certificate on all servers
- Restarted UM service
- Did the above for all MB and CAS servers
- Wait about an hour
Lync fails to send calls to voice mail, giving me events 45024 and 44022 on the Lync FE stating that Lync could not connect to the Exch MB servers and the attempt to connect to UM failed.
Any suggestions?
Do I need to rerun the following ?
- Exchucutl.ps1
- Ocsumutil.exe
Thanks!
Tom

When I go into the Exchange EAC Unified messaing / UM IP Gateway screen I see the Um IP Gateways configured in the legacy Exchange systems and had hoped that these existing gateway definitions would suffice.
Does exchucutil.ps1 need to run from a 2013 Exch server to initialize these gateways in Exch 2013?
On my fist attempt, VM was failing for my 2007/2010 users. I had not even started to test with a 2013 user. I successfully backed out by dis-associating the dial plan in the Exchange EAC console from all the Exch 2013 servers.
If I run exchucutil.ps1, try again, and it fails, what is my backout plan? Do I need to rerun exchucutil.ps1 on a legacy Exchange system? or will merely dis-associateing the diual plan in Exchange 2013 again suffice.
Thanks Tom
After typing this, I realize that this is probably more of an Exchange question so I posted the question there. I apologize now for any cross posting misbehavour.
Posted to -
http://social.technet.microsoft.com/Forums/exchange/en-US/6fbfad13-3480-46c6-804d-3757110e61c7/exchange-um-coexistence-exch-20072010-and-exch-2013?forum=exchangesvrunifiedmessaging

How to establish a Microsoft Exchange connection (Office 365)?

My institution has just informed me that they are switching off IMAP and POP access from Monday. Email and calendaring are provided by Office 365. Alternative configuration instructions are available for mobile devices (iOS, Blackberry, Android etc.) but not for Thunderbird. Their only suggestion is a paid plugin which my school would have to pay for. This just ain't gonna happen. Moreover, I would prefer a free software option if at all possible. ('Free' as in 'freedom', though beer is important, too.)
Calendaring isn't important as I have that setup independently of my organisation's provision. Only email matters.
Searching rather urgently has turned up a few leads but they are generally quite old and almost all require IMAP and/or POP enabled on the server. Beyond that, I've come across the following possibilities:
davmail which apparently bridges between OWA and IMAP/POP, but I'm not clear if this would work with Office 365 as I've only found references to using it with older MS Exchange servers;
evolution with a plugin;
possibly KDE's mail programme, although I'm not clear from the information I've found whether this is really an option or not.
I'm running KDE. If possible, I'd prefer to avoid the Gnome dependencies of evolution. However, if that's the only option, so be it. An ideal solution will work on Fedora as well as Arch. (Obviously Fedora is off-topic here - I just thought I might as well mention it.) A really ideal solution would also let me continue using Thunderbird without relying on proprietary code, but I'm beginning to think this is probably a pipe dream.
The most attractive of the above options is currently davmail, if that is really an option. However, I get the impression that this could require considerable overhead.
I would greatly appreciate any advice or pointers anybody can offer me. So far, I've not found anything which even mentions Linux with Office 365. I'm not sure if this is because 'Office 365' is actually relying on something else (and that's what I need to search for), whether it is because the situation is hopeless or whether it is for some other reason.

brebs wrote:
cfr wrote:I'm not clear if this would work with Office 365
Well, 10 seconds of googling for "office 365 imap" shows encouraging davmail fixed bug report.
Thanks. Sorry. I did spend a lot of time searching but I did not find that. (Using IXQ for search.) But I was not trying 'imap' specifically - rather 'linux' - as I just wanted any way to access it. And the results I got tended to assume the Exchange server had imap enabled.
Some things I would raise:
* Check the IT policy regarding whether Linux is supported/accepted. And if not, why not.
* Push for clarification regarding the supposed security risk, or whatever is being used as justification.
As Trilby pointed out, this is useless.
Linux is not supported except on a 'best effort' basis. I run Linux on my office PC. I'm entirely responsible for it. Local IT will help if they possibly can. Central IT will say that Linux is supported sufficiently because you can use web mail.
They do not need to justify this. There does not need to be an answer to 'why not?'
No justification has been offered for switching off the support. Trilby's IT invoke security to justify not turning it on. My IT offer no reason for turning it off. It is just a fact that it is being switched off.
[For some reason, it has not yet been switched off, although they said it would be yesterday.]
The suggestion of raising these issues may sound perfectly reasonable, but it is a suggestion based on ignorance of reality.
In a sane world, it would make perfect sense. But this is academia in 2015. (Not just academia, I know.) Sanity is an irrelevant standard.
Last edited by cfr (2015-06-09 15:31:28)

Exchange Connector / Office 365 Not matching affected user to AD user

We use Office 365 to host our email services. AD is not synchronized to office 365. We're bringing Exchange on premises soon so there isn't a lot we want to invest in that existing infrastructure. I'm using Service Manager 2012 R2.
I have the ADConnector configured, bringing in Active Directory users/groups/computers.
I've gotten the Exchange Connector running in order to retrieve emails from an "IT Services" Office 365 mailbox and automatically create tickets. Notifications back to the users are working fine.
The problem I'm having is the affected user is not being set properly when a user emails the mailbox and an incident is created. It is setting the Affected User to that user's name, but when I double click the Affected user, it brings up the "User
- <UserName>" screen. All of the information that would be coming in from AD is blank. So that association between my office 365 email address and the AD user account is not being made. Even though it says my name with
correct (username) on the incident as the affected user. And even though my email address is stored inside of AD in the e-mail field.
What am I missing in this process?
Thank you,
Mark

I ended up messing around and added a UPN to AD Domains and Trusts matching the domain of our email accounts through Office 365. I found this because similar preparation is required for AD sync to Office 365, so a proper match can be made.
So for example, if our internal domain is Contoso.Local, and our email addresses are [email protected]
I added a UPN for contosolimited.com in Active Directory Domains & Trusts. Then I changed my UPN in Active Directory Users and Computers (Account tab), to @contosolimited.com.
Now when the AD Connector ran, it set my user CI UPN (in the Extensions tab) to [email protected] I then sent an email to [email protected] and it matched my email correctly to my user CI created by the AD Connector.
Now I just have to run a script against AD to update all user UPNs to @contosolimited.com from @Contoso.local.

Exchange Online Office 365 integration questions

Hi Guys,
I am about to setup a pilot and wanted to ask a few questions.
I am planning a multi-domain exchange deployment...where I am hosting my main email on site with a domain of company.com and I want to host 1.company.com and 2.company.com on my office 365 Exchange online implementation. To do this do I have to define the
new domains on my current exchange server and then setup the users on office 365?
one of the things that my user base wants is single sign on but they won't be using rich clients. I know this works well for rich clients, but can single sign on also sign on to Office 365 web and one drive?
I will be implementing ADFS and DIrSync for AD replication and ADFS for single sign on.
How does licensing work? if my entire directory replicates to Office 365 and I only want some users over there activated, how do those I want activated. Can I easily activated a bunch of users for only some services at one time? If I deactivate or delete
an account locally, will those changes take at office 365? How does that work with licensing? do my licenses get automatically freed up?

Hi Emil,
Thank you for your question.
There are two sentences I don’t understand:
Leave both environments as is
Would this work also (X500 addresses would be written and updated, move requests would work, F/B, etc)?
AD trust is important for us to share organization information between ADs.
AAD has capability which AD and Exchange multi-forest forest environment can be extended to cloud, so we could not run it in both AD environment. There is a alternative solution which use FIM. We could refer to the following link:
http://azure.microsoft.com/en-us/documentation/articles/active-directory-whatis/
If there are any questions regarding this issue, please be free to let me know.
Best Regard,
Jim
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Jim Xu
TechNet Community Support

Single inbox for exchange and office 365

hi , we have single inbox for exchange configured, customer now has some test users on office 365.
can we have integrations to both environments on same unity connection box? Broadly speaking, would that be a new service to office 365 with the office 365 users using that service? regards
jag

http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCug48560
This patch did not make it in 8.62 su3

Creating a new address list for Exchange Online (Office 365) by two parameters

Good day!
I need to create two new address list in Exchange Online 2013 (Office 365) that users will choose the two parameters.
Address sheet1: No staff
Address Sheet2: Staff
Parameters address sheet not staff:
Parameter 1: Company
It must match the value - MyCompany
Parameter 2: job title
it must be different from the value - Staff
Parameters address sheet Staff:
Parameter 1: Company
It must match the value - MyCompany
Parameter 2: job title
It must match the value - Staff
Problems:
1) Is it possible to filter user mailboxes on the parameter of discrepancy?
2) Can not find the parameter values for the script field job title
https://technet.microsoft.com/ru-ru/library/aa996912%28v=exchg.150%29.aspx
https://technet.microsoft.com/en-us/library/bb738157%28v=exchg.150%29.aspx
While on the side of 365 in the user properties such parameter is:
http://joxi.ru/MAj0Jj7hGyDbme
Company option too.

I got to build a team that I need (describes the necessary conditions)
and successfully held in PS 4.0 after connecting to the office 365:
1) Set-ExecutionPolicy unrestricted
2) $ UserCredential = Get-Credential
(Data Entry Administrator 365)
3) $ Session = New-PSSession -ConfigurationName
Microsoft.Exchange -ConnectionUri https://outlook.office365.com/powershell-liveid/ -Credential $ UserCredential -Authentication Basic -AllowRedirection
Import-PSSession $ Session
4)
PS C:\Windows\system32> New-AddressList -Name 'TEST1234' -RecipientFilter {((RecipientType -eq 'UserMailbox') -and ((Com
pany -eq 'Company1') -and (Title -ne 'Student')))}
Name DisplayName RecipientFilter
TEST1234 TEST1234 ((RecipientType -eq 'UserMailbox')
-and (((Company -eq 'Company1...
As a result, the new address list TEST1234 immediately appears. (When creating a new letter in the menu "To"), but on the inside
it is empty (although there is 1 user which is fully consistent with those described in the filter conditions.).
= (
Tried a simple version:
Office365
не отображается в адресном списке.">The same thing - the only user with such parameters in AD -> Office365 is not displayed in the address list.
(After running for a list TEST123 more than two days)
Tell me what could be the problem?

Exchange Management Tools? Hybrid Exchange 2010 SP3 - Exchange 2013 (Office 365 - Exchange Online)

When running in Hybrid mode... is there any advantage to installing the Exchange 2013 server management tools on my machine versus the Exchange 2010 management tools?
Any advantages/disadvantages?
I still do have some on premises mailboxes that need to be migrated to the cloud (Exchange Online).
Thoughts? Suggestions? Experiences?

Hi Viva,
We don't have Exchange Management Console in Exchagne 2013 in all the web interface we used in Exchange server 2013. In Exchange 2010 we are having Exchange management console. Hence we can able to access exchange 2010 and 2013 both on the same server.
Exchange Queries

OUTLOOK 2013 on Exchange in Office 365 LOCAL FAILURES

Unable to SAVE & CLOSE New Contacts. These land in LOCAL FAILURES. Can NOT update existing contacts. Outlook send/receive is functional for email.
Performed REPAIR of connection to EXCHANGE SERVER in ACCOUNT SETTINGS. No failure noted there.
Any ideas?

Hi,
Please disable Exchange cached mode in Outlook and use Online mode to check whether you can Save&Close New Contacts properly.
If the issue persists in Outlook Online mode, please start Outlook in safe mode to create a new contact to have a try. To start Outlook in safe mode, please type Outlook /safe in the Search box of the Start Menu.
Regards,
Winnie Liang
TechNet Community Support

Multiple OnPremise Orgs -- Migration to Exchange Online / Office 365

Hi,
we have two separate forests (and two separate MSX orgs). We want to migrate to Exchange Online. The information I find states that we need to establish a trust-relationship between the ADs of both forests. Also it states that we run AAD Sync only in one
forest and connect it to the other. I also read that Hybrid Configuration Wizard might fail, if we do not do what was written above.
So, I am wondering why would I need a AD trust? I would also want to know if you can't do the following in our case:
Leave both environments as is
run aad sync in both environments (there are only unique objects in the Ads)
run HCW against one Org and do all the steps manually on the other Org (Org relationship)
(if we decide to use ADFS, we could install it also in each forest separately)
Would this work also (X500 addresses would be written and updated, move requests would work, F/B, etc)?
Is there more detailed information available? Technet isn't really precise here (https://technet.microsoft.com/en-us/library/jj873754%28v=exchg.150%29.aspx?f=255&MSPPError=-2147217396)
Thanks for all input!
Emil

Hi Emil,
Thank you for your question.
There are two sentences I don’t understand:
Leave both environments as is
Would this work also (X500 addresses would be written and updated, move requests would work, F/B, etc)?
AD trust is important for us to share organization information between ADs.
AAD has capability which AD and Exchange multi-forest forest environment can be extended to cloud, so we could not run it in both AD environment. There is a alternative solution which use FIM. We could refer to the following link:
http://azure.microsoft.com/en-us/documentation/articles/active-directory-whatis/
If there are any questions regarding this issue, please be free to let me know.
Best Regard,
Jim
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Jim Xu
TechNet Community Support

How To Manage Exchange in Office 365 AD Sync Environment

Pisces225x wrote:
So, for example, right now I have no way to manage distribution lists beyond adding and removing members? For example, I can't edit the default configuration on a distribution list to allow it to accept external messages.
You can do that in EAC.
https://technet.microsoft.com/library/bb124513.aspx#deliverymanagement

I implemented AD Sync in our O365 environment a while back. After this I continued to manage Exchange entirely in the O365 admin console. Recently I had a reason to go ahead and extend the AD Schema to include the Exchange attributes. Now the majority of management needs to be done in our local AD. I'm fine with this. My issues are the following:- I initially created and managed all distribution lists in the O365 EAC. They have never existed as objects in our local AD and I have never had on prem Exchange. Is there a way to sync the lists back to our AD? I don't see that they exist anywhere as objects and hence I can't manage them.- Is there anything to be gained by installing Exchange on a local server, even if only to gain access to a local EAC? I'm not interested in trying to set up any kind of hybrid environment.I know someone else...
This topic first appeared in the Spiceworks Community

Exchange 2010 Free/Busy Federation with vendor's Office 365 tenant

Here the situation,
ORG A
====
Exchange 2010 SP3 On-premise. No externally accessible CAS available/published (we are very secure and require VPN for Outlook/OWA from home/outside network)
ORG B
====
Office 365
ASK
===
ORG B is a vendor for ORG A and we would like to have federated free/busy sharing between the two organizations. I have read the steps about setting up a federation trust, configuring org relationships both ways, configuring autodiscover on our end.
My specific questions are,
1. Currently we don't have any externally published CAS servers. My assumption is we need atleast one (and probably more for fault tolerance) for federated free/busy sharing correct? We obviously don't want to place this in the DMZ/externally...so what are
the recommended configuration? Publish the CAS externally? Any other more secure recommendations? We don't have TMG or any other Microsoft solution for that purpose...are there any other options? We use Cisco IronPorts for inbound/outbound email.
2. Does this coexistence server have to be Exchange 2013 or will Exchange 2010 sp3 suffice?
3. Are there any other methods of accomplishing this ask? We don't want users to have to individually share calendars...so internet calendar sharing is out of the question.

Hi,
If the organization receives or sends Internet e-mail for the domain, we need to
configure an
internet facing CAS server.
For your reference, here are some articles that may be helpful to you:
Exchange 2010 SP1 and Exchange Online (Office 365) Calendaring:
http://blogs.technet.com/b/exchange/archive/2011/02/16/3412010.aspx
Federation in Office 365 and Exchange
http://community.office365.com/en-us/wikis/exchange/federation-in-office-365-and-exchange.aspx
Create a Federation Trust
http://technet.microsoft.com/en-us/library/dd335198.aspx
Thanks,
Winnie Liang
TechNet Community Support

Exchange 2007/Office 365 Merger Coexistence

Similar Messages

Maybe you are looking for