If you are only running FTP, then 99% chance all your IIS configuration is in %windir%\system32\inetsrv\config (there are three config files there)
There's a history of changes in %windir%\system32\inetsrv\history You just need to keep track of the local user passwords (if you are using Windows accounts rather than IIS accounts). Given that you have to create these in the first place, you must have some way of storing this info someway. Or, do as Brian suggests, and do a backup of the server. Cheers Ken -----Original Message----- From: Kurt Buff [mailto:[email protected]] Sent: Friday, 9 March 2012 7:59 AM To: NT System Admin Issues Subject: Re: FTP site configuration backups That's a good theory, and indeed part of the solution, but in practice, people are fallible, and will fail to keep the script updated. So, what's needed is a script to read the current configuration and produce output that can be fed back into (another|this) script to recreate the site on a new machine. I'm thinking it might be a good project for me to learn some 1337 powershell skllz. Kurt On Thu, Mar 8, 2012 at 15:11, Joseph L. Casale <[email protected]> wrote: > 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 [[email protected]] > 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 [email protected] > with the body: unsubscribe ntsysadmin > ~ 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 [email protected] with the body: unsubscribe ntsysadmin ~ 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 [email protected] with the body: unsubscribe ntsysadmin
