2012 в систему вошло слишком много пользователей windows server 2012 r2

Куда копать?
В систему не могут войти одновременно несколько пользователей.

«Выберите какого пользователя отключить чтобы вы могли выполнить вход»

Минуточку внимания

Answers

• Are the PCs connecting via remote desktop so they can actually run an app that resides on the server?  I’m still not sure what your ultimate goal is here.  Maybe you could explain what it is you are trying to accomplish.

  
  —
  Merv  Porter   [SBS-MVP]
  ============================

  • Marked as answer by

    Thursday, March 28, 2013 10:04 AM

• With WS2012E, you can have 25 users in the domain but you can only make two Remote Desktop Connections to the server at any one time (and those connections are supposed to be for server administration purposes).  This is hard coded
  into WS2012E.

  In order to have more remote desktop connections, you would need to buy an additional server with a full Windows 2012 server and install the RDS role, then buy RDS CALs to support each session you need to create. 
  

  I have a feeling you bought the wrong Windows server product (WS2012E) for your needs.

  
  —
  Merv  Porter   [SBS-MVP]
  ============================

  • Marked as answer by
    Andy Qi
    Thursday, March 28, 2013 10:04 AM

• There is a big difference between ‘remotely controlling the server’ and ‘logging into the domain’.

  You can have 25 users in the WS2012E domain.  They can all log ‘into the domain’ from their computers once they have been joined to that domain.  All of them can access ‘shared data’ stored on the server.  However, you can
  only have 2 users ‘remote into’ (remotely log onto) the server at any one time. 
  

  I looked at Kitomba’s web site and it was unclear how their software needs to be installed in a networked environment.  Normally, you would store a database itself on the server and then each computer
  would have ‘client’ software installed, pointing to the server database.  When the user then logs onto his computer, he would open the client software and access the database on the server.  There would be no need to ‘remote into» the server
  to run any software.

  In your current scenario, you apparently need 3 «remote control connections» to the software on the server, which can’t be done with WS2012E.  For that, you would need a either a second server set up as an RDS (Remote Desktop Services
  <formerly called Terminal Services.) in the WS2012E domain; or you would need to buy Windows Server 2012 Standard edition, install it on your server in place of WS2012E and then install the RDS role.  You would then also need Windows 2012 User
  CALs and RDS CALs for your users.  This RDS server would usually not be a domain controller (like WS2012E).  At that point, you would install Kitomba on the RDS server and then all your users could ‘remotely control’ the RDS server and the Kitomba
  software installed on it.

  I think you may need to get back with Kitomba support, tell them your current hardware set up and let them guide you in the best network setup to meet your requirements.  My guess is that you can install the Kitomba software on
  each PC, install just the main database on the WS2012E server and then point each PC’s Kitomba software installation to the main database on the server.  No ‘remote control of the Kitomba software on the server’ would be necessary.

  
  —
  Merv  Porter   [SBS-MVP]
  ============================

  • Marked as answer by
    Andy Qi
    Thursday, March 28, 2013 10:04 AM

• … You would need to purchase additional Terminal Service CALS.

  On Essentials, you can’t install additional Terminal Service CALs. Two simultaneous Remote Desktop connections to your server is all you can have.

  ---

  I’m not on the WHS team, I just post a lot.

  • Marked as answer by
    Andy Qi
    Thursday, March 28, 2013 10:04 AM
• • Marked as answer by
    Still Grey
    Sunday, September 20, 2015 5:14 PM