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

Similar Messages

Lync 2013 Edge Server Migration

Hi,
Our organisation is in the process of changing gateway providers, so we have to move our currently deployed Lync 2013 Edge Server and TMG (Lync related sites) to the new provider datacentre. We have new public and DMZ IP addresses allocated for these services
and we can't use the current addresses.
Has someone been through this and is there a best practice to follow to transition these services with minimal outages to the users?
Any help would be appreciated.

the steps that you mentioned would work. I need to add some bits in to it,
1. Take a copy of the current Edge Server (VM) and place into the new datacentre
2. changed the IP addressing (of services) for the Edge Pool in the Topology builder and publish/sync
3. Change the IP address of the edge server and run the deployment wizard with "Add remove Lync server component step"
3. Start services
4. Publish the Lync services on the new TMG reverse proxy
5. Test connectivity
http://thamaraw.com

I am not able login in Lync 2013 android application in my mobile

Dear team ,
I Have a lync account ,still i am using in my orginization ,but i am not able to login in my android mobile, I am system administrator in my orginization ,i gave all server names and Domain and my user name,but still i am unable to login,its showing Cannot
sign in.please verify sign-in adress and try again ,not only for me ,all are facing this problem ,we are downloading third party software and we are using
Please suggest me ASAP

If you are talking about sending photos via messaging then:
Have you turned on MMS Messaging in Settings?
See Settings > Messages > MMS Messaging and turn this ON.

Lync 2013 x64 silent client deployment via SCCM 2012 SP1

Greetings everyone!
I ran into a problem with Lync 2013 x64 silent deployment.
I need to provide every workstation with Lync 2013 client, so i decided to use deployment via SCCM 2012 sp1.
I created 2 msp files with OCT, one based on x86 Office 2013 Proplus, and other based on x64 Office 2013 Proplus.
Added them as applications to sccm software library.
Deployment of Lync 2013 x86 application was a success with over than 80% compliance.
But all Lync 2013 x64 automatic installations finish with different errors.
I created special device collection for workstations with office 2010 x64 and 2013 x64, because i can't install other architecture products once it has x64 product installed.
My membership query-rules for this collection:
Office 2013 x64
select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System inner join SMS_G_System_INSTALLED_SOFTWARE on SMS_G_System_INSTALLED_SOFTWARE.ResourceId
= SMS_R_System.ResourceId where UPPER(SMS_G_System_INSTALLED_SOFTWARE.SoftwareCode) = "{90150000-0011-0000-1000-0000000FF1CE}"
Office 2010 x64
select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System inner join SMS_G_System_INSTALLED_SOFTWARE on SMS_G_System_INSTALLED_SOFTWARE.ResourceId
= SMS_R_System.ResourceId where UPPER(SMS_G_System_INSTALLED_SOFTWARE.SoftwareCode) = "{90140000-0011-0000-1000-0000000FF1CE}"
My application deployment type points to setup.exe in office 2013 x64 installation folder, where i created msp file in updates folder via OCT and edited config.xml file in proplus.ww folder.
So my installation program looks like this setup.exe /adminfile updates\1lync.msp /config proplus.ww\config.xml
The same configuration works with Lync 2013 x86 deployment, except other setup folders.
When i try running installation program setup.exe with /adminfile and /config parameters locally, it installs successfully without errors or warnings.
I'm trying to find out problem source, does anyone have ideas what I am doing wrong?
Also i'm trying to reduce office 2013 installation folder size, what subfolders are necessary for Office 2013 proplus installation (still installing only lync with common files and tools)? Because now 3.5 GB package is quite hard to distribute to sccm secondary
sites with deployment point.
Thanks in advance.

Hi,
Here are some tips and tricks for your reference.
Tips and Tricks: Deploying Lync 2013 client using SCCM 2012 | Lync 2013 Client Customization for SCCM 2012 Deployment Package
http://zahirshahblog.com/2014/01/08/tips-and-tricks-deploying-lync-2013-client-using-sccm-2012-lync-2013-client-customization-for-sccm-2012-deployment-package/
Note: Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Lync 2013 Showing Phone Numbers which have been removed from AD

My Server is Lync 2013, Exchange is 2010 SP3. I'm also running 2012 Domain Controllers. The Lync 2013 install is migrated from 2010.
I have a myriad of users who have moved departments and thus have a new, or altered phone number, but for some reason the contact cards in all of my Lync 2010/2013 clients and Outlook 2010/2013 are showing phone numbers that no longer exist in Active
Directory.
If the Lync client is closed the Outlook Contact card does not show these "phantom" numbers:
But if the client is open the contact card has a number that doesn't exist in any field in Active Directory (I checked twice):
Suggestions? I have many users displaying phantom numbers in Contact Cards. My normalization rules are working correctly (no errors), and synchronization seems to be working as expected. I have also run debug-csaddressbookreplication with verifyreplication
on a problem user and it succeeds. I've also double-checked the attribute values and this phantom phone number does not exist.
Is it possible that the 2010 Contacts migrated from the old server contain these phantom entries, is there a way to clear this information out and start fresh if need be?
Thanks Kindly!

