OCS Migration to Lync 2013 Delegate which Director that authenticates

Hello - I am in the middle of a migration from OCS 07 to Lync 2013. Everything is working pretty well. I have a new Lync Server with some users migrated over to it already and communication is fine between the Lync Desktop Clients and the OCS Desktop Clients.
We now want to use the Mobile Lync Client so I have installed Lync 2013 Client on my iPhone 5S. I was able to install the root cert on the phone however, when I try to sign in, I am getting the following error:
"We can't sign you in because your organization doesn't support this version of Lync. Please install Lync 2010 from your mobile store."
I am running Lync 2013 Standard Edition and I am running Lync 2013 Client for iOS. I can only assume that because the OCS director is still running it is handling authentication and its not compatible with Lync 2013. Is this a correct assumption?
That being said, and if that's indeed the issue, is there a way to delegate the Lync 2013 Director to take over authentication?
Thank you!
Russ, MCSE

Hi there,
Lync 2013 Mobile clients relies on UCWA services to connect to Lync server 2013 services, also Lync mobile autodiscovery depends on Lync web services publishing. Therefore you should make sure that lyncdiscover.sipdomain and lyncdiscoverinternal.sipdomain
points to Lync server 2013 web services and not OCS 2007.
specifically Lyncdiscover.sipdomain should point to the public IP address on which the Lync External WebServices are published.
so it is quite sure that if the above requirements are not met and especially the DNS configuration for Lyncdiscover and lyncdiscoverinternal mobile clients will not be able to connect.
Regards,
Charbel Hanna
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread

Similar Messages

Error during the migration of Lync 2013 onpremise user to Office 365 Lync

Hi,
I am trying to migrate a Lync 2013 onpremise user to Office 365 Lync in a Hybrid environment.
I am connecting to the Lync server from my machine with the following commands
$lyncOptions = New-PSSessionOption -SkipRevocationCheck -SkipCACheck -SkipCNCheck
$lync = New-PSSession -ConnectionUri https://lyncserver/ocspowershell -SessionOption $lyncOptions -Authentication NegotiateWithImplicitCredential
Import-PSSession $lync
In the next step I am trying to migrate the user to the Office 365 Lync:
Move-CsUser -Identity "username" -Target 'sipfed.online.lync.com' -HostedMigrationOverrideUrl 'https://admin1e.online.lync.com/HostedMigration/hostedmigrationservice.svc'
After that I get a warning message due to to migration to a previous version which I accept.
WARNING: Moving a user from the current version to an earlier version (or to a service version) can cause data loss.
Confirm
Move-CsUser
[Y] Yes [A] Yes to All [N] No [L] No to All [?] Help (default is "Y"): y
Then I am getting the following error message:
Can not load Live Id module. Make sure correct version of Live Id Sign-in assistant is installed.
    + CategoryInfo          : NotSpecified: (:) [Move-CsUser], CommonAuthException
    + FullyQualifiedErrorId : Microsoft.Rtc.Admin.Authentication.CommonAuthException,Microsoft.Rtc.Management.AD.Cmdle
   ts.MoveOcsUserCmdlet
    + PSComputerName        : lyncserver
Tried to Google it but found nothing.
As far as I can see it is complaining about the Live ID Sign-in assistant, which is installed (the 64bit version) on my computer but not on the remote server. Does it need to be installed on the server as well?
Thanks for the answers in advance.
Regards,
Akos
Akos_DB

This error related to reporting services, you need to verify that reporting services is installed on these instances.
Secondly, you didn't need to create this instance manually then setup monitoring role. delete this instance from shared storage and try again to setup rule using different instance name and it will create automatic on shared storage.
You can also refer below link
http://windowspbx.blogspot.com/2012/07/aaa-donotpost-install-lync-standard.html
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"

Migration to Lync 2013 from OCS 2007 R2 - queries

