GPO User Policy not applied when using FSLogix profile container used

Question

I"m setting up an RDS farm with server 2016 and trying out FSLogix Profile containers without any success.

The user's FSLogix profile disk is created and mounted as expected and the user is able to log into the RDS session server.

However, the user portion of GPO is not applied. If you type "gpresult /v" the result is:

INFO: The User does not have RSoP data.

If I log into the same RDS session server with a user that is in the FSLogix exclude list, no profile disk is mounted, and the user portion of the GPO is processed correctly as expected.

What's going on and how do I fix this? If i cannot push GPO User Policy when using FSLogix profiles, i don't see how they are useful at all, so obviously i must be missing some basic configuration.

Answer 1

I"m setting up an RDS farm with server 2016 and trying out FSLogix Profile containers without any success.

The user's FSLogix profile disk is created and mounted as expected and the user is able to log into the RDS session server.

However, the user portion of GPO is not applied. If you type "gpresult /v" the result is:

INFO: The User does not have RSoP data.

If I log into the same RDS session server with a user that is in the FSLogix exclude list, no profile disk is mounted, and the user portion of the GPO is processed correctly as expected.

What's going on and how do I fix this? If i cannot push GPO User Policy when using FSLogix profiles, i don't see how they are useful at all, so obviously i must be missing some basic configuration.

This is not an issue that I have seen before or have had reported.  We will need to collect logs, and investigate to understand what is happening.  Have you opened a support case yet?  That would the right way for us to get the needed information.

Answer 2

I'm experiencing somewhat similar behavior, although in a VMware Horizon Windows 10 2019 LTSC environment.

In general a user enabled for FSLogix will get the "INFO: The User does not have RSoP data".  However I've noticed that if I actually implement a new user GPO, on that first logon, the RSoP will generate successfully.  I do get a success event ID 1503 that seems to prove it as well.  On subsequent logons I get the error about not having RSoP data.  In my case though I haven't observed that it isn't actually applying policy though since I get a success event ID 1501 normally or a 1503 when I have made a change to policy.

It does appear to be related to FSLogix as I can't reproduce this behavior either when profile disk is not mounted.

Answer 3

We have the same with Windows 10 1809 build in a VMWare Horizon environment. 

Answer 4

I'm experiencing somewhat similar behavior, although in a VMware Horizon Windows 10 2019 LTSC environment.

In general a user enabled for FSLogix will get the "INFO: The User does not have RSoP data".  However I've noticed that if I actually implement a new user GPO, on that first logon, the RSoP will generate successfully.  I do get a success event ID 1503 that seems to prove it as well.  On subsequent logons I get the error about not having RSoP data.  In my case though I haven't observed that it isn't actually applying policy though since I get a success event ID 1501 normally or a 1503 when I have made a change to policy.

It does appear to be related to FSLogix as I can't reproduce this behavior either when profile disk is not mounted.

Thank you!  This is not something we have seen before. We will need get some repro information on this, and put someone on it.  I would recommend opening a support case for it so that we can get an engineer assigned to the investigation.

Answer 5

We have the same with Windows 10 1809 build in a VMWare Horizon environment. 

I have logged an internal bug for investigation.  But a support ticket would help us raise the priority on it.  Thank you!

Answer 6

We see the same problem on our Windows Server 2019 Remote Desktop server, using FSLogix Profile Containers.

Best regards,
Dennis.

Answer 7

 I have logged an internal bug for investigation.  But a support ticket would help us raise the priority on it.  Thank you!

I just created a support case.

Best regards,
Dennis.

Answer 8

We have the same issue within a Windows Server 2016 RDS environment. All policies seem to work, both user and computer policies. However, the following error appears when FSLogix is active. 

Answer 9

Hi,

Any updates on the case?

I use Horizon with AppVolumes, DEM and FSlogix.

When I turn on FSlogix profile, first login is working as expected.

Second one, after opening profile VHD - breaks user GPO -> no other settings are processed.

Is there any patch availabe?

Regards

Michal

Answer 10

Exactly the same issue;

RDS 2016 environment, using FsLogix Profiles

First logon with a user works as usual, subsequent logons - RSoP fails.

PS C:\Windows\System32\WindowsPowerShell\v1.0> gpresult /v
INFO: The user does not have RSoP data.

Answer 11

Hi!!!

Any progress with support cases? I've created one on VMware side - still waiting...

Regards

Michal

Answer 12

