Ready to decommission our only Lync 2010 FE server

We are fully functional on Lync 2013 including our Edge server. I have a single Lync 2010 FE server I wish to remove. There are of course no users on it. We never used conferencing and no telephony at all. Just simple IM and presence. The 2010 server was
more of a proof of concept and just had our IT department as users.
The CMS was moved to 2013 a long time ago and I am at this point ready to remove the 2010 server completely. There are so many articles out there with way more detail than I need. I am thinking the steps are just this:
Verify no users, contacts devices etc... exist on the 2010 server
Delete the Conference directory on the 2010 server (No data because we never used conferencing)
Uninstall the CMS from the 2010 FE using the PS command
Uninstall-CsDatabase
-CentralManagementDatabase -SqlServerFqdn <FQDN of SQL Server>
-SqlInstanceName <Name of source server>
Remove the 2010 FE from Topology builder answering yes to removing the file share
Publish the Topology
Run setup.exe on the Lync 2010 to remove components (not sure about this step)
Done
I tried following some of the many documents out there but many don't mention the uninstall of the CMS on the legacy 2010 server and the MS documents go into exhaustive detail, much of which doesn't apply to me.
Lastly, I noticed in Topology builder there is the Lync 2010 SE FE server, an A/V Conferencing Pool and a Mediation Pool. Only the server itself can be deleted.
I am guessing when you delete the FE server, the other pools go away?

Working from bottom up.
Yes, deleting the server will remove the AV pool/mediation servers.
CMS SQL instance. There really isn't a reason or need to remove it. If the server is simply going to be turned off (deleted if VM) you can save yourself the work.
Same with setup. There isn't a real compelling reason to do this but you can if you like.
Lastly, if you are using conferencing on the 2013 servers, I would move your conference directory from 2010 to 2013. I've seen some really strange things happen in environments where people delete conference directories even when they thought no one
was using them. It doesn't hurt to have more than one conference directory and there are a laundry list of reasons to have multiples.
Thanks,
Richard
Richard Brynteson, Lync MVP | http://masteringlync.com | http://lyncvalidator.com

Similar Messages

Lync 2013 sql database on existing lync 2010 sql server

Dear All,
I have query regarding the SQL server requirement for Lync 2013 enterprise,when there is a co-existence or migration from lync 2010 to 2013, it it possible to use the same Lync 2010 enterprise sql server with different instance name or we have to create
a new sql server for lync 2013, please advice me.
Thanks and regards,
sarma kumar

No it is not possible. Topology builder won't allow it, it needs to be a completely different server name.
When you input the server into Topology builder you enter the server name and instance in two separate fields, it will give you a red X as soon as you try to put the server name in if it's already in the topology.
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 2010 Mediation Server Static Route

Has anyone used this method for allowing NON enterprise voice users the ability to utilize the conference call back feature?
http://www.confusedamused.com/notebook/lync-dial-in-conferencing-static-route-configuration/
If so, can you answer these questions? We have deployed this successfully but with a few hiccups.
When a non enterprise voice user uses the conference call back feature, the lync dial plans are ignored but the number is sent with a +1 in front of it. Is there a way for the CUCM to strip off that +1 and add a 9 to it? Whats the best way to accomplish this?
When the conference does call them back, the caller ID displays their Lync number. We would rather it display a different number. Is this possible? How could we accomplish this on the CUCM?
Thanks!

You can modify the trunk configuration using Lync Server 2013 Control Panel which were created using Lync Server 2010 Control Panel.
You can set different Pool Trunks, defining the different features for each trunk.
Lisa Zheng
TechNet Community Support

Lync 2013 MX (on windows rt) will not connect to Lync 2010 enterprise server

Both internal and external (through edge) will not connect. I will put in the SIP address, try to connect and it will ask for the logon credentials (domain is different from SIP domain) A minute later it will state that it was unable to sign on. When I enable
logs I get a massive log file (~etl.bak) that is garbled and snooper will not read.
I have had no problem signing in users with Lync for the ipad, windows phone, or android devices. Does anyone know a way to troubleshoot this further?

