Bondy. tech _ headaches of an sccm admin

So you’re testing out deployment of the new 1607 feature upgrade for Windows 10 in your shiny new 1606 SCCM console. Tools sql server The upgrade appears in your client’s Software Center and starts downloading* and then installing…and then disaster. Sql server convert You are hit with the dreaded message The software change returned error code 0xC1800118(-1048575720). How to sql server Some Googling reveals a lot of the same responses, ie that you’ve allegedly forgotten to apply KB3159706 before synchronising. Sql server news (Just in case this happens to be the case, check out the MS blog with appropriate links) but of course you we all know you applied that correctly, so what else?

It goes without saying that if you’re up and running with the official advice then leave as is and don’t fiddle further unnecessarily. Sql server 2008 express advanced However, if you’re still reading then the chances are that that isn’t the case. Sql server service pack Well there are a number of other solutions describing how you must add the MIME type for the WSUS server as follows:

Again, however, this didn’t fix my issue.

 Maybe I was looking in the wrong places but I could find no information on the internet which fitted my particular set of circumstances, although there appear to be many in the same boat with unanswered forum posts. Sql server 2014 express with tools RESOLUTION

After some head-scratching I did find a solution that worked. Or in sql server I simply reinstalled the the SCCM client agent from the client folder on the site server. Ms sql server 2008 Huh? This didn’t make too much sense to me until I took a closer look at the client version number before and after.

Following this I was able to make the feature upgrade run without error. Subsequent SCCM servicing upgrades also upgraded the client files in this directory and the new client version has clearly fixed some compatibility issues with the 1607 feature upgrade.

I updated the default SCCM client version in the console and ensured all new 1511 builds were running the newer client version. Ms sql server 11 Sure enough, feature updates worked perfectly following every new build. Server 2012 sql I then rolled out the new client agent version to my existing estate. From sql server This will obviously be a pre-requisite to ensure all machines upgrade as expected when the 1607 feature upgrade is rolled out wholesale.

* Another issue I have seen is where the feature upgrade gets stuck downloading at 0%. Sql server for I solved this problem by simply creating a new package and re-downloading the feature upgrade and re-deploying. Sql server express 32 bit -1048575720 0XC1800118

In short, we needed to use the MultiSubnetFailover option string with our SQL AOAG making up the CM2016 back end. Ms sql server 2012 price We have two SQL DBs, one in London and one in Slough. Sql server installation As one might typically expect, these exist on separate subnets. For sql server 2008 After hunting around the internet to try to ensure the supportability of this configuration it quickly became clear that a call to Premier Support was required to confirm. Ms sql server 2008 express edition In particular, we were interested to know whether the ODBC System DSN driver should remain the same on the site server. Ms sql server training By default this uses an old version which doesn’t have the MultiSubnetFailover checkbox available. Sql server registration We figured this might need changing to the newer 11.x native client when AOAG were used over separate subnets. Sql server express 2008 r2 There was an awful lot of to-and-fro between ourselves and Microsoft and it was clear this was an area where there was little clear knowledge. Latest version of sql server We did finally prize an answer out of them however and the following is an edited transcript of the outcome:

ANS: Multi-site Cluster is supported but it`s a complex solution to implement. Ms sql server administration It is heavily dependent on the Hardware Supportability and Networking. Sql server standard edition Storage should also be carefully considered:

• Should we make SCCM use the “SQL server native client V 11.0” ODBC connection “system DSN” connection which has a check box that seems to have “ multisubnetfailover” option or the default SCCM installed “SQL driver” for ODBC connection?

ANS : We should not be making any changes to the default configuration made as part of the ConfigMgr installation. Ms sql server 2012 express edition ConfigMgr does not support SQL Server Multi-subnet clustering.

• If we upgrade SCCM from 1511 to 1602 (or to a later version in future) will the upgrade make the site server use the “SQL driver ODBC” connection again, needing a manual change to SQL native client again?

• [PS Engineer] wrote the following “…SCCM Components make use of dll’ (some components) and SQL Server native Client both. Sql server enterprise Native Client will get updated as per SCCM need, and we can leave sqlsvr32.dll’ as its default version.”

Our response: But slqsvr32.dll, does it have the multisubnetfailover option? We cannot see this. Sql server 2005 developer edition Where and how do we configure ALL the components to use multisubnetfailover on primary site server and other component servers as appropriate?