The latest version of Dell Server Update Utility (SUU 14.10.00) has been released. The SUU is an application used to help patch Dell PowerEdge servers. It will compare currently installed drivers and firmware with those available on the DVD or mounted iso file.
OpenManage Essentials 2.0 was released on the 8th September 2014. It adds support for 13th Generation servers, enhancements in search and discovery, deployment of iDRAC service modules, enhanced scalability, additional inventory and reporting plus many more features.
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!
I hope this walk through help.
OxfordSBSGuy Continue reading
Last week I rebooted one of the management servers I use, everything looked fine, but the Veeam backup didn’t run that evening.
Veeam reported the following error:
“Task failed Error: No connection could be made because the traget actively refused it. ipaddress:443″
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.
http://support.apple.com/kb/DL1769 (for Mavericks)
http://support.apple.com/kb/DL1768 (for Mountain Lion)
http://support.apple.com/kb/DL1767 (for Lion)
On August 28th Microsoft released the Exchange 2010 SP3 Update Rollup 7. The Update Rollup 6 for Exchange Server 2010 SP3 contains the fixes for the security issue that is described in KB2961522.
Update Rollup 7 for Exchange Server 2010 SP3 resolves the issues that are described in the following Microsoft Knowledge Base (KB) articles:
2983261 “HTTP 400 – Bad Request” error when you open a shared mailbox in Outlook Web App in an Exchange Server 2010 environment
2982873 Outlook Web App logon times out in an Exchange Server 2010 environment
2980300 Event 4999 is logged when the World Wide Web publishing service crashes after you install Exchange Server 2010 SP3
2979253 Email messages that contain invalid control characters cannot be retrieved by an EWS-based application
2978645 S/MIME option disappears when you use Outlook Web App in Internet Explorer 11 in an Exchange Server 2010 environment
2977410 Email attachments are not visible in Outlook or other MAPI clients in an Exchange Server 2010 environment
2976887 eDiscovery search fails if an on-premises Exchange Server 2010 mailbox has an Exchange Online archive mailbox
2976322 Assistant stops processing new requests when Events in Queue value exceeds 500 in Exchange Server 2010
2975988 S/MIME certificates with EKU Any Purpose (184.108.40.206.0) are not included in OAB in Exchange Server 2010
2966923 Domain controller is overloaded after you change Active Directory configurations in Exchange Server 2010
The update can be downloaded from here.
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.