After the excitement of the previous evening, the day kicked of a little later than the norm for me with the Elastic
One of the things I wasn’t especially aware of was the X-Pack by Elastic and that there is a free, basic version available of that after a 30 day trial. Elastic Cloud may also be an option if we do not want to have to run the underlying infrastructure but just be a consumer of the platform. Shortly after that the session became more of a deep dive into Azure provisioning Elastic with the ARM config files, which was a bit out of my depth.
If you are an Active Directory Administrator, Check out this presentation by MVP Jess Dodson on AD Security and Maintenance which was presented in the main hall at MSIgnite NZ a couple of weeks ago.
Some of you may already be familiar with Jess’s work over at Girlgerms Online and if not, these is definitely one of the better systems administration blogs in Australia 🙂
Edit 6/11/16 – WordPress is not correctly embedding video – looks fine in editor, but shows a link when published. have updated URL to direct link to the Channel 9 site.
Where I work we have recently acquired a number of Dell R620 servers to be used in remote locations. Personally I think they are a great all round server for the light to medium workloads seen on the infrastructure we manage.
I’ve been pushing hard to use automated deployment systems that rely on the iDRAC interface, with the plan being that people take the rack and stack a previously unopened server at the remote site, use the front panel to configure iDRAC Network and then come back to work to provision the server remotely. The default username and password for the iDRAC is well known. That is until recently when we placed a server on site, confirmed we could remotely contact the iDRAC and came back, only to find the defaults not working.
It would appear that certainly the batch of servers we have, and some anecdotal reports from friends deploying Dell servers is that some server’s iDRAC interface appears to have a “faulty” default password. This was confirmed with a follow up call to Dell support. Current fix is (you guessed it) to ensure you set the password before going out on site. Whilst an inconvenience, luckily this was discovered after one server went out, and not all of them.
So just a heads for people that if you are relying on you iDRAC to remotely provision brand new boxes, you may want to set the default username/password yourself rather than making an assumption it will work.