I actually found a bit of a solution without going to MS for support.
I haven't done this for all users yet, but I tested this solution on two users last week.
I removed the problem users from the Lync pool via the Lync console.
I then ran update-csaddressbook and waited the requisite time for a full address book sync to complete.
I then added the user back into the pool and ran another update-csaddressbook.
The contact details were refreshed and updated correctly. It appears that this was the only way to force-remove the legacy address and phone number information from the problem users I tested on as the problem users were added back in as a "new" user.
Hopefully this solution works for you too.

Upgrading from OCS2007R2 to Lync 2013

Folks,
We are looking to migrate our OCS 2007 R2 Enterprise, to Lync 2013.
We are running AD windows Server 2012 R2 functioanl level.
We have completed the schema,forest and domain prep for Lync 2013.
I have a few questions that you guys may be able to answer.
1.)
Can we upgrade from OCS 2007 R2 enterprise pool to LYNC 2013 standard pool.
2.)
Is there any concise documents out there that document how to upgrade form OCS 2007 R2 to Lync 2013.
Regards

Hi,
Migration of all Lync Server topologies and server roles is supported. You can migrate from one topology to a different topology, including from Standard Edition server to Enterprise
Edition server.
Click on the link below for more details,
Supported server migration paths and coexistence scenarios in Lync Server 2013
http://technet.microsoft.com/en-us/library/gg425764.aspx
Best regards,
Eric

OCS to Lync 2013, move all users over before client deployed?

Hello, quick question hoping someone can answer...
We've deployed Lync 2013 and are migrating about 2000 users from OCS across many branch offices, going branch-by-branch.
Is there any downside to moving ALL 2000 users over to the Lync pool before they have the Lync client deployed to their site? They would still be using Communicator until their site receives the Lync install. I know Communicator works when connecting to
the Lync pool so I'm guessing this should be OK.
The problem we're seeing during this transition phase is when an employee travels to a site that's had Lync client deployed but the employee is still on the Communicator pool because their primary site hasn't been upgraded yet, and are thus unable to sign-in
to Lync.

I would agree with Anthony,
The basic features works with the Communicator clients but when it comes to conferencing users will face a lot of problems, also a problem as been identified during such scenario is when users homed on the lync pool and signing in using the OC client
experience a weird behavior when their contact lists disappear, then it appears again when logging using a lync client.
as a resume.
If you are obliged to use the OC client please make sure that it is patched with the latest updated released.
as a best practice move to Lync client as soon as possible.
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

Migrating Lync 2010 Std to Lync 2103 Std- Move PSTN Gateway and Trusted Applications

We had a Lync 2010 Std server in one site and pool and migrated to Lync 2013 Std by creating another site and pool. Same SIP domain, etc. Everything is working so far that we have tested.
My question is now is there a way to just move the PSTN gateway and trunk that shows in the shared components of the Lync 2010 site to the Lync 2013 site?

Hi,
You can create PSTN geteway for Lync 2013. As Holger said, you cannot movei it.
Kent Huang
TechNet Community Support

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 2013 migration from Lync 2010

Hi All,
I have a problem after I've successfully migrated our Lync environment from Lync 2010 (what was migrated from OCS 2008 R2) to Lync 2013.
When I would like to delete the old Lync 2010 Front End server from the topology I cannot do that, because there are some TrustedApplicationPool registered to that. And I cannot delete this unused TrustedApplicationPools, because I got the following error:
"Remove-CsTrustedApplicationPool : Cannot remove legacy trusted application pool. Use the legacy tools to remove the pool, then run Merge-CsTopology."
I've tried that many ways, I've tried the merging etc. but it was unsuccessful. Has anybody any idea, step-by-step or something what can helpful to me?
Many thanks,
Tamás Dobos

Hi,
Did you check this step by step migration lync 2010 to 2013
http://www.oiboran.com/?p=1073
To remove Trusted application pools
Get-CSTrustedApplicationPool
Remove-CSTrustedApplicationPool -Identity nameofthepool
Removing Lync 2010
http://terenceluk.blogspot.nl/2012/12/removing-lync-server-2010-standard.html
Whenever you see a helpful reply, click on Vote As Helpful & click on Mark As Answer if a post answers your question.

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]

CMS Migration - Lync 2010 to Lync 2013 & Pool Pairing

Hi all,
Question regarding CMS installation when migrating away from Lync 2010.
Here's a brief overview of topology
- Lync 2010 Pool in Data Centre 1
- Lync 2013 Pool #1 in Data Centre 1
- Lync 2013 Pool #2 in Data Centre 2
- Lync 2013 Pools are paired
Consider the following
- CMS located on SQL Backend server for Lync 2010 Pool
- CMS database installed on SQL Back end for Lync 2013 Pool #1. CMS is moved to this location
Now for correct pool pairing and failover capabilities I would assume that
- CMS database needs to also be installed on SQL back end for Lync 2013 Pool #2
Once this is done then Lync 2013 Pool #2 Front Ends should replicate back into the CMS stored on the back end SQL database for pool #2? Nothing else would need to be done? As soon as it's installed its now a backup?
If I'm reading into this correctly the following from TechNet is basically telling me to do this?
When you establish a pool pairing that includes the pool hosting the Central
Management store, a backup Central Management store database is set up in the
backup pool, and Central Management store services are installed in both pools.
At any point in time, one of the two Central Management store databases is the
active master, and the other is a standby. The content is replicated by the
Backup Service from the active master to the standby.
Thanks,
paul.