Make sure you use the following to log on
SIP Address : [email protected]
Account : Domain\user
- Belgian Unified Communications Community : http://www.pro-lync.be - MCM/MVP/MCT
Tried all the combinations, but I heard a rumor that the company has messed-up or incomplete DNS entries and won't fix it. On the Lync desktop versions I can work around this by using advanced connection settings (which don't exist on the WinRT/Store
app) to specify manual internal and external names.
Also tried entering sip.company.com and sipexternal.company.com in hosts file but that doesn't work either. that was suggested elsewhere as a fallback mechanism, but it doesn't seem to work when potentially invalid SRV entries already exist.
What I really need is for Microsoft to support the advanced connection settings, there's no other way around that.
Two questions:
1) Anyone know how to get access to the logging information which is enabled in the options of the Windows Store app? It's a long shot but maybe I can find somebody in this big company who will want to correct it.
2) Do we use the usual MS Connect to make bug/feature requests for the store apps too? For many years now a lot of products have been missing from there in favor of other feedback systems like User Voice (e.g. Windows Phone and Visual Studio). So you never
know exactly which is the right place to report such stuff nowadays (shame because Connect seemed like a universal solution at the start).
Key Artefacts

LYNC 2010 Edge server deployment issues

I've been able to install LYNC and have the meet and dialin function working properly internal/external. I'm attempting to test setting up external access to the client with an edge server. All seems to install properly etc with no errors being thrown my
way. But in the services i have a few that will not start with the below errors. Can anyone point me to a deployment scenario with an edge server how-to?
Any help would be greatly appreciated.
The Lync Server Access Edge service terminated with service-specific error %%-1008124918.
The Lync Server Web Conferencing Edge service terminated with the following error:
The requested address is not valid in its context.

Hi every body, I am trying to do a
proof of concept before we buy the public Certificate for my Edge server but I have this error..
I have the same error as you guys (1008124918 )
Here is my setup
Active directory with a CA on it. ( I used this CA for my Front-End, and for both Internal/External Edge Certificate )
FrontEnd ;
-In the domain
-192.168.16.55 255.255.255.0
==
Edge:
Inside NIC : 192.168.16.57 255.255.255.0, no gateway
Outside NIC (dmz ) : 192.168.18.80 255.255.255.0 . Gateway 192.168.18.0
The edge is not in the domain.
==
My Public IP : 69.70.xx.xx
=====================
In the wizzard for the edge-pool
I choose:
-Single computer pool
I check :
- Use a single FQDN & IP
-Enable federation ( port 5061 )
-The external IP address of this edge pool is translated by Nat
external fqdn : sip.OurCie.com / 5061 Port
Internal IP : 192.168.16.57
External IP ( for sip access, web conf, A/V Edge services ) : 192.168.18.80
Public IP used by nat : 69.70.xx.xx
=====================
So when I start the service I have this error code : Windows could not start the Lync Server Access Edge....code : 1008124918
in the eventvwr here is ther error that I have :
Transport TLS has failed to start on local ip : 69.70.xx.xx at port 5061
cause: config error, low system ressources or another proram is using this port
can also happen if the ip address has become invalid
Any idea ?

WHILE INSTALLING LYNC 2010 IN SERVER 2008 R2 AND NOT SHOWING COMPLETE OPTION AFTER FINISH

hmmm

Hi,
Please make sure you’re logged onto the server with a domain user account that’s both a local administrator and
a member of the RTCUniversalReadOnlyAdmin group.
Best regards,
Eric

For Your Consideration: Ultimate Lync 2010 client install with SCCM 2007

