SysprepMe

For those still trying to use the older Device-Based Activation method with opptransition.exe, which according to Microsoft should still work, but for us had become very unreliable, here is a new version of opptransition.exe they shared with me. This has worked much better for us (although still not quite 100%): https://1drv.ms/u/s!Ap1UEodVD0yRj4Ne252E5UYor-3ZOw?e=pAhd2V

We're also seeing very inconsistent activations (usually doesn't activate) of Office365 ProPlus C2R at or district since August using the older device-based activation method (using OPPTransition.exe). Was working fine with no issues before that. Symptoms much like those posted here: -Office doesn't activate and prompts to login as the Azure device user _device_computername -No failures in the OPPTransition logs, but when activation fails there is no entry "product key added successfully" -An event log from the Office Licensing Service with an error basically saying there was no product key supplied -ospp.vbs /dstatus shows no product keys installed Did anyone find out anything from Microsoft about why this is failing now? Is this older DBA process on the way out? Do we need to implement the one they introduced in August with the different licensing and devices hybrid azure-ad joined? Any information would be helpful as our Microsoft partner seems to be in the dark as well. Thanks!