Quantcast
Channel: VMware Communities: Message List
Viewing all 230299 articles
Browse latest View live

Re: Bootup stuck at Winodow logo screen.

$
0
0

Boot it to safe mode and then disable none Microsoft service (Clean boot) and then restart the machine.

Then check its events and find the root cause. I think, this is OS issue.


Operating System /Remote Service Monitoring Licensing

$
0
0

Hi guys;

 

Could you please tell me, does the installed agent of the End Point Operations Management Solutions  takes another vRops license or it uses the same license of the VM ?

 

Thank you.

 

Regards.

Re: Unable to Install vCenter server 6.0 Update2

$
0
0

Cause

This issue occurs because of the vCenter Server configuration. You see this issue if your vCenter Server uses one of these configurations: 

  • Your system is configured with a Hosts file for mapping of hostnames to IP address:

    vCenter Single Sign-On system pulls Domain Name Server (DNS) information from the guest operating system during the installation. If a Host's file is configured on the Windows system with the shortname rather than the fully qualified domain name (FQDN), this will result in the SSL certificates for vCenter Single Sign-On generating incorrectly. This in turn results in the vCenter Single Sign-On Lookup Service being configured with the FQDN of the system, while the SSL certificates are generated with the shortname of the system the Lookup Service becomes unresponsive.
  • If the system has been multihomed via multiple (v)NIC:

    vCenter Single Sign-On system pulls DNS information from the guest operating system during the installation, if the order of the (v)NICs on the system is setup where the DNS information is incorrect or different than the true hostname of the system resulting in incorrect SSL certificates, either using the hostname or IP address assigned to the (v)NIC. The vCenter Single Sign-On Lookup Service is then configured with the correct FQDN of the system while the SSL certificates are generated with the incorrect FQDN or IP of the system, as a result the Lookup Service becomes unresponsive.

Resolution

This is a known issue affecting vCenter Single Sign-On 5.5 and vSphere Web Client 5.5.

To work around this issue, perform one of these options depending on your environment's configuration:

  • Update the Windows Host's file with the proper FQDN of the vCenter Server.
  • Update the order of the (v)NIC on vCenter Server for proper FQDN resolution.

To Update the Windows Host's file with the proper FQDN of the vCenter Server

  1. Connect to the vCenter Server system via remote desktop or console.
  2. Navigate to this directory containing the Host's file:

    %systemroot%\system32\drivers\etc\

  3. Open the hosts file using a plain text editor.
  4. Locate the entry for the the vCenter Server's hostname. Ensure that the hostname has been entered as the FQDN as well as the proper case as reported when running the hostname oripconfig /all commands via command prompt.

    For example, use this mode:

    ...

    # localhost name resolution is handled within DNS itself.
    # 127.0.0.1 localhost
    # ::1 localhost
    192.169.1.10 vCenterServer.domain.local
    ...


  5. Uninstall that instance of vCenter Single Sign-On 5.5 and clean up the %ProgramData% installation directory. For more information, see the Resolution section of Installing or upgrading vCenter Single Sign-On 5.5 fails with the error: vCenter Single Sign-On Setup Wizard ended prematurely because of an error (2059481).
  6. Reinstall vCenter Single Sign-On 5.5 to generate the SSL certificates using the proper FQDN. For more information, see Installing vCenter Single Sign-On 5.5 on a Microsoft Windows platform (2058239)

 

Please refer to below kb for more info:https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2062921

 

Thanks,

Amz

Re: workspace 2.0 external access error DNS_PROBE_FINISHED_NXDOMAIN

WMI Query Issue with "ExistingPageFiles" Key

$
0
0

Although this is technically not PowerCLI, the core code uses it to manipulate WMI further down the road.

 

Synopsis:

 

I am trying to set the pagefile on all servers from 2008 and above to system on the C: drive only. If I run the following code:

 

   $a = Get-WmiObject Win32_ComputerSystem -EnableAllPrivileges
   $a.AutomaticManagedPagefile = $True
   $a.Put()

 

The code works, and in server 2008 there is now a tickbox for "Automatically manage paging file size for all drives" whereas this feature wasnt available in Server 2003.

 

This is where my problem states, the following key is available in server 2008 and above:

 

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\ExistingPageFiles

 

However I dont know how to query it via WBEMTEST. Does anyone know where it resides?

 

If you run the code above however, and you have 2 separate drives that are custom sized then it simply sets both drives to "system managed" which is greyed out and ticks "Automatically manage paging file size for all drives".

 

I cannot seem to find any material that will allow me to probe the ExistingPageFiles registry key directly.

 

Any help would be greatly appreciated

Re: VMware Horizon, перенаправление записи звука в терминальный сеанс

$
0
0