While the subject of my post may be very presumptuous, I submit the following for your consideration to answer the often-asked question about how to deploy Lync 2010 client with SCCM.
Background:
I cannot understand why Microsoft made the Lync install so darned confusing, complex, and convoluted.
After our Lync 2010 FE server was up and running and all users migrated off our OCS server to the Lync environment, I spent about a month and a half trying to figure out how to:
1. Uninstall the OCS 2007 R2 client
2. Install all prerequisites for the Lync client
3. Install Lync on all user workstations silently.
While researching this, the simple answer I kept seeing given to this question was, "just use the .exe with the right switches according to the TechNet article here: http://technet.microsoft.com/en-us/library/gg425733.aspx". Well, my response is, I
tried that and while the program installed itself correctly pushed through SCCM, because I was doing it using an administrative account (i.e. the SYSTEM account) due to our users not having admin rights, when the install was done, Lync would automatically
start up, but in the SYSTEM context so that the user couldn't see it was running, they go to run it and it won't run for them. I was unable to find any switch or option to prevent the automatic launch. I suppose the simple solution to that would
be to have the user reboot, but that's unnecessarily disruptive and was contrary to the desire to make this a silent install.
The next simplest answer I saw was, "extract the MSI and use that with the right switches". Problem with that is that the MSI by itself doesn't remove the OCS client or install the prerequisites, and also either requires a registry change to even allow
the MSI to be used or a hacked MSI that bypasses the registry key check. I tried to put a package together to uninstall OCS, install the prereqs, and use a hacked MSI, but I never could get the MSI hacked properly. The other problem I ran into
was detecting if the OCS client was running in a predictable way so I could terminate it, properly uninstall it, and then do the rest of the installations. It was this problem that ultimately led me to the solution that I'm about to detail and that has
worked marvellously for us.
Solution:
As I said before, when I first looked at this problem, I started by building a typical software deployment package (Computer Management -> Software Distribution -> Packages) and then created the programs to do the install. My first attempt was
just with the .exe file provided as-is by Microsoft using the switches they document in the link above for IT-Managed Installation of Lync, and...well, the end result wasn't quite as desirable as hoped. So, my next attempt was to extract all the prerequisite
files and the Lync install MSI (both for x86 and x64), attempt to hack it to get around the "UseMSIForLyncInstallation" registry key, and make the command-lines to terminate OCS and uninstall it.
In the past when I had an install to do with SCCM that also required uninstalling an older version of a given application, I typically used the program-chaining technique. That's where you have, for example, 3 or more programs that run in a package
in a sequence and you have Program 3 be set to run after Program 2 does and then set Program 2 to run after Program 1 so you get the desired sequence of Programs 1-2-3 running in that order. So, I created programs to 1) kill Communicator.exe 2) uninstall
Communicator 2007 R2 by doing an "msiexec /uninstall {GUID}" 3) install Silverlight 4) install Visual C++ x86 5) optionally install Visual C++ x64, and then 6) install the Lync x86 or x64 client. That final step was always the point of failure because
I couldn't get the hacked MSI for the Lync Client install to work. I also realized that if Communicator wasn't running when the deployment started, that step would fail and cause the whole process to bail out with an error. That's one of the downsides
of program-chaining, if one step fails, SCCM completely bails on the deployment. This is what also led me to the key to my solution: TASK SEQUENCES.
I'm not sure how many people out there look in the "Operating System Deployment" area of SCCM 2007 where Task Sequences normally live, but I also wonder how many people realize that Task Sequences can be used for more than just Operating System deployments.
One of the biggest advantages of a task sequence is you can set a step to ignore an error condition, such as if you try to terminate a process that isn't running. Another advantage is that task sequences have some very good built-in conditionals that
you can apply to steps, for example, having the sequence skip a step if a certain application (or specific version of an application) is not installed on the machine. Both of those advantages factor highly into my solution.
OK, for those who already think this is "TL;DR", here's the step-by-step of how to do this:
First, you need to extract all the files from the LyncSetup.exe for your needed architectures. We have a mix of Windows XP and Windows 7 64-bit, so my solution here will take both possibilities into account. To extract the files, just start up
the .exe like you're going to install it, but then when the first dialog comes up, navigate to "%programfiles%\OCSetup" and copy everything there to a new location. The main files you need are: Silverlight.exe, vcredist.exe (the x64 LyncSetup.exe includes
both x86 and x64 Visual C++ runtimes, you need them both, just rename them to differentiate), and Lync.msi (this also comes in an x86 and x64 flavor, so if you have a mix of architectures in your environment, get both and either put them into their own directories
or rename them to reflect the architecture).
For my setup, I extracted the files for the x86 and x64 clients and just dumped them each into directories named after the architectures.
Next, move these files into a directory to your SCCM file server, whatever it might be that you deploy from, in our case, it was just another volume on our central site server. Go to the SCCM console into Computer Management -> Software Distribution
-> Packages and then create a new package, call it something meaningful, and then point to the directory on your SCCM file server for the source files.
Now you need to create 3 to 5 programs inside the package:
1. Name: Silverlight
   Command Line: x86\Silverlight.exe /q     (remember, inside my main Lync install folder on my distribution point, I have an x86 directory for the files from the x86 installer and an x64 folder for the files from the x64 installer.
The fact is the Silverlight installer is the same in both, so you only need one of them.)
   On the Environment tab: Program can run whether or not a user is logged in, runs with administrative rights, Runs with UNC name
   On the Advanced tab: Suppress program notifications
   All other options leave default.
