anyweb

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 ?

ok and the first message about 'login failed' are you using the same user account in both environments ?

well 11.0.5388.0 is somewhere between SQL Server 2012 SP2 and SP3 according to https://sqlserverbuilds.blogspot.se/ your other version (test env) is using SQL Server 2012 RTM so you must update it to SP2 prior to doing the testdbupgrade

what version is your SQL server, the version needed is listed in your last screenshot

clearly something else is happening then, as it's not doing what it's supposed to, can you attach the entire smsts*.log pls

thanks for the code update and the comments, i appreciate it :-)

that comes later, the focus here was sql server 2016 on windows server 2016 with the latest Current Branch baseline installer

what error do you get ? did you add the database components to your boot images ? WinPE-MDAC

I'd recommend you use virtual machines for operating system reference image creation that way you keep it driver agnostic and it's easy to deploy the captured image to real hardware using customized Apply Driver Package steps based on wmi queries, the build and capture process is how you create a new reference image using SCCM, but you can also create a reference image using MDT, what version of SCCM do you have ? and what operating system are you trying to deploy ? the guides here will help you

hi and welcome, i'd recommend you start by looking at these two guides How can I deploy Windows 10 with MDT 2013 Update 2 integrated with System Center Configuration Manager (Current Branch) How can I install Windows 10 language packs offline with an MDT Integrated Task Sequence in System Center Configuration Manager (Current Branch)

if you want it dutch by default then install using the dutch media and add the english language pack as an add on

can you post the relevant bits from your logs pls

as long as you don't change the OSDUILanguage of the operating system then you should have what you want, so just modify the solution presented above to achieve that (disable the OSDUILanguage references or set them to en-us)