Lync 2010 and 2013 coexistence - DNS

Hi all,
we are planning to upgrade from Lync server 2010 to 2013.During this mode,what is best to do regarding DNS?
Should we just keep existing ones and let Lync server proxy users, or do we need to point dns (internal and external) to the new 2013 server?
Like in Exchange 2010 and 2013 coexistence we had to point all dns to 2013 server,or users wont be proxied.
These are the DNS:
lyncdiscoverinternal
meet,dialin,admin
_sipinternaltls._tcp.domain.com
_sipfederationtls._tcp
sip.domain.com
Other DNS i might forgot?
thanks!
Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you. Thank you! Off2work

If you don't want to cut everyone over at once, you'll need different FQDNs for external web services between the pools, because mobility and meetings will use them both, regardless of where lyncdiscover and meet point.
If you want to keep the same name, that's fine, but you'll have to cut over in one big shot.
Also, pick a different name for the internal vs external web services. Mobility uses the external name, even when connecting on internal WiFi, so you'll want to redirect requests on port 443 to port 4443 for that and make it available internally.
If you have the same name for the internal web services, then internal requests will also use that path, which can cause issues or at the least route through a reverse proxy for no good reason.
Correct about pool FQDN being unique, also internal and external web service FQDNs unless you move everyone in one shot and don't care.
Everything else is pretty much a repoint when you're ready situation.
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answer".
SWC Unified Communications
This forum post is based upon my personal experience and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Similar Messages

Phone edition Aries Polycom CX600 coexistence - Lync 2010 and 2013

Hi all,
Currently busy with a Lync 2010 > 2013 migration where Aries Lync phones like Polycom CX 600 (using a blend of USB tethering, PIN authentication as well as common area phones) are involved. Phones have a blend of different CU releases ranging from .4066
(CU5) to .4451 (CU14)
User migration must be done in stages. That’s presenting a challenge in that Lync 2010 and 2013 must coexist for some time, yet providing seamless support for Lync phones.
The normal migration scenario will be based on a site-by-site migration: users are moved from 2010 to 2013, DHCP options for that site are changed to provide relevant Lync phones the new Lync 2013 pool parameters. HOWEVER, there is a considerable number
of users travelling across sites, and it’s likely occurrence that a user still on 2010 would travel to a site migrated to 2013 (including phones). And the other way round can also occur.
Based on this, my questions are:
1) Can a Lync 2010 user sign-in (USB tethering) on a phone if DHCP is providing options for Lync 2013?
2) Can a Lync 2010 user sign-in (PIN auth) on a phone if DHCP is providing options for Lync 2013?
3) Can a Lync 2013 user sign-in (USB tethering) on a phone if DHCP is providing options for Lync 2010?
4) Can a Lync 2013 user sign-in (PIN auth) on a phone if DHCP is providing options for Lync 2010?
Also, is there any dependancy on a specific CU version for the sign-in process to succeed? Note all discovery records are strict domain matching compliant.
I was hoping LPE would feature a redirect mechanism like with desktop client but based on the very little specific literature available, that does not seem the case. Any advice would be very welcome.
thanks all.
Alessio Giombini | Microsoft Solutions Architect | Twitter: @AlessioGiombini
Lync 2013 Detailed Design Calculator: try it at http://goo.gl/jU1hZR

Hi,
You can refer to the following link of “Lync 2010 – 2013 Migration: Lync phone edition devices”:
http://unifiedme.co.uk/2013/09/lync-2010-2013-migration-lync-phone-edition-devices/
Note: 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 link.
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

Lync Phone Edition coexistance with lync 2010 and 2013

Hi Everyone
I am currently planning a coexistent network between Lync 2010 and 2013 as I need to get 2013 out urgently. My question is around the Lync phone edition and how to get the phone to find the front end to register the phone to depending on which lync
pool the user is configured to use. Right now all phones are configured with DHCP and are configured to use the 2010 front end server to get its cert provisioned. I also use the HP 4110 and 4120 phones in the office.
How should I configure DHCP so that I do not cut my user off if they are moved the 2013 pool?
Many Thanks
Joe
Joe

Hi,
Check this old Thread
https://social.technet.microsoft.com/Forums/office/en-US/fca0b7be-124e-4480-ba2f-19ca4eebbd53/phone-edition-aries-polycom-cx600-coexistence-lync-2010-and-2013?forum=lyncvoice
http://unifiedme.co.uk/2013/09/lync-2010-2013-migration-lync-phone-edition-devices/
Whenever you see a helpful reply, click on Vote As Helpful & click on Mark As Answer if a post answers your question.

Exchange 2010 and 2013 coexistence Internal and external URL

Hi all,
been reading alot of threads about Outlook anywhere and virtual directories in co-existence exchange 2010 and 2013.
Still i dont get any smarter.
Here is scenario:
Exchange 2010
Cas1
Cas2
Mailbox1
Mailbox2
Casarray is Exchange.casarray,com ( internal dns pointed to CAS1 in exchange 2010).Seems like by default both exchange 2013 cas servers are added to the casarray.
Exchange 2013
CAS+Mailbox
Cas+Mailbox
DNS
mail.exchange.com pointing to VIP (kemp loadbalancer)
Autodiscover ( pointed to same vip ,kemp load balancer)
Outlook anywhere on all servers (2010 and 2013)
Internal ( pointing to VIP on Kemp)
External ( pointing to external IP,then it passes firewall that again passes to kemp)
Problem we are having is when migrating users from Exchange 2010 - 2013.
Users using Outlook 2010
restart of outlook and mail works fine.
OWA works fine
Active sync fails ( need to inherit permission of users AD object),wait couple of hours then mobile can sync again.)
Users using Outlook 2013
Outlook in disconnected status,only fix is to create new profile.
OWA works fine
Active sync fails ( need to inherit permission of users AD object),wait couple of hours then mobile can sync again.)
Question is,what should be set for internal and external url (active sync,owa,ews)on 2010 and 2013 servers?
Where is the config wrong?
Thanks!
Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you. Thank you! Off2work

