GPO setting

%3CLINGO-SUB%20id%3D%22lingo-sub-744675%22%20slang%3D%22en-US%22%3EGPO%20setting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-744675%22%20slang%3D%22en-US%22%3E%3CP%3EHello%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20am%20not%20sure%20if%20this%20is%20the%20right%20location%20to%20put%20it.%3C%2FP%3E%3CP%3ESince%20a%20few%20years%20we%20have%26nbsp%3Bthe%20following%26nbsp%3BGPO%20setting%20in%20our%20domain%20enabled%3A%26nbsp%3B%22Delete%20cached%20copies%20of%20roaming%20profiles%22%20%26amp%3B%20%22Do%20not%20check%20for%20user%20ownership%20of%20Roaming%20Profile%20Folders%22.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIt%20is%20applied%20to%20160%20FAT-clients%20and%20we%20have%20noticed%20that%20alot%20of%20them%20did%20not%20delete%20the%20profiles.%3C%2FP%3E%3CP%3EIt%20seems%20that%20sometimes%20it%20works%20and%20sometimes%20it%20does%20not.%3C%2FP%3E%3CP%3ESome%20profiles%20are%20partly%20deleted%2C%20because%20of%20files%20in%20use%20or%20path%20too%20long%20which%20prevents%20this%20policy%20from%20completing%20the%20task%2C%20however%20there%20are%20also%20full%20profiles%20which%20can%20be%20deleted%20manually.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHow%20reliable%20is%20this%20policy%20setting%3F%20I%20have%20read%20it%20does%20not%20always%20work%3F%3C%2FP%3E%3CP%3EWe%20use%20Windows%20Server%202012%20R2%2C%20client%20computers%20are%20Windows%208.1.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBest%20regards%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERamon%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-744675%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EWindows%20Server%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
RamonTB
New Contributor

Hello,

 

I am not sure if this is the right location to put it.

Since a few years we have the following GPO setting in our domain enabled: "Delete cached copies of roaming profiles" & "Do not check for user ownership of Roaming Profile Folders".

 

It is applied to 160 FAT-clients and we have noticed that alot of them did not delete the profiles.

It seems that sometimes it works and sometimes it does not.

Some profiles are partly deleted, because of files in use or path too long which prevents this policy from completing the task, however there are also full profiles which can be deleted manually.

 

How reliable is this policy setting? I have read it does not always work?

We use Windows Server 2012 R2, client computers are Windows 8.1.

 

Best regards,

 

Ramon