anyweb

the error translates to Failed to verify the executable file is valid or to construct the associated command line. Source: System Center Configuration Manager ----- you can use Cmtrace to convert these errors into meaningful text

does it fail consistently or randomly ? what version of MDT is it occurring with ?

i'd suggest you open a ticket with Microsoft CSS, did you have any replication issues prior to the upgrade ?

thanks for clarifying that, I never got around to it due to time constraints and went the eval route for my blog post, along with a follow up here > How can I change System Center Configuration Manager from an Eval edition to a Licensed edition ? I've also added this point to the guide, thanks again !

yes but you might want to upgrade it at some point Windows Server 2008 R2 with SP1 (x64) - Standard, Enterprise, DatacenterWindows Server 2008 R2 is now in extended support and no longer in mainstream support, as detailed by the Microsoft Support Lifecycle. For more information regarding future support for these operating systems as site system servers with Configuration Manager, see Removed and deprecated features for System Center Configuration Manager. Site servers: Central administration site Primary site Secondary site Site system servers: Application Catalog web service point Application Catalog website point Asset Intelligence synchronization point Certificate registration point Distribution point Distribution points support several different configurations that each have different requirements and in some cases support installation not only on servers, but on client operating systems. For more information about the options available for distribution points, see Manage content and content infrastructure for System Center Configuration Manager. Endpoint Protection point Enrollment point Enrollment proxy point Fallback status point Management point Reporting services point Service connection point Site database server Site database servers are not supported on a read-only domain controller (RODC). For more information, see You may encounter problems when installing SQL Server on a domain controller in the Microsoft Knowledge Base. Additionally, secondary site servers are not supported on any domain controller. SMS_Provider Software Update point State migration point Windows Server 2008 with SP2 (x86, x64) - Standard, Enterprise, DatacenterWindows Server 2008 is now in extended support and no longer in mainstream support, as detailed by the Microsoft Support Lifecycle. For more information regarding future support for these operating systems as site system servers with Configuration Manager, see Removed and deprecated features for System Center Configuration Manager. Site servers: Central administration site Primary site Secondary site Site system servers: Application Catalog web service point Application Catalog website point Asset Intelligence synchronization point Certificate registration point Distribution point Distribution points on this operating system do not support Multicast. Distribution points on this operating system are supported for PXE, but do not support network booting of client computers in EFI mode. Client computers with BIOS or with EFI booting in legacy mode are supported. Distribution points support several different configurations that each have different requirements and in some cases support installation not only on servers, but on client operating systems. For more information about the options available for distribution points, see Manage content and content infrastructure for System Center Configuration Manager. Endpoint Protection point Enrollment point Enrollment proxy point Fallback status point Management point Reporting services point Service connection point Site database server Site database servers are not supported on a read-only domain controller (RODC). For more information, see You may encounter problems when installing SQL Server on a domain controller in the Microsoft Knowledge Base. Additionally, secondary site servers are not supported on any domain controller. SMS_Provider Software Update point State migration point https://docs.microsoft.com/en-us/sccm/core/plan-design/configs/supported-operating-systems-for-site-system-servers

here's the process https://www.windows-noob.com/forums/index.php?/topic/4683-using-sccm-2012-rc-in-a-lab-part-12-updating-an-operating-system-image-using-offline-servicing/ however it does not apply to office updates

I like offline servicing myself, what OS are you interested in patching ?

to support Windows 10 servicing, your software update point (SUP) needs to be running WSUS 4.0 or later, and that means Windows Server 2012 or later, with SCCM CB 1610 you can do an in place upgrade of the operating system from Server 2008 to Server 2012R2 see > https://docs.microsoft.com/en-us/sccm/core/plan-design/changes/whats-new-in-version-1602#site-infrastructure also take note of the Warning... WarningBefore you upgrade to Windows Server 2012 R2, you must uninstall WSUS 3.2 from the server. For information about this critical step, see the New and changed functionality section in Windows Server Update Services Overview in the Windows Server documentation.

it doesn't work that way, you can only upgrade to a newer version of Windows 10 using the upgrade task sequence, or using a frontend HTA to 'refresh' while in WinPE, but that would mean having to define your own USMT ruleset, i'd suggest if you want to upgrade, then do it in Windows or instead of applying the 1511 wim why not simply apply the 1607 wim ?

