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

Similar Messages

New Lync 2013 and no mobile to PC calling

I have a new Lync 2013 enterprise server deployment. PC with 2013 client and android phone with 2013 mobile client can both connect and IM fine. but when I make a Lync call it will ring but not answer even if I click accept. It just says
connecting.... I have looked at logs for the PC, phone and on the server but dont see any errors. I am just not sure where to go from here. Any suggestions would be greatly appreciated.
Thanks!!

After looking through the massive lync clinet 2010 log for almost 3 hours I finally found this:
02/07/2014|11:14:20.065 1250:120C INFO :: BYE sip:[email protected];opaque=user:epid:F75G9E5FoVmO8RMWQRntYgAA;gruu SIP/2.0 Via: SIP/2.0/TLS 127.0.0.1:50042 Max-Forwards: 70 From: <sip:[email protected]>;tag=967b0de09e;epid=e115ec3448
To: "phone"<sip:[email protected]>;tag=d007b4c5e;epid=212185984839 Call-ID: d6c4a0b89c58477b87650daa0bb16fe9 CSeq: 3 BYE User-Agent: UCCAPI/4.0.7577.0 OC/4.0.7577.0 (Microsoft Lync 2010) ms-client-diagnostics: 23; reason="Call failed to establish
due to a media connectivity failure when one endpoint is internal and the other is remote";CallerMediaDebug="audio:ICEWarn=0x2b,LocalSite=10.1.1.158:14842,LocalMR=pu.bl.ic.ip-AV:3478,RemoteSite=10.38.210.159:19600,PortRange=1025:65000,LocalLocation=1,RemoteLocation=2,FederationType=0"
Proxy-Authorization: NTLM qop="auth", realm="SIP Communications Service", opaque="E84145BE", targetname="FrontEndSrv1.domain.local", crand="f5c0735e", cnum="28", response="0100000065633334d5df23b80d7f3491" Content-Length: 0
02/07/2014|11:14:20.065 1250:120C INFO :: End of Sending Packet - pu.bl.ic.ip-sip:443 (From Local Address: 127.0.0.1:50042) 994 bytes
someone please tell me you know exactly what I need to do to fix it. THANKS!!!

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

Move Users from OCS 2007 R2 to New Lync 2013

I am trying to move users from OCS to Lync 2013 from within the Lync 2013 Control Panel and am getting an error that states "Cannot find Registrar pool. Verify that "FQDN of old pool" is a valid registrar pool.

Give this Lync powershell command a go:
Move-CsLegacyUser <user> -Target <Lync2013 Pool Name>
Move-CsLegacyUser -Identity "Pilar Ackerman" -Target "atl-cs-001.litwareinc.com"
Have you reviewed the OCS to 2013 migration documents?
http://technet.microsoft.com/en-us/library/jj205375.aspx
Did you add the OCS pool to the 2013 topology?
Have you visited Lync News lately? All of the latest Lync news, articles, and tips collected in one giant aggregator. http://lyncne.ws

Unable to start Lync 2013 FE service on one of the pooled server, error "The evaluation period for Microsoft Lync Server 2013 has expired"

