Considerations when planning your System Tree An efficient and well-organized System Tree can simplify maintenance. Many administrative, network, and political realities of each environment can affect how your System Tree is structured. Plan the organization of the System Tree before you build and populate it. Especially for a large network, you want to build the System Tree only once. Because every network is different and requires different policies, and possibly different management, plan your System Tree before adding the systems. Regardless of the methods you choose to create and populate the System Tree, consider your environment while planning the System Tree. Administrator accessWhen planning your System Tree organization, consider the access requirements of users who must manage the systems. Environmental borders and their impact on system organizationHow you organize the systems for management depends on the borders that exist in your network. These borders influence the organization of the System Tree differently than the organization of your network topology. Subnets and IP address rangesOften, organizational units of a network use specific subnets or IP address ranges, so you can create a group for a geographic location and set IP address filters for it. Operating systems and softwareConsider grouping systems with similar operating systems to manage products and policies more easily. If you have legacy systems, you can create a group for them and deploy and manage security products on these systems separately. Also, by giving these systems a corresponding tag, you can automatically sort them into a group. Tags and systems with similar characteristicsYou can use tags and tag groups to automate sorting into groups. Parent topic: Using the System Tree and Tags
Considerations when planning your System Tree An efficient and well-organized System Tree can simplify maintenance. Many administrative, network, and political realities of each environment can affect how your System Tree is structured. Plan the organization of the System Tree before you build and populate it. Especially for a large network, you want to build the System Tree only once. Because every network is different and requires different policies, and possibly different management, plan your System Tree before adding the systems. Regardless of the methods you choose to create and populate the System Tree, consider your environment while planning the System Tree. Administrator accessWhen planning your System Tree organization, consider the access requirements of users who must manage the systems. Environmental borders and their impact on system organizationHow you organize the systems for management depends on the borders that exist in your network. These borders influence the organization of the System Tree differently than the organization of your network topology. Subnets and IP address rangesOften, organizational units of a network use specific subnets or IP address ranges, so you can create a group for a geographic location and set IP address filters for it. Operating systems and softwareConsider grouping systems with similar operating systems to manage products and policies more easily. If you have legacy systems, you can create a group for them and deploy and manage security products on these systems separately. Also, by giving these systems a corresponding tag, you can automatically sort them into a group. Tags and systems with similar characteristicsYou can use tags and tag groups to automate sorting into groups. Parent topic: Using the System Tree and Tags
