Invalid Exchange Server version using Veeam Backup for Microsoft Office 365 #updated #withSolution

Update: After contacting Veeam support they attended me that there is a private fix voor version 912.

  • stop all jobs
  • stop “Veeam Backup for Microsoft Office 365 Service”
  • replace Veeam.Ews with the DLL from the archive https://storage.veeam.com/Fix_113114_fbcf2c440c.zip 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

veeam_o365_error_working

As you can see the problem is solved and I’m able to backup Office 365 again!


People (including me :-))  are reporting problems using Veeam Backup for Microsoft Office 365. It seems that Microsoft made some kind of change on their back-end. At this time Veeam reports that they are looking into the problem..

I’m running Version 1.0.0.912…. a newer version isn’t available on the general download site. So upgrading the Veeam software isn’t the solution for now.

veeam_o365_error_version

Don’t seem to be (Windows) update related. Before and after updating my test server I receive the same error. 🙁

veeam_o365_error

When there is a solution I shall mention this in this blogpost.


How to fix VM guest only showing 1/4th of the console window

I’ve noticed that when I’m running on some (high resolution) laptops I’m unable to see the whole console screen of a VM guest. Connecting those laptops to a docking resolves the problem.

As you can see in the following example you don’t see only a quarter of the console session :

vm_notshowing_example

After some investigation I found the solution. Open the shortcut of the VMware Client and open the properties. Enable the disable display scaling option.

vm_notshowing_solution

Make sure you save the settings and try again.

vm_notshowing_fixed

As you can see in the above example, the whole screen is displayed!


How to configure PXE booting using PfSense

For some testing in my lab environment I needed PXE boot to work. This is how I configured PfSense to support PXE boot. In this scenario I wanted some Windows and Linux devices to boot to an imaging environment. For the Windows devices I needed option 66 en 67 but somehow when I specified those settings in PfSense I didn’t got it to work. The solution was very simple :

Log on to the Webinterface of PfSense, go to services/dhcp server.

Specify the following options :

  • IP Address of TFTP server
  • Enable network booting yes
  • Next Server (= IP Address of TFTP server)
  • Default Bios file name (= filename of legacy of UEFI bootfile name, in my case undionly.kpxe)

pfsense_pxeboot

Save these settings and you’re all set! You don’t have to specify the 66 and 67 settings!


How to fix non booting laptops hanging at HP logo 2

While working on a large deployment project I noticed a strange behaviour with HP laptops. After deploying some laptops didn’t pass the HP logo. Nothing happend.

hp_bootlogo

After searching the internet and contacting HP (no solution) the solution came through (by mistake :-))

When you see the above hp logo and your laptop doesn’t start through…. press the up (no keypad) or the 8 (with the up arrow) and voila!

HP_8arrowup

After pressing the up arrow the problem is solved. 🙂


Troubleshooting KACE 1000 client issues

I recently ran into some issues with installing the KACE 1000 client. KACE 1000 is the KACE Systems Management Appliance from Quest software.

In this example I want to push the agent to a specific client and that fails.

Check the logging

First step is to check the logging. Go to settings, Provisioning, Provisioning results. There you find the logging of the deployment tasks.

k1000_provisionerror

When you want more information you can easily click the specific task and see more details :

k1000_provisioninglog

Try installing the agent manually

You can save youreself a lot of time troubleshooting the issue when you try to install the agent manually. This way you can quickly troubleshoot the problem and often (when you have multiple clients with problems) the solution you’re going to find is also the answer for your other clients.

Go to the machine you want to install the client on. Open File Explorer and browse to the following directory:

kace1000_clientlocation.png

In my example I want to install the client on a Windows device. (There are also Linux and Mac clients)

Use the agent_msi_provision script to manually install the K1000 client. The script automatically tries to detect the K1000 server. Sometimes (due to DNS problems for example) it fails to determine the K1000 server. You can use the command line option %1 for specifying the K1000 server. So use the following command agent_msi_provision 192.168.1.41 In my example the IP address of the K1000 in the demo environment has the .41 IP Address

Wait a minute and check in the Devices windows of the K1000 for the specific client.

Check network connectivity

When that doesn’t work (the first step often doesn’t :-)) check the network connectivity. Can you ping the client <> K1000? Are the right firewall rules in place? You can decide to temporary disable the firewall (and after adding it to K1000 use the K1000 options to enable the firewall again). I don’t encourage disabling firewalls, so use this tip only for troubleshooting.

net stop wuauserv
sc config wuauserv start=disabled (to keep it disabled after a reboot)

Turn on Network discovery and turn on file and printer sharing.

k1000_networkdetection

Check sharing and security settings

The installer uses the default ADMIN$ share to connect to the client to install the software. Go to the client and browse to the \\clientname\ADMIN$ share. Can you see the files using the account you specified in the K1000 provisioning task? No? Check if the shares are available.

