Imaging Jobs are failing on some machines with "Replicated" status
search cancel

Imaging Jobs are failing on some machines with "Replicated" status


Article ID: 224713


Updated On:


Deployment Solution


The customer is trying to re-image some machines so new users can use them. These are pre-existing computers.

Some of those machines will fail when the image job runs on them. When those jobs fail, the only status that they get is "Replicated".

They never had a hierarchy setup so the "Replicated" status doesn't make sense. Also, they are not using a "standalone replication" rule to send these computers information between 2 SMP servers.

If they delete these computers from the SMP Console, then the image job works or if it fails, at least they see "Failed" status rather than "Replicated".                                        


ITMS 8.5 RU4, 8.6, 8.6 RU1


The problem is related to resources that are selected as targets for deployment. The specified computer is detected as "unknown" resource by the Task Server and since task itself is replicable - it gets "replicated" status. 

Two possible scenarios:

1. Somehow the Task Server failed to recognize them and assumes that they are managed by some other SMP Server.

2. The affected resources may have an asset status other than "Active"


Make sure these pre-existing machines are no set to an Asset status other than "Active"


In this particular scenario, this is what we were able to discover.
According to the customer's process, when they get the client machine from an User, they change the asset status from "Active" to "In Stock". Then, when it is time to return the machine and done with imaging, then they change it back to "Active".

Our code suppose to be looking for machines with active status.

So we ran the following query to find machines with asset status other than "active".

FROM     dbo.vRM_Computer AS rmc LEFT OUTER JOIN
                  dbo.ResourceAssociation AS resAssoc ON rmc.Guid = resAssoc.ParentResourceGuid AND resAssoc.ResourceAssociationTypeGuid = '3028166F-C0D6-41D8-9CB7-F64852E0FD01'
WHERE  (rmc.Deleted = 0) AND (resAssoc.ChildResourceGuid <> '0A0203A5-D2B6-49f1-A53B-5EC31A89437C')

The machine that we were testing with was in the results. We also ran this other query:

select * from vComputerResource where Guid = 'GUIDgoesHere'

and the test machine was not there. Which tells us that the Task Server can't see it as an active machine that can assign the image task to run.