You've likely been itching to get rid of that pesky Java requirement if you want to remotely administer your Supermicro gear that's blessed with free IPMI/BMC/iKVM. Especially if you read my closely-related posts earlier this year: Supermicro's beloved iKVM Console Redirection is dumping problem-ridden Java for HTML5, yay! MAR 08 2016 I then dove in a little deeper: Supermicro Redfish API in IPMI
You heard all about guestOS = "winhyperv" here first! What if you just want to virtually "kick the tires" on the latest Microsoft Hyper-V Server 2012, without committing dedicated hardware, to focus more on learning the features than the performance? Well, if you already have the prerequisites: a) an ESXi 5.1 lab where you're allowed to tweak the Hyper-V VM's vmx file slightly (not changing anythi
I tend to stick with technical articles and how to guides. But there's something else I've been worrying about for months now. How will VMware be handling the move toward vSphere 5.5 and eventually 6.0, where the vSphere Client will be entirely gone, completely replaced by the vSphere Web Client. That means you will have to have a VCSA (vCenter Server Appliance) to attach to, making VCSA is no lon
ESXi 5.0 and 5.1 all worked fine with the common Realtek 8111/8168 series of network adapters, typically found in a variety of consumer-class motherboards. What to do for ESXi 5.5 in the home lab? Suddenly you can't even install ESXi, even though you have a perfectly workable system that happens to already have Realtek on board. Such as my very own vZilla. Yes, with 5.5, you'll get the dreaded “No
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く