OCS 2007 R2 and Exchange 2013

Cannot find any information about this. I cannot find anything on OCS2007 R2 with Exchange 2013.
We have OCS 2007 R2 with Exchange 2007. The plan is to migrate Exchange 2007 to Exchange 2013. We configured new Exchange server and migrated test user. Now caller cannot reach voicemail for the test user.
We are planning to migrate OCS to Lync 2013 in a couple of months, but we wanted to migrate Exchange first.
Any ideas what to do?
Thank you. Eric.

Is your OCS 2007 R2 environment updated to CU 10 or above? http://technet.microsoft.com/en-us/library/jj851069(v=exchg.150).aspx
If this helped you please click "Vote As Helpful" if it answered your question please click "Mark As Answer"
Georg Thomas | Lync MVP
Blog www.lynced.com.au | Twitter
@georgathomas
Lync Edge Port Check (Beta)
This forum post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Similar Messages

Upgrade from OCS 2007 to OCS 2007 R2 and Lync 2013

Hy friends!
Help me, please!
Scenario: Migration from OCS 2007 RTM to OCS 2007 R2
Target: Keep user contact list (I'm talking about only OCS contact list from internal organization users, I'm not refer about external addresses)
Question: I want to know if when I move a user from OCS 2007 RTM to OCS 2007 R2 the user contact list is also migrated?
If Yes, can you share the Microsoft documentation that describe it?
So, after I migrate the users to OCS 2007 R2, finally I can do a supported migration to Lync Server 2013.
Thanks in advance.

If you do a side-by-side migration the contact lists (and other user data) should remain intact. If you tear down OCS2007 and then install OCS2007R2, then you will need to use dbimpexp.exe to export the contact list from OCS2007.
Here is an overview: http://blogs.technet.com/b/ucedsg/archive/2009/02/07/how-do-i-get-from-ocs-rtm-r1-to-ocs-r2.aspx
Also take a look at the deployment guide: https://www.microsoft.com/en-us/download/details.aspx?id=19984 specifically
the section called "Updating from Office Communications Server 2007" which lists some potential issues.
If this helped you please click "Vote As Helpful" if it answered your question please click "Mark As Answer"
Georg Thomas | MVP (Skype for Business)
Blog skype4bexpert.com | Twitter
@georgathomas
Lync/Skype for Business Edge Port Check (Beta)
This forum post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

OCS 2007 R2 to Lync 2013 migration – The new environment will be in a completely different forest with Lync 2013.

Hi All,
Need help - we are planning to migrate around 14000 ~ 16000 users from OCS 2007 R2 to Lync 2013 environment -
issues are - the new Lync 2013 environment will be in a new forest and sip address will not change.
Considering the same - I understand we don't have any option other than going for a cut-over.
please help me to understand how can I move the user's contact and other configurations from OCS 2007 R2 to Lync 2013.
Thanking you
Maz

Hi,
It is indeed a clean cut over. BIG BANG.
You export all users from your OCS environment. All scheduled live meetings will need to be rescheduled because Lync Server 2013 doesn't support Live Meetings anymore.
I would export, convert and import all users like this:
Dbimpexp.exe /hrxmlfile:"C:\Logs\Lync2010data.xml" /sqlserver:Sql.contoso.com\rtc
Convert-CsUserData -InputFile "C:\Logs\Lync2010data.xml" -OutputFile "C:\Logs\Lync2013Data.Zip" -TargetVersion Current
Import-CsUserData -PoolFqdn "atl-cs-001.litwareinc.com" -FileName "C:\Logs\Lync2013Data.Zip"
Don't use Import-CsUserData twice, but use Update-CsUserData the second time if needed.
Have fun!

Remove Exchange 2007 from an Exchange 2013 coexistence.

Hey everyone,
I've just installed Exchange 2013 on a new server and all is working great. It is currently in coexistence with our old Exchange 2007 server. I've since shut the server down and Exchange 2013 has been working without issue. However, I haven't
been able to find any articles on this matter so I figured I would ask the question here.
How do you remove Exchange 2007 from the coexistence. Do I just uninstall Exchange 2007 from the old server and it will remove itself from the server and the domain? Any help/link on this matter would be greatly appreciated.
Thank you,
Chris

Hi Simon,
I am about to do the same exercise as Chris, I just would like some clarity.
1) When you say mailbox Database, do you mean make sure there are no more mailboxes that you want to move over, or are you actually meaning delete the physical DB on the exchange 2007 server.
2) If there is no use of public folders does anything need to happen?
Thanks,
Terry

