- Not keeping track of end customer licenses. Your sellers need to remind your customers of license mobility. Yes, your customer may have active software assurance when they first bring licenses into your datacenter, they have to maintain software assurance. It does expire.
- Office 365. Hosting O365 without QMTH on shared infrastructure. Don’t do it.
- Not having rules in place that prohibits and engineer from installing whatever they want to install. Your engineer installs SQL Enterprise out of convenience but you thought it was SQL Standard. Guess what? You owe for SQL Enterprise.
- Reporting usage just to report usage. Reporting needs to used as business intelligence. In the above example, if you report incorrectly, you are not charging your customers correctly.
- Not having a tool in place to help support and track your licenses. Check out www.octopus.cloud
If you are going through an audit, reach out to us. I know the audit process well and our team can help!
info@splalciensing.com
Thanks for reading,
SPLA Man
SPLA Licensing 
Lucelvi Melo
November 4, 2021 at 10:39 am
Hello and thank you for your Blog, it’s very helpfuly. I have a doubt… I have 2 Host, the first one with many VMs runningt and the second one with many VMs off. Do I have to report both hosts or just one?
Many thank you.
MS Licensing
November 15, 2021 at 4:47 pm
Always report the physical host. Datacenter you get to run unlimited VMs though 🙂
Steve
May 18, 2022 at 8:12 am
Hey, can I use a MS Windows Server retail license and offer Services (for example Exchange, RDS) licensed as SAL via SPLA? So mixing Retail and SPLA licenses??
MS Licensing
May 26, 2022 at 10:59 am
No. Windows Retail does not allow hosting