DS 8.5 RU4: Unable to capture Image package

book

Article ID: 197268

calendar_today

Updated On:

Products

Deployment Solution Management Platform (Formerly known as Notification Server)

Issue/Introduction

After upgrade to DS 8.5 RU4 , it seems we are not able to properly capture an image.


From Agent logs, we can see:

  • Imaging job is starting
  • Imaging tools is downloaded and Client requests to create image package:

[2020/07/29 08:33:04.51 1932:1460 <TRC>] Create Image Package: SOAP embedded request: <ImagePackage><Name>win10ent1909gold.gho</Name><Location></Location><ImageMetaData> <Description></Description> <ImageTool>1</ImageTool> <ImageType>0</ImageType> <OSType>Windows 10</OSType> <AcceleratePackageStaging>True</AcceleratePackageStaging> <CreatePackage>False</CreatePackage> <CreateExternalPackage>True</CreateExternalPackage> <ClientResourceGuid>{2FAF74C5-F65C-4839-A15A-43C2209AEE04}</ClientResourceGuid> <SystemPartionNo>1</SystemPartionNo> <ImagingDisk>1</ImagingDisk> <IsUseHttp>False</IsUseHttp> <addresses> <address ip="192.168.91.131"/> </addresses></ImageMetaData></ImagePackage>[2020/07/29 08:33:04.66 1932:1460 <TRC>] Create Image Package: Request Url: https://smp.domain.com:443/Altiris/Deployment/Agent/DeploymentWebService.asmx

  • To what we receive response from NS with Package Server name:

<?xml version="1.0" encoding="utf-8"?><soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"><soap:Body><CreateSoftwareResourceResponse xmlns="http://Altiris/Deployment/"><CreateSoftwareResourceResult><PackageReturnValues><PackageGuid>32e366ab-7d50-4d54-8940-85d8f7c1c4e7</PackageGuid><PackageServerGuid>0131b452-37b0-443d-a6e2-447f2f669836</PackageServerGuid><PackageServerName>PS01.domain.com</PackageServerName></PackageReturnValues></CreateSoftwareResourceResult></CreateSoftwareResourceResponse></soap:Body></soap:Envelope>

  • After that seems client is checking with the Package Server if the package is created and ready, but this is the point we are stuck on.
    From NS logs seem like NS is forcing the Package Server to update the package:

Accelerated package staging requested. Notifying each of 1 package servers to force them to update their client configuration. The package servers are: [1] 0131b452-37b0-443d-a6e2-447f2f669836.
-----------------------------------------------------------------------------------------------------
Date: 29-Jul-20 8:33:08 AM, Tick Count: 323687812 (3.17:54:47.8120000), Size: 513 BProcess: w3wp (12592), Thread ID: 247, Module: Altiris.NS.StandardItems.dllPriority: 4, Source: Altiris.NS.StandardItems.SoftwareDelivery.Tasks.PsPackageDeliveryAccelerator.InitiatePSPackageDeliveryTask

Assigning package delivery task to 1 package servers.
-----------------------------------------------------------------------------------------------------
Date: 29-Jul-20 8:33:08 AM, Tick Count: 323688062 (3.17:54:48.0620000), Size: 276 BProcess: w3wp (12592), Thread ID: 247, Module: w3wp.exePriority: 4, Source: PsPackageDeliveryAccelerator

 

Cause

Acceleration that is executed for PS 0131b452-37b0-443d-a6e2-447f2f669836 fails with warning:
Cannot execute task, batch 1/1, task=89dd282d-f98c-4914-b4dc-6458a74b577b, name=Package Server Package Delivery Task, agents_total=1, in_batch=1, delay=0

No computers or targets with computers were assigned.
[Altiris.TaskManagement.ClientTask.Exceptions.NoComputersAssignedToTaskException @ Altiris.NS]
at Altiris.NS.TaskManagement.TaskExecutionInstanceWrapper.ExecuteTask(Guid taskVersionGuid, String name, Dictionary`2 inputParameterValues)
at Altiris.NS.AgentManagement.Communication.Invokers.TaskActionInvoker.<ExecuteTaskInBatch>d__3.MoveNext()

There is also such verbose: Unable to retrieve item: 0131b452-37b0-443d-a6e2-447f2f669836
It looks like TS filters out PS machine that is target for task execution.

Environment

DS 8.5 RU3, RU4

Resolution

This issue has been reported to our Symantec Development team. A fix has been targeted for DS 8.6. Stored Procedure "spDeployment_GetCompDetailsFromName" was corrected to process only existing computer resources.

In the meantime, make sure that the resource Package Server GUID (we will use '0131b452-37b0-443d-a6e2-447f2f669836' as example) exists in next DB tables:

select * from Inv_Client_Task_Resources where _ResourceGuid = '0131b452-37b0-443d-a6e2-447f2f669836'
select * from TaskTargetDeviceCache where [Guid] = '0131b452-37b0-443d-a6e2-447f2f669836'


If does not exist in the last table, try execute the next procedure:

execute [dbo].[tmBuildTargetDeviceCache] null


Also, verify that there are not junk entries in "Inv_AeX_AC_Identification" table. It could be that there are orphaned entries for same PS but with another GUID. DS "sp spDeployment_GetCompDetailsFromName" just locates fist one by PS name and assumes that this is desired PS. So we get invalid PS GUID.