SMP 7.1 SP2 Point Fixes Rollup Version 4 Information Notes
| Article:HOWTO64413 | | | Created: 2012-01-03 | | | Updated: 2013-04-11 | | | Article URL http://www.symantec.com/docs/HOWTO64413 |
SMP 7.1 SP2 Point Fixes Rollup Version 4 Information Notes
- Introduction
- Installation
- Fixed Issues in This Release
- Known Issues in This Release
Introduction
The current version for this Rollup that can be provided to customers is 7.1 SP2 Point Fixes Rollup version 4, which contains Server and Client side fixes.
This rollup introduces new fixes that target customer reported defect from resource merge, NS security and replication areas. Also Rollup v4 fixed few inconsistencies in Task Server and SMF code introduced by previous rollup versions.
Rollup v4 can be installed either on clean ITMS 7.1 SP2 or atop of rollup v2 or v3. All corresponding files will be replaced with newer ones.
Note: Server side components are a blind revision of the 7.1 SP2 code and should have a version of 7.1.8280
Installation
Server: SMP 7.1 SP2 (7.1.8280)
Agent: 7.1.8280
Solutions: ITMS 7.1 SP2
If you have not upgraded to SMP 7.1 SP2 yet, please review the information contained in TECH177513”Upgrading to ITMS 7.1 SP2 - Best Practices”.
It is highly recommended to temporarily uninstall Inventory solution plug-in on NS before SMA upgrade after rollup v4 was applied.
Note 2:
The 7.1 SP2 Point Fixes Rollup needs to be applied in each SMP Server in a Hierarchy. It is recommended upgrading child servers first and then parent NS in the Hierarchy. Please refer to HOWTO21657.
Installation Steps
- Extract the files contained on this ‘SMP7_1_SP2_Rollup_v4_May02_2012.zip’ into your SMP Server hard drive. The file is attached to this article.
Note: Please ensure that rollup binaries WILL NOT BE KEPT within Altiris folder’s tree. - After the files are extracted, you will notice 3 subfolders: “UpgradeFromSP2”, “UpgradeFromSP2v2” and “UpgradeFromSP2v3”.
Rollup v4 can be installed either on clean ITMS 7.1 SP2 or atop of Rollup v2. All corresponding files will be replaced with newer ones. Depending on what is your current status, select the proper folder that applies to your case: If not previous Rollups were applied on your SMP 7.1 SP2, follow the instructions below using the files on “UpgradeFromSP2” folder. If you have SMP 7.1 SP2 Rollup v2, then use the files on “UpgradeFromSP2v2” folder. The same will apply for SMP 7.1 SP2 Rollup v3. - Open CMD shell as Administrator and run ‘Install.cmd’ to install the assemblies required for this Rollup.
- The original assemblies will be backed up in the same folder where the 'Install.cmd' is located.
Note: This installation RESTARTS Altiris Services and Web Services.
- Data about rollup version will be placed into the registry (under HKLM>SOFTWARE>ALTIRIS>POINTFIXES).
6. In order to install the Symantec Management Agent provided in this Rollup, go to Settings->Agent Plug-ins->All Agents Plug-ins->Symantec Management Agent->Windows-> Non Site Servers ->Symantec Management Agent for Windows x64 (or x86) (Non-Site Servers) –Upgrade to 64-bit (or 32-bit) Symantec Management Agent 7.1 and roll out the policy to Windows based clients. Symantec Management Agent will be upgraded upon policy receipt.
Note: SMA version for rollup v4 is 7.1.15350.8350.
Note: In case that you have your Upgrade policies set to “Run Once ASAP”, the upgrade policy will not run again on your client machines since it has run once already.
You may want to clone your Upgrade policies or create new ones and use the desired filter/target.
- Regarding the fix for eTrack 2627692 “Scheduling options for roles and accounts, allowing to scope subset to be replicated by specific rule”, for how to create new rule see ReadMe.txt under the CreateRule folder.
- For Site Servers (Remote Task Servers) you need to execute PFInstaller.exe on Remote Task server from folder RemoteTS. .
Note: This is only necessary for Task Servers that were installed using an SP2 GA package or SP2 Rollup v2 package. There were 2 issues fixed in Remote TS and NS:
1. Etrack 2575047 “Deployment jobs randomly stop when agent components upgrade during a task”
2. Etrack 2661494 “point-fix does not work for client job which contains tasks and another client job within”
Remote TS will still work fine without upgrade Remote TS. These 2 fixes were made for particular customer only, so customers do not need to install them unless they have such problem.
a. Copy folder RemoteTS to your Remote Task Server
b. Run PFInstaller.exe as Administrator. PFInstaller.exe requires .NET Framework 3.5 installed on PC and Notification Server or Site Server.
c. Select checkbox “Remote Site Servet(Not NS)”
d. Click Install Files button.
- In previous versions of the Rollups, all database cleanup scripts were executed automatically. Because certain scripts can take an extended period of time, it was decided to not run them automatically. We suggest pausing NS Processing (SMP Console>Settings>All Settings>Notification Server>Notification Server Settings and turn Off ‘Server Processing’) before running these scripts. The scripts that need to be manually executed on your SMP server are:
a. Cleanup Orphan Tasks. Execute “OrphanTasks.bat” from CleanupOrphanTasks folder.
b. Clear old Filters For Script Tasks. “Execute Filters.bat” from ClearFiltersForScriptTasks folder.
c. ReSave SWD Policy. Execute “LegacySWDPolicies.bat” from ReSaveSWDPolicy folder.
After these scripts complete, don’t forget to restart NS Activities.
Note: Run these scripts as Administrator. Running these scripts can take some time to finish, so plan accordingly. In most cases it should take few minutes.
Rollback Steps
1. Make sure that Backup folder exist in the same location as uninstall.cmd.
- Run ‘Restore.cmd’. Make sure that you run the uninstall script from Administrator elevated cmd.exe.
Assemblies will be restored from the 'Backup' folder.
Note: This installation RESTARTS Altiris Services and Web Services.
3. To uninstall the updated Symantec Management Agent provided with this Rollup, go to Settings->Agent Plug-ins->All Agents Plug-ins->Symantec Management Agent->Windows-> and enable the Symantec Management Agent for Windows- Uninstall policy. Schedule policy to install SMA on clients. The original version of SMA will be installed.
Fixed Issues in This Rollup
The following are the currently reported fixes included on this SMP 7.1 SP2 Point Fixes Rollup v1. If additional information about an issue is available, it is possible to access this by clicking the Article ID link. (Note: N/A = Not Available)
|
Internal ID |
Issue Abstract |
Article ID |
|
Notification Server Core |
||
|
2620808 |
We need to evaluate the time that takes to load the Right-Click menu for Computers resources |
N/A |
|
2634514 |
Slow performance when clicking update membership with a large membership - spGetComputerResources |
N/A |
|
2627875 |
Getting deadlocks in sp_Inv_AeX_SWD_Status_Summary_clean |
N/A |
|
2627692 |
Scheduling options for roles and accounts, allowing to scope subset to be replicated by specific rule |
N/A |
|
2627677 |
Performance optimizations on replication of roles and accounts required |
N/A |
|
2627388 |
Replication in hierarchy doesn't propagate resource deletion from parent to child |
N/A |
|
2627390 |
'Role' resources are constantly replicated during differential replication |
N/A |
|
2611595 |
Slow performance when updating policy with a large target |
N/A |
The following are the currently reported fixes included on this SMP 7.1 SP2 Point Fixes Rollup v2. If additional information about an issue is available, it can be accessed by clicking the Article ID link. (Note: N/A = Not Available)
|
Internal ID |
Issue Abstract |
Article ID |
|
|
Notification Server Core |
|
|
2636958 |
Image creation failed if teaming is created using two physical NIC |
N/A |
|
2643544 |
Unable to import computers from all security groups in Active Directory or from within a specific organizational unit |
TECH183474 |
|
2653019 |
Condition cannot be added in Normal mode under Filter expressions in Query builder |
TECH179348 |
|
2652467 |
Unable to delete Computer resource. Error: Violation of PRIMARY KEY constraint 'PK_ResourceTargetContainerChanges'. Defect in trigger trgScopeUpdateTargetInvalidate |
N/A |
|
2658306 |
Resource updates are taking large amount of time and memory resources due to multiple MonitorChangesAsync threads when there should only be one |
N/A |
|
2655827 |
Importing security groups from AD does not contain all the members. |
TECH178787 |
|
|
Task Server |
|
|
2637403 |
Task run instances scheduled at the parent cannot be "stopped". The message indicates it will, but it does not. |
N/A |
|
2629544 |
Client task agent started running old tasks multiple times daily. Tasks had been configured to run just once and had already ran previously weeks before. |
N/A |
|
2625970 |
RCa - Hierarchy - Client Task will be replicated each differential replication even if it wasn't changed in case it was executed on child's computers |
N/A |
|
2575924 |
Task run-instances are replicated erroneously to all child nodes in a hierarchy instead of only the one(s) to which it belongs. |
N/A |
|
2124511 |
Schedules added to client tasks after first replication are not replicated unless the client task itself changes |
N/A |
|
1647634 |
TS 7.0 Replicating a scheduled task using a Target causes blank computers to appear in list |
N/A |
|
2143240 |
Task Server: Tasks set to run to a schedule and assigned to agents at both levels of a hierarchy will eventually be marked as ‘Failed’ on the Parent NS. |
N/A |
|
|
Symantec Management Framework |
|
|
2620222 |
SoftwareCache.xml is overwritten during execution of dozen detection checks from MD policies which are scheduled in one time |
N/A |
|
2636128 |
Task within a MSD set to run only at maintenance window, executes immediately if override is set and if the Task is first in the list |
N/A |
The following are the currently reported fixes included on this SMP 7.1 SP2 Point Fixes Rollup v3. If additional information about an issue is available, it can be accessed by clicking the Article ID link. (Note: N/A = Not Available)
|
Internal ID |
Issue Abstract |
Article ID |
|
|
Notification Server Core |
|
|
2642971 |
Non-Symantec Administrators with rights to create targets are unable to view and update membership of custom targets created by other users. |
N/A |
|
2663091 |
Filters created by AD Site import are getting deleted and then get recreated on the next import, but with a different GUID |
N/A |
|
2667544 |
Filters with a large number (2000 or more) of statically assigned computers, takes a long time to Open, hit Edit, and also Save |
N/A |
|
2669872 |
Settings for "Use multiple schedules" in Shared Schedules GUI are not respected. |
TECH183457 |
|
2681855 |
The "Users" report located at \Reports\Notification Server Management\Server\Resource has poor scoping performance. |
N/A |
|
2698825 |
AD Account and Role Import no longer traverses groups inside the imported group. Groups within the membership of a group are not processed or associated to the parent group |
TECH183463 |
|
2705767 |
AD Import only imports the users of the first group, and not that nested group. |
TECH183464 |
|
|
Task Server |
|
|
2575047 |
Deployment jobs randomly stop when agent components upgrade during a task. |
N/A |
|
2659363 |
Client Task Agent shows multiple running tasks. No new tasks accepted. |
N/A |
|
2661494 |
point-fix does not work for client job which contains tasks and another client job within |
N/A |
|
2679526 |
Client Task Agent may enter the loop while failing to post task status to TS Server. |
N/A |
|
|
Symantec Management Framework |
|
|
2643799 |
The notice that a Managed Delivery Policy is available does not work, the pop-up does not appear |
TECH177164 |
|
2682976 |
SoftwareReleaseResource item is replicated on each differential replication. |
TECH183470 |
|
|
MP_UI |
|
|
2641092 |
In a large DB the process of building a target takes several minutes each attempt often failing the first few times due to a "The Data Cannot be Loaded" error. In all building a single target can take up to an hour. |
N/A |
|
2650998 |
Report columns don't resize properly to show all data |
N/A |
The following are the currently reported fixes included on this SMP 7.1 SP2 Point Fixes Rollup v4 (the ones mentioned above are also included). If additional information about an issue is available, it can be accessed by clicking the Article ID link. (Note: N/A = Not Available)
|
Internal ID |
Issue Abstract |
Article ID |
|
|
Notification Server Core |
|
|
2220166 |
spResourceMerge is killing performance in large replication environment |
N/A |
|
2657265 |
Resource Merge is not keeping both ResourceKey values for the following resources (Company, Product, Software Release). |
N/A |
|
2722216 |
Replication is overwriting security role permissions on child NS that don't exist on the parent |
N/A |
|
2654047 |
Resource Merge is allowing Resources with the No Delete attribute to be merged into other resources. |
N/A |
|
2678785 |
Package Server on Win Server 2003 will not download package files over 4 GB when UNC is disabled. |
N/A |
|
2686685 |
ITMS7.1SP2 with Rollup v2 - Condition cannot be added in Advanced mode under Filter expressions in Query builder. |
N/A |
|
2687977 |
AD Import no longer imports users into roles when OU contains '/' character. |
TECH180929 |
|
2702824 |
vproduct seems to be causing blocking on the database. |
N/A |
|
2732748 |
CollectionMembershipChanges table is no longer purged after installing Altiris.NS.dll from SMP 7.1 SP2 v2 rollup |
TECH185400 |
|
|
Task Server |
|
|
2671707 |
Client task schedule is missing from console on 7.1 sp2 upgrade. |
N/A |
|
2681908 |
Restricted users are unable to see task instance details. |
TECH184912 |
|
2695630 |
Unable to Import task if RunAs Specified user is selected |
TECH181758 |
|
2729130 |
Binary incompatibility broken in 7.1SP2 ClientTaskInstanceReplicationDataCollection class derived from other class , than was. |
TECH185077 |
|
2729129 |
Binary incompatibility broken in 7.1SP2 all Task Management VersionItems are Items. |
TECH185077 |
|
2762563 |
Binary incompatibility. Missing public method DeleteHierarchyreplicatedInstances() |
TECH185077 |
|
|
Symantec Management Framework |
|
|
2676645 |
Create cleanup script to remove orphan SWM tasks. |
N/A |
|
2692043 |
ITMS7.1SP2 - Upgraded from 7.x - SMA receives new client policy every time it requests update. |
N/A |
|
2701339 |
Software Package Resources replicate "Command Line Requires Package" parent association type in "Add" mode, rather than "Replace". |
N/A |
|
2744175 |
"Updates" association is not deleted from child NS side if it was removed on parent NS side for Software Resource. |
N/A |
Known Issues in This Release
The following are known issues for this Rollup. If additional information about an issue is available, you can read it by clicking the Article ID link.
|
Issue |
Article ID |
Internal ID |
|
Remote task server should be upgraded from 7.1 SP2 GA and 7.1 SP2 rollup v2 only. Upgrade of Remote Task Server from rollup v3 version is not necessary. |
N/A |
N/A |
|
Once the snapshot file is deleted for a package, it is not getting recreated though the package is re-downloaded |
N/A |
2763722 |
|
Entry for Resource target is not getting added in ResourceTargetContainerChanges’ table |
N/A |
2763740 |
|
Replication hung sending data up after applying SMP 7.1 SP2 Rollup v4 |
TECH189467 |
2791898 |
Attachments
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Article URL http://www.symantec.com/docs/HOWTO64413
Terms of use for this information are found in Legal Notices









Thank you.