Upgraded data

The following 7.x data classes have their data populated from the 6.x data classes:

Base type is Infrastructure Device with associated data classes:

• Device Identification
• Device Details
• Device Network Interface
• Device SNMP Info
• Device TCP/IP
• Discovery Task
• AMT Network Info
• ASF Network Info

The following data classes are not imported:

• Device Bridge Port
• Medium Member

GridControl-SNMP Device Classification

Scrolling in the grid causes the grid columns to expand beyond the container

Network Discovery SNMP Device Classifications will not replicate

Topology View is unable to show computers gathered by Network Discovery

ATRSHost crash when stopping a running Network Discovery task

Using Connection Profiles

Network Discovery tasks use Connection Profiles to configure the protocols that are used to communicate with network devices.

Importing .MIB files on Symantec Management Platform 7.0

Symantec Management Platform Security Privileges

Scheduling a Network Discovery task

If you schedule a Network Discovery task to run on a recurring basis, you won't be able to stop that task unless you either delete the task, or cancel the schedule by deleting the next scheduled occurrence of it in Manage > Jobs and Tasks.

HTTP is not reported as a discovery protocol

Even though it may be enabled in a connection profile, the filter for HTTP will not work because HTTP is not a discovery protocol. This means that you will not be able to filter devices by HTTP in the Discovered Devices report. 

Recommended not to discover a Parent Notification Server from a Child Notification Server

It is HIGHLY recommended not to discover a Parent Notification Server from a Child Notification Server. It causes some strange behavior within the Site Server settings on the Parent Notification Server.

Retry and Timeout values may not be used during connection

Each protocol lets you specify its own timeout and retry value. However, these values are typically only used during the execution of commands by the protocols, but not when attempting to connect to a target computer using these protocols. Because Network Discovery only attempts to connect to targets to determine availability, but does not execute any commands over the protocols used to connect, it should not be expected by the user that failed connection attempts would be retried. Failed connectiona are only retried during the next scheduled or manual discovery process.

Unable to push Altiris Agent to Windows Servers discovered using SNMP/default

Discovered Devices by Group Report pie chart not working

Dummy Connection Profile listed in Discovery drop-down

Discovered Devices by Group drill-down not working

Stop request doesn't work for multi-selected tasks

Error Refreshing Discovered Devices by Group Report

After changing information for an existing SNMP Device Classification, any device previously classified using that entry needs to be re-discovered to be reclassified