Learn when you want, where you want with convenient online training courses. Sign up now!
[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More
Experts Exchange Solution brought to you by
"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.
The global-level presence settings that control the maximum number of devices apply to all Session Initiation Protocol (SIP) users in an Active Directory forest. Reasonable limits based on your infrastructure help ensure optimum throughput and performance.
To specify the maximum number of devices per user
Open the Office Communications Server 2007 R2 snap-in.
In the console tree, right-click the forest node, click Properties, and then click Global Properties.
On the User tab, in Maximum devices per user, type a number from 1 through 64 for the maximum number of endpoints that a registered user can have. The default is 8.
James and Peter-
I've recently had the same issue for a major program i run, and was able to get escalated engineering support. It does appear the issue you are describing is related to time. (Not sure about the other folks here having things happen only to users that start with A) I would get all users logging off at the same time, with the "maximum connections" error message. I too tried to up the maximum endpoints without resolution.
After some talks with Engineering, it appears that time sync adjustment on a Lync FE server of greater than a minute can cause this issue. In order to test this, we turned off all hyper-V time syncing, as well as disconnected the entire forest from the internet, and kept the DC in sync with the Lync FE. This resolved the problem. We then tried other variables, such as enabling time sync again, but syncing more often. The two that always work for us are disabling Hyper-V time sync for the DC and the FE, and leaving time sync only enabled for the DC and syncing everything else off the DC.
I would start by maybe trying to turn off all of your time syncing for the FE and maybe syncing it direct to a public time source? If you have the luxury, maybe disable time syncing across your entire forest temporarily to test.
Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.
From novice to tech pro — start learning today.
Premium members can enroll in this course at no extra cost.