none
Windows 10 Clients and Server 2012/R2 Essentials RRS feed

  • Question

  • We have a number of clients that have Windows Server Essentials 2012 and 2012R2 networks.  The client workstations are all Windows 7 Professional.  This combination has worked very well for everyone.  However, with the "free" Windows 10 upgrade soon-to-expire, we are getting questions about upgrading the client OS to Windows 10 Pro (and/or adding new Windows 10 computers to the existing network).  One reason we have held off on this is that I know there have been problems with Windows 10 and Server Essentials 2012.

    Here is my question:  Does Windows 10 now work properly with Essentials, the connector software, etc.?  Or are there still issues/problems with this combination?  Understandably, I'd rather know about any looming potential obstacles prior to implementing the client OS upgrade.

    Thanks very much.


    John

    Thursday, July 7, 2016 7:35 PM

Answers

  • I disagree that Windows 10 works "essentially" well enough to deploy in production with Windows Server 2012 R2 Essentials.

    Indeed, even with the latest patched connector software, the Windows Server Essentials Dashboard Devices tab incorrectly reports the status of Group Policy for Windows 10 clients. Considering that Windows 10 is Microsoft's flagship desktop operating system and Windows Server 2012 R2 Essentials is the latest-and-greatest small business server actually available for purchase, I find it inexcusable that it doesn't report correctly all of the status information presented on the Dashboard.

    I'm not even going to dwell on the hard-to-stomach time it took for Microsoft to release the current, shoddy version of the connector software; but I will mention it. For months after Windows 10 was released, there wasn't even a version of the connector software available that would install on Windows 10 clients! It seemed Microsoft didn't have any understanding that we needed time to test Windows 10 with Windows Server 2012 R2 Essentials BEFORE we could recommend it to our clients. That meant we didn't start testing until we had access to the "working" connector software in November.

    Just as we got started testing Windows 10 with Windows Server 2012 R2 Essentials in the lab, we were hit with another big issue: the connector software is removed every time Windows 10 installs a Feature Upgrade. See the link below:

    https://blogs.technet.microsoft.com/sbs/2016/01/22/windows-10-feature-upgrade-breaks-client-connector-for-window-server-2012-r2-essentials-windows-server-2012-essentials-and-windows-small-business-server-2011-essentials/

    If we had deployed Windows 10 in production, one day after a Windows Update Feature Upgrade was released, all of our client's workstations would lose their connector functions the next morning! The workaround is to simply reinstall the connector software on each workstation again. That's not so easy if you have to do it on a few hundred workstations all at once! The "coming fix" was described more than six months ago; since then, no fix and no updates about when we'll see it.

    Because we considered it too risky to deploy Windows 10 in Windows Server 2012 R2 Essentials environments, due to the fact that the next Feature Upgrade will take out the connector software, we continued to rely on Windows 7 in those environments. And since Microsoft never provided the "coming fix" before the free upgrade from Windows 7 to Windows 10 expired, we probably won't ever upgrade those client workstations to Windows 10. 

    That brings us up to where we are now. And right on que, the Windows 10 Anniversary Feature Upgrade was just released:

    https://blogs.windows.com/windowsexperience/2016/08/02/how-to-get-the-windows-10-anniversary-update/

    All of you who did deploy Windows 10 with the Essentials Connector, enjoy reinstalling the connector on all your Windows 10 workstations again!

    Oh but wait--it get's better! It appears that not only will the connector be removed again by the Anniversary Update, but after the upgrade, it won't reinstall correctly. After attempting to reinstall it, the connector icon no longer appears in the system tray, and there doesn't seem to be a way to open the Essentials Launchpad. I'd say that pretty much puts us right back to where we were before last November when we couldn't get the connector to work on Windows 10 clients.

    If and when Microsoft provides a stable Windows 10 client that connects--and stays connected--with a Windows Server Essentials environment, we'll begin testing it in the hopes that one day we can deploy it for use by our customers. And it wouldn't hurt if the Dashboard displayed correct information about Windows 10 clients, too! I suspect we may have to wait for Windows Server 2016 or 2017, as Microsoft has shown very little progress in getting the Windows Server 2012 R2 version to work reliably with Windows 10 clients.

    If and when they do finally provide such an environment, Microsoft should allow us to upgrade the clients from Windows 7 to Windows 10 for free at that time. After all, it isn't our fault that it was impractical to take advantage of the free upgrade while Windows 10 doesn't work right with Windows Server 2012 R2 Essentials. Ironically, we did upgrade all of our Windows 7 clients to Windows 10 in our Small Business Server 2011 sites. The SBS 2011 connector works on Windows 10, and stays installed--even during the initial upgrade from Windows 7 to Windows 10. In those environments, we now can't upgrade the server because nothing newer than SBS 2011 supports Windows 10 clients reliably!


    Trilon, Inc.

    • Marked as answer by JN92 Wednesday, August 3, 2016 1:59 PM
    Wednesday, August 3, 2016 9:50 AM
  • There are some known issues, like the Dashboard not displaying status of the Windows 10 correctly, but 'Essentially' windows 10 works ok with all versions of Essentials.

    Robert Pearman Cloud & Datacentre MVP
    @titlerequired | LinkedIn | Google+
    Facebook | Windows Server Essentials.com

    • Marked as answer by JN92 Sunday, July 17, 2016 2:18 PM
    Friday, July 8, 2016 2:31 PM
    Moderator
  • you will have to reinstall it as the upgrade simply removes it

    It will say a machine with this name is already there just hit next


    Grey

    Friday, July 8, 2016 4:42 PM
    Moderator
  • https://support.microsoft.com/en-us/kb/3172614

    Includes this fix "Updated the inbox component in Windows Server 2012 R2 Essentials to use the new client connector, so that the inbox component won't get uninstalled during Windows 10 upgrades."

    • Marked as answer by JN92 Wednesday, August 3, 2016 3:27 PM
    Wednesday, August 3, 2016 2:32 PM