We are currently running OCS 2007 R2 across Citrix Presentation server 4.5 and Desktops using just IM functionality. We are looking to upgrade to LYNC 2013 for IM and to start using Group Chat. We currently have a Physical OCS front end server,
a physical server running SQL for the DB's and then a physical server running the Archive OCS component.
How easy is this to do? Would we keep the same Pool name?
Can the OCS client be used to connect to Lync 2013?
Can we move the physical servers into VM's? Do we need 3 or can we have all on one VM now?
The SQL DB part can this now be hosted on a stand alone SQL cluster in its own instance if required?
LYNC IM and Group Chat client - is it supported to run on Citrix Presentation server 6.5?
Is a Schema Update required?
Are there any good walk throughs on the internet just covering IM and Group chat migrations etc as from what I have been seeing there are some out there but have voice in them as well.
Thanks.

In addition, the presence and IM features in Office Communicator 2007 R2 are compatible with Lync Server 2013, but conferencing features are not. During migration from Office Communications Server 2007 R2, Office
Communicator 2007 R2 is suitable for presence and IM interoperability, but users should use Lync Web App 2013 to join Lync Server 2013 meetings.
Q: Is it supported to run on Citrix Presentation server 6.5?
A: check the official document at http://support.citrix.com/article/CTX138408
Is a Schema Update required?
Yes, schema update is required. See
http://technet.microsoft.com/en-us/library/jj205265.aspx
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.
Lisa Zheng
TechNet Community Support

Migrating to Lync 2013 from OCS 2007 R2 ... to unprep or not to unprep

I've been reading on TechNet that I should unprep the domain and forest after decommissioning / uninstalling all OCS 2007 R2 server roles:
http://technet.microsoft.com/en-us/library/dd572243(v=office.13).aspx
...but then, in other places (such as blogs and TechNet forums), I've read not to unprep the domain and forest if Lync 2013 is already deployed:
http://social.technet.microsoft.com/Forums/lync/en-US/6b8cd7ca-fe67-418b-ae66-5be682d8d2d6/unprep-ocs-2007-r2-domain-and-forest-with-existing-lync-installation?forum=ocsplanningdeployment
http://www.ucprofessional.com/2011/04/decommisioning-ocs-2007-r2-after.html
Would someone please clarify what to do here and why?

While I haven't personally done a deep dive on everything it does, my understanding is that's it's more than just a simple mod to the system container. For example, from the OCS decommission article you referenced: "Running
Unprep for a domain removes the access control entries (ACEs) granted to Active Directory universal groups". Lync still uses the same RTCUniversal groups, so touching it at all with Lync in production as well could be bad.
Forest prep actually creates these groups:
http://technet.microsoft.com/en-us/library/dd441353(v=office.13).aspx That said, I haven't seen an unprep referenced in the migration from OCS to Lync docs, and the doc you referenced is specifically for completely removing OCS from your environment
where these groups wouldn't be needed. So, while I can't tell you exactly what all it does, I really wouldn't mess with it unless you have a strong reason to or are willing to rebuild Lync to get a few old objects out of the system container.
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

OCS 2007 to Lync 2013 migration approach & steps

Hi,
I am looking for migration approach from OCS 2007 (not OCS 2007 r2) to Lync 2013 for 4000 users. as per the MS technet its not supported. has anyone tried and tested if yes please provide the steps and risk involved. thanks

Hi Nmits,
Since it is not supported to migration from OCS 2007 to Lync server 2013 directly, you have two ways to complete the migration process:
Migration from OCS 2007 to OCS 2007 R2 first, then migration from OCS 2007 R2 to Lync server 2013.
Migration from OCS 2007 to Lync server 2010 first, then migration from Lync server 2010 to Lync server 2013.
Migration from OCS 2007 to OCS 2007 R2:
http://technet.microsoft.com/en-us/library/dd572505(v=office.13).aspx
Migration from OCS 2007 to Lync server 2010:
http://www.microsoft.com/en-in/download/details.aspx?id=7327
http://blogs.technet.com/b/nexthop/archive/2011/05/23/migrating-from-office-communications-server-2007-to-lync-server-2010.aspx
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

