Ok my rebuilt upgrade is working fine. This is without the patch switch being used in the original TS.
Are the original install parameters stored in the registry or a file in the ccmsetup folder? The reinstall must be calling these up. I'll take a look later. On Fri, Nov 14, 2014 at 2:32 PM, Paul Winstanley <[email protected]> wrote: > That's cool Mike. I'm just throwing it out there to see if any one > experiencing the same thing. I could opt out and point my patch switch to a > share but I know that's pretty lame and most of us push this down to the TS. > > I'm currently running a build without the patch switch included. I'm sure > this will be fine...not a fix though. > > On Fri, Nov 14, 2014 at 2:21 PM, Marable, Mike <[email protected]> > wrote: > >> Duh! >> >> >> >> Sorry, I have just been so out of it. >> >> >> >> My original TS to build the Win7 does not have any patches. I’m hoping >> to get some free time either this evening or over the weekend to try the >> in-place upgrade using the new build. I’ll had the same hotfix to my Win7 >> sequence and see what I get. >> >> >> >> Sorry about that. >> >> >> >> >> >> *From:* [email protected] [mailto: >> [email protected]] *On Behalf Of *Paul Winstanley >> *Sent:* Friday, November 14, 2014 9:09 AM >> *To:* [email protected] >> *Subject:* Re: [mssms] Windows 10 In-Place upgrade. ConfigMgr client >> fails to install >> >> >> >> Yes Mike this is the process I am undertaking. >> >> >> >> Post O/S upgrade setupcomplete.cmd is run and the following command is >> executed to remediate the client. >> >> >> >> 'Create-LogEntry "CCMREPAIR..." >> >> >> >> $process = Start-Process $env:WinDir\ccmsetup\ccmsetup.exe >> -ArgumentList "/remediate:client" -Wait -NoNewWindow -PassThru >> >> >> >> Create-LogEntry "Return code: $($process.ExitCode)"' >> >> >> >> I'm not sure where it's grabbing the -arguementlist "/remediate:client" >> details from but it seems to be including details from the original >> install, which includes the patch. >> >> >> >> >> >> >> >> On Fri, Nov 14, 2014 at 1:53 PM, Marable, Mike <[email protected]> >> wrote: >> >> I knew I should have taken today off to work on the new build! >> >> >> >> Are you doing this “in-place” upgrade: >> >> >> http://blogs.technet.com/b/configmgrteam/archive/2014/10/29/how-to-upgrade-to-win-10-using-the-task-sequence-in-sc-2012-r2-configmgr.aspx >> >> >> >> I used the sequence from that posting a while back and didn’t have to >> re-install or repair the client. >> >> >> >> *Mike Marable* >> >> Application Programmer/Analyst Lead >> >> Enterprise Device Engineering and Management >> >> MCTS, MCITP, MCSA, MS [Profile >> <https://www.mcpvirtualbusinesscard.com/VBCServer/MikeMarable/profile>] [ >> Blog <http://thesystemsmonkey.wordpress.com/>] >> >> -------------------------------------------- >> >> *"The difficult we do at once. The impossible takes a little longer."* >> >> -US Army Corps of Engineers >> >> >> >> *"It is better to have less thunder in the mouth and more lightning in >> the hand."* >> >> -Apache Proverb >> >> >> >> I will rise when I have fallen. >> >> >> >> *"Unless you try to do something beyond what you have already mastered, >> you will never grow."* >> >> -Ralph Waldo Emerson >> >> >> >> >> >> >> >> *From:* [email protected] [mailto: >> [email protected]] *On Behalf Of *Paul Winstanley >> *Sent:* Friday, November 14, 2014 8:23 AM >> *To:* [email protected] >> *Subject:* [mssms] Windows 10 In-Place upgrade. ConfigMgr client fails >> to install >> >> >> >> I'm currently seeing the following behaviour when running an In-Place >> upgrade to Win 10 in my client.msi log. >> >> >> >> Client MSI >> >> >> >> 'This update package could not be opened. Verify that the update package >> exists and that you can access it, or contact the application vendor to >> verify that this is a valid Windows Installer update package.' >> >> >> >> In the ccmsetup.log it is using the following syntax to run the install: >> >> >> >> MSI PROPERTIES are REINSTALL=ALL REINSTALLMODE=vmous INSTALL="ALL" >> PATCH="C:\_SMSTASKSEQUENCE\OSD\***00004\HOTFIX\KB2938441\X64\CONFIGMGR2012AC-R2-KB2938441-X64.MSP" >> SMSSITECODE="***" CCMHTTPPORT="80" CCMHTTPSPORT="443" CCMHTTPSSTATE="224" >> CCMFIRSTCERT="1" CCMCERTID="SMS;651D68A957E24DB0FDA887EB1494580F1A0ECFC0" >> REMEDIATE="true" CCMUPDATEOSVERSION="6.4.9841" SMSPUBLICROOTKEY=******** >> >> >> >> My initial thought is is that it is calling up the patch command issued >> as part of my Win 7 TS build originally laid down on the machine. The >> C:\_SMSTASKSEQUENCE\OSD\***00004\HOTFIX\KB2938441\X64\ no longer being >> available on the endpoint post original O/S build. >> >> >> >> Is anyone successfully running in-place upgrade with the patch command >> being used in their original OSD TS? >> >> >> >> Cheers >> >> Paul >> >> >> >> ********************************************************** >> Electronic Mail is not secure, may not be read every day, and should not >> be used for urgent or sensitive issues >> >> >> >> >> >> >> >> ********************************************************** >> Electronic Mail is not secure, may not be read every day, and should not >> be used for urgent or sensitive issues >> >> > >
