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

Similar Messages

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

Lync 2010 to 2013 Migration (Standard) - Can't Move CMS

New virtual machine has Lync 2013 Standard installed. I've selected "Prepare first Standard Edition server" and launched the Lync Powershell, entered enable-cstopology, then move-csmanagementserver. It fails with the error "The New CMS located
at X.domain.com\rtc" is not accessible. -FullyQualifiedErrorId: Move not supported.,Microsoft.Rtc.Management.Deployment.MoveCms.Movecmscmdlet".
I've seen several commands to try while Googling, but unsure of which one to try:
Install-CsDatabase -CentralManagementDatabase -SqlServerFqdn t-sql03.wesselius.local –SqlInstance –clean
Install-CsDatabase -CentralManagementDatabase -sqlserverfqdn server.fqdn.local -sqlinstancename rtc -clean
Install-CsDatabase -CentralManagementDatabase -SqlServerFqdn sql.domain.local -SqlInstanceName INSTANCE -clean
If I download my current topology, expand Shared Components and then SQL Server Stores I see:
-servername.domain.com\rtc (lync 2010 FE server)
-servername2013.domain.com\rtc (lync 2013 FE server)

On the Lync 2013 vm I've been through all of the "prepare ad" steps, all of the "install or update lync server system" steps, "prepare first SE server", etc. So if I download my current topology, you can see my 2013 lync server
if you expand down to Lync server - OrgName - Lync Server 2013 - Standard Edition FE Servers.
All services are started.
I cannot move users to the pool due to what I have mentioned above. My CMS is still 2010/located on my 2010 server which is coexisting until the migration is complete. You cannot migrate a user to the 2013 pool from the 2010 CMS console.
I am running the command on the 2013 server.
Edit: I guess this link would show about where I am: http://technet.microsoft.com/en-us/library/jj205420.aspx
The difference is my 2013 CMS link doesn't work, I just get a "403 - Forbidden. Access is denied" error. If I launch my 2010 CMS link and go to the topology tab, I can see my 2013 lync server and the replication status is good.

Exchange 2010 to 2013 Migration: Authentication/Proxy Settings Issue

I'm in the final stages of preparing for our Exchange 2010 to 2013 migration. I'm noticing minor authentication issues on mobile devices (android & ios) and proxy setting issues with Outlook that require user intervention. In an effort to make the migration
as smooth as possible for our internal users, I'd like to get these settings ironed out before starting the migration.
Symptoms:
Outlook - I'm aware that internal Outlook usage has changed its connection protocol from RCP/TCP to RCP/HTTP, but it appears that Outlook isn't updating its settings in the "Microsoft Exchange Proxy Settings" after a users mailbox has been migrated
from 2010 to 2013. Currently, 2010 users with Outlook 2013 have the following settings configured in Outlook's Exchange Proxy Settings:
URL to connect to my proxy server for Exchange: webmail.domain.com
Connect using SSL only: Checked
Only connect to proxy servers that have this principal name in their certificates: Unchecked
On fast networks, connect using HTTP first, then connect using TCP/IP: Unchecked
On slow networks, connect using HTTP first, then connect using TCP/IP: Checked
After migrating a user's mailbox from 2010 to 2013, the above settings remain the same in Outlook and their client disconnects from Exchange and isn't able to reconnect. After manually enabling the checkbox for "On fast networks, connect using HTTP
first, then connect using TCP/IP", Outlook clients are able to connect to Exchange via their newly migrated mailbox.
Is there a way to automatically updating these 2 proxy settings in Outlook during the migration instead of having to manually change each user's configuration in Outlook?
Android & iOS - Currently, users on Android & iOS with Exchange 2010 mailboxes have the following configuration:
domain: blank
username: their AD username
server: webmail.domain.com
After migrating a mobile users mailbox from 2010 to 2013, neither OS (Android or iOS) is able to connect due to an authentication failure. On iOS, if I manually change the domain from blank to my company's domain, authentication succeeds and their 2013 mailbox
begins to update. On Android, the option to change the domain name from null is grayed out, requiring the user to delete the Exchange profile and re-add it with the domain name intact. Is there a way to configure Exchange 2013 to not require the domain name
for mobile users in the same way that it's been working for us with Exchange 2010?
Please let me know if you require cmdlet print outs of my virtual directories to help troubleshoot the issue.

