Viewing the Secondary Site in the Configuration Manager Console

Once your secondary site has been installed, it direct be viewable within the Configuration Manager corbel. Any child site (including primary and proxy sites) will be listed in the Site Management swelling directly under its designated parent original site. Once the secondary site is expanded.

Settings node is available with almost the strict same options as the primary location, excluding the Client Agent node. Client actor properties are inherited from the father primary site and cannot be configured at the delegate site (Figure 5.29).

locations are unsecured, we chose to constitute these servers read-only domain controllers. When we started planning as antidote to our Configuration Manager 2007 rollout, we past dispute to also use these servers taken in the character of secondary site servers since these sites were related through relatively slow T1 lines. We planned gone ~ how our sender addresses would have existence set up, including rate limits and schedules basedon the product hours of each location and got approval from our comptroller to go ahead with the rollout.

We past dispute to use the Secondary Site Installation Wizard from the Configuration Manager ancone to deploy our secondary site servers since we have no IT staff at these locations and for the reason that it seemed to be the easiest rule overall. We made sure that altogether of the prerequisites had been met (or in like manner we thought) and started the investiture. We expected to see these sites point out to up under our central-primary location in the Configuration Manager console on the other hand nothing ever happened. We checked the delegate site servers to see if ~ one Configuration Manager folders had been created for the period of installation but nothing was there. Nothing happened. 

locations are unsecured, we chose to mould these servers read-only domain controllers. When we started planning in quest of our Configuration Manager 2007 rollout, we categorical to also use these servers since secondary site servers since these sites were leading one into the other through relatively slow T1 lines. We planned lacking how our sender addresses would have existence set up, including rate limits and schedules basedon the fruit hours of each location and got approval from our economist to go ahead with the rollout.

We indisputable to use the Secondary Site Installation Wizard from the Configuration Manager bracket to deploy our secondary site servers because that we have no IT staff at these locations and since it seemed to be the easiest manner overall. We made sure that aggregate of the prerequisites had been met (or with equal rea~n we thought) and started the inauguration. We expected to see these sites mask up under our central-primary station in the Configuration Manager console ~-end nothing ever happened. We checked the proxy site servers to see if somewhat Configuration Manager folders had been created for the period of installation but nothing was there. Nothing happened.