Troubles in Active Directory with Windows Server 2016 and Windows 10

For several months I have the difficulty on Windows 10 clients that group policies are suddenly no longer read. 'gpresult -r' shows that the logged user no have RSoP Data. Deleting the files under C:\Windows\security\database\*.* also removing the entries under 'HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Group Policy\History' usually brings only short-term relaxation ...
Who has a tip for me?
Wolfgang FrickMCTAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Sekar ChinnakannuStaff EngineerCommented:
Whenever the issue arise are you getting trust relationship error? IS this happens to all computers or any specific machines?
Check on the machine which you have a problem should have allthese entries. To view yo uhave to use ADSIEDIT.
Please share and upload the outputfile.html of the following command which needs to be executed on an elevated command prompt on a client:
gpresult /h %temp%\outputfile.html

Open in new window

Shaun VermaakTechnical SpecialistCommented:
Running Symantec Antivirus? Either way, you need to exempt the correct files from your Anti-Virus
Determine the Perfect Price for Your IT Services

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!

Wolfgang FrickMCTAuthor Commented:
Many thanks at all. All your inputs are helpful, but I think it's a 'bigger problem' with Windows Server 2016 Standard and Windows 10 Pro/Enterprise both OS updated from August or later. We will see … We know this bad Windows 10 Version 1809!!!
You wrote "for several months", so the problems have been with the previous version as well, not only 1809. Be so kind and share your outputfile (on an elevated command prompt, run gpresult /h %temp%\outputfile.html) and I am sure we can make some progress.
Wolfgang FrickMCTAuthor Commented:
Thank you McMnife
You're right. My Lab has had Windows Server 2016 with newest Windows Updates and Windows 10 1803  with newest Updates.
Because I don't have had enough time, I build a new LAB with Windows Server 2012 R2 (inkl. all Updates) and Windows 10 1803 (updating 1808). And now: I don't have Troubles. Sorry, when I don't bringing your ordered gpresult-Report. I was under pressure on my workplace.
Alright. If you find your workaround suitable, you may close the question, now. We run 1803 and server 2016 since April now - no problems with GPOs (which we heavily rely on).

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
I did not solve your question, so you shouldn't accept it as solution, but rather you own comment with your workaround. You could request moderator attention to change your choice.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows 10

From novice to tech pro — start learning today.