I am happy to help. I have gotten a lot of good help from this site over the years. I have all maintenance tasks in my environments configured with custom stored procedures that are called by jobs. Your last post revealed something new to me though, which is that the management server you want to use doesn't have the SQL engine and agent installed.

I am not sure why you don't want to place stored procedures on databases in any of your existing SQL Servers. Just create a management database like "DBA" and create your procedures there. Even if you don't want to do that you could still create a job that has all the code you need in it. Personally I have several database management jobs on every one of my SQL Servers, which is recommended over having one centralized management server.

All that being said, you can still issue sql commands to affect maintenance tasks from a server that does not have the sql engine or agent installed, it's just that I can't think of a good reason why you would want to when you have an SQL Agent service available to you on your existing sql server instances. If you are resolved to use just one server can you select a server with the sql engine and agent on it? If so then we can discuss what you need to do from there, if not then you will be forced to issue sqlcmd calls to the other servers for your maintenance tasks.

Regards,

Toby