Servers power many organisations and are even making their way into homes (even if it is a simple NAS box). With more RAM then you could even imagine (I have to admit I’m a RAM addict) and processors that make the latest and greatest gaming PC look minuscule in comparison it is these mighty machines that make the world go round.
It’s that magical time of the year where…new network switches arrive! Given that the new Aruba branding has taken full control of what was ProCurve I thought I should post some photos of the new paintwork. Happy to say the colour black isn’t half bad!
Included in the images are
- J9729A 2920-48G-PoE+
- J9728A 2920-48G
- J9731A 2920 2-Port 10Gbe SFP+ Module
- J9733A 2920 2-Port Stacking Module
- J9734A 2920 0.5m Stacking Cable
After recently deploying a Windows Server 2012 R2 WSUS server (afraid we couldn’t wait much longer for 2016 (which is now out by the way!)) we started seeing Error 8024400E on our clients and servers (from 2008R2/Windows 7 to Server 2012 R2/Windows 10).
As it transpires Microsoft published KB3159706 for the WSUS server which adds some new features to be able to manage Windows 10 updates and thus requires some manual post installation steps which can be found at this link here – https://support.microsoft.com/en-gb/kb/3159706.
The steps only took a few minutes to go through so it was a pretty easy fix in the end.
In this guide I’ll show a ‘working’ method to upgrade from MySQL Server 5.1 to 5.5 on a Windows Server 2008 R2 machine. In this case MySQL Server 5.1 was installed by the Microsoft Web Platform Installer some time ago, however this version doesn’t deliver very good performance (and its horribly outdated!) so it was time to get it replaced.
The good chaps at MySQL do offer a guide on how to do this on their website – https://dev.mysql.com/doc/refman/5.5/en/windows-upgrading.html however I hope you will find this one will serve you better.
A few points to note before we continue….
- This guide assumes you are using a default install of MySQL Server 5.1 (as delivered by the Microsoft Web Platform Installer)
- This guide only looks at a ‘simple’ server deployment i.e. no clustering or other funky features are in use
- It is recommended to jump only one version at a time when going from MySQL version to version e.g. 5.1 to 5.5 (there were no 5.2, 5.3 or 5.4 versions) and then 5.5 to 5.6 and 5.6 to 5.7…
- You can download previous versions of MySQL Server from this link – http://dev.mysql.com/downloads/mysql/ just click on the ‘Looking for previous GA versions?’ link
- Be sure to take a backup of your databases before you attempt this guide on a production machine (see https://dev.mysql.com/doc/refman/5.5/en/backup-methods.html for some ideas on how to do this)
- If possible run through the upgrade process a few times on a testing machine (one that you can break and no one will notice) first
So on with the guide!
Final point to note….this guide only works with migrations to 5.5 from 5.1, if going to further versions you will be missing some tables which will in turn generate error messages during the upgrade process. More information on that here http://dba.stackexchange.com/questions/54608/innodb-error-table-mysql-innodb-table-stats-not-found-after-upgrade-to-mys.
Work is coming along nicely with the Server Room, we’ve now removed the last Cisco switch from our infrastructure and the HP 5400R series switch is deployed replacing the 2530 that was in its place; over time we’ll be bringing more fibre from our edge switches into this room as well hence the number of SFP+ ports on the 5400R. The entire front of the cabinet is now populated with hardware or a blanking panel as well (panels available from Comms Express) to keep things looking tidy. I wish there were a little more that I could do with the cables coming into the 5400R however with a very narrow rack there’s not much that can be done.
Some interesting things have come out of both Rucks and PaloAlto recently in that they offer Hyper-V compatible VMs for their services which could free up a further 3U of space and remove a further 4-6 cables out of the picture.
Looking for some fun ways to get more out of your your Smart Card deployment? If so have you tried……?
- Use Smart Cards to login to your Servers via Remote Desktop
- Use Smart Cards with the PowerShell Get-Credential Commandlet
- Use Smart Cards with your Firewall for single sign on
- Use Smart Cards to login to IIS Web Applications (just a box to tick and a radio option to select)
- Store multiple identities on your Smart Card and assign different (and perhaps more complex) PINs to the identities
Have a look at the screen shots below for some more details…
One of those monthly jobs that every SysAdmin will come across is good old Patch Tuesday; to help make Patch Tuesday a little more fun after all of the servers have been updated I use Hyper-V Replica (run by a PowerShell script) to shutdown each Virtual Machine and move it onto another host (ticks the box for the machine reboot component of Windows Updates and also tests our DR solution in one hit!).
However as both of my DCs are Virtual Machines I want to make sure that at least one DC is up at all times, to do that I have built a little PowerShell function (see below to download it within a zip file!) that is run before every migration to ensure that both DCs are up and running (along with the Network Policy Server service which is used to authenticate clients on the network (and so is very important!!)) before any migration happens.
Hopefully this will help someone someday!
See if DCs are up (905 bytes, 283 hits)
A silly gotcha more than anything else…. after recently updating my WSUS server to use SSL (to allow publishing through the firewall) I noticed my clients that were deployed with MDT (Microsoft Deployment Toolkit) were not installing updates as part of the Task Sequence; indeed the message log at the end indicated that the updates could not be downloaded as there was no connectivity to the WSUS server.
Lone behold I had updated the path to be https:// (against http://) in the Group Policies that pointed the clients at the WSUS server but not in the Deployment Share properties in MDT. So let the lesson be learnt… be sure to make the URL change in MDT as well as in Group Policy.
While working on my most recent Hyper-V Replica PowerShell script when attempting to reverse replication from a source Hyper-V host to the a target host using Certificate authentication I was getting the error message…
Hyper-V failed to establish a connection with the Replica server ‘<target hostname>’ on port ‘443’. Error: The connection with the server was terminated abnormally (0x00002EFE).
As it turns out I had recently deleted and created a new certificate for the target host and as such there was no certificate listed in Hyper-V Settings > Replication Configuration. The fix was to set the replacement certificate in the box provided. See the screenshots below for a little more…
Having recently purchased a Dell T430 tower server which we will be using for backup and Hyper-V replica I thought I’d share some photos of what the castors (an option in place of either the rack mounting kit or the floor stand feet) look like!
The castor assembly comes in a separate box to the server and only takes a minute or two to install; I perhaps was expecting slightly larger wheels however they do a good job all the same on hard floors.
The screenshot above shows a portion of the sensor in its default form; in this post I’m going to show how to…
- Remove the red ‘downtime’ line from the bottom of the chart
- Set maximum and minimum values of the graph to display 0 to 100%
- Set the gauge to display its value in GByte instead of MByte
Red Downtime line
Pure aesthetics with this tweak – the memory sensor isn’t something that I would expect to ever encounter downtime (if there server were offline then the PING sensor would pause the memory sensor automatically). The only real application for the downtime sensor would be if WMI wasn’t responding.
Max and Min
PRTG will automatically set the scale for your graphs but I prefer to see the full range of 0 – 100%; this tweak makes that possible.
GByte instead of MByte
When working with servers with small amounts of RAM (lets say 4GB and less) it is typically going to work out best to view free RAM as MBytes but when working with Hyper-V hosts (48GB and 96GB in my case) GBytes are a much better value to work with.