You can sort the systems into your ePO - SaaS System Tree using a combination of system criteria and other elements.
Creating the basic groups
You can organize the System Tree by creating small groups.
GEO — Geographic location
NET — Network location
BU — Business unit
SBU — Sub business unit
FUNC — Function of the system (web, SQL, app server)
CHS — Chassis (server, workstation, laptop)
Selecting and ordering the basic groups
After you decide on the basic building blocks for groups in the System Tree, you must determine which building blocks to use and in which order based on these factors:
Policy assignment — Do you have many custom product policies to assign to groups based on chassis or function? Do certain business units require their own custom product policy?
Network topology — Do you have sensitive WANs in your organization that a content update might easily saturate? If you have only major locations, this is not a concern for your environment.
Client task assignment — When you create a client task, such as an on-demand scan, do you need to do it at a group level, like a business unit, or system type, like a web server?
Content distribution — Do you have an agent policy that specifies that certain groups must get their content from a specific repository?
Operational controls — Do you need specific rights delegated to your ePO - SaaS admin that allow them to administer specific locations in the tree?
Queries — Do you need many options when filtering your queries to return results from a specific group in the System Tree?
After you choose the basics for your tree structure, create a few sample System Tree models and look at the pros and cons of each design. There is no right way or wrong way to build your System Tree, just pluses and minuses depending on what you choose.
Here are a few of the most commonly used System Tree designs:
GEO -> CHS -> FUNC
NET -> CHS -> FUNC
GEO -> BU -> FUNC