1

I have windows staging and live servers for hosting our companies asp .net web applications.

Recently, there have been issues with changes existing between the staging environment and the live environment that have only been discovered during the release process.

Ideally, I would like to proactively monitor any differences between the servers to ensure that releases are as smooth as possible when moving the sites.

Also, we have a change management process in place for the servers but this provide a further degree of reassurance.

Thanks,

Brian.

womble
  • 95,029
  • 29
  • 173
  • 228
Brian Scott
  • 113
  • 3
  • anytime you let a human touch a server things will be screwed up! – tony roth Oct 21 '10 at 19:52
  • *Also, we have a change management process in place for the servers but this provide a further degree of reassurance.* What does that statement mean, exactly? What's your process for moving things from staging to production? What exactly is being moved from staging to production; web sites, application pools, etc? – joeqwerty Oct 21 '10 at 11:45

3 Answers3

0

As far as I know SCOM can do this for you, perhaps not to a byte level like diff'ing the drives but from a windows config perspective I'm pretty sure it'll do what you need.

Chopper3
  • 100,240
  • 9
  • 106
  • 238
0

You could use the diff tool or the binary diff tool.

Ablue
  • 1,140
  • 1
  • 12
  • 32
0

WebDeploy does a good job of capturing all configurations that are particular to ASP .Net Web Apps. It captures app pools, registry settings, gac assemblies, etc.

LeWoody
  • 299
  • 1
  • 2
  • 8