Jump to content

Recommended Posts

Posted
I missed this part but have now done it for Exchange and Skype. This has had no effect on "Connected Services". I might check it is enabled on SharePoint as well

 

I just read I don't need to do this with SharePoint online after all

Posted (edited)
I just read I don't need to do this with SharePoint online after all

 

I think it is working. Not sure which of the steps fixed the issue.

 

In addition to those documented above I also logged onto SharePoint Online and ran Set-SpoTenant -OfficeClientADALDisabled $False

 

This had no effect to any accounts with an existing profiles on the PC.

 

I then deleted the profiles from the PC and each account that subsequently logged on got the Connected Services.

 

Thanks for the help will see how this replicates across the estate. It might be that we need to lower the profile deletion time if that is the prerequisite of it working

 

Going to add a caveat to this. If the machine has been activated using DBA all is ok. If the machine has office belonging to a user it still fails. I think we have some installs where office is belonging to a user as DBA has failed during the imaging of a PC or a user has some how taken over the license

 

Robbie

Edited by robbie-w
Posted
I think it is working. Not sure which of the steps fixed the issue.

 

In addition to those documented above I also logged onto SharePoint Online and ran Set-SpoTenant -OfficeClientADALDisabled $False

 

This had no effect to any accounts with an existing profiles on the PC.

 

I then deleted the profiles from the PC and each account that subsequently logged on got the Connected Services.

 

Thanks for the help will see how this replicates across the estate. It might be that we need to lower the profile deletion time if that is the prerequisite of it working

 

Robbie

 

Great to hear it looks like it is working - I was going to say the only other thing was that I setup the hybrid join over the summer as part of my annual windows 10 rebuild to the latest release, so all devices where fresh with no profiles.

Posted
Great to hear it looks like it is working - I was going to say the only other thing was that I setup the hybrid join over the summer as part of my annual windows 10 rebuild to the latest release, so all devices where fresh with no profiles.

 

I just found an 1809 client that it doesn't work on. The Office clients that were working were on 1810. Updating the "non working" computer and will feedback

 

Robbie

Posted
Updated the client to 1810 and all is working fine. I wonder if there is an issue with 1809?

 

Hard to say as I did not see any issues with clients on version 1809 - as mentioned I did my hybrid join over the summer what would have been using an older version, and no issues have been reported. It may just be as you did the hybrid join etc today that everything is syncing and updating the client forced the changes - fingers crossed all keeps going well :-)

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