When I import settings from a server that is "on" into a server that is "off", it turns the latter "on". That's problematic. My use case is that I am setting up a backup server, and am copying the production server's settings to the backup. I don't want the backup server to be "on" because I don't want any of the imported jobs to start (unless/until we need to run them). Of course, I can just turn the server off again after the import -- but there is a window of vulnerability there where jobs could start if a trigger condition were to occur at just the wrong time. It doesn't seem like On/Off should be a server configuration item, but rather an independent "switch" of some sort.