So you know the passwords, you know the config, you set the perms, so why not simply keep a powershell script of all the account creation etc updated. It sounds like like its fairly repetitive and you could simply loop through all the user/directory creation, apply acl's etc from the list of users.
Server breaks, you redeploy and execute a continuously updated script. Powershell has some IIS extensions (although I have never done explicit ftp work with it)... I really don't see it needing to be more complex than this? ________________________________________ From: Kurt Buff [kurt.b...@gmail.com] Sent: Thursday, March 08, 2012 2:12 PM To: NT System Admin Issues Subject: Re: FTP site configuration backups I believe I have a slightly different situation than what you're describing, but I could be wrong, so correct me if I am. On this server, the FTP users are accounts in the local accounts base - we chose to do that so that vendors/partners would each have a protected directory with exclusive access to it. That would place the names and accounts in the SAM database, correct? Regardless, this would require poking holes in the firewall that aren't already there, which I'm reluctant to do. Thanks, Kurt ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe ntsysadmin
