Getting back on track –

We’re getting ready for a proof of concept to showcase moving from SBS 2008 to Essentials R2 with Exchange 2013 sp1.

You can now download both 2012 R2 with update 1 and Essentials 2012 R2 with update 1.  If you have not yet deployed R2 servers, I’d recommend that you jump to this version and save the time and hassle of downloading KB2919355.

I’m going to manually join this 2012 R2 server to the existing SBS 2008 domain.  Remember Essentials you do the same, you stop the wizard upon running and manually join it to the domain.

But I’m getting ahead of myself.

First let’s join our 2012 r2 server to our SBS 2008 domain.  To make it easy in VM I manually change the DNS settings on the workstation in order to look at the virtual DC.


Over on the 2012 r2 change the DNS setting to match the server.

Then you go into the computer info and change it to join it to the domain

Add domain credentials and reboot the server.

Now log into the server with the domain credentials

Blogging my way (starting over) through a proof of concept migration from SBS 2008 to Essentials 2012 R2 series will be a SMB kitchen project whitepaper.  More about the SMBKitchen project at –  and check out our new project the ASP  Remember only two days left to check out the resources.  Hop on, see what you are missing, we think you’ll stick around for more.

A friend of mine, Dave Sanford, passes this along:

We experienced an issue when installing the Quickbooks client upgrade to QBEv14R5, just last week. 

We had 3 users in one office and 4 users in another and the first 3 went through no problem, then the other 4 threw the error  (sample below) no matter what we did. The install went fine, but then just died whenever you tried to open a company file, with the error message.

Name:  \\server\quickbooks file name

Description ND File

//This is QuickBooks configuration file. It exists while users are connected ..//to a company file. Do not delete this file yourself. QuickBooks may not .. // operate correctly IF you manually delete this file.

[NetConnect] ..ServerIP=192.168.x.x..EngineName=QB_Servername..ServerPort=55358 File path = (location of file) ServerMode=1

We were using the QBE V14 R5 installer, and performed all the possible resolutions we could think of, including recreating and verifying the .ND files, coping the company files to a local machine to isolate any network/server issue, running the QB built in File & Network diagnostics and the QBInstallDiagnosticTool on the clients, same results.

Finally, one of our techs received the “DbProviderFactories section can only appear once per config file” error when trying to open Quickbooks, and searching for that error led him to this link: 

We then checked all of the machines we had installed the upgrade on and found that all of the machines with the error indeed did have the extra DbProviderFactories empty element in the Dot_Net_v4… machine.config file. Once we commented out the extra element, all of the machines were able to boot QBE and access the company files without issue.

I then installed on my laptop, got the same error and applied the same fix, after which I could proceed without error.

The odd thing is that it seems some machines have the extra element in the Dot_Net_V4 file and some do not… yet we cannot identify any difference in the level of Dot_Net updates applied – they are all running Win 7 Pro – and none of these machines, including my laptop, have anything to do with Visual Studio of any version… go figger!?!

In the event, just wanted to let you know as maybe it will help others that encounter this issue in the future?

No, not 3 more days to install KB2919355, three more days to sign up for free access to the SMB Kitchen ASP project to get a sneak preview until April 30th.  Come May, it will be subscriber only.  In May you’ll get my client facing security communication to used to help “patch” the users of the computers. 

Speaking of patching, if you sign up for the free access now, you’ll get my take on this latest IE zero day that was just announced(1)  and what it means for XP’s still in use and what actions you can take to protect them.

I’ll be sending it off to Amy shortly and she’ll be publishing it up their for your review.

For those of you who subscribed last year, you’ll still get a copy of my step by step proof of concept migration (that I apologize I got a bit sidetracked with busy season and with KB2919355 but I’ll be back blogging on it tomorrow)

(1) and

(broken record here just making it clear) Unmanaged systems – those not behind WSUS/Intune/System center still have a May 13th deadline of getting 2919355 installed.

Spotted a post in the forum with some interesting debugging:

Windows 8.1 update fails to install – KB2919355 – Microsoft Community:

Success at last. I have been researching and working on this for over a week and have attempted every single “fix” or “repair” proposed here and via MS troubleshooting pages with absolutely no success.

sfc /scannow reported no errors. I used Dism which indicated the store was repairable however RestoreHealth always provided the following message:

The restore operation failed. Either the repair source was not found or the component store cannot be repaired.
Error: 0x800f081f
DISM failed. No operation was performed.

I reviewed the CBS.log file and found a report of missing files (mshtml.tlb, mshtml.dll and F12.dll) which I tracked down via the log file to update KB2909921. I downloaded the KB2909921.msu and used 7-Zip to extract the files contained in the msu to a folder on a USB drive. I then expanded the cabinet archive to the same folder. After locating the above files I restored them to the appropriate containers using the information found here: <>

and here:

After making the repairs dism /restorehealth continued to indicate the restore operation failed with the same message, *HOWEVER now the CBS.log file reported everything appeared to be ok* other than a reference to a problem with meta data.

Operation: Detect and Repair
Operation result: 0x0
Last Successful Step: Entire operation completes.
Total Detected Corruption:0
CBS Manifest Corruption:0
CBS Metadata Corruption:0
CSI Manifest Corruption:0
CSI Metadata Corruption:0
*CSI Payload Corruption:**0*
Total Repaired Corruption:0
CBS Manifest Repaired:0
CSI Manifest Repaired:0
CSI Payload Repaired:0
CSI Store Metadata refreshed:True

Previously it was reporting “CSI Payload Corruption: 3” which was apparently related to the missing files referred to above and which previously indicated was not repaired, presumably because the files could not be found.

I had previously been unable to install KB2939087 and KB2919355 and always received error 80073712 after trying every fix mentioned in the forum. I ran Windows Update Diagnostic again and received the same messages I had always received, but because the CBS log showed things were ok, I decided to try to download and install again using Desktop Windows Update.

I first attempted to install KB2939087 which installed, asked for a restart and was successful. I then attempted to install KB2919355 which likewise installed, asked for a restart and was successful.



21 days before unmanaged 8.1 systems are locked out of getting security updates.  And I’m still seeing issues with folks trying to get the update installed.

I worked with Robert (the PowerShell genius) to build a PowerShell tool that let’s you run some of the commands in the post in the answers forum as well as checking on the free space in the C drive and in the reserved partition.

This however is very disturbing.  I can confirm that after installing KB2919355 and running that dism command you get a failure


Seeing what I can find about it now.

For those running default SBS 2003 R2/2008 and 2011 with WSUS – it auto approves security updates to servers and workstations.  If you have an 8.1 or R2 deployed in that network, KB2919355 will be automatically approved and probably automatically installed tonight.

Just be aware and watch your patch settings.

2919355 is deemed a critical security update and thus will automatically be installed if you have not changed the settings.

For those of you behind WSUS, Intune or System center the less than 30 days before KB2919355 has to be installed has been extended.

Folks who patch with WSUS/Intune or System center have until August to roll out KB2919355

The issue with WSUS has now been fixed.  You’ll see on your manually or WU updates boxes that already have KB2919355 ANOTHER KB2919355 this time a much smaller update that fixes just the issue with the WSUS deployment


Only 29 days-ish to get KB2919355 installed.  And we’re starting to see people getting their issues resolved (yea) and starting to see the support engineers move from the fishing expeditions to where they can start giving out canned responses to the problems. 

Still Microsoft is in it’s offering up mode and not pushing out the door mode (you can tell this in the USA as the update is offered up but not yet checked). 

I’ll be starting my roll out this week and I’ll let you know how it goes.

One Surface/one 2012 r2 server.