I have tested it on two different 2016 Rds' -> same issue

Tested in our 2019 test rds -> no issue

Answer 13

I am seeing exactly the same issue. I have raised a support case with MS. I thought I was going mad thinking I was unique in this situation until I came across this thread. There is very little out there on this which surprises me.

Answer 14

We have created a support case too.

Im seeing the same issue on server 2019 as well.

Answer 15

Hello,

Any update from Microsoft? We are having the same problem - RDS 2016 with latest FSL build. If we do a 'gpupdate /force /target:user' from within the affected session, the policies *DO* get applied again, and then break on the next login. 

Thank you,

~Tim

Answer 16

Hello, is there any update from Microsoft on this yet?

Thank you,

~Tim

Answer 17

My support case is quite frankly next to useless. It's as if they don't believe it is happening.

I will keep pushing though.

Answer 18

I'm also having the same problem.

We are running a Citrix VDA Farm with FSLogix Office and Profile Containers configured on Server 2019.

If I run gpresult against my standard user account or run the GP Result Wizard on the DC then I get one of two things:

1. gpresult - When I run gpresult /h I get "Error: Invalid Pointer and the file is empty"

2. Wizard - Either the User details section is blank OR "An error occurred while generating report: Object reference note set to an instance of an object."

I get the same result with multiple users on multiple Citrix servers, even after a reboot.

If I add the user to the FSLogix Profile Exclude group on the local server, gpresult and the Wizard report correctly.

This is also the case for my admin account that is in the exclude group by default.

It would appear that gpresult cannot retrieve the correct information when the profile is redirected into the VHD(X) file.

I tried the gpupdate /force /target:user option and this does resolve the problem until the next log on as Tim suggests. I am able to view the output from the gpresult command immediately after running the gpupdate however it is missing the folder redirection data I am trying to view because I need to log off for that to apply.

Answer 19

I am also seeing these behaviors. User GPO's neither show nor apply when FSLogix disks are mounted at login, but delete those, and user gets user GPOs, until the second login. Obviously, deleting the VHDs and tossing the profile isn't a sustainable business practice when we need to make changes to user specific GPO settings. Where are we on a fix for this?

Answer 20

did you try to get back to the basics; only set profile to enabled and tell it where to put the profile? I think people might get caught up in the intresting options the GPO templates give us. More documentation is needed imho

Answer 21

I'm not facing this issue so far - since I was busy finding a workaround to export local profiles (frx.exe not working, PS Modules provided by MS worked somewhat) - just be aware FSLogix even if you have placed the VHDX's in the right place with the right permission, if a local profile exists - based on the docs it should "Check for data export"  and load the FSLogix profile instead of the local profile - forget it, it will load anyway the local profile. By removing the local Profile like I mentioned on another post, then it's working correctly.

Anyway, back on topic - I am not sure anymore, because I've spent so much time doing testing - I had a similar issues when redirections.xml was not configured properly. 

In my scenario, i've configured loopback modus on OU containing the RDSh Computer objects, and the policies I specify for the Users are working correctly and merged with the other policies assigned to Users OU.
You may try to do the same and see if in this way your Users GPOs will be processed. Just a blind shot advice tough ;)

Answer 22

For us, this was a *perfectly working environment*, not new. We updated FSLogix, and now things are broken. We are downgrading to 2.9.7117 version tonight to see if this helps, although it does break our Outlook / OneNote search. I'd rather our users get the correct settings than be able to search.

I'll update with our findings.

~Tim

Answer 23

Thanks, let us know please - I am considering downgrading as well. The last build seems to have so many issues, and so far there are no updates from Microsoft / FSLogix Devs Team.

Answer 24

Agreed. We downgraded to 2.9.7117, and will be pushing to Prod tonight. I'll update tomorrow.

~Tim

Answer 25

Did the downgrade resolve your issue?

Answer 26

So far, it's good. We pulled our WEM login action to refresh user policy, and users are getting correct policies again. I will continue to keep an eye on it.

~Tim

Answer 27

Judging by user experience on the World Of EUC slack, it *looks* like the issue stems from a combination of circumstances, namely:

1. FSLogix version after 2.9.7117
2. Machine account is in an OU path with GP Inheritance Disabled

This is currently based on 3 different org's experience, can anyone else chime in to confirm/deny?

Heck, even upvotes if you're seeing the same thing but don't want to type out an explanation :)

Answer 28

Where did you download 2.9.7117 from?

