Product Directory Structure Recommendations Parent topic

Trend Micro recommends the following when planning your Product Directory structure for managed products and child servers:

Considerations when Grouping Managed Products or Child Servers

Structure
Description
Company network and security policies
If different access and sharing rights apply to the company network, group managed products and child servers according to company network and security policies.
Organization and function
Group managed products and child servers according to the company's organizational and functional division. For example, have two Control Manager servers that manage the production and testing groups.
Geographical location
Use geographical location as a grouping criterion if the location of the managed products and child servers affects the communication between the Control Manager server and its managed products or child servers.
Administrative responsibility
Group managed products and child servers according to system or security personnel assigned to them. This allows group configuration.
The Product Directory provides a user-specified grouping of managed products which allows you to perform the following for administering managed products:
  • Configuring managed products
  • Request products to perform a Scan Now (if this command is supported)
  • View product information, as well as details about its operating environment (for example, product version, pattern file and scan engine versions, operating system information, and so on)
  • View product-level logs
  • Deploy virus pattern, scan engine, anti-spam rule, and program updates
Plan this structure carefully, because the structure also affects the following:

Considerations for the Structure

Consider
Effect
User access
When creating user accounts, Control Manager prompts for the segment of the Product Directory that the user can access. For example, granting access to the root segment grants access to the entire directory. Granting access to a specific managed product only grants access to that specific product.
Deployment planning
Control Manager deploys update components (for example, virus pattern files, scan engines, anti-spam rules, program updates) to products based on Deployment Plans. These plans deploy to Product Directory folders, rather than individual products. A well-structured directory therefore simplifies the designation of recipients.
Outbreak Prevention Policy (OPP) and Damage Control Template (DCT) deployments
OPP and DCT deployments depend on Deployment Plans for efficient distribution of Outbreak Prevention Policy and cleanup tasks.

Managed Product Icons

Icon
Description
eman.gif
InterScan eManager
osce.gif
OfficeScan Corporate Edition
spnt.gif
ServerProtect Information Server
domain.GIF
ServerProtect Domain
NT.gif
ServerProtect for Windows (Normal Server)
NW.gif
ServerProtect for NetWare (Normal Server)
imss.gif
InterScan Messaging Security Suite
iwss.gif
InterScan Web Security Suite
isnt.gif
InterScan VirusWall for Windows
isux.gif
InterScan VirusWall for UNIX
smex-2.gif
ScanMail for Microsoft Exchange
smln.gif
ScanMail for Lotus Notes
nvw_icon.gif
Network VirusWall
netscreen_fw-2.gif
NetScreen Global PRO Firewall
mp_active.gif
Managed Product connection status icon
Arrange the Product Directory using the Directory Manager. Use descriptive folder names to group your managed products according to their protection type or the Control Manager network administration model.