Windows Storage Server 2003 File Server Role - Export Orphaned folders list to *.csv
Trying to script an export of orphaned folders on a 2003 file server, we are migrating to a 2008 SP2 File Server. The 2003 server does not have powershell installed and the 2008 server can only be certified with Powershell 1.0. I previously exported all the usernames and HomeDirectories to excel and then dumped the folder list and did a compare. That was painfully slow and It gave me that outdated feeling, any help is appreciated.
I am not sure I understand your Question. Are you wanting a PowerShell script to find orphaned folders on your 2003 server even through PowerShell is not installed on it? Do you want the script in VB? What do you mean by "orphaned folders"? My assumption would be empty folders, but I am not sure. Also, what data do you want in the dump into your CSV file?
Justin
Justin
ASKER
Sorry for the lack of clarity, the powershell can be on the 2008 Cluster.
And yes a wsh or vbscript would be required for the 2003 server.
Orphaned folders are deleted users former home directories,
csv or txt. would be ok.
And yes a wsh or vbscript would be required for the 2003 server.
Orphaned folders are deleted users former home directories,
csv or txt. would be ok.
So, to further clarify, you need a VBScript which polls AD for user accounts, and then compares that output to a list of home directories on your server. The comparison would then output to a CSV file any folders in your home directory it finds which do not have a valid AD account present.
Is that correct?
Is that correct?
ASKER
2003 server yes, on the migrated to server 2008 - that could be powershell, but not 2.0 since the domain is still at 2003 r2 level. Quest QADUSER syntax creates a problem for iterating through the folders and htne checkiong AD for the sid state. I can do the discovery on either server, just informaing that the domain is 2003 r2.
Do the folder names match the AD names? In other words, if John Doe's AD account is jdoe, will his user folder be named jdoe?
ASKER
90%, user name sytanx is first initial;last initial: number.
So jDoe would be jd01, next JDoe would be jd02 etc.
Exec's and Managers can reqest a non - standard name.
Just initerested in the standard 90% of users.
So jDoe would be jd01, next JDoe would be jd02 etc.
Exec's and Managers can reqest a non - standard name.
Just initerested in the standard 90% of users.
OK, but the question is this: in your 90%, does the USER NAME always match the FOLDER NAME?
ASKER
YES,
Sorry I did not understand your question previously,
the login name jd01@domainname , matches the folder name jd01
Sorry I did not understand your question previously,
the login name jd01@domainname , matches the folder name jd01
I have asked a Moderator to add this to the VBScript Zone for you.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Got it, Ill let you know A.M. tomorrow. I'll kick it off before leaving tonight, thanks.
ASKER
This Worked, I am now looking at the data set for false negatvies. So far it appears to have been very successful. Thanks
No problem... Just do me a favor, and if you reuse it in the future, be sure you don't pull Dave's name out of the comment lines. :) He is rather proud of his work (as he has a right to be).
Justin
Justin
ASKER