danholme

For whomever runs across this post, I have replicated the behavior: ICACLS path /SETOWNER DOMAIN\Username DOES NOT WORK on Windows Server 2003 SP2. There MUST be a bug in the application, because I can run the exact same command, logged on as the exact same user, against the same path, from a Windows Vista SP1 system (which has a new version of icacls), and it works. It seems to me that by doing this test I've ruled out user credentials problems, permissions problems, user rights problems... the only "variable" is the version of icacls.exe.

Razormon... Did your (first post) folder structure work for XP *also*? That would be interesting to know. Mine works for both XP and vista, but there may be situations where changes should be LIMITED to Vista, so if yours achieves that, that'd be cool. Then the next question would be what if you used BOTH structures...?

For anyone who finds this thread, there's been some back and forth about what "can" versus "should" be done. I just care what WORKS, so I'd like to confirm, per the first post, that the $DOCS folder works. I am using XPSP2 *and* VISTA RTM. My deployment is through the BDD 2007. In the BDD's .\Distribution folder, I created the following folder structure with the indicated "test files": $OEM$ $DOCS All Users Desktop "All Users Desktop Test File.txt" Start Menu Programs "All Users Start Menu Shortcut.lnk" Startup "All Users Startup Test.bat" Default User Desktop "Default User Desktop Test File.txt" Start Menu Programs "Default User Start Menu Shortcut.lnk" Startup "All User Startup Test.bat" My Documents "Default User My Documents Test File.txt" Application Data Microsoft Internet Explorer Quick Launch "Default User Quick Launch Shortcut.lnk" NOTE!! The entire structure under $DOCS uses *LEGACY* folder names (Application Data, not AppData; Default User not Default; All Users not Public; My Documents not Documents). And it works PERFECTLY in both XPSP2 and Vista RTM deployments. Hope this helps!

Did you ever figure out what was going wrong? I also have an Intel 965 chipset and am having the same issue. I injected the network drivers into WinPE--the same drivers I downloaded successfully and used within the OS--and no luck!

The link to 899587 in the list actually goes to 899591... needs a quick correction on the href.

The latest XPSP2 list includes 896727 (MS05-038) which is not necessary since 896688 (MS05-052) supercedes it.

KB884020 (under "non-critical patches") has been rolled into KB893066, so is not nec if you *are* installing KB893066.