Migrating Lync 2013 to new domain

I have a customer who wants to migrate their Lync servers to a new domain. Is this possible with the existing servers or do I need to backup the config, deploy new Lync servers in that domain and restore the config? Thanks in advance.

New SIP domain or a new Active Directory Domain? You can easily add new SIP domains to the environment. You cannot move a Lync Server from one AD domain to another. You would need to migrate users in a cross forest scenario or backup contacts
and restore.
Thanks,
Richard
Richard Brynteson, Lync MVP | http://masteringlync.com | http://lyncvalidator.com

Similar Messages

Migration; Exchange 2003 SP2 to Exchange 2013 on new Domain and DC

I wasn't prepared for this task, and it was thrown at me to do... Eyes are bleeding from planning reading and planning, would LOVE any input from you guys. First time posting, here and have heard great things about these forums. The Company
I work for obtained a new client and a network that is in a cluster at the moment, so I'm having to dig through everything and restructure..
Scenario:
Old Domain/Server: (To be decommissioned)
Server 2003 Standard SP2 (Domain: cosco.com; NETBIOS name: coscoex)
Exchange 2003 SP2 (6.5.7638.1)
Server is a domain controller and exchange server.
Migrating to:
Server 2012 R2 Datacenter (New Domain ad.cosco.com; NETBIOS name: cosco)
VM #1: Server 2012 R2 Domain Controller at 2012 R2 Functionality
VM #2: Server 2012 R2 with Exchange 2013 Standard (Not Yet Installed) Joined to ad.cosco.com domain
VM #3: Server 2012 R2 with Exchange 2010 (Not Yet Installed) joined to ad.cosco.com domain
These are probably not ideal conditions, but I have to work with what I'm given.
Host server (2012 R2) is in work group mode. Hyper V Installed with a VM of Server 2012 R2 and as a DC at a functionality level of Server 2012 R2. I had intended starting at a lower functionality level and raising
it later, but.... ya I forgot to change it. If needed I can spool up a new DC with a lower functional level.
DNS, AD and group policy is all jacked up on the 2003 DC so that doesn't matter, All user accounts are going to be created under the new domain. The concern is migrating the mailboxes from Exchange 2003 on the old domain to
Exchange 2013 on the new domain. The client is going to provide CSV of the AD accounts that are still valid (a lot of accounts are no longer used or are from people that no longer with the organization.)
I had some ideas, but I'm not sure if they will work. This is something I have never done before (Senior Engineer Quit).
My thoughts:
- Establish a two way trust relationship between the two domains.
- Create two VM's, one with Exchange 2010 and one with Exchange 2013 (They have a 2010 licence that was not used).
- Create the users on the new domain
- Use the double hop method from Exchange 2003 > Exchange 2010 > Exchange 2013
- Link Exchange accounts to the correct user accounts on the new DC.
Can this be done cleanly? Am I going about this the correct way? Any feedback would be GREATLY appreciated.
Note: We are forced to use ad.cosco.com (Obviously not the actual domain name)

Hi,
Base on my experience, your idea is feasible.
However, before getting started, you should note that Exchange 2010 (with any service pack or update rollups) is not (yet) supported to install on Windows 2012 R2. More details refer to the following link:
http://technet.microsoft.com/library/ff728623(v=exchg.150).aspx
After all the preparations complete, you can refer to the following articles to migration exchange 2003 to 2010, then to 2013:
Exchange 2003 to 2010 Cross-Forest Migration Step by Step Guide
Exchange 2010/2007 to 2013 Migration and Co-existence Guide
Best regards,
Niko Cheng
TechNet Community Support

Migrating Spiceworks to a new domain

Hi,We are currently migrating between domains, and I have been tasked with migrating Spiceworks. I've moved between servers before by exporting the database and re-importing it on the new server, but this is slightly different.The install is AD integrated, and we are moving from one domain to the other. The username structure will be the same but obviously change due to the domain change (e.g: domain1\abc becomes domain2\abc.) However, the email address is staying the same which uses a different domain name which we just use for email.We want to preserve the logged tickets, users logged against tickets, AD logon to the portal, avoid duplication in the people database (e.g: avoid one entry on each domain for each person) and keep the network scan.Is there some sort of conversion tool or script to run to help with this?Thanks,Dan
This topic first appeared in the Spiceworks Community