All replies

  • Hi,

    Windows 10 Feature Upgrade breaks client connector for Window Server 2012 R2 Essentials, Windows Server 2012 Essentials and Windows Small Business Server 2011 Essentials:
    https://blogs.technet.microsoft.com/sbs/2016/01/22/windows-10-feature-upgrade-breaks-client-connector-for-window-server-2012-r2-essentials-windows-server-2012-essentials-and-windows-small-business-server-2011-essentials/

    As mentioned that the fix is expected in the coming months and there is workaround before the coming fix.

    It is always recommend to upgrade the OS to latest edition due to new functions and improved performance. 

    I have built a test environment which includes Windows Server 2012 R2 Essentials and multi Windows 10 clients for months, everything goes smoothly. 

    I would recommend you to build a test environment, or, have several client to be upgraded and check the result. for system upgrading, there are some factors should be considered, such as compatibility with existing application, hardware, and important data/system backup.

    Best Regards,
    Eve Wang

    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Friday, July 8, 2016 7:51 AM
    Moderator
  • Thanks for your reply. Just so I understand this, are you saying that the workaround for this problem is to rerun the Connector program on the Windows 10 client machine? Do we need to uninstall/remove the existing Connector software first?

    John

    Friday, July 8, 2016 1:04 PM
  • There are some known issues, like the Dashboard not displaying status of the Windows 10 correctly, but 'Essentially' windows 10 works ok with all versions of Essentials.

    Robert Pearman Cloud & Datacentre MVP
    @titlerequired | LinkedIn | Google+
    Facebook | Windows Server Essentials.com

    • Marked as answer by JN92 Sunday, July 17, 2016 2:18 PM
    Friday, July 8, 2016 2:31 PM
    Moderator
  • Thanks Robert, that's good to hear. Is the best way to do this to reinstall the Connector after the Win 10 upgrade has completed?

    John

    • Marked as answer by JN92 Sunday, July 17, 2016 2:18 PM
    • Unmarked as answer by JN92 Sunday, July 17, 2016 2:18 PM
    Friday, July 8, 2016 3:16 PM
  • you will have to reinstall it as the upgrade simply removes it

    It will say a machine with this name is already there just hit next


    Grey

    Friday, July 8, 2016 4:42 PM
    Moderator
  • I disagree that Windows 10 works "essentially" well enough to deploy in production with Windows Server 2012 R2 Essentials.

    Indeed, even with the latest patched connector software, the Windows Server Essentials Dashboard Devices tab incorrectly reports the status of Group Policy for Windows 10 clients. Considering that Windows 10 is Microsoft's flagship desktop operating system and Windows Server 2012 R2 Essentials is the latest-and-greatest small business server actually available for purchase, I find it inexcusable that it doesn't report correctly all of the status information presented on the Dashboard.

    I'm not even going to dwell on the hard-to-stomach time it took for Microsoft to release the current, shoddy version of the connector software; but I will mention it. For months after Windows 10 was released, there wasn't even a version of the connector software available that would install on Windows 10 clients! It seemed Microsoft didn't have any understanding that we needed time to test Windows 10 with Windows Server 2012 R2 Essentials BEFORE we could recommend it to our clients. That meant we didn't start testing until we had access to the "working" connector software in November.

    Just as we got started testing Windows 10 with Windows Server 2012 R2 Essentials in the lab, we were hit with another big issue: the connector software is removed every time Windows 10 installs a Feature Upgrade. See the link below:

    https://blogs.technet.microsoft.com/sbs/2016/01/22/windows-10-feature-upgrade-breaks-client-connector-for-window-server-2012-r2-essentials-windows-server-2012-essentials-and-windows-small-business-server-2011-essentials/

    If we had deployed Windows 10 in production, one day after a Windows Update Feature Upgrade was released, all of our client's workstations would lose their connector functions the next morning! The workaround is to simply reinstall the connector software on each workstation again. That's not so easy if you have to do it on a few hundred workstations all at once! The "coming fix" was described more than six months ago; since then, no fix and no updates about when we'll see it.

    Because we considered it too risky to deploy Windows 10 in Windows Server 2012 R2 Essentials environments, due to the fact that the next Feature Upgrade will take out the connector software, we continued to rely on Windows 7 in those environments. And since Microsoft never provided the "coming fix" before the free upgrade from Windows 7 to Windows 10 expired, we probably won't ever upgrade those client workstations to Windows 10. 

    That brings us up to where we are now. And right on que, the Windows 10 Anniversary Feature Upgrade was just released:

    https://blogs.windows.com/windowsexperience/2016/08/02/how-to-get-the-windows-10-anniversary-update/

    All of you who did deploy Windows 10 with the Essentials Connector, enjoy reinstalling the connector on all your Windows 10 workstations again!

    Oh but wait--it get's better! It appears that not only will the connector be removed again by the Anniversary Update, but after the upgrade, it won't reinstall correctly. After attempting to reinstall it, the connector icon no longer appears in the system tray, and there doesn't seem to be a way to open the Essentials Launchpad. I'd say that pretty much puts us right back to where we were before last November when we couldn't get the connector to work on Windows 10 clients.

    If and when Microsoft provides a stable Windows 10 client that connects--and stays connected--with a Windows Server Essentials environment, we'll begin testing it in the hopes that one day we can deploy it for use by our customers. And it wouldn't hurt if the Dashboard displayed correct information about Windows 10 clients, too! I suspect we may have to wait for Windows Server 2016 or 2017, as Microsoft has shown very little progress in getting the Windows Server 2012 R2 version to work reliably with Windows 10 clients.

    If and when they do finally provide such an environment, Microsoft should allow us to upgrade the clients from Windows 7 to Windows 10 for free at that time. After all, it isn't our fault that it was impractical to take advantage of the free upgrade while Windows 10 doesn't work right with Windows Server 2012 R2 Essentials. Ironically, we did upgrade all of our Windows 7 clients to Windows 10 in our Small Business Server 2011 sites. The SBS 2011 connector works on Windows 10, and stays installed--even during the initial upgrade from Windows 7 to Windows 10. In those environments, we now can't upgrade the server because nothing newer than SBS 2011 supports Windows 10 clients reliably!


    Trilon, Inc.

    • Marked as answer by JN92 Wednesday, August 3, 2016 1:59 PM
    Wednesday, August 3, 2016 9:50 AM
  • Thanks very much for your detailed "real world" response. We could probably adjust to some of the problems you mention, but (like you) we simply cannot deal with emergency reinstallations of every Windows 10 client after every OS update. It is amazing (and disturbing) that this level of problem has gone unfixed for over a year now.

    John

    Wednesday, August 3, 2016 1:59 PM
  • John?  After this latest update, what issues are you seeing?  It should work.  If it's not let's discuss what you are seeing.
    Wednesday, August 3, 2016 2:29 PM
  • The Server update rollup that was released in July should get rid of the issue that the connector has to be reinstalled each release.
    Wednesday, August 3, 2016 2:29 PM
  • https://support.microsoft.com/en-us/kb/3172614

    Includes this fix "Updated the inbox component in Windows Server 2012 R2 Essentials to use the new client connector, so that the inbox component won't get uninstalled during Windows 10 upgrades."

    • Marked as answer by JN92 Wednesday, August 3, 2016 3:27 PM
    Wednesday, August 3, 2016 2:32 PM
  • Susan:

    As per my initial post, our test Windows 10 workstations, which were connected to the Windows Server 2012 R2 Essential system via the released connector software, did, in fact, lose their installations of the connector software after the Windows 10 Anniversary Update was installed upon them. Worse, when we attempt to reinstall it by going to http://<our-server>/connect and going through the Windows Server Essentials Connector Configuration Wizard procedure, the procedure completes yet there is now no connector icon shown in the system tray, nor any way I can find to launch the Essentials Launchpad at the Windows 10 workstation post the installation of the Windows 10 Anniversary Update.

    Do you have Windows 10 Anniversary Updated workstations able to install the Essentials Connector such that you can see the connector icon in the system tray and/or can launch the Essentials Launchpad?


    Trilon, Inc.

    Wednesday, August 3, 2016 3:26 PM
  • Thanks Susan. I will make certain that this server OS update is installed on Windows Server 2012/R2 Essentials before upgrading the workstations to Windows 10. John

    John

    • Marked as answer by JN92 Wednesday, August 3, 2016 3:27 PM
    • Unmarked as answer by JN92 Wednesday, August 3, 2016 3:27 PM
    Wednesday, August 3, 2016 3:27 PM
  • Note that even if the July rollup would get rid of the issue that the connector has to be reinstalled each release, the July update would only update the connector distribution on the Essentials server. Thus, any Windows 10 clients that already installed the released connector would still get kicked out when the Windows 10 Anniversary Update gets installed. Only after then reinstalling the updated connector again would the Windows 10 client get the July connector update.

    That is, the July update doesn't update the already installed connectors on Windows 10 workstations. It only updates the distribution of the connector software in the Essentials server such that any subsequent installations will be the updated July code.


    Trilon, Inc.

    Wednesday, August 3, 2016 3:50 PM
  • I have confirmed my Windows Server 2012 R2 Essentials test system installed the Update for Windows Server 2012 R2 (KB3172614) update on July 25. So when I now attempt to reinstall the connector on my test Windows 10 client workstation that have the Windows 10 Anniversary Update, I should be trying to install the July updated connector software. And when I do so, the Windows Server Essentials Connector Configuration Wizard procedure completes, yet there is no connector icon shown in the system tray, nor any way I can find to launch the Essentials Launchpad.

    Trilon, Inc.

    Wednesday, August 3, 2016 3:55 PM
  • You shouldn't need to reinstall any connector.  It shouldn't lose it in the first place.
    Wednesday, August 3, 2016 5:27 PM
  • In program files is there a Window server essentials folder?
    Wednesday, August 3, 2016 5:28 PM
  • Rule of Susan, I never install big updates on the day they come out.  Ever.  I have a 2012 r2 Storage server essentials (same code as Essentials R2) and my 10's are behind WSUS and 10 1607 isn't yet on WSUS.

    Let me get up to 1607 on a test machine and I'll report back.

    Wednesday, August 3, 2016 5:30 PM
  • In reading the OLD blog post it said "We recommend to connect the Windows 10 client one more time to Windows Server 2012 R2 Essentials when the fix is out"
    Wednesday, August 3, 2016 5:49 PM
  • Hi I have exactly the same issue as you do. I can launch the Launchpad manually with C:\Program Files\Windows Server\Bin\LaunchPad.exe, however. I think there is a good possibility that the issue with the missing tray icon is unrelated to the Anniversary Update v 1607 and is just an issue with the "inbox" connector install included with KB3172614 that would result in a missing icon on Windows 10 v 1511 as well. This missing tray icon issue was reported in these forums on 23 July, before the general release of the Anniversaty Update. Of course, it's possible that the post on 23 July related to a Windows 10 workstation on the Insider Program, but I an not convinced this issue is only occuring on workstations updated to the Anniversary Update. Robert
    Wednesday, August 3, 2016 6:33 PM
  • Same behaviour for us.

    We were preparing a Sysprep image on July 23. Just before the roleout finished, the 1607 update his a couple of the freshly installed Windows 10 PCs with Essentials COnnector (2012R2 Essentials had the Rollup-Update with the fix) , the connectors got lost on all PCs. 

    We had to reninstall  (Connector from https://server/Connect) and then Update the Connector again to Windows 10 Version (https://blogs.technet.microsoft.com/sbs/2015/11/17/client-connector-availability-with-windows-home-server-small-business-server-and-windows-server-essentials-for-supported-client-os/) . 

    After these steps it is working again. 

    As some of you mentioned, it is impossible to have emergency support on a whole bunch of PCs one morning after an upgrade from Microsoft was forced. 

    We opened a ticket with Microsoft support and will let you know the outcome, in case there is any.

    Thursday, August 4, 2016 10:07 AM
  • Hi Christian

    So if I understand you correctly, you are saying that you had PCs that had been connected with the updated connector which is supposed to remain in place through an upgrade, but in actual fact, the Anniversary Update removed it all the same. So, the Rollup-Update in your experience does nothing to fix the long-standing issue with the connector being removed on upgrading Windows 10.

    Apologies, but I don't understand your fix. When you say "Update the Connector again to Windows 10 Version", what exactly did you do? Did you, effectively, "downgrade" the connector to the previous version directly from the MS website (https://www.microsoft.com/en-us/download/details.aspx?id=40285)?

    Thanks for your input on this, much appreciated.

    Thursday, August 4, 2016 3:22 PM
  • Yes, we used the updated connector before the feature update was installed (Windows 10 1511 to 1607) . Connector got removed by Upgrade.

    Then we reconnected with https://yourserver/Connect , restarted etc. Last step, as this connector is not working with Windows 10 we updated the Essentials Connector from here:

     (https://blogs.technet.microsoft.com/sbs/2015/11/17/client-connector-availability-with-windows-home-server-small-business-server-and-windows-server-essentials-for-supported-client-os/

    No update on the Microsoft ticket.

    We submitted some logfiles so far.

    Thursday, August 4, 2016 4:55 PM
  • KB3172614 <<< is a brand new connector and the one on that old post would be the old code.  Before you went from 1511 to 1607 did you install the update rollup on the server?
    Thursday, August 4, 2016 4:57 PM
  • Windows 10 1511 Connector installed as an Update, Dashboard and Launchpad worked with NO problem.

    Windows Server Essentials R2 all updates installed including KB3172314.

    Update to Windows 10 1607. The Dashboard and Launchpad Icons were removed.

    Reinstall the connector and still No Icons on the Tray.

    Checking the Apps there are 2 entries Windows server connector and Windows server Dashboard. Clicking on the Dashboard it starts and after signing it Loading for a few seconds and then it close with no connection to server.

    However if you use the Remote Desktop App you are able to connect the server and the Dashboard.

    I called Microsoft support but after 3 Different agents they had NO idea what I was taking about!!!!

    I Hope that Microsoft fixes the problem soon or revert to  widows 1511 only have 10 Days   

    Thursday, August 4, 2016 5:48 PM
  • Mimis?  Let me open a support case on your behalf and get you in the right department.

    email me at susan-at-msmvps.com and I'll need your phone number.

    How do you only have 10 days?  Not following?

    Thursday, August 4, 2016 6:08 PM
  • Mimis,

    on of 6 machines we have currently the same issue. the other 5 are working well in this particular environment. All were installed on exactly the same hardware with exactly the same sysprep image. 

    Very interesting again (although time consuming) .

    Please let us have an update in case you find a solution.

    Thursday, August 4, 2016 6:29 PM
  • Nevermind:

    https://www.petri.com/microsoft-cuts-windows-10-rollback-period-10-days

    The reason for the reduction, according to Microsoft, is that the
    telemetry they received said that users will roll-back in the first
    several days or not at all. In addition, by cutting the length of the
    roll-back period to ten days, this allows Windows 10 to remove the old
    files and clear up space on the hard drive.

    Winsupersite obtained the comment below from Microsoft regarding the change in the rollback period:

    Based on our user research, we noticed most users who choose to
    go back to a previous version of Windows do it within the first several
    days. As such, we changed the setting to 10 days to free storage space
    used by previous copies

    Thursday, August 4, 2016 8:09 PM
  • Susan

    I have uninstalled the connector ( is not an update anymore but is installed as an program).

    Installed the connector but at the final step after logging the connector cannot find the server.

    Extremely frustrating

    I have email you my Coordinates

    Thursday, August 4, 2016 8:45 PM
  • Count me in with the same problem on two machines.  Been on phone with MS technical support for 3 hrs.  Cant even get anyone to take time to understand the issue.

    ---

    EDIT: The tech on the phone said just now:  "This is a known issue and our engineers are working on it.  No date identified for a solutions.  The Workaround is to roll back."

    • Edited by Tefal Friday, August 5, 2016 5:06 AM
    Friday, August 5, 2016 5:02 AM
  • So here's what I think is going on.

    KB3172314 should be installed on the server.  Check.  All of you have indicated this has been done.

    The step I think is missing is that we should be uninstalling the OLD connector and installing this NEW one.  I think the NEW one survives the updating process. 

    No one anywhere has stated the exact process we're supposed to do to get this new connector installed.

    Friday, August 5, 2016 3:58 PM
  • https://support.microsoft.com/en-us/kb/3172614

    Includes this fix "Updated the inbox component in Windows Server 2012 R2 Essentials to use the new client connector, so that the inbox component won't get uninstalled during Windows 10 upgrades."

    Yay. 

    I can confirm that this update was installed on my Server 2012R2 Essentials system already. In fact, it was installed on July 28th. 

    However, on the one system that's gotten the anniversery update, the Connector software DID NOT SURVIVE THE UPDATE PROCESS.  I had to go, and re-download the connector software and reinstall it. 

    Additionally, the Tray Icon is DEFINITELY bugged. 

    I'm see a set of these errors for each time it's tried to load:

    [08/05/2016 09:35:39  b08] Failed to create tray icon. Error Code: -2147467259
    [08/05/2016 09:35:39  b08] TrayManager::Initialize ResetTrayIcon failed.
    [08/05/2016 09:35:39  b08] Failed to initialize tray icon.

    (this is from the EssentialsTrayIcon log file located in "C:\ProgramData\Microsoft\Windows Server\Logs" on the client). 


    [Insert snarky/a$$hole comment about everything working properly and being ready]

    Friday, August 5, 2016 5:09 PM
  • Can you look if the PRIOR essentials client code is still installed?
    Friday, August 5, 2016 5:15 PM
  • Not really sure how to tell.

    But I suspect that it wasn't there.  It looks like it was moved the Windows.old folder.  So definitely not retained.  I'll check on the next system that gets the update. 

    Friday, August 5, 2016 5:29 PM
  • Installed KB3172614 on Aug 4.  On Aug 6 updated clients to newest release.  Had to reinstall the Connector on all but one that had a Clean install of 1607.

    Kent

    Sunday, August 7, 2016 4:10 PM
  • Hi All,

    Please see the solution I gave for the problem where the Essentials notification area icon (EssentialsTrayApp.exe) is not appearing in the notification area posted over in the following thread:

    -- MIKE (The Office Maven)
    • Proposed as answer by TheOfficeMaven Wednesday, August 10, 2016 6:35 PM
    Wednesday, August 10, 2016 6:35 PM
  • One client Windows 10 Pro machine updated to 1607 before the server's KB3172614 patch. The only remnant of the connector left on the client was an empty Start menu entry.  Servername/connect (again prior to KB3172614) worked but took a very long time, probably because I'd forgotten to enter the registry option to skip domain which is how I run. On restart, it would freeze before the logon screen every time.  I restored the previous day's backup and successfully updated to 1607 (or Win 10.2 as Woody Leonhard puts it) with a working connector this way:

    1. Uninstalled Windows Server Essentials Connector and reinstalled using severname/connect after installing KB3172614 on the server. (On another machine, I've installed the new connector over the old one, but haven't put the Anniversary update on it yet so i don't know if uninstalling the old is a necessary step.) No connector tray icon, so I used the batch file for resetting notification area icons referenced above by MIKE TheTheOfficeMaven. Merged the skip domain join registry data.

    2. Installed the 1607 update and found the connector software still installed, including registry options, but the connector icon in the tray was grey, unconnected. The only way I could find to reconnect to server was to reinstall using servername/connect, after which everything worked okay.

    KB3172614 should have been issued the previous month as a critical update. And client computers should then have been prompted to reinstall the connector software on first connection. (I remember such a prompt on the client at some time in the past pre-Win 10, so i know that can be done.)  However,MS should have made the connector and the connection survive the update. I can't imagine the labor intensive effort needed to reconnect many clients every time there's a feature update.

    Thursday, August 11, 2016 6:49 PM
  • Mike?  May I blog all of your solutions and then recommend that the Essentials team blog it as well?

    Thanks in advance if it's okay with you.

    Thursday, August 11, 2016 7:18 PM
  • Hi Susan,

    You most certainly can. Please feel free to pass the information along however you see fit.

    Oh and BTW, thank you for all of the help you give to us Essentials folks (behind the scenes and otherwise).

    -- MIKE (The Office Maven)

    Thursday, August 11, 2016 7:50 PM
  • I;d rather see a blog saying a fix has been published, not a link to a workaround :)

    Grey

    Thursday, August 11, 2016 8:16 PM
    Moderator
  • Mick, I got your message but didn't see it here, so I replied to this post. Yep, I got it to work as well. I put it up on a test machine and it worked fine. Now I'm working my way through the other 6 machines with Windows 10 1511 to get them all to 1607.
    Thursday, August 11, 2016 8:56 PM
  • Just a slight deviation, but one cause of clients not connecting to server when connector software is working otherwise --

    I don't know how common this, but one or more of my machines can't connect to the server after a major Windows update because a timeout was reached (30000 milliseconds) while waiting for the NetTcpPortSharing service to connect, then the WseClientMonitorSvc service depends on the NetTcpPortSharing service, so both fail to start.  I believe this problem is related to file fragmentation and usually resolves after a few boots down the road, I guess when caching or prefetch becomes effective. (Oddly though, I've actually the problem precipitated by PerfectDisk boot time defrag.)  In the meantime, it can be fixed by using a greater timeout in the registry, such as 45,000 or 60,000 ms, then test drop back to 30,000 ms later.  I've got a reg file for each:

    ServicesPipeTimeout 60,000.reg --

    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control]
    "ServicesPipeTimeout"=dword:0000ea60

    ; Use to fix errors such as "A timeout was reached (30000 milliseconds) while waiting for the xxxxxx service to connect."
    ; Increase decimal by smallest amount above default 30,000 milliseconds that will prevent errors. 

    ServicesPipeTimeout 45,000.reg --

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control]
    "ServicesPipeTimeout"=dword:0000afc8

    ServicesPipeTimeout 30,000 Default.reg --

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control]
    "ServicesPipeTimeout"=dword:00007530

    Thursday, August 11, 2016 9:58 PM
  • Mick, I was good for a while, but now it's messed up again. I installed 1607 on all my machines with no issues. Now, according to the server attempting a backup, one of the machines fails. Server message says.

    Backup cannot connect to the Windows Server Essentials Client Computer Management Service on your computer. If this problem persists, you may be able to resolve the issue by restarting the client computer.

    I went into services and tried to start the Windows Server Essentials Client Computer Management Service manually and it failed with the log message as follows:

    Application: WseClientSvc.exe
    Framework Version: v4.0.30319
    Description: The application requested process termination through System.Environment.FailFast(string message).
    Message: Unhandled exception in OnStart: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.IO.DirectoryNotFoundException: The system cannot find the path specified. (Exception from HRESULT: 0x80070003)
       at TaskSchedulerV2.ITaskFolder.RegisterTaskDefinition(String Path, ITaskDefinition pDefinition, Int32 flags, Object UserId, Object password, _TASK_LOGON_TYPE LogonType, Object sddl)
       at Microsoft.WindowsServerSolutions.Common.ProviderFramework.SchedulerVersion2._saveV2Definition(String taskName, Boolean isUserContext, Boolean createNew, ITaskDefinition& taskDef)
       at Microsoft.WindowsServerSolutions.Common.ProviderFramework.SchedulerVersion2.RegisterTask(TaskDefinition definition)
       at Microsoft.WindowsServerSolutions.DataProtection.PCBackup.Provider.ScheduledTaskManager.UpdateScheduledTask(Boolean forceUpdate)
       at Microsoft.WindowsServerSolutions.DataProtection.PCBackup.Provider.ScheduledTaskManager.CheckCompliance(Boolean forceUpdateScheduledTask)
       at Microsoft.WindowsServerSolutions.DataProtection.PCBackup.Provider.ScheduledTaskManager.OnStart()
       at Microsoft.WindowsServerSolutions.DataProtection.PCBackup.Provider.PCBackupClientProviderImpl..ctor()
       --- End of inner exception stack trace ---
       at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
       at System.Reflection.RuntimeConstructorInfo.Invoke(BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
       at System.ServiceModel.Description.ServiceDescription.CreateImplementation(Type serviceType)
       at System.ServiceModel.Description.ServiceDescription.SetupSingleton(ServiceDescription serviceDescription, Object implementation, Boolean isWellKnown)
       at System.ServiceModel.Description.ServiceDescription.GetService(Type serviceType)
       at System.ServiceModel.ServiceHost.CreateDescription(IDictionary`2& implementedContracts)
       at System.ServiceModel.ServiceHostBase.InitializeDescription(UriSchemeKeyedCollection baseAddresses)
       at System.ServiceModel.ServiceHost..ctor(Type serviceType, Uri[] baseAddresses)
       at Microsoft.WindowsServerSolutions.Common.ProviderFramework.ProviderHost.<>c__DisplayClass2.<.ctor>b__0()
       at Microsoft.WindowsServerSolutions.Common.ProviderFramework.ProviderHost..ctor(Type providerType, String providerId, IList`1 serviceContractInterfaces, ProviderFrameworkConfigurator configurator)
       at Microsoft.WindowsServerSolutions.DataProtection.PCBackup.Provider.PCBackupClientWorkload.CreateProviderHosts()
       at Microsoft.WindowsServer.Essentials.WindowsService.WseServiceBase.CreateProviderHosts()
       at Microsoft.WindowsServerSolutions.Common.ProviderFramework.ProviderServiceBase._OpenHosts()
       at Microsoft.WindowsServer.Essentials.WindowsService.WseServiceBase.OnStartInner(String[] args)
       at Microsoft.WindowsServerSolutions.Common.ProviderFramework.ProviderServiceBase.OnStart(String[] args)
    Stack:
       at System.Environment.FailFast(System.String, System.Exception)
       at Microsoft.WindowsServerSolutions.Common.ProviderFramework.ProviderServiceBase.OnStart(System.String[])
       at System.ServiceProcess.ServiceBase.ServiceQueuedMainCallback(System.Object)
       at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
       at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
       at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
       at System.Threading.ThreadPoolWorkQueue.Dispatch()

    Well,  a restart didn't help. I tried uninstalling the connector software and reinstalling, but it fails during installation without any message. Just goes away.

    Any insight or suggestions?


    • Edited by Page Hite Tuesday, August 30, 2016 7:26 PM
    Tuesday, August 30, 2016 7:05 PM
  • IT IS MICROSOFT'S JOB TO TEST THEIR DAMN UPDATES



    22nd Century Tech Inc

    Wednesday, November 2, 2016 9:50 PM
  • Well its nothing to do with any previous install of the connector or lacking any updates for me- all fresh installs and updated as of 2 minutes ago.

    In the log its states that the connector software is not supported on this platform - i.e. the connector is out of date and therefore useless. The error you get from the install is misleading "package install did not succeed" rather than give a meaningful error message.

    [11/15/2016 21:54:04 1710] wmain: Start of Computerconnector
    [11/15/2016 21:54:04 1710] GlobalData::Initialize (192.168.1.80, C:\Users\TimSkull\Downloads\ComputerConnector(192.168.1.80).exe)
    [11/15/2016 21:54:04 1710] =================================
    [11/15/2016 21:54:04 1710] Current Os information:
    [11/15/2016 21:54:04 1710] Suite = [256]
    [11/15/2016 21:54:04 1710] Type = [1]
    [11/15/2016 21:54:04 1710] Architecture = [9]
    [11/15/2016 21:54:04 1710] IsStarterEdition = [0]
    [11/15/2016 21:54:04 1710] IsHomeSku = [0]
    [11/15/2016 21:54:04 1710] Major = [6]
    [11/15/2016 21:54:04 1710] Minor = [2]
    [11/15/2016 21:54:04 1710] Build = [9200]
    [11/15/2016 21:54:04 1710] SPMajor = [0]
    [11/15/2016 21:54:04 1710] SPMinor = [0]
    [11/15/2016 21:54:04 1710] =================================
    [11/15/2016 21:54:04 1710] ExpandEnvironmentStrings return (C:\WINDOWS\Temp\ClientDeploymentTempFiles\)
    [11/15/2016 21:54:04 1710] SetPackageDlcUrl: .NET url is set to http://go.microsoft.com/?linkid=9816306
    [11/15/2016 21:54:04 1710] SetPackageDlcUrl: Connector url is set to http://go.microsoft.com/fwlink/p/?LinkId=275100
    [11/15/2016 21:54:04 1710] wmain: Calling Computerconnector::ShowWizard()
    [11/15/2016 21:54:04 1710] CComputerconnector::ShowWizard: Initializing common controls
    [11/15/2016 21:54:04 1710] CComputerconnector::ShowWizard: Done initializing common controls
    [11/15/2016 21:54:04 1710] Displaying the wizard
    [11/15/2016 21:54:04 1710] CComputerconnector::WelcomeDlgProc: IDD_PROPPAGE_WELCOME Page Initialization
    [11/15/2016 21:54:04 1710] Current user default UI lang setting is 2057
    [11/15/2016 21:54:04 11c8] CComputerconnector::Run: Installation is ready to run
    [11/15/2016 21:54:07 1710] CComputerconnector::TaskDlgProc: IDD_PROPPAGE_TASKS Page Initialization
    [11/15/2016 21:54:07 2300] CComputerconnector::RunTasks: Running Task: Id=-1 Description=Detecting the current system requirements... Index=  0
    [11/15/2016 21:54:07 2300] CMsi::IsMsiInstalled: MsiQueryProductState for ProductCode {21E49794-7C13-4E84-8659-55BD378267D5} returned -1
    [11/15/2016 21:54:07 2300] CMsi::IsMsiInstalled: MsiQueryProductState for ProductCode {46DCED50-3A1D-4EF4-94F0-45F2681E3D70} returned -1
    [11/15/2016 21:54:07 2300] CMsi::IsMsiInstalled: MsiQueryProductState for ProductCode {C1E4D639-4A33-4314-809E-89BD0EF48522} returned -1
    [11/15/2016 21:54:07 2300] Connector installation state is 0
    [11/15/2016 21:54:07 2300] CComputerconnector::RunTasks: Running Task: Id=-1 Description=Downloading .NET Framework 4.5... Index=  1
    [11/15/2016 21:54:07 2300] CComputerconnector::RunTasks: Running Task: Id=-1 Description=Installing .NET Framework 4.5... Index=  2
    [11/15/2016 21:54:07 2300] CComputerconnector::RunTasks: Running Task: Id=-1 Description=Downloading the Connector... Index=  3
    [11/15/2016 21:54:07 2300] NetworkUtil::DownloadFromLocal(pData, Windows8-RT-KB2790621-x64.msu)
    [11/15/2016 21:54:07 2300] NetworkUtil::DownloadFromLocal: the package could not be found in current program location
    [11/15/2016 21:54:07 2300] NetworkUtil::DownloadFromServer(pData, Connect/default.aspx?Get=ClientCore.cab&os=Windows8-RT&amd64=1, ClientCore.cab)
    [11/15/2016 21:54:07 2300] NetworkUtil::DownloadFile(pData, Connect/default.aspx?Get=ClientCore.cab&os=Windows8-RT&amd64=1, C:\WINDOWS\Temp\ClientDeploymentTempFiles\ClientCore.cab, 443, HTTPS)
    [11/15/2016 21:54:07 2300] NetworkUtil::DownloadFile (https://192.168.1.80:443/Connect/default.aspx?Get=ClientCore.cab&os=Windows8-RT&amd64=1, C:\WINDOWS\Temp\ClientDeploymentTempFiles\ClientCore.cab)
    [11/15/2016 21:54:07 2300] NetworkUtil::DownloadFile - Create directory [C:\WINDOWS\Temp\ClientDeploymentTempFiles] if not exist.
    [11/15/2016 21:54:07 2300] NetworkUtil::_WinInetDownloadFile (https://192.168.1.80:443/Connect/default.aspx?Get=ClientCore.cab&os=Windows8-RT&amd64=1, C:\WINDOWS\Temp\ClientDeploymentTempFiles\ClientCore.cab)
    [11/15/2016 21:54:07 1710] CComputerconnector::TaskDlgProc: DIALOG_UPDATE: Running
    [11/15/2016 21:54:07 1710] CComputerconnector::TaskDlgProc: DIALOG_TASK_PROGRESS: Task Description: Detecting the current system requirements...
    [11/15/2016 21:54:07 1710] CComputerconnector::TaskDlgProc: DIALOG_TASK_PROGRESS: Task Description: Downloading .NET Framework 4.5...
    [11/15/2016 21:54:07 1710] CComputerconnector::TaskDlgProc: DIALOG_TASK_PROGRESS: Task Description: Installing .NET Framework 4.5...
    [11/15/2016 21:54:08 1710] CComputerconnector::TaskDlgProc: DIALOG_TASK_PROGRESS: Task Description: Downloading the Connector...
    [11/15/2016 21:54:08 2300] InternetOpenUrl (https://192.168.1.80:443/Connect/default.aspx?Get=ClientCore.cab&os=Windows8-RT&amd64=1) returns 12038
    [11/15/2016 21:54:08 2300] _WinInetDownloadFile returns 0x80072f06.
    [11/15/2016 21:54:08 2300] NetworkUtil::DownloadFromServer:DownloadFile(https://192.168.1.80:443, Connect/default.aspx?Get=ClientCore.cab&os=Windows8-RT&amd64=1, C:\WINDOWS\Temp\ClientDeploymentTempFiles\ClientCore.cab) failed with hr = 0x80072f06. Try http.
    [11/15/2016 21:54:08 2300] NetworkUtil::DownloadFile(pData, Connect/default.aspx?Get=ClientCore.cab&os=Windows8-RT&amd64=1, C:\WINDOWS\Temp\ClientDeploymentTempFiles\ClientCore.cab, 80, HTTP)
    [11/15/2016 21:54:08 2300] NetworkUtil::DownloadFile (http://192.168.1.80:80/Connect/default.aspx?Get=ClientCore.cab&os=Windows8-RT&amd64=1, C:\WINDOWS\Temp\ClientDeploymentTempFiles\ClientCore.cab)
    [11/15/2016 21:54:08 2300] NetworkUtil::DownloadFile - Create directory [C:\WINDOWS\Temp\ClientDeploymentTempFiles] if not exist.
    [11/15/2016 21:54:08 2300] NetworkUtil::_WinInetDownloadFile (http://192.168.1.80:80/Connect/default.aspx?Get=ClientCore.cab&os=Windows8-RT&amd64=1, C:\WINDOWS\Temp\ClientDeploymentTempFiles\ClientCore.cab)
    [11/15/2016 21:54:08 2300] Download from url: http://192.168.1.80:80/Connect/default.aspx?Get=ClientCore.cab&os=Windows8-RT&amd64=1 failed with HTTP error 404
    [11/15/2016 21:54:08 2300] _WinInetDownloadFile returns 0x8000ffff.
    [11/15/2016 21:54:08 2300] NetworkUtil::DownloadFromServer:DownloadFile(http://192.168.1.80:80, Connect/default.aspx?Get=ClientCore.cab&os=Windows8-RT&amd64=1, C:\WINDOWS\Temp\ClientDeploymentTempFiles\ClientCore.cab) failed with hr = 0x8000ffff.
    [11/15/2016 21:54:08 2300] NetworkUtil::DownloadFromDLC(pData, http://go.microsoft.com/fwlink/p/?LinkId=275100, Windows8-RT-KB2790621-x64.msu)
    [11/15/2016 21:54:08 2300] NetworkUtil::DownloadFile (http://go.microsoft.com/fwlink/p/?LinkId=275100, C:\WINDOWS\Temp\ClientDeploymentTempFiles\Windows8-RT-KB2790621-x64.msu)
    [11/15/2016 21:54:08 2300] NetworkUtil::DownloadFile - Create directory [C:\WINDOWS\Temp\ClientDeploymentTempFiles] if not exist.
    [11/15/2016 21:54:08 2300] NetworkUtil::_WinInetDownloadFile (http://go.microsoft.com/fwlink/p/?LinkId=275100, C:\WINDOWS\Temp\ClientDeploymentTempFiles\Windows8-RT-KB2790621-x64.msu)
    [11/15/2016 21:54:10 2300] CComputerconnector::RunTasks: Running Task: Id=-1 Description=Installing Windows Server Essentials Connector... Index=  4
    [11/15/2016 21:54:10 1710] CComputerconnector::TaskDlgProc: DIALOG_TASK_PROGRESS: Task Description: Installing Windows Server Essentials Connector...
    [11/15/2016 21:54:10 2300] Entering Connector::Install.
    [11/15/2016 21:54:10 2300] Connector::Install - Installing Connector by running ["C:\WINDOWS\system32\wusa.exe" "C:\WINDOWS\Temp\ClientDeploymentTempFiles\Windows8-RT-KB2790621-x64.msu" /quiet /norestart]
    [11/15/2016 21:54:10 2300] Connector::Install - Connector installation finished with exit code = 0x80240017
    [11/15/2016 21:54:10 2300] Exiting Connector::Install.
    [11/15/2016 21:54:10 2300] Connector Install (C:\WINDOWS\Temp\ClientDeploymentTempFiles\Windows8-RT-KB2790621-x64.msu) failed with status 4
    [11/15/2016 21:54:10 2300] CComputerconnector::RunTasks: Task Id=-1 Description=Installing Windows Server Essentials Connector... Failed
    [11/15/2016 21:54:10 2300] CComputerconnector::Run: RunTasks: 0x8000ffff
    [11/15/2016 21:54:10 1710] CComputerconnector::TaskDlgProc: DIALOG_UPDATE: FatalError

    The above is a sample of the error - get same if you run the win 10 version - above was done with compatibility mode on as a test.

    If you run the Win 10 KB2790621-x64 msu directly it states that "The update is not applicable to your computer" - so as i said useless as we are all supposed to update automatically!

    The 2012 r2 Essentials is a new install as well - it also is upto date as of 18.30 today - just adding a .net November Quality roll up update as i type - not hopeful thats going to help as it appears to be a client issue.

    I also added KB 3197875 earlier to the server but no change.

    Any insight would be good



    2 home servers plus vail test server 10tb storage combined

    Tuesday, November 15, 2016 10:10 PM
  • Hi Susan,

    Are there still problems using Windows 10 workstations on a 2012 /R2 Essentials server?  Given the outpouring of problems people on the forum have reported with Win 10 clients losing standard functions (connector, dashboard, etc.), we decided to delay upgrading workstations from Windows 7 to Windows 10.  We deal with small companies that simply don't have the IT knowledge to regenerate Win 10 connector features every time Windows 10 is upgraded.  Have these problems been rectified (is it safe now to go into the water?), or should we continue waiting?

    Thanks very much for your assistance with this.


    John

    Friday, November 18, 2016 10:47 PM
  • Now with the Anniversary Update 1607 being forced on users, you will find that if you have the connector installed it will be removed during the update process.

    This should be a sign to you that the connector and 1607 Windows 10 don't play nice.

    Like me you may find that you will attempt to re-install the connector after the 1607 Anniversary Update. Like me you may find it installs fine (as a Windows update) but getting it to connect and work is another story. If you are lucky enough to get the connector to connect after running the 2012 Server Configuration Wizard on the client computer you will find that the Dashboard does not see Windows 10 1607 as anything other than an Unknown Operating System. What does this mean for you? Well, don't expect backup to work, don't expect Group Policy to work, don't expect monitoring to work and so on and so on.

    I had previously reported this all to Microsoft and then uninstalled the Anniversary Update and clicked "defer upgrades" to find that now, some time later, I am being forced into Windows 10 1607. In an environment where the user needs the computer to work and work right, and right now this is unacceptable. Even without the connector installed and using good old manual input, Windows 1607 Credential Manager does not like to remember 2012 r2 Essentials credentials as well as a few other problems.

    Why has the connector been such a train wreck and continues to be so is beyond me. For my environment, I rely on it as I wear multiple hats from IT on down to client user and when things don't work correctly I spend too much time wearing the IT hat.

    Saturday, January 21, 2017 6:58 PM
  • I had a Win 10 Pro machine update to 1607 on Saturday, the connector didn't survive. When I attempted to reinstall it, it stopped with no error codes, just stopped and shut down.

    I made sure it was pointed to the server DNS, uninstalled and cleaned out all the files. Then re-installed, but it didn't do a full domain join. Still trouble shooting that.

    Sad that after all this time and effort, by a lot of people it still is a Royal Pain.


    RS

    Monday, January 23, 2017 10:41 PM
  • John,

    Thanks for taking the time to clearly state the issue(s) here.  I'm a small business consultant and ran into a shop today with about a dozen surface's running Win10 and essentials connector.  All dead in the water, no backups for months.

    It'll cost the client more than the essentials license (BY FAR!) for me to intervene and correct this problem - until Creator's edition comes around and borks the entire mess all over again.

    I am flabbergasted.  This is horrible - I am now officially "DONE" with Windows 10.  I'm also "DONE" with server essentials.  Veeam free endpoint backup, here we come.

    What a nightmare.  Totally unacceptable.


    Scott.

    Friday, January 27, 2017 12:45 AM
  • I too have been having mega-hassle with the "Connect" applet.

    Clean Essentials2012R2 install, clean Win10Pro desktop installs. Running applet from <a href="http:///connect">http://<svr>/connect just threw "Wizard can't install" errors, downloaded WSEClient package installer and had similar errors running that.

    A dig around with file explorer showed the package installed in \program files\server\bin, ran ClientDeploy from there and - finally!! - managed to get it to complete successfully, client shows in devices in server dashboard and client has system tray icon displayed and can open Launchpad from there.

    It has been a massive palaver to get this far, and has consumed far too much time!! (fwiw, I'm not a newbie to this, been working with MS server products since NT3.5 and plenty of experience with SBS2000 thru 2011)

    I'm totally in agreement with everyone else's aggrieved responses above, this is NOT an acceptable situation for a flagship product!!

    Tuesday, April 18, 2017 11:49 AM
  • Interesting that we still have this issue with v.1703 & v1709. On some of our client sites we find running the Essentials Connector App reconnects the workstations. On other sites the Browser Connector reconnects after the Version updates. Some workstations have to be disjoined from the Domain & all Connector software removed before they can reconnect. We can't attribute the difference to x32 vs. x64 versions of Windows 10.

    It seems likely the issue is how Windows 10 treats installed Applications during version upgrades. Without the Win 10 team's cooperation, the Connector is disabled / removed / broken.

    A shame the technical abilities & internal negotiation skills of the old Redmond SBS team aren't available to solve this. The Essentials team in China has not stepped up with a solution. Now that mid-size organizations are using the Connector Role, even more resources are wasted twice a year.


    Rod Cederblom

    Friday, February 9, 2018 10:15 AM
  • It might be time to pursue a class action lawsuit to recover IT service company time expenses and customers monetary costs. Let the court decide if Microsoft did the proper due diligence. It sure seems like they didn't.

    5280

    Friday, February 16, 2018 1:49 PM
  • If you use computer management to connect to an offending client (that is on, but showing off-line in the console), go to services, look at the 5 Windows Server Essentials services. They are set to manual start, and are likely not running.

    If you start them, the console shows 'online'.

    I'm not proposing this as a fix, just an observation that *might* get us closer to a resolution.

    Yes, it's a shame that this is being ignored by those that takes our money ;-/.


    MVP-SBS 2001-2011 (retired)

    Sunday, February 18, 2018 3:55 PM