Lync 2013 standard deployment: Exchange 2010 Sharepoint 2010 and outlook 2007 collaboration

HI
I have Exchange 2010 and sharepoint 2010 with all our user using outlook 2007. what options do I have for collaborations between these systems if I was to install Lync 2013. I have seen posts that mention that you cannot use outlook 2007 and lync 2013 and
that you would be better off installing the lync 2010 client?
1. would we be covered from a licensing point of view if we had bought lync 2013 cals but install the lync 2010 software on desktops?
2. what Cals do we require for presence to be available in SharePoint we currently have standard sharepoint cals?
3. what new features will we loose if we install 2010 lync software.
4. if our mobile users use the 2013 lync software will these be able to communicate with the 2010 users?
thanks
J

Hi,
If you use Lync 2013 client with Outlook, multiple functions will not be achieved, such as: customize Outlook meeting invitations (add logo, help URL, disclaimer, footer text), in Outlook, configure meeting option to mute attendee audio and video by default,
presence status in the Microsoft Outlook To and Cc fields, and so on. As Lync 2013 is the part of Office 2013, the best choice is using Outlook 2013.
More details:
https://technet.microsoft.com/en-us/library/gg412817.aspx
For the CAL requirement, you can refer to following link:
Lync Licensing Guide
You can refer to the link below of “What’s new for clients in Lync Server 2013” to understand the new features for Lync 2013:
https://technet.microsoft.com/en-us/library/jj204933.aspx
If you use Lync 2013 mobile clients, you can communicate with 2010 users with no possible.
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

Similar Messages

Lync 2013 - Presence not showing in SharePoint 2010

Hello,
Presence was showing while on Lync 2010 and Office 2010 but at some point we lost the jellybean presence.
We recently upgraded to Lync 2013 and O365. Yet our SharePoint 2010 libraries are no longer showing the presence next to Modifiied By or Created By.
I've checked CA and presence is enabled. AcriveX add-in ia as well.
Thank you,
Andrea

Hi,
Did the Lync Server 2013 install On-Premises or online?
If it is On-Premises deployment, Presence is displayed by using an ActiveX® control and Lync APIs.
Please check if the Office to be the Latest version, if not, update it and test again.
If it is Lync online, you can also post a question on Office365 forum for assistance. Thank you for your understanding.
http://community.office365.com/en-us/forums/163/categories.aspx
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

Lync Server 2013 Standard Deployment: Cannot Open Service Control Manager...

Hi
thanks for any advice.I've just install Lync 2013 Standard as the steps in Technet,When I publish the topology,meet the error as listed.
****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.XdsDatabase'****
Initializing DbSetupBase
Parsing parameters...
Found Parameter: SqlServer Value lync2012ek.ek2012.net\rtc.
Found Parameter: SqlFilePath Value C:\Program Files\Common Files\Microsoft Lync Server 2013\DbSetup.
Found Parameter: Publisheracct Value EK2012\RTCUniversalServerAdmins.
Found Parameter: Replicatoracct Value EK2012\RTCUniversalConfigReplicator.
Found Parameter: Consumeracct EK2012\RTCUniversalReadOnlyAdmins.
Found Parameter: Role Value master.
Trying to connect to Sql Server lync2012ek.ek2012.net\rtc. using windows authentication...
Exception Stack:
Type: System.InvalidOperationException, Message: Cannot open Service Control Manager on computer 'lync2012ek.ek2012.net'. This operation might require other privileges.
Type: System.ComponentModel.Win32Exception, Message: Access is denied.
best regards,
George
George Guo

please verify your computer name while you creating FQDN pool FQDN of Server name
example
computer name
is server1
domain name is abc.ae
so,
your FQDN pool name will be server1.abc.ae
problem solved :)

Certificate Requirement for Lync 2013 Standard Edition

I have successfully run the setup of lync 2013 standard edition now I am stuck due to certificates required for lync 2013. when I generate a csr. it show the subjected urls for that.
hostname.domain.com
sip.domain.com
diali.domain.com
meet.domain.com
admin.domain.com
lyncdiscover.domain.com
lyncdiscoverinternal.domain.com
im.domain.com (External URL)
so if I go for 3 party CA then I need 8 certicate only for internal lync. As I also need to connected federated partner and external user so I need Edge for again I need 3 more certificates
web.domain.com
a/v.domain.com
sip.domain.com
now when I go for these certificate it quit costly and I didn't understand why such certifcates required. can anyone help me to fix such requirement.
Or, what are the necessary url to which I buy 3 party CA rest leave as it is.
I also want to deploy Edge with single adopter as we have only one network so can anyone assist me to proceed it further.
Talha Faraz Malik