2. Name: Visual C++ x86
    Command Line: x86\vcredist_x86.exe /q
   On the Requirements tab: Click the radio button next to "This program can run only on specified client platforms:" and then check off the desired x86 clients.
   Environment and Advanced tabs: same as Silverlight
   (If you have only x64 clients in your environment, change all x86 references to x64. If you have a mixed environment, create another program identical to this one, replacing references to x86 with x64.)
3. Name: Lync x86
    Command Line: msiexec /qn /i x86\Lync.msi OCSETUPDIR="C:\Program Files\Microsoft Lync" (The OCSETUPDIR fixes the issue with the Lync client wanting to "reinstall" itself every time it starts up)
    Requirements, Environment, and Advanced tabs: Same as with Visual C++ and Silverlight
    (Same deal as above if you have all x64 clients or a mix, either change this program to reflect or make a second program if necessary)
Now you need to make the Task Sequence. Go to Computer Management -> Operating System Deployment -> Task Sequences. Under the Actions pane, click New -> Task Sequence. In the Create a New Task Sequence dialog, choose "create a
new custom task sequence", Next, enter a meaningful name for the task sequence like "Install Microsoft Lync", Next, Next, Close.
The task sequence will have up to 12 steps in it. I'll break the steps down into 3 phases, the prereqs phase, uninstall OCS phase, and then Lync install phase.
Prereqs Phase:
These are the easiest of the steps to do. Highlight the task sequence and then in the Actions pane, click Edit.
1. Click Add -> General -> Install Software. Name: "Install Microsoft Silverlight". Select "Install a single application", browse to the Lync package created earlier and then select the Silverlight program.
2. Add -> General -> Install Software. Name: "Install Microsoft Visual C++ 2008 x86". Install Single Application, browse to the Lync package, select the Visual C++ x86 package.
As before, if you're an all-x64 environment, replace the x86 references with x64. If you have a mixed environment, repeat step 2, replacing x86 with x64.
3. Add -> General -> Run Command Line. Name: "Enable Lync Installation". This step gets around the UseMSIForLyncInstallation registry requirement. The Lync client MSI simply looks for the presence of this key when it runs, so
we'll inject it into the registry now and it doesn't require a reboot or anything. It just has to be there before the client MSI starts.
Command Line: reg add "hklm\Software\Policies\Microsoft\Communicator" /v UseMSIForLyncInstallation /t REG_DWORD /d 1 /f
Uninstall OCS Phase:
This part consists of up to 6 Run Command Line steps. (Add -> General -> Run Command Line)
4. Name: "Terminate Communicator". Command Line: "taskkill /f /im communicator.exe". On the Options page, check the box next to "Continue on error". This will terminate the Communicator process if it's running, and if it's not, it'll
ignore the error.
5. Name: "Terminate Outlook". Command Line: "taskkill /f /im OUTLOOK.exe". Check the "Continue on error" on the Options page here too. Communicator 2007 hooks into Outlook, so if you don't kill Outlook, it might prompt for a reboot
because components are in use.
(NOTE: If necessary, you could also add another step that terminates Internet Explorer because Communicator does hook into IE and without killing IE, it might require a restart after uninstalling Communicator in the next steps. I didn't run into
this in my environment, though. Just repeat step 5, but replace OUTLOOK.EXE with IEXPLORE.EXE)
6. Name: "Uninstall Microsoft Office Communicator 2007". Command Line: "msiexec.exe /qn /uninstall {E5BA0430-919F-46DD-B656-0796F8A5ADFF} /norestart" On the Options page: Add Condition -> Installed Software -> Browse to the
Office Communicator 2007 non-R2 MSI -> select "Match this specific product (Product Code and Upgrade Code)".
7. Name: "Uninstall Microsoft Office Communicator 2007 R2". Command Line: "msiexec.exe /qn /uninstall {0D1CBBB9-F4A8-45B6-95E7-202BA61D7AF4} /norestart". On the Options page: Add Condition -> Installed Software ->
Browse to the Office Communicator 2007 R2 MSI -> select "Match any version of this product (Upgrade Code Only)".
SIDEBAR
OK, I need to stop here and explain steps 6 and 7 in more detail because it was a gotcha that bit me after I'd already started deploying Lync with this task sequence. I found out after I'd been deploying for a while that a tech in one of our remote
offices was reinstalling machines and putting the Communicator 2007 non-R2 client on instead of the R2 client, and my task sequence was expecting R2, mostly because I thought we didn't have any non-R2 clients out there. So, at first I just had our Help
Desk people do those installs manually, but later on decided to add support for this possibility into my task sequence. Now, when you normally uninstall something with msiexec, you would use the Product Code GUID in the command, as you see in steps 6
and 7. All applications have a Product Code that's unique to a specific version of an application, but applications also have an Upgrade Code GUID that is unique for an application but common across versions. This is part of how Windows knows that
Application X version 1.2 is an upgrade to Application X version 1.1, i.e. Application X would have a common Upgrade Code, but the Product Code would differ between versions 1.1 and 1.2.
The complication comes in that Communicator 2007 and Communicator 2007 R2 have a common Upgrade Code, but different Product Codes and the "MSIEXEC /uninstall" command uses the Product Code, not the Upgrade Code. This means that if I didn't have step
6 to catch the non-R2 clients, step 7 would be fine for the R2 clients, but fail on non-R2 clients because the Product Code in the MSIEXEC command would be wrong. Luckily, we only had one version of the non-R2 client to deal with versus 4 or 5 versions
of the R2 client. So, I put the command to remove Communicator 2007 non-R2 first and checked for that specific product and version on the machine. If it was present, it uninstalled it and then skipped over the R2 step. If non-R2 was not present,
it skipped that step and instead uninstalled any version of the R2 client. It's important that steps 6 and 7 are in the order they are because if you swap them, then you'd have the same outcome as if step 6 wasn't there. What if neither is on the
machine? Well the collection this was targeted to included only machines with any version of Communicator 2007 installed, so this was not a problem. It was assumed that the machines had some version of Communicator on them.
8. Name: "Uninstall Conferencing Add-In for Outlook". Command Line: "msiexec.exe /qn /uninstall {730000A1-6206-4597-966F-953827FC40F7} /norestart". Check the "Continue on error" on the Options Page and then Add Condition ->
Installed Software -> Browse to the MSI for this optional component and set it to match any version of the product. If you don't use this in your environment, you can omit this step.
9. Name: "Uninstall Live Meeting 2007". Command Line: "msiexec.exe /qn /uninstall {69CEBEF8-52AA-4436-A3C9-684AF57B0307} /norestart". Check the "Continue on error" on the Options Page and then Add Condition -> Installed Software
-> Browse to the MSI for this optional component and set it to match any version of the product. If you don't use this in your environment, you can omit this step.
Install Lync phase:
Now, finally the main event, and it's pretty simple:
10. Click Add -> General -> Install Software. Name: "Install Microsoft Lync 2010 x86". Select "Install a single application", browse to the Lync package created earlier and then select the "Lync x86" program. As before, if you
only have x64 in your environment, replace the x86 with x64, or if you have a mixed environment, copy this step, replacing x86 references with x64.
And the task sequence is done! The final thing you need to do now is highlight the task, click Advertise in the Actions pane, and deploy it to a collection like you would with any other software distribution advertisement. Go get a beer!
Some final notes to keep in mind:
1. You can't make a task sequence totally silent...easily. Users will get balloon notifications that an application is available to install. The notifications cannot be suppressed through the GUI. I've found scripts that supposedly
hack the advertisement to make it be silent, but neither of them worked for me. It was OK, though because in the end we wanted users, especially laptop users, to be able to pick a convenient time to do the upgrade. The task sequence will appear
in the "Add/Remove Programs" or "Programs and Features" Control Panel. You can still do mandatory assignments to force the install to happen, you just can't make it totally silent. On the plus side, the user shouldn't have to reboot at any point
during or after the install!
2. In the advertisement setup, you can optionally show the task sequence progress. I've configured the individual installs in this process to be silent, however, I did show the user the task sequence progress. This means instead of seeing
5 or 6 Installer windows pop up and go away, the user will have a single progress bar with the name of the step that is executing.
3. One step that I didn't consider when I actually did this was starting the Lync client as the user when the install was complete. The user either had to start the client manually or just let it start on its own at the next logon. However,
while I was writing this, I realized that I could possibly start the client after installing by making another Program in the Lync Package with a command line that was along the lines of "%programfiles%\Microsoft Lync\communicator.exe" and then in the Environment
tab, set it to "Run with user's rights" "only when a user is logged on".
4. My first revision of this task sequence has the Prereqs phase happening after the OCS uninstall phase, but I kept running into problems where the Silverlight installer would throw some bizarre error that it couldn't open a window or something wacky
and it would fail. Problem was, I couldn't re-run the task sequence because now it would fail because OCS had been uninstalled, so that's why the Prereqs happen first. It ran much more reliably this way.
5. For some reason that baffles me, when I'd check the logs on the Site Server to monitor the deployment, I'd frequently see situations where the task sequence would start on a given machine, complete successfully, almost immediately start again, and
then fail. I'm not sure what is causing that, but I suspect either users are going to Add/Remove Programs and double-clicking the Add button to start the install instead of just single-clicking it, or the notification that they have software to install
doesn't go away immediately or Lync doesn't start up right after the install, so they think the first time it didn't take and try it a second time.
I hope this helps some of you SCCM and Lync admins out there!