Hi,
Generally, when the user mailbox is moved from Exchange 2010 to Exchange 2013, the Autodiscover service would detect the changes and update the new configuration automatically.
Please make sure the autodiscover service in your new Exchange 2013 is configured correctly. We can create a new mailbox in Exchange 2013 and check whether the new Exchange 2013 user can setup account successfully in Outlook or not. If the new user works
fine, it indicates the autodiscover service in Exchange 2013 should be proper for internal user.
Please restart the following Exchange service to have a try:
Microsoft Exchange RPC Client Access
Microsoft Exchange Mailbox Replication
Restart IIS service by running IISReset in a Command Prompt window.
Then check whether the Outlook client can connect to Exchange 2013 or not.
As for Android & iOS issue, I suggest we can ask a question in ActiveSync forum for more suggestion:
https://social.technet.microsoft.com/Forums/en-US/home?forum=exchangesvrmobility
Regards,
Winnie Liang
TechNet Community Support

Need clarification on DNS, Certificate and URL? during 2010 to 2013 migration

Hi Guys,
I am working on a migration project Lync server 2010 to 2013.
Lync 2010 Standard Edition and Edge
Lync 2013 Ent edition and Edge (Enterprise Voice "SIP Trunk")
I need few clarification on How to setup the DNS, Certificate and URL Pre and post migration?
Shall we use the Lync 2010 existing internal and external URLs to lync 2013 or do we need to setup a new URLs for lync 2013?
How about the DNS records and Certificates?
I have gone trough the below blogs but need clear understanding on this part..
http://lyncdude.com/2013/08/11/understanding-lync-dns-records-and-autoconfiguration/
https://technet.microsoft.com/en-us/library/hh690044.aspx
and few more....
Thanks,
Balakrishna G
Regards, Balgates

Hi,
Agree with Thamara.Wijesinghe.
You need to different Web service URL for Lync Server 2010 and Lync Server 2013. If you only have Web service URL for Lync Server 2010, then Lync 2013 mobile will fail to connect to FE Server. If you point Web service URL point to Lync Server 2013 Pool,
then both Lync 2010 and 2013 mobile clients will connect to FE Server successfully.
Best Regards,
Eason Huang
Eason Huang
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

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.

Questions on Lync 2010 to 2013 Addressbook Migration

Hi Team,
We are in the process of migrating the users from Lync 2010 to Lync 2013 pilot pool.
https://technet.microsoft.com/en-us/library/jj205160.aspx
According to the above article, basically the Lync Server 2010 Address Book is migrated along with the rest of your topology and don’t have to worry about the post migration steps if we don’t have customized settings such as GAL partition (By setting
up an attribute ‘msRTCSIP-GroupingID’), customized AB normalization rules and customized phone normalization rules.
Questions:
1. How do we confirm that there is no customized settings of phone normalization, AB normalization and GAL partition in the existing Lync 2010 environment?
2. Is there any powershell command to validate the current Lync 2010 settings?
Please advise.
Many Thanks.

The grouping ID is not something you'd normally put in. If all users can search for and see all other users, you'd be fine.
For the AB normalization look for Company_Phone_Number_Normalization_Rules.txt in your Lync file share in
X-WebServices-X\ABFiles (replace the X with whatever you see). If you have one, you could copy it over to your new Lync 2013 file share. This file is for normalizing phone numbers found in AD. To validate current settings, you can run
the BPA http://www.microsoft.com/en-us/download/details.aspx?id=4750 but if you're moving away from it, I wouldn't kill myself resolving issues. From PowerShell, there
are many things you could validate, is there something specific you're worried about?
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.

