Windows 8 / Windows Server 2012 Operating System does not boot or install on ESXi or ESX (2006859)
Symptoms
- Windows 8 / Windows Server 2012 fails to boot or install on any version of ESXi or ESX
- Windows 8 / Windows Server 2012 is not working
- You cannot use Windows 8 / Windows Server 2012 in ESXi or ESX
Resolution
Windows 8 / Windows Server 2012 is fully supported for ESXi 5.1 and ESXi 5.0 U1 and ESXi 5.0 U2.
Note: For Windows Server 2012, you must install the patch ESXi500-201209001(Patch 04) on ESXi 5.0 U1. For more information, see 
VMware ESXi 5.0, Patch Release ESXi500-201209001 (2032584).
Steps
- Windows 8 Developer Preview / Windows Server 2012 Release Candidate does not boot on ESXi 5.0. To resolve this issue, you must install patch ESXi500-201112001 (Patch 02):
- Download and install ESXi500-201112001 (Patch 02). For more information, see VMware ESXi 5.0, Patch Release ESXi500-201112001 (2007680).
- Create a new virtual machine configured for either Windows 7 or Windows 2008 R2.
- Enable 3D graphics or do not install VMware’s WDDM video driver.
- Install Windows 8 / Windows Server 2012 from Media.
- Install VMware Tools.Note: VMware does not recommend installing VMware’s WDDM video driver. Use the default VESA driver.
- If you experience a black screen after installing VMware’s WDDM video driver in a virtual machine with Windows 8 / Windows Server 2012, enable 3D graphics or reinstall the operating system and VMware Tools without VMware’s WDDM video driver.
- VMware does not currently recommend using USB xHCI with Windows 8 / Windows Server 2012. To work around this issue, remove the USB xHCI controller or use the USB EHCI+UHCI controller.Note: Any changes to the virtual hardware must be preceded by a full shutdown on the command line (shutdown /s /t 0 /full). Otherwise, the Windows 8 / Windows Server 2012 hibernate-shutdown may not fully detect hardware changes and you may experience a blue diagnostic screen or triple fault at boot.
- The vmxnet3 virtual NIC does not work in a Windows 8 / Windows Server 2012 virtual machine with ESXi 5.0. To work around this issue, use e1000e or e1000 NICs.
Ref.:
Consultando os servidores que detem as FSMOS de um domínio
Para verificar quais DCs hospedam as FSMO dentro da floresta ou domínio, digite o comando “netdom query fsmo” em um prompt de comando.
Parqa Windows 2000/2003, você precisa instalar o “Support Tools” a partir do diretório \Support\Tools do CD de instalação do windows.
Veja o exemplo:
C:\>netdom query fsmo Schema master SRV02.TESTE.CORP Domain naming master SRV02.TESTE.CORP PDC SRV01.TESTE.CORP RID pool manager SRV01.TESTE.CORP Infrastructure master SRV01.TESTE.CORP The command completed successfully. C:\>
Documentos com opções, design e configuração de Private Cloud com Windows 2012
Este link são 4 documentos que falam sobre como deve ser especificado, desenhado e até implementado.
O documento de implementação, por exemplo, contem passo a passo como deve ser feito e sempre com os comandos em PowerShell.
Muito bom! http://www.microsoft.com/en-us/download/details.aspx?id=36795
Windows Server 2012 ODX support with EqualLogic Storage
Here is a good paper written by Chuck Farah and Rajkumar MR titled “Understanding Microsoft Offloaded Data Transfer on Dell EqualLogic PS Series Arrays”.
Abstract: This White Paper provides basic understanding of the bulk data transfer functionality of Offloaded Data Transfer, ODX with Microsoft Windows Server 2012 providing improved compute utilization on DellTM EqualLogicTM PS Series SANs.
One of the things I have been doing recently in my lab is creating Hyper-V SQL Server VMs from a 20GB Hyper-V template which lives on a file share called Z:\VMgoldcopy directory (on EQL storage). The template is syspreped so all I have to do is copy the template from Z: to my shared E:\VMStorage (on same EQL Storage as Z:\) , rename it, then use Hyper-V Manager to create a new VM using this copied / renamed VHDX as the virtual hard disk. The copy process is smoking fast, hitting 300+MB/s thanks to ODX. This paper provides details behind this goodness and gives you an idea of the benefits it can provide to you and our customers using EQL with Windows.
The whitepaper on Hyper-V and ODX with EQL can be found at: http://i.dell.com/sites/doccontent/business/solutions/whitepapers/en/Documents/microsoft-offloaded-data-transfer-equallogic.pdf
System Center 2012: Marcelo Sincic´s notes
Suíte System Center 2012 não é voltada para SMB, em resposta a não ser lançado um System Center Essentials 2012 (o ultimo é o SCE2010).
A estratégia da Microsoft é direcionar SMB para gerenciamento e hospedagem em cloud (Windows Azure) que agora permite Quick Migration de VMs criadas no Hyper-V diretamente com o Azure.
Baseado nisso temos o Windows Intune (similar ao SCCM) para CCM que é pago mas inclui a licença do Windows e gerencia iOS e Android também (http://www.microsoft.com/pt-br/windows/windowsintune/pc-management.aspx)
Para gerenciamento de servidores, esta semana a Microsoft anunciou que o System Center Advisor (similar ao SCOM) agora é gratuito (https://www.systemcenteradvisor.com/) e terá suporte a Windows 2012 lançado no MMS.
Windows Server 2012: Failover Cluster and Hyper-V hotfix
You can find in the links below a list of hot fix for your failover cluster and hyper-v in Windows Server 2012.
It´s always a good idea to apply all required hotfix.
RedHat 6.2 and Oracle: BONDING for local network and Interconnect
Oracle 11.2.0.3
RedHat 6.2
bond0 – 2 Broadcom NIC 10Gbps for public network
bond1 – 2 Broadcom NIC 1Gbps for Oracle interconnect
Let´s start stopping NetworkManager to avoid headaches:
[root@ora1 ~]# service NetworkManager stop Stopping NetworkManager daemon: [ OK ] [root@ora1 ~]# chkconfig NetworkManager off
Set all DNS and domain:
[root@ora1 ~]cat /etc/resolf.conf search dominio.corp nameserver 172.17.160.104 nameserver 172.17.160.105
Create alias for your bonding:
[root@ora1 ~]# cat /etc/modprobe.d/modprobe.conf alias bond0 bonding alias bond1 bonding
Listing network scripts:
[root@ora1 ~]# ll /etc/sysconfig/network-scripts/ifcfg-* -rw-r--r--. 1 root root 102 Mar 1 11:41 /etc/sysconfig/network-scripts/ifcfg-em1 -rw-r--r--. 1 root root 102 Mar 1 11:42 /etc/sysconfig/network-scripts/ifcfg-em2 -rw-r--r--. 1 root root 254 Oct 7 2011 /etc/sysconfig/network-scripts/ifcfg-lo -rw-r--r--. 1 root root 103 Mar 1 11:42 /etc/sysconfig/network-scripts/ifcfg-p3p1 -rw-r--r--. 1 root root 103 Mar 1 11:42 /etc/sysconfig/network-scripts/ifcfg-p3p2
Script to create bond0 with NICs em1 and em2.
mode=0: Load balancing using Round Robin.
[root@ora1 ~]# cat /etc/sysconfig/network-scripts/ifcfg-bond0 DEVICE="bond0" IPADDR=10.0.8.148 NETMASK=255.255.255.0 GATEWAY=10.0.8.1 NM_CONTROLLED=no BOOTPROTO=none ONBOOT=yes USERCTL=no TYPE=BOND BONDING_OPTS="mode=0 miimon=100 downdelay=200 updelay=200" IPV6INIT=no [root@ora1 ~]# cat /etc/sysconfig/network-scripts/ifcfg-em1 DEVICE="em1" HWADDR="90:B1:1C:E5:93:41" ONBOOT=yes MASTER=bond0 SLAVE=yes USERCTL=no NM_CONTROLLED=no [root@ora1 ~]# cat /etc/sysconfig/network-scripts/ifcfg-em2 DEVICE="em2" HWADDR="90:B1:1C:E5:93:44" ONBOOT=yes MASTER=bond0 SLAVE=yes USERCTL=no NM_CONTROLLED=no
Script to create bond1 with NICs p3p1 and p3p2.
mode=6: Adaptive load balancing mode
MTU=9000: Recommended for Oracle interconnect
[root@ora1 ~]# cat /etc/sysconfig/network-scripts/ifcfg-bond1 DEVICE="bond1" IPADDR=10.0.200.148 NETMASK=255.255.255.0 NM_CONTROLLED=no BOOTPROTO=none ONBOOT=yes USERCTL=no TYPE=BOND BONDING_OPTS="mode=6 miimon=100 downdelay=200 updelay=100" MTU=9000 IPV6INIT=no [root@ora1 ~]# cat /etc/sysconfig/network-scripts/ifcfg-p3p1 DEVICE="p3p1" HWADDR="90:B1:1C:E5:93:45" ONBOOT=yes SLAVE=yes MASTER=bond1 USERCTL=no NM_CONTROLLED=no [root@ora1 ~]# cat /etc/sysconfig/network-scripts/ifcfg-p3p2 DEVICE="p3p2" HWADDR="90:B1:1C:E5:93:48" ONBOOT=yes SLAVE=yes MASTER=bond1 USERCTL=no NM_CONTROLLED=no
Listing network script again:
[root@ora1 ~]# ll /etc/sysconfig/network-scripts/ifcfg-* -rw-r--r--. 1 root root 207 Mar 1 11:40 /etc/sysconfig/network-scripts/ifcfg-bond0 -rw-r--r--. 1 root root 201 Mar 1 11:41 /etc/sysconfig/network-scripts/ifcfg-bond1 -rw-r--r--. 1 root root 102 Mar 1 11:41 /etc/sysconfig/network-scripts/ifcfg-em1 -rw-r--r--. 1 root root 102 Mar 1 11:42 /etc/sysconfig/network-scripts/ifcfg-em2 -rw-r--r--. 1 root root 254 Oct 7 2011 /etc/sysconfig/network-scripts/ifcfg-lo -rw-r--r--. 1 root root 103 Mar 1 11:42 /etc/sysconfig/network-scripts/ifcfg-p3p1 -rw-r--r--. 1 root root 103 Mar 1 11:42 /etc/sysconfig/network-scripts/ifcfg-p3p2
Loading bonding alias:
[root@ora1 ~]# modprobe -v bonding
Restarting network services:
[root@ora1 ~]# service network restart Shutting down interface bond0: [ OK ] Shutting down interface bond1: [ OK ] Shutting down loopback interface: [ OK ] Bringing up loopback interface: [ OK ] Bringing up interface bond0: [ OK ] Bringing up interface bond1: [ OK ]
Checking configuration:
[root@ora1 ~]# cat /proc/net/bonding/bond0 Ethernet Channel Bonding Driver: v3.6.0 (September 26, 2009) Bonding Mode: load balancing (round-robin) MII Status: up MII Polling Interval (ms): 100 Up Delay (ms): 200 Down Delay (ms): 200 Slave Interface: em1 MII Status: up Speed: 10000 Mbps Duplex: full Link Failure Count: 0 Permanent HW addr: 90:b1:1c:e5:93:41 Slave queue ID: 0 Slave Interface: em2 MII Status: up Speed: 100 Mbps Duplex: full Link Failure Count: 0 Permanent HW addr: 90:b1:1c:e5:93:44 Slave queue ID: 0 [root@ora1 ~]# cat /proc/net/bonding/bond1 Ethernet Channel Bonding Driver: v3.6.0 (September 26, 2009) Bonding Mode: adaptive load balancing Primary Slave: None Currently Active Slave: p3p1 MII Status: up MII Polling Interval (ms): 100 Up Delay (ms): 100 Down Delay (ms): 200 Slave Interface: p3p1 MII Status: up Speed: 1000 Mbps Duplex: full Link Failure Count: 0 Permanent HW addr: 90:b1:1c:e5:93:45 Slave queue ID: 0 Slave Interface: p3p2 MII Status: up Speed: 1000 Mbps Duplex: full Link Failure Count: 0 Permanent HW addr: 90:b1:1c:e5:93:48 Slave queue ID: 0
More about bonding mode:
- Mode 0 (balance-rr)
This mode transmits packets in a sequential order from the first available slave through the last. If two real interfaces are slaves in the bond and two packets arrive destined out of the bonded interface the first will be transmitted on the first slave and the second frame will be transmitted on the second slave. The third packet will be sent on the first and so on. This provides load balancing and fault tolerance.
- Mode 1 (active-backup)
This mode places one of the interfaces into a backup state and will only make it active if the link is lost by the active interface. Only one slave in the bond is active at an instance of time. A different slave becomes active only when the active slave fails. This mode provides fault tolerance.
- Mode 2 (balance-xor)
Transmits based on XOR formula. (Source MAC address is XOR’d with destination MAC address) modula slave count. This selects the same slave for each destination MAC address and provides load balancing and fault tolerance.
- Mode 3 (broadcast)
This mode transmits everything on all slave interfaces. This mode is least used (only for specific purpose) and provides only fault tolerance.
- Mode 4 (802.3ad)
This mode is known as Dynamic Link Aggregation mode. It creates aggregation groups that share the same speed and duplex settings. This mode requires a switch that supports IEEE 802.3ad Dynamic link.
- Mode 5 (balance-tlb)
This is called as Adaptive transmit load balancing. The outgoing traffic is distributed according to the current load and queue on each slave interface. Incoming traffic is received by the current slave.
- Mode 6 (balance-alb)
This is Adaptive load balancing mode. This includes balance-tlb + receive load balancing (rlb) for IPV4 traffic. The receive load balancing is achieved by ARP negotiation. The bonding driver intercepts the ARP Replies sent by the server on their way out and overwrites the src hw address with the unique hw address of one of the slaves in the bond such that different clients use different hw addresses for the server.
