Wednesday, February 15th, 2012
Microsoft have today released via Windows Update and WSUS, the 2nd rollup of patches for the family of products including SBS 2011 Essentials, Windows Storage Server 2008 R2 Essentials and Windows Home Server 2011 Premium. The individual patches are listed below for the relevant products.
2630429 Update Rollup 2 for Windows Small Business Server 2011 Essentials is available
2630434 Update Rollup 2 for Windows Home Server 2011 is available
2630436 Update Rollup 2 for Windows Storage Server 2008 R2 Essentials is available
The update can be seen in Windows Update as you can see from the screenshot below. It takes less than 5 minutes to apply this update and reboot the computer.
There is also a series of fixes for the client side of the above products and Microsoft have detailed the KB article below. You don’t need to deploy anything specific however to the clients as the clients will automatically update once the server side update is in place.
2630445 The client-side package for Update Rollup 2 for Windows Small Business Server 2011 Essentials, for Windows Home Server 2011, and for Windows Storage Server 2008 R2 Essentials is available
Below you can see the client machine automatically installing the updates.
There are some updates that will require the restart of any client machine – and the alert below shows you this. very clearly.
Thursday, July 14th, 2011
Microsoft have pulled the above mentioned Update Rollup due to a number of issues seen in the field . So much so that Microsoft have taken action to remove it from the update site. Their blog post here talks about how there is the potential for data loss if the Public Folders are moved from within Outlook. Whilst the risk is minor they have pulled the update and will leave it until August to fix when they release Update Rollup 5 for Exchange 2010 SP1.
Wednesday, July 13th, 2011
I was writing this blog post over the weekend and downloading Update Rollup 4 for Exchange Server 2007 Service Pack 3 and could not help but notice, that Microsoft is now pushing Office 365 to you even when you go to patch your Exchange server. They really are desperate to get you to move to the cloud even if it’s not the right thing for your business. See the screenshot below for the advert for Office 365.
Tuesday, May 17th, 2011
I was doing some work last week on an Exchange 2010 server and multitasking a little too much maybe .
I lost connection with the Exchange server services and then discovered in the Services MMC that they were all set to disabled as you can see below.
For a moment I had a heart attack and wonder just what the heck was going on… then I remembered that in my multitasking, I was actually installing an Update Rollup for Exchange which had set the services to disabled so that it can replace the required program files for Exchange.
Lesson #1342 for today – too much multitasking can be a bad thing… slow down
Monday, May 16th, 2011
I’ve had this question asked of myself quite a few times now, and my response has been sure – as long as the application providers you run on your server support it. By that I mean things like your AV vendor and any LOB software that you run on the server need to support the Service Pack 1 for Windows Server 2008 R2. I know that Trend as of WFBS 7.0 Build 1435 support it and now the SBS team have come out to say that yes – the in fact recommend it here
What about SBS 2011 Essentials I hear you ask? Well if you look carefully you will see that SBS 2011 Essentials already has Service Pack 1 installed as it came out a few months after the SBS 2011 Standard edition.
Ok – what are you waiting for… do your backup and get on with it.
Wednesday, March 23rd, 2011
Last week on two separate Windows Server 2008 R2 servers on a clients site, both of them decided they would not correctly recognise the tape drives anymore. These servers had not been patched in a few months (due to the onsite IT Admin) and therefore there were a large number of patches installed. The problem showed up in Device Manager with the HP LTO Tape Drive having a yellow exclamation mark against it. If you drill down into the device itself it gave the error message below
Windows cannot start this hardware device because its configuration information (in the registry) is incomplete or damaged. (Code 19)
At first I attempted to remove and reinstall the device but that did not resolve the issue. I then removed the device, rebooted and let it scan the devices again – same problem – still not resolved.
In the end I did some digging with Google and found a similar case here where someone had issues with their CDROM drive playing up. I dug deeper to find the specific key that referred to the HP LTO Tape Drive and executed the same modifications.
To resolve the issue use this procedure;
Problem solved – the device is now recognised correctly and works just fine
I’m still confused however as to how this issue came about and in particular why on two nearly identical servers did it occur at the same time. Keen to know if someone can explain this to me as I’m in the midst of creating a standard build for a client which will be used across 25 servers spread over 25 physical locations.
Tuesday, February 1st, 2011
Microsoft last week released Update Rollup 5 for SBS 2008. If you have default settings for your SBS 2008 patch management then it will automatically download it for installation on your SBS 2008 server as per my screenshot below. Installation for me did not require a reboot and took only a few minutes.
The list of things fixed by this is documented here
One of the key things this patch now does is to better manage the log files generated by WSUS 3.0 on SBS 2008. It contains as task that runs daily and clears out any log file older than 30 days.
Monday, January 31st, 2011
Trend this last week silently released another patch for WFBS 7.0 to combat issues people are seeing in the real world. The patch is cumulative of the previous public released hotfixes and supersedes the 1370 patch (Trend WFBS 7.0 – Patch 1370 Now Available) released in December.
I found out about the patch via the WFBS Security Console. This is a new feature in WFBS 7 that alerts you when there’s a new significant patch available.
What’s fixed with it?
The fix list includes the following known issues;
There is also at least one undocumented new feature in this release. The screenshot below from my server shows build 1370 – but you will notice the additional lines showing the hotfixes installed on this server – woohoo! I’ve bee asking for that for years now and finally it’s good to see it there.
Where can you get it?
You can get the patch from here on the Product Patch Tab.
Installation for me on my production SBS 2008 server went without a hitch. It only took a few minutes and it pushed out to the client security agents automatically. I was not currently seeing any of the issues others have seen on this server, but I applied it anyway to check out what might happen. If you are installing new sites, I’d recommend applying this patch ASAP as preventative measures. Below you can see my servers status after the upgrade. Note the Hot Fix History section which lists all applied hotfixes to the server.
What about WFBS 7 SP1?
Trend are working on this now with a public beta available shortly. It will be much more than a collection of hotfixes – it will contain official support for SBS 2011 Standard Edition. Yes – that’s right – WFBS 7.0 as per the documentation DOES NOT SUPPORT SBS 2011 Standard Edition. It only supported the pre-release version. If you assumed it would support the release version of SBS 2011 Standard – you are wrong – bad move WFBS 7 SP1 will be out soon.
Monday, January 24th, 2011
I was building a couple of virtual Windows Server 2008 R2 servers for a client for an Exchange 2010 deployment project last week. I noticed this morning that one of them would not allow me to add roles or features to it which was rather strange. I got the error below when I investigated – 0×800F0818.
I found this Blog post which helped me resolve the issue.
Monday, December 20th, 2010
Microsoft this week has released more update rollups for Exchange 2007 – if you are up to date with your patching on your SBS 2008 servers then the one that interests you most is Exchange 2007 Service Pack 3 Update Rollup 2. Wow – what a mouthful. You can find out more about what’s in this patch here, but the key thing is that it fixes the broken files links for SharePoint in OWA that were broken with the Service Pack 3 for Exchange 2007.
You can download the patch directly from Microsoft here or it should appear in your SBS 2008 security console as highlighted below where you can approve the update for deployment to your SBS 2008 server
I approved the patch and it downloaded to my SBS 2008 server. Windows Update prompted me to install the patch later that day.
Installation took around 15 minutes on my SBS 2008 server and it ran through without any errors. Now whilst the patch did not ask for a reboot, I have this “thing” where whenever I make major changes to the system like this, I prefer to reboot it and then test things out. That way I know for sure that the patch has applied successfully and not broken anything major.
Now that I’ve applied this patch to my own servers today and so far no issues – I’ll monitor it over the next few days before applying it to client sites.