On Step 8 I found multiple product codes for the Conferencing Add-In for Outlook. Here's a list of the ones I found in the machines on my network:
{987CAEDE-EB67-4D5A-B0C0-AE0640A17B5F}
{2BB9B2F5-79E7-4220-B903-22E849100547}
{13BEAC7C-69C1-4A9E-89A3-D5F311DE2B69}
{C5586971-E3A9-432A-93B7-D1D0EF076764}
I'm sure there's others one, just be mindful that this add-in will have numerous product codes.

Uninstalling CMS from Lync 2010

Now that the CMS has been migrated to our Lync 2013 FE servers, I need to remove the replica from our single Lync 2010 server using
Uninstall-CsDatabase -CentralManagementDatabase -SqlServerFqdn <FQDN of SQL Server> -SqlInstanceName <Name of source server>
We plan on keeping the Lync 2010 server around for a bit even though there are no users on it. I have a single Trusted App for webmail integration still attached to the Lync 2010 server which I plan to move to 2013 sometime in the future. Our
Edge is still 2010.
Question is by removing the CMS replica from the Lync 2010 server, will this interfere with operation of the Edge server? All I am doing is removing CMS replica which is something you are supposed to do after moving CMS to 2013 but I am not sure where the
Edge is currently pulling its replica data from. Since the Edge has access to all internal FE servers I assume that if its getting changes from the 2010 FE and I remove that replica, it will get changes going forward from the 2013 FE. Is there any way
to see the Lync FE replication partners so I can verify this?
Eventually, we will build out a 2013 Edge and at that time decommission the 2010 completely. Its a very simple environment. Just IM and presence. No telephony, monitoring or archiving.