Hi Martina,
did the test as mentioned,even tried both CAS 2013 servers.Flush and registerdns didnt help.
Still Outlook is Connected to the cas.exchange.as (which again Points to 1 of Exchange 2010 servers),
Tried repair Outlook profile,no og.Only fix is to setup New account.
Any more tips?
thanks!
Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you. Thank you! Off2work

Lync server 2010 and 2013 coexistence replacing edge servers

Hi all,
here is Our current deployment:
Lync server 2010:
1 edge
1 FE
3 branch sites
1 Monitoring server
Lync server 2013:
3 FrontEnd
2 Edge
2 Mediation
3 Backend
Simple urls are still point to Legacy (2010) servers.
External settings of Edge 2013 servers have been define With different name (Access,WEB and AV) and DNS (internally and externally) is pointing to New 2013 servers (via KEMP and TMG).
ATM 2013 topology is using edge2010 server.
Seems like we have two options for replacing Edge servers,one is Rip and replace and the other one is side by side transition.
We would like to do rip and replace so we can keep old simple urls (so that we dont have to send notice to external partners about Our New Access edge info) and using 2013 edge servers for federation and keep users on 2010 servers,then move them in
a controlled way.
What is the best way to do this?
Thanks!
Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you. Thank you! Off2work

Hi,
From your description above, the purpose is no need to update the New Access Edge info to the external partners. So for those external partners who set federation type of “Allowed Partner Server”, you need to keep the SIP domain name and the Edge Server
FQDN the same as before.
So base on my knowledge, you need to plan a down time, and firstly cancel the federation route for the Lync Edge 2010 Server. Delete the Lync Edge 2010 Server and publish the topology. Then deploy the Lync 2013 Edge Server with the same FQDN with Lync Edge
2010 Server. Then enable federation for it and point to the Lync Server 2013 FE Pool.
Best Regards,
Eason Huang
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]
Eason Huang
TechNet Community Support

Unknown Presence in Lync 2010 and Lync 2013 co-existence

I have lync 2010 and lync 2013 in my environment. Everything was working fine except when I moved the DNS of the Lync 2013 pool to the load balancer. When I did that, users on lync2013 could see the presence of users on Lync2010 pool but not vice versa.
I have point the Lyncdiscoverinternal.domain.com to the lync2013 pool DNS. I have opened migration ports on the load balancer but still not working. It works perfectly fine if I point the DNS of the pool to one server directly without going
through the Load balancer VIP.
Am I missing anything here?
Thanks!
Alert from TechNet Posting

Hi Kojo Obeng Antwi,
Please check out the following information.
Deploying DNS load balancing on Front End pools requires you to perform a couple of extra steps with FQDNs and DNS
records.
A pool that uses DNS load balancing must have two FQDNs: the regular pool FQDN that is used by DNS load balancing (such as pool01.contoso.com), and resolves to the physical
IPs of the servers in the pool, and another FQDN for the pool’s Web services (such as web01.contoso.com), which resolves to virtual IP address of the pool.
In Topology Builder, if you want to deploy DNS load balancing for a pool, to create this extra FQDN for the pool’s Web services
you must select the Override internal Web Services pool FQDN check box and type the FQDN, in the Specify the Web Services URLs for this Pool page.
To support the FQDN used by DNS load balancing, you must provision DNS to resolve the pool FQDN (such as pool01.contoso.com) to the IP addresses of all the servers in the pool
(for example, 192.168.1.1, 192.168.1.2, and so on). You should include only the IP addresses of servers that are currently deployed.
Best regards,
Eric

Need assistance creating applications with superseedence to uninstall Office 2010, Lync 2010 and then install Office 365 click to run 2013

We are getting ready in a few months to uninstall our locally installed Office 2010 and head to the cloud with Office 365 2013. I have created applications to uninstall Office 2010 and Lync 2010 and then added them to the supersedence tab for Office 365
office 2013 click to run with appv5.
When deploying the office 365 2013 application it does not uninstall office 2010 or lync 2010 with the supersedence. I am able to manually uninstall Office 2010 and Lync 2010 with the command lines I am using in the applications.
The application uninstall for Office 2010 is:
The application uninstall is an exe so I created an application, created a deployment type with the location of our Office 2010 admin point, installation program and uninstall program are set with the same line as I have tried to deploy it separately and
also as a supersedence in the Office 365 application setup.exe /uninstall ProPlus /config "\\sccmserver\share\Office2010\ProPlus.ww\silentuninstallconfig.xml. The silentuninstallconfig.xml was created from the original config.xml file and edited
to these settings:<Configuration Product="ProPlus">
<Display Level="none" CompletionNotice="NO" SuppressModal="yes" AcceptEula="yes" />
<Setting Id="Reboot" Value="Never" />
<Setting Id="SETUP_REBOOT" Value="NEVER" />
<OptionState Id="ProductFiles" State="Local" Children="force" />
</Configuration>
The detection method is the folder path to see that office 14 exists. When I deploy this the machines finish with success showing this exists, but does not uninstall Office 2010.
running the command line manually mapped to this location on a machine uninstalls office 2010 without issue.
Lync 2010 uninstall:
Lync is an exe so I am using the LyncSetup.exe /silent /uninstall. The application is in the supersedence tab for Office 365 2013. This never installs. If I create a softare distribution and deploy it on its own it uninstalls without issue.
We are going to use Lync 2013 with our office 365 2013 installation so we need to uninstall this. The detection method for lync is file system folder and the Microsoft lync folder for detection.
MS Office 15 (Office 365) was created with the click to run tool. I can install this with the application I created using the appv5 package created with the click to run tool. The issue is we need Office 2010 and Lync 2010 uninstalled first.
Having both versions of Office installed in test has caused issues where Office 15 365 will not list in add and remove programs and cannot be uninstalled even with the fix it article to remove office 2013.
I have looked at many articles and so far it is not working for us. Any help appreciated to get us to the cloud.
Thanks,
Brit

