I understand Scott comment about trusting hyper-v vs. VMware but the reality of that situation bro I was down at the hyper-v is so young in comparison to VMware
I'm not recommending it here, only stating that it is a weird emotional thing for the manager to dis VMware for Microsoft in a place where it is a pretty obvious technical problem but not do it where it would make sense.
LOl is it really weird? or is it normal even though it probably shouldn't be?
As soon as the team is added, connectivity is lost. Can't even get as far as adding the adapter before connectivity is lost.
So... once you create the virtual switch in Hyper-V Manager Virtual Switch Manager, using the NIC Team you created on the Host OS, all connectivity is lost?
At that point, what do the event logs say? Is there some kind of weird MAC conflict? When you look at the connection status of the virtual switch in Control Panel -> Network Connections, what does it look like? Are you getting a 169 address? Is it all 0's? What's actually going on and what does Event Viewer say?
Good article. There is ZERO reason to have a GUI on a Domain Controller. Everything can be done through Server Manager on Windows 10/8
You mean RSAT
Both? You can do a lot of directory management through Server Manager as well.
Ok, agree. Just don't like the Server Manager this much, ugly interface. I want to be sure WHICH drive on WHICH host I'm going to format for example. But that is just my personal opinion and I'm more or less a console fetishist
But when it comes to ADSIedit or AD sites, you really want to have RSAT.
Those options are generally only there is RSAT is installed.
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.
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!
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.
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.
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.
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.
Looks like your connection to MangoLassi was lost, please wait while we try to reconnect.