1709 and Essentials 2012 R2

On December 31, 2017, in news, by susan

I’ve seen several posts and had several people indicate that the upgrade to 1709 kills the connector software on Essentials 2012 R2.   However, I’m finding in my own tests that when I have rebooted three times after installing the 1709, the connector lights up again and is connected.

If you have issues, some in this thread have indicated that the following works:

“But you can start the following exe (on the client) to reregister the client:

C:\Program Files\Windows Server\Bin\ClientDeploy.exe

After this the client is online in the dashboard and the backup works also.”


UPS worldship and 1709 Windows 10

On December 31, 2017, in news, by susan

UPS worldship and 1709 Windows 10

Thanks to Peter Perry for another 1709 workaround:

“UPS Support Level 2 fixed the issue. They acknowledged 1709 exacerbates the problem. It requires deleting a bunch of config files in the Program Data folder, disabling BITS, rebooting, run UPS WorldShip (which then works), the re-enable BITS. It continues to work thereafter.”


1709 known issues – follow up

On December 5, 2017, in news, by susan


KB4051963 has helped some users with the RDP crashing issue.  However a few folks still have rdp crashing issues when printing is redirected.  To figure out WHAT printer is the problem, follow this guideline:

Follow this:

If anyone else runs into this issue I would suggest the following steps:
1. Disable the “printers” check box on your Remote Desktop Connection by navigating to Options>Local Resources>Local Devices and resources. Then try to connect.
2. If connection is successful with the printers disable, start removing printers on your local machine one by one in order to figure out which printer is causing the problem.
3. Once you have figured out the problem printer driver, reinstall with a different driver.

It’s helped a few folks here in this forum https://answers.microsoft.com/en-us/windows/forum/windows_10-networking/windows-10-fall-creators-update-remote-desktop/d8e0273d-a82a-4ae6-88ce-450b846946ac?messageId=af70b487-1a9f-4026-94ae-e8bf37d62554


1709 and Essentials

On October 19, 2017, in news, by susan

Getting multiple reports that after the install of 1709 the client connector from the Essentials 2012 R2 is gone and can’t be reinstalled.

Hang loose, seeing about getting cases opened up to investigate.


1709 side effects (at this time)

On October 18, 2017, in news, by susan

Just a heads up, installing Windows 10 1709 fall release causes the classic rdp/rdgateway application to constantly crash.  This impacts RWW/RWA on SBS and Essentials.  As a workaround you can use the RDP app from the Windows store, however it doesn’t remote print.

So once again a strong… hold off on installing the fall release … until we get some of these early bugs worked out.

Temp disable remote printing as a workaround 


Fixing up the Dual Scan problem

On August 7, 2017, in news, by susan

For those of you (like me) who just recently updated to 1703, we will need to wait until September  until we can squash a bug in the interaction between WSUS and Microsoft update.  If you configure any of the “Windows update for business” settings AND have WSUS installed, you will see your machines going to both WSUS and MU for their updates.  In the August updates out tomorrow, the 1607 release get a new group policy setting that will allow you to stop the machines from going out to MU and WSUS at the same time.

1703’s will have to wait a bit before we get the fix.

Improving Dual Scan on 1607


Are we in a “serverless” environment?

On August 7, 2017, in news, by susan

Microsoft is positioning that small businesses are in a serverless world.  Put data in onenote, have hosted email and that will work for some businesses.  But not all.  I don’t think we’re quite there for all small businesses.  Cloud based applications still need some time and age to mature to match premises software.  Hosted solutions are really not “serverless”, the server is just located in another geographic location.

But what I do know that right now buying the small business licensing is still messy.


I’ve attempted to buy Windows 10 E5 subscription from CDW and pretty much failed in the process.  It took Amy Babinchak and her techdata contacts before I was successful in purchasing the low numbers I wanted to purchase.

This points out a key requirement in the current world – having good vendor relationships and finding ways to get your clients the licenses they need.

Do you have a “goto” vendor?


So Microsoft? You serious about Small Business?

On August 2, 2017, in news, by susan

Dear Microsoft:  I think we need to talk.  I don’t think you are as serious about small business as you say you are.  Why do I say that?  Because the server and server role you say is all about Small business isn’t officially supported to have Azure AD connect installed on it.  Yet you are building more and more subscriptions and Windows 10 features on using Azure AD connect.

Microsoft knows that https://docs.microsoft.com/en-us/azure/active-directory/connect/active-directory-aadconnect-prerequisites “Azure AD Connect cannot be installed on Small Business Server or Windows Server Essentials. ” this statement is a mere support statement.  They don’t want us to try to do the Office 365 wizard AND the Azure AD connect at the same time because obviously the two wizards/technology will fight one another on syncing passwords.  But if you are really serious about small business – no current server sku should be blocked from having Azure AD connect installed.

So Microsoft?  How about you get serious.  Either allow Essentials to have the Azure AD connect code installed or be honest with all of us and stop building Essentials.

I for one, want Microsoft to still build Essentials and the Essentials role. Why?  Because I want to have Microsoft to still have a stake in small business in the server section.

So pardon me as I go give feedback in the Server 2016 insider edition.