Infopath forms 2010 to 2013 migration issue

I need to migrate InfoPath forms 2010 to SP 2013. Now in 2010 InfoPath forms are connected to data connection library & having classic authentication. Since SP 2013 doesn't support classic authentication what are the issues should come to handle? What
should be correct strategy & steps for this migration?

Hi Sunil
Sharepoint 2013 will support the Classic mode authintication but while creating any new webapplication using sharepoint central administration you can only used claim based authintication
Check the below link for step by step approcah about infopath
http://technet.microsoft.com/en-in/library/cc262263(v=office.14).aspx
You can alos check this link
Claims-based authentication is an essential component to enable the advanced functionality of SharePoint 2013. To move classic-mode web applications from SharePoint 2010 Products to SharePoint 2013, you can convert them to claims-based web applications within
SharePoint 2010 Products, and then migrate them to SharePoint 2013. The procedures in this article illustrate various supported scenarios.
The Windows PowerShell Convert-SPWebApplication cmdlet in SharePoint 2013 converts classic-mode web applications to claims-based web applications.
http://technet.microsoft.com/en-us/library/gg251985(v=office.15).aspx
http://blogs.technet.com/b/rajbugga/archive/2013/08/07/infopath-over-claims-authentication-sharepoint-2010-amp-2013.aspx
Please mark the Answer and Vote me if you think that it will you to resolved your issue
did you missed to give any link here:
"You can alos check this link" ?
Also, Can you plz tell how to manage data connections in case of infopath migration?
Your answer is overall good.

Project Pro 2013 client Deployment with Lync 2010 and Team Explorer Excel Issues Following

Current machines are Office 2010 SP1 or SP2 32-bit
Just deployed Project 2013 Pro and Std to the existing machines that had Project 2010 Pro or Std. We selected the full install since people use integration into different tools.
Results:
lync 2010 64-bit when attending a meeting prompted user to start using and download the Lync Web Component, which breaks features such as muting, etc.
A repair sent to the workstations for Lync 2010 64-bit fixed that.
Team Explorer 2012 Export to excel from queries gives error Unable to cast COM object of type 'Microsoft.Office.Interop.Excel.ApplicationClass' to interface type 'Microsoft.Office.Interop.Excel._Application'. This operation failed because
the QueryInterface call on the COM component for the interface with IID '{000208D5-0000-0000-C000-000000000046}' failed due to the following error: The interface is unknown. (Exception from HRESULT: 0x800706B5).
Repair of Team Explorer, Office, Test Manager 2012, etc did not assist. if we go into excel and connect to TFS, we can then retrieve the query data. Just not from TFS exporting to excel. Had to unload Project 2013, repair Office 2010
and rebooted with project off the machine and now it works. It seems maybe the setup with the shared features and Office tools are breaking something? We need the ability for VBA and .net functionality, but what could be breaking this?

Hi,
Your environment will support 32 bit of Project professional 2013 (x86) as you have Windows and Office of (X86).
You try to modify registry then you wont face issue.
The issue when you hit a "1653" is that Windows
Installer "DisableRollback" is set. Office 2013 requires that "rollback" be enabled. If you are getting a "1653"
error in your logs as Ken did then the solution is to delete the "DisableRollback" (or set to '0') at the following registry keys:
HKEY_CURRENT_USER\Software\Policies\Microsoft\Windows\Installer
HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer
these are the issues I've seen:
Scheduler service was stopped. At a cmd window typing "net start schedule" resolves the problem.
CMD.exe was customized via the following registry key. Solution was to temporarily disable the customization by changing autorun value to autorun_old.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Command Processor
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Command Processor
Permission issues - seems some custom permissions affected Ingram's install which he explained in his previous post.
Environment variable "ComSpec" had been modified (semicolon added). Fix was to remove the added semicolon (there should be no semicolon).
The way to identify you are hitting this specific issue is if in the %temp%\OfficeSetup.log there is a mention of "Office64MUI.msi" failing to install with return value of 1603
If you want to enable verbose logging via the following key, rerun your failed install, and collect all the setup and MSI* logs that will give more information.
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer]
"logging"= "voicewarmup"
kirtesh

