Lync Standard Edition Servers - paired across datacenters question

Hi all
I am designing a Lync deployment for a small org (circa 800 users) obviously they keep banging on about HA/resiliency etc
my initial design was a pair of standard edition servers in a single (tier 3) datacentre (with dual edge servers), they keep insisting they require a 50/50 split across a second datacenter
so obviously with Enterprise Edition it is possible to have a high degree of resiliency both in and between datacenters - but at some cost and with massive server bloat - seems over engineered
and if you do it with SE server - I,e split the SE server between datacenters you loose any resiliency in each datacentre - and presumably if a server needs maintenance etc then you need to fail over the entire userbase from one datacentre to the other
what are people views on this - I still think the paired SE topology in a single datacentre is the best compromise (the WAN with be fully resilient too)
do I have any other options

Keep in mind, pool pairing isn't HA and it's not automatic, it's just a level of resiliency.  If one server needed maintenance, you'd still want to plan downtime to manually fail the users over so they didn't see the blip. 
The large benefit to running the pair in the same site where all the users live in that site would mostly just be the WAN access.  Two party audio/video chats will generally send the media directly between the endpoints, so that wouldn't necessarily
cross the WAN anyway. IM traffic is pretty negligible, but would hit the front ends and if you're strapped for WAN bandwidth you may want to watch it. More so, if someone on the far end datacenter scheduled a conference for users in the main datacenter with
video, then you could have heavy traffic hitting the WAN to get to the other site and back.
The big benefit to putting it in a different datacenter is of course simply site resiliency. 
The difference between a full datacenter failover and a failover in the same site isn't that different with pool pairing however, in both cases it's a handful of PowerShell commands and in a pinch some quick DNS and topology changes.
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

