Cannot update host agent

[4c7]

I've just installed 8.0.0.2029
And I cannot update one of my Hyper-V host. It says access denied. However the accounts I've tried all have local admin rights (I've tried both domain and local accounts). I can access Admin$ share just fine with all the accounts from the Veeam server (using IP, NETBIOS name or FQDN). Firewall's are off. So I have this question. What is going on right here?
I've also rebooted Hyper-V host and Veeam Server. No luck.

ps. Is there a way to manually install Veeam Package?
pps. Is there a DSC resource for that?

[veremin]

You might want to install required packages manually and see whether it helps. The packages are the following: VeeamTransport.msi, VeeamHvIntegration.msi (those can be found in the directory VB&R is installed on; \Backup\Packages). Thanks.

[4c7]

Well this is weird. So the story goes like this.
I've rebuild this server a few weeks ago. And I forgot to re-add Veeam Service Account to local administrators group. Somehow everything was working fine, now after the update (which it won't let me do with the accounts that had local admin rights, I had to login locally on hyper-v host with the same account), Veeam recognizes the server, but says it's unavailable, even thou Veeam can get all the information it needs from the Host.

[foggy]

If you're able to install required components but the server is still not recognized, please contact technical support to investigate the reasons of this behavior.

[4c7]

Could you kindly guide me how to do that?

[veremin]

Copy the mentioned packages to required server, and install them manually.

As to support case, it can be opened and required logs can be attached by going to the following site:

http://cp.veeam.com/

Thanks.

[4c7]

I'm struggling to choose which support case should I open (on the "Add attachments to your case" page)

[foggy]

You can select "Installation issue".

[4c7]

So after a few restarts this started working. go figure.

[veremin]

Might have been some intermittent issue. In case it re-occurs, reach our support team directly. Thanks.