Issue sending bulk email after Exchange 2010 to 2013 migration

Hi!
I have an issue with some reporting software sending bulk emails after our Exchange 2013 migration.
I can see the connections in the firewall and I can see the first connections under the protocol logs in the Exchange servers. What happens is that after ~10 emails, within the same amount of seconds from what I can tell, the mail flow just stops to the
Exchange server. I cant seem to find an error message anywhere within the Exchange logs and I've tried updating the receive connector with higher timeouts / Connection limits but the users still cant send all the invoices etc right away.
We have multiple applications / receive connectors with this issue and the users did not report any issues with Exchange 2010 so I am assuming that this issue did not exist there.
We're running two multi-role (CAS/MB) Exchange 2013 servers in a DAG. Exchange 2010 is not fully decommissioned yet but all links and users are moved to 2013.
Any help is much appreciated!

Hi ,
To avoid the issues when relaying the emails from application server through exchange then we need concentrate on the below mentioned parameters on the receive connectors in exchange 2013 cas servers and also we need to set the parameter value as per your
environment requirement.
Please check the below mentioned values on the dedicated receive connectors in exchange 2013 cas server to relay emails from the application server
Parameters :
ConnectionInactivityTimeout
ConnectionTimeout
MaxInboundConnection
MaxInboundConnectionPercentagePerSource
MaxInboundConnectionPerSource
MaxRecipientsPerMessage
MessageRateLimit
Note : In case if none of the above changes help you then the final option would be to enable the protocol logging on the receive connector utilized by the application server to relay emails via exchange server and with the help of the logs we can can came
to know that why the connections from the application server to exchange server is disconnecting after some emails has send.
Thanks & Regards S.Nithyanandham
Here are the relevant values for the receive connector, doublechecked and it's the same on both DAG members;
ConnectionTimeout : 00:20:00
ConnectionInactivityTimeout : 00:05:00
MaxInboundConnection : 5000
MaxInboundConnectionPerSource : Unlimited
MaxInboundConnectionPercentagePerSource : 100
MaxRecipientsPerMessage : 200
MessageRateLimit
: Unlimited
Adding logs for one big connection spike from the customer. About 50 inbound connections to the Exchange servers .
SMTP Receive;
2015-01-26T18:02:46.991Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,0,DAG member 01:587,Customer IP:60262,+,,
2015-01-26T18:02:47.006Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,1,DAG member 01:587,Customer IP:60262,*,SMTPSubmit SMTPAcceptAnySender SMTPAcceptAuthoritativeDomainSender AcceptRoutingHeaders,Set Session Permissions
2015-01-26T18:02:47.006Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,2,DAG member 01:587,Customer IP:60262,>,"220 DAG member 01 Microsoft ESMTP MAIL Service ready at Mon, 26 Jan 2015 19:02:46 +0100",
2015-01-26T18:02:47.006Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,3,DAG member 01:587,Customer IP:60262,<,EHLO customerdomain.com,
2015-01-26T18:02:47.006Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,4,DAG member 01:587,Customer IP:60262,>,250-DAG member 01 Hello [Customer IP],
2015-01-26T18:02:47.006Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,5,DAG member 01:587,Customer IP:60262,>,250-SIZE 36700160,
2015-01-26T18:02:47.006Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,6,DAG member 01:587,Customer IP:60262,>,250-PIPELINING,
2015-01-26T18:02:47.006Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,7,DAG member 01:587,Customer IP:60262,>,250-DSN,
2015-01-26T18:02:47.006Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,8,DAG member 01:587,Customer IP:60262,>,250-ENHANCEDSTATUSCODES,
2015-01-26T18:02:47.006Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,9,DAG member 01:587,Customer IP:60262,>,250-STARTTLS,
2015-01-26T18:02:47.006Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,10,DAG member 01:587,Customer IP:60262,>,250-AUTH LOGIN,
2015-01-26T18:02:47.006Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,11,DAG member 01:587,Customer IP:60262,>,250-8BITMIME,
2015-01-26T18:02:47.006Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,12,DAG member 01:587,Customer IP:60262,>,250-BINARYMIME,
2015-01-26T18:02:47.006Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,13,DAG member 01:587,Customer IP:60262,>,250 CHUNKING,
2015-01-26T18:02:47.022Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,14,DAG member 01:587,Customer IP:60262,<,STARTTLS,
2015-01-26T18:02:47.022Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,15,DAG member 01:587,Customer IP:60262,>,220 2.0.0 SMTP server ready,
2015-01-26T18:02:47.022Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,16,DAG member 01:587,Customer IP:60262,*,,Sending certificate
2015-01-26T18:02:47.022Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,17,DAG member 01:587,Customer IP:60262,*,CN=server,Certificate subject
2015-01-26T18:02:47.022Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,18,DAG member 01:587,Customer IP:60262,*,CN=server,Certificate issuer name
2015-01-26T18:02:47.022Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,21,DAG member 01:587,Customer IP:60262,*,server;DAG member 01,Certificate alternate names
2015-01-26T18:02:47.053Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,22,DAG member 01:587,Customer IP:60262,*,,TLS negotiation succeeded
2015-01-26T18:02:47.069Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,23,DAG member 01:587,Customer IP:60262,<,EHLO customerdomain.com,
2015-01-26T18:02:47.069Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,24,DAG member 01:587,Customer IP:60262,*,,Client certificate chain validation status: 'EmptyCertificate'
2015-01-26T18:02:47.069Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,25,DAG member 01:587,Customer IP:60262,*,,TlsDomainCapabilities='None'; Status='NoRemoteCertificate'
2015-01-26T18:02:47.069Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,26,DAG member 01:587,Customer IP:60262,>,250-DAG member 01 Hello [Customer IP],
2015-01-26T18:02:47.069Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,27,DAG member 01:587,Customer IP:60262,>,250-SIZE 36700160,
2015-01-26T18:02:47.069Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,28,DAG member 01:587,Customer IP:60262,>,250-PIPELINING,
2015-01-26T18:02:47.069Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,29,DAG member 01:587,Customer IP:60262,>,250-DSN,
2015-01-26T18:02:47.069Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,30,DAG member 01:587,Customer IP:60262,>,250-ENHANCEDSTATUSCODES,
2015-01-26T18:02:47.069Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,31,DAG member 01:587,Customer IP:60262,>,250-AUTH LOGIN,
2015-01-26T18:02:47.069Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,32,DAG member 01:587,Customer IP:60262,>,250-8BITMIME,
2015-01-26T18:02:47.069Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,33,DAG member 01:587,Customer IP:60262,>,250-BINARYMIME,
2015-01-26T18:02:47.069Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,34,DAG member 01:587,Customer IP:60262,>,250 CHUNKING,
2015-01-26T18:02:47.085Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,35,DAG member 01:587,Customer IP:60262,<,AUTH LOGIN,
2015-01-26T18:02:47.085Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,36,DAG member 01:587,Customer IP:60262,>,334 <authentication response>,
2015-01-26T18:02:47.100Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,37,DAG member 01:587,Customer IP:60262,>,334 <authentication response>,
2015-01-26T18:02:47.131Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,38,DAG member 01:587,Customer IP:60262,*,SMTPSubmit SMTPAcceptAnyRecCustomer IPient BypassAntiSpam AcceptRoutingHeaders,Set Session Permissions
2015-01-26T18:02:47.147Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,39,DAG member 01:587,Customer IP:60262,*,[email protected],authenticated
2015-01-26T18:02:47.272Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,40,DAG member 01:587,Customer IP:60262,*,,Proxy session was successfully set up. Session [email protected] will now be proxied
2015-01-26T18:02:47.272Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,41,DAG member 01:587,Customer IP:60262,>,235 2.7.0 Authentication successful,
2015-01-26T18:02:47.819Z,RECEIVE CONNECTOR,08D2051B7AE3DA8E,42,DAG member 01:587,Customer IP:60262,-,,Local
SMTP Send
2015-01-26T18:02:47.163Z,Client Proxy Send Connector,08D2051B7AE3DA8F,0,,DAG member 02:465,*,,attempting to connect. Client proxy session for [email protected]
2015-01-26T18:02:47.163Z,Client Proxy Send Connector,08D2051B7AE3DA8F,1,DAG member 01:57446,DAG member 02:465,+,,
2015-01-26T18:02:47.163Z,Client Proxy Send Connector,08D2051B7AE3DA8F,2,DAG member 01:57446,DAG member 02:465,<,"220 DAG member 02 Microsoft ESMTP MAIL Service ready at Mon, 26 Jan 2015 19:02:46 +0100",
2015-01-26T18:02:47.163Z,Client Proxy Send Connector,08D2051B7AE3DA8F,3,DAG member 01:57446,DAG member 02:465,>,EHLO DAG member 01,
2015-01-26T18:02:47.163Z,Client Proxy Send Connector,08D2051B7AE3DA8F,4,DAG member 01:57446,DAG member 02:465,<,250-DAG member 02 Hello [DAG member 01],
2015-01-26T18:02:47.163Z,Client Proxy Send Connector,08D2051B7AE3DA8F,5,DAG member 01:57446,DAG member 02:465,<,250-SIZE 36700160,
2015-01-26T18:02:47.163Z,Client Proxy Send Connector,08D2051B7AE3DA8F,6,DAG member 01:57446,DAG member 02:465,<,250-PIPELINING,
2015-01-26T18:02:47.163Z,Client Proxy Send Connector,08D2051B7AE3DA8F,7,DAG member 01:57446,DAG member 02:465,<,250-DSN,
2015-01-26T18:02:47.163Z,Client Proxy Send Connector,08D2051B7AE3DA8F,8,DAG member 01:57446,DAG member 02:465,<,250-ENHANCEDSTATUSCODES,
2015-01-26T18:02:47.163Z,Client Proxy Send Connector,08D2051B7AE3DA8F,9,DAG member 01:57446,DAG member 02:465,<,250-STARTTLS,
2015-01-26T18:02:47.163Z,Client Proxy Send Connector,08D2051B7AE3DA8F,10,DAG member 01:57446,DAG member 02:465,<,250-X-ANONYMOUSTLS,
2015-01-26T18:02:47.163Z,Client Proxy Send Connector,08D2051B7AE3DA8F,11,DAG member 01:57446,DAG member 02:465,<,250-AUTH GSSAPI NTLM,
2015-01-26T18:02:47.163Z,Client Proxy Send Connector,08D2051B7AE3DA8F,12,DAG member 01:57446,DAG member 02:465,<,250-X-EXPS GSSAPI NTLM,
2015-01-26T18:02:47.163Z,Client Proxy Send Connector,08D2051B7AE3DA8F,13,DAG member 01:57446,DAG member 02:465,<,250-8BITMIME,
2015-01-26T18:02:47.163Z,Client Proxy Send Connector,08D2051B7AE3DA8F,14,DAG member 01:57446,DAG member 02:465,<,250-BINARYMIME,
2015-01-26T18:02:47.163Z,Client Proxy Send Connector,08D2051B7AE3DA8F,15,DAG member 01:57446,DAG member 02:465,<,250-CHUNKING,
2015-01-26T18:02:47.163Z,Client Proxy Send Connector,08D2051B7AE3DA8F,16,DAG member 01:57446,DAG member 02:465,<,250-XEXCH50,
2015-01-26T18:02:47.163Z,Client Proxy Send Connector,08D2051B7AE3DA8F,17,DAG member 01:57446,DAG member 02:465,<,250-XRDST,
2015-01-26T18:02:47.163Z,Client Proxy Send Connector,08D2051B7AE3DA8F,18,DAG member 01:57446,DAG member 02:465,<,250 XSHADOWREQUEST,
2015-01-26T18:02:47.163Z,Client Proxy Send Connector,08D2051B7AE3DA8F,19,DAG member 01:57446,DAG member 02:465,>,X-ANONYMOUSTLS,
2015-01-26T18:02:47.163Z,Client Proxy Send Connector,08D2051B7AE3DA8F,20,DAG member 01:57446,DAG member 02:465,<,220 2.0.0 SMTP server ready,
2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,21,DAG member 01:57446,DAG member 02:465,*,,Received certificate
2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,23,DAG member 01:57446,DAG member 02:465,*,,Proxy target certificate
2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,24,DAG member 01:57446,DAG member 02:465,*,"CN=*.email.com, OU=IT, O=X, L=X, S=X, C=SE",Certificate subject
2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,25,DAG member 01:57446,DAG member 02:465,*,"CN=DigiCert High Assurance CA-3, OU=www.digicert.com, O=DigiCert Inc, C=US",Certificate issuer name
2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,28,DAG member 01:57446,DAG member 02:465,*,*.email.com;email.com,Certificate alternate names
2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,29,DAG member 01:57446,DAG member 02:465,>,EHLO DAG member 01,
2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,30,DAG member 01:57446,DAG member 02:465,<,250-DAG member 02 Hello [DAG member 01],
2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,31,DAG member 01:57446,DAG member 02:465,<,250-SIZE 36700160,
2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,32,DAG member 01:57446,DAG member 02:465,<,250-PIPELINING,
2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,33,DAG member 01:57446,DAG member 02:465,<,250-DSN,
2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,34,DAG member 01:57446,DAG member 02:465,<,250-ENHANCEDSTATUSCODES,
2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,35,DAG member 01:57446,DAG member 02:465,<,250-AUTH GSSAPI NTLM LOGIN,
2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,36,DAG member 01:57446,DAG member 02:465,<,250-X-EXPS EXCHANGEAUTH GSSAPI NTLM,
2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,37,DAG member 01:57446,DAG member 02:465,<,250-X-EXCHANGEAUTH SHA256,
2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,38,DAG member 01:57446,DAG member 02:465,<,250-8BITMIME,
2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,39,DAG member 01:57446,DAG member 02:465,<,250-BINARYMIME,
2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,40,DAG member 01:57446,DAG member 02:465,<,250-CHUNKING,
2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,41,DAG member 01:57446,DAG member 02:465,<,250-XEXCH50,
2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,42,DAG member 01:57446,DAG member 02:465,<,250-XRDST,
2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,43,DAG member 01:57446,DAG member 02:465,<,250-XSHADOWREQUEST,
2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,44,DAG member 01:57446,DAG member 02:465,<,250-XPROXY,
2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,45,DAG member 01:57446,DAG member 02:465,<,250-XPROXYFROM,
2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,46,DAG member 01:57446,DAG member 02:465,<,250-X-MESSAGECONTEXT ADRC-2.1.0.0 EPROP-1.2.0.0,
2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,47,DAG member 01:57446,DAG member 02:465,<,250 XSYSPROBE,
2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,48,DAG member 01:57446,DAG member 02:465,>,X-EXPS EXCHANGEAUTH SHA256 ,
2015-01-26T18:02:47.257Z,Client Proxy Send Connector,08D2051B7AE3DA8F,49,DAG member 01:57446,DAG member 02:465,>,<Binary Data>,
2015-01-26T18:02:47.272Z,Client Proxy Send Connector,08D2051B7AE3DA8F,50,DAG member 01:57446,DAG member 02:465,<,235 <authentication information>,
2015-01-26T18:02:47.272Z,Client Proxy Send Connector,08D2051B7AE3DA8F,51,DAG member 01:57446,DAG member 02:465,>,XPROXY SID=08D2051B7AE3DA8E IP=Customer IP PORT=60262 DOMAIN=customerdomain.com CAPABILITIES=0
2015-01-26T18:02:47.272Z,Client Proxy Send Connector,08D2051B7AE3DA8F,52,DAG member 01:57446,DAG member 02:465,<,250 XProxy accepted and authenticated,
2015-01-26T18:02:47.272Z,Client Proxy Send Connector,08D2051B7AE3DA8F,53,DAG member 01:57446,DAG member 02:465,*,,Proxy session successfully set up for [email protected]. Inbound session will now be blindly proxied
2015-01-26T18:02:47.819Z,Client Proxy Send Connector,08D2051B7AE3DA8F,54,DAG member 01:57446,DAG member 02:465,-,,Remote
Nothing after these logs indicating any type of issue with the receive connector. Tried to make the logs as anonymous as possible. Hope they still make sense.
Note; Database was active on DAG member 02 but all incoming traffic on port 587 was directed to DAG member 01.

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.

