Jump to content

Recommended Posts

Posted

I'm currently testing our almost ready to deploy Windows 10 Edu 1903 build (previously we've been on 1607 LTSB for years without issue)

 

Office is installed during deployment via our WDS/MDT setup, exact version is Office 365 MSO (16.0.11929.20288) 64-bit

 

When opening Office for the first time my test user encounters quite a few screens to click through, interested to find out how many of these are seen in a "normal" environment.

 

Firstly the user is presented with a sign-in screen.

 

1. signin.jpg

 

 

Then a screen about "Use this account everywhere on this device"

 

2. everywhere.jpg

 

 

The device then seems to "register"!

 

3. register.jpg

(Where would I see this registration?)

 

 

Then the user gets confirmation.

 

4. ready.jpg

 

 

The user then gets a privacy message.

 

5. privacy.jpg

 

 

Then default file types need to be chosen.

 

6. defaultfiletypes.jpg

 

 

 

On brief testing it looks like the user gets none of the above screens on subsequent logons to the test PC. Not sure what messages might appear on first logon to another device as of yet!

 

Any guidance much appreciated.

 

Cheers

Posted (edited)
Set up Azure AD Connect Seamless SSO to remove some of that, and GPO should remove more, don't have exact details because LibreOffice

 

Hi,

 

We do have Azure AD Connect installed on one of our DC's, currently when you launch the email shortcut you have to enter your email address the first time and then it signs you straight in, subsequent times you just click on your email address from the list.

 

emaillogon.JPG

 

 

Even if you've signed in to Office 365 for email then launch say Excel on my new W10 Edu build, you are still presented with the "Sign in to setup Office" screen :( - which seems to be an activation !

 

activeoffice.JPG

Edited by kennysarmy
Posted

You've probably read it but bumped into this the other day :

 

https://docs.microsoft.com/en-us/deployoffice/deploy-office-365-proplus-as-part-of-an-operating-system-image

 

(Was reading https://docs.microsoft.com/en-us/deployoffice/deploy-office-365-proplus-by-using-remote-desktop-services - there might be something you can use for licencing in the config files, as I've just deployed this on the RDS setup and it only prompts once, rather than on each application)

  • Thanks 1
Posted
The Seamless SSO means if you go to your domain's office login page you're auto signed in, and I think if that's true, then it's also true for local O365 installs
Posted
Hybrid Azure AD Join got rid of the "Use this account everywhere on this device" screen on Store apps, may be similar for this too
Posted
Hybrid Azure AD Join got rid of the "Use this account everywhere on this device" screen on Store apps, may be similar for this too

 

Managed to crack getting my new Windows PC's to appear in Azure AD 'Hybrid Azure AD joined'

 

:)

Posted
Hybrid join will sign you into office but will not activate office automatically, how are you currently activating office?

 

Not currently activating it seems - still getting my head around it all.

 

Much more complicated than Office 2016 and Active Directory Based Activation.

 

 

Just been doing a bit more research and came across this:

 

You can leverage the “Use a device-based license for Office 365 ProPlus” policy setting in the admin template to set the appropriate reg key. This policy setting can be found under Computer Configuration\Policies\Administrative Templates\Microsoft Office 2016 (Machine)\Licensing Settings. The correlating registry key is HKLM\SOFTWARE\Microsoft\Office\ClickToRun\Configuration\O365ProPlusRetail.DeviceBasedLicensing with a value of “1”.

Posted
You will also need the addon license - no license and of course will not activate, on top of hybrid join you also need to create a group in Azure AD / assign the addon license to the group and add the devices you would like to use with device based activation
  • Thanks 1
Posted
Switch to LibreOffice, easier to install, easier to activate, easier to buy.

 

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

 

So for device based you need hybrid AD joined machine, and Win10 1803 or later

 

 

From what I'm reading I also need a new licence !

 

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

Posted
You will also need the addon license - no license and of course will not activate, on top of hybrid join you also need to create a group in Azure AD / assign the addon license to the group and add the devices you would like to use with device based activation

 

Yea, I'm getting there!

 

Sorted out Hybrid AD yesterday.

 

Created a test Azure group this morning.

 

But now I find I need a new licence :( - fired an email off to Capita who we use for licences to find out the next hoop to jump through!

  • 8 months later...
Posted

For the Device Based Activation you have to assign the license in Office 365 Admin portal (Now Microsoft 365 admin center (https://admin.microsoft.com/Adminportal/Home?source=applauncher#/homepage) to a Azure AD group and the device object be it Azure Hybrid or Full Azure Join has to be in that group. Note there can only be 1 group for this assignment.

 

If you are using User authentication and after they log into an Office 365 app and still get requires activation then they most likely they have a A1 and not a A3/5 license. An A3/5 license is required for the full Office 365 apps A1 only gives you the web apps. The assigned user license is checked in the Office 365 Admin portal

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...