Installation Manual

HP Storage Essentials SRM 6.0 Installation Guide 355
Keep in mind the following:
• You cannot edit the Everything organization.
• Users can view all elements only in the Discovery pages. In all other pages, only the members
of the active organization are available. Discovery lists in HP SE (Discovery tab on the SE Home
page) are not filtered. Users can see all elements in the discovery lists regardless of their
affiliation with an organization.
• Events from all elements regardless of the user’s organization are displayed by Event Manager.
• Reports only display elements assigned to the user's organization, including child
organizations. For example, if you attempt to view a Host Summary report and you do not have
permission to access hosts through your organization, you are not given information about the
hosts in the report. This is also true when you email reports. If you do not have permission to
access hosts, the reports you e-mail, including the host-specific reports, will not contain
information about hosts. If the users receiving your reports want to be able to view information
about hosts, one of the following must happen:
• The hosts in question must be added to your organization.
• Someone else, who has the hosts in question already in their organization, must send the
reports.
Planning Your Hierarchy
Before you begin creating organizations, plan your hierarchy. Do you want the hierarchy to be
based on location, departments, hardware, software, or tasks? Or perhaps you want a
combination of these options.
To help you with your task, create a table of users who manage elements on the network and the
elements they must access to do their job. You might start seeing groups of users who oversee the
same or similar elements. This table may help you in assigning users to the appropriate
organizations.
Once you are done with planning your hierarchy, draw the hierarchy in a graphics illustration
program, so you can keep track of which organizations are parents and children.
Create the child organizations first, then their parents. See ”Adding an Organization” on
page 363 for more information.
Naming Organizations
When you create an organization, give it a name that reflects its members. You might want to use
one or more of the following as a guideline:
• Type of elements that are members of the organization, such as switches, Sun Solaris hosts
• Location of the elements, such as San Jose
• Task, such as backup machines
You may find that it is easy to forget which containers are parents and which are children. When
you name an organization, you might want to include a portion of the name of the dominant
parent organization. For example, if you have two types of Web hosts in Boston, Microsoft
Windows and Sun Solaris, you might name the two children organizations
BostonWebHost_Windows and BostonWebHost_Solaris and their parent, BostonWebHosts.