You'd also need to automate their removal when the VMs are spun down and dismantled to prevent old VMs from hogging all the licenses.

But in that case your VMs stop being ephemeral unless you automate the process of domain joining them and placing them in the appropriate Azure AD group when the VMs are created. You would need Office 2016 or 2019 for this use case. I don't believe you're able to activate Office 365 with KMS. I've learned how to set up Office 365 on a non-persistent desktop, and I've been able to figure out how to set up a general KMS server, except my question is now, how do I get them to talk to each other? How do I get the KMS server to authenticate 365 every time a new VM is spun up? I'm trying to replicate this in a virtualbox environment on my home system, but having trouble figuring it out. I like to think of myself as capable, I'm very resourceful and obviously the network team is more than happy to help, but I want to try to prove I can do this without them having to hold my hand. Just yesterday, I was asked to take ownership of setting up the VM desktop and configuring/deploying a KMS server to activate 365 on the desktops, sweet! Except now, I kind of feel a bit over my head since I've only been studying this stuff a couple of hours every week for the past 2 months or so. We're currently working on setting up our new VMWare desktop environment and they asked me to be part of the team to which I gladly accepted. I haven't been putting too much pressure on myself, as I'm not in a rush because I'm still learning more and more of our system every day.Īnyway, I have a good relationship with the network admin team and they know of my desire to learn more and advance. Over the past couple months I've decided I want to pursue the sys admin path, and I have been studying when I can. Hey all, so I've been working Desktop Support at my current company for the past year, started as an intern and have been full-time since beginning of the year.

Office 365 pro plus activator kms