J_Bolton
asked on
Sharepoint - Open with Explorer Issue (Only working with non-domain joined machines)
I have tried everything I can google to get our SharePoint 2013 Foundation Server to allow - Open with Explorer.
This used to work in the past but has since stopped.
The item I hope will give somebody some attempt to assist me to resolve is - this function will work with a non domain joined computer. All domain joined machines will no longer allow it and throw up the error - add to Trusted Sites which makes no difference.
This used to work in the past but has since stopped.
The item I hope will give somebody some attempt to assist me to resolve is - this function will work with a non domain joined computer. All domain joined machines will no longer allow it and throw up the error - add to Trusted Sites which makes no difference.
Ensure all updates are installed (client/server)
Added to trusted sites (seems you have done that)
Ensure Web Client Service is running (client)
Added to trusted sites (seems you have done that)
Ensure Web Client Service is running (client)
ASKER
Yep, using IEx32 and all updated, trusted sites added and web client running
If you running SSL try the following. We had a simular issue and this was the fix for us.
http://stephenmoody.net/2014/09/fix-for-open-with-explorer-in-sharepoint-2013/
http://stephenmoody.net/2014/09/fix-for-open-with-explorer-in-sharepoint-2013/
ASKER
I thought you were going to have the solution for me, but not binding https.......
The search goes on......
The search goes on......
You mention two points that are important.
Seems if a group policy was recently applied to Domain machines that broke this. Check with the System Admin to see what recent GPO changes were applied. If there is a new policy being applied that broke this, maybe they can resend the policy and return your functionality.
Good luck...
- One - this just broke recently,
- Two - this works with non-domain machines
Seems if a group policy was recently applied to Domain machines that broke this. Check with the System Admin to see what recent GPO changes were applied. If there is a new policy being applied that broke this, maybe they can resend the policy and return your functionality.
Good luck...
ASKER
The only thing that changed is we introduced 2 new 2016 domain controllers. We haven't raised the functional level of AD though yet.
HI,
it definitely sounds like a GPO,
You can run this command from an administrative command line
gpresult /H c:\users\<myUserName>\desk
then you can open gporeport.html to see the settings that are getting applied to your machine and your account and by which GPO
it definitely sounds like a GPO,
You can run this command from an administrative command line
gpresult /H c:\users\<myUserName>\desk
then you can open gporeport.html to see the settings that are getting applied to your machine and your account and by which GPO
This question needs an answer!
Become an EE member today
7 DAY FREE TRIALMembers can start a 7-Day Free trial then enjoy unlimited access to the platform.
View membership options
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Good luck...