LYNC 2010 : Steps to migrate from one pool to another pool

Hi,
We have LYNC 2010 deployed in 2 site (sit1 & Site2)
Currently all user host on Site1 pool. CMS exist in Site1
we have also mediation role and EDGE role on both site.
we have dial in conference on site1.
Currently public DNS record (for edge and as for reverse proxy) point to Site1.
Certificate Authority for site 1 and and site2 is different. However SAN entries and subject name is same for all certificate and bot CA are public CA.
We have to move all users to site2 pool and will also move CMS to site2 and we have to decommission site1.
What is the step by step process to move users, CMS, Edge server Traffic and Mediation server, reverse proxy?
Thanks
jitender

Hi,
The migration process from one pool to another pool is similar for from Lync Server 2010 to Lync Server 2013.
You can refer to the link below of “Migration from Lync Server 2010 to Lync Server 2013”
https://technet.microsoft.com/en-us/library/jj205369.aspx
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

Exchange 2010 to 2013 migration: Mailbox move requests are journaled.

Hello,
I've installed Exchange 2013 into Exchange 2010 infrastructure
[ single Exchange 2010 server; single AD site; AD = 2003 ],
Exchange 2010 has 2 databases:
1. Database with users mailboxes;    Journaling YES: Journal account.
2. Database with 1 mailbox for Journal user mentioned above:     Journaling NO.
Exchange 2013 has 1 database:
1. Database with moved users mailboxes;    Journaling YES: Journal account.
I saw that when I move mailbox from 2010 to 2013 then Journal Database INCREASES about size of MOVED MAILBOX !
I logged into Journal mailbox by OWA and didn't see any duplicate messages concerned with this mailbox user...
I'd like:
* to understand technically what happened,
* to avoid unnecessary growth of Journal Database.
I'd like not to switch off journaling for all users during mailbox move.
best regards Janusz Such

Hello Winnie,
your understanding is not correct:
I move mailboxes from first DATABASE which is journaled;
second database is dedicated solely for Journal user's mailbox and is not touched now.
Thank you for PS commands; I'll use them...
best regards Janusz Such
Hi Janusz,
Sorry for my delay. In your original posting, "I saw that when I move mailbox from 2010 to 2013 then Journal Database INCREASES about size of MOVED MAILBOX !"
My understanding is that when you move mailbox from Exchange 2010 Database 1 to Exchange 2013 database, the journal mailbox in Exchange 2010 Database 2 is incleased. Is it right?
Generally, the mailbox move would not be journaled unless there is any new email bening sent to the mailbox during the migration. Please run the commands in my original posting to check the statistics about it, and refer to Ed Crowdly's suggestion to use
Journal rule instead of database journal as a workaround.
Regards,
Winnie Liang
TechNet Community Support

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

Similar Messages

Maybe you are looking for