SOLVED Issue with Upgrade Task Sequence Reporting

[Nav4339]

I have a strange problem with reporting. I have created my upgrade TS to upgrade to from Windows 7 to Windows 10. The TS runs successfully and the machine does upgrade with no issues. My problem is that SCCM is stills reporting that the machines are still on Windows 7. Any suggestions on how to resolve this issue. I have even tried to create a new TS, but that made no difference.

 

[Garth]

Have you force a Heartbeat discovery and Hardware inventory to happen?

 

[Nav4339]

Hi Garth, yes I have. One my other deployment which was more that 7 days ago, it also reporting the same as well

 

[Garth]

So to be 100% clear you have FORCED both HW inventory and heartbeat discovery on that computer? I'm double checking it is those two items which update the OS details for a computer. https://www.enhansoft.com/?s=force+hardware+inventory

 

[Nav4339]

Hi there - I ran it form the Control Panel on the client - Hardware Inventory Cycle. Let me try your suggestions though

 

[Garth]

What about Heartbeat discovery (Discovery data collection cycle)?

 

[Nav4339]

I have tried all the options from the action center.

I have also tested the Right Click Tools now and there is no update. The machine still displays as Windows 7 OS

 

[Garth]

Check your site health for duplicate computers, to make sure inventory is getting processed, etc.

 

[Prajwal Desai]

Ensure the inventory details are sent to SCCM server.

 

[Nav4339]

Check your site health for duplicate computers, to make sure inventory is getting processed, etc.

I have a collection the scans for duplicate computers every hour and I manually delete objects from there. There has not been any duplicates for the past few days

 

[Nav4339]

Okay so I forced the Discovery Data Collection Cycle on 3 clients now and the OS has updated almost immediately on the Console. For some reason the other times it did not work. How can I do this for all machines to scan on a schedule?

 

[Garth]

You can do this or turn this into a batch file/script.

How to Avoid Receiving Inventory Re-Sync Requests for Snapshot VMs

This blog post show you how to avoid receiving inventory re-sync requests for snapshot virtual machines (VMs). Check it out!

www.enhansoft.com

 

[Nav4339]

That is from the client though as this means this needs to be setup on each client? Is it possible to do this from CM itself?

 

[Garth]

You can convert the script to a Batch file and deploy it via CM. OR you can convert it to a script and use the script feature within CM. But these commands must be run on the client.

 

[Nav4339]

Thank you - is there no other way to do this from the CM console or sever though? To do this on even 50 machines is a problem. And worse is that some users dont restart or shut down their devices.

 

[Garth]

Sure you can do it via the console. You need to create a package or covert the batch file to a script and use the CM script feature.

 

[Nav4339]

So basically if I do that, the Data Discovery runs, and the update happens without the need for the client to be restarted?

 

[Garth]

Correct.

 

[Nav4339]

thank you Garth for your assistance with this issue - devices are updating now