RDS CALs can be tracked using Per Device, whereas they cannot be tracked within a workgroup for Per User.In Per User, RDS CALs are assigned in Active Directory. With Per Device, each device has RDS CALs physically assigned to them.To better understand the two types of RDS CALs, some of the main differences are outlined below: *Note: To grant a user remote access, you need a Windows Server CAL and an RDS CAL for each user or device. If the RDS CAL is available, the RDSH server accepts the connection from the user and starts a session.
When a user attempts to connect to an RDSH server, the server checks to see if the user has an active User CAL by contacting the RD licensing server. To install and keep track of the RDS CALs, you need an RD Licensing Server, which is a component of the RDS Collection. However, older RDS CALs cannot work with new RDSH servers, and you need to purchase new licenses. With newer RDS CALs, you can access older RDSH servers. Remote client devices that access the server must have a User CAL. The actual RDSH that hosts the resources must have a Windows Server CAL matching the OS version. Typically, the RD Session Host (RDSH) server hosts the resources-such as Windows applications or files-and clients connect to the RDSH to access those resources. If you want to provide access to users to an RDS Collection or RDS Components of a Windows Server operating system, you need to purchase additional licenses.
0 kommentar(er)