Correct, when you enable pool pairing on Pool A - if it's a CMS server - it will prompt you to create the CMS database on Pool B. If you move CMS into a pool that is already pool paired, my experience is that CMS doesn't get created on Pool B because the
creation only happens during the pool pairing setup. Thanks -Richard
Richard Brynteson, Lync MVP | http://masteringlync.com | http://lyncvalidator.com

Lync 2010 to Lync 2013 migration - Dialin conferencing

While migrating from Lync 2010 to Lync 2013, i have stopped all services on the Lync 2010 servers to make sure all is okay and everything is working fine with Lync 2013.
Nevertheless, when someone on Lync 2013 schedule a meeting, and someone dial one of the PSTN Dialin conference number and enter the conference ID, this scenario is not working.
If i start the Lync 2010 front end services, then the previous scenario works.
So i did something else. I have scheduled a meeting and i change the meeting options to get a new conference ID. this makes the conference work over dial in pst number while Lync 2010 services are down.
This means:
- When someone (Lync 2013 user) schedule a meeting, the default conference ID that is generated, requires the existence of Lync 2010 services for a PSTN Dial in user to connect
-When someone (Lync 2013 user) schedule a meeting and change the meeting options to get a new conference ID, then the PSTN Dial in user can connect even if all Lync 2010 services are down.
Any clue?
ammarhasayen

i have found it. moving the conference directories from Lync 2010 to Lync 2013 solves the whole thing.
ammarhasayen

Lync 2013 multitenant hosting pack and lync 2010 on-prem - coexistence options, alternative migration scenarios

In post http://social.technet.microsoft.com/Forums/lync/en-US/8a22eed7-cc63-4f9e-b422-3c5a57fb32b0/lync-2013-multitenant-pack-and-lync-2010?forum=lyncdeploy , which was already answered, the answer is no, you cannot migrate from 2010 on-prem. to lync 2013
hosted pack.
Trying to get my head around #1 -why, and #2 -what other alternatives are available.
Lisa answered that there can only be 1 CMS per forest. Is it one CMS per forest, or
one CMS per front end pool in a forest? Meaning you can have different CMS pools. If that were true, we could migrate users to a different front end pool in a coexistence scenario between 2010 on-prem to 2013 hosted pack.
Has anyone done this?
This is tough. I guess a cutover then from 2010 to 2013 multitenant hosted pack would be what?
1. Uninstall 2010, decommission users, decom environment/servers.
2. Fresh install in same AD environment of 2013 hosted pack.
That's tough for our users to make such a transition and have potentially days of downtime.
Is there no other way to do this?
Josh

It is one CMS per forest.
There is no official guide to move from Microsoft Lync Server to Microsoft Lync Server Multitenant Hosting Pack.
This topic has been discussed several times before:
http://social.technet.microsoft.com/Forums/lync/en-US/9d438b55-ec53-478a-9247-6d355abedb78/started-installing-lync-2010-enterprise-discovered-multitenant-hosting-pack-do-i-need-to-uninstall?forum=ocsplanningdeployment
http://social.technet.microsoft.com/Forums/lync/en-US/ad0b77ca-d47e-457b-8f77-33f84409a119/schema-update-lync-hosting-pack?forum=ocsplanningdeployment
Lisa Zheng
TechNet Community Support

User migration from Lync 2010 to Lync 2013

We have Lync 2013 pool co-existence with Lync 2010 pool. Need to move users based on their AD Group membership. In a particular AD group, only few of the users are enabled for LYNC 2010, not all users. How to get the list of only Lync enabled users in AD
group and move them on to Lync 2013 by PowerShell script?
Thanks in advance for your help
Tek-Nerd

When I ran the below command
Get-ADGroupMember Mygroup | where {$_.msRTCSIP-UserEnabled -eq "true"}
on my Lync 2013 server, got the below error message...
At line:1 char:46
+ Get-ADGroupMember MyGroup | where {$_.msRTCSIP-UserEnabled -eq "true"}
+
~~~~~~~~~~~~
Unexpected token '-UserEnabled' in expression or statement.
At line:1 char:59
+ Get-ADGroupMember MyGroup | where {$_.msRTCSIP-UserEnabled -eq "true"}
+
~~~
Unexpected token '-eq' in expression or statement.
    + CategoryInfo          : ParserError: (:) [], ParentContainsErrorRecordExcep
    + FullyQualifiedErrorId : UnexpectedToken
Tek-Nerd

Lync 2010 to Lync 2013 Trusted application Migration

Similar Messages

Maybe you are looking for