Суть у нас в том что бы как можно больше людей могли нормально работать... у нас стоят моноблоки с очень слабыми процессорами, и они не тянут даже антивирус... а работаю удаленно в личной сессии терминалов, все сотрудники могут работать без проблем) а так как сервер у нас под это дело есть только один, решили что нужен терминальный сервер. Но если не решиться вопрос с перенаправлением микрофона, то конечно сделаем с линк клонами... надеюсь сервак сможет потянуть 15 машин.

Re: how to import ovf from www using powercli?

$
0
0

thank you Sir, could you please post the script importing local ovf file? it still can teach me a lot, thanks

 

Simon

protect VM through powercli not working: Not authenticated into SRM

$
0
0

We are trying to automate the protection of a VM through powercli

We followed the several posts available on internet like fe http://www.automate-it.today/automating-srm-powercli/

However we end up with the error Not authenticated into SRM <remote vcenter server name>

 

What's not working in our enviromnemt is to log in with -RemoteUser or -RemoteCredential to SRM although the user specified has the priviliges to log in.

 

Anyone a suggestion how to solve this?


Re: arping can linux guest on esxi but no ip is working

$
0
0

Jul 28 10:36:50 switchff3a2d 3SWCOS %3SWCOS-I-LOGACLINETPORTS: gi1/1/2: permit ACE IPv4(UDP) 0.0.0.0(68) -> 255.255.255.255(67),trapped 

 

thats what comes up on the switch syslog when i try and get a dhcp address on either interface of the ubuntu clilent.

 

Jul 28 10:41:00 bwell dhcpd[12197]: DHCPDISCOVER from 00:0c:29:0b:ca:be (usrvtest1) via enp10s0.200

Jul 28 10:41:00 bwell dhcpd[12197]: DHCPOFFER on 192.168.2.8 to 00:0c:29:0b:ca:be (usrvtest1) via enp10s0.200

Jul 28 10:41:00 bwell dhcpd[12197]: DHCPDISCOVER from 00:0c:29:0b:ca:be (usrvtest1) via enp10s0.200

Jul 28 10:41:00 bwell dhcpd[12197]: DHCPOFFER on 192.168.2.8 to 00:0c:29:0b:ca:be (usrvtest1) via enp10s0.200

Jul 28 10:41:00 bwell dhcpd[12197]: DHCPDISCOVER from 00:0c:29:0b:ca:be (usrvtest1) via 192.168.2.254

Jul 28 10:41:00 bwell dhcpd[12197]: DHCPOFFER on 192.168.2.8 to 00:0c:29:0b:ca:be (usrvtest1) via 192.168.2.254

Jul 28 10:41:00 bwell dhcpd[12197]: DHCPDISCOVER from 00:0c:29:0b:ca:be (usrvtest1) via 192.168.2.254

Jul 28 10:41:00 bwell dhcpd[12197]: DHCPOFFER on 192.168.2.8 to 00:0c:29:0b:ca:be (usrvtest1) via 192.168.2.254

 

discover offer but no answers from the dhcpd thats strange too. dhcpd works and answers normal when not coming from the esxi/workstation12 host.

 

would be great if one of the experts here could help me. im going nuts...

Purple Screen - NMI/LINT1 motherboard interrupt. This is a hardware problem; please contact your hardware vendor

$
0
0

Ciao a tutti,

ho un cluster HA composto da 4 HP DL380 g8 con ESXi 5.1 UP3 e lunedì pomeriggio un host è andato in crash visualizzando la PSOD con l'immagine che segue:

 

P60725-165121.jpg

Le macchine virtuali sono state spostate, in automatico, sui restati nodi e i servizi sono stati erogati correttamente.

Ho riacceso il server interessato e tutt'ora funziona correttamente. Investigando un pò, ho letto che potrebbe essere legato al firmware della ILO che deve essere superiore alla 1.5, la nostra è 1.4.

Ho controllato i log vari ma non ho trovato nessuna segnalazione della problematica, mentre aprendo il dump ho trovato che il PSOD è accaduto alle 14.26 e che le macchine virtuali hanno retto fino alle 16.32, momento in cui sono state "switchate"

Vi allego un txt con la parte del log del dump e vi chiedo se potete aiutarmi a capire se è solo necessario l'aggiornamento della ILO o ci sono altri passi da fare.

 

 

Grazie

Re: VMware Horizon, перенаправление записи звука в терминальный сеанс

$
0
0

Эм, я имею в виду зачем при наличии лицензии horizon вообще использовать службы терминалов, а не использовать vdi? Службы терминалов я могу развернуть и без horizon.

Re: How to change "display name" of the esx host in vCenter?

$
0
0

Hi,

 

the display name is set to how you add the host to the vCenter.

So to display the hostname or the FQDN remove the host form vCenter and add it again using not the ip, but the FQDN.

 

Tim

Re: ESXi login failure

$
0
0

ok but the problem is not at that point. Actually I can't connect to ESXi so I can't run the setup install of PSC.

 

As I've said before, I need to restart Managment and Agents to get acces to my ESXi

Re: VMware Workstation 12 Player crashes to desktop loading Windows 10 VM after host crashed

