Can't update components on Windows 7 64.

Hyper-V specific discussions

Can't update components on Windows 7 64.

Veeam Logoby dan.hoffman » Mon Oct 15, 2012 11:04 pm

OK. I made sure I CAN access the Admin$ share on the target repository, but update will not install on that workstation.
My other targets are all 2008 R2 server and work fine. This Win 7 pro 64 box was working properly for a long time. Then I updated to 6.1 and the update ran fine for all repositories and hosts other than this one. I can access the Admin$ share through explorer using the same credentials I use in Veeam. But, Veeam still reports an error when trying to connect to this Win 7 repository to do the update.
Firewall is off, using Symantec endpoint security with exceptions added for all veeam .exe and .dll in the windows/veeam folder.
When trying to discover the target's components it errors: failed to install deployment service. there are currently no logon servers available to service the logon request.
tr: failed to create persisent connection to ADMIN$ shared folder on host [xxx.xxx.xxx.xxx]

Veeam services are all running on target. RPC is also running.

Any ideas?
dan.hoffman
Novice
 
Posts: 7
Liked: never
Joined: Fri Feb 24, 2012 10:50 pm
Full Name: Dan Hoffman

Re: Can't update components on Windows 7 64.

Veeam Logoby Gostev » Mon Oct 15, 2012 11:06 pm

Hi Dan, please include support case ID when posting about any technical issues, otherwise your post will be removed, as explained when you click New Topic. Thanks!
Gostev
Veeam Software
 
Posts: 21390
Liked: 2349 times
Joined: Sun Jan 01, 2006 1:01 am
Location: Baar, Switzerland

Re: Can't update components on Windows 7 64.

Veeam Logoby dan.hoffman » Mon Oct 15, 2012 11:29 pm

OK. Not hit support yet with this. Kill it. If I can't get this addressed there, I will post here. Kind of redundant though.
dan.hoffman
Novice
 
Posts: 7
Liked: never
Joined: Fri Feb 24, 2012 10:50 pm
Full Name: Dan Hoffman

Re: Can't update components on Windows 7 64.

Veeam Logoby Gostev » Mon Oct 15, 2012 11:38 pm

Naturally, it would be best to keep the thread, but include the support case ID for it. This way, in case if future readers have the same problem, we will be able to look up the support case if you never come back to post the resolution (which is what 9 out of 10 posters do). BTW, it takes less than a minute to open a support case and receive the case ID. Thank you!
Gostev
Veeam Software
 
Posts: 21390
Liked: 2349 times
Joined: Sun Jan 01, 2006 1:01 am
Location: Baar, Switzerland


Return to Microsoft Hyper-V



Who is online

Users browsing this forum: No registered users and 7 guests