Unable to connect as a formal agent to a Response Group after Migration to Lync 2013

We are in the process of migrating our Lync 2010 servers to Lync 2013. Everything seems to go well, but problems started to appear after we migrated the Lync 2010 response groups to Lync 2013. Now only those groups with informal agents work. All the groups
with formal agent, when they try select their group through the web page, they all get the error:
You are not a member of any group. For assistance, contact your support team"
Did anyone experience such an issue ?
Thanks,
Antonio

We had this problem with our recent migration of c. 350 response groups, many of which had formal agent groups. The cause appears to be that after the migration, the formal agent registration screen sees both the 'old' and the 'new' formal agent groups of
which the current user is a member and resolves these to only one entry on the registration screen (which is understandable). But the entry seems to be connected to the 'old' and not the 'new' agent group. We were able to verify this by checking in the old
and new pool database (rgsdyn) and seeing that even after the migration the formal agents were signing in to the old pool and not the new one. One solution is to delete the members from the old formal agent groups so that future registrations are forced to
take place in the new pool database. However, if you do this, bear in mind that if you have to back out the migration, you have to restore these.
We were also had to abandon one migration attempt because of another problem where the migration tool does not support the migration of agents who are defined indirectly in the agent group through a mail distribution group.
tags: Move-CsRgsConfiguration ; formal agent groups ; lync2013 ;

Migrated to Lync 2013 now need federation assistance

I have migrated from a Lync 2010 environment to a Lync 2013 environment for the Front End Servers. I am now needing to be able to Federate with several other external companies. I am a somewhat intelligent person however, this piece has me perplexed.
internal domain - domain.local
external domain - domain.com
internal front end server - server00.domain.local
edge server - server11.domain.local (in a workgroup in DMZ)
email domain - domain-company.com
SIP addresses - [email protected]
I have a DMZ that has an internal and external Checkpoint Firewall, we have blown so many holes through it the Security Expert here is afraid, however, Testconnectivity.microsoft.com succeeds as long as I do not choose A/V tests.
I want to have Directed federation with other entities within our company and have done nslookup's, used Lync IP Tools, and multiple other tests to find out where I am failing to understand why I cannot get Federation to work.
Any thoughts?
I absolutely deplore certificates....

When you say you want to federate with other entities within your company, are they separate forest/domains? How do you connect to them, over the Internet or via a direct path? Or do I misunderstand? Is your intention to also federate with
entities external to your company?
Your sip domain really should match your email domain, just to make it easier to locate your users from outside. On top of this, you'll be able to get a third party certificate (they won't typically issue one for .local) which will be valuable for
Lync mobility and federation without having the others install your self signed cert.
Are the certificates currently deployed on the edge self signed or third party?
How many SIP domains do you have deployed?
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 2013 - Delegates are all of a sudden showing up in contacts list

All of a sudden, folks are seeing Delegates displaying in their Lync 2013 contacts list.
We never had enterprise voice enabled in our environment. Recently, I ran Windows updates on the 2012 R2 DC's.
Suggestions?
Should I set "EnableDelegation" to False so that folks won't see any Delegates in their contacts list?
Thanks
Ron

Hi Ron,
Based on my understanding, Lync syncs the information from Outlook.
You can try running the following command to disable synchronization.
Set-CsclientPolicy –EnableExchangeDelegateSync $false
Hope it can be helpful.
Best regards,
Eric

Migration to Lync 2013 - Unable to remove 2010 Edge Server

