Home folders renames to My Documents

[kholler]

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

[AlexB]

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 kholler

 

Glad you found a solution. I'd recommend bookmarking Edugeek, there are lots of people here with vast knowledge between them, I rarely find they can't help me

[klop]

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?

 

thanks

[bewlay51]

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.

 

Regards,

 

John

[AlexB]

We are only Windows 7 here, sry

[zag]

File Synchronisation – Stopping

You may wish to prevent file and folder synchronisation taking place when a user logs off. If so, you will need to edit the two group polices as described below.

 

Thanks for this.

 

Its been bugging me for a while.

 

Fixed it perfectly as far as I can see.

[Firefox]

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.

 

Do you need FRSM installed on all DC's for this to work?

Also how when choosing the File screen Path, do you select a network location? I seem only to be able to select local drives

[AlexB]

Do you need FRSM installed on all DC's for this to work?

Also how when choosing the File screen Path, do you select a network location? I seem only to be able to select local drives

 

Hi

 

You only need to install FRSM on the file server(s) you are trying to restrict.

 

As you installing locally on the machine you are restricting you use the local path to configure.

 

Alex.

[SmellyLlama]

This is making my brain hurt at the moment, I thought I'd cracked it but they came back :S, I'll pop back in here when I'm back in the school tomorrow afternoon.

[Firefox]

Hi

 

You only need to install FRSM on the file server(s) you are trying to restrict.

 

As you installing locally on the machine you are restricting you use the local path to configure.

 

Alex.

 

ah unfortunately we're using CIF shares so now sure we can implement this. What adverse effect would be seen from simply deleting desktop.ini from the My documents folders? in testing I noticed if deleted it does not get recreated, and I'm not seeing any obvious detremental effect.

 

It seems desktop.ini is initially created when your roaming profile first updates when logging off of a Windows 7 device. When using just a local profile the desktop.ini is not created. After first upload of the file, if I delete it, subsequent log on/off events do not create another ini file.

[AlexB]

ah unfortunately we're using CIF shares so now sure we can implement this. What adverse effect would be seen from simply deleting desktop.ini from the My documents folders? in testing I noticed if deleted it does not get recreated, and I'm not seeing any obvious detremental effect.

 

It seems desktop.ini is initially created when your roaming profile first updates when logging off of a Windows 7 device. When using just a local profile the desktop.ini is not created. After first upload of the file, if I delete it, subsequent log on/off events do not create another ini file.

 

I don't know what a CIF share is, but FRSM only works on local drives at source as far as I know.

[pdr]

Hope you'll excuse me picking you up on this, but I have so far not been successful in stopping creation of desktop.ini files, and am still deleting them to re-establish folder name.

In your solution you say:-

"you will need to edit the two group polices as described below"

However you only appear to refer to one group policy (Default Domain Policy):-

a) Run group policy editor and navigate to “Default Domain Policy"

c) Navigate to “Default Domain Policy” right click and choose edit.

 

 

 

 

Sorry, not been around for a while.

I did fix the problem by disabling file synchronisation on the home folders. I did it on the caching tab of the share, in my case "home$" Simple FIX. The following maybe of some help, but stops all synchronisation....

 

File Synchronisation – Stopping

You may wish to prevent file and folder synchronisation taking place when a user logs off. If so, you will need to edit the two group polices as described below.

 

a) Run group policy editor and navigate to “Default Domain Policy” right click and choose edit.

b) Choose Computer Configuration >Administrative Templates > Networking > Offline files.

 

Make the following changes:

 

Allow or disallow use of offline files features Disable

Synchronize all offline files when logging on Disable

Synchronize all offline files when logging off Disable

Synchronize all offline files before suspend Disable

 

Remove “Make Available Offline” Enabled

Prevent the use of offline file folders Enabled

 

Prohibit “Make available Offline” for those files and folders Disable

 

 

c) Navigate to “Default Domain Policy” right click and choose edit.

d) Choose Computer Configuration >Administrative Templates > Networking > Offline files.

 

Allow or disallow use of offline files features Disable

 

NEXT

e) Right click on the “home” share the select > Sharing > Caching >

f) Enable the last option “Files and programs from the share will not be available offline”. If wished, this option can be enabled for all shared folders.

 

Re-boot the server

[sly888]

Instead of using a script you can just add 'filename' column to your windows explorer view parameter.

“View”, “Choose Details…”, activate “Filename” and press “OK”

[flyinghaggis]

ah unfortunately we're using CIF shares so now sure we can implement this. What adverse effect would be seen from simply deleting desktop.ini from the My documents folders? in testing I noticed if deleted it does not get recreated, and I'm not seeing any obvious detremental effect.

 

It seems desktop.ini is initially created when your roaming profile first updates when logging off of a Windows 7 device. When using just a local profile the desktop.ini is not created. After first upload of the file, if I delete it, subsequent log on/off events do not create another ini file.

 

We're contemplating blocking desktop.ini file creation in our pupils documents folders using FSRM. Has anyone been running this for any length of time and discovered any side-effects or is it safe enough to do?

[Arthur]

We're contemplating blocking desktop.ini file creation in our pupils documents folders using FSRM. Has anyone been running this for any length of time and discovered any side-effects or is it safe enough to do?

Blocking the desktop.ini file will significantly increase your logon times so isn't recommended.

[teklogic]

I set a bat script to update once a day to deny the read permissions, works well.

 

$usernames = get-childitem C:\DATALOCATION*

foreach ($name in $usernames ){icacls $name\desktop.ini /deny "STAFFGROUP:®"}

 

Don't deny access for the administrators group, otherwise you cannot run the scripts.

[Chuckster]

Run this reg on all your machines and you will never have the issue of home folders being renamed to Documents.

 

Windows Registry Editor Version 5.00

; Prevents User folders being renamed to Documents after logging on

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\FolderDescriptions\{FDD39AD0-238F-46AF-ADB4-6C85480369C7}]
"LocalizedName"=hex(2):00,00

 

I no longer have to use a script to remove the desktop.ini file as the above fixes that issue.

[Jawloms]

Holy necro thread! I've just had this problem and done the FSRM thing. Happy now

[FN-GM]

Holy necro thread! I've just had this problem and done the FSRM thing. Happy now

Expect an impact on your login times.