The applications I have for uninstall of office 2010 and Lync 2010 for some reason do not uninstall. Manually testing the command lines they do. The detection method seems to be hanging things up. On the lync uninstall detection method I have
the setting type of file system, type folder, path c:\program files\ folder name Microsoft Lync.
I highly recommend using something other than a file/folder "exists" detection method. Installers are constantly leaving things behind due to environmental inconsistencies. It may leave files/folders behind with a schedule to delete files on next reboot.
These things are unpredictable and very hard to use. I just use the "HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall" Registry location. There you can actually key off the "Product Version" DWORD as well which gives you an even more accurate method
to determine if the application you are trying to deploy (or expect to exist) is truly there. This, of course, being if you are not using an MSI. If you have MSI technology ALWAYS use the product code unless the person writing the MSI chooses to use the same
product code for every version release of their product. In which case, Use the registry method.
As far as getting the supersedence and everything working. You need to start from the basics. Create Applications for all of the apps you want to remove. Make sure they install and uninstall properly (seems like overkill but it isn't that hard). Once you
have working install/uninstall applications then you can easily apply supersedence to your new applications with a setting of Uninstall on the superseded apps you should have no problem getting rid of them. I have done this for numerous things.
For example, I did this with Cisco Jabber to replace older versions of jabber, older versions of cisco unified personal communicator and lync and OSC. All of these replaced versions had to have an Application but once it was in it took two seconds to apply
all the supersedence rules and now I know when I push that software out no matter version is running on any machine it will pull all the old apps off and put the new one on.
Dustin Estes - MCP | www.dustinestes.com

Lync 2010 and Lync 2013 blinking icon in taskbar not working properly

Hi,
We're experiencing a strange behaviour. Lync IM notifications are supposed to work this way below:
1) Notification bubble on the right-bottom corner
2) After a few seconds, a blinking icon in the task bar
3) After a few seconds, a coloured icon remains in the task bar
Some of our users, both Lync 2010 and Lync 2013, go 1) and 2) but then icon won't remain in the task bar, so they don't realize they have a conversation waiting (Windows XP and Windows 7).
If they open the icon, the conversation is there and coloured, and they can answer.
In my computer, it has also happened but most of the time it works fine (testing it, maybe it works 15 times and fails 1). Nevertheless, a lot of people is suffering from this strange behaviour.
We have looked into the causes but haven't found anything.
Any clue?
Thanks!

How long have you seen the problem?
What version of your Lync client? Try to update your Lync client to the latest version.
Try to repair office 2013.
Uninstall and reinstall Lync 2010.
Please install Lync 2013 or Lync 2010 on a fresh installation of Window to check if you can still see this problem.
Lisa Zheng
TechNet Community Support

Co-Existence Lync 2010 and Lync 2013

Hi,
How do we check that CMS is moved from lync 2010 to Lync 2013 in Co-Existance environment lync standard edition.
I know that users are moved form Lync 2010 to Lync 2013 but i don't if CMS is moved? And in the existing co-existence we have two edge servers Lync 2010 and Lync 2013. How can i check if traffic is routing through Lync 2010 or lync 2013.
Because we want to Decommission the Lync 2010 STD Edition before doing this i want to make sure every thing go smooth.
Please help me on this.
Thanks
Whenever you see a helpful reply, click on Vote As Helpful & click on Mark As Answer if a post answers your question.

To find out if the CMS is moved:
Get-CsConfigurationStoreLocation, if it's a standard server it will tell you the pool name. If it's an Enterprise server, it will tell you the SQL server name associated with the pool.
http://technet.microsoft.com/en-us/library/gg412814.aspx
Otherwise it's at the top of the topology builder (the top top part that says Lync Server in the left pane, under the Central Management Server spot in the right pane.
For a full decommission article, here's a decent one with screenshots. As Ben said, if you can advise about the other places we could be more specific.
http://www.oiboran.com/?p=1073
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answer".
SWC Unified Communications

Exchange 2007 and 2013 coexistence

Hi,
we have exchange 2007 and 2013 coexistence. we have created a new url for 2007 legacy servers. Now, when using OWA url (now set for exchange 2013 server) i am getting OWA exchange 2007 login page for exchange 2007 mailboxs.
I was expecting exchange 2013 OWA page and then redirection to OWA 2007.
Thanks

Hello,
Please check your DNS configuration and ISA/TMG rules.
We recommend you use TMG or UAG.
You can refer to the "TMG rules" section in the following article:
http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-3-step-by-step-exchange-2007-to-2013-migration.aspx
Cara Chen
TechNet Community Support

CMS database move from Lync 2010 to 2013 went well but.....

Something odd when I was done. Everything went perfectly. No errors at all and went as expected. I noticed though after everything was done and I had not yet uninstalled the CMS from Lync 2010 that two services on the Lync 2010 were stopped but in an Automatic
startup state. They are the "Lync Server File Transfer Agent' and the "Lync Server Master Replicator Agent'. Thought it was odd they were both stopped. I am sure it had something to do with the CMS move and all the scripting that goes on. The rest
of the Lync services are running.
I am thinking though if they were supposed to be stopped, why not disable them. Why leave them at Automatic. I am not seeing any errors or warnings at all on the Lync 2010 or 2013 servers. Application, System and Lync Server logs are clean. Everything appears
to be OK.
Thing that concerns me though is when I run the Get-CsManagementStoreReplicationStatus on the 2013 FE, the databases all come back looking good with UpToDate = True but the last replication was last night (about 8-9 hours ago) shortly after I completed the
procedure.
I want to just uninstall the CMS on Lync 2010 which is the last step but I want to make sure everything is OK before I do. Not sure if I should start those services. I never rebooted the 2010 server after moving the CMS. Seems if I did, those services would
have tried to start. Very confused here.
Wanted to add also that I have both the above services on the 2013 FE server and they are both running. And, when I run Get-CsManagementStoreReplicationStatus -CentralManagementStoreStatus on my Lync 2013 FE, it says it is the active master and active file
transfer agent so maybe that is why the services are stopped? If so, what if I had rebooted the 2010 server. Those services would have tried to start because they are set to Automatic.
I guess the real question here is how often should the Lync servers being updating their replicas with each other. We have a very small environment right now with only a few hundred users.

