Dell® Client Manager 3.2 Release Notes

Dell® Client Manager 3.2
Release Notes
Dell® Client Manager 3.2 Release Notes
The software described in this book is furnished under a license agreement and may be used
only in accordance with the terms of the agreement.
Legal Notice
Copyright © 2011 Symantec Corporation. All rights reserved.
Symantec and the Symantec Logo, Altiris, and any Altiris or Symantec trademarks used in
the product are trademarks or registered trademarks of Symantec Corporation or its affiliates
in the U.S. and other countries. Other names may be trademarks of their respective owners.
The product described in this document is distributed under licenses restricting its use,
copying, distribution, and decompilation/reverse engineering. No part of this document
may be reproduced in any form by any means without prior written authorization of
Symantec Corporation and its licensors, if any.
THE DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS,
REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT,
ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO
BE LEGALLY INVALID. SYMANTEC CORPORATION SHALL NOT BE LIABLE FOR INCIDENTAL
OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING,
PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINED
IN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE.
Symantec Corporation
350 Ellis Street
Mountain View, CA 94043
http://www.symantec.com
Dell® Client Manager 3.2
Release Notes
This document includes the following topics:
■
About Dell Client Manager
■
Dell Client Manager versions
■
Supported systems
■
What's new in Dell Client Manager
■
General installation and upgrade information
■
System requirements
■
Upgrade
■
Known issues
■
Fixed issues
■
Other things to know
■
Documentation that is installed
■
Other information
About Dell Client Manager
Dell Client Manager is the most powerful Dell hardware management solution
available for Dell Precision™ workstations, OptiPlex™ desktops, and Latitude™
notebooks. The unprecedented integration of Dell OpenManage Client
4
Dell® Client Manager 3.2 Release Notes
Dell Client Manager versions
Instrumentation with the Symantec Management Platform has resulted in a single,
remote console—the Dell Client Management Console.
Dell Client Manager versions
Dell Client Manager provides three levels of capability to fit the varying needs
and types of organizations. Each level—Standard, Plus, and Dell Client Management
Suite—builds upon the previous level. Each level snaps additional management
capability into the Dell Client Manager unified management architecture, adhering
to and leveraging the same familiar interface, the same database, and the same
management agent. With Dell Client Manager, you outfit yourself with sufficient
capability to produce the outcomes you want in the near term and easily adopt
additional capability—and the associated benefits—when you are ready to take
the next step.
Dell Client Manager Standard
With Dell Client Manager Standard, you can perform the following actions:
■
Remotely identify, inventory, and add Dell computers to the pool of managed
resources in your environment.
■
Automatically deploy the Dell OpenManage Client Instrumentation (OMCI)
agent to client computers.
■
Obtain detailed inventory client computer data, including hardware information
and BIOS settings.
■
Remotely update the BIOS on client computers to the latest version.
■
Remotely configure BIOS settings on client computers.
■
Employ hardware health monitoring that can trigger alerts on client computers.
■
Generate a wide range of reports that help you manage client computers.
■
Perform real-time, one-to-one management of the client computers.
■
Configure Dell display settings and turn off Dell displays.
Dell Client Management Suite
Dell Client Management Suite provides the following additional capabilities:
■
Ensure that all computers are compliant with published security patches.
■
Track the distribution and usage of software licenses.
■
Establish and enforce system configuration and software usage policies.
Dell® Client Manager 3.2 Release Notes
Supported systems
■
Take control of a remote computer on a WAN.
Supported systems
Supported Dell computer models
Dell Client Manager supports all Dell Precision workstations, OptiPlex desktops,
and Latitude notebooks. Dell Client Manager does not support Dell Dimension
desktops, Dell Inspiron notebooks, and Dell Vostro notebooks.
Dell computer models that support patching
For the list of the Dell computers and devices that support patching, see the PDKPC
readme at http://ftp.dell.com/cmsdk/PDKPC_Readme.doc
Supported Dell displays
Dell Client Manager can inventory and manage the following displays:
1708FP-BLK, 1908FP-BLK, E1609W, E1709W, E1909W, E2009W, E2209W, E170S
, E190S, E1910, E1910H, E2010H, E2210, E2210H, E2310H, G2210, G2410, P170S,
P2210, P190S, P2010H, P2210H, P2310H, U2410.
All newer Business Client Models of the E, P, and U series are also supported. The
consumer models (IN, ST, SX, and AW series) are not supported.
Note: Display ports are not supported for managing the displays. If you connect
displays by the Display Port, you cannot perform inventory on them; in addition,
display task cannot be executed on them.
Dell computer models that support Alert Standard Format (ASF)
Some Dell models are ASF 2.0 capable. To be ASF 2.0 capable, a computer must
have a network adapter and computer BIOS that supports ASF 2.0. Some Dell
computers have Broadcom network adapters that support ASF 2.0 while the
computer BIOS does not. You can discover ASF-capable computers using the Out
of Band Discovery policy.
For more information, see the Out of Band Management Component Implementation
Guide.
Supported ASF computers can be identified through the SupportedASF2.0capable
Dell client computers filter. Dell Client Manager may recognize other models
5
6
Dell® Client Manager 3.2 Release Notes
What's new in Dell Client Manager
that have ASF-capable network adapters but do not have ASF 2.0 support in the
computer BIOS. In these cases, these computers are listed as capable in the
ASF/DASH Capable Computers filter. They can have the Out of Band Task Agent
installed on them, along with fully supported models. ASF 2.0 functionality is not
available on these computers, and it does not cause any problems to have the
agent installed on the computers that are not fully supported.
Dell computer models that support Intel® Active Management
Technology (Intel® AMT)
Some Dell models support Intel AMT 2.0 and later. You can discover Intel
AMT-capable computers by using the Out of Band Discovery policy.
For more information, see the Out of Band Management Component Implementation
Guide.
What's new in Dell Client Manager
The following new features are introduced in the 3.2 release of Dell Client Manager:
■
Dell Client Manager installs Dell OpenManage Client Instrumentation (OMCI)
8.0 to the client Dell computers.
■
You can use reports to identify computers that need a BIOS update and create
a BIOS update job directly from the report.
■
You can use reports to identify computers whose BIOS settings are out of
compliance and create a BIOS settings job directly from the report.
General installation and upgrade information
You install this product by using the Symantec Installation Manager. You can
download the installation files directly to your server or you can create offline
installation packages.
For more information, see the IT Management Suite Implementation Guide at
http://www.symantec.com/docs/DOC3464.
System requirements
Dell Client Manager has the following system requirements:
■
Symantec Management Platform 7.0 SP5
Dell client computer has the following system requirements:
Dell® Client Manager 3.2 Release Notes
Upgrade
Table 1-1
Dell client computer requirements
Requirement
Description
Operating system
Microsoft Windows XP SP2 or later with .NET Framework 3.5 SP1
installed
Available disk space 20 MB disk space for the Symantec Management Agent, plus space
to install required software
Memory
64 MB RAM
In Dell OpenManage Client Instrumentation (OMCI) 8.0, the following change was
made to the client computer:
■
.NET Framework 3.5 SP1 or later is required with Microsoft Windows XP
operating system for OMCI to install and operate.
Upgrade
You can upgrade this product from 2.x versions if you run the Symantec
Installation Manager on a Notification Server 6.x computer. To upgrade from the
2.x version, you must first upgrade your 6.x Notification Server to Symantec
Management Platform 7.0 or later. During the Notification Server upgrade process,
you can select to upgrade to the latest version of this product.
For more information, see the Symantec Management Platform Installation Guide
(see knowledgebase article 45732).
After you upgrade the product, you must upgrade the Symantec Management
Agent and the Dell Client Manager Agent that are installed on the target Dell
computers.
Known issues
The following are known issues for this release. If additional information about
an issue is available, the issue has a corresponding Article link.
The known issues are separated into the following groups:
■
Upgrade issues
See Table 1-2 on page 8.
■
Client upgrade issues
See Table 1-3 on page 10.
■
Boot order limitation issues
7
8
Dell® Client Manager 3.2 Release Notes
Known issues
See Table 1-4 on page 10.
■
Other known issues
See Table 1-5 on page 12.
Upgrade issues
Table 1-2
Issue
Description
Collected inventory data not When you upgrade Dell Client Manager from version 2.x (Notification Server
transferred during upgrade. 6.x based) to 3.x, some hardware and BIOS inventory is not transferred to
the new database. This is because of the changes to the database structure
in this release. After you install Dell Client Manager 3.x, run the inventory
tasks and re-collect all inventory.
If you still want to see the inventory data that you collected using the
previous version of Dell Client Manager (for example, you want to see the
inventory that you collected from the computers that are not available any
more and whose inventory you cannot re-collect), you can use the Altiris
Notification Store Browser to view the Store.adb file that you exported.
Issue when upgrading to a
different location.
If you install Symantec Installation Manager 7.0 to a location, other than
where the previous version of Dell Client Manager and Notification Server
6.0 is installed, the Dell Client Manager exporters are not available in the
Migration Wizard.
To resolve this issue, do the following before clicking Next in the
Migration Wizard:
Dell Monitoring Policy is
disabled after upgrade.
1
On the Notification Server computer, open to the Notification Server
6.0 installation folder, and find the Upgrade folder.
2
Copy all of the files from this Upgrade folder into the Upgrade folder
that is located at the new Symantec Installation Manager installation
directory.
3
In the Migration Wizard, click Next, and continue with the migration.
When you upgrade Dell Client Manager from version 2.x (Notification Server
6.x based) to 3.x, the Dell Monitoring Policy becomes disabled and some
settings are not migrated. You must reconfigure the policy settings after
upgrade.
Article
link
Dell® Client Manager 3.2 Release Notes
Known issues
Table 1-2
Issue
Upgrade issues (continued)
Description
Migrated BIOS Settings
When you upgrade Dell Client Manager from version 2.x (Notification Server
packages cause errors in log. 6.x based) to 3.x, the BIOS Settings packages are migrated, but the associated
files are not. An error is displayed in the log that the files location does not
exist. The packages are read-only and cannot be deleted from the console.
You can delete the packages after you remove the read-only attribute. To
remote the read-only attribute, in the SQL Server Management Studio, open
the Item database, locate the item that you want to delete, and insert 0 in
the Attributes field. Then, in the Dell Management Console, delete the
package.
Apply Dell Client Discovery Dell Client Discovery policy should be applied to all clients before agent
policy to all clients before
upgrade. Dell Client re-discovery should be performed to update in the
agent upgrade.
database. Without that the Dell Client Software Upgrade policy will not
have the clients that require upgrade on the resource target, also some Dell
Client Manager filters will not contain Dell client resources.
Do not disable Restart the
computer after task option
in Dell Client Software
Upgrade policy.
Restart the computer after task option should not be disabled in Dell Client
Software Upgrade policy after applying the policy to the clients. Restart of
the clients is needed to make the OMCI component working properly.
Without having a restart of the inventory, BIOS Settings and Monitoring
tasks do not work on the upgraded clients.
Counters are reset on Dell
Counters on Dell Client Discovery and Installation Summary page on DCM
Client Discovery and
portal reset after the upgrade. To restore the values for these counters, you
Installation Summary after need to run Dell Client Discovery policy on the clients.
the upgrade.
BIOS Settings tasks are reset This is a common issue that is due to changes that were made in the OMCI
after the upgrade.
component in Dell Client Manager 3.2.
The target of Monitoring
policy is updated to exclude
the "not upgraded DCM
clients".
This issue is related to the problem of the previous version of Dell Client
Manager agent crashing if the new monitoring policy is applied to them.
Note: Make sure to exclude the clients with the previous Dell Client Manager
agent installed while you create custom resource target for monitoring
policies after the upgrade.
Article
link
9
10
Dell® Client Manager 3.2 Release Notes
Known issues
Table 1-3
Client upgrade issues
Issue
Description
Article
link
Upgrading the Symantec
Management Agent and the
Dell Client Manager Agent.
After you upgrade the product, you must upgrade the Symantec Management
Agent and the Dell Client Manager Agent that are installed on the target
Dell computers. To upgrade the agents, turn on the Symantec Management
Agent for Windows - Upgrade and Dell Client Software - Upgrade policies.
We recommend that you configure the upgrade policies to run on a schedule.
Upgrading the client
Upgrade from OMCI versions earlier than 7.x is not supported. You must
computer from OMCI 5.x and manually uninstall OMCI and then use the Dell Client Software - Install
6.x.
policy to install the current version.
Upgrading the client
computer from OMCI 7.x.
If you upgrade OMCI from an earlier version of 7.x, a restart might be
necessary. You can configure the upgrade task to restart the computer after
upgrade, or you can run the restart task on the Supported Dell Client
Computers Awaiting Reboot to Finish Installation filter later.
User rights and OMCI 7.1
If a computer has OMCI 7.1, and the current logged on user does not have
upgrade on client computer. administrator rights, an automatic upgrade to a newer version of OMCI will
fail. To upgrade, manually uninstall OMCI 7.1 and then use the Dell Client
Software - Install policy to reinstall OMCI. Dell Client Manager includes a
filter named Dell OMCI Previous Version installed that can help you identify
these computers.
Table 1-4
Boot order limitation issues
Issue
Description
Drive type limitations.
The current boot order functionality cannot distinguish between different
hard drive types (IDE, SATA, SCSI) and multiple hard drives of the same. If
you have multiple hard drives, you cannot configure a specific hard drive
to boot from.
RAID volumes not
recognized for boot order.
RAID volumes are not recognized for boot order configuration. RAID volumes
are also ignored if boot order configuration is imported using the Import
feature of BIOS Profile Editor.
BIOS upgrade not
automatically performed
with password-locked screen
saver.
When using the BIOS Update Job for a client computer that has a
password-locked screen saver, by default the screen saver will prevent the
computer from automatically restarting and flashing the BIOS. (If the
computer is manually rebooted, it will then flash the BIOS). In the Restart
by Power Control task, the Force applications to close without prompting
option is cleared by default. If you select this option, the computer will
restart and flash the BIOS.
Article
link
Dell® Client Manager 3.2 Release Notes
Known issues
Table 1-4
Issue
Boot order limitation issues (continued)
Description
Hyperthreading settings
Hyperthreading status on Dell OptiPlex 745 and 745C computers is displayed
management not possible on as Disabled or Enabled, but in fact, the settings are not supported by the
some models.
BIOS and cannot be changed.
On Dell Latitude D420, D520, D620, D820, Dell Precision Workstation M65,
and M90 notebooks, changing Hyperthreading settings (using the BIOS
Settings task or the Real-Time view) changes Multicore settings instead.
You must upgrade BIOS on
Dell Latitude 131L before
managing the computer.
Hardware inventory collection and monitoring policies fail to run on Dell
Latitude 131L computers with BIOS version 1.7 or earlier. To manage the
computers, manually upgrade the BIOS to version 2.1 or later by running
Dell's BIOS upgrade package on the client computer.
The BIOS upgrade package can be obtained from the Dell Web site
(http://support.dell.com/).
BIOS cannot be upgraded on You cannot upgrade the BIOS to versions 2.1 or earlier on Dell Latitude 131L
Dell Latitude 131L.
remotely, using the BIOS Update Task. You have to upgrade the BIOS
manually by running Dell's BIOS upgrade package on the client computer.
Dell is currently working on resolving the issue. Check the Dell Web site if
a newer version of BIOS is available (http://support.dell.com/).
BIOS settings cannot be
changed on Dell Latitude
131L.
BIOS settings on Dell Latitude 131L cannot be changed, either by using the
BIOS Settings Task or the Real-Time view.
BIOS cannot be upgraded on You cannot upgrade the BIOS to versions 1.0.5 or earlier on Dell OptiPlex
Dell OptiPlex 740.
740 remotely, using the BIOS Update Task. Dell is currently working on
resolving the issue. Check the Dell Web site if a newer version of BIOS is
available (http://support.dell.com/).
ASF out-of-band power
management limitation.
Dell Latitude D531, D630, D631, and D830 notebooks with ASF 2.0 capability
do not support the Reboot/Reset power action (see the Real-Time Console
Infrastructure's Power Management task) using ASF technology—only Power
On and Power Off power actions are supported.
ASF Configuration takes an ASF Configuration/Inventory tasks take a long time to complete or times
excessive amount of time to out completely.
complete or times out on
Vista x64.
Not possible to create
dynamic filters.
Currently, it is not possible to create dynamic custom filters.
Article
link
11
12
Dell® Client Manager 3.2 Release Notes
Known issues
Boot order limitation issues (continued)
Table 1-4
Issue
Description
Article
link
Power Scheme Tasks conflict When you run a power scheme task on a Dell computer with the Dell Control
with Dell Control Point
Point software installed, the power scheme settings take effect, but the
software.
values in the Power Options Properties dialog box on the Dell client computer
do not change.
Where to look for the
WSMAN event messages in the Event Console do not contain a description
WSMAN event descriptions. of the event. To understand the event, you must refer to the Standard
Message Registry. This registry is not provided in the Help documentation.
The registry is attached to article 43656.
The "Reboot after change"
option on the BIOS Settings
and Boot Order pages does
not work.
The Reboot after change option on the BIOS Settings and Boot Order pages
in the Resource Manager's Real-Time view does not work. After you click
Save changes, the changes that you made apply to the target computer, but
the computer does not restart.
Changing some BIOS settings requires the target computer to be restarted.
You can use the Real-Time Console Infrastructure's Power Management
task to reboot the computer remotely.
Other known issues
Table 1-5
Issue
Description
Do not perform the
After performing a BIOS update, the computer must be restarted rather
shutdown operation after the than shut down. If a computer is shut down, the BIOS upgrade will not take
BIOS version update.
effect and you may cause the computer to not start properly.
1
BIOS Update Task—We recommend that you do not run the BIOS
Update Task alone without a follow-up restart task. Combine the BIOS
Update Task and the Restart by Power Control task into a job, or use
the sample BIOS Update Job included with Dell Client Manager.
2
BIOS Update Job—The BIOS Update Job includes the Restart by Power
Control task. We recommend that you use the BIOS Update Job to
update a BIOS.
3
BIOS Update Stand-alone Package—When you run the BIOS Update
stand-alone package, the computer will be restarted in 2 minutes by
default.
Article
link
Dell® Client Manager 3.2 Release Notes
Known issues
Other known issues (continued)
Table 1-5
Issue
Description
BIOS password restrictions.
BIOS Passwords set in a BIOS policy have the following restrictions:
1
Only alphanumeric passwords are supported.
2
Spaces may not be used. Using spaces will result in incorrect passwords.
For example, if you specified the BIOS password as "qwe 123", the
password will be set as "qwe".
3
The maximum length is dependent on the computer model. For example,
on Dell Latitude notebooks, the maximum is eight characters. When
using the Real-Time view to provide a password with more than the
maximum characters, the password will be truncated to the first number
of characters allowed. For example, if the maximum is eight characters
and you provide a 12-character password, only the first eight characters
are used. You will need to use that truncated password to use or clear
the BIOS password.
These restrictions apply to both setting passwords and password verification.
Article
link
13
14
Dell® Client Manager 3.2 Release Notes
Known issues
Other known issues (continued)
Table 1-5
Issue
Description
BIOS password numeric
values.
When using a computer's BIOS configuration utility (after a start or restart),
a BIOS password entered from the numeric keypad on the keyboard (under
the NumLock key) does not match a similar password entered by using the
numeric keys under the F1...F10 keys. Dell Client Manager does not recognize
the format from the numeric keypad in the BIOS.
Scenario 1:
1
In the BIOS, you turned on NumLock and provided a password from
the numeric part of the keyboard (under the NumLock key).
2
Using a task, the Real-Time view, attempt to modify this password (or
apply some BIOS Settings on the computer where you need to provide
a password to change them). Your password (the same as you entered
in the BIOS) will not be accepted. It does not matter which kind of
number keys you use in Dell Client Manager; it will not match.
Scenario 2:
1
Using a Dell Client Manager policy, the Real-Time view, set the BIOS
password using numbers (either form of numbers).
2
Enter BIOS and attempt to enter the same password using numeric
keypad keys—it will not match. It will work only if you enter this from
the numeric keys (under F1...F10 keys).
Solution:
When using a computer's BIOS configuration utility (after a start or restart),
to enter the BIOS password, always use the numeric keys under the F1...F10
keys.
Extracting .hdr file from
When using DOS-based BIOS upgrade files, you must extract the .hdr file
non-packaged BIOS upgrade from the downloaded .exe file. You can do this by running filename.exe
.exe file.
–writehdrfile.
Some files may not extract correctly. This occurs because the extraction
process requires more memory than it's allocated by default. If this occurs,
right-click the .exe, click the Memory tab of the .exe file properties, and
modify memory allocation values to maximum values for all settings. Then
close the Properties dialog box and re-execute the extraction process.
Article
link
Dell® Client Manager 3.2 Release Notes
Fixed issues
Table 1-5
Issue
Other known issues (continued)
Description
Article
link
Asset tag length limitations. When setting the Asset Tag value in the BIOS Settings Task, there is a
10-character limit. If you have more than 10 characters, this will cause the
changing of an Asset Tag (of more than 10 characters) to fail.
For example, if you use a %systemname% macro as a value for the Asset
Tag, and if %systemname% is more than 10 characters, the set operation
will fail.
Asset tag macro limitations. When you use a %username% macro as a value for the Asset Tag when no
user is currently logged on the target computer, the set operation will fail.
Updating BIOS with Dell
Client Manager Patch
Management functionality
can fail.
Updating BIOS on clients with Dell Client Manager Patch Management
functionality may fail on some systems with the BIOS password set on them.
In this case, we recommend that you clear the BIOS password before applying
the BIOS update with Patch Management. For example, the BIOS Settings
task can be added manually into Patch Management's rollout job: in the
beginning, to clear the BIOS password; in the end, to set the BIOS password
back.
.NET Framework 3.5 SP1 or
later is required.
You need to have .NET Framework 3.5 SP1 or later installed on the clients
with Microsoft Windows XP for OMCI to install and to operate. Without
having installed .NET Framework 3.5 SP1 or later, the installation of OMCI
would fail.
Displayed hidden boot
devices.
Hidden boot devices are displayed in Dell Client Manager inventory in the
resource manager for some Latitude notebooks. However, on those
notebooks' BIOS, there is no information about those hidden devices on the
BIOS setting screen.
F2/F12 POST Display
instances are not available in
OMCI 8.0 on some Latitude
computers.
F2 and F12 POST Display instances are not available for some Latitude
computers. When you perform BIOS Inventory task on clients, on the
Resource Manager, go to View > Inventory > Data Classes > Dell Client
Inventory > Dell Client BIOS Settings > Post Behaviour. F2/F12 at POST
values are equal to "-1" which means unsupported. However, these instances
are available on the BIOS setting screen.
"Disk free space warning"
alert does not work.
"Disk free space warning" alert does not work.
Fixed issues
The following are the previous issues that were fixed in this release. If additional
information about an issue is available, the issue has a corresponding Article link.
15
16
Dell® Client Manager 3.2 Release Notes
Other things to know
Table 1-6
Issue
Fixed issues
Description
Article
link
Automated action defined by If you turn on the policy by right-clicking Dell Client Monitoring Policy in
Dell Client Monitoring Policy the left pane and then clicking Enable, the automated action that is defined
does not work.
in the policy (By default: Email Automated Action for Dell Client Manager
Alert) does not work.
Instead, turn on the policy using the On/Off button on the upper-right corner
of the Dell Client Monitoring Policy page, and then click Save changes.
Pre-populated Data Source
fields lost after Dell Client
Monitoring Policy automated
action performed.
When you click Edit input parameters on the Dell Client Monitoring Policy
page, the Edit Job/Task Input Parameters virtual window appears. If you
click Cancelor close this virtual window, the pre-populated Data Source
fields can be lost. Instead, click OK, even if you did not change anything in
the virtual window. If you did, click Cancel, and then navigate away from
the Dell Client Monitoring Policy page without saving anything. Then come
back to the page—the lost Data Source fields should now be restored.
Other things to know
The following are things to know about this release. If additional information
about an issue is available, the issue has a corresponding Article link.
Table 1-7
Other things to know
Issue
Description
Hierarchy is not supported.
This product does not support hierarchy and replication.
Article
link
Dell® Client Manager 3.2 Release Notes
Documentation that is installed
Table 1-7
Issue
Other things to know (continued)
Description
Article
link
Recommendations for
Dell Client Manager lets you import the Dell Client Update Packages Catalog
importing Dell Client Update from the Dell Web site or from a custom location. If you want to import from
Packages Catalog from a
the custom location, follow these recommendations:
custom location.
■ You can download the catalogPC.cab from http://ftp.dell.com/ catalog
and the appropriate InvColPC_*.exe from http://ftp.dell.com/cmsdk
■
To find out which version of the InvColPC_*.exe file to download,
extract the catalogPC.cab and examine the CatalogPC.xml file.
Place the catalogPC.cab and InvColPC_*.exe files in the same
directory. Then, on the Dell Client Update Packages Catalog Import
page, configure the custom location of the catalog.
■ If your Notification Server is on an isolated network, you may want to
create a local storage for the update files. To do this, you must set up an
intranet Web site, and then download the update files from
http://ftp.dell.com/. Maintain the same folder structure as on
http://ftp.dell.com/. Modify the baseLocation value in the
CatalogPC.xml file (skip the http:// prefix) and put the file back to
catalogPC.cab (to be able to create cab files, download the CABARC
SDK from the Microsoft Web site ).
■
Documentation that is installed
Table 1-8
Documentation that is included into the product installation
Document
Description
Location
Help
Information about how to use this
product.
The Documentation Library, which is
available in the Symantec Management
Console on the Help menu.
Help is available at the solution level and
at the suite level.
Context-sensitive help is available for
most screens in the Symantec
This information is available in HTML
Management Console.
help format.
You can open context-sensitive help in
the following ways:
■
The F1 key when the page is active.
■
The Context command, which is
available in the Symantec
Management Console on the Help
menu.
17
18
Dell® Client Manager 3.2 Release Notes
Other information
Table 1-8
Documentation that is included into the product installation
(continued)
Document
Description
Location
User Guide
Information about how to use this
product.
■
This information is available in PDF
format.
Symantec Management
Platform Help
Information about how to use the
Symantec Management Platform
The Documentation Library, which is
available in the Symantec
Management Console on the Help
menu.
The Documentation Library provides
a link to the PDF User Guide on the
Symantec support Web site.
■ Supported Products page
Same as above.
Other information
Table 1-9
Information resources that you can use to get more information
Document
Description
Location
Symantec Management
Platform User Guide
Information about using the Symantec
Management Platform.
Symantec Management Platform
Documentation page
Symantec Management
Platform Release Notes
Information about new features and
important issues in the Symantec
Management Platform.
Symantec Management Platform
Documentation page
Symantec Management
Platform Installation Guide
Information about using Symantec
Installation Manager to install the
Symantec Management Platform
products.
http://go.symantec.com/sim_doc
Knowledge base
Articles, incidents, and issues about this
product.
SymWISE support page
Symantec Connect
An online magazine that contains best
practices, tips, tricks, and articles for
users of this product.
Symantec Connect page