No, it doesn't support this. RAID 1, you are correct, but Parity RAID 5 or 6 it does not. The OS needs to be up and running to be able to manage the parity RAID so you can't use it for the system install, only for extra data volumes.

That's the big thing with XenApp, application performance. And integration with XenDesktop for VDI.

OK solved this.

Ran a chkdsk in read-only and poof the problem was gone.

odd - it indicated there were no problems, but after I ran it in read-only it worked fine.

Well - continuing down the fan spin up, spin down saga - Today HP had me send them logs from iLo. Those logs showed that I am using a NIC firmware that they have since pulled (but it was in the service pack DVD ISO - so WTF?). They want me to downgrade the NIC firmware.

Of course, the single install file for NIC firmware is gui based, and even though you can extract the dozen or so files from the installer and run them direct, they don't have instructions for doing so.

So now I'm stuck downloading and old Service Pack DVD ISO so I can boot from that and downgrade my firmware. oh boy!

Well this saga isn't over yet.

My old Windows 2008 R2 KMS server is still up and running, has KMS installed, but is NOT published in DNS - I've confirmed this.

But when I went to a computer and ran

cscript slmgr.vbs /ato

to force a re-registration, it still registered with the old server.

Now I've disabled the port (1688) on the old server. Now to see how the client PCs handle that.

OMG, nevermind. Figured that out too. Was a combination of a missing default path and the same .NET CLR pool version as before. It's a subfolder and needs its CLR version set, too. Argh. All is well now.

If you want to use a newer version of .Net, I generally tell it to use whatever version I want and the "Classic" version if it is listed. I've had problems similar using any other version.

@Minion-Queen -- Yes, this code is available for anyone to test. It needs to be run from the Connection Broker, for now.

If folks find it useful enough, I may change that.

Here is an example:

Three hosts, each running two Windows Server VMs, each with two sockets. Say Dell Power Edge R610 or HP Proliant DL360 nodes. Windows Standard Licensing.

Cost per license: ~$700

To license each node to run its normal load is $700 for a total of $2,100.

If we want to address the ability of any node to be a failover for the others or for non-disruptive maintenance, we need an additional license per machine. So we suddenly jump from $700 per node to $1,400 per node and the whole cluster jumps to $4,200 while gaining nothing during normal production times.

Now that only addresses single node failover. If we want to maintain the ability to do failover during times of maintenance we need yet another license for each machine! That means $2,100 per machine and $6,300 for the cluster.

Suddenly $350 per virtual machine in licensing has exploded to $1,050. A non-trivial increase.

Now we can choose which level and which features we want, but typically the value of an inverted pyramid is sold based on this top level of flexibility. If we are dealing with Data Center licensing this is more obvious and far less complex, but SMBs would rarely pay for that level of workload and may not think through the additional costs that this style of architecture potentially bring to the table.

Easier question to ask - did any computers loose power at all? If the answer is yes, then ask, was it all or just some? If some, then possibly you had a 3 phase power related issue. If not, then this is not an issue.

@GregoryHall said:

This write up is what I point people to when they have these questions (*the one my MS rep from SW said is gospel)
http://www.microsoft.com/OEM/en/licensing/sblicensing/Pages/downgrade_rights.aspx#fbid=D7zcRxMWVLN

Yeah but that says nothing about this specific case in regards to VOSE rights.

@dafyre said:

If you haven't, make a specific AD account for the TFS server and let it run under that account and see what happens?

That's the plan, well not a specific one. we have a service account and it should have been setup that way but it was not, now I have to deal with the issues. It will have to wait til tonight when no DevOPs are doing anything to check it.

Me too, that sounds good now that you say it.

I am staying with my dad too, here in the land of pizza, subs and fish frys.

It's apparently a sporadic issue with Server 2012 r2 or Windows 8.1 running on Hyper-V on Windows 8.1/Server 2k12 R2 with Generation 2 VMs and secure boot. Secure boot needs to be disable for some updates. All expect for 3 out of the 98 were failing. Odd thing is there are four other 2k12 r2 Gen 2 VMs on the host that had no issues with the windows updates. Disabled Secure boot on the VM and it worked fine.

Pertino is what we do.... full mesh VPN / Software Defined Network. Every device is on it. So every server, every desktop, every laptop and soon NAS devices and iOS devices as well (as soon as they get on the iOS bus!!) But you can do other things too like Cisco IPSEC VPNs, OpenVPN, etc. Lots of options.

@IRJ fixed