How to Produce a Document of Folder Structure of Data Server

Associate
Joined
22 Mar 2012
Posts
1,161
Hi Guys,

One of our customer has asked us to produce a report detailing the folder structure of their data server so that they can review it and then hopefully tidy it up.

As much as I would love to do this manually :eek: I am hoping someone can point me in the direction of some software that will do this for me.

I used Treesize and then exported it but the results weren't particularly clear and made for a 1300 page document:D

They haven't asked for it yet but I can also see them asking us to detail the permissions for each folder as well. So if anyone has any suggestions on this they would also be appreciated :D
 
Do you know what format you want the results displayed as? Should be fairly easy to do a script that would output details (depending on how you would want it displayed!) What platform is the server? Win or *nix? Is it multiple drives that you want reported on?

I wrote a powershell script to do this, ended up identifying around 10,000,000 folders. You can get folder permissions this way too.

As for permissions, this will depend on if they want to keep the structure or not. I'd suggest that if they want wholesale permissions changes you create a new structure and move the files between the two. Failing that, come up with a manageable group structure for read/write, read only and traverse/list and populate those groups appropriately. I'm guessing that a 1300 page document means you have a reasonable number of users here so its very much a case of identifying someone in the business that wants to help facilitate change (for the better) and getting that person or group of people to do a lot of the legwork for you.

When you're done, write a solid document for your helpdesk team to follow or it'll have gone to **** in a week.

It's Windows based. Ideally I suppose we would want to output it to a word/pdf document so that the client can read it fairly easily. Something tells me it won't be that simple though. I suspect we'll have to go down the .csv or .txt route and then work from there to make it into a easily readable doc.

Do you guys have an example scripts? I'll then tailor it to the network.
 
Back
Top Bottom