One of our customers is having an issue with ConfigMgr Current Branch 1702 where the Task Sequence engine is reporting ‘there are no task sequences available to this computer’ when using Unknown Computer Support.
According to this post on Reddit, Microsoft is aware of a known bug in 1702 where the SMSUID of the x64 Unknown Computer object is assigned to another computer object, rather than it generating a new SMSUID.
We can verify that this is the case in SQL by running the following commands
select * from UnknownSystem_DISC
We can then run the following query to locate the computer object using this SMSUID.
select * from System_DISC where SMS_Unique_Identifier0 like '32c7eedc-1497-4fe3-b3ad-6cb5b55b2bb3'
We can see that another computer object has this SMSUID!
Therefore we receive ‘there are no task sequences available to this computer’ as the Task Sequence engine processing assigned Task Sequence deployments for that machine.
The post includes a permanent fix and states that Microsoft will be releasing a hotfix for 1702 to address this issue which I recommend waiting for. For now we have a few options:
1. Pre-stage the computer object (using Import-CMComputerInformation cmdlet) so that we’re building using known objects only
2. Delete the computer object that has the same SMSUID as the x64 Unknown Computer object, delete SMSCFG.ini on the machine and restart ccmexec to generate a new SMSUID.
Microsoft have fixed this issue in an update rollup released for ConfigMgr CB 1702
We’ve had one of our customers report that this issue has resurfaced, however they’re running release 1910. So just a heads up that this issue might still appear from time to time!
Hope this helps!