k1000_adminshares

User account control (UAC) must be configured in one of two ways: Turn UAC off or set user account control: run all administrators in admin approval mode to enabled.

Ofcourse the specified user in the provisioning job has to exist and has local administrator rights.

Install the client using winrm method

I found installing using the winrm service to be a quick fix for me. You can easily enable that on the provisioning task :

k1000_enablewinrm

For this to work, the winrm service has to be enabled and running :

k1000_winrmservice

Wrap up

So in a nutshell :

  1. Check the logging
  2. Try troubleshooting installing the K1000 using manually install
  3. Appropiate account? (UAC disabled?)
  4. Check network connectivity (DNS/Firewall/same domain?)
  5. Fall back to WinRm method

 

 


New Features in the Upcoming NAKIVO v7.2

Some information from my sponsor Nakivo.

Nakivo v7.2 is on his way. Register for v7.2 Beta now!  All Beta program participants who fulfill the Beta program requirements will receive a gift card.

A list of new features that we be added in the upcoming v7.2 :

  • Asustor NAS Support: Install NAKIVO Backup & Replication on an Asustor NAS to create a high-performance VM backup appliance that combines backup software, backup hardware, backup storage, and data deduplication in a single cost-effective device.
  • Log Truncation for Microsoft SQL: Automatically delete SQL transaction log files that could otherwise fill up all the free space and crash the entire server.
  • Instant Object Recovery to Source for Microsoft SQL: Recover Microsoft SQL Server objects, such as databases and tables, directly to the source SQL server, a different SQL server, or export objects to a custom location.
  • Calendar Dashboard: View all jobs and their predicted duration in a calendar dashboard (much like meetings in a calendar application), as well as create new and manage existing jobs.
  • Flexible Job Scheduling: Add multiple schedules to a single job. This way, it will be possible to schedule a single job to run at different times, as required by the business needs.

Nakivo beta

I’m also testing the v7.2 and shall blog about this on vWorld.nl!


How to Add an extra email address to your O365 mailbox the right way

This blogpost describes how to add an extra email address on your O365 mailbox. Someone told me that when he tries to add an extra email address using the Office 365 admin partner he receives the following error :

o365_mailbox_address1

The error says that this action (adding an extra email address) should be performed on the object in your on-premises organization. This means that your Active Directory is connected to Azure (O365). So extra email address should be added on the specific user properties and not directly using the Exchange admin interface. Your changes are automatically replicated to Azure.

Go to your domain controller and open dsa.msc (Active Directory Users and Computers) and go to the user you wish to provide an extra email address. Important : don’t search for this specific user, this way you don’t see all the properties later on. Also make sure that you have the advanced view enabled in dsa.msc, otherwise you won’t see the Attribute editor tab.

o365_mailbox_address2

Open the properties of the specific user and select Attribute Editor and go to ProxyAddresses. Now you have the option to add an extra emailaddress, use the following Value : smtp:user@email.nl

Make sure that the @email.nl domain is registred correctly in O365.

(Thanks to Roelf Z for the comment)

 


Solved: No Attribute Editor option within ADUC

I received a question why the Attrib Editor option didn’t show up in Active Directory Users & Computers. See the picture below.

attrib1

This is well known issue (by design). When you search for a user there is no Attrib Editor option. Instead go to the specific OU and open the properties from that specific user.

attrib2

Notice the Attrib Editor is now showing up!


Webinar: How to Migrate to VMware for Hyper-V administrators

If you’re a IT Pro who started with Hyper-V but find yourself in a situation where you need to migrate to a VMware platform, this is the perfect webinar to get up to speed.

My sponsor Altaro is hosting a webinar, tuesday June 27th 2017.

More information here

altaro_webinar


Nakivo backup appliance now also for QNAP NAS

I’m using the Nakivo backup appliance on my Synology NAS for some time now. I’m quite happy with I thought it would be nice when there became support for QNAP. I have a high end QNAP NAS with more performance then my Synology devices, so it would be nice if I could use the extra performance and disk capacity. Now it’s possible!

Nakivo_qnap

Nakivo released their appliance now with support for QNAP! Using their appliance could save you a lot of time, because the appliance writes directly to the disks in doesn’t rely on networkprotocols such as NFS and CIFS. You should notice that with your backup times!

The reason I think using a NAS device for backup is that you just buy a nice enough NAS and you’re ready to go. You don’t have to use servers, virtualization software, antivirus software, management tooling etc. Just one box, place it whereover you like and off you go! Another point to keep in mind, you’re backup VM in on the same host as the server(s) which are down? Now you don’t have to reinstall or restore that server. It saves you time!

Installation of the QNAP package is very simple. Just login to your QNAP and open the AppCenter. Go to Backup/Sync and notice the NAKIVO package. Just click on it to install. You don’t have to manually download&upload the file or something like that. The program itself has the same look and feel.