Microsoft entra en el iPad

Microsoft ha decidido romper fronteras. Quiere entrar en el mundo Apple, especialmente en los 100 mi...

http://www.elpais.com/articulo/tecnologia/Microsoft/entra/iPad/elpeputec/20111215elpeputec_2/Tes
PABLO CRUCES
http://virtualshocks.blogspot.com

Enviado desde mi BlackBerry® de Vodafone

Error al cargar los plug-ins de vSphere vCenter Server

Si al cargar los plug-ins nos da un error sobre un fichero XML, se debe corregir el varios ficheros las entradas con el nombre del host del vCenter. Esto suele ocurrir si se renombra manualmente tras haber cargado los plugins ya que la informacion no se actuliza en la estructura de ficheros xml.

Erro tipo: "The following error occurred while downloading the script plugin from https://hostname.domain.com:8443/health-ui/scriptConfig.xml: The remote name could not be resolved: 'hostname.domain.com'"

Los enlaces donde se debe modificar el hostname son los siguientes (https://):

%ProgramFiles%\VMware\Infrastructure\VirtualCenter Server\extensions\cim-ui\extension.xml
%ProgramFiles%\VMware\Infrastructure\tomcat\webapps\cim-ui\scriptConfig.xml
%ProgramFiles%\VMware\Infrastructure\VirtualCenter Server\extensions\health-ui\extension.xml
%ProgramFiles%\VMware\Infrastructure\tomcat\webapps\health-ui\scriptConfig.xml
%ProgramFiles%\VMware\Infrastructure\VirtualCenter Server\extensions\com.vmware.vim.stats.report\extension.xml
%ProgramFiles%\VMware\VMware\Infrastructure\tomcat\webapps\statsreport\WEB-INF\web.xml

Una vez cambiados los nombres del host, sera necesario reiniciar los webservices del vCenter, o directamente el servicio del vCenter Server que forzará a su vez el reinicio de los webservices.

 

SRM no es compatible con ODBC 64 bit

Si instalais SRM sobre un Windows 2008 R2 (64bit) os dara este error:

"Failed to start service.
VMware vCenter Site Recovery Manager service failed to start. Check that all required Windows services are running. View the server log for more information.
Press retry to try again or press cancel to exit installation."

Para solucionarlo, debereis tener instalado el driver ODBC de 32 bit, que podeis descargar de la web de Microsoft (el del Native client x32 del 2008 sirve) Pero para poder crear el ODBC de 32, no ejecuteis el que os aparece en en el panel de control (abrira el ODBC x64), si no que debeis ejecutar el ...\SysWOW64\odbcad32.exe

Enjoy!

Que sistemas operativos soportan VMXNET ? ...no todos

• VMXNET 3 — The VMXNET 3 adapter is the next generation of a paravirtualized NIC designed for performance, and is not related to VMXNET or VMXNET 2. It offers all the features available in VMXNET 2, and adds several new features like multiqueue support (also known as Receive Side Scaling in Windows), IPv6 offloads, and MSI/MSI-X interrupt delivery.
  
  VMXNET 3 is supported only for virtual machines version 7 and later, with a limited set of guest operating systems:
  
  • 32- and 64-bit versions of Microsoft Windows XP,7, 2003, 2003 R2, 2008, and 2008 R2
  • 32- and 64-bit versions of Red Hat Enterprise Linux 5.0 and later
  • 32- and 64-bit versions of SUSE Linux Enterprise Server 10 and later
  • 32- and 64-bit versions of Asianux 3 and later
  • 32- and 64-bit versions of Debian 4
  • 32- and 64-bit versions of Ubuntu 7.04 and later
  • 32- and 64-bit versions of Sun Solaris 10 U4 and later
    
  Notes:
  • Jumbo frames are not supported in Solaris Guest OS with VMXNET 2 or VMXNET 3.
  • Fault Tolerance is not supported on a virtual machine configured with a VMXNET 3 vNIC in vSphere 4.0, but is fully supported on vSphere 4.1.

Nuevo TR: NetApp Storage Best Practices for VMware vSphere 5

Nuevo documento de December 2011 actualizado tambien a la version vSphere 5 (ESXi)

Lo podeis descargar del siguiente enlace: http://media.netapp.com/documents/tr-3749.pdf

Del documento destacaria la referencia al "Storage DRS" con los "Datastore Cluster" de la nueva version vSphere 5, y las recomendaciones sobre su configuracion:

Following are the key recommendations when configuring storage DRS and datastore cluster:
- Set SDRS to manual mode and to review the recommendations before accepting them.
- All datastores in the cluster should use the same type of storage (SAS, SATA, and so on) and have the same replication and protection settings.
- SDRS will move VMDKs between datastores, and any space savings from NetApp cloning or deduplication will be lost when the VMDK is moved. You can rerun deduplication to regain these savings.
- After SDRS moves VMDKs, it is recommended to recreate the Snapshot copies at the destination datastore.
- Do not use SDRS on thinly provisioned VMFS datastores due to the risk of reaching an out-of-space situation.
- Do not mix replicated and nonreplicated datastores in a datastore cluster.
- All datastores in an SDRS cluster must either be all VMFS or all NFS datastores.
- Datastores cannot be shared between different sites.
- All datastore hosts within the datastore cluster must be ESXi 5 hosts.