A word of caution with Hyper-V’s new guest UEFI support…

As it turns out, the new implementation of UEFI for guests in Hyper-V 2012 R2 requires a GPT disk with an EFI system partition on it.

What does this mean to the average sys admin loaded with PowerShell scripts who wish to deploy VM’s using the new “Generation 2” feature of Hyper-V 2012 R2? It means your existing VHD provisioning scripts don’t work for Generation 2 guests.

When I regain my sanity, I’ll might publish a code snippet on handling that type of a deployment. In the meantime, going back to evaluating Hyper-V 2012 R2 before the BUILD conference.

PowerShell cmdlet for Getting Your Bank Account Balance(s) at PC Financial

I’m just gonna dump this code block I wrote so I don’t have to click and point on PCF’s messed up website.

I’m going to assume you probably know how to use PowerShell modules and using that said function. In this case all you need to do with this function is:

Get-PCFBalance -CardNumber 6018871011111110 -Password InsertYourPasswordInPlainTextHere
Continue reading “PowerShell cmdlet for Getting Your Bank Account Balance(s) at PC Financial”

Samba 4 Active Directory Domain Controller for a Microsoft Failover Cluster

With the release of Samba 4, there’s now the possibility of running an Active Directory-compatible controller on most *nixes out there. Don’t get me wrong about the real Active Directory solution from Microsoft out there, it’s a great solution for larger enterprises, but for the others out there who are either too restricted in terms of budgeting or just don’t want to touch a Microsoft Windows Server for Active Directory; Samba 4 can be a good option.

Up until now, using a Samba 4 AD domain controller for a Microsoft Failover Cluster is almost next to impossible as the validation pages fail on this error:

An error occurred while executing the test.
There was an error initializing the network tests.

There was an error creating the server side agent (CPrepSrv).

Creating an instance of the COM component with CLSID {E1568352-586D-43E4-933F-8E6DC4DE317A} from the IClassFactory failed due to the following error: 80070721 A security package specific error occurred. (Exception from HRESULT: 0x80070721).

Fortunately there is a way to temporarily resolve this issue. That solution is to add any value to the servicePrincipalName attribute via ADSI Edit or the Active Directory Users and Computers MMC snap-in. (Sorry folks, can’t use Active Directory Administrative Center as Samba4 doesn’t currently emulate an AD DS Web Service server…). And yes the people at the Samba project are aware about this “bug” due to the way of a developer interpreting how the security should have been implemented. (Sorry Andrew, I didn’t mean to throw you under the bus 😉

After adding that attribute, you should be able to validate successfully and have a fully functional Hyper-V cluster for almost next to nothing. (Except the cost of a Windows 8 Pro license)

Edit: Apologies of me being a little ambiguous on “any value” to the servicePrincipleName attribute. What I really meant was setting a non-NULL value on servicePrincipalName on the user who’s performing the validation checks and forming the cluster, not the computer account of the cluster member.

Getting faster optical media write speeds on your laptop (Well, sorta via iSCSI)

Ever been in a situation where you have plenty of 16x DVD-R media but your laptop’s slimline DVD writer has a maximum write speed of 8x?

I’m sure you’ve been there. For most users having a DVD to write slower than usual is not a big deal if they’re just creating a DVD for an odd occasion or two. (I mean, with USB’s flash drives and hard drives with an storage capacity that’s about 210x of what a DVD can store, who even bothers with optical drives anymore?)
Continue reading “Getting faster optical media write speeds on your laptop (Well, sorta via iSCSI)”

KB2750149 and the Failover Cluster GUI… Ouch

Last Patch Tuseday’s round had an update (KB2750149) for the .NET Framework on Windows 8/2012 systems that broke the Failover Cluster management UI. It’s a known issue for Microsoft as reported on their blog below:

http://blogs.technet.com/b/askcore/archive/2013/01/14/error-in-failover-cluster-manager-after-install-of-kb2750149.aspx

Unfortunately as of writing, Microsoft hasn’t pushed an update for fixing what they broke. However what they broke should not affect the functionality of the Failover Cluster itself. As the blog post stated above, the Failover Cluster will still function as normal and can still be managed using the PowerShell cmdlets or the command line tools.

To fix the issue you’ll probably have to either use DISM or the Windows Image Servicing PowerShell cmdlets to remove the .NET Framework Update. By performing a dism /online /get-packages or Get-WindowsPackage -Online and searching for the string ‘KB2750149’ should be sufficient enough to start the removal process.

Again before removing the patch, consult with the documentation. I can’t be responsible if you break your own system when you remove that patch mentioned above 😉