2. Configuring Senders
By default, standard and courier senders are
installed automatically on every site server. To configure additional
senders, refer to http://technet.microsoft.com/en-us/library/bb694245.aspx, which discusses preparing servers for different senders.
Depending on the number of child sites, you may need to modify the sender properties. Figure 4 displays the default settings for the standard sender.
The Advanced tab allows you to specify the
maximum number of concurrent connections the ConfigMgr server can make,
the number of retries allowed, and how often the sender may retry a
failed attempt.
The “Maximum current sendings” section allows
you to specify the maximum number of simultaneous communications allowed
for this sender and each destination site:
All sites—
Specifying a number here will set the total number of simultaneous
connections. This number should always be larger than the Per site
setting.
Per site— This setting determines how many simultaneous connections are permitted to a single site.
For a smaller hierarchy, the default settings
may be sufficient. If you have more than two or three child sites, you
may want to consider increasing these numbers, provided there is
available bandwidth from the parent site. See http://technet.microsoft.com/en-us/library/bb632976.aspx for additional information on sender properties.
3. Attaching to Parent
After installing the primary site and
configuring the addresses and senders, you are ready to attach to a
parent site. Perform the following steps:
1. | To
attach a primary child site to a parent, connect to the ConfigMgr
console of the child site, expand Site Management, right-click the
primary site name, and select Properties.
|
2. | In the General tab of the Site Properties dialog box, click the Select Parent Site button.
|
3. | Because you have already created the proper addresses, simply click the Report to parent site radio button displayed in Figure 5
and select the parent site from the dropdown list. (If you have an
Asset Intelligence synchronization point configured on the child site,
you must remove this role before attaching to the parent site.)
|
Once
you complete the wizard, replicating objects from the parent site to
the child site may take from a few minutes to several hours, depending
on the number of objects (packages, programs, collections, software
updates, and so on) on the parent site. Review sender.log on both the
parent and child site to verify site connectivity. Also, when you attach
your site to a parent site, you may experience backlogs in some of your
inbox folders (for example, ddm.box, dataldr.box, sinv.box,
statmgr.box\statmsgs, and statesys.box, to name a few). During the
attachment process, local inbox processing is paused until the child
site has forwarded all site and client information to its new parent
site.
4. Installing Child Primary Sites
When installing a ConfigMgr site that will be a
child site, install the site and then apply the same level of service
pack (and R2 and hotfixes, if applicable) on the parent site before
attaching the child site to the parent site.
After attaching the child primary site
to the parent site, perform any additional configurations necessary.
5. Installing Secondary Sites
Two methods are available for installing secondary sites:
- Installing directly from the ConfigMgr installation media
- Installing the secondary from the ConfigMgr console of the parent site
If you choose to install
using installation media, you will also need to ensure you apply the
appropriate service pack (and R2, if required). Installing the secondary
site from the ConfigMgr console will install the same version of
ConfigMgr that is on the parent site.
To install a secondary site from its parent, perform the following steps:
1. | From
the ConfigMgr console of the parent site, expand Site Database ->
Site Management, right-click the parent site name, and then select New
Secondary Site to begin the Secondary Site Creation Wizard.
|
2. | After the Welcome screen, specify the site code and site name. Click Next.
|
3. | At
the Site Server page, specify the site server name (NetBIOS name) and
installation directory (for example, C:\ConfigMgr). Click Next.
|
4. | Select
Copy installation source file over the network from the parent site
server. If the secondary site is on a very slow link, you may want to
consider pre-staging the source files on the new server and then specify
the path.
|
5. | Specify
a new sender address (use the FQDN if possible). Also, specify a site
connection account, or ensure that the system account of the parent site
has administrative access to the new secondary site server.
|
6. | Specify the sender address from the secondary site to the primary (use the FQDN if possible).
|
7. | Complete the installation wizard, and monitor the following log files on the new secondary site:
SMS_BOOTSTRAP.log ConfigMgrPrereq.log ConfigMgrSetup.log
After ConfigMgrSetup.log indicates the installation is complete,
several background processes will continue to complete the
configuration. You can view the installation and configuration status in
the ConfigMgr console from the parent site, as shown in Figure 6, which shows the state as “Pending.” Review the ConfigMgrSetup.log for any potential problems.
|
8. | After installation completes, install R2 (if applicable). |
