![]() We only needed it for directAccess though. I ran into the same problem, the solution is actually simpler than I thought it would be. The only thing i've been able to find on the web is people adding Office into the image, and not the whole base process. I'm guessing the Office 2016 piece is easier, just install but don't open it, then when i log on the user for the first time i can activate it with their o365 account. Okay, great, but if I'm building the base image (which isn't a licensed user) how can i make sure its Enterprise enabled on the image. I also read that Win10 Enterprise is actually baked into Win10 Pro, you just need the license to turn on the features. Okay, but where do i get my downloads to build the images? Do i use the Windows 10 Pro media creation tool from the portal to download the ISO? What about the Office 2016 ISO's? How does this work with o365? They explained that licenses get applied when a licensed user logs in. I'm used to going to the VLSC and downloading the ISO's i need (windows 10 enterprise and Office 2016, putting the KMS key on our server, building the images, installing the software, and pushing it up to our WDS for deployment. My question is how does the imaging and such work for this? So we are transitioning from the traditional volume license (here's your iso / here's your key) to Office 365 Business for our end user MS licensing.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |