When you attempt to replicate tasks (Specifically Script tasks, and items or Folders under Jobs and Tasks) down a Hierarchy, they do not show up on a brand new Child Notification Server install.
The following trace level log message is seen on the Parent NS:
Priority: 8 Date: 7/8/2010 11:51:27 AM Tick Count: 177277515 Host Name: NSSERVERNAMEHERE Process: AeXSvc (9364) Thread ID: 61 Module: AeXSVC.exe Source: SourceReplicationImportExportProvider Description: The specified item does not support replication on the destination NS. The item has been excluded from the replication manifest (Item: TestScriptTask (b4a63788-9a3e-423c-b274-60a3da0ed09f)).
The Child NS does not show any log messages about the item that is being replicated.
Note: Recently after customers upgraded to SMP 7 SP5, the following NS log on the Child server showed the following:
<![CDATA[Error moving Item guid ba63e656-3303-4026-b4ba-f8a93a3e81a6 to folder guid aefb8046-63bf-4b8a-a3e2-9399df9b9892. Folder does not exist.]]></event>
In this case the Parent NS was upgraded to SP5 from SP4 and the Child server was installed to SP5 directly.
The upgrade to Task Server 7.0 SP4 introduces 2 new productGuids which takes over certain task server classGuids. As the Product & class don't match between the upgraded NS and the child Notification Servers, no tasks or folders created under Manage -> Jobs and Tasks can be replicated down the Hierarchy.
You can verify this by:
1) Loading this web page from the Parent NS (you must be logged on locally for this to work):
2) Clicking on GetInstalledProducts 3) Click on the "Invoke" button 4) Search for Altiris Task Management 7.0 SP4 Upgrade -If there are GUIDS listed under "Replicable Classes", your NS is affected
On SP5, this task will be named "Altiris Task Management 7.1 Upgrade"
5) Search for Task Server Core Tasks 7.0 SP4 Upgrade Installation -If there are GUIDS listed under "Replicable Classes", your NS is affected
On SP5 this task will be named "Task Server Core Tasks 7.1 Upgrade"
This issue has been fixed in ITMS 7.1 SP1 release.
To work around this issue prior to 7.1 SP1:
1) Backup the Symantec_DB on the Upgraded (parent) NS 2) Run these SQL Queries:
update classproductreplication set productguid = '9f9a80fc-2d71-4b08-a1ad-fb146b4af2c6' --Altiris Task Management where productguid = 'fa1f619b-5f4c-4406-acae-d7d62576dda4' --Altiris Task Management 7.0 SP4 Upgrade
update classproductreplication set productguid = 'D1341AA4-95D3-4335-AD2F-A7F3389783B6' --Task Server Tasks where productguid = '1D886777-EF3D-4EEC-AD9B-7333BCA7AB47' --Task Server Core Tasks 7.0 SP4 Upgrade Installation
update classproductreplication set productguid = '9f9a80fc-2d71-4b08-a1ad-fb146b4af2c6' --Altiris Task Management where productguid = '5526fb8d-f9a3-494a-bd7d-51777748fecc' --Altiris Task Management 7.0 SP5 Upgrade
update classproductreplication set productguid = 'D1341AA4-95D3-4335-AD2F-A7F3389783B6' --Task Server Tasks where productguid = '543ac081-8ecc-475b-994b-0acac0d00797' --Task Server Core Tasks 7.0 SP5 Upgrade Installation
3) Restart the Altiris Service 4) Run an IISReset
At this point you should be able to replicate tasks successfully down the Hierarchy
Note: This only applies to the upgrade to SP4, or SP5, respectively. If you are experiencing this issue after upgrading to a Different version, DO NOT run the SQL Queries listed above as you may experience undesired effects.
Parent NS upgraded to SP4 (or from SP4 to SP5)
Child NS Clean installed to SP4 (or directly to SP5)
ID: ETK 2087826
Logged in Etrack (Symantec) database
Imported Document ID: TECH133430
Subscribing will provide email updates when this Article is updated. Login is required.