ACE 4710 and Exchange 2013

Greetings everyone.
I am curious if anyone has any experiences with Exchange 2013 and ACE SLB functions. I know they changed to RPC over HTTPS on exch side and few other items changed as well. I do not forsee any issues just looking to see if anyone has any feedback from a production deployment.
Thanks
Joel

Joel, I checked internally and only located one case raised against ACE and Exchange 2013. The issue was resolved via defect CSCuc98599 "ACE randomly resets POST requests with SSL offloading". Use A5.2.2 or apply workaround (increase maxparselen to 65k). Matthew

SCCM 2012 and Exchange 2013 Connector

Hello all,
I hope that you are well!
I have an issue that I can't explain for the moment, maybe someone can help me.
Actually we have SCCM 2012 SP1 and Exchange 2013 Enterprise in our LAN.
Now I did the configuration within SCCM of creating a new Exchange Server Connectors, everything seem's to be okay, no warning, no active alert, the Exchange server connection account and so on..
But I can't see the mobile devices from my user into the All Mobile Devices within SCCM 2012.
Do I miss something into this specific configuration, certificate or something related !
Best regards to all of you
Stephane

Hello Gerry,
This is what I got on EassDisc.log
ERROR: [MANAGED] Invoking cmdlet Get-Recipient failed. Exception: System.Management.Automation.RemoteException: Cannot bind parameter 'Filter' to the target. Exception setting "Filter": "The value "$true" could not be converted to type System.Boolean."~~
at System.Management.Automation.PowerShell.CoreInvoke[TOutput](IEnumerable input, PSDataCollection`1 output, PSInvocationSettings settings)~~   at System.Management.Automation.PowerShell.Invoke(IEnumerable input, PSInvocationSettings settings)~~
at System.Management.Automation.PowerShell.Invoke()~~   at Microsoft.ConfigurationManager.ExchangeConnector.Connector.Invoke(PSCommand cmd)
ERROR: [MANAGED] Exception: Cannot bind parameter 'Filter' to the target. Exception setting "Filter": "The value "$true" could not be converted to type System.Boolean."
ERROR: Failed to check status of discovery thread of managed COM. error = Unknown error 0x80131501
But that is old error, since I configure the Account properly
Regards to you,
Stephane

Exchange 2007 edb to Exchange 2013 - mailbox extraction and mounting

Hello everyone, here is my question:
I have a client who has Exchange 2007 running on a Domain Controller which is a Server 2008 and that is the only domain controller in his environment. That said, his domain controller crashed and all the AD data is now lost along with Exchange except the
EDB files. He wants to create a new domain controller with Server 2012 and wants to deploy Exchange Server 2013. Since the Domain Name will be the same, is it even possible to extract the mailbox information from Exchange 2007 EDB and attach it with new Exchange
Server 2013 and point them to newly created users on Exchange? If yes, how exactly will this work? Thanks in advance.

Excellent and factual responses from the others and the instructions/guidance should serve you well. If however you want to avoid building a new server etc you could use Lucid8's DigiScope
http://www.lucid8.com/product/digiscope.asp to open the 2007 EDB on a 64 bit machine and then you could take 1 of 2 actions to resolve your issue.
1. You could then export all mailboxes to PST and then Import them into the 2013 environment
2. OR you could have DigiScope migrate/recover the data directly from the offline 2007 EDB into the Production 2013 server on the fly, i.e. no end user downtime is required.
Search, Recover, & Extract Mailboxes, Folders, & Email Items from Offline Exchange Mailbox and Public Folder EDB's and Live Exchange Servers or Import/Migrate direct from Offline EDB to Any Production Exchange Server, even cross version i.e. 2003 -->
2007 --> 2010 --> 2013 with Lucid8's
DigiScope

Outlook 2003 and Exchange 2013

We have just installed Exchange 2013 servers in our organization alongside existing Exchange 2007 servers. No mailboxes have been migrated yet and we are about ready to point our client access namespace to the Exchange 2013 servers and go into the co-existence
stage.
We still have some Outlook 2003 clients and I know these need to be updated to 2007 SP3 or 2010 Sp1 or 2013 before those mailboxes are migrated to Exchange 2013.
However, I am curious as to whether we would hit any problems at all if we pointed our namespace to E2K13 before upgrading the Outlook 2003 clients, as long as none of the Outlook 2003 clients use Outlook Anywhere and the mailboxes those clients
connect to remained on Exchange 2007 for the time being ?
Clearly, Outlook 2003 is not 'supported' but the wording in the following link...
http://social.technet.microsoft.com/wiki/contents/articles/845.outlook-versions-supported-by-exchange-200720102013online.aspx
says " Please bear in mind there’s a difference between what is supported and what might be compatible with Exchange 2013"
Would the situation I'm thinking of be one of those 'compatible but unsupported' scenarios. i.e I can't think of any reason why the Outlook 2003 clients would have a need to connect to an E2K13 CAS server ...
I'd be interested to hear other people experiences/opinions on this. Thanks!

Hi,
Based on my knowledge, for internal users whose mailboxes exist on Exchange 2007, it is ok to still use Outlook 2003 as clients. Because
they will still connect to the Exchange 2007 Mailbox server instance hosting the mailbox. If the user is moved to Exchange 2013, please upgrade the Outlook client to higher version. Because Exchange 2013 doesn’t support Outlook 2003 client.
For Outlook 2003 clients connected to Exchange 2007, they doesn’t support autodiscover service to get some Exchange services such as free/busy information, OAB. Outlook 2003 would connect to Public Folder in Exchange 2007 to retrieve these
services. For OWA and ActiveSync service, it is not related to Outlook 2003 client, the CAS2013 would redirect the service request or send to CAS2007 for necessary data.
Regards,
Winnie Liang
TechNet Community Support

Exchange 2007 migrate to Exchange 2013

Dear MS Support,
I did migrate Exchange 2007 to Exchange 2013
The install complete, the exchange 2007 and 2013 can work together successful
DAG has created and work fine
Below is capture on exchange group after migrate
The exchange 2007 work fine with outlook anywhere, all the users can connected and send and receive mail in 5 year
The cerificate enroll with
Alternative Names: mail.biendongpoc.vn
The autodiscover on exchange 2007:
[PS] C:\Windows\system32>Get-ClientAccessServer | ft Identity,*uri* -AutoSize
Creating a new session for implicit remoting of "Get-ClientAccessServer" command...
Identity AutoDiscoverServiceInternalUri
BDPOC-SERVER1 https://mail.biendongpoc.vn/Autodiscover/Autodiscover.xml
I have created new certificate for Two exchange 2013
The certificate enroll with
Alternative Names: cas.biendongpoc.vn
I have create cname cas point to dag on DNS server
I have create A record autodiscover.biendongpoc.vn point to IP of dag.biendongpoc.vn
I did migrate mailbox from exchange 2007 to exchange 2013, the migrate successful , the outlook can
connected to Exchange 2013 and working perfectly
Our problem, the account exchange 2007 work not stable ,
sometime it connect to mail.abc.com, sometime it connect to cas.abc.com
If the outlook connect to cas.biendongpoc.vn, the request put password and i can't connect to exchange 2007, if outlook connect to mail.biendongpoc.vn i can connect
It is not stable for current exchange 2007
Anyone who can help me ?
Thanks

Hi
huynhtrongnhatminh,
I suggest you please go through this article.
http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx
Please check this for step by step guide.
http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-1-step-by-step-exchange-2007-to-2013-migration.aspx
Please point your autodiscover and commonname to Exchange2013 CAS
Please configure your URLs. There is no CAS array in Exchange2013 but the concept of single name space remains.
You need to have an A record (e.g. legacy.domain.com) in yout external DNS and add that name (legacy.domain.com) in your certificate for exchange 2007 users to have access externally.
Configure your commonname URLs in Exchange2013. Point commonname and autodiscover to exchange2013 in both external and internal DNS servers
Configure URLshttp://www.mustbegeek.com/configure-external-and-internal-url-in-exchange-2013/
No CASARRAY in 2013http://exchangeserverpro.com/exchange-2013-client-access-server-high-availability/
Please configure splitdns or pinpoint DNS in your internal DNS server if not configured
http://exchange.sembee.mobi/network/split-dns.asp
Thanks, MAS
Please mark as helpful if you find my comment helpful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

Exchange 2007 migration to Exchange 2013

Hello Exchange experts,
I’m Planning an Exchange migration (EX07 to EX13) and despite to have read many many tutorials and technet opinions, I cannot see the correct path to migrate. I hope someone can help me.
- Actual Infrastructure:
     1 Physical server (SERVER_08): DC + Exchange 2007. IP: 192.168.1.10
- Future Infrastructure:
     1 Physical Server (SERVER_2012R2): DC, GC, FS. IP: 192.168.1.50
    1 Physical Server (EX2013): CAS,Mailbox. IP: 192.168.1.51
My questions come once I’ve prepared the squema and I have to start with the Exchange Migration. As far as I know, I think the steps and infrastructure behavior will flow in this way:
Initial State: Only one Exchange2007 installed and all the clients point to this server, and thus in this moment the value of SCP is the initial Exchange Server SERVER_08.
In SERVER_08 there is one self-certificate with this names: SERVER_08.test.local and SERVER_08 and all the Outlook clients and Windows Phones use this certificate. This works perfectly.
I install a secondary Exchange (EX2013) in a new server but in the same internal domain (test.local).
Once the second Exchange server is installed, the SCP is automactly updated with the new SCP pointing to this Exchange 2013 (EX2013).
      So that the clients don’t give them
a prompt message, the SCP must be changed with PowerShell to point the initial    Exchange Server (SERVER_08). (Right?)
Create a A register (mail.test.local) pointing to the new Exchange 2013 (EX2013 - 192.168.1.51).
        At this point, I understand that the clients can coexist with both Exchange Servers (EX07/EX13) and no one will be prompted with new certificate issues. Right?
Once the Mailbox Databases/Connectors are migrated to the new exchange 2013, I need to modify again through PowerShell the SCP value with the new EX2013
(mail.test.local).
When the clients open again the Outlook client, will be prompted to agree the new Exchange 2013 certificate and
everything will work fine during the next 5 years (Exchange 2013 self-certificate lifetime).
I’ve been reading many tutorials and I want to make sure the steps until coexist both Exchange works fine, and obviously
if the experts can suggest me something.
Thanks in advance
Best Regards
Tecnico Superior de Sistemas

There a few things missing in here like the legacy URL specifics, and Outlook client version requirements (do not overlook Outlook, or it will bite you).
I'm curious about this bit "When the clients open again the Outlook client, will be prompted to agree the new Exchange 2013 certificate and
everything will work fine during the next 5 years (Exchange 2013 self-certificate lifetime). "
You should not be advocating the use of self signed certs, they are not supported for Outlook Anywhere. Even if this is testing, install a Windows CA and use that to issue certs of
get a cheap commercial one.
Training users it is OK to click here to see the dancing pigs never bodes well :)
Cheers,
Rhoderick
Microsoft Senior Exchange PFE
Blog:
http://blogs.technet.com/rmilne
Twitter:   LinkedIn:
  Facebook:
  XING:
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Migrate exchange 2007 mailboxes to exchange 2013

Hi Guys,
im trying to move exchange 2007 mailboxes to 2013. to cut to the chase, is this possible because im getting different kinds of errors?
Please advise if this is possible and how to do it.
Thanks!

Hi,
Below link also will help you
Microsoft Exchange Server Deployment Assistant
http://technet.microsoft.com/en-us/office/dn756393.aspx
Before migrating exchange server, Make a plan
try to practcice on lab. " Production environment and practice lab is entire different"
I dont know your environment. Hope your Domain controller and Exchange environment is residing in same place. If it is different site, move FSMO roles to that site for installing purpose.
IT is really challenge and excitement .
Try to find the solution of client outlook connectivity,
I had this problem, after I install Cumulative update, this problem gone.
Login ECP console after install exchange server,
Certificate installation,
DNS pointing, port forward,
Apply auto discover.
I faced another issue as well during the installation. My ex admin upgraded exchange server 2003 to 2007. He may not uninstall exchange server 2003 properly. Exchange server
2003 record was in active directory. Exchange 2013 doesnt suport mixed version of exchange 2003 and 2013. I have to delete the Exchange server 2003 record under DNS and Adsiedit. After that only exchange server 2013 allow to continue to install.
Best of Luck " Nothing is impossible"
Regards,
Joby

Exchange Migration 2007 2010 to Exchange 2013

Let me lay it all out. We are running an Exchange 2007 environment with 2-CAS, 2-HT's and 2-MBX's clustered. We started a migration to Exchange 2010 and after starting the migration it was decided that we would instead got to Exchange 2013. In Exchange 2010
we have 3-CAS, 2-HT's and 2-MBX's. We have moved our external connections over to Exchange 2010 and only have test mailboxes on 2010 and that's where we stopped.
We installed Exchange 2013 3-CAS, 2-MBX's. We are testing out 2013 installation. We can access 2013 Web App with the 2013 test accounts. I can access 2013 test mailbox with outlook 2010 by configuring outlook for rpc/https. I am not getting free/busy
form 2007 or 2013 when logged into my 2013 test mailbox. My virtual directories are configured as the following:
Exchange 2007 - mail2007.domain.com\
Exchange 2010 - mail.domain.com\
Exchange 2013 - mail2013.domain.com\

Hello,
Please check internalurl of the Exchange 2007 and 2010 EWS virtual, you can use:
Get-WebservicesVirtualDirectory | select internalurl
If they are not set to their own FQDN, please change it back and restart the IIS services.
Thanks,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

Redirection loop detected while opening Exchange 2007 mailboxes through Exchange 2013 OWA page

Team, in our infra Exchange 2013 CU8 & Exchange 2007 SP3 RU15 running. Exchange 2013 recently deployed but while opening exchange 2007 users mailbox through 2013 OWA getting error "Redirection loop detected". Want to update you few things :
Public DNS record created as mail.myinfra.in with x.x.x.2 IP and legacy.myinfra.in with x.x.x.3 IP.
Virtual directory modified mail.myinfra.in for 2013 & legacy.myinfra.in for 2007.
All the OWA request need to pass through public DNS only no internal DNS record for OWA.
Through ISA already rule created and tested also like https://mail.myinfra.in/owa giving me 2013 OWA page & https://legacy.myinfra.in/owa giving 2007 owa page. Only problem while opening https://mail.myinfra.in/owa with 2013 mailbox id/pwd working fine
but with 2007 mailbox id/pwd giving error "Redirection loop detected".
Appreciate if you can help quickly.

Hello
tip: check iis log on both of exch servers and check owa application haven't got "HTTP redirect" enabled.
sorry my english

Migrating Exchange 2007 SP1 to Exchange 2013

Follow the Exchange Deployment Assistant to the letter and you will not have issues.http://technet.microsoft.com/en-ca/exdeploy2013/Checklist.aspxAnd my guide:You need to make sure your OutlookAnywhere and AutoDiscover settings are setup properly along with Split-DNS. OutlookAnywhere and Split-DNS are vital for future-proofing your Exchange configuration and making it work properly now, regardless if you use Exchange 2007, 2010, or 2013. For Exchange 2013, OutlookAnywhere is a requirement and Split-DNS is Best Practice. If you are on Exchange 2007 or 2010, and you do not have OutlookAnywhere enabled, enable OutlookAnywhere and follow this guide.You should always use NTLM over Basic authentication, as Basic sends the username and password in the clear, and NTLM is Windows Authentication. On Exchange 2013, you also have a new option...

This is a slightly daunting task I must admit. I am migrating an old exchange 2007 SP1 installation over to 2013 SP1 and looking for good advice and/or tips. I am finding the whole thing slightly unnerving as there seems to be about a million caveats give or take a few thousand. There seems to be about the same amount of tips, tricks and guides as well, but sadly they are not quite consistent and some are down right contradicting each other.I'm reading similar questions here on spiceworks, and it seems like I'm reading about one horrible episode after another. By now, I assume most have migrated already, so I though I might pick some brains and figure out the best way to do this ;)Might software like CodeTwo Exchange Migration or Dell Migration Manager be a good idea? Are there maybe similar tools available as well?Any feedback is very...
This topic first appeared in the Spiceworks Community

Connect to Exchange 2007 Mailboxes with Exchange 2013 Management shell

Hello,
I was wondering if it is possible to use the Exchange 2013 Management Shell with the older version of Exchange 2007. When I run the console now it give me an error saying no exchange servers are available in the Active Directory site. When I use Exchange
management shell for 2007 the errors do not appear. Wondering if the management shell is backwards compatible.
Thanks,

No. your management shell MUST be the same roll-up version of exchange. I have applied updates and learned the hard way to block all updates that go beyond the server version you are
running.
http://social.technet.microsoft.com/wiki/contents/articles/240.exchange-server-and-update-rollup-bui...
To this end, you can use the same installation media that was used to install your Exchange server "Provided you are hosting your own", just install the management console instead of the whole thing,

OCS 2007 R2 and Exchange 2013

Similar Messages

Maybe you are looking for