Answered by:
Upgrade from Windows 7 to Windows 10 (1903) - SCCM In-Place Upgrade

Question
-
Hello everyone,
I am doing for the first time an in-place upgrade from windwos 7 to windows 10 using sccm (1902 CB version), I wish to benefit from your experiences to do things properly.
I started by doing a check of windows 10 version 1903 compatibility but most of the error codes are: 1047526904, 10737411819 and 1047526912 or the check is failed.
On 100 stations with win 7 none has remapped the code 0xC1900210 -1047526896 (no problem).
my questions are:
- should I migrate first to a lesser version of windows 10 (1607 or 1703) to minimize incompatibility problems and then move on to 1903?
- Is there any verification for the drivers? how sccm handles driver version during in-place upgrade?
- how long can the upgrade take?
- is the data protected at 100?- Can KASPERSKY block the upgrade?
- in case of network failure is the rolback automatic?
Thank you in advance for your help.
Cordially.Hadjer Yahiaoui
- Edited by Hadjer YH Wednesday, November 27, 2019 8:33 AM
Wednesday, November 27, 2019 8:21 AM
Answers
-
Hi
All these errors (1047526904, 10737411819 and 1047526912) are because of incompatible apps, you have to uninstall those application and do validate again
For driver management check this blog - https://deploymentresearch.com/improving-the-configmgr-inplace-upgrade-task-sequence/
I would recommend to disable antivirus before upgrade
Also refer the below Microsoft article for upgrade failed issues
https://docs.microsoft.com/en-us/windows/deployment/upgrade/resolve-windows-10-upgrade-errors
https://docs.microsoft.com/en-us/windows/deployment/upgrade/troubleshoot-upgrade-errors
For Rollback - https://www.recastsoftware.com/blog/windows-10-rollback-setuprollback-cmd-and-configmgr
- Proposed as answer by Kalyan Sundar Thursday, November 28, 2019 9:37 AM
- Marked as answer by Hadjer YH Sunday, December 1, 2019 8:34 AM
Wednesday, November 27, 2019 9:16 AM -
> should I migrate first to a lesser version of windows 10 (1607 or 1703) to minimize incompatibility problems and then move on to 1903?
Should you? Yes as those are Win 10 versions past their end of life. That really has nothing to with when you do them though. You should do them all. The order doesn't matter and doesn't change whether systems are compatible or not.
> Is there any verification for the drivers? how sccm handles driver version during in-place upgrade?
Yes, drivers are checked by the upgrade process. See https://www.imab.dk/windows-as-a-service-precaching-drivers-before-in-place-upgrades-with-configmgr-task-sequences/ for info on drivers during an upgrade task sequence.
> how long can the upgrade take?
That depends on many external factors like disk speed, CPU speed, RAM, network speed, what else you are doing in the task sequence, etc. It can go as quick as 45 minutes or take as long as 5-6 hours.
> is the data protected at 100?
User data and software are not touched during the upgrade. They are not protected either though, they are just in-place as is.
> Can KASPERSKY block the upgrade?
Lots of things can block the upgrade. As Kaylan noted, I strongly recommend disabling third-party AV during the upgrade process.
> in case of network failure is the rolback automatic?
No, as that won't impact the upgrade itself which is a local process and not dependent on the network.
Jason | https://home.configmgrftw.com | @jasonsandys
- Proposed as answer by Simon RenMicrosoft contingent staff Thursday, November 28, 2019 2:49 AM
- Marked as answer by Hadjer YH Sunday, December 1, 2019 8:40 AM
Wednesday, November 27, 2019 3:15 PM -
When upgrading uninstall all non-Microsoft antivirus, firewall, and drive encryption.
When uninstalling antivirus use the applicable uninstall tool.
Microsoft has a tool to troubleshoot Windows upgrade failures.
It used to have approximately 20 failures and has grown to approximately 60.
After any Windows upgrade failure run: setupdiag
https://docs.microsoft.com/en-us/windows/deployment/upgrade/setupdiag
Review the quick fixes:
https://docs.microsoft.com/en-us/windows/deployment/upgrade/quick-fixes
This is a list of the more common error codes and resolution methods:
https://docs.microsoft.com/en-us/windows/deployment/upgrade/resolution-procedures
.
.
.
.
.
Please remember to vote and to mark the replies as answers if they help.
.
.
.
.
.
- Edited by questionsformicrosoftproducts Sunday, December 1, 2019 10:21 AM
- Marked as answer by Hadjer YH Saturday, December 7, 2019 9:29 AM
Sunday, December 1, 2019 10:20 AM
All replies
-
Hi
All these errors (1047526904, 10737411819 and 1047526912) are because of incompatible apps, you have to uninstall those application and do validate again
For driver management check this blog - https://deploymentresearch.com/improving-the-configmgr-inplace-upgrade-task-sequence/
I would recommend to disable antivirus before upgrade
Also refer the below Microsoft article for upgrade failed issues
https://docs.microsoft.com/en-us/windows/deployment/upgrade/resolve-windows-10-upgrade-errors
https://docs.microsoft.com/en-us/windows/deployment/upgrade/troubleshoot-upgrade-errors
For Rollback - https://www.recastsoftware.com/blog/windows-10-rollback-setuprollback-cmd-and-configmgr
- Proposed as answer by Kalyan Sundar Thursday, November 28, 2019 9:37 AM
- Marked as answer by Hadjer YH Sunday, December 1, 2019 8:34 AM
Wednesday, November 27, 2019 9:16 AM -
> should I migrate first to a lesser version of windows 10 (1607 or 1703) to minimize incompatibility problems and then move on to 1903?
Should you? Yes as those are Win 10 versions past their end of life. That really has nothing to with when you do them though. You should do them all. The order doesn't matter and doesn't change whether systems are compatible or not.
> Is there any verification for the drivers? how sccm handles driver version during in-place upgrade?
Yes, drivers are checked by the upgrade process. See https://www.imab.dk/windows-as-a-service-precaching-drivers-before-in-place-upgrades-with-configmgr-task-sequences/ for info on drivers during an upgrade task sequence.
> how long can the upgrade take?
That depends on many external factors like disk speed, CPU speed, RAM, network speed, what else you are doing in the task sequence, etc. It can go as quick as 45 minutes or take as long as 5-6 hours.
> is the data protected at 100?
User data and software are not touched during the upgrade. They are not protected either though, they are just in-place as is.
> Can KASPERSKY block the upgrade?
Lots of things can block the upgrade. As Kaylan noted, I strongly recommend disabling third-party AV during the upgrade process.
> in case of network failure is the rolback automatic?
No, as that won't impact the upgrade itself which is a local process and not dependent on the network.
Jason | https://home.configmgrftw.com | @jasonsandys
- Proposed as answer by Simon RenMicrosoft contingent staff Thursday, November 28, 2019 2:49 AM
- Marked as answer by Hadjer YH Sunday, December 1, 2019 8:40 AM
Wednesday, November 27, 2019 3:15 PM -
Hello Kalyan and Jason,
thank you a lot for your help and your recommendations.
Cordially.
Hadjer YAHIAOUI
- Edited by Hadjer YH Sunday, December 1, 2019 8:40 AM
Sunday, December 1, 2019 8:36 AM -
When upgrading uninstall all non-Microsoft antivirus, firewall, and drive encryption.
When uninstalling antivirus use the applicable uninstall tool.
Microsoft has a tool to troubleshoot Windows upgrade failures.
It used to have approximately 20 failures and has grown to approximately 60.
After any Windows upgrade failure run: setupdiag
https://docs.microsoft.com/en-us/windows/deployment/upgrade/setupdiag
Review the quick fixes:
https://docs.microsoft.com/en-us/windows/deployment/upgrade/quick-fixes
This is a list of the more common error codes and resolution methods:
https://docs.microsoft.com/en-us/windows/deployment/upgrade/resolution-procedures
.
.
.
.
.
Please remember to vote and to mark the replies as answers if they help.
.
.
.
.
.
- Edited by questionsformicrosoftproducts Sunday, December 1, 2019 10:21 AM
- Marked as answer by Hadjer YH Saturday, December 7, 2019 9:29 AM
Sunday, December 1, 2019 10:20 AM