[ms office - o365] Most features are turned off because a shared computer license isn't available

[CHiLL]

I've just deployed Office 365 to a number of machines using Shared Computer Activation (configured in the XML) and Office 365 is asking users to log in to license the product. If the user closes this, they receive a message stating that "Most features are turned off because a shared computer license isn't available.".

 

Have I used the wrong configuration in the XML? What is the best option to deploying Office 365 in classrooms/suites?

 

All of our users have the correct licenses assigned to them in Office 365.

Edited October 23, 2018 by CHiLL

[Boredguy]

When using shared Activation, you to either have SSO configured so the users can sign in automatically when the Office application launches, or get the user to enter their details manually so it can confirm if the user has the licence rights for it in the first place.

[CHiLL]

When using shared Activation, you to either have SSO configured so the users can sign in automatically when the Office application launches, or get the user to enter their details manually so it can confirm if the user has the licence rights for it in the first place.

We do have SSO configured, but I'm thinking I've used the wrong activation method. From what I'm gathering, Shared Activation is basically for RDS only.

[Boredguy]

It's available on any workstation, not just RDS.

 

We went down the Device Activation route as we had the A1 Plus licences (and we use accounts that do not always have Office 365 accounts)

[CHiLL]

It's available on any workstation, not just RDS.

 

We went down the Device Activation route as we had the A1 Plus licences (and we use accounts that do not always have Office 365 accounts)

So as a test, I changed the following registry entry on one the machines:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\ClickToRun\Configuration = 0

 

I rebooted the machine and logged back into an account I have confirmed has Office 365 ProPlus for Students and Office 365 A1 licenses assigned to it.

 

It still asked me to log in as that user. If I dismissed the login box, it did not show the shared computer license warning, but instead says it's running an unlicensed product that will expire on 28th October.

 

We have AD FS enabled (have done for a few years) and it currently works if a user uses Internet Explorer and browses to Office 365. They aren't prompted to log in, and are logged straight in automatically using SSO. We are using Azure AD Sync to syncronise our users with AD. Does Office use this, or does it need something else specific to be configured?

Edited October 23, 2018 by CHiLL

[CHiLL]

Update: After some research, apparently there can be issues when the UPN suffix being incorrect. So I've just checked the AD properties of the user I was using and found that it was set to our domain suffix, rather than our Office 365 one. I changed that amended the machine back to shared activation and rebooted the laptop and performed a sync Office 365. I then logged in with the test account and Office was automatically signed in and activated.

 

Update 2: I have two teachers that have the correct UPN suffix and it is asking them to sign in. When they sign in, it redirects to our ADFS login page, but says an error occurred when entering their passwords.

 

Update 3: One of the teachers only had an A1 license assigned. I have assigned the ProPlus license and it's worked.

 

I'm confused.

Edited October 23, 2018 by CHiLL

[3s-gtech]

Make sure that you're running the latest version of AADC. I updated ours last week after passwords stopped syncing across (error messages in Windows logs helped) - took quite a bit of working out though!