Answer 29

Download link on: https://social.msdn.microsoft.com/Forums/sqlserver/en-US/53263a51-856f-4e64-bc0e-a689d4cc5a8b/release-notes-for-1907-build-29711727413?forum=FSLogix

Answer 30

Thanks a lot!
I have just testet and can confirm it doesn't have the same issue with gpresult as the newer version
(Testet in a 2016 rds environment)

In regard to our support case with MS, they have escalated it to the dev team. Still nothing about comfirming they have an issue or a sollution..

Answer 31

Judging by user experience on the World Of EUC slack, it *looks* like the issue stems from a combination of circumstances, namely:

1. FSLogix version after 2.9.7117
2. Machine account is in an OU path with GP Inheritance Disabled

This is currently based on 3 different org's experience, can anyone else chime in to confirm/deny?

Heck, even upvotes if you're seeing the same thing but don't want to type out an explanation :)

It looks like that "Inheritance disabled" is the culprit in my environment. If I remove "Inheritance disabled" from the group policy structure GPOs are applied. (But I still get the RSoP error)

Answer 32

@Brian Mann1

Is there any news on this? Where not getting anywhere, it seems.

Best regards,
Dennis.

Answer 33

Hello,

I have the same problem. I have the newest version of FSLogix (2.9.7237.48865).

Please tell me that someone has figured out how to fix this. How can MS take so long to fix this with a working update?

Answer 34

The only solution for us so far is using the old version linked to above.

Our MS case stalled after they escalated it to the dev team, we haven't heard from them since last week

Answer 35

Hi,

I can confirm that the issue is still not resolved in the latest public preview. I am opening a support case, as I have seen this at a customer and I am able to reproduce the issue in my lab.

Answer 36

Hi Brian

Have you guys done some investigation on this issue. I have contact with a few persons on Slack who has this issue. I have experienced the issue in a customer setup and I am able to reproduce the issue in my lab. It looks like the issue is not resolved in the latest public preview and considering this forum post was created almost 3 months ago, I cannot understand why this issue is still not resolved.

Answer 37

Hi Kasper,

I created a support case with Microsoft, but they say they can't recreate the problem.

Best regards,
Dennis.

Answer 38

I can recreated the problem in my environment at will. Why don't they just contact one of us? Literally, all I need to do is install this version, and my image stops working correctly.

~Tim

Answer 39

Probably a GPO caching issue. See here https://james-rankin.com/articles/user-group-policies-not-applying-when-using-fslogix-profile-containers/

Answer 40

Probably a GPO caching issue. See here https://james-rankin.com/articles/user-group-policies-not-applying-when-using-fslogix-profile-containers/

I was hopeful when I read your reply, but I don't have the exclusion mentioned in the article in place. 

Best regards,
Dennis.

Answer 41

Hi Kasper

I got this answer from MS;

Download and install the new update (I haven't done this as I am awaiting the download link...)

Configure this registry key. 
DWORD GroupPolicyState = 0 under 
HKLM\SOFTWARE\FSLogix\Profiles\

Answer 42

@Martin K. Simonsen

Let's hope this fixes the GPO problems! Let us know your results. (Or forward the download link :-) )

Best regards,
Dennis.

Answer 43

Hi Martin

I have tested with the latest FSLogix Apps 2004 Public Preview on WS2019, and I can confirm that setting the specified registry value, solves the issue :)

Answer 44

@Kasper

Thats great!

I still haven't recieved the download link, so Im not able to test it myself yet :(

Answer 45

I didn't receive the download link yet either, that's too bad. I'm eager to test this new version and whether it will fix this mess.

Best regards,
Dennis.

Answer 46

I have the download for the public preview, not sure if it is allowed to be shared.

Answer 47

Hi Kezza2,

It's called a public preview, so if you would be inclined to share it with us, I would be immensely grateful. :-)

Best regards,
Dennis.

Answer 48

Denis, Happy to send a link to you but not post it publicly.

Answer 49

I would also appreciate a link if anyone can share.

Not sure if this is the problem we're having, but with FSLogix enabled we've hit a problem where after the first login - our users cannot access ADFS authenticated resources with a TLS error on the web browser. It seems to have some relationship with GPO as admin accounts (with no GPO assigned) have no such problems.

Answer 50

I am interested in the link and happy to let everyone know the results once tested.  The lack of movement from the guys in charge on this one is maddening.

Answer 51

Hi Kasper