To save on the cost of your third party certificates, I would deploy an internal certificate authority to sign certificates for your internal front end. For your third party certificate, you would only need the SANs for the edge and for your
reverse proxy and as Edwin said, this can be a single cert with multiple SANs.
For example, for your edge you would need:
sip.domain.com
web.domain.com
You would not need A/V as this role does not require a SAN on your certificate. On the same certificate, which you could also use on your reverse proxy, you'd likely want the following FQDNs.
lyncdiscover.domain.com
im.domain.com (your external web services FQDN)
meet.domain.com
dialin.domain.com
You may also want to consider your internal web services FQDN and include the following so third party mobile devices can connect without needing a certificate installed:
im_internal.domain.com (your internal web services FQDN)
lyncdiscoverinternal.domain.com
I'm sure that's not entirely clear yet, so feel free to ask more questions or what the purpose of each is.
When you say Edge with a single adapter, you mean a single adapter in a DMZ or internal? You definably want two NICS, both in separate DMZs, but I've managed to get the edge working with a single adapter in a DMZ before. What you don't want is
the edge in your internal network.
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.

Lync 2013- Standard Edition - Persistent Chat

What is the capacity of the Persistent Chat if it is collocated on Lync 2013 Standard edition front end ?
ie, number of chat rooms /usage?
In a Lync 2013 standard edition deployment if Persistent Chat is on separate server, can the SQL be offloaded to central SQL cluster enviornment or it will be held on the local server?

I haven't seen a chart that really defines the capacity, and it's difficult to measure because it's difficult to say how active the rooms will be or how much content you'll generate. That much is different from organization to organization.
There are some guidelines in general here:
https://technet.microsoft.com/en-us/library/gg615006(v=ocs.15).aspx but they don't really touch the standard model.
The pChat database can be offloaded to a central SQL cluster if you'd prefer, there are no requirements to collocate it with the local Lync databases.
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.

Lync 2013 Standard Edition on Cisco UCS E-Series

Hello,
We have a working Lync 2013 deployment:
- Front-End Enterprise Pool consisting of 3 FE servers
- one Edge Server
- one Back-End server
- one Mediation Server
- one IP PBX gateway, where ITSP's SIP trunks end.
Because we have geographically distributed offices, we are considering deploying of branch offices deployments.
Technet recommends to use SBA for branch offices where there are less than 1000 users. But in case of WAN outage, no conferencing will be available for branch users.
Lync 2013 Standard edition branch deployment would offer all Lync features in case of WAN outage.
In every branch, we consider deploying a Cisco ISR G2 router for terminating branch SIP trunks. This equipment have option to add Cisco UCS E-Series blade that supports CPU with hardware virtualization and supports decent amount of RAM (up to 16GB and up
to 48GB).
Have anyone experience with deploying Lync Standard Edition on this equipment - Cisco UCS E-Series blades? In every branch office there are up to 50 - 500 users that will use Lync.
Thanks,
Andrei Moraru Endava

Hi,
I don’t think you can deploy Lync server 2013 on Cisco UCS E-Series blades.
Here is a link below of “System Requirements for Servers Running Lync Server 2013” may help you:
http://technet.microsoft.com/en-us/library/gg398588.aspx
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

Lync 2013 standard server for 3000

Planning to deploy Lync 2013 standard server for 3000 users, IM/presence, Audio/video, persistence chat, monitoring/archive. external access required so 1 edge server in DC and 1 in DR. No enterprise voice. DC and DR are corrected with dark fiber
one lync 2013 standard server in DC and 1 in DR. 1 edge server in DC and 1 Edge server in D R.have couple of queries.
1. can i get HA while doing server pairing in DC and DR?
2. how much time will it take for frontend failover if my frontend server is down in DC.
3. how much time will take for external access failover in DC and DR?
4. are there any potential risks if using standard version instead of enterprise?
Basically client need cost effective solution as lync is not critical for him, does not want to use 3 FE servers in DC and 3 FE in DR to achive HA. want to achieve the solution with standard servers.

