gromack

<div>
When people leave, change their passwords and disconnect any sessions. Then add the new person in their place. That should not affect licensing.
</div>


When people leave, change their passwords and disconnect any sessions. Then add the new person in their place. That should not affect licensing.

<div>
Office licenses on my remote access server are the ones I thought were tied to a particular user,
</div>


Office licenses on my remote access server are the ones I thought were tied to a particular user,

<div>
Microsoft corporate licensing counts the number of uses as was noted earlier. <br />
<br />
If you are using corporate licensing, no issue. <br />
<br />
If you are using &nbsp;subscription licensing, it is tied to the machine and so if you have the machine, still no issue.
</div>


Microsoft corporate licensing counts the number of uses as was noted earlier.

If you are using corporate licensing, no issue.

If you are using  subscription licensing, it is tied to the machine and so if you have the machine, still no issue.

<div>
No subscriptions. When setting this up, I was told that I had to have a license for each user that would connect. I have maybe 10 people who could connect, with never more than about 6 at any given time &amp;&nbsp;was told I needed 10 licenses.
</div>


No subscriptions. When setting this up, I was told that I had to have a license for each user that would connect. I have maybe 10 people who could connect, with never more than about 6 at any given time & was told I needed 10 licenses.

<div>
You never know who might connect when, so 10 licenses for 10 people is quite reasonable. Still, the licenses are not tied to specific individuals and can be reused for new people
</div>


You never know who might connect when, so 10 licenses for 10 people is quite reasonable. Still, the licenses are not tied to specific individuals and can be reused for new people

<div>
<div class="content wysiwyg-content">
We’ve recently had several sales people leave &amp;&nbsp;replaced with new ones &amp;&nbsp;I’m wondering how to handle my office licenses on my remote access server. How can I ‘free them up’ for the new users who have replaced the ones who’ve left?<br />
Also, I’m needing to give drivers email addresses for interacting with a driver related software. These users won’t be logging onto any other servers or using any other network resources, so is there an exchange only licensing option or do they need a server license &amp;&nbsp;then an exchange license on top of that?
</div>
</div>


We’ve recently had several sales people leave & replaced with new ones & I’m wondering how to handle my office licenses on my remote access server. How can I ‘free them up’ for the new users who have replaced the ones who’ve left?
Also, I’m needing to give drivers email addresses for interacting with a driver related software. These users won’t be logging onto any other servers or using any other network resources, so is there an exchange only licensing option or do they need a server license & then an exchange license on top of that?

Licensing questions...

Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.

Exchange

Windows 10 is a personal computer operating system featuring the "universal application architecture" (UAP); apps can be designed to run across multiple devices with nearly identical code, including PCs, tablets, smartphones, embedded systems, Xbox One, Surface Hub and HoloLens. Windows 10 also includes a virtual desktop system, a window and desktop management feature called Task View, the Microsoft Edge web browser, support for fingerprint and face recognition login, voice-based search (Cortana), new security features for enterprise environments, and DirectX 12 and WDDM 2.0 to improve the operating system's graphics capabilities for games.

Windows 10

Microsoft Azure is a cloud computing platform and infrastructure for building, deploying and managing applications and services through datacenters. It provides both platform-as-a-service (PaaS) and infrastructure-as-a-service (IaaS) services and supports many different programming languages, tools and frameworks, including both Microsoft-specific and third-party software and systems. Cloud Services is a PaaS environment and can be used to create scalable applications and services; there are specific software development kits (SDKs) provided by Microsoft for Python, Java, Node.js and .NET. Azure also has file and storage services, data management, analytics and DNS services.

Azure

Windows Server 2016 is the successor to Windows Server 2012 R2. Built upon the same core code as Windows 10, Windows Server 2016 brings enhancements in security, servicing, and connectivity. A particular focus on this release was hybrid-cloud scenarios, and has close ties to Azure and other Microsoft cloud initiatives. This does not detract from the many improvements that are available for on-premises-only deployments

Windows Server 2016 comes in Datacenter, Standard, and Essentials editions, and for servicing, has adopted windows 10's cumulative model. The new nano-server install is designed to be remotely managed and is designed to be kept current through continuous feature updates. The full GUI install operates similarly to windows 10's "Long Term Servicing Branch" (LTSB) model with cumulative security updates.

Windows Server 2016 has also shifted from a per-processor-and-CAL licensing model to a per-core-and CAL licensing model. This brings Windows Server's licensing more in line with Microsoft's other products and makes hybrid-cloud license planning easier as well.