Link to home
Start Free TrialLog in
Avatar of Jody Davis
Jody DavisFlag for United States of America

asked on

Is more users than RDS licensing keeping employees from connecting?

Our MS Server 2012 R2 RDS Farm has a lot of new users. They are experiencing a huge growth, and having connectivity issues.

** Is there a RDS log that i can see if people are being denied with "There was a problem connecting to the remote resource" due to insufficient licenses OR is it something else?

I've checked mem/cpu on the servers, pretty high so i keep adding as needed, but i should be over licensing as well - how can i tell for sure which is the problem with logs?  Need an answer today, no time to add/purchase software that may help. Please advise
Avatar of Lee W, MVP
Lee W, MVP
Flag of United States of America image

Proper licensing is your answer.  Since licenses are per HUMAN BEING or end user device, if you're licensed per human being it's EASY to know how many total licenses you need and subsequently get them.

Any MSP who's a Microsoft partner can get you licenses in a few minutes; CSP licensing allows the order to be taken and processed in minutes - you just might have to grant access to them as a partner (which also takes minutes).

(If it's not licensing, I would check your event logs on the client and server(s)).


Avatar of Jody Davis

ASKER

Agreed on the licensing, and i just finished goin through accounting, received a proper PO for the purchase and already forwarded that to our MS partner.

** where/which log can i view to see a user being rejected by insufficient licensing or resource limitations - which log can i see that error/event ID so i can tell my bosses definitively (users are in India so i have minimal info on true problems sometimes) the issue is licensing, for instance, and they'll suffer til then - or which log can tell me what the issue may be?  I can really use an answer to forward today before India comes back online tonight, our time.
Any number of things.  Event logs need to be reviewed.  RDS related logs, System, Application on the client and the server(s).  TIMING is helpful in troubleshooting - filter for everything but information and look at the times when the errors occurred.  There can be a lot of noise, getting rid of the informational alerts can make it easier to spot (unless you're servers aren't healthy to begin with).
This has to be it. Easier to tell the boss "see, disconnects and here is all the errors".   

Which logs can i look to verify the licensing is showing the disconnects instead of just thing obvious number?

User generated image 

ASKER CERTIFIED SOLUTION
Avatar of Lee W, MVP
Lee W, MVP
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Thanks, as you see we have a lot more users than licenses - will MS deny you access if over licensing?  Or could it be something else that's causing users not to be able to get on the Farm?
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
<< and having connectivity issues. >>

<<"There was a problem connecting to the remote resource" >>

 Sounds more like a server resource limit.     Once users are connected, are they having any issues?  i.e. abnormal disconnects, etc?

Jim. 
* can someone verify please if 2012 MS RDS farm will disallow if no licenses available?

* i may throw another server at the Farm as well, perhaps we're out of resources as well.

<<* i may throw another server at the Farm as well, perhaps we're out of resources as well. >>

Where are you at with this?   Any improvements or still in the same boat?
 
There is a setting that controls how many connection a session host server will accept.  I'll look for it if you haven't already tripped over it.

Jim.
The issue ended up being cpu ready in vsphere - the VMs were competing with other VMs for the phys cpu time. I moved a new host server into the cluster which added more available phys cpus and added 2 more VMs - and it did the trick. Thanks guys, all these points were helpful.
Glad to hear you got it resolved.

Jim.