The official blog for Windows Server Essentials and Small Business Server support and product group communications.
EPS Team Blogs
The Update Rollup 3 for Windows Server 2012 Essentials has been released and is now available for download from Microsoft Update. You can read about the issues this rollup update addresses in Microsoft Support Knowledgebase 2862551.
The client-side package for this update rollup is downloaded to the Windows Server 2012 Essentials along with this update rollup. The user does not have to go to the Windows Update website to obtain the package separately for the client machines. The Update Rollup 3 client-side package is same as the existing Update Rollup 1 client-side package 2781268.
This update rollup contains improvements such as DNS auto-detect and configure for the clients, some new Best Practice Analyzer rules and introduces a new branding name for the Windows Azure Backup integration add-in. Apart from the improvements, this update rollup also resolves certain previously identified issues.
For more information, please visit this link.
The KB article indicates "After Update Rollup 3 is installed, all the clients that are joined to the Windows Server Essentials server automatically skip the DNS detection. The existing clients that were connected to the Windows Server Essentials server before the update rollup was installed must reconnect to the Windows Server 2012 Essentials server."
After I installed the update rollup, clients stopped reporting into the Dashboard. I indeed had to uninstall the connector and reinstall. This is going to be a nightmare for my clients that have many PCs. Am I missing something?
I am having the same issue pperry803, has any one figured this out yet? What a nightmare!
Reboot the server again and see if it fixes the issue. It did for another one of my customers.
Anyone having an issue with client backup: my client laptops are waking to backup even if they aren't plugged in. Previously, I don't believe they woke unless they were plugged in. Thoughts on what I can do to resolve?
Since the update, my win7-clients only partly report into the dashboard. Update and backupstatus get reported, but I always get an yellow warning for those machines. (Win8-Clients don't have this issue).
I also found an FixIt that claims to solve the problem, but the description only suits previous Versions of WinServer , also it is older than the Update that caused the malfunction. So probably it won't do it, and I am still waiting for a Fix for the Update.
So relieved user feedback about this issue (back in Sep 2012) has been addressed by Microsoft, with the original story here:
"Windows Server 2012 Essentials remote client loses its Internet connection, here’s your DNS-related fix"
I've now put together a new post, summarizing how to clean up after UR3. Hopefully folks find it helpful!
"Windows Server 2012 Essentials Update Rollup 3 has arrived, with DNS fixes"