Similar Messages

  • Lync Standard Edition Server pairing -- Archiving and monitoring collocated but Single SQL backend

    Hi,
    I have a scenario where in ---we have Two Standard Edition Servers ( SE1 and SE2) with 1K users each ( Total 2K in one Site) paired to enable High Availability. The Standard Edition Server has archiving and monitoring and mediation server collocated.
    For archiving + monitoring database we have a Seperate SQL enterprise edition server.
    Quetions:
    1. Can we use single SQL Enterprise Edition as backend for (archiving and monitoring ) for both SE1 and SE2 ?
    2. If yes, do we need two seperate instances?
    3. If not, could you please suggest the best possible solution in such an environment ?
    Regards,
    Archana Rao

    Hi ArchanaVR,
    Agree with Michael, and add some more details.
    By default, the SQL Server Express back-end database is collocated on the Standard Edition server. You cannot move it to a separate computer. With one exception, you cannot collocate other databases on the Standard Edition server. If you choose to deploy
    Persistent Chat Server on a Standard Edition server, you can collocate the Persistent chat database and the Persistent Chat Compliance database on the same Standard Edition server.
    You can collocate each of the following databases on a single database server:
    Monitoring database
    Archiving database
    A back-end database for an Enterprise Edition Front End pool
    You can collocate any or any or all of these databases in a single SQL instance or use a separate SQL instances for each, with the following limitations:
    Each SQL instance can contain only a single back-end database (for an Enterprise Edition Front End pool), single Monitoring database, single Archiving database, single persistent chat database, and single persistent chat compliance database.
    The database server cannot support more than one Enterprise Edition Front End pool, one server running Archiving, one server running Monitoring, single Persistent Chat database, and single Persistent Chat compliance database, but it can support one of each,
    regardless of whether the databases use the same instance of SQL Server or separate instances of SQL Server.
    http://technet.microsoft.com/en-us/library/gg398131.aspx
    Best regards,
    Eric

  • Is it possible to have two Paired Lync Standard Edition servers in different domains?

    We initially installed Lync in a parent domain with all the users in the child domain. The user's SIP addresses is that of the child domain. We now have a requirement to migrate the server to the same child domain as the users. At the same time we
    need to set-up a new server to test some planned network changes. Would it be possible to set-up another Standard Edition Front End Server in the child domain and pair it with the server in the primary domain? We can then migrate the users across as required.

    Hi PanosE,
    Yes, you can set up another Standard Edition Server in child domain and then deploy pool pairing.
    You need to deploy a new Front End Pool for the new Standard Edition Server.
    A similar case for your reference.
    https://social.technet.microsoft.com/Forums/office/en-US/eca4299c-8edb-481e-b328-c7deba2a79ba/lync-2013-standard-edition-lync-fe-pools-in-multiple-domain-single-forest-senario?forum=lyncdeploy
    Best regards,
    Eric
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]

  • What is the difference with 1 Lync Standard Edition using VMware Fault Tolerant and 2 Lync Enterprise Edition in a cluster

    Hi
    As I will be planning to setup Lync on a virtual environment regardless if it is going to be the Standard or Enterprise edition.
    I am thinking if we use 1 Lync Standard Edition for the FE Server with Fault Tolerance enabled, would it be as good as having 2 Lync Enterprise Edition in a cluster?
    Thanks

    Hi there,
    the main difference between using Lync enterprise and lync standard is the High availability and scalability feature,
    you will get fault tolrance setup with one lync standard edition running on whatever hyper-v and vmware platform, however this will not be an optimum highly available solution for the simple reason that upon a host server failure the image will move
    to another available host server and users will lose their active session durin the move process.
    on the other hand what you will gain if you the Enterprise edition is that you will have a unique identity to which all lync clients will be connecting and this identity is the lync pool identity which is in the background handled with multiple Front-End
    servers and AV conferencing pools, mediation pools and so on.
    In additioin when you have multiple front-ends in place, those front-ends will not work in active/passive mode as in a regular cluster, in contrairy all the servers will be active and handeling the work load.
    hope i make it a bit clear, if yiu need more info i am ready
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread
    Thanks for the response, being a small environment of 300 users, standard edition would be more than enough for me but the fact for HA is very critical for me at this stage. That is why I am exploring the option of using VMware FT.
    I don't quick get what you mean on the users having to move to another image as my understanding of FT is in the event of a host failure (not VM failure like bluescreen etc), the VM will fail over to another host with no lost in any ping etc.
    So, in theory, the Lync Server VM would never know that the parent ESX host had failed and it needed to failover to another host. Hope my understanding is correct.
    Thanks

  • SharePoint 2013 Enterprise and SQL Server 2012 Standard edition vs. Enterprise - feature question

    I can't seem to find any clear answers to the implications of installing SQL Server 2012 standard edition vs. enterprise in regards to SharePoint 2013. 
    I understand that to get many of the features you need Enterprise edition of SQL 2012; but, what I can't figure out is if the backend SharePoint SQL 2012 is standard; but, the PowerPivot/SSRS server is Enterprise will we still get the features?
    If we have 3 tier SharePoint farm, one of those tiers is for the SQL Server database backend.  If that SQL instance is 2012 standard and we add another server to the farm w/ SQL 2012 Enterprise to handle the tabular models, PowerPivot, and SSRS in integrated
    mode will we still get the features?
    Or, can we (should we) install Enterprise 2012 as the SharePoint database backend and let that instance triple down as also the PowerPivot and SSRS instance?
    The Degenerate Dimension

    Hi MMilligan,
    SQL Server 2012 Standard is not supported PowePivot for SharePoint . In addition, SQL Server 2012 Standard is also not support some Reporting Services Features.
    For more information, please refer to Features Supported by the Editions of SQL Server 2012:
    http://msdn.microsoft.com/en-us/library/cc645993.aspx.
    Install SQL Server BI Features with SharePoint 2013 (SQL Server 2012 SP1):
    http://msdn.microsoft.com/en-us/library/jj218795.aspx.
    If you have any problem, please feel free to let me know.
    Thanks.
    If you have any feedback on our support, please click
    here.
    Maggie Luo
    TechNet Community Support

  • Not able to install rtcxds database with Lync Standard Edition

    Hello everybody,
    I'm trying to install Lync 2013 Standard in an lab environment. After publishing my topology i try to
    install the database from the topology builder and everything works fine, but the rtcxds database times out.
    It says that the database does not exist and will be created but it fails then with a timeout. The other
    databases are created successfully. A 4gb file is in the expected folder, which gets deleted when the timeout appears.
    I got 4 services on my server that won't start (SQL Server-Agent RTC & SQL Server-Agent LYNCLOCAL & SQL Server-Agent RTCLOCAL & Lync Server XMPP-Übersetzungsgateway)
    Log-File:
    ****DbSetupInstance für 'Microsoft.Rtc.Common.Data.BlobStore' wird erstellt****
    "DbSetupBase" wird initialisiert.
    Analyseparameter...
    Gefundener Parameter: SqlServer Wert lync01.lynctest.local\rtc.
    Gefundener Parameter: SqlFilePath Wert C:\Program Files\Common Files\Microsoft Lync Server 2013\DbSetup.
    Gefundener Parameter: Publisheracct Wert LYNCTEST\RTCHSUniversalServices;RTC Server Local Group;RTC Local Administrators;LYNCTEST\RTCUniversalServerAdmins.
    Gefundener Parameter: Replicatoracct Wert LYNCTEST\RTCHSUniversalServices;RTC Server Local Group.
    Gefundener Parameter: Consumeracct Wert LYNCTEST\RTCHSUniversalServices;RTC Server Local Group;RTC Local Read-only Administrators;LYNCTEST\RTCUniversalReadOnlyAdmins.
    Gefundener Parameter: DbPath Wert e:\csdata\BackendStore\rtc\DbPath.
    Gefundener Parameter: LogPath Wert f:\cslog\BackendStore\rtc\LogPath.
    Gefundener Parameter: Role Wert master.
    Versuch, eine Verbindung mit SQL Server "lync01.lynctest.local\rtc" herzustellen. mit Windows-Authentifizierung...
    SQL-Version: Hauptversion: 11, Unterversion: 0, Build 5058.
    Die SQL-Version ist akzeptabel.
    Parameter werden überprüft...
    DbName rtcxds überprüft.
    SqlFilePath C:\Program Files\Common Files\Microsoft Lync Server 2013\DbSetup überprüft.
    DbFileBase rtcxds überprüft.
    DbPath e:\csdata\BackendStore\rtc\DbPath überprüft.
    Wirksamer Datenbankpfad: \\lync01.lynctest.local\e$\csdata\BackendStore\rtc\DbPath.
    LogPath f:\cslog\BackendStore\rtc\LogPath überprüft.
    Wirksamer Protokollpfad: \\lync01.lynctest.local\f$\cslog\BackendStore\rtc\LogPath.
    Der Status für Datenbank "rtcxds" wird überprüft.
    Der Status für Datenbank "rtcxds" wird überprüft.
    Der Status der Datenbank "rtcxds" ist getrennt.
    Die Datenbank "rtcxds" wird von Datenpfad "\\lync01.lynctest.local\e$\csdata\BackendStore\rtc\DbPath" und Protokollpfad "\\lync01.lynctest.local\f$\cslog\BackendStore\rtc\LogPath" angefügt.
    Fehler des Vorgangs, weil die Datei "\\lync01.lynctest.local\e$\csdata\BackendStore\rtc\DbPath\rtcxds.mdf" fehlt.
    Fehler beim Anfügen der Datenbank, da eine der Dateien nicht gefunden wurde. Die Datenbank wird erstellt.
    Der Status der Datenbank "rtcxds" ist "DbState_DoesNotExist".
    Die Datenbank "rtcxds" wird von Grund auf neu erstellt. Pfad der Datendatei = e:\csdata\BackendStore\rtc\DbPath, Pfad der Protokolldatei = f:\cslog\BackendStore\rtc\LogPath.
    Die Installationsdatenbank "rtcxds" wird bereinigt.
    Timeout abgelaufen. Das Zeitlimit wurde vor dem Beenden des Vorgangs überschritten oder der Server reagiert nicht.
    ****DbSetupInstance für 'Microsoft.Rtc.Common.Data.RtcSharedDatabase' wird erstellt****
    "DbSetupBase" wird initialisiert.
    Analyseparameter...
    Gefundener Parameter: SqlServer Wert lync01.lynctest.local\rtc.
    Gefundener Parameter: SqlFilePath Wert C:\Program Files\Common Files\Microsoft Lync Server 2013\DbSetup.
    Gefundener Parameter: Serveracct Wert LYNCTEST\RTCHSUniversalServices;RTC Server Local Group.
    Gefundener Parameter: DbPath Wert e:\csdata\BackendStore\rtc\DbPath.
    Gefundener Parameter: LogPath Wert f:\cslog\BackendStore\rtc\LogPath.
    Versuch, eine Verbindung mit SQL Server "lync01.lynctest.local\rtc" herzustellen. mit Windows-Authentifizierung...
    SQL-Version: Hauptversion: 11, Unterversion: 0, Build 5058.
    Die SQL-Version ist akzeptabel.
    Parameter werden überprüft...
    DbName rtcshared überprüft.
    SqlFilePath C:\Program Files\Common Files\Microsoft Lync Server 2013\DbSetup überprüft.
    DbFileBase rtcshared überprüft.
    DbPath e:\csdata\BackendStore\rtc\DbPath überprüft.
    Wirksamer Datenbankpfad: \\lync01.lynctest.local\e$\csdata\BackendStore\rtc\DbPath.
    LogPath f:\cslog\BackendStore\rtc\LogPath überprüft.
    Wirksamer Protokollpfad: \\lync01.lynctest.local\f$\cslog\BackendStore\rtc\LogPath.
    Der Status für Datenbank "rtcshared" wird überprüft.
    Die Datenbankversion für Datenbank "rtcshared" wird gelesen.
    Datenbankversion für Datenbank "rtcshared" – Schemaversion 5, Version der gespeicherten Prozedur 0, Updateversion 1.
    Does anyone have an idea, what causes this timeout/error?
    Thanks in Advance!
    Kind regards,
    Fabio

    Datei "\\lync01.lynctest.local\e$\csdata\BackendStore\rtc\DbPath\rtcxds.mdf" fehlt.
     Fehler beim Anfügen der Datenbank, da eine der Dateien nicht gefunden wurde. Die Datenbank wird erstellt.
    It looks like it can't find that file.  Do you see it on your drive? 
    If you run Topology Builder, will it let you download the topology from the Central Management store and publish a tiny change at the moment? 
    Do you get the same error if you rerun step 2?
    To confirm, this is your first Lync server in the environment?
    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 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

  • Cramming it all into one Standard Edition server

    Hello,
    I'm rolling out a fresh deployment of Lync Server 2013.  Right now the idea is to have one Standard Edition server with about 2500 users homed there that will have the following things collocated:
    A/V Conferencing service
    Mediation service
    Monitoring and Archiving services (will probably use Exchange 2013 for storage)
    Persistent Chat server
    The two Persistent Chat databases: the PC database and the PC Compliance DB
    So, from everything I've read, it's supported to have all that stuff on one Standard Edition server.  Is it wise to do that if there are 2500 users?  Seems to me like a lot of load, even though all those roles are technically supported.
    We're considering having two Standard Edition servers for high availability that would have our 2500 users spread evenly between them.  (not a Enterprise FE pool).  We should be able to spread out those collocated roles if we had two SE servers,
    right?
    Thanks for the help,
    Brandon

    Yes, a Lync Standard edition server will support up to 5,000 users. The only thing to do is to make sure you have sufficiently spec'd your hardware, use the Capacity Planning tool to input the users and traffic to ensure you have sufficient hardware to cope
    with the load: http://www.microsoft.com/en-us/download/details.aspx?id=36828
    Regarding spreading out co-located roles if you pair two Standard Edition servers; this is not possible. Both servers will have all the roles and you pair them, so that in the event
    of failure of one server, you can fail over to the other server. You could home users on either pool to distribute load that way, just make sure that either pool can handle the load of all users should a failure occur and failover is required.
    On a side note, if you need external access, Edge services (and Directors, Reverse Proxy, etc) will need their own servers, as will the Office Web App Server if you want to do PowerPoint sharing in Lync meetings
    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 standard 2013 deployment with standard SQL 2008/2012

    Hi 
    I have been looking into the requirements and of setup Lync 2013 and I'm getting a little confused at to what would be required for SQL databases and what servers they need to be located on. 
    we have two sites siteA and siteB and a fast link between them 1g 
    I want to have two FE lync servers at site A in a pool 
    I want to have two FE Lync servers at site B in a pool
    want to have the DR capabilities that have been mentioned in pool pairing as well can this be done with standard only 
    Do I require SQL for these Front end servers? or do I just need two BE servers at each location each with SQL standard installed?
    To start with we really only want to use lync for IM and Presence but will require access from Iphones will this require a edge server in the DMZ? or could you use TMG? 
    what other roles will be required if we need to look at conversation that occurred in IM for auditing purposes. 
    I have looked on Technet and it only really refers to using SQL express  for standard, which to me historically is something I have not done since it has been looked upon as free and therefore maybe not seen as an medium enterprise solution. 
    thanks in advanced 
    J

    If you're using Standard edition servers, meaning you'd have 1 server per pool and you'd pair between the sites, no SQL licensing is required unless you want it for monitoring or persistent chat databases.
    If you want to have multiple servers in a pool for high availability (you mentioned 2 per pool, you want a minimum of 3 per pool), you'll need a Lync Enterprise pool with a full SQL backend.
    You can pool pair with both Standard and Enterprise.
    You don't require SQL for the front ends in either scenario, as SQL Express will be installed.  For the Enterprise edition pool you'll need at least one SQL Standard instance, but a second for high availability using mirroring would be nice.  You'll
    want a third SQL server acting as a witness to allow for automatic failover within the mirror, but this can be SQL express and doesn't require a license. 
    For access from an iPhone, using the Lync mobility client, you'll need an edge for A/V traffic and a TMG or other reverse proxy such as IIS ARR or WAP to publish the web services on the front end pool to the Internet. 
    Since this is Lync 2013, you don't need an additional role for auditing, auditing can be collocated on the front end server and write to the same SQL instance you're using for the front end pool.  You could also choose to keep the data in Exchange if
    you're running at least Exchange 2013.
    SQL express is the only thing you can use for Lync standard back end, but this isn't awful.  It does the job for Lync.  If you prefer a full SQL instance, then Enterprise is the way to go, and if you want HA with multiple servers in a pool, this
    is your only option.  Lync will install SQL Express on each server regardless for local copies of the management store databases and presence information, but the primary copies will be in the full SQL back end instances. 
    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.

  • Co-location of persistent chat and monitoring databases on Standard Edition server

    Hello, I've seen all kinds of different answers to this question around the web with conflicting answers.
    We have a basic IM/Presence only install of Lync 2013 and now want to deploy Monitoring and Persistent Chat roles.
    As per this blog, it states you can co-locate all of these on one FE server.
    http://windowspbx.blogspot.ca/2012/07/aaa-donotpost-install-lync-standard.html
    Which does match what this TechNet article states:
    http://technet.microsoft.com/en-us/library/gg398131.aspx
    However, in the Blog, it says you need to install Full SQL Server 2008 in order to collocate, yet this goes against what TechNet says is possible, in that you can have all databases in one instance:
    Each SQL instance can contain only a single back-end database (for an Enterprise Edition Front End pool), single Monitoring database, single Archiving database, single persistent chat database, and single persistent chat compliance database.
    I guess my question is, can I simply install Monitoring and Persistent Chat using the same default SQL Server 2012 instance that was installed along with the Front End Standard Edition server (RTC instance)? Or should I create a new instance? Or do I need
    to install a new SQL Server 2012 somewhere on a different server altogether?
    Thanks!

    Hi,
    Lync standard edition server has SQL express database by default to host RTC instance. Monitoring server required SQL reporting services, SQL express does not have reporting components part of it. Hence, you required full SQL version for monitoring
    and archiving deployment.
    Technically, you can install full SQL server on the standard edition server itself. But , it is not recommended in production environment. It's good idea to install SQL server on a dedicated server for hosting monitoring and archiving database.
    Thanks
    Saleesh
    If answer is helpful, please hit the green arrow on the left, or mark as answer. Blog : http://blogs.technet.com/b/saleesh_nv/

  • Installing Standard Edition One

    Hi,
    I was asked to test SE1 in order to see if it fits certain requirement. In order to do so I choose one of my RH 4.0 boxes and downloaded the database for the Linux 64 bits. Then I began installing.
    However, when I was asked to choose the Installation Type I only had 3 options:
    Enterprise Edition, Standard Edition and Personalize.
    My questions:
    1- Where are the Standard Edition One and the Personal Edition options?
    2- Is it possible that the Standard Edition One is the same installation as the Standard Edition and the only difference is certain hardware constraint (as seen @ the license documentation)?
    Any help will be appreciated.
    Best regards.

    Unfortunately, patches can cause that to change.
    See Metalink Note:219233.1
    You're correct, they can do that, but on the more
    recent versions, if you're really careful in
    following the patch instructions they typically
    don't.
    Though in all fairness 10.2.0.1 => 10.2.0.2 is a more recent version (see bug 5100038).
    This sort of thing repeatedly happens sadly with Oracle and SE. Oh and the fix noted in 219233.1 doesn't apply to windows either.
    So, to the OP, there isn't any really nice way of determining that you are running SE or SE1, you are looking for an absence of the word Enterprise - and that might be wrong because of a bug. I don't believe Express Edition identifies itself nicely either, but you can tell you are running that because it installs properly using appropriate installation media (windows installer or an rpm).

  • 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.

  • HLB for Lync Server 2013 Standard Edition

    Hi Guys,
    I am planning to add an additional new Lync Central site with paired Lync Server 2013 standard edition in Primary and DR data centers. with 1 or 2 OWAS Servers in each DCs. No Edge
    server in this new Lync central site as we already have an Edge pool in another central site for federation. Only IM & P and Conferencing, no External Access, Mobility and EV.
    My question is, for LS2013 Standard edition paired pools in the new Lync Central site. should I use HLB or DNS LB should be ok? as technically we do not have any HA here only DR.
    Any advantage using HLB over DNS LB in LS2013 Standard edition?
    Thanks for your help.
    Cheer....

    You typically wouldn't need HLB with standard edition at all.  What were you planning to accomplish?
    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

  • Assign 2 of Windows Server 2012 Standard edition licensing question

    I'm new at this and I have bought Windows 2012 Standard with 5 CALs back in January from Microsoft store on the Internet using as the host. There is Windows 2008 R2 installed as the virtual machine on the host. Few hours ago I have decided to buy another
    license with 5 CALs to upgrade those even that I did need two license of Windows 2012 Standard anyway to support 4 physical processor as my server have quad core processor.
    The question here that I need to ask is how do I assign 2 license of Windows Server 2012 Standard edition on the host to lift the limit and that up to 4 VMs will be allowed or does it automatically do that after upgrading to Windows 2012 Standard in
    the virtual machine even that 5 CALs plus 5 CALs equal 10 CALs are done automatically?

    Hello,
    You have 2 questions here:
    1. How can I stack multiple OS licence in order to have more virtualization rights (more VMs) running on that host?
    2. How can I stack Windows CAL licence from OEM.
    Answers are:
    1. You only have to licence the original licence on the physical host. You can use the same license key for all 4 VMs or use 2 VM key from the first package and 2 VM keys from the second licence package you just bought.
    There is nowhere to register those licence, except one by one inside the VM themselves.
    You have to keep all licence document in case of control by Microsoft.
    2. Windows CAL allows a user (or a computer) to connect to an unlimited number of Windows Server within your company network. You have 10 CAL so you can have up to 10 users or computers in your company that will connect to your servers (even if you have 1.000
    servers)
    There is nowhere to register those licence, except one by one inside the VM themselves.
    You have to keep all licence document in case of control by Microsoft.
    Regards
    PS: The only licence that require maintenance and central registration are Remote Desktop Licences.
    MCITP: Enterprise Messaging Administrator 2010 MCTS: Lync Server 2010, Configuring MCSE
    That is what I thought as I was told before even seen licensing details except a direction of how to attach the second license and I had to make sure. Thank you

  • Oracle 9iAS Standard Edition licensing question

    What, if anything, can be stored in OID if I purchase 9iAS standard edition? Here is my configuration:
    * Login via Oracle Portal
    * I need to support both authentication and authorization at the web and EJB levels
    Obviously, the security info needs to be stored in some JNDI-compliant server. Can that server be OID or do I need to store in the file-based provider (jazn-data.xml)?
    If I cannot use OID, has anyone successfully used a different LDAP server with 9iAS?
    Thanks,
    Ara

    Hello,
    You have 2 questions here:
    1. How can I stack multiple OS licence in order to have more virtualization rights (more VMs) running on that host?
    2. How can I stack Windows CAL licence from OEM.
    Answers are:
    1. You only have to licence the original licence on the physical host. You can use the same license key for all 4 VMs or use 2 VM key from the first package and 2 VM keys from the second licence package you just bought.
    There is nowhere to register those licence, except one by one inside the VM themselves.
    You have to keep all licence document in case of control by Microsoft.
    2. Windows CAL allows a user (or a computer) to connect to an unlimited number of Windows Server within your company network. You have 10 CAL so you can have up to 10 users or computers in your company that will connect to your servers (even if you have 1.000
    servers)
    There is nowhere to register those licence, except one by one inside the VM themselves.
    You have to keep all licence document in case of control by Microsoft.
    Regards
    PS: The only licence that require maintenance and central registration are Remote Desktop Licences.
    MCITP: Enterprise Messaging Administrator 2010 MCTS: Lync Server 2010, Configuring MCSE
    That is what I thought as I was told before even seen licensing details except a direction of how to attach the second license and I had to make sure. Thank you

Maybe you are looking for