yeah we saw a lot of failures at first but got around most of them by using logic to detect for those things causing failures in no specific order
bit9 sep on a vpn not meeting requirements lack of disc space etc.. we are using a customized version of this https://www.windows-noob.com/forums/topic/14118-a-deeper-look-at-the-upgrade-task-sequence-in-system-center-configuration-manager-current-branch/ On Thu, Jan 19, 2017 at 6:03 PM, Adam Juelich <[email protected]> wrote: > Any third-party VPNs? Those and Anti-Virus were responsible for the > biggest roadblocks.... > > > On Thu, Jan 19, 2017 at 10:39 AM, Matt Gerding <[email protected]> > wrote: > >> They are all Win7 SP1 enterprise x64 to Win10 1607 Enterprise x64. I >> don’t think we have applied the KB2952664. When they fail, smsts log >> always gives me an error code that relates to generic application >> incompatibility, but again, I’ve taken the computers that the in-place will >> fail on, rerun the TS and it will sometimes work, without making any >> changes. All test scenarios I’ve run have not helped me narrow down the >> issue. Seems to be no consistency. >> >> >> >> *From:* [email protected] [mailto:[email protected] >> orum.com] *On Behalf Of *John Aubrey >> *Sent:* Thursday, January 19, 2017 10:41 AM >> *To:* [email protected] >> *Subject:* [mssms] RE: Windows 10 In-Place Upgrade Failures >> >> >> >> Are you going win10 to win10 or win7 to win10? Have you applied >> KB2952664 if they are Windows 7. I have had a lot of flakiness with win7 >> to win10 upgrades recently. Clean VM’s built a few would work, more than a >> few would fail. Task sequence wouldn’t fail, it would just get stuck. >> Could be related to moving from 1511 to 1607 for us. Anything in your >> smsts log? What about the Windows setup log? >> >> >> >> *From:* [email protected] [mailto:[email protected] >> orum.com <[email protected]>] *On Behalf Of *Matt Gerding >> *Sent:* Thursday, January 19, 2017 10:19 AM >> *To:* [email protected] >> *Subject:* [mssms] Windows 10 In-Place Upgrade Failures >> >> >> >> Has anyone experienced high failure rates with Windows 10 in-place >> upgrade Task Sequence deployments? >> >> >> >> I’ve been rolling Windows 10 out to our organization and am trying to >> leverage the in-place upgrade TS to save money and time. I’ve had the >> in-place configured and working for a couple of months and have thoroughly >> tested it on ~15 machines with no problems. During testing, the in-place >> was successfully applied on new imaged equipment, old equipment, laptops, >> desktops, power users, equipment on separate VLANS, equipment in different >> remote geographical locations, equipment with 3rd party applications >> installed on them, logged in as local admin, logged in as a generic domain >> account..etc. >> >> >> >> Now that we are starting to move forward with our rollout, I’m noticing >> some inconsistent issues. About 75% of our in-place upgrades have been >> failing and the logs almost always point to a generic application >> incompatibility error. Since the failures, I’ve started testing the >> following scenarios to attempt to narrow down the issue. >> >> >> >> *Test Scenarios:* >> >> >> >> - Took a failed in-place upgrade from our accounting department >> (different VLAN than IT), plugged it in to our IT lab VLAN, made no other >> changes, reran the in-place, and it worked fine. Then took a newly imaged >> laptop back to the accounting department, plugged into an Ethernet port on >> their VLAN, ran the in-place and when I expected it to fail, it worked and >> completed successfully. >> >> - Verified potential application incompatibilities, removed the >> software and 3rd party applications that are potentially not supported >> and then re-run and the in-place works. However, Will take another device, >> install all of the conflicting applications, run an in-place and it works >> fine when I would assume it should fail. >> >> - Symantec Endpoint Protection was an issue when I first >> started testing. I have our version of SEP on the supported version, so >> that’s no longer an issue. Regardless, we have taken safety precautions and >> removed SEP all together prior to performing in-place upgrades and have >> still seen failures. >> >> >> >> I know there are countless things that could be causing this and every >> environment differs. Just looking for any insight. Thoughts? >> >> >> >> >> >> Regards >> >> >> >> *Matthew R. Gerding* >> >> System Engineer >> >> Information Technology >> >> Centurion Medical Products >> >> 517.540.1618 <(517)%20540-1618> >> >> www.centurionmp.com >> >> ••••••••••••••••••••••••• >> >> *PATIENT CARE WITHOUT COMPROMISE™* >> >> >> >> >> >> >> >> > >
