Desktop.ini GPP fix

[Ephelyon]

A number of solutions have been proposed to the desktop.ini problem (where all home folders display as "Documents" instead of the username), but I've just discovered another one I wanted to share. Can't see any disadvantages to it as yet. Essentially it's an Ini Files user preference like so:

 

 

Tested working over here. Anyone have any thoughts?

[TechSupp]

Maybe a possible solution but some have had issues getting rid of the file. There does not seem to be one fool proof quick fix (notice I said quick fix, the ideal way is to use the suggested MS folder structure I know). Not gone that route, used the file resource fix, works just fine here but others have had slow logon issues. Be interesting to see what others who use your method think.

[Ephelyon]

That entry isn't deleting the file; it's deleting the offending line in it that causes the apparent renaming during logon. The rest is still there, so you get the custom Documents icon but the name stays the same.

[fairm010]

I use the FSRM method with no login speed issues by I may use this instead.

[FN-GM]

Why bother making shortcuts and not just do it the proper way?

[Ephelyon]

What would that be?

[Arthur]

What would that be?

Sub-folders.

 

• KB947222 - When you redirect the Documents folder on a Windows 7-based computer to a network share, the folder name unexpectedly changes back to Documents (see Method 1)
  
• www.edugeek.net/forums/windows-server-2008/100566-desktop-ini-my-documents.html#post866681
  
• www.edugeek.net/forums/windows-server-2008-r2/105138-user-folders-renaming-themselves-my-documents.html#post901773
  

[Ephelyon]

That's fine for new setups, but if you've already got a folder structure set up for users it means either moving stuff around yourself or sending e-mails explaining why something like that has changed and which sub-folder new documents will be stored in by default from now on. Special schools with lots of autistic students might find that tricky as they often can't stand change. I remember the hoo-hah when we changed the default home page one time.

 

Or you could just do this in 30 seconds and not have the hassle in an existing setup.

[TechSupp]

That entry isn't deleting the file; it's deleting the offending line in it that causes the apparent renaming during logon. The rest is still there, so you get the custom Documents icon but the name stays the same.

 

Oops! You are correct, that's me not reading it correctly. Interesting all the same.

[detjo]

I deleted all desktop.ini files in '\\Server\Docs' and set FSRM on it. Never had a problem with it

[Ephelyon]

That's good; you're in one of those environments that doesn't seem to suffer from an extended logon time if you FSRM it then. We did here though.

 

It would be interesting if someone could do some research on this. As far as I'm aware, the principle is that Windows will try to create the file, be told it's not allowed to, and then apply the "continuous retry until limit is exceeded" approach. Another example of this can be found in the RoboCopy command, which by default will retry a file copy operation one million times, waiting thirty seconds between each, unless it's told otherwise - so you really want to add "/r:0 /w:0" to any RoboCopy command you execute!

 

But what's behind this? Could it be that some members, rather than simply working in an environment where a longer logon time isn't considered noteworthy, have in fact set some obscure (GPO?) setting somewhere that tells Windows not to bother retrying a file creation operation if it's not successful the first time, and that those members are consequently not seeing a problem when using FSRM to fix the desktop.ini issue?

[FN-GM]

That's fine for new setups, but if you've already got a folder structure set up for users it means either moving stuff around yourself or sending e-mails explaining why something like that has changed and which sub-folder new documents will be stored in by default from now on. Special schools with lots of autistic students might find that tricky as they often can't stand change. I remember the hoo-hah when we changed the default home page one time.

 

Or you could just do this in 30 seconds and not have the hassle in an existing setup.

 

By mapping the home drive to the sub folder the user doesn't even notice the difference.

 

A simple robocopy can move the files and a quick change to the AD mappings.

Edited November 29, 2014 by FN-GM

[Ephelyon]

It does matter if they're using programmes that reference absolute file paths (sometimes by share, not by drive mappings).

 

