“…the Windows Server Essentials Connector software is sourced and delivered directly from the Essentials server itself…”

Hm, interesting to hear you say that. My experience has been otherwise.

Yes, the initial connection to and download from occurs with the local server, but during Setup the installer goes out and downloads some bits from the Dark Side.

I’ve been able to confirm this behavior (repeatedly) by noting the steady and prolonged network activity in Task Manager, activity that exactly equates to my bandwidth speed cap, and that persists for roughly 30-60 seconds.

If the installer were downloading those bits from the local server, the download would be nearly instant and I’d have seen a mere blip on the 1Gbps radar.

I’ve also tried running the installer with the Internet gateway turned off, and with my previously-archived bits in place, and Setup has failed (message something like “couldn’t access necessary components” or some such thing).

Again, this is in my experience.

“…Microsoft will no longer be supporting any of the Essentials bits after that.”

Actually, according to Mariette Knap over at http://www.Server-Essentials.com, Microsoft refuses to support the WSE bits even today, if they’re installed on top of anything that they didn’t ship with (Server 2019, 2022, etc.). But that’s not the point—for my part at least, I don’t care whether they support it or not. Or whether it’s long in the tooth or not. It’s near-bulletproof and it works as is.

The point is the beautiful simplicity in server management that WSEE brings to the table. I tried my hand at WAC and found myself pulling at the small amount of hair I have left within mere minutes.

Naturally I’ll be adopting the underlying server OSs as they release, so that part’s not a problem.

I’ve just gone and fallen in love with the Essentials Experience, that’s all :- )

So the problem remains—what to do about that awful day when the Connector installer won’t be able to download those necessary bits?

It’s been quite a while since I’ve looked at that part of the Essentials source code, but as far as I remember, the client connector installer program is indeed pulled across the LAN/WAN from the Essentials server, and is not downloaded directly from Microsoft’s servers. If you use http://YourServerName/connect to retrieve the client connector, then it would come across the local network (just like the /connect webpage that you’re being served up does), and if you use something like https://remote.YourDomainName.remotewebaccess.com/connect, then it would come across the Internet (again, just like the /connect webpage that you’re being served up does). The file that you’re being served up (ComputerConnector.exe) comes from the Essentials server located at “C:\Program Files (x86)\Windows Server\Bin\WebApps\Client\Package(2)”. Again, that’s how the source code works unless Microsoft has changed something in it since the last time I looked at it (years ago now). I suppose that you could always compare the digital signature on the file to see if you’re getting the same one (or better yet, just replace the local file with a dummy file of the same name and see if the dummy file gets delivered to you from the /connect webpage instead).

Obviously, Microsoft would never support installing the Essentials bits from Windows Server 2016 onto Windows Server 2019/2022 (and so Mariette is indeed correct there), but they should still fully support the Essentials bits over on 2016 itself until 1/12/2027. And if Microsoft ever updates/changes any of those bits, I’ll deliver them to 2019/2022 via my WSEE Updater program (hence you’d still receive the updates of those “supported” bits). However, after 1/12/2027, Microsoft most likely won’t ever update any of the Essentials bits even under 2016. That being said… I think Microsoft gave up on Essentials a long time ago and has no plans on updating/fixing anything it in ever again (unless some catastrophe forces them to do so that is). According to my records, Microsoft hasn’t updated/changed any of the Essentials bits since way back in January of 2021 when OS Build 14393.4169 was released.

With all of that said… I personally wouldn’t plan on continuing to use the Essentials bits (be it under 2016, 2019, 2022, etc.) after 1/12/2027, but that’s just me. I assume that the client connector will continue to work just fine until then. After that, you can always just grab it straight from the server and copy it over to your clients if I am wrong on the delivery mechanism (which I don’t think I am ;- ) ).

“…if I am wrong on the delivery mechanism…”

Try it out, you’ll see what I mean :- )

Yes, the first part does indeed download from the server, LAN-only. But after about the second screen or so, ComputerConnector.exe starts pulling down files from some destination across the Internet. (In hindsight, I suppose I could’ve used Fiddler to get at that info.)

If you’re running a fast connection from your ISP you likely wouldn’t notice it, but at the time we had a max 2 Mbps. It really showed up then.

And like I said… I tried a few different approaches, e.g. getting the process run location and archiving those files for the next time out. But ultimately nothing worked except letting the installer take the time to download what it needed from Microsoft. That was a real PITA with a slow connection and many workstations (which is what inspired my efforts to make it all local in the first place).

Give it a spin when you get a chance—I’m confident you’ll be able to reproduce this behavior.

Righto, it’s after ComputerConnector.exe runs. Thanks for having a look at it.

Would that we even make it to 2027 ;- )

@billd

> however there’s a workaround if for some reason the download fails

Good sleuthing! We can use this.

I believe you’re correct on the ‘Not Supported’ question. I ran into the same thing under the exact same circumstances.

@build

Nice sleuthing indeed! Appreciate you chiming in on this one.

Although it may well have all been for not seeing as you can actually download all iterations of the Windows Server Essentials Connector software (i.e. Mac, Windows 7, 8.x, and 10+) directly from Microsoft over here:

Windows Server Essentials Connector

Might be a good idea for folks to grab them all as a “just in case”. ;- )

BTW, it appears that the ComputerConnector.exe program that’s downloaded from the Essentials server merely evaluates the client computer’s specs and then reaches out to Microsoft’s servers and grabs the appropriate iteration of the client connector MSI file. Lastly, it doesn’t look like Microsoft has changed/updated any of the client connector MSI files since 2016 (although I’m unsure if Windows Update updates any of the files once the client connector software has been installed onto the client).

Get Connected in Windows Server Essentials

FYI:

PS S:\Setup\WSE 2016> Get-FileHash .\WSEClient-x64.msi
SHA256
14EB793F4A74507AB39C77F2ACD1DCCF7E6BEA4F3819E40809E71B687558139F

PS S:\Setup\WSE 2016\Connector Installers> Get-FileHash .\WSEClient-x64.msi
SHA256
14EB793F4A74507AB39C77F2ACD1DCCF7E6BEA4F3819E40809E71B687558139F

So this one and the one from the previous download link are the same.

I found this thread while doing some research. My current Windows backup/restore solution is WSE2016 on a Dell T340. And using the WSEE is a very nice facility and one which was easy to transition to from Windows Home Server.

The research is primarily to find the next generation of on premise backup/restore solution for my Windows systems. One possible scenario is to get a newer generation Dell server with it provisioned with WS2025 Essentials and to acquire from Office Maven the WSEE in order to continue using the client backup/restore facility.

But reading this thread casts a lot of doubt. My expectation is that whatever solution I find to replace my existing setup would last for 5 years, give or take. After WS(E)2016 reaches EOL, if WSEE and the connector might go belly up then it seems like a repeat of the experience when the WHS connector was broken about 2 years ago.

Am I off base with my concerns about the viability of WSEE and the connector? Like another poster said, WSEE is great b/c it just works.

Mike, thanks for the detailed response. It does help. And the item about the .NET V4 dependency is also appreciated — up until now I was blissfully ignorant of that little tidbit. And I guess if MSFT has not seen fit to revisit the connector by using current versions of .NET then it just underscores your recommendation.

Now I guess any hope that something might save me from things LINUX I can see it is now time to embrace it.