I got this answer from MS;

Download and install the new update (I haven't done this as I am awaiting the download link...)

Configure this registry key. 
DWORD GroupPolicyState = 0 under 
HKLM\SOFTWARE\FSLogix\Profiles\

This registry key works on the current release of FSLogix too. You don't need the new version for this workaround. In my experience the GPOs still aren't applied at logon, but are applied at gpo background processing, when this regkey is in effect.

Best regards,
Dennis.

Answer 52

I finally got my download link and I have testet it

Without the regkey it doesn't work, with the regkey it works

Answer 53

I think we are running into this issue as well. None of our User Based Settings GPO's are loading on user logon. What version did you get from Microsoft? Currently we are on 2.9.7237.48865 and I'd like to see if we can get the latest build as well.

Answer 54

Join the "World of EUC" in Slack! Here you get the download link in the FSLogix channel, or just ask for it.
https://join.slack.com/t/worldofeuc/shared_invite/zt-dexotib9-vL0IzKmh9QhPrGxE8LotAA

Hope to see you!

Kind regards
Dennis

Answer 55

I think we are running into this issue as well. None of our User Based Settings GPO's are loading on user logon. What version did you get from Microsoft? Currently we are on 2.9.7237.48865 and I'd like to see if we can get the latest build as well.

The public preview is this "FSLogix_Apps_2.9.7349.30108"

But as Dennis wrote; "This registry key works on the current release of FSLogix too"

Answer 56

I think we are running into this issue as well. None of our User Based Settings GPO's are loading on user logon. What version did you get from Microsoft? Currently we are on 2.9.7237.48865 and I'd like to see if we can get the latest build as well.

The public preview is this "FSLogix_Apps_2.9.7349.30108"

But as Dennis wrote; "This registry key works on the current release of FSLogix too"

Partially. It seems to work with version 2.9.7237.48865 only at the background refresh and not at login. Since I do not have the download for the public preview I cannot tell about this version. I've already applied for the new version. But have not received the download link yet.

Answer 57

For those still waiting for a download link, fill in the form here:

https://forms.office.com/Pages/ResponsePage.aspx?id=v4j5cvGGr0GRqy180BHbR3HZFwpyCxVCngXplJaL78tUQ0tVM1AxM05FQzg5SFQxRlMwOFNLRUQwTi4u

(provided to me by MS Support)

I'm refreshing my WVD master image today with the preview version to see if my GPO issues are resolved.

Answer 58

But as Dennis wrote; "This registry key works on the current release of FSLogix too"

Partially. It seems to work with version 2.9.7237.48865 only at the background refresh and not at login. Since I do not have the download for the public preview I cannot tell about this version. I've already applied for the new version. But have not received the download link yet.

Correct, it partially works.  We're also wanting to Exclude the Users' Desktop folder so that we can redirect that via Group Policy.  Unfortunately that Group Policy Setting only works at logon, so if it fails during logon it will never take effect, even during background refresh.

Also, waiting for a background refresh for Software Restriction policies and other security related settings are a non-starter.

Answer 59

After I've received the download link, I've tested with the new version. But as I have expected, the user policies do not work at login, only during background refresh.

Answer 60

After I've received the download link, I've tested with the new version. But as I have expected, the user policies do not work at login, only during background refresh.

That's really disappointing to hear.  I really want to ditch Roaming Profiles in favor of FSLogix, but it's a complete non-starter if it breaks User-based Group Policy settings. 

It would be really nice to see this called out as a known issue along with a commitment to fix it within a reasonable timeline.

Answer 61

Hi Kasper

I got this answer from MS;

Download and install the new update (I haven't done this as I am awaiting the download link...)

Configure this registry key. 
DWORD GroupPolicyState = 0 under 
HKLM\SOFTWARE\FSLogix\Profiles\

This is the proposed workaround. We are currently working with the group policy team to find the best solution going forward. When we do have the right fix for this you will no longer need to configure this key.

Answer 62

edit
I have now had some time testing it and I am not getting the exact same results as others. As far as I can see the user GPO's are applied at logon. Can someone give me an exact example of something that doesn't? I will then test it in my test environment.

On a related note, search does NOT work correctly but thats for another thread..

My test is Windows Server 2019 1809 (build 17763.1098) FSLogix v. (Version 2.9.7349.30108)

 

Answer 63

edit
I have now had some time testing it and I am not getting the exact same results as others. As far as I can see the user GPO's are applied at logon. Can someone give me an exact example of something that doesn't? I will then test it in my test environment.

On a related note, search does NOT work correctly but thats for another thread..

My test is Windows Server 2019 1809 (build 17763.1098) FSLogix v. (Version 2.9.7349.30108)

 

It is easy to reproduce. 

1. Login the user

2. do some GPP changes, for example add some registry keys or values

3. logout the user - wait 5 minutes

4. login the user

5. GPP changes are not applied.

A manual gpupdate /force would apply the settings.

Answer 64

I tried and the gpo was applied at logon.

Have you set the key:
DWORD GroupPolicyState = 0 under 
HKLM\SOFTWARE\FSLogix\Profiles\ ?

Answer 65

This has been a great group. We had the same issue and was tearing my hair out and my stress levels was going through the roof.  New install of WVD With FSLogix, User Policy errors after second login.

The registry fix has resolved the issues.

Thank you again.

Answer 66

Hi Kasper

I got this answer from MS;

Download and install the new update (I haven't done this as I am awaiting the download link...)

Configure this registry key. 
DWORD GroupPolicyState = 0 under 
HKLM\SOFTWARE\FSLogix\Profiles\

This is the proposed workaround. We are currently working with the group policy team to find the best solution going forward. When we do have the right fix for this you will no longer need to configure this key.

Any chance you can give us some details on exactly what this key does? I've seen this setting as 1 in FSL logs in the past, but can't find any actual information on it. I have never had the user GPO issues described here, and am a little hesitant to enable this without knowing a little more about it.

Answer 67

If it wasn't for this reg key, I was going to pull the plug on using FSLogix in my new CVAD 1912 build and probably revert to using Citrix UPM.  Without the user GPOs applying consistently, the user experience would have been 100% frustrating.

Applying this reg key sorts my issue out.

Great!

Answer 68

• Hello, everyone,
  
  We still have the following effect with the current FSLogix version (2.9.7349.30108):
  

Environment:

• Citrix environment, based on Server 2019 (1809 build 17763.1282) workers
• AD Forest & Domain Functional Level: 2012
• Registry key: "DWORD HKLM\SOFTWARE\FSLogix\Profiles\GroupPolicyState = 0"
• Loopback Replace

Effekt:

• Newly linked user policies are correctly recognized and applied at user logon
• Changes to existing user GPO parameter values are correctly recognized and applied at user logon
• Changes to existing User GPO parameter manipulation from "enable" to "not configured" are generally not being set back to default!!
• Unlink (OU) of an existing User GPO is not recognized and the settings are not being set back to default (example: Restrict the visible control panel menus)!!
• if we switch FSLogix off  for the test user and work with traditional local user profiles, everything works fine.

Does anyone have any news or feedback from an ms case regarding workarounds or hotfixes? 

Best regards,

Patrick

Answer 69

My environment is:

RDSH 2016 (many servers)

FSlogix client installed is updated

Problem occurs only using FSlogix profiles and not normal profiles.

My problem is kinda the same as told here.

Group policy is being applied to fslogix profiles but once the group policy parameters is changed the fslogix profile remain with the old policy parameter means group policy not being refreshed and updated to the user.

I created a policy regarding user configuration that blocks the user from changing the desktop background.

At first logon with FSLOGIX, vhdx created and user unable to change the desktop background, running RSOP showing the policy is being enabled to the user, till here everything is good.

Making a deny on apply group policy to this user making RSOP to show the policy is being denied and should be ok to change his desktop background but no, the user still being denied from changing it.

Any news about this ?

I opened a support ticket to the fslogix team, the guy have no idea what is going on and kept walking me around with frustrating testing for them,

I kept doing some testing and as written here the only solution for now is downgrading the fslogix version to 2.9.7117.27413 from this link -

https://social.msdn.microsoft.com/Forums/sqlserver/en-US/53263a51-856f-4e64-bc0e-a689d4cc5a8b/release-notes-for-1907-build-29711727413?forum=FSLogix

Workaround fix for this issue:

1. Make sure the fslogix user profile is not connected and vhdx is unmounted.
2. Mount the vhdx to get access to the registry editor of the user profile.
3. Navigate to HKEY_USERS\SOFTWARE and delete the key Policies.
4. Close the registry editor and unmount the vhdx in order to make sure the user will be able to connect .
5. Connect with the user and GPO is being refreshed and user successfully being excluded from the desired GPO.

Answer 70

Similar issues here with Group Policy.

Citrix Virtual Apps and Desktop VDA v2003 on Server 2016

FSLogix V 2.9.7349.30108 w/Azure storage

Group Policy User Settings sometimes do not apply. Under the User Settings section in gpresult /R we receive:

Applied Group Policy Objects - N/A

The Users is a part if the following security groups - ERROR: An unexpected error occurred.

Also, at the same time the FSLogix Apps Event viewer on the VDA server we get 3 errors: Event ID 26 LoadProfile Failed. (The process cannot access the file because another process has locked a portion of the file.)

Event ID 25 - Profile Load: Status 0x1 Reason 0x0 Error 0x21

Event ID 26 - Could not acquire an exclusive lock for vhd(x). (The process cannot access the file because another process has locked a portion of the file.)

I have a ticket opened currently with FSLogix support too.

Any ideas? Thank you

Answer 71

I'm also having an issue with TLS errors when attempting to auth to our ADFS using IE 11.  Chrome seems to work, however.  Have you had in success in fixing this?

Answer 72

• Hello, everyone,
  
  We still have the following effect with the current FSLogix version (2.9.7349.30108):

Environment:

• Citrix environment, based on Server 2019 (1809 build 17763.1282) workers
• AD Forest & Domain Functional Level: 2012
• Registry key: "DWORD HKLM\SOFTWARE\FSLogix\Profiles\GroupPolicyState = 0"
• Loopback Replace

Effekt:

• Newly linked user policies are correctly recognized and applied at user logon
• Changes to existing user GPO parameter values are correctly recognized and applied at user logon
• Changes to existing User GPO parameter manipulation from "enable" to "not configured" are generally not being set back to default!!
• Unlink (OU) of an existing User GPO is not recognized and the settings are not being set back to default (example: Restrict the visible control panel menus)!!
• if we switch FSLogix off  for the test user and work with traditional local user profiles, everything works fine.

Does anyone have any news or feedback from an ms case regarding workarounds or hotfixes? 

Best regards,

Patrick

Hello,

same problem for me:

Different Windows environments with server 2019 and 2016, Loopback "merge", no block of GPO inheritance. The "GroupPolicyState = 0" does not help nor does it seem to change anything. I downgraded to the last three releases, including 1809 (17763.1282) with always the same results:

The user policies are just applied correctly on first logon:

> allow use of registry

> allow cmd

> start menu layout

After that, changes to these policies (f.e. switching from "enabled" to "not configured") are not applied. If I switch to "disabled", the GPO is correctly applied.

Can somebody of MS/FSLogix take over responsibility, confirm the problem and give a workaround or at least a statement, please? How can we make use of this product like this?

I claimed access to the public preview, nothing happens. This is really frustrating.

Thanks.

Answer 73

@KUNP @ente_0815

What you're describing is not a problem with FSLogix.

Changing a policy setting from "enabled" to "not configured" doesn't change settings back to default, and it's not supposed to. That is how Group Policy works and it has been that way for decades.

"Not configured" is NOT the same as "default".

"Not configured" basically tells Group Policy to ignore that setting and leave it as-is, no matter how the target computer/user is currently configured.

Once you've enabled a GPO setting, the only way to revert it back is to apply a GPO to set the value you want.

Answer 74

@KUNP @ente_0815

What you're describing is not a problem with FSLogix.

Changing a policy setting from "enabled" to "not configured" doesn't change settings back to default, and it's not supposed to. That is how Group Policy works and it has been that way for decades.

"Not configured" is NOT the same as "default".

"Not configured" basically tells Group Policy to ignore that setting and leave it as-is, no matter how the target computer/user is currently configured.

Once you've enabled a GPO setting, the only way to revert it back is to apply a GPO to set the value you want.

But the behavior described influence only FSLogix profiles, not the normal local profiles.

So from what you said it should also be the same within the methods... how come they  are different ?

Answer 75

Are you sure your testing methodology is correct?

You would need to first apply the "enabled" policy to both users (FSLogix & non-FSLogix), and then make sure the profiles aren't being destroyed before applying the "not configured" policy.

If your process is ending up with a new user profile for whatever reason, then the GPO settings would be applying to new default values rather than the values previously modified by the other GPO.

Answer 76

I don't think you are correct.

GPO User Preferences are not put back to default on the computer after removing them from a GPO policy.

GPO User Administrative Templates are put back to default on the computer when you put them on not configured.