This process of transferring information updates from master to replica is called replication. The replication process consists of copying information between directories from the master to the replicas, applying the changes received to the
replica and report status back to the master.
The MASTER generates the data package containing new changes to CMS and stores a copy in each to-replica directory for every replica.
The data package must be copied to all replicas. All Lync Server 2013 servers, except the Edge Server, uses the Windows file copy SMB protocol mechanism to push the data package from the CMS master to the replica.
For Edge servers, since Edge servers is not a member of domain, the file copy is performed over an HTTPS channel. The Edge Server runs a Web Service on the port specified for the ManagementServices in the topology document. The default port is 4443. Even
you Move CMS store and CMS Master service from 2010 to 2013, the replication is a logical concept so you can replicate CMS information with the help of Lync server 2013 CMS master service.
You can refer to the link below, it is for Lync server 2010 but similar for Lync server 2013:
https://blogs.technet.com/b/jenstr/archive/2010/10/13/what-is-central-management-store-cms.aspx
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

Lync 2010 to 2013 Migration DB issue, central management database.

Hello ,
During Lync 2010 to 2013 migration , on my back end database for Lync 2013 I previously created there data base instances on my lync 2013 BE , (RTC,MON, ARC) THERE DIFFERENT ISTNACE using sql server enterprise 2012 .
Now I want to finish the migration by moving the central management server to the lync server 2013.
my question now I tried to create a new DB instance and I face some issue related the space on the server .
can I use any of the existing isnatce which I created before for the (RTC,MON, ARC) or can I sue the default instance which is created by default with sql 2012 server installation .to install the central management database.
do I need a spate instance ? for the new central management store on my lync server 2013
Thanks
MK

Hello
After I run the command
Install-CsDatabase -CentralManagementDatabase -SqlServerFqdn hq-lync2013-be.MYDOMAIN -SqlInstanceName RTC.
-Then
Enable-CsTopology
-Then
Move-CsManagementServer .
And now after the move when I check the logs :
WARNING: The move completed successfully but the following additional steps are required:
Run local setup on the following computers to remove Central Management services that are no longer defined in the topology:
    - HQ-LYNC-FE-01.MYDOMAIN
WARNING: "Move-CsManagementServer" processing has completed with warnings. "2" warnings were recorded during this run.
WARNING: Detailed results can be found at
"C:\Users\MYUSER\AppData\Local\Temp\2\Move-CsManagementServer-0d4806f4-554d-497d-a0dc-0fc98a6e076d.html".
THESE AR ETEH TWO WARININGS :
Warning: Failed to cleanup file store for the new Central Management Server. Error The directory is not empty.
Warning: The move completed successfully but the following additional steps are required:
Run local setup on the following computers to remove Central Management services that are no longer defined in the topology:
- HQ-LYNC-FE-01.MYDOMAIN.
I Run the local setup on both the FE2013 AND FE2010.
now when I run the command :
Get-CsManagementStoreReplicationStatus
UpToDate           : False    (I shutdown this server )
ReplicaFqdn        : HQ-EDGE01.mydomain
LastStatusReport   :
LastUpdateCreation : 3/16/2015 1:52:45 PM
ProductVersion     :
UpToDate           : False
ReplicaFqdn        : HQ-LYNC2013-FE.mydomain
LastStatusReport   :
LastUpdateCreation : 3/16/2015 1:52:45 PM
ProductVersion     :
UpToDate           : False
ReplicaFqdn        : HQ-LYNC-FE-01.mydomain
LastStatusReport   :
LastUpdateCreation : 3/16/2015 1:52:45 PM
ProductVersion     :
UpToDate           : False
ReplicaFqdn        : HQ-LYNC-MA-01.mydomain
LastStatusReport   :
LastUpdateCreation : 3/16/2015 1:52:45 PM
ProductVersion     :
NOW THEER IS REPLICATION ISSUE ?
I notice that service on my lync 2010 SOME OF THEM ARE STOPPED :
FILE TRANSFER AGENT , MASTER REPLICATORE AGENT , CALL PARK SERVICE (ALL ON LYNC 2010)
ALL SERVICE ON 2013 FE IS OK AND RUNNING..
I notice this error in my lync server 2013 vents .
I host the shared file on my lync server 2010 mediation server
Microsoft Lync Server 2013, Master Replicator Agent service encountered an error while accessing a file share and will continuously attempt to access this file share until this issue is resolved. While this condition persists, replication to replica machines
might not occur.
IO failure occurred for Path=\\HQ-LYNC-MA-01.mydomain\LYNCSHARE\1-CentralMgmt-1\CMSFileStore\xds-master\working\replication\tmp. Exception=Access to the path '\\HQ-LYNC-MA-01.mydomain\LYNCSHARE\1-CentralMgmt-1' is denied..
Cause: Possible issues with file share permissions. This can occur if the computer hosting the file share has outdated cached credentials for the computer that is trying to access the file share.
Resolution:
For details about how to resolve file share permission issues, see the product documentation.
SO ANY ADVICE ?
Regards
MK

