Desktop.ini stores all sorts of stuff like this. PersonalizedName stores the 
value you're probably seeing.  Hard to say exactly how or when it gets set, but 
I'm sure the old users must have used that folder for something at some point.  
I'd make it a point to create fresh folders for new people and delete/archive 
old folders when people leave.  Alternatively, you can look for hidden files 
like desktop.ini and thumbs.db and delete them before reuse.  Also, if you use 
cmd to look at the root folder, you should see the real name and not the 
PersonalizedName that explorer.exe shows.

-----Original Message-----
From: Kennedy, Jim [mailto:[email protected]] 
Sent: Thursday, January 05, 2012 12:40 PM
To: NT System Admin Issues
Subject: RE: Network folders renaming themselves

Ok, delete the desktop.ini file inside each folder fixes it. Question is how is 
the bad one getting there.

-----Original Message-----
From: Kennedy, Jim [mailto:[email protected]]
Sent: Thursday, January 05, 2012 1:31 PM
To: NT System Admin Issues
Subject: Network folders renaming themselves

This is freaky.

2003 R2 file server serving files to staff. These are their re-directed My 
Documents folders.  Clients are a mixture of XP and Win 7.  I have one share 
that contains 10 users in a department. The folders are all LastnameFirstname.  
Only the user, domain admins and local administrators have access to the 
folders. And local admins are just the domain admins.

The folders are periodically renaming themselves. Right now I am looking at it 
and two of the folders are renamed to the SAME name....two folders that now 
have LastnameFirstname of an ex-employee that left 8 months ago and was NEVER 
in this department or in this folder. And these two identically named folders 
are in the same spot. Files inside are intact and as they should be.

My only thought is maybe one of these users is hitting that folder with an old 
computer that this ex-employee used and there is some kind of offline files 
thing going on. But that is a real stretch. The ex-employee and these two 
impacted users are not in the same buildings...it could happen but that is a 
real reach. 

~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ 
<http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to [email protected]
with the body: unsubscribe ntsysadmin

~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ 
<http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to [email protected]
with the body: unsubscribe ntsysadmin

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to [email protected]
with the body: unsubscribe ntsysadmin

Reply via email to