Thanks for the feedback. Maybe I wasn't clear enough about the design. My plan is to setup a pool pair between the two sites using Lync Enterprise with a full SQL backend, which I'll mirror. I cant use Lync Std Edition because I need full blown SQL for archiving.

You can use Lync Std edition and have SQL standard version on a dedicated server for Archiving. it has nothing to do with Enterprise or Standard edition! Lync Archiving role is now collocated on the Front end! it's no longer a dedicate role like in Lync 2010.

If you don't have more than 5000 users in both sites then Lync Standard on each site with pool pairing between them would be the best way to go with it for both HA and site resiliency. you can check microsoft's technet KB articles about it.

We're not using Lync archiving, we're using a separate archiving solution to export Lync chat data to a third party which doesn't work with SQL express, we have to use full blown SQL, which requires Lync Enterprise setup.

Archiving role on both Lync Enterprise and Standard requires SQL standard/Enterprise to be deployed on a separate dedicated server (Not the FE) in order for it to be functional and it doesn't work with SQL express.

The SQL Express is installed on Lync FE for Standard edition to save the Central Management store.

Your following statement, Your design is correct but it one server in Enterprise pool is not recommended because it would break the windows fabric.

Is this still a problem with the design?

Yes because the recommended number of servers for the fabric pool to work is 3 Enterprise servers at least. you will have a lot of issues between the two pools that you're intending to deploy between the two sites.

If you would do a cost effective solution then your best bet is to use the standard edition, otherwise I would only recommend enterprise pools with 3 Lync enterprise servers in each pool for each site.

I would love to use Standard Edition, except the archiving solution we are using requires the FE server use SQL, and not SQL express. The solution connects to the FE server which must be connected to SQL, not express. If the solution would connect directly to a SQL database, that would be great, but it doesn't, else I would use Std Edition with a SQL archive database.

Is that a total of three servers between the two sites, or is that three servers for each pool?

Yes true you could pair between two pools but to be honest I have never tried pairing two enterprise pools with only one server on each site but I'm assuming that it will work without an issue however! If for any reason the server 1 on Pool 1 fails then you will have a painful job to do which is failover users, CMS...etc and then when this Server is back up and running you will have to failback to it.

I'm probably going to apply this scenario in a lab and see how it works because I know when Lync enterprise have 2 servers in a pool and one of the servers goes off the other server goes crazy and services would stop and you will have to restart all servers in order unless there are 3 servers then the fabric pool works as supposedly.

Sometimes we have such a need to use two Skype accounts, for example, you may have a personal and a business account that you want to keep separate. By default, Skype can be run only once. Attempting to start it a second time fails.
However, we …

Popular third-party chat platforms like Slack, Discord, and Telegram are just a few of the many new productivity applications that are being hijacked by cybercriminals to create command-and-control (C&C) communications infrastructures for their malw…

In this video you will find out how to export Office 365 mailboxes using the built in eDiscovery tool. Bear in mind that although this method might be useful in some cases, using PST files as Office 365 backup is troublesome in a long run (more on t…