Generally, I'm opposed to the idea that a Windows server should be rebooted on a regular schedule EXCEPT in relation to TS/RDS servers. We reboot ours every day. It clears up old sessions, releases in use resources (CPU, RAM, file handles, etc.), so my opinion and suggestion would be that you do configure a daily scheduled reboot of your RDS servers.
Users refuse to log off instead of disconnect
Setup the appropriate group policies to auto-logoff them. You can separately control an idle timeout and logoff. That should certainly minimize some of the issue during the day.
I restart my 3 server TS farm daily at 3:00am. Because, yes crap can build up over time when you have lots of people using a single ...
The following table summarizes the ports and protocols used by Skype for Business/Lync clients:
Port Protocol Notes
5061 TCP (SIP) Used for SIP/MTLS authentication of A/V users. Communications flow outbound through the internal firewall
443 TCP (HTTP) Used by Skype for Business clients/Lync connecting from outside the intranet for SIP ...
For me, Lync conversation history was not getting displayed in outlook (a Form region cannot be opened).
Issue got solved after removing the entries HKEY_CURRENT_USER\Software\Microsoft\Office\Outlook\FormRegions and by restarting Outlook.
Follow the instruction at link :
Outlook has certain built in ...
When you installed Lync did you add the CSAdministrator and RTCUniversalServerAdmins to your Administrator Member Of Security group?
Without CSAdministrator you cannot log into the Control Pannel, and without RTCUniversalServerAdmins, you will have some trouble in doing some advanced powershell stuff.
I have a similar setup to you, and here's what I'm doing and everything works:
External IP1, Port 80/TCP is NAT/PAT to Standard server port 8080/TCP
External IP1, Port 443/TCP is NAT/PAT to Standard server port 4443/TCP
Since you're not using a TMG server, your firewall must do port translation so that external requests hit the correct site in IIS on your ...
What you are looking for is called self-service password reset. It even has an acronym (SSPR) and is part of identity and access management.
Loads of vendors publish solutions for this, and though product recommendations are not on-topic here, vendors include IBM, Hitachi ID Systems, Microsoft, and Courion.
Usually this is the cheapest and most basic ...
Depending on your cash, time, and the savviness of your users, another idea could be to stand up a second server. You'll still need to reboot occasionally, but you seem to be reaching the limits of a single server.
You should be able to use the same client CAL's (licensing's not my strongest area), and depending on your virtualization solution an additional ...
It is a little hackish, but if you right click > copy the Join Skype Meeting url from the invite, paste it in your browser and add "?SL=1" (without the quotes, so it would look something like https://meet.yourdomain.com/user/98daf9w?SL=1) on the end, it will force to join in via the web app (where you can join as guest) instead of automatically opening Lync/...
It's supposedly not support by Microsoft. The biggest things you'll run into deal with the fact that both Exchange and Lync use IIS and listen on the default ports of 80 and 443.
You are better off having Lync on it's own server...just use a VM.
The Lync File Share is used to house a bunch of Lync Shared Resources between servers.
Once up in running the server generates 3 subfolders:
1-ApplicationServer-1 - This is where custom application services settings are stored. like custom music on hold (I think).
1-CentralMgmt-1 - This is the Central Management store replication service does is magic in ...
I am familiar with the "user type" that refuses to logoff. However, they seemed to have no issue understanding that the Server would be rebooting nightly so any unsaved work would be lost. This is on Server 2008 R2 TS Supporting About 20 users on a single machine.
You will need an on-premise Lync deployment to get the functionality you are after. In Lync this feature is called Enterprise voice.
There are a number of ways to connect the Lync environment to the PSTN the 2 most commons are:
Use a TDM/IP gateway to connect to an existing ISDN circuit.
SIP trunk over MPLS (you can get them over the internet but the ...
There is no problem at all in using the same certificate in two different applications, if everything else is ok. The certificate in itself is not the problem, the problem lies in some misconfiguration on the Lync side.
You should check all URLs Lync uses (they are a lot...), and verify that your certificate actually contains all the names being used. Also, ...
Interoperability with existing telephony infrastructure
Lync Server 2010 uses standards and published interfaces to interoperate with existing infrastructure. Gateway and SIP options for interconnection to IP PBX systems and the Public Switched Telephone Network (PSTN) allow companies to migrate users to Lync Server 2010 Enterprise Voice over time while ...
No, each client has its own stream. Keep in mind Office365 Skype for Business uses a server in the cloud not on premises.
Essentially what you are asking is can Skype for Business detect you are all in the same gateway and send all the data as one session. Ignoring that each session is separate no because Skype for Business does not to my knowledge ...
This can be done with an Edge server. Once a Lync front-end is deployed you can rollout an edge server. This will allow for a number of things federation with other Lync users, connectivity to external IM services like AIM, MSN and Jabber/XMPP clients, as well as external access for users.
Here is the MS deployment guide: http://www.microsoft.com/download/...
Sometimes, you just have to get creative! A few ways you could handle this:
Gently: Set up an advertisement that is optional for the update. The user will see that an update for Lync is available, but it can be installed at their discretion. You can then run a compliance report, say, two weeks later and follow up with the stragglers.
Draconian: Do an ...
If you're installing them in seperate VMs, you'll need a reverse proxy or ISA server or Threat Management Gateway or a good wired-router to figure out what the originator is requesting.
For example, Lync traffic, to Lync VM.
Exchange traffic, to exchange VM.
Answered by @ryanlowdermilk from Twitter:
@gabesumner no hard limit, 250 multi-party video. however, not
"hollywood squares" style; it would be speaker highlighted style.
This also supports a discussion I was seeing in the Microsoft TechNet forums.
I'm by no means an expert, but I'll give you the little bit of knowledge that I have.
With regards to your last question: No, you don't need to connect Lync to a PBX/external phone system to make use of it. You can have Lync exist as an isolated communication system, and be able to have users send each other instant messages, audio calls, video calls, and ...
It turns out this is expected behavior.
Office 365's Exchange service uses basic authentication passed through SSL, because of the nature of o365 there is no way to change the authentication type.
On initial sign-in that prompt is expected if outlook is not open. The credentials can be stored to avoid future prompts, however every 3 months (password reset),...
Do you mean Proxy or Reverse Proxy ? Nevermind...
Neither an Edge Server nor a (Reverse)Proxy are required to access Lync through VPN.
These are only required to access Lync from outside your LAN (external users and federation). VPN users are virtually in your LAN.
If you have a firewall between your LAN and your VPN subnet, just ensure to open ports but ...
I'm not aware of any official tool for this. MS treats Lync just like Outlook in that there is a "global address list" you can search but contacts are like Outlook contacts, added per account.
However, there is a developed tool to handle this:
Now...I've never had to use it, but I bookmarked it just in case we ever went down ...
There is no way to go straight to S4B.
The best solution I found was to just install Office 2016, which would also install S4B 2016 Client. The Office 2016 installation. With OCT you can customise the installation.
According to the official Microsoft documentation here:
This topic provides details on deploying the Microsoft Lync VDI
plug-in, which is only supported on Windows 7 and Windows 8 or Windows
Server 2008, and only supports Lync 2013 or Skype for Business 2015
Using the Lync VDI plugin should work with your Skype for Business 2015 clients. ...
I resolved this by amending the manifest file reported in the error (C:\Program Files\Microsoft Office 15\root\office15\LYNC.EXE.MANIFEST), changing the processor architecture of the UccApi DLL.
<assemblyIdentity type="win32" name="UccApi" version="18.104.22.168" processorArchitecture="*"></assemblyIdentity>
Short answer: Lync 2010/2013 are replaced by Skype for Business. Therefore you couldn´t any longer find them. But as Skype for Business also offered to manage the firmware for Lync Phones you should try that one (see here).
Keep noted that Lync 2010 already reached the end of the Mainstream Support as it was fully replaced by Lync ...