claudetools/.claude/memory/reference_cascades_fr_gpo_fix.md

name, description, metadata

name	description	metadata
Cascades Folder Redirection GPO — DOA root cause + fix (misnamed fdeploy)	Why native Folder Redirection failed on EVERY Cascades machine (LE + staff) and forced the per-user registry workaround — the GPO's redirect targets were saved in a misnamed fdeploy1.ini; Windows only reads fdeploy.ini. Fixed 2026-06-08. Read when touching Cascades folder redirection or onboarding a new Cascades user.	type reference

Root cause (found 2026-06-08): Native Folder Redirection never worked at Cascades — every machine needed fix-shell-redirect.ps1. The FR GPO CSC - Folder Redirection ({512B43A4-F049-4CE5-BFAC-860AD13E92BE}) had its redirect targets in a file named fdeploy1.ini, but the Windows FR client-side extension reads fdeploy.ini only. No fdeploy.ini existed → the client knew which 5 folders to redirect but got an empty target path (FR Operational log event 1006 shows Path = "", and there is NO event 1008 "successfully redirected"). It silently no-op'd. The GPO had been hand-built by editing the wrong filename.

Fix: wrote a correct fdeploy.ini (5 folders, Flags=187, FullPath=\\CS-SERVER\Homes\%USERNAME%\<Folder>) into {512B43A4-...}\User\Documents & Settings\, then bumped the GPO version 917506→983042 keeping GPT.INI Version AND the AD versionNumber attribute in sync (FR is a foreground/logon CSE; it only re-applies when the version changes). Canonical artifact: clients/cascades-tucson/gpo/fdeploy.ini. Backup of original \User tree + GPT.INI: C:\Windows\Temp\frfix-20260608-161144 on CS-SERVER.

How to apply / diagnose elsewhere:

• Diagnose: on the client, Get-WinEvent -LogName 'Microsoft-Windows-Folder Redirection/Operational' — Path = "" in event 1006 + no 1008 = the GPO is delivering no target path (missing/empty/misnamed fdeploy.ini).
• The dead fdeploy1.ini was LEFT in place (Windows ignores it) — do NOT edit it. Edit redirection via GPMC, or replace fdeploy.ini from the repo artifact.
• The LE GPO CSC - Folder Redirection (LE) ({889BE7BE-...}) is also broken — \User tree completely empty. Retire it / move LE users into SG-FolderRedirect, or apply the same fix.
• After the fix, the per-user registry workaround should no longer be needed; native FR redirects all 5 folders on first logon. Still pre-create the home folder (New-HomeFolder) before first logon. See feedback_cascades.

Also (2026-06-08): CS-SERVER live GuruRMM agent re-enrolled to c39f1de7-d5b6-45ae-b132-e06977ab1713 (old 6766e973 is stale) — always resolve the agent live by hostname, never hardcode. Related: project_cascades.