Well, first you must divide network to intra and DMZ. In DMZ only Windows stuff is ISA server for Exchange - OWA etc... In Intra I got divided server with pre-set aliases, for example company ARC have every server with name ARCServer-function_of_server, e.g. ARCServer-Exchange. The "-" symbol is for parsing purposes, e.g. If first token is equal ARCServer, it is in group servers and second token identifies server. If first token is ARC, second is workstation alias. For example ARC-001, ARC-002 etc... I also use different names for locations, for locality Prague is PR-001, PR-002, locality Brno is BR-001, BR-002 etc... So I can use "testing" localities - when I created new script, I can try it first on one locality, e.g. If token 1 not equal to PR, skip. For another infrastructure, of course I am using AD + DNS, RAS is not implemented (I had callbacks, now I am on VPNs from CheckPoint). For File&Print servers (and Exchange of course) I am using clusters. I also have deployment server for distribution purposes, in fact I got three - one is data storage, second is production server and last is testing server. When testing server becomes better (performance, stability...), they switch their roles, so I am switching servers every few months.