1) HA typically refers to automatic failover, so not with Standard edition, but you can get manual failover with this with nearly full functionality.
2) Again, this is manual, but once invoked less than 20 minutes I'd think, possibly faster, only testing invoke-failover will tell you for sure but it won't be too bad.
3) This involves a topology change to change the federation route, possibly next hop for the edge, and possibly media path for a front end pool. That can be completed and replicated in under a minute. You may want to point your external simple
URLs and such (lyncdiscover) at the remaining server, this may be a DNS change to point to a separate reverse proxy. Your _sipfederationtls._tcp SRV record can have a lower matching partner as well, but I typically prefer to keep low TTLs on the external
DNS records so they can be changed quickly.
4) Sure, no automatic failover, your scalability is limited without building out new pools later, no SQL backend that can be mirrored for a bit more resiliency. But again, you can manually failover without issue, you just have to be able to tolerate
a short outage.
Technically, you'd only need 1 FE in the DR site. You have to match Ent/Ent or Std/Std in a pool pair, but the number of servers don't need to match. Still, the HLB and SQL requirements can be costly so I understand this.
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answer".
SWC Unified Communications

Lync 2013 standard edition server disadvantages

I have 3000 users, client is so cost effective , wanna insisting on Lync 2013 standard edition server. no enterprise voice
Feature required :- IM.presence, A/V conf, persistence chat, external access.
planned servers :- 1 Standard server in DC, 1 in DR. 1 edge server in DC and 1 in DR
1. if i make a pool of standard servers, then will it serve as HA, if yes how much time wil take for failover and what would be the impact on users?
2. If complete DC is down how mch time would take for fail-over and what is the procedure, impact on users?
3. can i collocate persistence chat role on standard edition? any limitation? how backend sizing would be for persistence chat as sql express would be there
4. can i suggest any better solution with standard servers where HA in DC .

For 3000 users Standard Edition will be fine. Use the capacity planner to size out your environment. http://www.microsoft.com/en-us/download/details.aspx?id=36828
1. It won't really serve as HA, as pool pairing is the only option it's more of a DR solution. The RTO for a pool failover is 30mins. So it could take anywhere up to 30mins. http://technet.microsoft.com/en-us/library/jj205079.aspx
2. Same as above. Here is how you failover http://technet.microsoft.com/en-us/library/jj204678.aspx
3. Yes, you can co-locate Persistent Chat on the Front End with Standard Edition. If sized correctly, there should be no performance issues.
4. The only option with Standard is Pool Pairing, so no better suggestions.
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.

Lync 2013 Standard backup questions

Hello
I need to backup our Lync 2013 Standard Edition setup.
We have Only one server atm.
Looking at this post for inspiration:
http://blogs.technet.com/b/heyscriptingguy/archive/2014/06/28/weekend-scripter-basic-lync-server-2013-backup-and-restore-part-1.aspx
As far as i can understand, i don't need to do SQL backup at all? Or am i missing the point?
Would I be able to restore my Lync from these 3 commands:
Export-CSConfiguratiom, Export-CSLisConfiguration and Export-CsUserData - Is that enough for a disasterrecovery?
And a bonus question:
When i run Export-CSLisConfiguration . The export only contains the following:
<?xml version="1.0"?>
<LisDatabase xmlns="urn:schema:Microsoft.Rtc.Lis.Database.2008"/>
Is that not incomplete somehow?

That much would get you back up and running, yes. But it may not be a "full" restore.
For example, if you have persistent chat data, it wouldn't necessarily be included in there. If you have an archiving database where all IMs are sent, that information wouldn't be in the PowerShell exports above. If you don't have a copy of the
certificate and private key, that's lost.
Typically, I run my own custom version of Lasse's backup script https://gallery.technet.microsoft.com/Backup-script-for-Lync-2013-aacbb9b9
That pulls all the data, including your file stores, SQL exports, certificates, and everything into a single folder and zips it for you. If you back those zips up, you'll have most everything.
Restoring directly back into SQL isn't the recommended method, if you did need to get back up you'd want to follow standard restore procedures by using the supported PowerShell, but you'll have other avenues to restore if needed and a more complete copy
of your data.
The LIS export may be complete if you don't have any Lync locations defined. You'd typically enter these for 911 purposes.
Check out Lasse's Channel 9 video as well:
http://channel9.msdn.com/Events/TechEd/Europe/2014/OFC-B331
Check out his backup series docs here as well:
http://tech.rundtomrundt.com/search/label/Backup-Lync2013
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.

