Jump to content

Recommended Posts

Posted (edited)

System almost ready for next week and just looking at home folder and notice that user folders are now My Documents. I know of this problem and when setting it up a powershell script to deny users access to the desktop.ini to stop this and it seemed to be working, however now users are logging on I seem to have My Documents again? We use redirected folders etc and local profiles and did read that this goes away after first creation of that local profile? Anyone confirm that?

 

Whats the best way to stop this happening or can I just do a massive search and delete of all the desktop.ini files in the folders of the users in the home directory?

I have for the moment just added the Filename column to the explorer view to see whats what but not ideal as I need to run a file dialogue box which shows up the folder names as displayed and I cant see which one to select as it stands only in a windows explorer view.

Edited by TechSupp
Posted

Dont deny permissions this will slow your login process. We did this and it added 30 - 45 seconds onto the login times.

 

There are lots of solutions on here for it. We put all our home folders in a sub folder.

 

For example

 

-JohnSmith

--Documents

Posted
Dont deny permissions this will slow your login process. We did this and it added 30 - 45 seconds onto the login times.

 

There are lots of solutions on here for it. We put all our home folders in a sub folder.

 

For example

 

-JohnSmith

--Documents

 

Thanks, but that was one of the options given on here somewhere. Dont want to go messing with the folder structure now as everyone back in on Monday and not risking doing it remotely.

What about the quick and dirty fix of just deleting all the desktop.ini files found? Have got a routine that will do that as each user logs off but dont know if that would work.

Posted
Dont deny permissions this will slow your login process. We did this and it added 30 - 45 seconds onto the login times.

 

I also had the same issue, but you can work around it by doing folder redirection manually (e.g. use a login script to set registry keys) instead of using folder redirection through group policy.

  • 3 weeks later...
Posted

Best solution I found was to add a Logoff Script to the GPO for the users.

 

Save this as anything.vbs and then add it to:

User Config>Policies>Windows Settings>Scripts>Logoff

 

When users logoff it deletes the desktop.ini file solving this problem.

 

On Error Resume Next
Set WSHShell = WScript.CreateObject("WScript.Shell")
Set FSO = CreateObject("Scripting.FileSystemObject")

DocsPath = WSHShell.SpecialFolders("MyDocuments")

If FSO.FileExists (DocsPath & "\desktop.ini") Then
 FSO.DeleteFile (DocsPath & "\desktop.ini")
End If

  • Thanks 3
Posted
Best solution I found was to add a Logoff Script to the GPO for the users.

 

Save this as anything.vbs and then add it to:

User Config>Policies>Windows Settings>Scripts>Logoff

 

When users logoff it deletes the desktop.ini file solving this problem.

 

On Error Resume Next
Set WSHShell = WScript.CreateObject("WScript.Shell")
Set FSO = CreateObject("Scripting.FileSystemObject")

DocsPath = WSHShell.SpecialFolders("MyDocuments")

If FSO.FileExists (DocsPath & "\desktop.ini") Then
 FSO.DeleteFile (DocsPath & "\desktop.ini")
End If

 

 

 

No good if they dont log off properly or they are still logged on when finding the home area.

  • 2 weeks later...
Posted

As suggested in the linked thread, I use FSRM for this.

 

Docs folders are redirected to \\Server\Doc$\Staff\%username% I had an 'executable' policy in FSRM anyway (for \\Server\Doc$ to cover students as well) so i added 'desktop.ini' to that as it was only one file.

It's been working great for about a year or so :)

  • Thanks 1
Posted
As suggested in the linked thread, I use FSRM for this.

 

Docs folders are redirected to \\Server\Doc$\Staff\%username% I had an 'executable' policy in FSRM anyway (for \\Server\Doc$ to cover students as well) so i added 'desktop.ini' to that as it was only one file.

It's been working great for about a year or so :)

 

 

that answer was the reason i subscribed to this thread!

  • Thanks 1

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...