DigiBen Posted April 15, 2016 Posted April 15, 2016 So I am trying to show the teachers all the wonderful things about Office 365...... yup...... and I cant even login to Office 2016 products with an Office 365 account?!? Has anyone had this problem? Zero errors, it just doesnt do anything. Asif it was accepted as the credentials, but just didnt sign in?
ModeratelyGruntled Posted April 18, 2016 Posted April 18, 2016 Check the registry hive below and change the value of SignInOptions. HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Common\SignIn https://technet.microsoft.com/en-gb/library/jj715259.aspx 1
DigiBen Posted April 22, 2016 Author Posted April 22, 2016 Still no luck sadly. Added HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Common\SignIn\SignInOptions as a DWORD, and set it to 0. But it had no effect. Still getting the "The background task activation is spurious" before I even type anything in. But I am not sure if this is relevant
win Posted April 22, 2016 Posted April 22, 2016 Works here with 2016 on a few test machines. Double check your licenses are issued correctly
synaesthesia Posted November 16, 2016 Posted November 16, 2016 Anyone else getting this background task activation is spurious message? Microsoft's latest remedy is still "click OK and ignore it", but for one of my users who is getting it constantly is getting more than annoying, very understandably! Everything is updated, windows 10 edu, office 2016 connected to the academy's Office 365. Tried all sorts with no luck
Sput Posted January 27, 2017 Posted January 27, 2017 We get this, and found that if you use a GPO to disable sign in to office it removes the spurious error, however we use onenote as a exercise book for Computer Sci, and it also stopped the OneNote 2016 Desktop application from working as that requires being signed into office. James
JasonNVSD Posted February 9, 2017 Posted February 9, 2017 Added HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Common\SignIn\SignInOptions as a DWORD, and set it to 0. But it had no effect. The key ModeratelyGruntled posted is for 2013. If you're deploying 2016, you would need to change 15.0 to 16.0. 1
MatthewL Posted February 9, 2017 Posted February 9, 2017 Does you firewall allow your computers to communicate to be able to sign into Office 365?
JasonNVSD Posted February 10, 2017 Posted February 10, 2017 Check the registry hive below and change the value of SignInOptions. HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Common\SignIn https://technet.microsoft.com/en-gb/library/jj715259.aspx It's not mentioned in the Technet article, but there's an equivalent to this in the Office Customization Tool, but it is was very hard to find: Features > Modify user settings > Microsoft Office 2016 > Miscellaneous > Block signing into Office. This policy setting controls whether users can provide credentials to Office using either their Microsoft Account or the user ID assigned by your organization for accessing Office 365. If you enable this policy setting, you can specify one of the following options: - If you select "Both IDs allowed", users can sign in and access Office content by using either ID - If you select "Microsoft Account only", users can sign in only by using their Microsoft Account. - If you select "Organization only", users can sign in only by using the user ID assigned by your organization for accessing Office 365. - If you select "None allowed", users cannot sign in by using either ID. If you disable or do not configure this policy setting, users can sign in by using either ID. Note: This policy does not apply to licensing. A user can license their product using any applicable ID if they have a valid license associated with that account. Providing credentials for licensing purposes when that ID type has been disabled, however, will not affect the signed in state of Office.
3s-gtech Posted February 11, 2017 Posted February 11, 2017 I recently changed this GP setting (block signing into Office) as our O365 is now up. Changing this setting was enough for it to work - we get a certificate revocation warning but that can be acknowledged. We also had to change another setting (Allow Office to connect to the internet) for it to work. Worth monitoring your filtering to see if a URL is being caught too.
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