Hello Spiceworks,Can someone please help with the following situation?I have an email domain set up using Horde (mail.my-company-name.com) and a set of email addresses ([email protected]). I want to migrate all of these accounts to Google Apps for Work, and I also need to migrate the emails, but it is unclear from the Google Help pages ( https://support.google.com/a/answer/6250450?hl=en ) how this is accomplished.More specifically, what will happen when I create a Google Apps for Work for my-company-name.com ? When someone sends an email to [email protected] , will it be received in my new Gmail account or on Horde? Or do I need to change MX records in my hosting control panel for this?Secondly, if I want to migrate the emails from Horde for userx, how do I set it up in Google (since the same [email protected]..

Lync 2013 & Active Directory Intra Domain Migrations

Hi all,
Hopefully this is the correction forum to ask. Suppose the following scenario
Parent Domain containing Lync 2013 Servers
Child domains consisting of user accounts
It is intended that child domains containing Lync 2013 enabled users be migrated to the parent domain.
A few questions
Is it possible to migrate user accounts to another domain and configure the migrated (technically new) account to link back to Lync so as to retain contact information?
Or prior to migration have contacts exported so they can be imported into the new Lync 2013 accounts?
Thanks,

Within a single forest it quite possible to have Lync installed in one domain and User a part of another domain
All we have to do during the Lync server install process run the domain prepaerationn wizard for all the domain weher we shall either have Lync user object or Lync server object
Please refer http://technet.microsoft.com/en-us/library/gg398630.aspx
I believe As long as the user SIP URI Doesn't change you can export the user data information and after the migration if you can import in user information
Please refer http://technet.microsoft.com/en-us/library/jj204897.aspx
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 Answered"

Migration from Exchange 2007 to 2013 between different domain

Hi,
Our company have two domains controller (AD1 and AD2) but it is not trusted. Due to company change, we need to plan merge two domains to new domain (AD3). Under the plan, we will user ADMT for user object migration and password.
For Exchange, we will plan to use Exchange 2013 on new domain. I want to know that what is the best way to migrate all mailboxes from AD1 and AD2 to AD3's new exchange server. We need to migrate over 500+ mailboxes.
Please anyone to suggest what is the best way to do it ?
thanks

Hello,
You can use the New-MigrationBatch cmdlet to move more than one mailbox at a time. When you create a migration batch, I recommend you use the LargeItemLimit parameter specifies the number of large items to skip if the move request encounters such items
in the mailbox.
If you have any feedback on our support, please click
here
Cara Chen
TechNet Community Support

Upgrading AD Server for Lync 2013

I have now a Lync 2013 infrastructure deployed on an Active Directory infrastructure based on Windows Server 2003 including the servers, the domain functional level and forest functional level. We are planning to upgrade to Windows Server 2012.
My questions are:
1/ What are the impacts to my Lync 2013 infrastructure?
2/ Is there any documentation addressing the changes on the Lync Infrastructure in relation to AD upgrade?
3/ Anyone could share his/her experience?
Albert

Hi Albert,
Lync 2013 supports a domain functional level of Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2, Windows Server 2008, or at least Windows Server 2003.
Hence when you introduce a Win2012 DC into the environment, it doesn't make any difference till you have the domain\forest Func Levels at Windows Server 2003.
Windows Server 2003 domain and functional levels of Active Directory are depreciated(soon to be removed) in Windows Server 2012 DC. So if you plan to remove the Windows 2003 and raise the FFL\DFL then you need to consider the questions you have
here.
What Happens Next?
Another common question: what impact does changing the Domain or Forest Functional Level have on enterprise applications like Exchange or Lync, or on third party applications? First, new features that rely on the Functional Level are generally limited to
Active Directory itself. Regardless, changing the Domain or Forest Functional Level should have no impact on an application that depends on Active Directory.
An application like Exchange uses Active Directory to store its objects, or to perform various operations, none of that functionality should be affected if the Domain or Forest Functional Mode changes. In fact, if your applications are also written to take
advantage of new features introduced in Active Directory, you may find that the capabilities of your applications increase when the Level changes.
The answer to the question about the impact of changing the Domain or Forest Functional Level is there should be no impact.
Lync 2013 FFL\DFL requirement
doesn't specify any additional features upon raising the levels beyond Win2003.
Just make sure you don't break the existing DC and have enough redundancy.
Supported in-place upgrade paths
Domain controllers that run 64-bit versions of Windows Server 2008 or Windows Server 2008 R2 can be upgraded to Windows Server 2012. You cannot upgrade domain controllers that run Windows Server 2003 or 32-bit versions of Windows Server 2008. To replace
them, install domain controllers that run a later version of Windows Server in the domain, and then remove the domain controllers that Windows Server 2003.
References:
https://technet.microsoft.com/en-us/library/gg412955(v=ocs.15).aspx
What is the Impact of Upgrading the Domain or Forest Functional Level?
Active Directory Domain Services support in Lync Server 2013
Regards,
Satyajit
Please “Vote As Helpful”
if you find my contribution useful or “Mark As Answer” if it does answer your question. That will encourage me - and others - to take time out to help you.

CMS Movement from Lync 2010 to Lync 2013 SQL Mirroring

Hi,
I have read the articles and i know how to move CMS to Lync 2013 , MY question is after moment CMS to Lync 2013 , the new DBs on SQL server will be mirrored automatically or i have to apply some procedure to make them mirror.
Regards
Usman Ghani
Usman Ghani - MCITP Exchange 2010

Good morning,
If the new Lync 2013 Enterprise Pool you deployed has a mirrored backend, then when you move the CMS to that instance the database will inherently be mirrored. There is no requirement to perform any additional action or procedure.
This assumes that you have an enterprise Lync 2013 deployment as a mirrored CMS would not be available on a standard edition deployment.
Kind regards
Ben
Note: If you find a post informative, please mark it so using the arrow to the left. If it answers a question you've asked, please mark the thread as answered to aid others when they're looking for solutions to similar problems or queries.
Lync Skype Blog: Gecko-Studio

Lync 2013 Topology Publication Failed!

Scenario
Lync Enterprise Edition!
Windows Server 2012R2 - LyncServer 2013
WIndows Server 2008R2 - Sql 2008 R2 Failover Cluster (Multiple Database and Instances Created) 5 Others Application Database also
Created which has been used.
DNS Entries
HOst Name :
LYNCFE.consoto.com
Pool.consoto.com (Host Name Created Same IP as Lync Frontend Server)
dialin.consoto.com
meet.consoto.com
admin.consoto.com
DBLYNC.consoto.com
Virtual Instant Name of Sql Database and Instance name : DBLYNC\Lynccore
Permission Rights:
I am using the Administrator account for Lync 2013 Installation.
Domain Administrator Account Member to CSAdministrator group and RTC Universal Server admin group.
SQL sysadmin Account member Sqladmin and Domain administrator User.
ShareFolder-Lyncshare on Storage.consoto.com
Permission:
Everyone
Read-write
RTCComponentUniversalServices Read-write
RTCHSUniversalServices Read-write
RTCUniversalServerAdmins Read-write
RTCUniversalConfigReplicator Read-write
Virtual Computer Name DBLYNC$
Full control
Issue : I have create one topology and try to publish but getting error.Log Detail Below
Feature: CentralMgmtStore
SQL Instance: domain-name.com\lynccore
Collocated: False
Found "RTCUniversalServerAdmins": True
Found "RTCUniversalConfigReplicator": True
Found "RTCUniversalReadOnlyAdmins": True
TaskFailed: Task execution failed.
Error:The network name cannot be found.
▼ Details
└ Type: IOException
└ ▼ Stack Trace
└ at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.Directory.InternalCreateDirectory(String fullPath, String path, Object dirSecurityObj, Boolean checkHost)
at System.IO.Directory.InternalCreateDirectoryHelper(String path, Boolean checkHost)
at Microsoft.Rtc.Common.Data.DatabaseManager.CreateDatabase(String dbFileBase, String dbPath, String logPath, Int32 dbSizeMB, Int32 logSizeMB, Int32 dbGrowthMB, Int32 logGrowthMB, Int32 maxDbSizeMB, Int32 maxLogSizeMB)
at Microsoft.Rtc.Common.Data.DatabaseManager.CleanInstallDatabase(String dbFileBase, String initialScripfilePath, String
dbPath, String logPath, Int32 dbSizeMB, Int32 logSizeMB, Int32 dbGrowthMB, Int32 logGrowthMB, Int32 maxDbSizeMB, Int32 maxLogSizeMB)
at Microsoft.Rtc.Common.Data.DbSetupBase.CleanInstallDatabase()
at Microsoft.Rtc.Common.Data.DbSetupBase.CreateOrUpdateDatabase()
at Microsoft.Rtc.Common.Data.XdsDatabase.CreateOrUpdateDatabase()
at Microsoft.Rtc.Management.Deployment.Tasks.DatabaseCreator.CreateDatabaseForFeature(String featureName, Boolean clean, Boolean update, String sqlServer, String instanceName, Boolean collocated, Boolean backup, Boolean noreindex,DatabasePathAssignment[]
pathAssignments, Boolean broadCast, String& logfile)
at Microsoft.Rtc.Management.Deployment.installdatabaseCmdlet.CreateDatabaseForFeature(Planitem i)
at Microsoft.Rtc.Management.Internal.Utilities.LogWriter.InvokeAndLog[T](Action`1 action,T arg)
TaskFailed: An error occurred while creating or updating the database for feature CentralMgmtStore. For details, see the log
file ‘C:\Users\Administrator\AppData\Local\Temp\2\Create-CentralMgmtStore-domain-name.com_lynccore-[2014_07_09]
[11_40_46].log’
TaskFailedResolution: Consult exception information and previous errors for more information on how to resolve this error.
Error: An error occurred: "System.IO.FileNotFoundException" "The network name cannot be found"

SQL Scenario
Windows Server 2008R2 - Sql 2008 R2 Failover Cluster (Multiple Database and Instances Created) 5 Others
Application Database also Created on the Failover Cluster.
Failover SQL Cluster
Active Passive
Computer Name: Cluster1.Consoto.com
Computer Name : Cluster2.Consoto.com
ping cluster1.consoto.com reply IP 192.168.0.30 from Lync FE ping
cluster2.consoto.com reply IP 192.168.0.31 from Lync FE
SQL Database DBLYNC IP is 192.168.0.40 and also reply from Lync Server

Lync 2013 Publish Topology Failed in window server 2012R2

Scenario
Lync Enterprise Edition!
Windows Server 2012R2 - LyncServer 2013
WIndows Server 2008R2 - Sql 2008 R2 Failover Cluster (Multiple Database and Instances Created) 5 Others Application Database also Created which has been used.
DNS Entries
HOst Name :
LYNCFE.consoto.com
Pool.consoto.com (Host Name Created Same IP as Lync Frontend Server)
dialin.consoto.com
meet.consoto.com
admin.consoto.com
DBLYNC.consoto.com
Virtual Instant Name of Sql Database and Instance name : DBLYNC\Lynccore
Permission Rights:
I am using the Administrator account for Lync 2013 Installation.
Domain Administrator Account Member to CSAdministrator group and RTC Universal Server admin group.
SQL sysadmin Account member Sqladmin and Domain administrator User.
ShareFolder-Lyncshare on Storage.consoto.com
Permission:
Everyone Read-write
RTCComponentUniversalServices Read-write
RTCHSUniversalServices Read-write
RTCUniversalServerAdmins Read-write
RTCUniversalConfigReplicator Read-write
Virtual Computer Name DBLYNC$ Full control
Issue : I have create one topology and try to publish but getting error.Log Detail Below
Feature: CentralMgmtStore
SQL Instance: domain-name.com\lynccore
Collocated: False
Found "RTCUniversalServerAdmins": True
Found "RTCUniversalConfigReplicator": True
Found "RTCUniversalReadOnlyAdmins": True
TaskFailed: Task execution failed.
Error:The network name cannot be found.
▼ Details
└ Type: IOException
└ ▼ Stack Trace
└ at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.Directory.InternalCreateDirectory(String fullPath, String path, Object dirSecurityObj, Boolean checkHost)
at System.IO.Directory.InternalCreateDirectoryHelper(String path, Boolean checkHost)
at Microsoft.Rtc.Common.Data.DatabaseManager.CreateDatabase(String dbFileBase, String dbPath, String logPath, Int32 dbSizeMB,
Int32 logSizeMB, Int32 dbGrowthMB, Int32 logGrowthMB, Int32 maxDbSizeMB, Int32 maxLogSizeMB)
at Microsoft.Rtc.Common.Data.DatabaseManager.CleanInstallDatabase(String dbFileBase, String initialScripfilePath, String
dbPath, String logPath, Int32 dbSizeMB, Int32 logSizeMB, Int32 dbGrowthMB, Int32 logGrowthMB, Int32 maxDbSizeMB, Int32
maxLogSizeMB)
at Microsoft.Rtc.Common.Data.DbSetupBase.CleanInstallDatabase()
at Microsoft.Rtc.Common.Data.DbSetupBase.CreateOrUpdateDatabase()
at Microsoft.Rtc.Common.Data.XdsDatabase.CreateOrUpdateDatabase()
at Microsoft.Rtc.Management.Deployment.Tasks.DatabaseCreator.CreateDatabaseForFeature(String featureName, Boolean clean,
Boolean update, String sqlServer, String instanceName, Boolean collocated, Boolean backup, Boolean noreindex,
DatabasePathAssignment[] pathAssignments, Boolean broadCast, String& logfile)
at Microsoft.Rtc.Management.Deployment.installdatabaseCmdlet.CreateDatabaseForFeature(Planitem i)
at Microsoft.Rtc.Management.Internal.Utilities.LogWriter.InvokeAndLog[T](Action`1 action,T arg)
TaskFailed: An error occurred while creating or updating the database for feature CentralMgmtStore. For details, see the log
file ‘C:\Users\Administrator\AppData\Local\Temp\2\Create-CentralMgmtStore-domain-name.com_lynccore-[2014_07_09]
[11_40_46].log’
TaskFailedResolution: Consult exception information and previous errors for more information on how to resolve this error.
Error: An error occurred: "System.IO.FileNotFoundException" "The network name cannot be found"


SQL Scenario
Windows Server 2008R2 - Sql 2008 R2 Failover Cluster (Multiple Database and Instances Created) 5 Others Application Database
also Created on the Failover Cluster.
Failover SQL Cluster
Active
Passive
Computer Name: Cluster1.Consoto.com
Computer Name : Cluster2.Consoto.com
ping cluster1.consoto.com reply IP 192.168.0.30 from Lync FE
ping cluster2.consoto.com reply IP 192.168.0.31 from Lync FE
SQL Database DBLYNC IP is 192.168.0.40 and also reply from Lync Server

New lync 2013 , 2 subdomains ,ad one domain in foreign country

As you can see in the picture below, I have the main AD called main.prod and two child1 and child2 subdomains. What is more I have AD called international.prod placed in foreign country. I have mbox, cas using child1.main.prod domain and
lync 2010 with UM funcion. The more I have 2way trust between child2.main.prod subdomain and international.prod domain. Now what I would like to do is : make CAS in subdomain child2.main.prod which is authorising people from domain international.prod
and have mailboxes on mbox from subdomain child1.main.prod as it is shown in the picture. Do you think it make sense? Or I have to make mbox in subdomain child2.main.prod????
WHat else: I would like resign Lync 2010 and install new Lync 2013 and make people from subdomains: child1 and child2 and domain international.prod using this new Lync ,and move UM funcionality from old 2010 lync into new 2013.
Any contraindications, suggestions??

Lync Server supports the following topologies for Exchange UM integration:
Multiple domain (that is, a root domain with one or more child domains). Lync Server, and Microsoft Exchange servers are deployed in different domains from the domain where you create users. Exchange UM servers can be deployed in different
domains from the Lync Server pool they support.
Lisa Zheng
TechNet Community Support

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

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

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

Lync 2013 migraiton from old domain (contoso.local) to new domain (contoso.co.uk)

Hi Team,
The following is our requirement and environment, please advise.
Environment 1
Domain1 : Contoso.local
Lync 2013 onpremise server
Environment 2
>> Created the following domain in New AD environment and built new lync machines.
Domain 2: Contoso.co.uk
Lync 2013 onpremise server
Requirement:
1. Wanted to move all configuration (DialPlans, VoicePolicy, Users, ResponseGroups, etc) from the old AD to the new AD on the newly built lync machines.
2. Prepared PowerShell script to get this done.
3. Plan is to export the configuration to the new servers and import those exported config files on the new machines.
Question:
1. Will it work if AD domain is different on each of those servers? Old server has contoso.local and new one has contoso.co.uk.
2. What are the impacts and will we be able to get this done?

I assume that those are different AD forests?. Even though it's different forest, you can export the Voice routing components, RGS components and import that in to the new setup and it will work fine. For RGS, you need to re assign the agents to the agent
groups after importing to the new server. And also, you can export the buddy list of the users and then import that in to the new Lync server as well upon enabling the users. I have done the same setup just exporting and importing using the Lync control panel.
Not sure what's the script that you're talking about.
http://thamaraw.com

No users are being migrated to the Unified Contact Store (UCS) for Lync 2013 - Exchange 2013

I'm having difficulty getting the unified contact store to work on a migrated Lync/Exchange environment. Both servers have been upgraded to 2013 CU2, and almost everything appears to be working properly...except UCS.
By default the global CsUserServicesPolicy has UcsAllowed set to True. In that mode, none of the Lync users were being migrated to UCS, so I set the global policy to False and created a new Policy called "AllowUCS" and set UcsAllowed to True. I then
assigned that policy to myself and a couple other test accounts. Still, my contacts are not being migrated to the UCS after logging in with Lync 2013.
Other Lync/Exchange integration features are working properly. I have set up OAuth, and it tests successfully, and Lync integration with OWA is working successfully, so I know at least some communication is happening properly between the servers.
Here is what I'm getting when I run some diagnostics from the Lync server:
PS C:\Users\administrator> get-csuser jdoe |FL Name,UserServicesPolicy
Name : Jon Doe
UserServicesPolicy: AllowUCS
PS C:\Users\administrator> Get-CsUserServicesPolicy |FL
Identity : Global
UcsAllowed : False
Identity : Tag:AllowUCS
UcsAllowed : True
PS C:\Users\administrator> Debug-CsUnifiedContactStore -Identity [email protected] |FL
UcsMigrationAttemptCount : 0
LastUcsMigrationAttempt :
SipUri : [email protected]
UcsMode : Disabled
PS C:\Users\administrator> Debug-CsUnifiedContactStore -PoolFqdn lync.domain.org
FrontEnd : lbclync.domain.org
UcsDisabledCount : 141
UcsAllowedCount : 0
UcsMigratingCount : 0
UcsMigratedCount : 0
FailedUserData :
PS C:\Users\administrator> Test-CsUnifiedContactStore -UserSipAddr
ess [email protected] -TargetFqdn lync.domain.org
Target Fqdn :lync.domain.org
Result : Failure
Latency : 00:00:00.0654970
Error Message : User has not been migrated. Verify that the user has a mailbox
in Exchange and that the user has been migrated.
Diagnosis :
Anyone know what I am missing?

Hi,
Please make sure the user has been provisioned with an Exchange 2013 mailbox and has signed into the mailbox at least once.
If the user logs in with a Lync 2010 or earlier client, or if the user is not connected to an Exchange 2013 server, the user services policy is ignored and the user's contacts remain in Lync Server.
Please also check the registry key on the client computer:
HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Lync\<SIP URL>\UCS
If the user's contacts are stored in Exchange 2013, this key contains a value of InUCSMode with a value of 2165.
Kent Huang
TechNet Community Support

Setting up a new Lync 2013 Lab

Hi there
We currently have a Lync 2013 enterprise setup running our production environment. We have some problems and have decided to setup a new Lab Lync 2013 environment to do some more testing on and to see if we can at a later stage migrate over from the production
environment to the Lab one.
We are planning on creating the lab one as close to the production one as possible, same amount of servers, same spec etc.
How would we go about this and is this possible to run on the same domain? We will be using different SIP and FQDN but what about the SQL server and when deploying the topology, will it have any effect on the current production environment? Or should we
not use the same AD forest and completely separate it from our current network.
Thank you.

Hi Jaco1301,
Agree with Tek-Nerd.
In addition, you could add the additional pools in Topology Builder. Then publish the topology, run Lync Server Deployment Wizard on each Front End server in the new pools. But the CMS is still
stored on your production server.
Best regards,
Eric

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"

Migrating Lync 2013 to new domain

Similar Messages

Maybe you are looking for