File Server designs/templates and auditing
Posted on 2012-08-29
1) Do you have a standard file server build for file servers in your environment? Is that consistent for all servers serving a specific role? Our IT have published a file server design document, which to me indicates that is going to be a standard for all new file servers utilised. Is this common?
2) Is the file server, before actual user files are added to do, referred to anything in particular, i.e. it’s basically the bare bones of the config but with no data as yet.
3) Will a standard file server build that’s intended to be the benchmark for all future file servers have a specific “name” in windows environments?
4) And will the file server in design phase typically be built well in advance of data being added to it and it going “live”. We want to audit the config of the template copy, but have no real idea how long before IT sections will build it, prior to it going live.
5) Are there any issues in auditing the config of the server in a test environment before it goes live, i.e. configs that cant be applied to a server in a non live environment that will only be applied once it goes into a live domain? I.e. is it worth auditing a file server in build phase in a non live environment, or better to wait until it goes into the live domain?