SOLVED

Group Policy does not apply, when using AVD with Entra Domain Services

Brass Contributor

Good morning community,

 

we are facing some very critical issues while using Group Policys in combination with Microsoft Entra Domain Services.

 

The problem is, that the group policys do not apply anymore.

This leads to the problem, that there are no mapped network drives, no customer specific settings and so on.

 

Meanwhile, we´ve got three customers with the problem.

The problem first started in the beginning of april.

 

We already got three MS premier support-tickets, but the microsoft technicans got no clue, where the root cause could be found.

 

 

Since there are three customers impacted, we no longer believe, that we are the only ones, who are facing these issues.

Anyone else?

7 Replies
For a week now we're facing the same issue in different customer environments. MS support isn't really helpful. GPOs are working sometimes and sometimes they don't.

Would be great, if you could keep us informed if the problem could be fixed.
We have been struggling with the same error in a few customer environments for about a week. The GPOs work sporadically as you mentioned.
As with you, MS support has not been very helpful - 2 tickets without any success or feedback.

If anyone has a solution please let me know immediately.

Thanks a lot!

We are having the same issue since about one week. Microsoft support hasn't been particularly helpful so far.

Would appreciate any helpful suggestions.

 

Thank you!

@ChrisW 

 

What is your Domain structure so far? ADDS with AAD?

@Kidd_Ip Good morning, yes, exactly.

In the meantime we were able to identify FSLogix in the newest version 2.9.8884.27471 as the root cause. With FSLogix in Version 2.9.8612.6005602 the issue does not occur.

 

We are waiting for the feedback from microsoft regarding these news.

Current status: No response from microsoft to our ticket so far. We are still using FSlogix in Version 2.9.8612.6005602
best response confirmed by ChrisW (Brass Contributor)
Solution
After deploying the following registry key, everything works as it should.

DWORD GroupPolicyState = 0 under HKLM\SOFTWARE\FSLogix\Profiles\

I´ve got no idea, why it was able to use GPOs the last years without this key ..
1 best response

Accepted Solutions
best response confirmed by ChrisW (Brass Contributor)
Solution
After deploying the following registry key, everything works as it should.

DWORD GroupPolicyState = 0 under HKLM\SOFTWARE\FSLogix\Profiles\

I´ve got no idea, why it was able to use GPOs the last years without this key ..

View solution in original post