Windows Server 2016 + VEP 1.5 ?

[AlexLeadingEdge]

We are about to roll out Windows Server 2016 for a client and we need to know if Veeam Endpoint 1.5 is compatible with a Windows Server 2016 domain. Has anyone looked at this aspect while we are waiting for Veeam Endpoint 2.0?

[PTide]

Hi,

There should be no issues with Endpoint in 2016 domain though it has not been fully tested. The only problem with 2016 is that you cannot install Endpoint on Windows 2016 without tweaking.

Thank you.

[Vitaliy S.]

Yes, if you want to have a fully supported solution, then you need to wait for version 2 (or an update from our dev team).

[Blacky]

Hi,
I would like to install VEB 1.5.306 on a Server 2016 but the installation failed.
When will an update be available?
Best regards

[Vitaliy S.]

The GA of the next version of Veeam Agent for Windows is scheduled to the next year.

[mkaec]

Oh, no! Upgrading our systems to Server 2016 was supposed to be our Christmas present!

What happens if VEB 1.5 is already installed on a 2012 R2 server and it is upgraded to 2016?

[Vitaliy S.]

I don't know whether this scenario was tested or not, but VEB might still work though it will be unsupported by our technical team.

[Dima P.]

Guys,

Official support from Windows Server 2016 comes with Veeam Agent for Windows 2.0 Meanwhile, feel free to install current version in your test environment and let us know the results.

[Gostev]

The GA of the next version of Veeam Agent for Windows is scheduled to the next year.

That said, we will have public beta before the end of this year.

Oh, no! Upgrading our systems to Server 2016 was supposed to be our Christmas present!

Are you sure this is a good idea? I mean, there's no better way to spoil yourself a festive season than getting into major upgrades just before one

[dellock6]

I still remember at a bank I was consulting years ago, December was called "frozen zone": because of the end of years calcs that needed to be done and all other operations, NO change to the environment was allowed other than security patches and only for some exposed systems, for everything else only daily activities were allowed.

[mkaec]

Are you sure this is a good idea? I mean, there's no better way to spoil yourself a festive season than getting into major upgrades just before one

On the flip side, it's easier to tell a user complaining about maintenance downtime to go spend time with his or her family.

[mkaec]

For us, our "frozen zone" tends to be January through April. Between the accountants handling year end and the tax guys getting ready for tax filing, some of our users keep odd hours during this time, making it difficult to schedule maintenance windows. We've gotten complaints, in the past, about maintenance that was running at 4:00 AM.

[togenshi]

Any caveats with Window Server 2016 internal alpha/beta so far? I'm guessing containers, ReFS and nano server features could make headache or two. I think an update on the RE environment will be needed as well?

Could there be a nice msi package this time?

[Vitaliy S.]

Yes, there are some things that are not supported in the current release. We will have a public beta of v2 soon, so you could start using it/testing it with Windows Server 2016.

[Dima P.]

I think an update on the RE environment will be needed as well?

Every major release requires update of Veeam Recovery Media. Same story with upcoming version

Could there be a nice msi package this time?

There is a non-supported hack to extract the components from the setup file and manually install them one by one. You can use it to test VEB 1.5 with Windows 2016 but as I said before, use it for testing purpose only.

[M4ximus]

Hello,

this is my first post in this forum. I hope to get some help with my issue.

I got a VMware ESXi Host running two identical VMs (SRV01 and SRV02) with Windows Server 2016 Standard OS version. (I know Endpoint is not yet released for Server 2016)

Both server have the same patchlevel and features (not roles!).

While Veeam Endpoint runs perfectly on SRV01 the installer quits on SRV02 after starting it with the following message:

Current operating system is not supported or lacks the required service pack. See system requirements for more information".

The only difference between those system is the installed software.
If you have any idea how to get the Veeam Endpoint running on this machine it would be very lucky.


Kind regards!

[Dima P.]

Hi M4ximus,

I assume that setup blocker checks the build version of the Windows Server, so consider this behavior as a bug. If you are still willing to install VEB 1.5 for testing purpose – extract the installer and setup all the components manually. Keep in mind that this scenario is not supported.

[M4ximus]

Thank you for your replay.

Meanwhile I found the "tweak" for the installation and I am not willing to do this I guess.

But it is strange because the two system are equal. The first installation finished without any issue.

Kind regards.

[Dima P.]

Can you share the Windows 2016 build number please?

[M4ximus]

Both servers run Windows Server 2016 Version 1607 (Build 14393.447).

Kind regards!

[Dima P.]

Maximus,

Thanks for your help! I'll pass this information to our dev team.

[M4ximus]

Thanks for your ultra quick reply

EDIT:
Now I "tweaked" the installer with the "7-Zip-method" and got it working now.

I unpacked the components and ran the installer one after the other and without any compatibility isuess all components are installed and the software is running now.

I am very happy with that and especially with the support forum here