Lync 2010 to 2013 migration - Moving the conferencing directory ?

I am in the process of finishing our migration from Lync 2010 to 2013.
Reading the technet page, I don't see any mention to migrate the Lync 2010 Conferencing Directory to 2013.
http://technet.microsoft.com/en-us/library/jj204998.aspx
But doing some quick research, I see that some blog are suggesting of doing it:
http://www.oiboran.com/?p=1219
All my users have already been migrate to the Lync 2013 Pool. No problem so far.
But I am still wondering if the Lync 2010 conferencing should be move or not?
thanks
John

In step 7,
http://technet.microsoft.com/en-us/library/jj688011.aspx
The following user account information does not move to the new server.
Meeting content. In order to move the content shared during a meeting, for example PowerPoint, Whiteboard, attachments or poll data, use the
-MoveConferenceData parameter as part of the Move-CsUser cmdlet.
====
Did you move users with the GUI or with move-csuser -MoveConferenceData?
If you moved with the GUI, the conference data noted above isn't moved. If you think your users would care about this, you could move the directory to 2013 and forget about it. Otherwise, you could just remove it as you decommission the 2010
pool. It's rare that people would care about this data.
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answer".
SWC Unified Communications

Outlook 2010 and 2013 are unable to connect but OWA (and mail routing) works fine

Hi-
Not sure why but this past Sunday (just after DST adjustment) outlook clients (using 2010 and 2013) were unable to connect to an Exchange 2013 server. OWA and mail routing (internal and external) is working fine. I've even tried on multiple machines
and all of them experience the same issue. On a new machine with a fresh version of outlook 2013 installed here is what happens:
Click on Outlook 2013
Click Next until the account setup is displayed.
Name and email is auto-populated
Established network connection is good
Searching for email address settings is good (once the self-signed exchange 2013 cert is accepted)
And then the logging onto the mail server fails. The first pop-up is:
The Connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action.
Clicking "OK" is followed up with a window with the Microsoft Exchange connection info.
It lists Microsoft Exchange server which is populated with: GUID@<domain suffix>
Mailbox which is populated with: =SMTP:<Valid Email address>
On the Exchange Server I have noticed that the Web Management Service (WMSVC) is stopped and will not start. Starting the service outputs:
EventID 7024
"The Web Management Service terminated with the following service-specific error: Unspecified error"
Not really helpful :)
Since this is only happening with Outlook on multiple clients I'm expecting something with Exchange or the ability for outlook to connect to exchange.
Thanks in advance!

