robyholmes Posted October 15, 2019 Posted October 15, 2019 Dear god what have I gotten in to. So I'm pretty new to SCCM so that might be my problem. But I've go to the Office 365 area in software inventory and followed the setup wizard for Office 365. However, the 'Device Based Activation' toggle is greyed out. Is this the right way to go about it and if so, how do I set DBA? I've emailed by Microsoft reseller to enquire about the licences themselves.
free780 Posted October 15, 2019 Posted October 15, 2019 Dear god what have I gotten in to. So I'm pretty new to SCCM so that might be my problem. But I've go to the Office 365 area in software inventory and followed the setup wizard for Office 365. However, the 'Device Based Activation' toggle is greyed out. Is this the right way to go about it and if so, how do I set DBA? I've emailed by Microsoft reseller to enquire about the licences themselves.I just used the latest version of https://docs.microsoft.com/en-us/deployoffice/overview-of-the-office-2016-deployment-tool#download-the-office-deployment-tool I edited the xml file. It may be if SCCM isn't on the latest or supports the feature yet.
robyholmes Posted October 15, 2019 Posted October 15, 2019 I just used the latest version of https://docs.microsoft.com/en-us/deployoffice/overview-of-the-office-2016-deployment-tool#download-the-office-deployment-tool I edited the xml file. It may be if SCCM isn't on the latest or supports the feature yet.I finished the SCCM wizard then edited the xml file to enable DBA. Hopefully that's all that's needed.
free780 Posted October 15, 2019 Posted October 15, 2019 There was another reg setting needed for DBL and the AzureAD side.
robyholmes Posted October 16, 2019 Posted October 16, 2019 There was another reg setting needed for DBL and the AzureAD side. To enable it on existing installations or on a new installation?
robyholmes Posted October 16, 2019 Posted October 16, 2019 Ok so I've heard back from my reseller about the licences. There only available for EES customers (IE more than 500 staff). So my question now is, what options do I have for licencing Office 365? Is it 'Shared Activation'? How does that go on if we need non-licenced users to use Office? Or do I cope out and deploy Office Pro 2019? Microsoft Licencing!!! Grrr
sparkeh Posted October 16, 2019 Posted October 16, 2019 Ok so I've heard back from my reseller about the licences. There only available for EES customers (IE more than 500 staff). So my question now is, what options do I have for licencing Office 365? Is it 'Shared Activation'? How does that go on if we need non-licenced users to use Office? Or do I cope out and deploy Office Pro 2019? Microsoft Licencing!!! Grrr Eh!? Which licences? The deal is, if you have Office volumed licenced through OVS-ES (no matter what the FTE count is) then you can use the 365 ProPlus licences AND you have the free 365 A1 licences then you are entitled to the 365 A1 Plus licence that enables the DBA. Resellers are nothing to do with the A1 Plus licence. It *should* happen automatically but doesn't always. (Or have I read your post wrong)
free780 Posted October 16, 2019 Posted October 16, 2019 https://docs.microsoft.com/en-us/deployoffice/device-based-licensing I meant this reg add HKLM\SOFTWARE\Microsoft\Office\ClickToRun\Configuration /v O365ProPlusRetail.DeviceBasedLicensing /t REG_SZ /d 1
robyholmes Posted October 16, 2019 Posted October 16, 2019 Eh!? Which licences? The deal is, if you have Office volumed licenced through OVS-ES (no matter what the FTE count is) then you can use the 365 ProPlus licences AND you have the free 365 A1 licences then you are entitled to the 365 A1 Plus licence that enables the DBA. Resellers are nothing to do with the A1 Plus licence. It *should* happen automatically but doesn't always. (Or have I read your post wrong) The licence I'm referring to is from this page: https://docs.microsoft.com/en-us/deployoffice/device-based-licensing So your licencing the PC/device rather than the user. Which means non A1 Plus licenced users can still use Office 365. We have A1 Plus licenses already on all our staff and students. However visitors who use are system do not. So if I deployed Office 365, my understanding is these users wouldn't only be able to open documents and not save. I also need to avoid the 5 activation limit which A1 Plus has, as we're not 1to1 for devices. However I think there's a middle ground using 'Shared Activation' but I'm not sure?
robyholmes Posted October 18, 2019 Posted October 18, 2019 So I've deployed the software using the Shared Computer Activation method but I'm concerned that this means any visitor accounts we create who don't have emails and thus, licences can't use office. How are people getting around this issue? I had hoped that once office was activated it would stay like that for x amount of days, meaning less chance of a visitor getting the requested login for a licence. However it looks to ask every time. I could give visitors a Office 365 licence using the Student one but I don't really want to be managing emails for them etc. Is this what other people are doing?
mullet_man Posted October 21, 2019 Posted October 21, 2019 So I've deployed the software using the Shared Computer Activation method but I'm concerned that this means any visitor accounts we create who don't have emails and thus, licences can't use office. How are people getting around this issue? I had hoped that once office was activated it would stay like that for x amount of days, meaning less chance of a visitor getting the requested login for a licence. However it looks to ask every time. I could give visitors a Office 365 licence using the Student one but I don't really want to be managing emails for them etc. Is this what other people are doing? I have a supply/visitor account we use for guests,supply or visitors. It only gets used every now and then. It is a pain making sure everyone does have a license but only ran into the problem a few times on random accounts we have such as a calendar user we have which holds calendars for various meeting rooms.
robyholmes Posted October 21, 2019 Posted October 21, 2019 I have a supply/visitor account we use for guests,supply or visitors. It only gets used every now and then. It is a pain making sure everyone does have a license but only ran into the problem a few times on random accounts we have such as a calendar user we have which holds calendars for various meeting rooms. We've gone down the route of having a guest account per visitor so we can track web usage and provide BYOD wireless using Radius. So I'd need to assign licences (Which can be done via Azure) to new visitor accounts but I'd need it to have synced before they can login. However staff don't tend to let me or the office know in advanced which doesn't help. Hmmm, shame BDA isn't allowed for OVES customers! Not sure what Microsoft are thinking there.
free780 Posted October 21, 2019 Posted October 21, 2019 I think your not supposed to technically use generic accounts on Office 365. But it happens.
mullet_man Posted October 22, 2019 Posted October 22, 2019 I think your not supposed to technically use generic accounts on Office 365. But it happens. Yeah they just so that they can use office when we have supply in using a laptop last minute.
sparkeh Posted October 24, 2019 Posted October 24, 2019 So I've been deploying Office again today and did run into a small problem. Reimaged machine were failing to activate Office via the OPPTransistion.exe DBA method (asking for user sign in and serial key) but new machines were ok. Solved the reimaging problem by logging into 365 admin area, going to the device's user records and deauthorising the office activation for each device. Those machines then activated fine. So the OPPTransistion method is still working for us but, for some reason, we now seem to have to remove the activation from within 365 to reinstall and reactivate. Which is a bit annoying really.
free780 Posted October 25, 2019 Posted October 25, 2019 I ended up deleting the user account for the device when it was working for us. I'm currently trying the new method on about 100 PCs. The main issue is getting the Hybrid Join and Co management correct. This is a lot better on 1809 but if it fails for any reason you have to delete the device from AzureAD and wait for it to rejoin on the device level which is now supported in SCCM and GPO.
RobFuller Posted October 28, 2019 Posted October 28, 2019 (edited) OK I now have Device Based Licencing functioning on Hybrid Devices. Make sure you update your ADMXs and enable the new policy. @free780 Which licence did you apply to the device? The Microsoft documentation isn't very clear " assign the appropriate licenses to that group." https://docs.microsoft.com/en-us/deployoffice/device-based-licensing My re seller advised it was the AADPEDUP1OpenStuUseBnft ShrdSvr licence which is only showing AADP EDU P1 Open StuUseBnft in my volume licencing Portal under Azure Active Directory which I have applied to our tenant. Thanks Edited October 28, 2019 by RobFuller
sparkeh Posted October 30, 2019 Posted October 30, 2019 After extensive testing of OPPTransistion and DBA I have concluded that it no longer works for newer versions of the 365 source. For example, deploying version 16.0.10228.20080 works flawlessly yet version 16.0.12026.20344 has lots of issues (for example won't activate as part of an SCCM OSD TS and requires running of the OPPTransition manually after OSD completes and needs the device record clearing from 365 if redeploying). Therefore you can still deploy an old version of 365 with OPPTransition and DBA and just let it update to the latest version.
KevinB Posted October 30, 2019 Author Posted October 30, 2019 I've never been able to get the OPPTransition method to work as part of an OSD TS and have always had to deploy Office 365 as a separate application (but still using OPPTransition) from Config Manager which has worked so far.
smarties11 Posted October 30, 2019 Posted October 30, 2019 That's interesting @sparkeh. We deploy 16.0.11029.20079 (December 2018 Monthly) and like you have had no issues when it comes to activation as part of the TS whether it's a new machine or a re-image. I was actually thinking that I should update the source soon but sounds like we're better off leaving it as is and let it update to the latest approved update in SCCM. @KevinB - this might be due to SCCM task sequences running under the 'Local System' identity. If you're behind a proxy this account will be unknown to it - make sure you have the URLs that OPPTransition.exe uses whitelisted on your proxy so they can be accessed by all users including unauthenticated users. This tripped me up for a little while when I first set it up.
KevinB Posted October 30, 2019 Author Posted October 30, 2019 Thanks @smarties11 I did have trouble initially with proxies but everything in Microsoft's recommended whitelist is globally whitelisted and set to bypass the proxy. It's not a big deal, O365 deploys automatically once the machine registers with SCCM anyway so I'm happy to work around it that way
free780 Posted October 30, 2019 Posted October 30, 2019 I also deploy the latest monthly version. So new features are ready and security updates are complete. As a cloud platform I guess you need to keep current. I have a script that updates my source files to the latest monthly updates and updates the SCCM content.
SysprepMe Posted November 11, 2019 Posted November 11, 2019 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 3
sparkeh Posted November 12, 2019 Posted November 12, 2019 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 @SysprepMe IT WORKS! It actually works. 365 v1910 activates with DBA using that version of OPPTransition!! Thanks so much for that. Did MS Support give you that version? Its interesting as the version you linked is v1.1.15.106 whereas the latest version available from http://aka.ms/OfficeDbaClient is v1.1.12.19 (which doesn't work). In fact the 1.1.15.106 version informs you that an 'updated' version is available to download (1.1.12.19!!) I guess that all our issues are down to MS not updating the download to the current version.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now