are you referring to updating the WIM files using offline servicing ? that process is covered in step 4 in the first guide linked below: How can I use the Upgrade Task Sequence in System Center Configuration Manager (Current Branch) ? A deeper look at the Upgrade task sequence in System Center Configuration Manager (Current Branch) if you have any issues let me know

thanks and welcome to windows-noob.com

what version of configuration manager are you running, on what server os ?

I'm afraid not, i just checked this and... Central administration site and Primary sites: The site database must use a full install of SQL Server.

hi, so you didn't try the fix above ?

what drivers are not installed in device manager ? did you download a SCCM cab file from Lenovo for this task ?

ok could be this, please try the suggested workaround below An update is stuck with a state of Downloading in the Updates and Servicing node of the Configuration Manager consoleDuring the automatic download of updates by an on-line service connection point, an update can become stuck with a stat of Downloading. When the download of an update is stuck, entries similar to the following appear in the indicated log files: DMPdownloader log: ERROR: Failed to download redist for 037cd17e-4d7b-40e1-802b-14bb682364c7 with command /RedistUrl http://go.microsoft.com/fwlink/?LinkID=724436 /LnManifestUrl http://go.microsoft.com/fwlink/?LinkID=724434 /RedistVersion 112015 /NoUI "D:\ConfigMgr\EasySetupPayload\037cd17e-4d7b-40e1-802b-14bb682364c7\redist" ConfigMgrSetup.log: Error: failed to verify 'd:\ConfigMgr\EasySetupPayload\037cd17e-4d7b-40e1-802b-14bb682364c7\redist\sqlncli.msi' authenticode signature. Error: file signature check failed for 'd:\ConfigMgr\EasySetupPayload\037cd17e-4d7b-40e1-802b-14bb682364c7\redist\sqlncli.msi Workaround: On the site server, modify the following registry key to match the following, and then either restart the SMS_Executive service, or wait up to 24 hours for the next automatic download cycle. Key to edit: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\WinTrust\Trust Providers\Software Publishing Value for State: Set to 146944 Decimal or 0x00023e00 Hexadecimal

is the client computer in a collection targeted by the ADR ?

Microsoft has had an amazing year, pushing out several builds of Windows 10 and Windows 10 Insider Previews and many other software releases such as Windows Server 2016, Configuration Manager Current Branch (and Technical Preview releases) and SQL Server 2016. All those achievements are amazing in their own right. However to the mainstream user, the Windows brand itself, embodies what Microsoft is to that user, as it's the operating system they use day in, day out. In a recent video interview with Paul Thurrott and Mary Jo Foley, they interviewed the Chief Marketing Officer of Microsoft (Chris Capossela) about the year that just went by, and Paul posed this question (edited for clarity/brevity) When you look back at last year, and maybe from a 'more of a negative standpoint' if you will, I mean are there other regrets or things you might have done differently (I don't mean you personally)... to which Chris replied (edited for clarity) And the last one for me, purely from a marketing or branding perspective, is what Paul alluded to, which essentially was for me the uh you know the oh, getting too aggressive in pushing out of the Windows 10 free upgrade, uh and uh you know we know we want people to be running Windows 10 and from a security perspective etc, uh but finding that right balance where you are not stepping over the line of being too aggressive, uh is something we tried and for a lot of the year I think we got it right, but there was one particular moment in particular where you know the red [x] in the dialogue box which typically means, you know, cancel, uh, didn't mean cancel.... and within a couple of hours, of that hitting the world we, you know with the listening systems we have we knew, uh that we had gone too far. so there you have it, Microsoft admitted that the cancel button on the GWX dialogue went too far, and hopefully we won't see any more of that in 2017, it's good to see that a company this big and powerful, has a conscience You can review the video mentioned above here.

have you attempted to restart the SMS_Executive component, notice any difference ? are you sure the proxy details entered are correct ?

can you please try with the full version of SQL to see what it says pls

oooh and it's an Eval version, why are you using that ? maybe that is the cause of the errors ?

use this method to determine SQL server version, what does it reveal ? https://support.cch.com/kb/solution.aspx/sw1873

can you open the db mentioned using SQL Server Management Studio ?

it's the service (user) account you use to install SCCM and to be able to login to SQL Server Management Studio when you did the new pre-req check after updating SQL to the supported version is it still complaining about the SQL version ?

would you like me to do a teamviewer session with you, if so pm me your details and a time frame and i'll connect and have a look but based on your error are you sure the computer is actually in a collection (and not obsolete) that is targeted with the deployment ?