How to Prepare Servers for Senders
Applies To: System Center Configuration Manager 2007, System Center Configuration Manager 2007 R2, System Center Configuration Manager 2007 R3, System Center Configuration Manager 2007 SP1, System Center Configuration Manager 2007 SP2
Senders can only be installed on the primary or secondary site server computer. Before you install a sender, the connectivity system between the sites must already be installed and configured on the server on which you install the sender.
The standard and courier senders are automatically installed on Configuration Manager site server systems and cannot be installed manually.
Preparing Servers for RAS Senders
For Remote Access Service (RAS) senders, install Microsoft RAS on the source and destination sites. Create RAS phone book entries for the RAS servers on each destination site. On each destination site, create a user account that the RAS sender on the site server can use and then grant the account Dial in and Dial out permissions in the RAS Administrator.
Before creating an Systems Network Architecture (SNA) RAS sender on a site server system, you must ensure that the site server system is configured correctly. This procedure is performed outside of Configuration Manager 2007, using Microsoft SNA Server. For detailed information about the steps and terms in this procedure, see your SNA Server product documentation.
To prepare a server for an SNA RAS sender
Check that Microsoft SNA Server is installed on computers in both the sending and destination sites. Make logical unit-pair connections between these installations of SNA Server.
On the server running SNA Server that you will install SNA sender on, create an advanced program-to-program communications (APPC) local logical unit that the SNA sender and SNA receiver will use.
On the destination sites, create an APPC local logical unit.
The logical units on these sites are used by the current site’s SNA sender.
Create a connection between the current site server SNA sender logical unit (the local logical unit) and all destination site SNA sender logical units (remote logical units). Create the connection on both sites.
The logical unit pair for both connections can use either #BATCH (batch) or #INTER (interactive) modes. For more information about local logical units, remote logical units, modes, and connections, see the SNA Server product documentation.
Before creating any of the three types of non-SNA RAS senders (Asynchronous, ISDN, or X.25) on a site system, ensure that the site system is configured correctly. To do so, use Microsoft Windows administration tools to complete the following procedures. For detailed information about the steps and terms in this procedure, see your Windows server product documentation.
To prepare a server for a non-SNA RAS sender
Ensure that Microsoft Windows RAS software is installed on a site system in the current site and in all destination sites. (The site systems on which RAS software is installed are RAS servers.)
On the RAS servers where you will install the RAS sender, create RAS phone book entries for the RAS servers at each destination site.
The types of phone book entries determine the types of senders and sender addresses you create. For example, if you create an ISDN phone book entry for a destination site, you must create an ISDN RAS sender address and an ISDN RAS sender on the RAS server.
At each destination site, create a user account that the RAS sender on the current site can use.
In RAS Administrator, grant the account Dial in and Dial out permissions.
For additional information, see Configuration Manager 2007 Information and Support.
To contact the documentation team, email SMSdocs@microsoft.com.