First, if the server is a "normal, everyday server" then, like a desktop, laptop, or virtual desktop, it counts as ONE license. However, if the server is "Citrix, RDS, or any Multi-Session Windows" serving multiple people on the same machine; then that usage counts as MULTIPLE licenses. See this two FAQs for details:

• General Citrix & Multi-Session Windows Licensing: https://www.policypak.com/purchasing/citrix-licensing-scenarios.html
• For Citrix + Cloud: https://kb.policypak.com/kb/article/972-how-do-i-license-my-citrix-rds-wvd-vdi-or-other-multi-session-windows-version-with-policypak-cloud/

That being said, you might want to license your "normal, everyday servers" for a variety of reasons. Here are some examples:

1. You can use PolicyPak Admin Templates Manager to reduce the amount of GPOs and then target them to specific servers. There are many, many use cases for this, but just one is Windows Update where you can take a bunch of GPOs and get them down to one. See this blog for details: https://www.policypak.com/pp-blog/windows-update-business. Then, here’s the video on how to perform reduction of existing GPOs: https://kb.policypak.com/kb/article/501-reduce-gpos-and-or-export-them-for-use-with-policypak-cloud-or-with-mdm/
2. You can use PolicyPak Admin Templates Manager to specify and lockdown settings for browsers and other applications when an admin logs on. Quick examples: https://kb.policypak.com/kb/article/518-what-is-policypak-application-manager-group-policy-edition/ and https://kb.policypak.com/kb/article/947-manage-internet-explorer-settings-with-policypak-application-settings-manager/
3. You can use PolicyPak Least Privilege Manager to block items that admins shouldn’t run. Example of blocking applications: https://kb.policypak.com/kb/article/748-policypak-application-control-with-pp-least-privilege-manager/
4. You can use PolicyPak Least Privilege Manager to reduce service account rights: https://kb.policypak.com/kb/article/804-reduce-or-specify-service-account-rights/
5. You can use PolicyPak Least Privilege Manager to block PowerShell except for where absolutely needed: https://kb.policypak.com/kb/article/792-block-powershell-in-general-open-up-for-specific-items/
6. You can use PolicyPak Least Privilege Manager to reduce the admin rights on specific processes or applications, like IE and others: https://kb.policypak.com/kb/article/163-07-can-i-use-policypak-least-privilege-manager-to-lower-remove-admin-rights-from-administrators-from-an-application-or-process-like-internet-explorer/
7. You can use PolicyPak Scripts Manager to perform specific logon scripts for specific servers using Triggers: https://kb.policypak.com/kb/article/943-policypak-scripts-and-triggers-get-to-understand-login-script-trigger-with-gp-and-mdm-systems/
8. You can use PolicyPak Scripts Manager to perform specific scripts like mapping a drive, or running another process when a parent process is launched: https://kb.policypak.com/kb/article/944-policypak-scripts-triggers-map-a-printer-or-drive-when-a-process-runs-and-un-map-it-when-closed/
9. You can use PolicyPak Admin Templates Manager and remove Loopback and specify specific user side settings for specific machines when any user (admin or otherwise) logs on to the machine: https://kb.policypak.com/kb/article/584-policypak-admin-templates-manager-switched-policies-without-loopback/

There are other uses, but those are the ones that most customers use.