Hi,
I'm one of the engineers working on a clean up project for my company. My company's current web application is outdated and our developers are currently working on a new solution, but in the meantime we have been patching multiple errors and it has started to get way out of hand. I am not a developer, but I have been tasked to re-architect the current web enviroment using the current hardware and software. Unfortunetly, I don't have much experience using IIS and need some help trying to figure out the best way to fix the current application while we are waiting on the new one to be completed.
In our current environment, the old engineer used four web frontends with IIS 7 and a F5 load balancer to control web access. The files were syncronized using a local robocopy script ran through a scheduled task every minute on each server (serious...not even joking). even though the files were mostly in sync, they never had a way to sync configuration changes and all four servers consistently had different IIS configurations. The current environment also uses classic asp to control some of the most important functionality, and also uses asp.net to support the features that were unable to be created in classic asp.
I have read and heard a lot of great information on the shared configuration through IIS 7, and have recently deployed it on our new development environment (they never had a development or testing environment prior, all changes were made and tested in production). So far this has worked, but with the F5 load balancer on the production network, I am unsure whether this is a viable solution. I have just started looking at WFF, but I don't know enough about it yet to determine if this will meet our needs. Any information will be greatly appreciated. Thank you in advance.
Current Needs:
1. Syncronize application files (current thought is to put in a CIF share and point Websites to the share instead of locally on each server)
2. Syncronize IIS Configuration (shared configuration? or WFF)
3. Use F5 for load balancing user connections
4. Fire previous engineers and development team