Team,
Unable to start FE service on one of the FE server, 2 Enterprise lync 2013 pool one FE in each pool, only following error in event vrw,
Log Name: Lync Server
Source: LS Server
Date: 12/30/2013 12:10:55 PM
Event ID: 12290
Task Category: (1000)
Level: Error
Keywords: Classic
User: N/A
Computer: ACS465-BH102.me.ykgw.net
Description:
The evaluation period has expired.
The evaluation period for Microsoft Lync Server 2013 has expired. Please upgrade from the evaluation version to the fully licensed version of the product. Look at help for Setup.exe to learn how to upgrade from evaluation version to the licensed version.
Cause: The evaluation period for Microsoft Lync Server 2013 has expired.
Resolution:
Please upgrade from the evaluation version to the licensed version of the product. Look at help for Setup.exe to learn how to upgrade from evaluation version to the licensed version.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="LS Server" />
<EventID Qualifiers="50152">12290</EventID>
<Level>2</Level>
<Task>1000</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2013-12-30T09:10:55.000000000Z" />
<EventRecordID>73953</EventRecordID>
<Channel>Lync Server</Channel>
<Computer>ACS465-BH102.me.ykgw.net</Computer>
<Security />
</System>
<EventData>
</EventData>
</Event>
Log Name: System
Source: Schannel
Date: 12/30/2013 12:13:36 PM
Event ID: 36888
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: ACS465-BH102.me.ykgw.net
Description:
The following fatal alert was generated: 10. The internal error state is 1203.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Schannel" Guid="{1F678132-5938-4686-9FDC-C8FF68F15C85}" />
<EventID>36888</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2013-12-30T09:13:36.779033200Z" />
<EventRecordID>83985</EventRecordID>
<Correlation />
<Execution ProcessID="556" ThreadID="3668" />
<Channel>System</Channel>
<Computer>ACS465-BH102.me.ykgw.net</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="AlertDesc">10</Data>
<Data Name="ErrorState">1203</Data>
</EventData>
</Event>
Server is already on Full version, ran Reset-CsPoolRegistrarState
for fillrest as wel as serviceret
Followed below as well,
http://social.technet.microsoft.com/Forums/lync/en-US/2a7e27ce-2dea-4e37-91ea-1ed42e110198/issue-updating-from-eval-to-volume-licenses?forum=ocsplanningdeployment
Currently done failover to another pool and users can login,
however i cant get the front end service on this server.Any pointers would be appreciated.
Praveen | MCSE Messaging 2003

rit, the command is not doing the trick since its already full version,
PS C:\Users\lyncadmin> Get-CsServerVersion
Microsoft Lync Server 2013 (5.0.8308.0): Volume license key installed.
only one server in one pool, total two pools.
Lync 2013 is on Win 2008 R2, and the event in system im inclining to since i have tried all,
Log Name: System
Source: Schannel
Date: 12/30/2013 9:26:34 AM
Event ID: 36888
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: ACS465-BH102.me.ykgw.net
Description:
The following fatal alert was generated: 10. The internal error state is 1203.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Schannel" Guid="{1F678132-5938-4686-9FDC-C8FF68F15C85}" />
<EventID>36888</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2013-12-30T06:26:34.877077500Z" />
<EventRecordID>64911</EventRecordID>
<Correlation />
<Execution ProcessID="556" ThreadID="620" />
<Channel>System</Channel>
<Computer>ACS465-BH102.me.ykgw.net</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="AlertDesc">10</Data>
<Data Name="ErrorState">1203</Data>
</EventData>
</Event>
Praveen | MCSE Messaging 2003

Lync 2013 FE server certificate - different domain name

Hi,
I am implementing a small Lync infrastructure with the following components in a Resource Forest - Account Forest type implementation with a bi-directional Trust between the two forests:
1 x Lync 2013 FE Standard, 1 x Mediation server and 1 x Office Web App server
Both AD forests have their PKI CAs, the certificate on the FE server is signed by the CA from the Account domain. All servers and workstations have both Root certificates implemented.
User’s SIP domain name (account forest) is different from the FE server (resource forest) domain name.
Question: When internal users sign-in to Lync they get a warning prompt as follows:
“Lync cannot verify that the server is trusted for your sign-in address. Connect anyway?”
Users can select to connect and everything functions correctly, however, I would like to get rid of the warning message at the beginning.
Any idea what may be wrong, is something missing on the certificate ?
Thanks for your help,
Luca

You can try to edit the internal web services FQDN and ensure your other populated DNS records point to a FQDN that matches the sip domain, or use the TrustModelData workaround here:http://support.microsoft.com/kb/2833618
Here are a couple extra articles that dive in to what's happening: http://terenceluk.blogspot.com/2013/04/signing-into-lync-2013-client-presents.html?m=1
http://blogs.technet.com/b/jenstr/archive/2011/02/10/lync-cannot-verify-that-the-server-is-trusted-for-your-sign-in-address.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 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.

