Last week Veeam released the latest version of the Veeam Availability Suite v9. Over the course of the next few weeks I’ll be looking at some of the new features included in the latest release, and to kick off I’ll take a look at the Standalone console.
Veeam have added many ground breaking features to the product; Scale-out Backup Repository, Bitlooker, EMC Snapshot integration, Direct NFS Access, ROBO enhancements, Tape enhancements, Veeam Explorer for Oracle, Cloud Connect Replication, and Standalone console to name just a few of them.
But after upgrading our Veeam Cloud Connect infrastructure the first thing I tried was the Standalone console. If you are a Managed Service Provider or Value Added Reseller, then the convenience of being able to launch a local Veeam Backup & Replication console from your desktop to connect to a remote Backup & Replication server will save so much time if you have to manage a large number of clients backup infrastructures. Continue reading
In this post I’ll look at how to delete the Hiberfil.sys file from your computer.
If you are reading this then you are probably trying to free up some diskspace on C:\ and have noticed you have a large file called Hiberfil.sys.
The Hiberfil.sys file is a file that Windows uses to write the contents of memory to when you ask your computer to Hibernate. The more memory you have in your computer the larger the Hiberfil.sys file is likely to be. Continue reading
I had a disk failure in a Dell PowerEdge R710 server recently and as the server itself is due to be decomissioned soon and we have a few spare HDDs available of the correct type, we decided to use one of them.
If the replacement HDD was blank or new then doing a simple swap out would start the array rebuilding, but because the disk I used had come from another server it already had some raid configuration data on it. So in this post I’ll look at how to clear the foreign configuration from a replacement HDD.
In this post I’ll look at how to configure a postmaster address for our Exchange Organisation.
The postmaster address is used for non-delivery reports (NDRs) sent to recipients outside of your Exchange Organisation and is specified in RFC 2821.
In Exchange 2013 the external postmaster address is blank by default. This has the effect of the external postmaster address being postmaster@YourDefaultAcceptedDomain.
It can be useful to create a postmaster mailbox, or assign the email address to an admin mailbox so that recipients can reply to NDR messages for assistance. Anyone who is familiar with NDRs will appreciate they are far more useful to admins than they are to end users! The downside of this though is as it’s a well known address it can be open to abuse and spam.
I’ve got a few Exchange 2013 installations in production now so I thought it was about time I wrote a post on best practices when installing Exchange 2013 Cumulative Updates and Service Packs.
Each Cumulative update is a version of Exchange in it own right. Therefore if you are installing a new deployment of Exchange you can install straight from latest Cumulative Update, which at the time of writing is CU11 (released December 2015). KB3099522 contains a list of fixes and enhancement for CU11.
This also means that once installed you cannot uninstall a Cumulative Update, if you do you uninstall Exchange.
The update is approximately 1.6GB in size and can be downloaded from here.
In my test lab with a single Exchange server and single Domain Controller the update took an 60 minutes to install.
The official Exchange Team blog post can be found here.
On 15th December Microsoft released the Exchange 2010 SP3 Update Rollup 12.
I installed Update Rollup 12 on my test SBS 2011 server this evening and it took 28 minutes from start to finish, so I wouldn’t expect it to take much longer than this in production.
The new update was released today so please test before installing into your production environment. Maybe even wait a few days or a week or two to make sure the QA is up to scratch on it.
For migrations to Exchange 2016, Exchange 2010 SP3 Update Rollup 11 is the minimum version that will be supported in a coexistance environment.
I’ve recently upgraded my home lab from running Windows 8.1 to running Windows 10. It wasn’t an inplace upgrade, as I replaced the OS drive so it was a fresh install onto an SSD, all was going swimmingly until i hit an issue with Windows Update replacing some of my drivers.
While the initial installation went ok, Windows Update ran and patched without a hitch. I then spent some time putting on the latest vendor drivers from Asus for the motherboard and AMD for the graphics card. The system ran perfectly for a couple of days until the next round of Windows Updates. After that Internet connectivity was intermittent, pings were dropping left, right and center making remote access impossible. On further investigation the network card driver had reverted from my Intel 82579LM to a Microsoft driver!
Well after unisnstalling the Microsoft driver, a scan for hardware changes and reinstalling the network card driver, the system was working well again, but I wanted to stop Windows Update from installing drivers for me in future.