We've had this recently with Mediator; students using this to create websites experience problems when the absolute file paths they've referenced no longer work when something is moved. Should they be being taught that way? No. But this is the real world...

[JATSO]

Just going to chip in here.

I deleted desktop.ini files as mentioned and have subsequently ended up with a longer logon time ie 3:30s from logging in to being usable.

At first I thought this was something to with what I had done by deleting the desktop.ini file but i noticed on the server that DNS was not integrating with my active directory Event id: 4007.

 

I restarted AD services and DNS a couple of times and then rechecked the the event log and the error had not shown up on the 3rd attempt at re-starting DNS thinking that this maybe what had caused my long login times.

 

I checked the login time and it was still what I consider to be long, as logins have always been generally quick especially as I was using a wired connection.

 

Unfortunately it was nearly 6pm and the the caretaker was tapping the window with the keys so I shall see what the comments from staff are tomorrow on my Friday visit to the school.

 

Any thoughts on why the long login appreciated.

[googlemad]

We tried FSRM for some exam logins as a test and it ended up breaking the entire folder redirection policies!

[fiza]

Just going to chip in here.

I deleted desktop.ini files as mentioned and have subsequently ended up with a longer logon time ie 3:30s from logging in to being usable.

At first I thought this was something to with what I had done by deleting the desktop.ini file but i noticed on the server that DNS was not integrating with my active directory Event id: 4007.

 

I restarted AD services and DNS a couple of times and then rechecked the the event log and the error had not shown up on the 3rd attempt at re-starting DNS thinking that this maybe what had caused my long login times.

 

I checked the login time and it was still what I consider to be long, as logins have always been generally quick especially as I was using a wired connection.

 

Unfortunately it was nearly 6pm and the the caretaker was tapping the window with the keys so I shall see what the comments from staff are tomorrow on my Friday visit to the school.

 

Any thoughts on why the long login appreciated.

 

Have you tried the method @Ephelyon shows in the first post? This doesn't delete the desktop.ini file it just deletes a line from the file.

 

- - - Updated - - -

 

Just going to chip in here.

I deleted desktop.ini files as mentioned and have subsequently ended up with a longer logon time ie 3:30s from logging in to being usable.

At first I thought this was something to with what I had done by deleting the desktop.ini file but i noticed on the server that DNS was not integrating with my active directory Event id: 4007.

 

I restarted AD services and DNS a couple of times and then rechecked the the event log and the error had not shown up on the 3rd attempt at re-starting DNS thinking that this maybe what had caused my long login times.

 

I checked the login time and it was still what I consider to be long, as logins have always been generally quick especially as I was using a wired connection.

 

Unfortunately it was nearly 6pm and the the caretaker was tapping the window with the keys so I shall see what the comments from staff are tomorrow on my Friday visit to the school.

 

Any thoughts on why the long login appreciated.

 

Have you tried the method @Ephelyon shows in the first post? This doesn't delete the desktop.ini file it just deletes a line from the file.

[Ephelyon]

@fiza, have you verified it as working on your site? It's working here but I haven't had confirmed reports from others yet I don't think...

[fiza]

@fiza, have you verified it as working on your site? It's working here but I haven't had confirmed reports from others yet I don't think...

 

Ive only attached it to year 7 so far. The names are certainly appearing in the list as students have logged in. Havent had many IT lessons today so should know more next week.

[themightymrp]

Can anybody else confirm that @Ephelyon 's method above has worked for them? I'm going to try it here if all is good.

[fiza]

Can anybody else confirm that @Ephelyon 's method above has worked for them? I'm going to try it here if all is good.

 

worked for us.

[themightymrp]

Nice one, cheers

[Ephelyon]

... and where was my Thanking, @fiza?

[LeMarchand]

There you go - it's accrued interest.

[themightymrp]

Just set it up and it seems to work Thanks!

[Ephelyon]

What's kinda funny is that I didn't come up with this method at school... that screenshot is from a server at a solicitors' firm that I was doing a network for on the side... xD