PENDING SCCCM clients not calling in after win10 in-place upgrade

[on_fifty_six]

I have been lining up windows 10 in place upgrades across the network via task sequence that one of our guys at work put together. all of them are windows 7 pro/ enterprise to windows 10. i'm finding that most of the time the upgrade is going just fine as long as the users follow the instructions which include

• leave computer at the office
• leave computer plugged into the LAN
• be disconnected from wireless
• logged out/ locked computer

unfortunately i have a 3rd party coming in late at night and reporting all of the upgrade failures. starting to notice that many of these "failures" or "in progress" are actually successes. but something is not clearing it as success. so they are creating a ticket for us and its starting to annoy me. as i start looking around it seems that all of these computers showing up stuck in "in-progress" or "unknown" status also havent checked into sccm since the upgrade. when i look at the windows build or operating system its not show win10, its showing win7 still. it's like the client is broken or its not fixing itself. but its not every client. some are just fine. but i dont know what to do.

has anyone ran into client/ heartbeat issues after windows 10 in place upgrade. or anything similar?

 

[joe_v]

Is there any reason for doing an in-place upgrade for your Windows 7 than a Format and Install. Are you Windows 7 clients 32-bit or 64-bit? Is the Windows 10 you are upgrading to, 32-bit or 64-bit?

 

[joe_v]

I am not crazy asking about the 32-bit

 

[on_fifty_six]

Sorry its all 64-bit. We are doing in-place upgrades because we cannot afford to rip and replace everything.

https://support.microsoft.com/en-us/help/4470553/configuration-manager-in-place-upgrade-task-sequence-does-not-continue

Apparently this is a thing so...i guess we are stuck with that.

 

[joe_v]

Do you have WMF 5.1? Does you $PSVersionTable.PSVersion in Powershell come up with version 5.1?

 

[on_fifty_six]