Altiris™ Software Management Solution 7.1 from Symantec™ Release Notes Altiris™ Software Management Solution 7.1 from Symantec™ 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 Altiris™ Software Management Solution 7.1 from Symantec™ Release Notes This document includes the following topics: ■ About Software Management Solution ■ What's new in Software Management Solution 7.1 ■ General installation and upgrade information ■ System requirements ■ Supported platforms ■ Known issues ■ Fixed issues ■ Other things to know ■ Documentation that is installed ■ Other information About Software Management Solution Altiris™ Software Management Solution from Symantec™ provides intelligent and bandwidth-sensitive distribution and management of software from a central 4 Altiris™ Software Management Solution 7.1 from Symantec™ Release Notes What's new in Software Management Solution 7.1 Web console. It significantly reduces desktop visits and lets you easily support your mobile work force. Software Management Solution also lets users directly download and install approved software, or request other software. This product is part of the following suites: ■ Altiris™ Client Management Suite from Symantec ■ Altiris™ Server Management Suite from Symantec ■ Altiris™ IT Management Suite from Symantec What's new in Software Management Solution 7.1 In the 7.1 release of Software Management Solution, the following new features are introduced: ■ The Software Management Solution Plug-in supports 64-bit client operating systems. ■ You can now perform remediation on a schedule. ■ The solution supports hierarchy editable properties. This feature lets you define which settings can be modified by the child Notification Server administrators. ■ Hierarchy reports let you view the software delivery summary and the Software Portal requests summary across the hierarchy. ■ In addition to Wake-on-LAN, you can use Intel AMT, ASF, and DASH technologies to power on computers for a Managed Delivery policy compliance check. ■ Added support of various Active Directory domain configurations for the Software Portal. The following configurations are supported: ■ ■ Domain nested groups ■ Parent-child domains relationship ■ Trusted domains from the same forests ■ Trusted domains from different forests The Symantec Workspace Virtualization agent that is included with the product installation is updated to version 6.1 SP6 MP1 HF1 (32-and 64-bit). Altiris™ Software Management Solution 7.1 from Symantec™ Release Notes General installation and upgrade information 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. For more information about migrating from 6.x and 7.0 to 7.1, see the following documentation resources: ■ IT Management Suite Migration Guide version 6.x to 7.1 at http://www.symantec.com/docs/DOC3549 ■ IT Management Suite Migration Guide version 7.0 to 7.1 at http://www.symantec.com/docs/DOC3550 System requirements Software Management Solution 7.1 requires the following software: ■ Symantec Management Platform 7.1. Supported platforms Software Management Solution can manage the following client platforms: ■ Windows XP (SP2 or later) x64/x86 ■ Windows Vista RTM and SP1 (all editions) ■ Windows 7 ■ Mac OS X 10.4.x (Universal binary), 10.5.x (Universal binary), 10.6 ■ Red Hat Enterprise Linux 4, 5, 5.1, 5.2, 5.3, 5.4 - x64/x86 ■ SUSE Linux Enterprise Desktop 10, 11 - x64/x86 Software Management Solution can manage the following server platforms: ■ Windows Server 2003 (SP1/SP2/R2) x64/x86 ■ Windows Server 2008 x64/x86 ■ Windows 2008 (R2) ■ Windows 2008 Core Edition 5 6 Altiris™ Software Management Solution 7.1 from Symantec™ Release Notes Known issues ■ Mac OS X Server 10.3.9 (PPC), 10.4.x (Universal binary), 10.5.x (Universal binary) ■ Red Hat Enterprise Linux 3, 4 - x64/x86 ■ Red Hat Enterprise Linux 5, 5.1, 5.2, 5.3 Server - x64/x86 ■ SUSE Linux Enterprise Server 10, 11 - x64/x86 ■ Solaris 9 SPARC, 10 SPARC, 10 - x64/x86 ■ Hewlett-Packard HP-UX 11.11 (11i) PA-RISC, 11.23 (11i v2) PA-RISC/IA-64, 11.23 (11i v3) PA-RISC/IA-64 ■ IBM AIX 5.2 PPC, 5.3 PPC, 6.1 PPC ■ VMware ESX Server 3.0.1, 3.0.2, 3.5 The Symantec Workspace Virtualization Agent 6.1 SP6 MP1 HF1 that is included in the product installation supports the following operating systems: ■ Microsoft Windows 7 (32-bit and 64-bit) ■ Microsoft Windows Vista SP1 or later (32-bit) ■ Microsoft Windows Vista SP2 or later (64-bit) ■ Microsoft Windows XP Professional SP2 or SP3 (32-bit) ■ Microsoft Windows Server 2008 (32-bit and 64-bit), when used as an endpoint ■ Microsoft Windows Server 2003 SP1 or later (32-bit), when used as an endpoint 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: ■ Installation and upgrade issues See Table 1-1 on page 7. ■ Known issues See Table 1-2 on page 8. ■ Replication issues See Table 1-3 on page 10. ■ Managed Software Delivery issues See Table 1-4 on page 13. ■ Software Portal issues Altiris™ Software Management Solution 7.1 from Symantec™ Release Notes Known issues See Table 1-5 on page 14. ■ Virtualization issues See Table 1-6 on page 16. ■ Non-Windows-specific issues See Table 1-7 on page 17. Table 1-1 Issue Installation and upgrade issues Description Article link Sequential software delivery Migration of sequential software delivery tasks from 6.x to 7.1 fails if TECH44430 tasks fail to migrate if Altiris the Altiris Profiler on the 6.x server is not up to date. Profiler is not up to date. On the 6.x Notification Server computer, launch the Altiris Profiler. If a dialog box appears with a request to upgrade the Altiris Profiler, click Yes. Local users in software availability settings are lost after upgrade. When you migrate to 7.1, you install the Symantec Management Platform 7.1 to a new computer. Because of this, the local users that you specified while configuring Software Resource Availability settings in software packages and managed delivery policies are no longer available after upgrade. The domain users and groups are migrated correctly. Some 6.x solution agents are After you upgrade the Altiris Agent 6.x to Symantec Management Agent not removed from the client 7.1, some of the 6.x solution agents may not be removed. For example, computer. the Software Delivery Agent for Task Server and Application Management Agent are not removed from the client and shown as installed in the Symantec Management Agent user interfaceI. Symantec recommends that you uninstall the solution agents that do not have an equivalent in 7.1 before you perform the upgrade. Error appears when you If you select a large number of software delivery packages and select assign 6.x software delivery the Action > Assign to Software Resources right-click action, an error packages to software can be displayed. resources. Workaround: select a smaller number of packages. You must upgrade the Software Portal plug-in and other client software to 7.1. After you upgrade to 7.1, you must upgrade the Symantec Management Agent and the Software Management Solution Plug-in, and turn on the Software Portal Plug-in Policy. Software Portal does not support computers with the previous versions of client management software installed. 7 8 Altiris™ Software Management Solution 7.1 from Symantec™ Release Notes Known issues Table 1-1 Issue Installation and upgrade issues (continued) Description Article link Not all of the command lines Sometimes, when you assign a 6.x software delivery package to a 7.1 are visible after software software resource, all of the command lines and associated packages delivery package conversion. may not be visible when you try to create a quick delivery task or a managed software delivery policy out of this software resource. To work around this issue do one of the following: ■ Convert the 6.x package again. ■ Restart the Notification Server computer. Legacy task's WOL feature does not work. The Wake-on-LAN task is created for the legacy software delivery policies, but it does not work. During an off-box upgrade, the Software Delivery Package File Importer in the migration wizard might fail. When you copy the software package migration data during an off-box upgrade, you must place both the PackageFiles folder and the data store (ADB) file in the same location on the 7.x Notification Server computer. Otherwise, the migration fails. When Sequential Software Delivery tasks are migrated to Managed Software Delivery policies, they do not download packages to the alternate download location. When you upgrade from Software Delivery 6.1 to Software Management Solution 7.x, you can migrate Sequential Software Delivery tasks to Managed Software Delivery policies. When you run those migrated policies, their packages are always downloaded to the default location on the client computers. If you specified an alternate download location in the download settings, it is not used. Table 1-2 Issue Known issues Description Quick delivery task timeouts A quick delivery task fails to run if it is scheduled to run immediately, if scheduled to run outside of and the schedule is outside of a maintenance window. This happens maintenance window. if a timeout period does not overlap with the maintenance window period. As a workaround, you can increase the timeout value or change the schedule. Legacy software delivery The legacy software delivery tasks always download their files to drive tasks download their files to C:, even if the Symantec Management Agent is installed on another drive C:. drive. For example, if the Agent is installed to E:/mydir/, legacy software delivery task's cache is created on C:/mydir/ instead. Article link Altiris™ Software Management Solution 7.1 from Symantec™ Release Notes Known issues Table 1-2 Issue Known issues (continued) Description Article link Compliance reports show If you reconfigure the solution through the Symantec Installation incorrect data after solution Manager, then compliance reports such as Software Compliance Status reconfiguration. may show incorrect data. Some MSI files do not install The problem can appear when you run any software delivery task or TECH122110 the software for the whole policy, because the problem is related to the nature of the MSI file. computer but only for the For more information, see knowledge base article TECH122110. user under which the installation runs. The configuration of a Quick Delivery task can cause Source Path Update tasks and Windows Installer Repair tasks to fail. When you install software with a Quick Delivery task, the MSI package TECH122112 is downloaded to and run on the client computer. In some cases, the way the Quick Delivery task is configured and installed can cause the Source Path Update task or the Windows Installer Repair task to fail. For more information, see knowledge base article TECH122112. A software delivery task or policy installs the Wise Toolkit only for the user under which the installation runs. When you create a software delivery task or policy to install Wise Toolkit and run it with the default settings (Run as option is set to Symantec Management Agent credentials), then Wise Toolkit items are not visible in the Add or Remove programs tool and in the Start menu for any user. Note that adding an option ALLUSERS=2 to the command line does not solve the problem, because the Wise Toolkit package is an EXE file and not an MSI file. Workaround: Set the Run as option of the task or policy to Currently logged-on user or set it to Specific user and specify the credentials of the user who will use the Wise Toolkit on the computer. Software that requires a restart during installation cannot be installed with Software Management Solution. You cannot use Software Management Solution to install software TECH44168 that requires a restart during installation. An example of such software is MS SQL Server 2008. Because the Software Management Solution plug-in cannot handle the restart, the installation task or policy does not complete successfully. A workaround is available. See knowledge base article TECH44168. The Software Management The Package Delivery, Quick Delivery, Source Path Update, and Solution tasks do not support Windows Installer Repair tasks do not use multicasting. Therefore, multicasting. even if the multicasting option is selected in the global Symantec Management Agent settings, and you use those settings for the task, the multicasting does not occur. 9 10 Altiris™ Software Management Solution 7.1 from Symantec™ Release Notes Known issues Known issues (continued) Table 1-2 Issue Description Article link Command lines are not available for selection in a Package Delivery task. If command lines are added to a software resource before the package is added, those command lines are not available for selection when you create a Package Delivery task for that software resource. Workaround: Use Quick Delivery to deliver such software resources. When you assign permissions for a software resource on a parent domain, you cannot search for users and groups on a child domain. When you publish a software resource to the Software Portal on a parent Notification Server computer, you cannot search for and select local users and groups of a child domain. You can assign permissions for users and groups that are visible on the parent domain only. When you create a detection rule for a migrated software resource, the default product code is invalid. By default, the software resources that you import from Software Delivery Solution 6.x do not have detection rules. When you add an MSI Product Code standard rule, an invalid MSI product code appears instead of the software package’s product code. Workaround: The software publishing in hierarchy works properly when the parent Notification Server computer and its children are in the same domain. Workaround: Use a tool like ORCA to find out the correct product code of the MSI and apply it to the detection rule manually. Hierarchy and replication issues Table 1-3 Issue Description Software Portal managed users are not replicated to child. Users that are assigned to a Software Portal manager are not replicated to the child Notification Servers. As a result, the software requests go to the Software Portal administrator instead of the manager. To work around this issue do the following: 1 Add users to the Software Portal manager's direct reports list on the child Notification Server manually. 2 Approve the Software Portal requests on the child Notification Server. 3 On the parent Notification Server, publish pre-approved software to the Software Portal. Article link Altiris™ Software Management Solution 7.1 from Symantec™ Release Notes Known issues Hierarchy and replication issues (continued) Table 1-3 Issue Description Published managed delivery The managed software delivery policies that are published to the Software policy cannot be edited and Portal and then replicated cannot be edited and executed on the child executed on child. Notification Server. This happens even if the Hierarchy Editable Properties settings allow editing. You can do one of the following to work around this issue: ■ Edit the policy on the parent Notification Server. ■ Clone the policy on the child and edit the cloned policy. Policies with Power on Managed software delivery policies that have the Power on computers if computers if necessary necessary (using Wake-on-LAN, Intel AMT, ASF or DASH) option checked option do not work correctly do not power on the computers when run from the child Notification Server. on child. Workaround: On the child Notification Server, open the replicated policy and click Save changes. This action recreates the power management task. Keep Resource target property enabled for some policies. If you want to publish a managed software delivery policy to the Software Portal on the child Notification Server, you must keep the Resource target hierarchy editable property checked, which is the default setting. The Software Delivery task or policy execution event data is not replicated up the hierarchy by default. The replication of the Software Delivery task or policy execution event data is disabled by default. As a result, the Software Management Solution reports on a parent Notification Server do not show any information from the child Notification Servers. To be able to view the reports from the child Notification Servers on the parent Notification Server, you must enable the AeX SWD Execution, AeX SWD Package, and AeX SWD Status data classes for replication. To enable the replication of the data classes: 1 In the Symantec Management Console, on the Settings menu, click Notification Server > Hierarchy. 2 In the right pane, on the Hierarchy Management page, on the Replication tab, under Events, check the Software Package and Delivery Event Replication Rule. Note: In some large environments the enablement of these data classes for replication has an impact on the performance of the parent Notification Server. It is recommended to evaluate the impact before the full-scale rollout. Article link 11 12 Altiris™ Software Management Solution 7.1 from Symantec™ Release Notes Known issues Table 1-3 Hierarchy and replication issues (continued) Issue Description Software Portal requests from a child Notification Server computer cannot be managed from the parent server. Software Portal requests from the clients of a child Notification Server are not replicated up the hierarchy. As a result, those requests cannot be processed from the parent Notification Server in a global hierarchy scenario. Workaround: Software Portal requests on a child Notification Server can be processed in either of the following ways: The administrator of the child Notification Server can process and manage the requests. ■ The administrator of the parent Notification Server can assign users or groups to the Software Portal manager role. Anyone who has the Software Portal manager role can process and manage the requests from the Software Portal Manager page on the child server. ■ It is not possible to replicate When you specify Software Portal settings on a parent Notification Server the Software Portal company and want to replicate these settings to its children, not all data is replicated logo settings. properly. The company logo is not replicated because it is a physical file that is stored on the parent Notification Server. It is not possible to replicate physical files. Workaround: You can manually replace the SymantecLogo.png image file on the child Notification Server computer, in the C:\Program files\Altiris\Software Management Solution\Software Portal\Web\Images folder. The Software Portal user rights of the local users do not replicate properly from the parent Notification Server computer to its children. The Software Portal user rights of the local users are replicated correctly from the parent server to the child servers only when a user with the same name already exists on the child Notification Server. This problem does not occur for the domain user accounts and user groups. Article link Altiris™ Software Management Solution 7.1 from Symantec™ Release Notes Known issues Managed software delivery issues Table 1-4 Issue Description Updates of dependent software are always executed under the logged in user context. When you add software A, dependent software B, and an update for software B in a managed delivery policy, the update is always executed under the logged in user context. The user interface does not provide the possibility to change the execution context for the dependent software updates. To work around this issue do one of the following: The Power on computers if necessary option is for compliance check only. ■ Ensure that the currently logged in user has rights to install software. ■ Install dependent software updates using another managed software delivery policy. The Power on computers if necessary (using Wake-on-LAN, Intel AMT, ASF or DASH) option is capable of waking up the computer for compliance check only. If the computer goes back to sleep before the remediation schedule, the remediation will not take place. The Wake-on-LAN task is not When you create a new managed delivery policy and check the Power on created when you create a computers if necessary (using Wake-on-LAN, Intel AMT, ASF or DASH) new policy. option, the Run Power On task is created under C:\Windows\Tasks, but the Run WOL Task is not. Workaround: Open the managed delivery policy and click Save changes again. This creates the Run WOL Task. In certain conditions, the managed delivery policy compliance status can be incorrect. The compliance status of a managed software delivery policy can be incorrect in the following scenario: 1 Task A is followed by software resource B. 2 The Upon failure the Managed Delivery will option for Task A is set to Continue. 3 When the managed software delivery policy runs on the client computer, task A fails, and the software resource B succeeds. The compliance status in this scenario will be Compliant, which is incorrect. Problems occur when you delete a Managed Software Delivery policy that is published in the Software Portal. When you delete a Managed Software Delivery policy that is published in the Software Portal, the following problems appear: You cannot select and delete multiple Managed Software Delivery policies at once. You must select a single Managed Software Delivery policy, delete its item references, and then delete the policy. ■ When you delete an item reference of a Managed Software Delivery policy, the Item References list is not automatically refreshed. You must refresh the Item References list manually to see which of the items have been deleted. ■ Article link 13 14 Altiris™ Software Management Solution 7.1 from Symantec™ Release Notes Known issues Managed software delivery issues (continued) Table 1-4 Issue Description Article link An imported Managed Software Delivery policy can be incorrectly marked as compliant. When you import Sequential Software Delivery tasks from 6.x to 7.x, they become Managed Delivery policies. When such a policy runs in 7.x, its status in the Symantec Management Agent is always set to Compliant, even if one or more of its sequential tasks fails. This status does not apply to an imported Managed Delivery policy, because its tasks always execute even if a preceding task fails. The Install command of a Managed Software Delivery policy for Symantec Endpoint Protection 11.0 returns false even if the installation is successful. The Symantec Endpoint Protection 11.0 installation returns 1 as a successful exit code; but in Software Management Solution, delivery tasks and policies are considered successful only when the installation is completed with exit code 0. When you install Symantec Endpoint Protection with a Managed Software Delivery policy, a successful installation is marked as a failure. Workaround: Specify 1 as a success code for the Symantec Endpoint Protection 11.0 installation command line, as follows: 1 In the Software Catalog, double-click the software resource for Symantec Endpoint Protection 11.0. 2 On the software resource page, click the Package tab. 3 On the Package tab, in the Command Lines list, select an Install command line and click Edit. 4 In the Edit Command Line dialog box, in the Success codes box, type 1, and then click OK. Table 1-5 Software Portal issues Issue Description Internet Explorer 6 is not supported. Software Portal does not work with Internet Explorer version 6. Incorrect quick delivery task An incorrect quick delivery task is created when the administrator approves created when approving the same software resource simultaneously for multiple users. multiple requests. All software delivery tasks will run on the same schedule, regardless of the settings in the individual request. Sometimes it happens that a software delivery task runs more than once. Workaround: Approve software one at a time. Article link Altiris™ Software Management Solution 7.1 from Symantec™ Release Notes Known issues Table 1-5 Issue Software Portal issues (continued) Description The Show link for Software The Show link for Software Portal in Start Menu option on the Software Portal in Start Menu option Portal Plug-in Policy page is non-functional. No link is created on the client is non-functional. computer. Workaround: Create a Symantec subfolder in the Start menu and then reapply the policy. User must refresh the desktop for the Software Portal shortcut to appear. If the Software Portal plug-in has just been installed, the desktop shortcut will appear after the desktop is refreshed. You must upgrade the Software Portal plug-in and other client software to 7.1. After you upgrade to 7.1, you must upgrade the Symantec Management Agent, the Software Management Solution Plug-in, and turn on the Software Portal Plug-in Policy. Software Portal does not support computers with the previous versions of client management software installed. Software Portal manager If a software was requested from a domain that is currently offline, the page fails to load if a domain Software Portal manager page fails to load. For example, this issue can occur is offline. if a trust relationship between two domains is removed after a software request was made. Possible workarounds: Approve the software requests from the software portal administrator's page. ■ Publish pre-approved software. ■ ■ Repair the domain connectivity issue. Software Portal fails to load If you join the Notification Server computer to a domain, the Software Portal if Notification Server is page becomes inaccessible. moved from workgroup to a Workaround: Configure the Notification Server Application Identity account domain. with the domain administrator account. Make sure this account also has access to the database. Some filters do not work as expected. The Approved Software and Approved Managed Delivery filters in the administrator's portal do not include pre-approved software that did not require an administrator's approval. Use the All Approved filter if you want to view both pre-approved software and the software requests that were approved by an administrator. Article link 15 16 Altiris™ Software Management Solution 7.1 from Symantec™ Release Notes Known issues Table 1-6 Issue Virtualization issues Description After you upgrade SVS agent, After you upgrade the SVS agent to Symantec Workspace Virtualization it is not shown as installed. agent 6.3, the latter is not shown as installed in the Symantec Management Agent user interface. To make the SWV agent data appear in the Symantec Management Agent user interface, add the following registry entry: [HKEY_LOCAL_MACHINE\SOFTWARE\Altiris\Altiris Agent\Plugin Objects\Agents\Software Virtualization Agent] "Build Number"="" "Agent Ident"="SVAgentSoln" "Product Version"="6.3.2065" "Install Path"="C:\\Program Files\\Symantec\\Workspace Virtualization\\" "Module"="" "Agent Name"="Symantec Workspace Virtualization Agent" The issue does not occur if you completely remove the previous version of the SVS agent before installing the new one. Sometimes software is installed on the hard disk instead of a virtual layer. Sometimes software can fail to install into a virtual layer with the following error: Module: smfagent.dll Source: CommandExecHook::HookExecution Description: Failed to start SVS capture for software installation. The software being installed will not be virtualized. SVS Error=1039 This issue occurs with Symantec Workspace Virtualization Agent 6.3, and is not dependent on an operating system or the software being installed. No workaround is available at this time. Sometimes Virtualized Sometimes, the Virtualized Software Resources reports can show Software Resources reports incomplete data related to operations with virtualized software, such as do not show all the data. installation to layer, layer activation, layer deactivation, and so on. Evaluation results for a managed software delivery policy that is installed into a virtual layer are also missing from the Virtualized Software Resources, Compliance, and Delivery reports. The issue can occur on Microsoft Windows Vista, 7 and 2008 operating systems. No workaround is available at this time. Article link Altiris™ Software Management Solution 7.1 from Symantec™ Release Notes Known issues Table 1-6 Virtualization issues (continued) Issue Description To successfully accomplish a Software Virtualization Command task that imports a VSA file, you must specify the same layer name that the VSA file contains. When you want to create a Software Virtualization Command task that imports a VSA file, you must specify a layer name. The problem is that the VSA file already contains a layer name; therefore, specifying it once more should not be necessary. Furthermore, when you specify a different layer name, the Software Virtualization import task fails. When you install software into a virtual software layer with a localized layer name, the localized name does not appear in the SVS Admin on the client computer. In a Managed Delivery policy, if you choose to virtualize the software during installation, you must provide a name for the virtual layer. If you enter a localized string as the layer name, the software appears in the SVS Admin with the default layer name "SWD" instead of the localized layer name that you provided. Workaround: Find out the layer name that the VSA file contains and type it in the Create new task dialog box, in the Layer name box. Table 1-7 Issue Article link Non-Windows-specific issues Description The Execution Attempts When you run a Quick Delivery task on a UNIX/Linux/Mac computer, two report shows two entries for entries appear in the Execution Attempts report. One entry has the task one task. name and the other has the name of the executed command line. Quick Delivery package download incorrectly reported as failed. When a Quick Delivery package is downloaded to the client successfully, but the task failed to run, the package download status is shown as Failed in the Download Status report. You can ignore this error. Solaris 10 zones are not supported. A Solaris 10 global zone that has non-global zones installed is not supported. However, Solaris 10 that does not contain any non-global zones is supported. Launching a GUI application via Software Delivery on a Mac computer is not recommended. To ensure the highest security, we recommend that you do not launch a GUI-based application through a Software Management or Inventory task on a Mac computer. If the computer is at the login window, you may inadvertently provide root access to the computer through the application. Article link 17 18 Altiris™ Software Management Solution 7.1 from Symantec™ Release Notes Fixed issues Table 1-7 Issue Non-Windows-specific issues (continued) Description Article link Some Managed Software Because the client-side user interface (on the Symantec Management Agent) Delivery settings do not work is not available on UNIX, Linux, or Mac computers, the following Managed for non-Windows software. Software Delivery settings do not apply to UNIX, Linux, or Mac delivery policies: Power on if necessary (using Wake-On-LAN, Intel AMT, ASF, DASH) Appears on the Managed Delivery Settings page, on the Schedule tab, under the Compliance section. ■ Only perform check if… Computer is available at the exact scheduled time Appears on the Managed Delivery Settings page, on the Schedule tab, when you click the Advanced button. ■ Upon success run Appears on the Managed Delivery Settings page, on the Run tab, under the Results-based actions section. ■ Also, you cannot specify a UNIX-style alternate location on a destination computer for software package download both for managed delivery global settings and for the particular managed software delivery policy. You cannot execute Managed Software Delivery policies from the client side on non-Windows computers. The client-side user interface (on the Symantec Management Agent) is not available on UNIX, Linux, or Mac computers. Therefore, you cannot execute Managed Software Delivery policies from those client computers. This issue occurs because those policies do not appear in the utility "aex-swdapm" on UNIX, Linux or Mac clients. 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. Table 1-8 Fixed issues Issue Description Article link Replicated Managed Software Delivery policies failed. A replicated Managed Software Delivery policy failed to execute when TECH46168 the installation file was an MSI and resource and item replication rules were used to replicate the software resource and the policy. Altiris™ Software Management Solution 7.1 from Symantec™ Release Notes Fixed issues Fixed issues (continued) Table 1-8 Issue Description Article link The Source Path Update task When you run the Source Path Update task for a software resource that does not work properly in the is replicated from a parent Notification Server computer to its child, hierarchy environment, on the task runs successfully but it does not update the source path. the child Notification Server computer. A Managed Software Delivery policy that contains an .msi software resource and that you have replicated with a "Replicate now" option fails to run on the child Notification Server computer clients. You can create a Managed Software Delivery policy, add an .msi software resource to it, and replicate this policy from a parent Notification Server computer to its children. When you run the replicated policy on the child Notification Server computer clients, the policy stops after the detection rule runs. Workaround: The problem does not occur when you run complete replication of a Managed Software Delivery policy. Legacy Software Delivery If you migrated 6.x Software Delivery tasks to 7.x policies, and those TECH44162 policies that are located in policies are organized in subfolders, they are not included in the subfolders are not replicated. replication of Software Management Solution policies. Any policies that are in the root of the Legacy Software Delivery policies folder are replicated correctly. A Managed Software Delivery policy that is created with the wizard does not install the software update. When you use the wizard to create a Managed Software Delivery policy for a software resource that contains updates and run the policy on the client computers, the software update is not installed. The problem appears only when you use the wizard to create the Managed Software Delivery policy. Workaround: After you create the Managed Software Delivery policy, open it for editing and click Save without making any changes. The Symantec Management Agent does not receive a Managed Software Delivery policy that is applied to the Active Directory user in the Default user organizational group. When you create a Managed Software Delivery policy, apply it to the default Active Directory user, then log in to a target computer with the same user credentials, and open the Symantec Management Agent, the Managed Software Delivery policy is not available. Workaround: 1 Use the Microsoft Active Directory Import task to import Active Directory users. 2 Open the Managed Software Delivery policy and set the imported Active Directory user as a target of the policy. 19 20 Altiris™ Software Management Solution 7.1 from Symantec™ Release Notes Other things to know Table 1-8 Fixed issues (continued) Issue Description When you log in to the Software Portal as a manager and want to open and edit a software request that is sent by a user that belongs to a user group, you get an unauthorized user error. When you log in to the Software Portal as a manager, you can add a group of users that report to you. After you add the user group, you can see the software requests of the users that belong to this user group. However, when you want to open and edit the software request that a user of this user group sent, you get an unauthorized user error. A Managed Software Delivery policy cannot correctly install software into a Symantec Workspace Virtualization 6.1 layer. Workspace Virtualization 6.1 is the new version of Software Virtualization Solution 2.1. Normally, a Managed Software Delivery policy can install software into a virtual layer on a client computer. However, if the client computer contains the agent for Workspace Virtualization 6.1, the software is installed and the layer is created. However, the layer does not contain any files and therefore cannot be used. This problem does not appear when you add the same user directly to the list of users that report to you. Workaround: If you plan to use Managed Software Delivery to install software into virtual layers, use the agent for Software Virtualization Solution 2.1. It is included with this version of Software Management Solution. Do not upgrade to Symantec Workspace Virtualization 6.1. Managed Software Delivery does not virtualize the software whose installation file is in EXE format. Managed Software Delivery does not virtualize an EXE package when you select the Install this policy’s software into a virtual software layer option. The software is installed normally instead of in a layer. Other things to know There are no other things to know in this release. Article link Altiris™ Software Management Solution 7.1 from Symantec™ Release Notes Documentation that is installed Documentation that is installed Table 1-9 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: 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 F1 key when the page is active. ■ The Context command, which is available in the Symantec Management Console on the Help menu. 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-10 Information resources that you can use to get more information Document Description Location ITMS 7.1 Implementation Guide Information about capacity http://www.symantec.com/docs/DOC3464 recommendations, design models, scenarios, test results, and optimization best practices to consider when planning or customizing ITMS. 21 22 Altiris™ Software Management Solution 7.1 from Symantec™ Release Notes Other information Table 1-10 Information resources that you can use to get more information (continued) 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
* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project
advertisement
© 2021