Awesome! Thank you both for your input. I tested another in place without SEP and it looks like Symantec is the issue.
From: [email protected] [mailto:[email protected]] On Behalf Of Jerousek, Jeff Sent: Wednesday, August 31, 2016 12:23 PM To: [email protected] Subject: RE: [External] [mssms] Windows 10 ent 1607 in-place upgrade This is why I use serviceui.exe to run the install. Using the task sequence published before 1506 was released. You can use the automated gui option and it will display any reasons for failing. Thanks, Jeff Jerousek<mailto:[email protected]> From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Bradley, Matt Sent: Wednesday, August 31, 2016 11:04 AM To: [email protected]<mailto:[email protected]> Subject: RE: [External] [mssms] Windows 10 ent 1607 in-place upgrade I'm currently working through this process myself with SCCM 1606 and Win10 1607 Enterprise. The one tip I can give you, is make sure your antivirus is compatible with the in-place upgrade. I had a test machine that was not totally current with Symantec Endpoint Protection version, and it would not work. I was getting that 80004005 error, but the logs were useless to where it was coming from. I had to upgrade the latest SEP version, and it would proceed. I was using Microsoft's Upgrade Analytics to help identify issues (recommended), and it flagged that one successfully as interfering with the in-place upgrade. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Gerding, Matt Sent: Wednesday, August 31, 2016 10:07 AM To: [email protected]<mailto:[email protected]> Subject: [External] [mssms] Windows 10 ent 1607 in-place upgrade Hello, I've recently set up a Windows 10 1607 Operating System Upgrade Package with its respective Windows 7 to Windows 10 in-place upgrade task sequence using SCCM version 1602. The Deployment is configured to be available for install to only configuration manager clients and I've left the defaults for the task sequence. When I deploy the TS to a test device collection, I am able to see the upgrade install option in the software center on the client it was deployed to. However, when I click on install, it starts the upgrade process but then fails ~ 10 minutes in. I've attempted this on two different Windows 7 Ent SP1 clients and am continuing to get the error message below. I've gone through the SMSTS log (which I have attached), to see if it failed because of an incompatibility with an application, there are a few errors in the log, but I'm not seeing anything specifically regarding application compatibility issues. Perhaps I'm missing something. Any feedback would be greatly appreciated! I originally attempted to attach the log to this email, but it was not sending to the forum, so I have a screen capture below. [cid:[email protected]] [cid:[email protected]] Matthew Gerding System Engineer Information Technology Centurion Medical Products [email protected]<mailto:[email protected]> 517-540-1618
