Jump to content

Recommended Posts

Posted

Did you guys have to do anything else or talk to anyone to get the A1 Plus for Students licenses assigned?

 

We supposedly got added to the Educational list earlier this week but when I self enroll a test student account they just get assigned the A1 for Student (*non* Plus) licenses.

Posted
Did you guys have to do anything else or talk to anyone to get the A1 Plus for Students licenses assigned?

 

We supposedly got added to the Educational list earlier this week but when I self enroll a test student account they just get assigned the A1 for Student (*non* Plus) licenses.

 

It took me a couple of weeks plugging away at support for it to eventually happen and even then it wasn't working as expected until I connected to our tenant in Powershell:

 

Import-Module MSOnline
$UserCredential = Get-Credential
Connect-MsolService -Credential $UserCredential

 

And then ran:

 

Set-MsolCompanySettings -AllowEmailVerifiedUsers $true

 

Once that was done it started to work.

  • 3 months later...
Posted
Shared Activation uses the logged on users credentials to activate the office session. So if you have a user that does not have any Office 365 licence, you might find that it says it is not activated.

 

Device Activation creates a computer account in 365 with the A1 Plus for Students licence and does not worry about what licence the current user might have.

 

Both methods are perfectly valid.

 

For shared activation where do I find the activation's in O365 admin?

 

I've tested 3 installs and am planning on rolling it out for staff, but want to make sure all of sudden they all don't activate or lose activation randomly.

Posted
I don't think you can with shared activation. Device Based Activation creates a user in AzureAD. Though I found I used a compliance item in SCCM to monitor it in case it got.l licenced against a user.
  • Thanks 1
Posted
For shared device activation the user activates the install on log in. A token is generated and stored in the profile for (I think) 30 days to prevent the requirement for reactivation. This is only valid for that user on that device. If they don't have a valid 365 licenced account, Office isn't activated.
Posted
Is device based activation now supported in the UK? And if not, is the process you're using the same as in territories where it is supported or does it rely on workarounds?
Posted
Is device based activation now supported in the UK? And if not, is the process you're using the same as in territories where it is supported or does it rely on workarounds?

 

We’ve been running it for a few years now in the UK

Posted
Yep I've tun it for just over a year. It's just the script and compliance items I had to tweak. If you reimage PCs a lot I have to run the script to force dba.
Posted
We’ve been running it for a few years now in the UK
Thanks - I've seen the threads on here about how. I just thought it was officially US only and that's why it's so complicated to make it work in the UK.
Posted
It's a bit inconstant as I actually submitted a ticket to MS about using it on RDS and they recommended Shared for RDS and Device for normal Windows 10. I get the occasional 1st launch on RDS say its not licenced but a close and reopen fixes it. I have User Profile Disks deployed so the token roams. If MS really insist it's OK only it wouldn't be too much work to switch to shared licensing. But the token would have to roam. You also don't know what the device activation count is or what MS allow.
Posted
I don't think you can with shared activation. Device Based Activation creates a user in AzureAD. Though I found I used a compliance item in SCCM to monitor it in case it got.l licenced against a user.

 

SCCM tells me 3 is installed, am happy to license against the user for staff. All have there own laptop and just needs to keep access to the internet to stay activated?

 

That's OK for me.

  • 6 months later...
Posted

I've had this working fine & activated on over 300 odd computers, but since yesterday my clients are all failing with

 

"21:57:27 | Exception: License unavailable - GetLicense - early exit"

 

I've allowed the change listed on the FAQ but with no joy - Only thing is that my Microsoft Agreement has changed (New term) so I have a new agreement number, tho I'm still listed with A1 Plus licenses - Has anyone else had to re-regster with microsoft?

 

Thanks

Posted

... so what's the betting this is why my DBA license stuff is broken?

 

https://educationblog.microsoft.com/en-us/2019/08/attention-it-administrators-announcing-device-based-subscription-for-education/

 

Old DBA was US only, tho when I contacted MS they gave it to us (and multiple others on here) so I'd put money on the fact that MS have invalidated all our previous tenant activations and now we have to apply via our resellers.

 

Grr....

Posted
... so what's the betting this is why my DBA license stuff is broken?

 

https://educationblog.microsoft.com/en-us/2019/08/attention-it-administrators-announcing-device-based-subscription-for-education/

 

Old DBA was US only, tho when I contacted MS they gave it to us (and multiple others on here) so I'd put money on the fact that MS have invalidated all our previous tenant activations and now we have to apply via our resellers.

 

Grr....

 

According to that (right at the bottom on the last Q&A) it says:

 

“Device must be Azure AD joined or Azure AD Hybrid joined.”

 

Most of my devices that use DBA are currently not.

Posted
I think at some point you have to move to hybrid device join. If your organisation has moved to Microsoft 365 licensing Windows 10 can be licensed by subscription so I guess this is similar.
Posted

I've done a bit of work on this.

https://docs.microsoft.com/en-us/deployoffice/device-based-licensing

 

You need hybrid join working.

You need to contact you reseller to ask to add the "Office 365 ProPlus for Education (device)" licence to your tenant.

 

https://docs.microsoft.com/en-us/Office365/Admin/misc/manage-licenses-for-devices?view=o365-worldwide

 

You need to add this line to you configuration.xml which Setup.exe calls . I haven't yet found the registry setting for "Use a device-based license for Office 365 ProPlus".

Posted
Weird, after a week of devices failing I've just done a test machine and it's gone through ok - Let me test a few more & update

 

I've been waiting about 4+ weeks for the correct device licences to be applied to our tenant via O365 support, I do hope its going to work otherwise falling back to Office 2019 deployment...

Posted
I've done a bit of work on this.

https://docs.microsoft.com/en-us/deployoffice/device-based-licensing

 

You need hybrid join working.

You need to contact you reseller to ask to add the "Office 365 ProPlus for Education (device)" licence to your tenant.

 

https://docs.microsoft.com/en-us/Office365/Admin/misc/manage-licenses-for-devices?view=o365-worldwide

 

You need to add this line to you configuration.xml which Setup.exe calls . I haven't yet found the registry setting for "Use a device-based license for Office 365 ProPlus".

I've got the licences in place now. But it's not working on my test VM. I've got a ticket open with MS. I may need to try a clean VM where office was never activated.

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 account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...