SC 3.x was simple a server and CLI in one so every instance you were running SC server and CLI.
SC 4.x we have split the server and CLI. The server is a server and the CLI a CLI.
You can certainly run an SC server, agent, and CLI on every app host or you can have SC server be central. In SC 4.x we dont dictate just like we didnt in SC 3.x that server should be central.
The only difference between SC 3.x and 4.x is that 4.x is java and 3.x is perl and that 4.x server is a daemon w/APIs where the 3.x server was not and had no APIs. Please explain how you feel SC 3.x was better than 4.x? I am not understanding your points in enough detail?
No SC 4 is a server and runs a daemon. I am saying it doesnt have to be central. The only difference between SC 4 and 3 was SC 3 wasnt a deamon it was a binary, however we needed to do things like support APIs and many other features so it was necessary to create a server.
Are you saying you have requirements to not run daemons? If so how do you use other products? Not many products out there that dont run some kind of daemon at least not backup products.
What you are wanting to do will be just as easy if not easier
SC 4 CLI allows you to actually configure schedules and if you want you can even talk to SC server directly over APIs. Did I mention there is also a powershell toolkit for interacting with SC 4? You could also install CLI on remote host and configure schedules from there. CLI can run on any host not just where SC server is. Of course this requires opening ports but the way I see things is you have a lot more flexibility now then you did before.
In addition the old SC 3.x did run a service for the GUI and hidden in this was a database, the database is now part of server and that is why CLI can now create schedules, not just GUI.
I recommend you try SC4 and experiment with different possibilities...we will definitely assist you but give it a chance. I know it is definitely more and a larger footprint that SC 3 but we did try and I feel succeeded at keeping things simple while providing enormous flexibility. If you find some areas of improvements please let us know and we will address them.
You bring up a good point, I will take this to engineering maybe there is something simple we can do to create a standalone SC server which doesnt run the web services but I dont think there is, everything is rather tightly coupled.