Exchange 2013 SP1 was released in February this year providing support for Windows Server 2012 R2. In this blog we’ll run through the installation process.
The demo environment I am using includes a Windows Server 2012 R2 domain controller and a Server 2012 R2 member server.
In the demo environment no previous versions of Exchange have been installed so as part of the installation the Exchange 2013 SP1 we will upgrade the AD Schema, even if you are running Exchange 2013, the installation of SP1 requires a Schema update. Note in this scenario we are going to jump straight to installing Exchange 2013 SP1, with out installing Exchange 2013 first.
Finally before we start, always test in a demo environment before deploying in Production!
The Shellshock vulnerability in Bash (a command line shell) hit the news last week and has the potential to be far more serious than the Heartbleed bug discovered earlier in the year. The Shellshock bug appears to mostly effect Macs, Linux, Unix, and websites based on Apache, although some network hardware may be effected.
There is a very good technical article that Troy Hunt has published which explains the vulnerability in some depth. You can view it here, as well as many other websites which are covering the story so I won’t go into detail, just type Shellshock into your favourite search engine.
Instead below is a list of the major vendors which we and customers use and links to any articles they have regarding Shellshock and their products.
Watchguard and Draytek have confirmed they have no effected products. Microsoft is also uneffected.
Keep checking back as I will update this as more detials from vendors become available.
If you know of any other Vendor statements regarding the ShellShock bug please add a comment below, and I will incorporate it into the post.
Here is another quick Exchange PowerShell post on distribution groups, in it we will look at how to check and modify a particular setting.
A client recently got in touch after a suspect email was sent to all staff in a particular distribution group. Usually only staff can send emails to distribution groups because you need to be authenticated, so I had a quick check of the distribution group’s settings to see what was going on.
I’m a keen photographer and for years have been using Breeze Downloader Pro to download photos from memory cards to my computer, before editing them in Adobe Lightroom.
Recently though I’ve been trying to simplify my workflow and found the built in import facility in Adobe Lightroom to be really good as you can add keyword metadata and automatically build previews when you import them which saves a lot of time.
So I needed to change the AutoPlay action when a memory card was inserted. Continue reading →
Veeam have released a new free tool which looks pretty useful for small Hyper-V deployments, Veeam Task Manager for Hyper-V.
On a Hyper-V machine we know that the host Task Manager only shows the performance of the parent partition, and you have to use PowerShell or Hyper-V Manager to view performance of the guest virtual machines.
Veeam have combined the two in their new Veeam Task Manager for Hyper-V. It only shows you the CPU and Memory utilisation, but if you are troubleshooting performance and don’t have a big performance monitoring application in place I suspect it will be pretty useful.