Arquivo do mês: junho 2013

Error de VMware Converter: Unable to obtain hardware information for the selected machine.

NOTE: If you need this article in english, click here. Also, I have a new article in english on this problem troubleshooting (broader), available on this link.

Averiguando este problema hoy en la conversión de un Windows 2003 Server, fue posible verificar el siguiente:

  • Se estavan utilizando credenciales de administrador local;
  • Habia acceso sin firewall al servidor;
  • El agente del converter se instalava con exito en el server;
  • El error ocurría tanto en una conversión remota cuanto instalando el Converter en la máquina a ser convertida (source).

En los logs del agente del converter (podes encontrarlos en %ALLUSERSPROFILE%\VMware\VMware vCenter Converter Standalone Agent\logs\vmware-converter-agent-1.log) había el siguiente error:


2013-06-10T16:52:32.997-03:00 [04488 warning 'Default'] Failed to get capacity for \\.\PhysicalDrive0: error opening disk device: The process cannot access the file because it is being used by another process (32) 2013-06-10T16:52:32.997-03:00 [04488 warning 'Default'] Skipping hard disk '\\.\PhysicalDrive0' 2013-06-10T16:52:32.997-03:00 [04488 warning 'Default'] Failed to get capacity for \\.\PhysicalDrive1: error opening disk device: The process cannot access the file because it is being used by another process (32) 2013-06-10T16:52:32.997-03:00 [04488 warning 'Default'] Skipping hard disk '\\.\PhysicalDrive1' .... 2013-06-10T16:52:32.997-03:00 [04488 error 'Default'] [LiveWindowsComputer] Unable to find any disks attached to the computer.

El error me dejó curioso: yo sí podia ver el contenido del C:, y el D:, pero el Converter no. Analisando lo que había instalado, fue posible encontrar el HP Insight Manager instalado.Este software dealguna forma estaba bloqueando el acceso al disco al Converter del modo que necesita. Simplemente bajando los servicios de HP fue posible proceder con la conversión.

Con la ayuda de Guilherme Pfeifer.

Anúncios

Que usuário utilizar para adicionar un Identity Source no SSO do vCenter 5.1?

Se voce já instalou alguma vez um vCenter 5.1 e teve que configurar um Identity Source para o  SSO, certamente teve que decidir que usuário utilizar para se registrar no AD/LDAP/NIS na configuracão dos Identity Sources:

Imagem

Na pressa as vezes usamos nosso próprio usuário, ou algum administrador, mas se algum dia a senha do usuário utilizado é alterada, é necessário reconfigurar o Identity Source e alterar a senha. Por isso, o ideal é que um usuário de servicos seja utilizado, que nunca tenha que ter a senha trocada ou se bloqueie.

O documento http://pubs.vmware.com/vsphere-51/index.jsp?topic=%2Fcom.vmware.vsphere.security.doc%2FGUID-B23B1360-8838-4FF2-B074-71643C4CB040.html mostra exatamente isso:

When you use the authentication type Password for an identity source, you must update the identity source details whenever the password changes for the configured user. You update the password on the Edit Identity Source dialog box.

If the user account is locked or disabled, authentications and group and group and user searches in the Active Directory domain will fail. The user account must have read-only access over the User and Group OU, and must be able to read user and group attributes. This is the default Active Directory domain configuration for user permissions. VMware recommends using a special service user to ensure that the password does not expire and lock out or disable the user account.

Cmm a ajuda de Mauricio Altamura

Que usuário utilizar para agregar un Identity Source al vCenter SSO?

Si ya instalaste el vCenter 5.1 alguna vez, y tuviste que configurar un Identity Source en el SSO, seguro te preguntaste que usuário utilizar para registrarte en el AD/LDAP/NIS, en la pantalla de configuración de Identity Sources:

Imagem

A veces, en el apuro, usas tu proprio usuário, o algun admin, pero si algun dia cambias tu password, o la password del usuário que utilizastes, tenés que volver a la pantalla de configuración y tenés que cambiar también. Por eso, es ideal que utilices un usuário de servicios, que nunca tenga que cambiar password o se bloquee.

El doc http://pubs.vmware.com/vsphere-51/index.jsp?topic=%2Fcom.vmware.vsphere.security.doc%2FGUID-B23B1360-8838-4FF2-B074-71643C4CB040.html comenta acerca de eso:

When you use the authentication type Password for an identity source, you must update the identity source details whenever the password changes for the configured user. You update the password on the Edit Identity Source dialog box.

If the user account is locked or disabled, authentications and group and group and user searches in the Active Directory domain will fail. The user account must have read-only access over the User and Group OU, and must be able to read user and group attributes. This is the default Active Directory domain configuration for user permissions. VMware recommends using a special service user to ensure that the password does not expire and lock out or disable the user account.

Con la colaboración de Mauricio Altamura