I have been adding new Hyper-V hosts into Veeam recently, where the hosts for some reason have been left on a WORKGROUP. This reuqires us to use a local administrator account, and quite often throws an error saying it "Failed to create persistent connection to ADMIN$".
This is luckily a very easy fix and can be sorted out within a couple of minutes by adding a registry DWOROD.
Navigate to the following:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
Create a DWORD value called LocalAccountTokenFilterPolicy and assign it a value of 1.
Once you've done this, you can add the Hyper-V host to Veeam and it will work perfectly!
Showing posts with label Veeam. Show all posts
Showing posts with label Veeam. Show all posts
07 September 2017
Veeam for Office 365 | Invalid Exchange Server version
Recently I noticed that clients of mine who were using Veeam for Office 365 started having issues with the product backing up their emails.
After looking into this, it looks as if Microsoft have updated their Exchange backend version without telling anyone, which has caused this issue. Whilst there's no update available through Veeam at the moment, logging a support case with them provided me with a fix to get this up and running.
The error message in question here states "Invalid Exchange Server version". This starts to fail for most mailboxes, and will eventually fail for all mailboxes. Obviously this is a P1 issue, as you don't have backups up and running.
The fix is only available if you're running version 1.0.0.912, and is the following:
After looking into this, it looks as if Microsoft have updated their Exchange backend version without telling anyone, which has caused this issue. Whilst there's no update available through Veeam at the moment, logging a support case with them provided me with a fix to get this up and running.
The error message in question here states "Invalid Exchange Server version". This starts to fail for most mailboxes, and will eventually fail for all mailboxes. Obviously this is a P1 issue, as you don't have backups up and running.
The fix is only available if you're running version 1.0.0.912, and is the following:
Download the hostfix file from https://storage.veeam.com/Fix_113114_fbcf2c440c.zip and follow the instruction to apply
the hot fix.
The workflow:
- Stop all the jobs
- Stop “Veeam Backup for Microsoft Office 365 Service”
- Rename and replace Veeam.Ews.dll with the DLL from the archive in C:\Program Files\Veeam\Backup365 (don't forget to back up the original DLL)
- Start “Veeam Backup for Microsoft Office 365 Service”
- Retry the job
After performing this fix, it has 100% resolved the issue for my clients.
Subscribe to:
Posts (Atom)