Need to generate a CSR for a new Lync 2013 Edge server

I am upgrading my Lync 2010 Edge to 2013. Part of the process is exporting all the certificates on the 2010, some public, and eventually importing them into my 2013 Edge. I have a problem with one certificate that was generated by our internal CA for the
2010 server itself named servername.domain.local. Since my new Edge will be renamed to the same name as the old Edge, I was planning on exporting this certificate but the private key can't be exported. The option is grayed out.
I need to therefore figure out how to get a certificate on my new Edge. No Lync software has been installed yet. What is the best way to generate a CSR so I can manually create a certificate on my internal CA. Since I don't have access to the internal CA
from the DMZ, I need to do it this way. I am thinking maybe the MMC but maybe Windows PowerShell? Once I get the CSR generated, I will figure out how to create a certificate on my internal CA.
I know I can do it during the Lync install but I wanted to have it ready on the server when installing.

The option is most likely grayed out, because the private key was not marked as exportable.
Now, you can either request the certificate by using the Deployment Tool and requesting the certificates, selecting offline and then manually copying the CSR to your Internal CA (and the certificate back)
Or you can use Powershell and do a Request-CsCertificate (see here: http://technet.microsoft.com/en-us/library/gg425723.aspx)
Try something like this: Request-CsCertificate -New -Type Internal -ComputerFqdn "lyncedge.domain.com" -FriendlyName "Internal Edge"
-Template jcila -PrivateKeyExportable $True -DomainName "edge.domain.com" -Output C:\path\test.req
If this helped you please click "Vote As Helpful" if it answered your question please click "Mark As Answer"
Georg Thomas | Lync MVP
Blog www.lynced.com.au | Twitter
@georgathomas
Lync Edge Port Check (Beta)
This forum post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Exchange server 2010 exchange server 2013 sp1 2 servers one domain

Scenario : Existing Server - Small Business Server 2011 with exchange 2010 \ Additional server on domain server 2012 r2 with exchange 2013 sp1 \ exchange 2013 sp1 installed on the second server but the exchange toolbox snap in fails, EAC login credentials
will not log on, and the shell tries to log onto the exchange 2013 with access denied error but then logs into the existing 2010 exchange server. Any suggestions on how to get these two installs of exchange to play nicely? reasoning is to eventually migrate
everything over to the new exchange.

Hi,
Based on my experience, here are some troubleshooting:
1. Check if all your Exchange 2013 services are working properly.
2. Check if the login account is a member of Exchange management group. You can try another admin account.
3. Check your event log and find if there is any error.
Thanks,
Angela Shi
TechNet Community Support

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"

Lync 2013 Clients in Child Domain Log "The server returned HTTP status code '403 (0x193)' with text 'Forbidden'."

Hey All, I am really stumped on this one.
Environment - Is using split DNS
Forest Root Domain - Contains new Lync 2013 Server Standard, ADDS, DNS, Enterprise CA, Workstations
Clients in this domain connect and work beautifully. No errors.
Child Domain - ADDS, DNS, Workstation, Lync 2013 client
Client autodiscovers, and then asks for a password. Enter the password and this comes up...
Can't sign in to Lync, You didnt get signed in, It might be your sign-in address or logon credentials.. blah blah blah"
Client log shows
Error:
There was an error communicating with the endpoint at 'https://domainlync13srv.Domain.net/WebTicket/WebTicketService.svc'.
The server returned HTTP status code '403 (0x193)' with text 'Forbidden'.
The server understood the request, but cannot fulfill it.
As far as i can tell certificates are correctly configured with all the SAN's possible in my forest. The user is correctly set up in Lync control panel. Autodiscovery seems to be working as it should. EWS is working correctly.
Repaired client, removed cached creds, has all lync 2013 updates no dice
Thank you all!

I am an IDIOT.
I did not prepare the child domain with the LYNC setup tool. Logged on to a file server in the child domain with domain admin rights and sure enough the setup said the domain was "partial". Ran the setup and bam it all started working.

Lync 2013 credentials problems on domain computers

Hi folks,
We are having trouble with Lync 2013 and credentials on our domain computers. We have been using Office 365 and Outlook for our email for a couple years and it has worked well enough, so recently we decided we wanted to start using Lync as well. We deployed
the Office 365 Pro Plus suite available to us through our Office 365 subscription and signed in. The first sign-in went as expected. It asked for a username and password, asks if it should remember those credentials for next sign-in (yes), then connects and
everything with Lync itself functioned normally. Subsequent sign-ins have not been normal.
When a user restarts their computer and launches Lync it remembers their user name but not their password. Once they type their password in it asks if it should remember those credentials for next sign-in again, then connects. If a user exits and re-launches
Lync without restarting it remembers their credentials and signs in properly, but then immediately a popup box appears saying that "Credentials are required" in order for Lync to get calendar information from Outlook ( http://i.imgur.com/hqcK426.png
We know the problem is only happening with computers on our domain, but we don't know why. I tested things out on my home desktop and network by installing Office 365 Pro Plus, setting up Outlook, and then Lync. Both Outlook and Lync auto-discovered everything
normally after getting my credentials and Lync behaves as expected every time the program launches. I then brought my personal laptop in and tried the same thing on my work network to see if it is network related, but Lync behaves normally on that computer
as well.
I originally worked on the problem at the Office 365 Community Forums ( http://community.office365.com/en-us/f/166/t/246014.aspx ), but after we isolated the problem to something with the domain computes I was told that they could not help me any further
and was referred here. Does anyone have any ideas as to what is keeping Lync from behaving properly on our domain computers? We have a mix of Windows 7 x64 and Windows 8.1 x64 computers, all joined to the same domain and with the same basic suite of software.
Thanks,
~Misharum
PS: How do I verify my account? The outlook.com email address has been verified, but I don't see anywhere to do verification in my TechNet profile here.

Yeah, the clients are fully patched. I put a support ticket in through Office 365 and the rep there was able to help me. It ended up being two separate problems.
Lync was not remembering my credentials to automatically log me in between restarts:
Installed the latest version of the Microsoft Online Services Sign-In Assistant.
After signing signing into Lync another popup appeared asking for credentials again to access calendar information. (two steps to solve this one).
In Active Directory Users and Computers, open up the properties of each affected user, go to the Attribute Editor tab, find and double click the proxyAddress attribute, and add in
sip:[email protected] where the userid is the user's login name and domain.com is your domain. I'd imagine this is scriptable in PowerShell but I don't know enough to do it.
Then on the computer that the users will be using, while the user is logged in, add a dword of NoDomainUser = 1 in the registry at HKCU\Software\Microsoft\Office\15.0\Common\Identity. The most sensible way to do this in my mind is with a group policy so
it will get written to each user's registry under their profile when they log in.
After doing all of this Lync remembered my credentials between restarts, signed me in automatically, and only gave that credentials popup on the first sign-in after applying both changes in step 2.

Lync 2013 federation failing for a specific domain

Hello,
We have recently migrated to Lync 2013 and noticed that one of the domains we federate with is unable to federate with us.
we are getting the following error:
Log Name: Lync Server Source: LS Protocol Stack Event ID: 14428 Task Category: (1001)
Level: Error Keywords: Classic User: N/A Computer: server.fqdn.com Description: TLS outgoing connection
failures.
Over the past 28 minutes, Lync Server has experienced TLS outgoing connection failures 4 time(s). The error code of the last failure is 0x80090325(SEC_E_UNTRUSTED_ROOT) while trying
to connect to the server "sip.example.com" at address [10.10.10.10:5061], and the display name in the peer certificate is "Unavailable". Cause: Most often a problem with the peer certificate or perhaps the host name (DNS) record used to
reach the peer server. Target principal name is incorrect means that the peer certificate does not contain the name that the local server used to connect. Certificate root not trusted error means that the peer certificate was issued by a remote CA that is
not trusted by the local machine. Resolution: Check that the address and port matches the FQDN used to connect, and that the peer certificate contains this FQDN somewhere in its subject or SAN fields. If the FQDN refers to a DNS load balanced pool then check
that all addresses returned by DNS refer to a server in the same pool. For untrusted root errors, ensure that the remote CA certificate chain is installed locally. If you have already installed the remote CA certificate chain, then try rebooting the local
machine.
Thanks

Thanks Michael.
That worked for one of two issues I'm seeing, I did use the same steps for the second issue but it didn't seem to work, I have imported the CA of the domain we would like to federate with to the trusted root certification authorities and the intermediate
certification authorities per the certificate issuer's website guidelines. I did learn that the federated partner is also using OCS 2007 R2, not sure if this may have to do with this.
Over the past 30 minutes, Lync Server has experienced TLS outgoing connection failures 1 time(s). The error code of the last failure is 0x80072746 while trying to connect to
the server "ocs.example.com" at address [10.10.10.10:5061], and the display name in the peer certificate is "ocs.example.com". Cause: Most often a problem with the peer certificate or perhaps the host name (DNS) record used to reach the peer server. Target
principal name is incorrect means that the peer certificate does not contain the name that the local server used to connect. Certificate root not trusted error means that the peer certificate was issued by a remote CA that is not trusted by the local machine.
Resolution: Check that the address and port matches the FQDN used to connect, and that the peer certificate contains this FQDN somewhere in its subject or SAN fields. If the FQDN refers to a DNS load balanced pool then check that all addresses returned by
DNS refer to a server in the same pool. For untrusted root errors, ensure that the remote CA certificate chain is installed locally. If you have already installed the remote CA certificate chain, then try rebooting the local machine.

Lync 2013 Deployment Requirements - One Server?

I have an organization that has an offsite Exchange Server 2010, and Windows Server 2008 R2 Domain Controller (for the Exchange Server).
I am trying to figure out what we need for hardware and Windows Server software to implement Lync 2013. I understand that Lync 2013 cannot be put on the same server as the Exchange Server. Can Lync 2013 be put on one Windows server?
Michael

Depends. Without knowing a lot about your environment (i.e users, HA requirements) ideally you'd have two. One as a Lync Standard Edition server (which can support up to 5000 users for Front End Services and Back-End database - but won't have HA) and one
as an Lync Edge server (for outside connectivity - also won't have HA)
Standard Edition will use SQL express as its database and automatically install it on the single server.
As for operating system Windows 2008 R2 or above.
As for hardware you can use this as a guide: http://technet.microsoft.com/en-us/library/gg398835.aspx and use the Lync Capacity planning tool http://www.microsoft.com/en-us/download/details.aspx?id=36828
How many users do you have? (for example the first link has 32GB as recommended memory for a Front End, but if you don't have many users you can use less than that - and the Cap Planner will reflect that)
If this helped you please click "Vote As Helpful" if it answered your question please click "Mark As Answer" | Blog
www.lynced.com.au | Twitter
@imlynced

LYNC 2013 generating Full Address book files but not the delta ones

Dear Experts,
I have noticed after I installed a new LYNC 2013 pool that the SQL share for address book is only showing F-xxxx for full downloads of address book but I am not seeing the D-xxx delta files which is causing my client not to receive the GALContactDelta file.
This new pool is an enterprise LYNC 2013 and I am currently testing to move from LYNC 2010. I have only one Address Book configuration policy and I did not create any new policy for the new pool/site. Any suggestions where to check the cause is appreciated.
Regards,
A. Zaher
A. Zaher

Hi,
If the address book contains over 50K entries, the client maintains a separate delta database GalContactsDelta.db and index GalContactsDelta.db.idx for GAL contacts, and periodically merges
updates into its main database GalContacts.db.
http://technet.microsoft.com/en-us/library/ee323492(v=office.13).aspx
Thanks,
Simon Wu
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!

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

Similar Messages

Maybe you are looking for