Hi
We did a migration from Lync 2010 to Lync 2013. Everything worked without any problems. But now we are unable to remove the Lync 2010 Edge Pool. Everything has been done according to
https://technet.microsoft.com/en-us/library/jj205369.aspx “Migration from Lync Server 2010 to Lync Server 2013”.
I am able to remove the 2010 Edge pool, but by trying to publish the topology, I receive the following error: “Error: An error occurred: "System.InvalidOperationException" "Cannot publish topology changes. Call orbit still
exists on one or more deleted application servers."
How can I resolve this error?
Regards
Peter

Hi Peter,
You have to change the Call Park Destination FQDN to the Lync 2013 Pool.
Please check out the following article.
Migrate Call Park application settings
Best regards,
Eric
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]

Migration to lync 2013 select central management store - what name should be there?

hello
trying to migration from lync 2010 to lync 2013. populated the topogoly builder and was going to publish.
the name in select central management store has the name of the lync 2010 environment, but if I hit next it has my new sql server.
should the new lync 2013 CMS be listed there?

Did you move the Central Management Store via the Powershell yet? If not, check this article:
http://technet.microsoft.com/en-us/library/jj688013.aspx
If you have moved it, you're most likely seeing an old topology, download it again before making changes and publishing. If you download again and still see the old server even though it's moved, I'd re-run through the steps in the article again.
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

How to remove OCS and install lync 2013 on MS Office 2007 and 2010

Hi,
We need to install lync 2013 on our systems having office 2007 and 2010 via SCCM 2012.
Please suggest.
Regards, Syed Fahad Ali

Lync 2013 no longer has its own installer, but instead uses the Office installer. You can create a customized installation and deploy it just like you do with Office:
http://technet.microsoft.com/en-us/library/jj204827.aspx
I hope that helps,
Nash
Nash Pherson, Senior Systems Consultant
Now Micro -
My Blog Posts
If you've found a bug or want the product worked differently,
share your feedback.
<-- If this post was helpful, please click "Vote as Helpful".

OCS 2007 R2 migration to Lync 2013

Anyone has a good migration guide for this project?
Thank you. Eric.

There's the TechNet guide:
http://technet.microsoft.com/en-us/library/jj205375.aspx :)
Oğuzhan ilkan Boran has a YouTube video as well, he often walks through the TechNet articles with a bit of a value-add which can be helpful.
https://www.youtube.com/watch?v=QoxZ-MDoZaA
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 2013 client is deployed but user accounts are not migrated from OCS to Lync 2013 Server - how to open Lync meetings automatically in the Lync Web Plug-in

We have in our enterprise the following scenario:
1 - Lync 2013 client is installed
2 - User accounts are not migrated to Lync 2013 Server, users are using Office Communicator as their main tool
3 - Users receive Lync 2013 meeting requests but when try to access them, Lync 2013 client launches and shows error. Users will need to open the browser and paste the URL to the address bar but this still open
4 - We cannot use the workaround of adding "?SL=1" to the Lync 2013 meeting URL as the user base is large and manual workaround is not accepted
5 - Question: is there any automated way, via egistry key or GPO setting, so that users temporarily (until their accounts are migrated to Lync 2013 server) can bypass Lync 2013 client completely and automatically open all Lync 2013 meetings
on the browser, using Lync Web Plug-in?

Thanks for the response,
First, I should have mentioned clearly that users have Office Communicator 2007 client and Lync 2013 client installed in their machines. Their accounts are not migrated yet to Lync 2013 server.
Second, we are using IE9 and IE10. The issue is that users CAN join Lync 2013 meetings with their browsers but have to paste the URL manually to browser and add "?SL=1" otherwise, if they just click at the "Join Online Meeting" or "Join
Lync Meeting" URL it launches Lync 2013 client which shows error because is not configured yet, as they are using OCS client and migrating slowly to Lync 2013 server.
Is there a Group Policy setting or a registry key from Microsoft that can be turned on to these users machines and make will all Lync meeting requests to be opened in IE browser instead of Lync 2013 client. We need a way to ignore
Lync 2013 client until user accounts are migrated to Lync 2013 Server. Manually typing URLs is not an option in a big organization, can't explain thousands of users of different levels what to do.
We are regretting the decision not to separate Lync 2013 from Office 2013 package we deployed recently. If Lync 2013 is uninstalled then all Lync meeting requests are opened in browser without an issue.