You can 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.
Lisa Zheng
TechNet Community Support

Lync 2013 Cumulative Update and Lync 2010 CM database ??

I was going through the update process for our new Lync 2013 Enterprise install, I just have a FE server up at this point. I ran the LyncServerUpdateInstaller and it ran fine. I then ran through the Backend SQL updates, and of course I
get to the end and read...
Note In a coexistence environment that contains both Lync Server 2010 and Lync Server 2013 in which the Central Management Service is located on a Lync Server 2010 pool, do not run the
Install-CsDatabase -CentralManagementDatabase cmdlet. If you later move the Central Management Service to a Lync Server 2013 pool, you have to run the
Install-CsDatabase -CentralManagementDatabase cmdlet to apply the changes.
And yes we have a Lync 2010 Standard server running and the CM DB is on the Lync 2010 pool. I haven't noticed any problems yet, Do I need to be concerned about this? And if so how do I fix it? I only have a test account on the Lync
2013 server at this point. So I could uninstall if needed.
Thanks,
Matt

Hi,
As I know, it better to move the Central Management Store from Lync server 2013 database back to Lync server 2010 database firstly. Then if needed, you can uninstall the Lync server 2013 database.
You can refer to the link below:
http://cmcgreanor.wordpress.com/2012/07/24/move-lync-central-management-store-and-front-end-servers-to-a-new-lync-pool-with-a-new-sql-backend/
Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make
sure that you completely understand the risk before retrieving any suggestions from the above link.
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

