OVS-ES vs Microsoft 365 E3
Hello, We're taking the opportunity during these strange times to review our licensing agreements and decide whether we would be better off changing things around. However, I'm having trouble understanding exactly what is included in the Microsoft 365 E3 package. The details state that it includes Windows 10 and Server CALs, but does that mean that we could safely cancel our existing OVS-ES agreement and switch to licensing directly from Microsoft? In doing so, we would gain lots of management capabilities using InTune (and Endpoint Manager), but the cost would be so high that it will only work if we can offset it against not renewing our OVS-ES agreement. We already have Office 365 ProPlus included with our Office 365 A1 package, and recently switched to licensing Office using the shared computer activation feature, thereby foregoing our entitlement to Office 2019 ProPlus from the OVS-ES agreement. (There's a strange link here anyway.. I feel like we only get O365 ProPlus installation rights through O365 because of the OVS-ES agreement, though we would keep this benefit if switching to M365 E3 anyway so this seems elementary to me.) Why is MS Licensing so convoluted?! (Probably out of necessity, I know.. just makes it hard to properly compare options!)IT Pro in Education Career Profile: James van den Berg
We just featured a career profile of MVP JamesvandenBerg who focuses on Azure, Windows Server and many other technologies in the Education space. If you're interested on his take on what a successful career in the cloud looks like, read the post in the IT Resources & Training community here: https://techcommunity.microsoft.com/t5/IT-Resources-Training/Cloud-Career-Profile-James-van-den-Berg/m-p/56082#M102
Odd Powershell Errors when Adding / Removing Server Roles
Good afternoon! On a Windows 2019 Server, we needed to add the Active Directory Certificate Services role. However, during the Post-Deployment Configuration it fails with the error: The term 'Get-_InternalAdcsConfigurationState' is not recognized as the name of a cmdlet, function.script file, or operable program. We attempted to remove the role so as to start over, but it fails with the same error. At first I thought it was specific to the Server Manager app. However we have found the same expression "The term xxxx is not recognized as the name...." when attempting to perform other PowerShell Active Directory commands. Has anyone else experienced this? Regards ~ Mike