Lync 2013 standard number of Backends required and pool paring setup?

Hi
I am in the process of putting together a lync 2013 implementation. The plan is to use lync 2013 standard as IM and Presence are the only requirement we have approx. 3000 users
we have two sites
Site A (Primary)
x 2 FE-A1 FE-A2 Lync 2013
x1 BE-A1 Lync 2013
Site B (D.R)
X 2 FE-B1 FE-B2 Lync 2013
X1 BE-B1 Lync 2013
what I want to know is
1. If Site A has two FE servers each will require there own pool if I pair FE-A1 with FE-A2 can I also pair FE-A1 with FE-B1 and the same for 2?
2. Can the servers FE-A1 and FE-A2 use the same BE server or should I be using a separate server for each?
3. In this design I was thinking of using two edge servers 1 at each site that would be published using TMG, would this be correct, this would be for IPhone mobile users to use.
thanks in advance
J

1) If site A has to FE servers, and you go with Standard edition, they would be their own pools. If you wanted HA you could put three enterprise servers together into a single pool and load balance them. If you pair FE-A1 with FE-A2, those
two pools cannot be paired with any other pool. You also can't Pair FE-A1 to FE-A2, then FE-A2 to FE-B1.
2) Your diagram looks like Lync 2013 for the back end, it would actually be SQL, and this would specifically apply if you're using Lync enterprise. If the Lync front end servers are in the same pool, they can use the same backend, if they're not they
need separate back ends.
3) Edge servers would be published with a standard firewall, if TMG is your firewall that would work. If TMG is only being used as a reverse proxy, you would use it to publish your web services on your front end servers. Either way, you'll need
to also publish the web services on your front end servers to the Internet for mobile clients to function.
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.

Outlook 2013 won't open calendar items created on Outlook 2007

I have a user that recently got office 2013 pro plus on his computer. We created a new profile and connected him to exchange 2010. Now when he tries to open up a calendar item that was created prior to the 2013 install it just spins and you have
to cancel outlook. He can create new calendar items and then open them up again but any item that was created with 2007 locks up.
Any ideas?
Thanks

Hi Jason,
I agreed with ED's point. If everything in your mailbox can work well in OWA and Outlook 2007, the mailbox in your server side should be healthy and configured properly.
Personal opinion, I suggest that we can try another computer with Outlook 2013 to check whether the issue persists. Also start Outlook by using Outlook /safe and Outlook /cleanprofile switches to have a try.
Thanks,
Winnie Liang
TechNet Community Support

Lync 2013 OCT deployment on machines with Office 2010. Installation Failure

Hi,
In our environment, we have Win7, Office 2010 x86. (no plans to upgrade all of Office to 2013 as yet)
I'm trying to deploy Lync 2013 x86, and have packaged an MSP using "setup /admin" for later deployment via SCCM.
Now I know there are no problems running Lync 2013 with Office 2010 as it works fine if you manually install.
Strange thing is, when I try running the setup with MSP for silent install, it runs silent and all looks well although all the Office Tools shortcuts are created and there are files under the Program Files folders for Office\15.0 as expected
but not Lync itself. ie: no lync.exe file or shortcuts.
Reviewing the setup log doesn't show any obvious errors that I can tell.
Also after this, if I go through the "Add/Remove Components" under Uninstall Programs\Lync 2013, and I can see in there that it DOES already show Lync as being installed, if I just click continue, it runs through the setup process and
then Lync will be installed
I've also tried this same process using the Full "Office Pro Plus 2013" and only select Lync to install and the same thing happens.
Has anyone else come across this issue or could point me in the right direction.
For the OCT (setup.exe /admin) the only settings I've changed from defaults are:
- Filled in the Organisation name
- Set KMS licensing, display level to none and suppress modal
- some regkeys for some default settings for GalDownloadInitialDelay, ShownFirstRunOptin
- Force on Lync (Run from My Computer)
I'm running "setup.exe /adminfile Lync_x86.MSP" in my case to test this MSP.