Mixed environment migration (OCS\Lync 2010 to Lync 2013) retaining BES Integration

Hi All,
I have an existing OCS 2007R2 and Lync 2010 environment which contains BES Collaboration for Enterprise IM on Blackberry devices. I want to migrate this environment to Lync 2013 whilst retaining the BES integration. Understanding that tri-existence is not supported
I've been going through the process of decommissioning all of my legacy OCS servers, which I have now completed, in readiness for starting the Lync 2013 deployment and prepping AD.
Here's my issue - The BES collaboration service was integrating with an old OCS CWA server. I removed the CWA server and migrated the Collaboration service to a new server so that I could configure it to directly communicate directly with the Lync 2010 pool,
however I still needed to install OCS components on the new server in order to achieve that integration. Now I've run the final step of Merging the OCS 2007R2 Topology with the Lync 2010 topology in preparation for deleting the BackCompatSite, the old OCS
servers have gone, but the new Collaboration server has now appeared as a trusted application server within the BackCompatSite. I've done an LDIFDE export of the RTC Service container and have had a look through the contents. I can see that the new BES Collaboration
server is there and that it has an msRTCSIP-TrustedServerVersion value of 4, whereas all the Lync 2010 values are 5, which I'm guessing is what the Lync Topology is using to establish that the BackCompatSite needs to be populated with that Trusted Server entry.
So my question is this - What do I need to do in order to successfully remove the BackCompatSite entry and migrate my environment to Lync 2013 whilst retaining integration with BES and keeping the Enterprise IM service service running on Blackberry devices?
Here's some options that I've thought about - Using ADSIEdit to remove the Trusted Server Application for the new BES Collaboration server so I can merge the Topology and delete the BackCompatSite, although will this break the Enterprise IM service? Temporarily
changing the value of the msRTCSIP-TrustedServerVersion for the Collaboration server from 4 to 5, merging the Topology, deleting the BackCompatSite and then changing the msRTCSIP-TrustedServerVersion back to 4 afterwards? Over a weekend\out of hours, removing
the BES Collaboration server and service altogether, going through the Topology merge\BackCompatSite deletion and then reinstalling the Collaboration service?
Has anyone else gone through this process, or got any advice\experience to pass on before I start working through my list of options?

I've asked this question several times:
Does the 2007 R2 CWA server count as tri-coexistence?
I've asked that both in MCM rotations and directly of people on the PG and the answer is always something along the lines of "nope, it's a trusted app server and not a pool". When I've run into this issue in other deployments, we simply left the backcompatsite
in the deployment into production.
I've never found the above as a publically approved statement just something I've asked previously and been told is OK to do. This is one of those situations that will work but was most likely not tested.
Thanks,
Richard
Richard Brynteson, Lync MVP | http://masteringlync.com | http://lyncvalidator.com

Lync 2010 to Lync 2013 Trusted application Migration

We have Mitel Live Business Gateway as trusted application server on the Lync 2010 server for Remote call control. I am in the process of migrating to Lync 2013 and can't find
a way to migrate the Trusted Application. This is how we setup the Trusted application on Lync 2010.
http://www.justin-morris.net/configuring-lync-server-2010-for-remote-call-control-with-mitel-3300/
Malli Boppe MCITP Enterprise Messaging Exchange 2010

Hi,
You cannot move it to Lync Server 2013. You need to create new trusted application server and select Lync Server 2013 front end pool as the next hop.
Configure Trusted Application Servers
http://technet.microsoft.com/en-us/library/jj204735.aspx
Kent Huang
TechNet Community Support

OCS Migration to Lync 2013 Delegate which Director that authenticates

Similar Messages

Maybe you are looking for