Sorry to dredge up old threads but I just got round to attempting to fix this (never really bothered me as always accessed users from unc shares) any way, I took the above guys test script, modded to work with xcacls.vbs and it works a treat, many thanks Nixphoe.
due to our legacy shares (created few year back by ranger, our issue was domain admin access to desktop.ini, not administrators)
script below if anyone wants a gander, modded to work straight from a batch file, and xcalcs.vbs from c drive
'dir /b "\\servername\students\"') DO cscript c:\XCACLS.vbs ""\\servername\students\%%a\desktop.ini /D "Domain Admins:R""
Sorry to dredge up this thread again, but i was also wanting to do this and keep syncronization. As i read through the thread i was eagerly awaiting the batch file script that could be scheduled to delete the desktop.ini file. But alas i have got to the end and there was no script so i sorted it. Batch file script to delete desktop.ini file.
Thought it would be nice to share with you all. If the link is helpful please thank me :)
which works fine. Saves a lot of time with scripting to delete files that get recreated every time the student logs in.Quote:
Instead of using a script you could also just add an extra column to the view of windows explorer called “Filename”
“View”, “Choose Details…”, activate “Filename” and press “OK”
Has anyone come up with a definate solution to this yet?
I have tried all of the group policy suggestions with no luck. I want to avoide having to setup scheduled tasks for scripts etc.
We use FSRM to block the creation of desktop.ini on the user shares. I think it is available in server 2003 r2 and up, but I know it is in 2008.
Obviously this only fixes new creation so once in place you'll have to remove the existing files.
We also use FSRM for quota management and I have to say I've been very impressed for something Microsoft provide for 'free'!
I love the way if you have a quota on a user's folder then drive display in my computer shows a bar of how much of the quota is in use.
I Must admit i didnt think of using a file screen.
All is well.
I signed up just to thank AlexB for the FSRM suggestion, I have 1200 users and was battling this desktop.ini problem by running scrips that created dummy desktop.ini files in folders all over the network, then other scripts that blocked "read" permission to them for "everyone." This was working until offline file synchronization (6 months later) started throwing synch errors for everyone trying to synch their (now access denied) desktop.ini files. I searched everywhere 6 months ago and this is the only place that a file screen was suggested, it is definitely the way to go, simpler, easier, will work for future user/folder creation, and allows for synching to work without error. I'm still surprised that we have to find work arounds for this and there's no official solution.
Thanks again, -KH
Hi, i've just put in place a file screen using FSRM, brilliant idea but now will redirected docs work for XP?
Seems there's a fail with copying desktop.ini so they wont.
Thought that was the perfect solution - are you guys using both xp and win 7 clients?
I don't use FSRM, I still use the solution I described earlier in this post and have used it on three server now without any issues. These have a mix of Win7 and XP pro.
We are only Windows 7 here, sry :(