cmdown
asked on
Virtual Server 2008 R2 Multiple 2511 Event ID after Migration from Physical 2003 R2
'morning Experts.
We picked up on a problem with our data server on Friday where a number of users shares had 'disappeared' to be replaced in the folder root by multiple folders called 'My Documents'. Over the weekend an automatic disc check kicked off and we have now found that we have multiple event 2511 entries in the system log. Back tracking the log has shown that these first appeared in January a few months after our physical 2003 R2 data box was migrated to a virtaul 2008 R2 running under VMware.
Most of the orphaned shares do appear to be true orphans in that they point to some very old data that is no longer required / on the server. What I am looking for is:
a) some pointers as to what may have caused this
b) a powershell or vbscript that will go through AD and the event log and remove the orphaned shares - preferably with a 'dummy run' switch first as this is a production server.
I have found a couple of similar questions elsewhere but they either relate to 2003 or don't do quite what I am looking for. The closest are:
http://mow001.blogspot.co.uk/2005/12/msh-orphan-share-remover-tool.html
and
https://www.experts-exchange.com/questions/26445772/Windows-Storage-Server-2003-File-Server-Role-Export-Orphaned-folders-list-to-csv.html
Thanks
We picked up on a problem with our data server on Friday where a number of users shares had 'disappeared' to be replaced in the folder root by multiple folders called 'My Documents'. Over the weekend an automatic disc check kicked off and we have now found that we have multiple event 2511 entries in the system log. Back tracking the log has shown that these first appeared in January a few months after our physical 2003 R2 data box was migrated to a virtaul 2008 R2 running under VMware.
Most of the orphaned shares do appear to be true orphans in that they point to some very old data that is no longer required / on the server. What I am looking for is:
a) some pointers as to what may have caused this
b) a powershell or vbscript that will go through AD and the event log and remove the orphaned shares - preferably with a 'dummy run' switch first as this is a production server.
I have found a couple of similar questions elsewhere but they either relate to 2003 or don't do quite what I am looking for. The closest are:
http://mow001.blogspot.co.uk/2005/12/msh-orphan-share-remover-tool.html
and
https://www.experts-exchange.com/questions/26445772/Windows-Storage-Server-2003-File-Server-Role-Export-Orphaned-folders-list-to-csv.html
Thanks
ASKER
Hi Krzysztof
Thanks for your reply. I can do this manually but we have quite a large user base and I would ideally like a tool that will give me a report of problem shares and the option to remove orphaned shares automatically.
Anyway, to answer your question,.. for some users yes.When the data was migrated from the physical 2003 box to the virtualised 2008 server one entire set of users were moved to a new drive due to space constraints. However the few orphans I've sampled seem to have dropped a space from the share name, i.e. Smith John has become SmithJohn ( yes I know there shouldn't have been a space there in the first place !!). However as to why/ how this has occurred I don't know - There shouldn't have been any manually 'intervention' on these folders.
Thanks for your reply. I can do this manually but we have quite a large user base and I would ideally like a tool that will give me a report of problem shares and the option to remove orphaned shares automatically.
Anyway, to answer your question,.. for some users yes.When the data was migrated from the physical 2003 box to the virtualised 2008 server one entire set of users were moved to a new drive due to space constraints. However the few orphans I've sampled seem to have dropped a space from the share name, i.e. Smith John has become SmithJohn ( yes I know there shouldn't have been a space there in the first place !!). However as to why/ how this has occurred I don't know - There shouldn't have been any manually 'intervention' on these folders.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks for the feedback on the folder name issue Craig. Can the .ini file be safely deleted? It is causing a problem because at the root level we have some 140 or so staff folders - mostly showing their correct folder name, such as SmithJB, but as per part of the question we have quite a few that show 'My Documents' which is difficult when trying to track down staff work!
Do you have any idea why we are getting the problem with the orphaned shares (event 2511) which was the main issue we were concerned about?
Do you have any idea why we are getting the problem with the orphaned shares (event 2511) which was the main issue we were concerned about?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks Craig
I'll give this a go tomorrow and feed back on result. Apologies for the delay in picking up your post.
I'll give this a go tomorrow and feed back on result. Apologies for the delay in picking up your post.
ASKER
Hi Craig
Sorry this one slipped off of the radar due to holiday and a major comms infrastructure change. I'll try and re-visit this later next week.
Sorry this one slipped off of the radar due to holiday and a major comms infrastructure change. I'll try and re-visit this later next week.
ASKER
Hi Craig
This worked - thank you
This worked - thank you
To remove orphaned shares, you can simply go into Windows registry and remove them manually (just only those you do not need anymore). Please see where shares are stored in a registry
http://support.microsoft.com/kb/125996
Just use only information about shares location in registry
Regards,
Krzysztof