$
0
0

Hello,

 

Welcome at the VMware community forums.

 

When I looked at your attached log I noticed the lines above the backtrace:

2016-07-22T11:36:11.120-07:00| mks| I125: GLManager: Emulating point sprites with quads.
2016-07-22T11:36:11.120-07:00| mks| I125: GLManager: using core profile
2016-07-22T11:36:11.120-07:00| mks| I125: GLManager: maxVertAttrStride = 2048
2016-07-22T11:36:11.120-07:00| mks| I125: GLManager: Host supports 18 vertex texture units, 18 fragment texture units, 18 geometry texture units and 54 combined texture units.
2016-07-22T11:36:11-07:00[+0.059]| mks| W115: Caught signal 4 -- tid 20708 (addr 7F5908E330C0)
2016-07-22T11:36:11-07:00[+0.059]| mks| I125: SIGNAL: rip 0x7f5908e330c0 rsp 0x7f5901d39d20 rbp 0x7f5901d39de0
2016-07-22T11:36:11-07:00[+0.059]| mks| I125: SIGNAL: rax 0x0 rbx 0x0 rcx 0x0 rdx 0x0 rsi 0x7f58f83086b0 rdi 0x10

 

So it seems that the VM crashes while configuring the graphical backend.

Signal 4 is "illegal instruction"  (see signal(7) - Linux manual page )

 

The  first thing I would do is ... make a copy of the VM to another disk so that whatever happens in the future you can go back to this pristine copy.


Then I would try and see if you can boot the VM after disabling 3D support under display settings.

 

--

Wil

Re: how to import ovf from www using powercli?

$
0
0

Drop me an email (link on my blog).
The script is still very raw, don't want to make it public yet


vcenter SSO - AD LDAP login problems

$
0
0

Hello everybody,

 

hope you're doing okay

 

I have a question regardings vcenter SSO login with Identity source type set as : Active Directory as a LDAP server. We have two vcenters (different geo locations) and in each there is a virtual domain controller server (win 2012) .


Now, our situation and problem is , that when the primary DC is not accessible or turned off we cannot authenticate anymore using secondary server. When secondary is turned off we can still authenticate.

 

These are the settings on both vcenters. We tested telnet connectivity on port 389 , and it works for both.

Both vcenters are at version 5.5 build 3252642

 

Any advice would be great about this

Thank you

 

2016-07-28 11_20_07-vSphere Web Client.png

 

BR

Damir Dukaric

Re: how to import ovf from www using powercli?

$
0
0

just send it in e-mail, thank you Sir,

 

Simon

Re: WMI Query Issue with "ExistingPageFiles" Key

$
0
0

Can't you just do?

 

(Get-ItemProperty-Path'HKLM:\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management').ExistingPageFiles

 

Re: VMINFO.PL: how to list the power state of the VM????

$
0
0

Hi,

 

Not sure if you have got the answer but it is quite easy & have done it myself. I came across this need of getting Power State few days back.

 

I have done few things that I am mentioning here :

 

1. Added a if condition for PowerState under foreach() loop like below-

 

elsif($_ eq 'powerState') {

if (defined($vm_view->runtime) && defined ($vm_view->runtime->powerState)) {

print_log($vm_view->runtime->powerState->val,"powerState", "Power State ");

}

}

 

2. I have updated the powerstate definition under %opts

powerstate' => {

      type    => "=s",

      help    => "State of the virtual machine: poweredOn or poweredOff",

      required => 0,

  }

 

3. Added "powerState" to validate() >> @valid_properties

 

With this I am able to manage to get the below output with Power State of the VM in context-

 

<Root>

<VM>

<Name>vm001</Name>

<noCPU>2</noCPU>

<memorySize>4096</memorySize>

<virtualDisks>1</virtualDisks>

<template>0</template>

<vmPathName>[hfesx005-data] vm001/vm001.vmx</vmPathName>

<guestOS>CentOS 4/5/6/7 (64-bit)</guestOS>

<guestId>centos64Guest</guestId>

<hostName>localhost.localdomain</hostName>

<ipAddress>16.71.85.181</ipAddress>

<VMwareTools>VMware Tools is running and the version is current</VMwareTools>

<cpuUsage>0 MHz</cpuUsage>

<hostMemoryUsage>742 MB</hostMemoryUsage>

<guestMemoryUsage>1064 MB</guestMemoryUsage>

<powerState>poweredOn</powerState>

<overallStatus>The entity is OK</overallStatus>

</VM>

</Root>

 

Hope this will help.

 

Regards

Akshat Tambe

Re: WMI Query Issue with "ExistingPageFiles" Key

$
0
0

The problem is, I need to change the details on 90 servers.

 

If you run a foreach loop, you cannot remotely authenticate using remote registry, but you can with Get-WMIObject and Set-WMIObject.

 

I really wanted to avoid having to use WMI at all because the registry is easier to target.

Viewing all 230299 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>