gouksss
asked on
Restoring OWA default status / folders ?
Hi, I'm facing a problem I frequently get when changing things on a Windows 2003 enterprise / Exchange 2003 server. OWA virtual directories are deleted / misconfigured in IIS.
By reinstalling IIS / exchange etc... I've been able to restore the folders in the past, but I'd like to know if there is a proper (and quicker) way to reset the owa folders and their permissions.
By reinstalling IIS / exchange etc... I've been able to restore the folders in the past, but I'd like to know if there is a proper (and quicker) way to reset the owa folders and their permissions.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Fair enough. I wasn't sure if other changes were being made as well. This is one of the reasons that I don't like running other websites on the Exchange server, but I understand not everyone has that luxury.
I honestly don't know of any other ways to (quickly) restore the OWA config. I'd stick with the method you are currently doing, as it works. I've recommended that same method to many others in the past when OWA gets screwed up. Also, you really ought to think about implementing some sort of change management on this web server. If OWA directories are being delete/misconfigured, someone is doing something they ought not to do. If you've got multiple IT people that are making changes, you need to make sure that everyone knows that the OWA directories are off limits.
I understand "what" your problem is, but to be totally honest, I do not understand "why" it is a problem. Would it be that difficult to make sure that everyone knows that "virtual directories a, b, c, and so on are not to be changed, deleted, etc."
Ben
I honestly don't know of any other ways to (quickly) restore the OWA config. I'd stick with the method you are currently doing, as it works. I've recommended that same method to many others in the past when OWA gets screwed up. Also, you really ought to think about implementing some sort of change management on this web server. If OWA directories are being delete/misconfigured, someone is doing something they ought not to do. If you've got multiple IT people that are making changes, you need to make sure that everyone knows that the OWA directories are off limits.
I understand "what" your problem is, but to be totally honest, I do not understand "why" it is a problem. Would it be that difficult to make sure that everyone knows that "virtual directories a, b, c, and so on are not to be changed, deleted, etc."
Ben
Once you get it configured the way you want, go into IIS and perform a backup. This will backup the Metabase from which you can restore using the following:
http://support.microsoft.com/?id=883380
http://support.microsoft.com/?id=883380
ASKER
I'm looking for a way to restore OWA's default config, (AppPool, Web service Extensions, VDs and their app settings / security settings) and not change the rest of IIS configuration.