Make a Master Server
Applies to: 
SQL Server
Important
On Azure SQL Managed Instance, most, but not all SQL Server Agent features are currently supported. See Azure SQL Managed Instance T-SQL differences from SQL Server for details.
This topic describes how to make a master server SQL Server by using SQL Server Management Studio or Transact-SQL.
Before You Begin
Security
Distributed jobs that have steps which are associated with a proxy run under the context of the proxy account on the target server. Make sure that the following conditions are met or job steps that are associated with a proxy will not be downloaded from the master server to the target:
The master server registry subkey \HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\<*instance_name*>\SQL Server Agent\AllowDownloadedJobsToMatchProxyName (REG_DWORD) is set to 1 (true). By default, this subkey is set to 0 (false).
A proxy account exists on the target server that has the same name as the master server proxy account under which the job step runs.
If job steps that use proxy accounts fail when downloading them from the master server to the target server, you can check the error_message column in the sysdownloadlist table in the msdb database for the following error messages:
"The job step requires a proxy account, however proxy matching is disabled on the target server."
To resolve this error, set the AllowDownloadedJobsToMatchProxyName registry subkey to 1.
"Proxy not found."
To resolve this error, make sure a proxy account exists on the target server that has the same name as the master server proxy account under which the job step runs.
Permissions
Permissions to execute this procedure default to members of the sysadmin fixed server role.
Using SQL Server Management Studio
To make a master server
In Object Explorer, connect to an instance of the Microsoft SQL Server Database Engine, and then expand that instance.
Right-click SQL Server Agent, point to Multi Server Administration, and then click Make this a Master. The Master Server Wizard guides you through the process of making a master server and adding target servers.
From the Master Server Operator page, configure an operator for the master server To send notifications to operators by using e-mail or pagers, SQL Server Agent must be configured to send e-mail. To send notifications to operators by using net send, the Messenger service must be running on the server where SQL Server Agent resides.
E-mail address
Sets the e-mail address for the operator.Pager address
Sets the pager e-mail address for the operator.Net send address
Sets the net send address for the operator.From the Target Server page, select target servers for the master server.
Registered Servers
Lists the servers registered in Microsoft SQL Server Management Studio that are not already target servers.Target Servers
Lists the servers that are target servers.>
Move the selected server to the target server list.>>
Move all servers to the target server list.<
Remove the selected server from the target server list.<<
Remove all servers from the target server list.Add connection
Add a server to the target server list without registering the server.Connection
Change the connection properties for the selected server.From the Master Server Login Credentials page to specify if you want to create a new login for the target server, if necessary, and assign it rights to the master server.
Create a new login if necessary and assign it rights to the MSX
Create a new login on the target server if the login specified does not already exist.
Using Transact-SQL
To make a master server
Connect to the Database Engine.
From the Standard bar, click New Query.
Copy and paste the following example into the query window and click Execute. This example enlists the current server into the AdventureWorks1 master server. The location for the current server is Building 21, Room 309, Rack 5.
USE msdb ;
GO
EXEC dbo.sp_msx_enlist N'AdventureWorks1',
N'Building 21, Room 309, Rack 5' ;
GO
For more information, see sp_msx_enlist (Transact-SQL).