Microsoft Lync 2010 continuously asks for credentials after signing in

Hi,
we have lync 2010 frontend server at our office, it is working fine for the all the users, but one user who will connect our network through VPN it will continuously prompts for credentials eventhough if we are providing right credentials, because of this
user will be not able to recieve emails from his outlook. all other VPN users working fine. how to troubleshoot this issue, please any help?
Regards
Asha

Hi,
The issue may occur if the Outlook integration is not correctly on this client after connecting through VPN. What is the
difference for the location or sign in type between this user and other working users?
Lync generally only prompts you for credentials after you are logged in when it must connect Lync to a linked service such as the Microsoft Exchange Free/Busy service or the Calendar service.
If Lync continues to ask for credentials after three separate dialog prompts, there is likely an issue with Outlook integration or with the Exchange services themselves. I suggest referring to the following information to check the issue.
http://support.microsoft.com/kb/2298541
http://support.microsoft.com/kb/2436962
Regards,
Kent

Lync 2010 PIC (Skype) Connectivity

Hi all,
we are using a Lync 2010 Standard Server, means all functions are installed on one single machine. So far we have no problems with this environment means IM is working internal and external also mobile devices can connect and use IM.
I've started the provisoning process some weeks ago and activated all federation options within lync. Just did everything i found on different guides/blogs.
But now the public federation (i'm testing with Skype) doesnt work at all. I cant see the presence neither i'm able to write messages.
I can add Lync contact for my domain on Skype which means the provisioning seems to be fine. But the presence is unknown.
So now i dont know where to start with troubleshooting. I would really appreciate some hints on how to find out what the problem is.
Best Regards
Daniel

Hi,
You can deploy only one Edge server for external access, federation with others (including with Skype).
Please check if you have deactivated the Federation on Lync Topology. If yes, enable it and test again.
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

Lync 2010 Edge Certificate Assigning issue.

Hello,
We are facing issue in assigning Public certificate for Lync 2010 Edge server.
Where as i able to successfully import the certificate from Deployment wizard, but when assigning the same not able to view the certificate which is successfully imported from same wizard.
Please suggest to fix this issue.
FYI: I am able to view the certificate in the Local account certificate container.

Try importing the certificate using the DigiCert's Certificate Utility: https://www.digicert.com/util/
works for certificates issued by other Certificate Authorities.
After the cert is Imported, run the key test from the DigiCert's Certificate Utility. Run Step 3 again (Lync Server Deployment Wizard) and select "assign" to use the new certificate.
Please mark posts as answers/helpful if it answers your question.
Blog
Lync Validator - Used to assist in the validation and documentation of Lync Server 2013.

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

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

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

Replication issue between lync 2010 FE and lync 2013 FE

Hello
I face any issue in my lync server's .
I was in the last steps in the migration process from lync 2010 to 2013 enterprise edition .
where CMS was moved already to 2013 , and later on many time I checked the replication and it was fine , then I deleted the CMS DB FROM 2010 FE and I checked the replication and it was fine .
later on I proceed to delete the archiving server and monitoring server and it was fine .
later on I proceed to
Reset call admission control
Prevent sessions for services
Stop Lync Server 2010 services
Remove a Front End Server from a pool
I just I face this replication issue after I start the process to delete the lync 2010 pool which im stuck on it now .
one more thing while I was trying to delete the 2010 front end pool , I got the error .
Error: An error occurred: "System.InvalidOperationException" "Cannot publish topology changes. Conference directories still exist on a pool that would be deleted. Remove the conference directories before continuing."
so I moved the conference directories from 2010 pool to the 2013 pool successfully.
but later on when I check the replication I notice the replication issue ?
Get-CsManagementStoreReplicationStatus
UpToDate           : False         """""""""""""""""""it is already shutdown
ReplicaFqdn        : HQ-EDGE01.mydom
LastStatusReport   :
LastUpdateCreation : 3/23/2015 11:22:17 AM
ProductVersion     :
UpToDate           : True
ReplicaFqdn        : HQ-LYNC2013-FE.mydom
LastStatusReport   : 3/19/2015 5:21:27 PM
LastUpdateCreation : 3/19/2015 5:21:25 PM
ProductVersion     : 5.0.8308.556
UpToDate           : False
ReplicaFqdn        : HQ-LYNC-FE-01.mydom
LastStatusReport   : 3/19/2015 11:38:25 AM
LastUpdateCreation : 3/23/2015 11:52:17 AM
ProductVersion     : 4.0.7577.0
then I run the
I run Invoke-CsManagementStoreReplication
Get-CsManagementStoreReplicationStatus
UpToDate           : False     """""""""""""""""""it is already shutdown """"""""""""""""""
ReplicaFqdn        : HQ-EDGE01.mydomain
LastStatusReport   :
LastUpdateCreation : 3/23/2015 10:18:22 PM
ProductVersion     :
UpToDate           : True
ReplicaFqdn        : HQ-LYNC2013-FE.mydomain
LastStatusReport   : 3/23/2015 10:18:26 PM
LastUpdateCreation : 3/23/2015 10:18:22 PM
ProductVersion     : 5.0.8308.556
UpToDate           : False
ReplicaFqdn        : HQ-LYNC-FE-01.mydomain
LastStatusReport   : 3/19/2015 11:38:25 AM
LastUpdateCreation : 3/23/2015 10:18:22 PM
ProductVersion     : 4.0.7577.0
====================
Get-CsManagementStoreReplicationStatus
UpToDate           : False """"""""""""""" it is already down """""""""""""""""""""
ReplicaFqdn        : HQ-EDGE01.mydomain
LastStatusReport   :
LastUpdateCreation : 3/23/2015 10:53:23 PM
ProductVersion     :
UpToDate           : True
ReplicaFqdn        : HQ-LYNC2013-FE.mydomain
LastStatusReport   : 3/23/2015 10:18:26 PM
LastUpdateCreation : 3/23/2015 10:18:22 PM
ProductVersion     : 5.0.8308.556
UpToDate           : False
ReplicaFqdn        : HQ-LYNC-FE-01.mydomain
LastStatusReport   : 3/19/2015 11:38:25 AM
LastUpdateCreation : 3/23/2015 10:53:23 PM
ProductVersion     : 4.0.7577.0
why LastUpdateCreation : 3/23/2015 10:53:23 PM from the lync 2010 pool ????
I'm not doing any change on 2010 pool now (I just try to delete it ) , all the change it is on 2013 pool .
for edge server 2013 I shut down the server since there is another configuration issue there (so replication to edge server not the issue now since it is down).
my question is this will affect my lync 2013 since it is the production now ? is this un completed steps for removing the 2010 pool affect my production.
is the replication issue affects my 2013 pool ?
Kind Regards
MK

Hi,
From your description above, did you mean before deleting the Lync Server 2010 Pool from topology, you found the replication of Lync 2010 FE Server not update to date?
If it is the case, based on my knowledge, there is no affect for Lync Server 2013 Pool. Please double check if Lync Server 2013 Pool work normally, and Lync users in Lync 2013 Pool can use all Lync function without issues. Then you can delete Lync 2010 Pool
from Topology and publish it. After finish it, please re-run step 2 on Lync Server 2013 FE Servers.
Best Regards,
Eason Huang
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Eason Huang
TechNet Community Support

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

Ready to decommission our only Lync 2010 FE server

Similar Messages

Maybe you are looking for