I had the same issue. As soon as I updated to the latest Admin admx/opal files, it worked great.
Cheers,
JeffCSP
This issue was introduced when SP1 was released, and is detailed here:
http://blogs.technet.com/b/odsupport/archive/2014/03/21/lync-2013-and-onedrive-for-business-are-not-installed-when-installing-office-2013-with-service-pack-1.aspx
(it remains uncorrected by MSFT :(
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

Lync 2013 Edge server compatibility with Lyn 2010 Front end Pool

Hi All,
Technet article (http://technet.microsoft.com/en-us/library/jj688121.aspx) says the following:
If your legacy Lync Server 2010 Edge Server is configured to use the same FQDN for the Access Edge service, Web Conferencing Edge service, and the A/V Edge service, the procedures in this section are not supported. If the
legacy Edge services are configured to use the same FQDN, you must first migrate all your users from Lync Server 2010 to Lync Server 2013, then decommission the Lync Server 2010 Edge Server before enabling federation on the Lync Server 2013 Edge Server.
Can you tell me why it is you have to change the External Lync Web services URL during a migration to Lync 2013 from Lync 2010. What purpose does this serve?
Also can you clarify this and explain why this is required, why would you have to migrate all of your users, would a Lync 2013 Edge not talk to a Lync 2010 front-end?
Any help would be much appreciated. MANY THANKS.

Thank you very much for all your inputs.
We still have few questions:
Questions:
Can you tell me if Lync 2010 users will be able to login using mobility if we repoint the reverse proxy (TMG) web services publishing rule to the Lync 2013 server? Remember both systems Lync 2010 and 2013 are using the same web
services URL so they will both end up at the Lync 2013 server. Alternatively if not we will migrate all users to 2013, this is not a problem
In addition to this I cannot find anything that states how Exchange UM will operate when you are running from a backup pool and the exchange UM contacts are not available because they are homed on the server that is down. This
configuration is 2 x standard edition servers pool paired. How can we make sure Exchange voice mail works during a pool failover?
Call Park is not clear to me I read the following:
Lync Server 2013 provides new disaster recovery mechanisms in the form of failover and failback processes. These failover and failback processes support recovery of Call Park functionality by allowing
users who are homed in the primary pool to leverage the Call Park application of the backup pool when an outage occurs in the primary pool. Support for disaster recovery of the Call Park application is enabled as part of the configuration and deployment of
paired Front End pools.
Is this saying we need to deploy Call Park in the DR pool and use a different range of orbit numbers, or can we use the same range in the DR pool?
Further, I can see that Common Area Phones will be fine as they will log into the DR pool automatically. Response Groups need to be exported and imported to the DR pool. Incidentally these did not migrate well at all and have
caused us a big headache!
Any inputs will be greatly appreciated. Thanks again for all of your time.

SharePoint 2007 to SharePoint 2013 Upgrade - Need to Goto SharePoint 2010 First?

All,
I've seen some posts that say one can go from SharePoint 2007 to SharePoint 2013 - without upgrading to SharePoint 2010. Other posts say otherwise.
Therefore, what is indeed the answer. Ideally I'm looking to stand-up a new SharePoint 2010 or SharePoint 2013 farm then likely do a detach then upgrade of the SharePoint 2007 content databases to SharePoint 2010 or 2013.
Thanks

If you want to do a standard SharePoint upgrade, yes you must go to SharePoint 2010 prior to 2013. If you want to use a 3rd part/in-house custom application content migration upgrade, then you can go straight from SharePoint 20xx to 2013.
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Lync 2013 SQL versus Exchange Archiving

Our organization has setup an internal lab for Lync and is trying to decide what the best option would be for deploying archiving with Lync and what the pros vs cons are.
We currently have one Lync 2013 FE Server and an Exchange 2010 server, which I already know does not support archiving. Would it be best to deploy a SQL server for archiving or upgrade Exchange 2010 to 2013? We can do either, but was is the recommended approach
and best practice/pros/cons?
I was planning on utilizing SQL server as the preferred for approach and so we don't have to upgrade Exchange -- just seems easier and will keep any additional load off the Exchange server and once deployed to a production environment.
Thanks.

Agree with Michael.
This data stored in Archiving database is not searchable, but it can be exported to formats that are searchable using other tools.
You can check the difference between these two archiving options at
http://technet.microsoft.com/en-us/library/jj204900.aspx.
Lisa Zheng
TechNet Community Support

Lync 2013 standard deployment: Exchange 2010 Sharepoint 2010 and outlook 2007 collaboration

Similar Messages

Maybe you are looking for