Hi
I know this is an old post, but I'm having a very similar issue. I have CU6 installed and all other client connectivity apart from internal Outlook connectivity is working fine. I have distributed the new Self-Signed Certificate and the tested to verify
the clients trust it. I have tried on multiple machine with multiple accounts and none of them connect.
I'm at the stage of reinstalling, but I would rather troubleshoot the problem, just in case ever hit the same wall in the future. I have run Test-OutlookConnectivity with the following output;
RunspaceId : 71f8d740-c499-4bbe-8baf-9cbb12566fb8
Server : PW-SC-01.companyname.local
MonitorIdentity : Outlook.Protocol\OutlookRpcDeepTestProbe\NEW2013
RequestId : 75641e34-aa49-4fce-aad7-181b56dd7b29
ExecutionStartTime : 10/11/2014 13:50:03
ExecutionEndTime : 10/11/2014 13:50:03
Error : Error 0x6ba (The RPC server is unavailable) from ClientAsyncCallState.CheckCompletion:
RpcAsyncCompleteCall
EEInfo: ComputerName: n/a
EEInfo: ProcessID: 14544
EEInfo: Generation Time: 2014-11-10 13:50:03.737
EEInfo: Generating component: 2
EEInfo: Status: 0x000006BA
EEInfo: Detection location: 1710
EEInfo: Flags: 0
EEInfo: NumberOfParameters: 1
EEInfo: prm[0]: Long val: 0 (0x00000000)
EEInfo: ComputerName: n/a
EEInfo: ProcessID: 14544
EEInfo: Generation Time: 2014-11-10 13:50:03.737
EEInfo: Generating component: 13
EEInfo: Status: 0x000006BA
EEInfo: Detection location: 1352
EEInfo: Flags: 0
EEInfo: NumberOfParameters: 1
EEInfo: prm[0]: Long val: -1073606646 (0xC002100A)
EEInfo: ComputerName: n/a
EEInfo: ProcessID: 14544
EEInfo: Generation Time: 2014-11-10 13:50:03.737
EEInfo: Generating component: 14
EEInfo: Status: 0xC002100A
EEInfo: Detection location: 1380
EEInfo: Flags: 0
EEInfo: NumberOfParameters: 2
EEInfo: prm[0]: Long val: 12175 (0x00002F8F)
EEInfo: prm[1]: Unicode string: /rpc/rpcproxy.dll?PW-SC-01.companyname.local:6001
EEInfo: ComputerName: n/a
EEInfo: ProcessID: 14544
EEInfo: Generation Time: 2014-11-10 13:50:03.737
EEInfo: Generating component: 14
EEInfo: Status: 0x00010000
EEInfo: Detection location: 1385
EEInfo: Flags: 0
EEInfo: NumberOfParameters: 2
EEInfo: prm[0]: Long val: 8 (0x00000008)
EEInfo: prm[1]: Binary Buffer: [48-1263-10248-1262-126-9632122164676121-3988104-118-11373-61-94
-111-112-98-1217048136942-12272-122-91311550483449324830638543192311910198979999101115115461121199
91111091091154699111461171074830231349524949485349505348484990231349574949485349505348484990483449
324830638543192311910198979999101115115461121199911110910911546991114611710748-12613448136942-1227
2-122-913111503-126115048-1261102-126110-22103-15-109-16-121-119-3121-4-106119-119-9369122-5779121
719-98-24-67-32918-98-236-19-10715326827-76102-61100108-12718-438331-37109-102-57-9942-11389-10374
-77-5-4-107109-11847342222-63-48-7468-17-1067033-56111-33-54-16-105-62-76-1282011-1664-12158-4915-
88-53-9-29-2994-49-54-5211-1364-212121-12396-127-353-396185117-681229-434246070-109818119-4858-128
-106-1279248-49110-44-81-121494199-118-17-106-71106828294-93-110-110-106-415084-127126-45-12331421
-61-2757-24-128-28-25111-52113121-56-98-5821527282-47255245104-111-55-1099747-115-11172-287-12526-
79-12430-119421360-107-6430-5410282-52-51-128533354-116672757-77-75-111-72-118-10114-84484825-40-1
8-70-24-9111-61-5391-8034125-12632-16-19-128112030-8-427523101-93-127-5348-127-5648146385291511-14
4325-9648-127-110638529174-127-11848-127-121-12623119101989799991011151154611211999111109109115469
911146117107-1262211211945115994548494611211999111109109115461081119997108-12626651171161116810511
59911111810111446808767111109109115461081119997108-12626651171161116810511599111118101114468087671
11109109115469911146117107-12613808767111109109115461081119997108-12613808767111109109115469911146
11710748196385293741248106843615573148126385291911-14248048136942-12272-122-913115503-12611081-930
6613-74953718-12745-14-25-94107-80-5-45-2231536-1728-12897-8587577-1252765-892896-83-10267-7926-20
-9841-1079-12-29-4315671111357-684036-40-5129-91-24-461066-12306-65-9118-89115191071-30-20-1067161
-83-91-74105-931649-48-96126-13-71-118-8967567-40-64-104-113-31-51-102357125100-50113-103-113123-9
873-627067-25-908-10131118125122-71-115-37-1850-1055851-31410-77-7312-36848124-26104-10711043-2048
-48-12666611759121127-2960-1571-9-95-98-1036911610-74221-32-25114-108749933-7147562114-3635-101-81
-1058-73108-61-78-128-116-715155112714-37-18-84-8331-2716-1174257-76-5-1598-15-12875-98-7329632178
-10714-123-6312212-1028359-56-76-683-873987-2120-845954-7617-71-57999828110], size=926
Exception : Microsoft.Exchange.Rpc.ServerUnavailableException: Error 0x6ba (The RPC server is unavailable)
from ClientAsyncCallState.CheckCompletion: RpcAsyncCompleteCall
EEInfo: ComputerName: n/a
EEInfo: ProcessID: 14544
EEInfo: Generation Time: 2014-11-10 13:50:03.737
EEInfo: Generating component: 2
EEInfo: Status: 0x000006BA
EEInfo: Detection location: 1710
EEInfo: Flags: 0
EEInfo: NumberOfParameters: 1
EEInfo: prm[0]: Long val: 0 (0x00000000)
EEInfo: ComputerName: n/a
EEInfo: ProcessID: 14544
EEInfo: Generation Time: 2014-11-10 13:50:03.737
EEInfo: Generating component: 13
EEInfo: Status: 0x000006BA
EEInfo: Detection location: 1352
EEInfo: Flags: 0
EEInfo: NumberOfParameters: 1
EEInfo: prm[0]: Long val: -1073606646 (0xC002100A)
EEInfo: ComputerName: n/a
EEInfo: ProcessID: 14544
EEInfo: Generation Time: 2014-11-10 13:50:03.737
EEInfo: Generating component: 14
EEInfo: Status: 0xC002100A
EEInfo: Detection location: 1380
EEInfo: Flags: 0
EEInfo: NumberOfParameters: 2
EEInfo: prm[0]: Long val: 12175 (0x00002F8F)
EEInfo: prm[1]: Unicode string: /rpc/rpcproxy.dll?PW-SC-01.companyname.local:6001
EEInfo: ComputerName: n/a
EEInfo: ProcessID: 14544
EEInfo: Generation Time: 2014-11-10 13:50:03.737
EEInfo: Generating component: 14
EEInfo: Status: 0x00010000
EEInfo: Detection location: 1385
EEInfo: Flags: 0
EEInfo: NumberOfParameters: 2
EEInfo: prm[0]: Long val: 8 (0x00000008)
EEInfo: prm[1]: Binary Buffer: [48-1263-10248-1262-126-9632122164676121-3988104-118-11373-61-94
-111-112-98-1217048136942-12272-122-91311550483449324830638543192311910198979999101115115461121199
91111091091154699111461171074830231349524949485349505348484990231349574949485349505348484990483449
324830638543192311910198979999101115115461121199911110910911546991114611710748-12613448136942-1227
2-122-913111503-126115048-1261102-126110-22103-15-109-16-121-119-3121-4-106119-119-9369122-5779121
719-98-24-67-32918-98-236-19-10715326827-76102-61100108-12718-438331-37109-102-57-9942-11389-10374
-77-5-4-107109-11847342222-63-48-7468-17-1067033-56111-33-54-16-105-62-76-1282011-1664-12158-4915-
88-53-9-29-2994-49-54-5211-1364-212121-12396-127-353-396185117-681229-434246070-109818119-4858-128
-106-1279248-49110-44-81-121494199-118-17-106-71106828294-93-110-110-106-415084-127126-45-12331421
-61-2757-24-128-28-25111-52113121-56-98-5821527282-47255245104-111-55-1099747-115-11172-287-12526-
79-12430-119421360-107-6430-5410282-52-51-128533354-116672757-77-75-111-72-118-10114-84484825-40-1
8-70-24-9111-61-5391-8034125-12632-16-19-128112030-8-427523101-93-127-5348-127-5648146385291511-14
4325-9648-127-110638529174-127-11848-127-121-12623119101989799991011151154611211999111109109115469
911146117107-1262211211945115994548494611211999111109109115461081119997108-12626651171161116810511
59911111810111446808767111109109115461081119997108-12626651171161116810511599111118101114468087671
11109109115469911146117107-12613808767111109109115461081119997108-12613808767111109109115469911146
11710748196385293741248106843615573148126385291911-14248048136942-12272-122-913115503-12611081-930
6613-74953718-12745-14-25-94107-80-5-45-2231536-1728-12897-8587577-1252765-892896-83-10267-7926-20
-9841-1079-12-29-4315671111357-684036-40-5129-91-24-461066-12306-65-9118-89115191071-30-20-1067161
-83-91-74105-931649-48-96126-13-71-118-8967567-40-64-104-113-31-51-102357125100-50113-103-113123-9
873-627067-25-908-10131118125122-71-115-37-1850-1055851-31410-77-7312-36848124-26104-10711043-2048
-48-12666611759121127-2960-1571-9-95-98-1036911610-74221-32-25114-108749933-7147562114-3635-101-81
-1058-73108-61-78-128-116-715155112714-37-18-84-8331-2716-1174257-76-5-1598-15-12875-98-7329632178
-10714-123-6312212-1028359-56-76-683-873987-2120-845954-7617-71-57999828110], size=926
at Microsoft.Exchange.Rpc.ClientAsyncCallState.CheckCompletion()
at Microsoft.Exchange.Rpc.ExchangeClient.ClientAsyncCallState_Connect.End(IntPtr&
contextHandle, TimeSpan& pollsMax, Int32& retryCount, TimeSpan& retryDelay, String& dn
PoisonedCount : 0
ExecutionId : 63105129
SampleValue : 33.5194
ExecutionContext : Mailbox logon verification
EMSMDB.Connect()
Task produced output:
- TaskStarted = 10/11/2014 13:50:03
- TaskFinished = 10/11/2014 13:50:03
- Exception = Microsoft.Exchange.Rpc.ServerUnavailableException: Error 0x6ba (The RPC
server is unavailable) from ClientAsyncCallState.CheckCompletion: RpcAsyncCompleteCall
EEInfo: ComputerName: n/a
EEInfo: ProcessID: 14544
EEInfo: Generation Time: 2014-11-10 13:50:03.737
EEInfo: Generating component: 2
EEInfo: Status: 0x000006BA
EEInfo: Detection location: 1710
EEInfo: Flags: 0
EEInfo: NumberOfParameters: 1
EEInfo: prm[0]: Long val: 0 (0x00000000)
EEInfo: ComputerName: n/a
EEInfo: ProcessID: 14544
EEInfo: Generation Time: 2014-11-10 13:50:03.737
EEInfo: Generating component: 13
EEInfo: Status: 0x000006BA
EEInfo: Detection location: 1352
EEInfo: Flags: 0
EEInfo: NumberOfParameters: 1
EEInfo: prm[0]: Long val: -1073606646 (0xC002100A)
EEInfo: ComputerName: n/a
EEInfo: ProcessID: 14544
EEInfo: Generation Time: 2014-11-10 13:50:03.737
EEInfo: Generating component: 14
EEInfo: Status: 0xC002100A
EEInfo: Detection location: 1380
EEInfo: Flags: 0
EEInfo: NumberOfParameters: 2
EEInfo: prm[0]: Long val: 12175 (0x00002F8F)
EEInfo: prm[1]: Unicode string: /rpc/rpcproxy.dll?PW-SC-01.companyname.local:6001
EEInfo: ComputerName: n/a
EEInfo: ProcessID: 14544
EEInfo: Generation Time: 2014-11-10 13:50:03.737
EEInfo: Generating component: 14
EEInfo: Status: 0x00010000
EEInfo: Detection location: 1385
EEInfo: Flags: 0
EEInfo: NumberOfParameters: 2
EEInfo: prm[0]: Long val: 8 (0x00000008)
EEInfo: prm[1]: Binary Buffer: [48-1263-10248-1262-126-9632122164676121-3988104-118-11373-61-94
-111-112-98-1217048136942-12272-122-91311550483449324830638543192311910198979999101115115461121199
91111091091154699111461171074830231349524949485349505348484990231349574949485349505348484990483449
324830638543192311910198979999101115115461121199911110910911546991114611710748-12613448136942-1227
2-122-913111503-126115048-1261102-126110-22103-15-109-16-121-119-3121-4-106119-119-9369122-5779121
719-98-24-67-32918-98-236-19-10715326827-76102-61100108-12718-438331-37109-102-57-9942-11389-10374
-77-5-4-107109-11847342222-63-48-7468-17-1067033-56111-33-54-16-105-62-76-1282011-1664-12158-4915-
88-53-9-29-2994-49-54-5211-1364-212121-12396-127-353-396185117-681229-434246070-109818119-4858-128
-106-1279248-49110-44-81-121494199-118-17-106-71106828294-93-110-110-106-415084-127126-45-12331421
-61-2757-24-128-28-25111-52113121-56-98-5821527282-47255245104-111-55-1099747-115-11172-287-12526-
79-12430-119421360-107-6430-5410282-52-51-128533354-116672757-77-75-111-72-118-10114-84484825-40-1
8-70-24-9111-61-5391-8034125-12632-16-19-128112030-8-427523101-93-127-5348-127-5648146385291511-14
4325-9648-127-110638529174-127-11848-127-121-12623119101989799991011151154611211999111109109115469
911146117107-1262211211945115994548494611211999111109109115461081119997108-12626651171161116810511
59911111810111446808767111109109115461081119997108-12626651171161116810511599111118101114468087671
11109109115469911146117107-12613808767111109109115461081119997108-12613808767111109109115469911146
11710748196385293741248106843615573148126385291911-14248048136942-12272-122-913115503-12611081-930
6613-74953718-12745-14-25-94107-80-5-45-2231536-1728-12897-8587577-1252765-892896-83-10267-7926-20
-9841-1079-12-29-4315671111357-684036-40-5129-91-24-461066-12306-65-9118-89115191071-30-20-1067161
-83-91-74105-931649-48-96126-13-71-118-8967567-40-64-104-113-31-51-102357125100-50113-103-113123-9
873-627067-25-908-10131118125122-71-115-37-1850-1055851-31410-77-7312-36848124-26104-10711043-2048
-48-12666611759121127-2960-1571-9-95-98-1036911610-74221-32-25114-108749933-7147562114-3635-101-81
-1058-73108-61-78-128-116-715155112714-37-18-84-8331-2716-1174257-76-5-1598-15-12875-98-7329632178
-10714-123-6312212-1028359-56-76-683-873987-2120-845954-7617-71-57999828110], size=926
at Microsoft.Exchange.Rpc.ClientAsy
FailureContext :
ExtensionXml :
ResultType : Failed
RetryCount : 0
ResultName : 75641e34aa494fceaad7181b56dd7b29-OutlookRpcDeepTestProbe/NEW2013
IsNotified : False
ResultId : 1748063
ServiceName : InvokeNow
StateAttribute1 : Momt
StateAttribute2 : UnknownIssue
StateAttribute3 : PW-SC-01.companyname.local
StateAttribute4 : Unknown
StateAttribute5 : {C54AD38D-1E00-4F53-ABAE-26518C3FF82F}
StateAttribute6 : 0
StateAttribute7 : 0
StateAttribute8 : 0
StateAttribute9 : 0
StateAttribute10 : 0
StateAttribute11 : Momt
StateAttribute12 :
StateAttribute13 : VgEAVAdXaW5kb3dzQwBBCEtlcmJlcm9zTA9QV0NPTU1TXG5hdGhhbmhVLlMtMS01LTIxLTIwNTc0OTEwMzItMzE4NDA2NDk3OC
0xNTQ2MTE0ODM1LTI2MzJHHQAAAAcAAAAtUy0xLTUtMjEtMjA1NzQ5MTAzMi0zMTg0MDY0OTc4LTE1NDYxMTQ4MzUtNTEzBwAA
AAdTLTEtMS0wBwAAAAdTLTEtNS0yBwAAAAhTLTEtNS0xMQcAAAAIUy0xLTUtMTUHAADAE1MtMS01LTUtMC0zNDc3ODcxMTMHAA
AALlMtMS01LTIxLTIwNTc0OTEwMzItMzE4NDA2NDk3OC0xNTQ2MTE0ODM1LTQxODcHAAAALVMtMS01LTIxLTIwNTc0OTEwMzIt
MzE4NDA2NDk3OC0xNTQ2MTE0ODM1LTUxMgcAAAAuUy0xLTUtMjEtMjA1NzQ5MTAzMi0zMTg0MDY0OTc4LTE1NDYxMTQ4MzUtND
E3NAcAAAAuUy0xLTUtMjEtMjA1NzQ5MTAzMi0zMTg0MDY0OTc4LTE1NDYxMTQ4MzUtMzU3MAcAAAAuUy0xLTUtMjEtMjA1NzQ5
MTAzMi0zMTg0MDY0OTc4LTE1NDYxMTQ4MzUtNDEyMgcAAAAuUy0xLTUtMjEtMjA1NzQ5MTAzMi0zMTg0MDY0OTc4LTE1NDYxMT
Q4MzUtMTE2NAcAAAAuUy0xLTUtMjEtMjA1NzQ5MTAzMi0zMTg0MDY0OTc4LTE1NDYxMTQ4MzUtMTE0MQcAAAAuUy0xLTUtMjEt
MjA1NzQ5MTAzMi0zMTg0MDY0OTc4LTE1NDYxMTQ4MzUtNDE1MwcAAAAuUy0xLTUtMjEtMjA1NzQ5MTAzMi0zMTg0MDY0OTc4LT
E1NDYxMTQ4MzUtNDE0NQcAAAAtUy0xLTUtMjEtMjA1NzQ5MTAzMi0zMTg0MDY0OTc4LTE1NDYxMTQ4MzUtNTE4BwAAAC5TLTEt
NS0yMS0yMDU3NDkxMDMyLTMxODQwNjQ5NzgtMTU0NjEx
StateAttribute14 :
StateAttribute15 :
StateAttribute16 : 0
StateAttribute17 : 0
StateAttribute18 : 0
StateAttribute19 : 0
StateAttribute20 : 0
StateAttribute21 : /o=companyname/ou=first administrative group/cn=Recipients/cn=NathanH
StateAttribute22 : EMSMDB.Connect()
StateAttribute23 : https://pw-sc-01.companyname.local:444/rpc/rpcproxy.dll?PW-SC-01.companyname.local:6001
StateAttribute24 : Negotiate
StateAttribute25 : [33]10/11/2014 13:50:03 [FAILED!] EMSMDB.Connect();
Identity : fcd6159dd8fe42aebf10100cc4934356
IsValid : True
ObjectState : New

How to enable the SharePoint 2010 and 2013 Developer Dashboard for specific WebApplication or Sitecollection?

How to enable the SharePoint 2010 and 2013 Developer Dashboard for specific Web Application or Site collection(not for all Web Application)?
Vishal Goyal

Hi Vishal,
I don't think there is option for specific site collection or web application,but there is option of enabling developer dashboard on specific master pages and that is one on of the way you could do it.
look article on below link to enable developer dashboard on specific master pages
https://msdn.microsoft.com/en-us/library/office/ff512745%28v=office.14%29.aspx?f=255&MSPPError=-2147217396
Let me know if this helps.
Thanks
Bhism

Lync 2010 and 2013 coexistence - DNS

Similar Messages

Maybe you are looking for