title: Designing a client/server program, design question (.Net)
body: <p>We are designing a client/server program and I need some help with a design decision.</p>
  
  <p>The server side of the program will run as a service on a number of Windows servers, the service is monitoring those servers, when needed the service will email us a report.</p>
  
  <p>The client will be used to control and manage the services running on the servers, but won't always be running. </p>
  
  <p>My question is where and how should I store the configuration for the service. The settings (smtp etc) will be defined on the client but the services running on remote servers (there may be many) need to be updated with the settings and also retain those settings unitil they are updates again.</p>
  
  <p>I can think of two options, a central Windows Share where the services read the settings from or when the client hits 'Save' the settings are saved to a location on each server.</p>
  
  <p>What would you do? Anything I should be aware of?</p>
  
  <p>Thanks</p>