Are you the publisher? Claim or contact us about this channel


Embed this content in your HTML

Search

Report adult content:

click to rate:

Account: (login)

More Channels


Channel Catalog


Channel Description:

Most recent forum messages

older | 1 | .... | 5498 | 5499 | (Page 5500) | 5501 | 5502 | .... | 5577 | newer

    0 0
  • 06/02/17--22:51: Re: move-vm svMotion error
  • Can you perhaps show us the code you are using.
    And perhaps an extract of your CSV file?

     

    One way or the other, there is a '+' appearing on cmdlet.


    0 0

    Hi All

    I will provide vsphere esxi to the customer for new project, but I want to find stable Build Number for production

    Is VMware have official document or other information like GA/RGA/MGA release?

     

     

    Sample:

    GA = General Availability
    RGA = Recommended General Availability - Recommended by official
    MGA = Mandatory General Availability - Minimum request

     

    please help thanks~~


    0 0

    Just  quick update for those attempting this.

     

    I bite the bullet and vmontioned the two VMs in the vApp. As  I was moving the vApp VMs to a different host in the same cluster it is a simple matter of migrating both VMs. No need to shutdown the vApp.

     

    Just be sure the host you are moving it to has the same networking config but this should not be a problem as any host in the same cluster would have the same network config anyway.


    0 0

    I want to Use Samsung Note 5 Pressure Sensitivity on Desktop Softwares Like Photoshop and Illustrator So, Is VMWare Provide Redirection of it?


    0 0

    Hello

     

    For those customers wanting to move their VIO VM's including the vApp all that is needed if you are moving to a different host in the same cluster is vmotion.

     

    We have successfully completed this with VIO 3.0 and there was zero down time and everything went smoothly with no impact on customer Instances.

    So for thse spending weeks looking for a definitive answer then here it is. As long as you are moving the VIO to a host in the same cluster then vmotion is your answer. If you are moving to a different cluster then DO NOT follow this guide as we have NOT attempted this and it is outside the scope of this article.


    0 0

    You mean is "/etc/resolv.conf" ?


    0 0

    In VRA6.2 I have used below module to update Archive Days. But in 7.2 the same is not working. Any idea on how to do it?

     

    ironPropretiesValue = new Properties();

    ironPropretiesValue.put("ExpireDays", a_IronArchivedays);

    actionResult = System.getModule("com.vmware.library.vcac").updateVCACEntity(hostId,modelName,entitySetName,entityIdString,ironPropretiesValue,links,headers) ;

     

     

    Untitled.png

     

    All I need is a solution to set "Destroy On" date to user requested date and get the VM deleted on that day.


    0 0

    Hello.

    I want to install VMWare ESXi 6.5 on HP ProLiant DL370 G6 Server but I got "LINT1 motherboard interrupt" error. How can I solve it? VMWare ESXi 4.1 not have any problem with this server model !!!

    This server model is VMWare and Citrix ready: HPE Support document - HPE Support Center

    20170603_104909.jpg

     

    Thank you.


    0 0

    The parameter set is depending on the vSphere version. I have tested against an ESXi v6.0U2 server.

     

    You can see the parameters needed using the following command:

    $esxcli.system.module.parameters.set

     

    The output of the preceding command is the following for me:

    TypeNameOfValue     : VMware.VimAutomation.ViCore.Util10Ps.EsxCliExtensionMethod

    OverloadDefinitions : {boolean set(boolean append, boolean force, string module, string parameterstring)}

    MemberType          : CodeMethod

    Value               : boolean set(boolean append, boolean force, string module, string parameterstring)

    Name                : set

    IsInstance          : True

     

    In the value of the OverloadDefinitions and Value properties, you can see the parameter set, where append is the first parameter, force is the second parameter, module is the third parameter and parameterstring is the fourth parameter. For the parameters you don't want to specify, you have to use $null.

     

    Another solution will be to use the Get-EsxCli version 2 interface with the -V2 parameter. In this case, you can get the parameters in a hash table using the CreateArgs() method, using the following commands:

    $esxcliv2 = Get-VMHost -Name 192.168.0.201 | Get-EsxCli -V2

    $Parameters = $esxcliv2.system.module.parameters.set.CreateArgs()

     

    Now, the variable $Parameters contains the parameter set in the following hash table:

    Name                           Value

    ----                           -----

    module                         Unset, ([string])

    parameterstring                Unset, ([string])

    append                         Unset, ([boolean], optional)

    force                          Unset, ([boolean], optional)

     

    You can set the required parameter values

    $Parameters['module'] = 'lpfc'

    $Parameters['parameterstring'] = 'lpfc_devloss_tmo=30'

     

    And finally, use the Invoke() method to run the following command with the parameter set:

    $esxcliv2.system.module.parameters.set.Invoke($Parameters)


    0 0
  • 06/03/17--01:00: script
  • Hi experts

     

    I need an help, i want to install vmware tools from the scrip(My goal is to install to vmware tools and shutdown virtual machines) and manually upgrade virtual hardware and power on the virtual machines.

    I am looking for a script to install vmware tools

     

    $vCname = Read-Host “Enter the vCenter or ESXi host name to connect:”

    if (-not (Get-PSSnapin VMware.VimAutomation.Core -ErrorAction SilentlyContinue)) {

    Add-PSSnapin VMware.VimAutomation.Core

    }

    Connect-VIserver $vcname

    $VirtualMachines = Get-Content "VMList.txt"

    foreach ($vm in (Get-VM -Name $VirtualMachines)){

    if($vm.config.Tools.ToolsUpgradePolicy -ne "UpgradeAtPowerCycle") {

    $config = New-Object VMware.Vim.VirtualMachineConfigSpec

    $config.ChangeVersion = $vm.ExtensionData.Config.ChangeVersion

    $config.Tools = New-Object VMware.Vim.ToolsConfigInfo

    $config.Tools.ToolsUpgradePolicy = "UpgradeAtPowerCycle"

    $vm.ExtensionData.ReconfigVM($config)

    Write-Host "Update Tools Policy on $vm completed" -ForegroundColor green

    }

    else {

    Write-Host "$vm couldn't found on vCenter Server" -ForegroundColor red

    }

    }


    0 0

    Thanks for the answer. Since the described effects take some time to appear, testing needs some days to see if the possible change is enduring.

     

    I looked into your suggestions and noticed a difference in

    1. Under Scale high resolution, select All View Modes.

    I had „Unitity“ selected. After changing it, the jumping to a lower res and smaller VM window did not reappear yet. I keep watching.

     

    All the rest was as suggested here. Your suggestion of playing with the Win DPIs did not change anything.

     

    I still find lagre black areas when reopening Quicken. The „Welcome“ window is most of the time completely black. Switching between full screen and windowed mode brings parts of the black areas back.

     

    Still no real solution for the glitches.

     

    Thanks MK


    0 0

    Thanks bfs, I think this has given me a clue. From vmware-ui-nnnn.log, vmware-ui has an issue communicating with vmware-authd - so it makes sense that the vmware-ui process needs to get UAC directly.

     

    The relevant portion of the log file is below... anyone know where the vmware-ui process is trying to read the port number from, and why it might be having trouble doing so? I did google, but didn't find anything definitive.

     

    Thanks

     

    2017-06-02T23:40:09.013+10:00| vthread-10| I125: VTHREAD initialize thread 10 "vthread-10" host id 1336

    2017-06-02T23:40:09.013+10:00| vthread-10| I125: CnxAuthdConnect: Returning false because CnxAuthdConnectPipe failed

    2017-06-02T23:40:09.013+10:00| vthread-10| I125: CnxConnectAuthd: Returning false because CnxAuthdConnect failed

    2017-06-02T23:40:09.013+10:00| vthread-10| I125: Cnx_Connect: Returning false because CnxConnectAuthd failed

    2017-06-02T23:40:09.013+10:00| vthread-10| I125: Cnx_Connect: Error message: Failed to read vmware-authd port number: Cannot connect to VMX: F:\VMWare\Win10B\Win10B.vmx

    2017-06-02T23:40:09.013+10:00| vthread-10| I125:

    2017-06-02T23:40:09.013+10:00| vthread-10| I125: Vix: [1336 foundryVMPowerOps.c:5940]: Error VIX_E_HOST_TCP_SOCKET_ERROR in FoundryVMOpenSocketToVMXThroughAuthd(): unable to contact authd: Failed to read vmware-authd port number: Cannot connect to VMX: F:\VMWare\Win10B\Win10B.vmx

    2017-06-02T23:40:09.013+10:00| vthread-10| I125:

    2017-06-02T23:40:09.049+10:00| vthread-7| I125: VTHREAD initialize thread 7 "vthread-7" host id 1120

    2017-06-02T23:40:09.049+10:00| vthread-7| I125: CnxAuthdConnect: Returning false because CnxAuthdConnectPipe failed

    2017-06-02T23:40:09.049+10:00| vthread-7| I125: CnxConnectAuthd: Returning false because CnxAuthdConnect failed

    2017-06-02T23:40:09.049+10:00| vthread-7| I125: Cnx_Connect: Returning false because CnxConnectAuthd failed

    2017-06-02T23:40:09.049+10:00| vthread-7| I125: Cnx_Connect: Error message: Failed to read vmware-authd port number: Cannot connect to VMX: F:\VMWare\Win10B\Win10B.vmx

    2017-06-02T23:40:09.049+10:00| vthread-7| I125:

    2017-06-02T23:40:09.049+10:00| vthread-7| I125: Vix: [1120 foundryVMPowerOps.c:5940]: Error VIX_E_HOST_TCP_SOCKET_ERROR in FoundryVMOpenSocketToVMXThroughAuthd(): unable to contact authd: Failed to read vmware-authd port number: Cannot connect to VMX: F:\VMWare\Win10B\Win10B.vmx

    2017-06-02T23:40:09.049+10:00| vthread-7| I125:

    2017-06-02T23:40:09.097+10:00| vigorCnx| I125: VTHREAD start thread 7 "vigorCnx" host id 892

    2017-06-02T23:40:09.127+10:00| vmui| I125: SnapshotTree: Emitting refresh (F:\VMWare\Win10B\Win10B.vmx)

    2017-06-02T23:40:09.148+10:00| vmui| I125: FILE: FileCreateDirectoryRetry: Non-retriable error encountered (C:\ProgramData\VMware): Cannot create a file when that file already exists (183)

    2017-06-02T23:40:09.157+10:00| vmui| I125: Setting power state poweredOff

    2017-06-02T23:40:09.475+10:00| vigorCnx| I125: VigorOfflineGetToolsVersion: updated tools version to 2826

    2017-06-02T23:40:09.522+10:00| vmui| I125: cui::VMMKS::OnVMStateChanged: alive = 0

    2017-06-02T23:40:09.524+10:00| vmui| I125: wui::ipc::CUnityHelper::Connect: Creating connection-ready notification event, name: {4E38F789-D310-437E-B9E7-2371727ABF8E}

    2017-06-02T23:40:09.524+10:00| vmui| I125: wui::ipc::CUnityHelper::LaunchDaemon: Running cmd line: "C:\Program Files (x86)\VMware\VMware Workstation\vmware-unity-helper.exe" -d -e:{4E38F789-D310-437E-B9E7-2371727ABF8E}

    2017-06-02T23:40:09.640+10:00| vmui| I125: cui::VMBindingUnityMgr::OnGuestCanRunUnityChanged: The guest is a supported version of Windows, checking Tools status. Version status: 5, running status: 3

    2017-06-02T23:40:09.640+10:00| vmui| I125: cui::VMBindingUnityMgr::OnGuestCanRunUnityChanged: Tools status is not INSTALLED

    2017-06-02T23:40:09.661+10:00| vmui| I125: VMMgr: Finished opening VM at /vm/#201625e0e6c7cbea/ from F:\VMWare\Win10B\Win10B.vmx

    2017-06-02T23:40:09.686+10:00| vmui| I125: CVMUIApp::OpenTabInt: opened F:\VMWare\Win10B\Win10B.vmx

    2017-06-02T23:40:09.686+10:00| vmui| I125: Switched to tab: F:\VMWare\Win10B\Win10B.vmx

    2017-06-02T23:40:09.691+10:00| vmui| I125: SnapshotTree: Populating (F:\VMWare\Win10B\Win10B.vmx)

    2017-06-02T23:40:09.761+10:00| vmui| I125: wui::control::MKSPanel::UpdateMKSLayout: MKS view is not initialized or not rendering.

    2017-06-02T23:40:09.761+10:00| vmui| I125: wui::control::MKSPanel::UpdateMKSLayout: MKS view is not initialized or not rendering.

    2017-06-02T23:40:09.761+10:00| vmui| I125: wui::control::MKSPanel::UpdateMKSLayout: MKS view is not initialized or not rendering.

    2017-06-02T23:40:09.794+10:00| vmui| I125: CVMUIFrame::OnGuestTopologyChanged: Passing main UI rect: 0x0 @ 0,0

    2017-06-02T23:40:09.794+10:00| vmui| I125: cui::MKSScreenWindowCoordinator::HandleGuestTopologyChange: main UI rect: 0x0 @ 0,0

    2017-06-02T23:40:09.794+10:00| vmui| I125: cui::MKSScreenWindowCoordinator::HandleGuestTopologyChange: Found 0 present screens

    2017-06-02T23:40:09.794+10:00| vmui| I125: cui::MKSScreenWindowCoordinator::HandleGuestTopologyChange: Windows for extra guest monitors will not be shown

    2017-06-02T23:40:09.794+10:00| vmui| I125: cui::MKSScreenWindowCoordinator::HandleGuestTopologyChange: setting main view to all displays

    2017-06-02T23:40:09.876+10:00| vmui| I125: VMHSGetDataFileKey: Could not get the dataFileKey from VMDB

    2017-06-02T23:40:09.878+10:00| vmui| I125: VMHSGetDataFileKey: Could not get the dataFileKey from VMDB

    2017-06-02T23:40:09.910+10:00| vmui| I125: VMHSGetDataFileKey: Could not get the dataFileKey from VMDB

    2017-06-02T23:41:44.179+10:00| vmui| I125: VMHSVMCbPower: F:\VMWare\Win10B\Win10B.vmx, Setting state of VM to powerOn with option soft


    0 0

    Below command will show the fc link status too along with all drivers,model details.

     

    #esxcfg-scsidevs -a


    0 0
  • 06/03/17--01:33: Re: script
  • Update tools at power cycle option is best option for tool upgrade. Find the below script which will enable this option in all VMs and also will give you the result in csv files.

    First get connect with the Vcenter server on which you are going to perform this then list the VMs in VMname.txt if it is not for all VMs else use only Get-VM.

    -------------------------------------------------------------------------------

    #list name of servers on which changes required in file

    $n = Get-Content "D:\Jitu\VMName.txt"

    foreach ($b in $n){

        #Command will extact details of VM

    $vm = Get-VM -Name $b | % {Get-View $_.ID}

    $value = New-Object VMware.Vim.VirtualMachineConfigSpec

    $value.tools = New-Object VMware.Vim.ToolsConfigInfo

        #This is where you mention which policy need to enter ,here we only need to enable checkbox to uprade vmware tools at power cycle. Same has been selected

    $value.tools.toolsUpgradePolicy = "upgradeAtPowerCycle"

    $vm.ReconfigVM_Task($value)

        #Below command will export the policy details of all VMs(updated/yet to be updated) in respective VC in csv format.

    get-view -ViewType virtualmachine | select name,@{N='ToolsUpgradePolicy';E={$_.Config.Tools.ToolsUpgradePolicy } } | Export-Csv "D:\ToolsOutput.csv" -UseCulture -NoTypeInformation

    }

     

     

        #or if we only need to export of tasks executed for number of VM then remove last line and add below instead of get-view:

    $vm.ReconfigVM_Task($value)| Export-Csv "D:\ToolsOutput.csv" -UseCulture -NoTypeInformation

    --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------


    0 0

    Found a fix...   this is taken from a Microsoft forum (http://answers.microsoft.com/en-us/windows/forum/windows_7-networking/problems-with-kb-3161608-and-kb-3161639/2cd5ffb3-c…) since that patch broke a lot more than just Vcenter.

     

    Basically add this registry entry and you're back in business:

     

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\KeyExchangeAlgorithms\Diffie-Hellman]

    "ClientMinKeyBitLength"=dword:00000200

     

    Do it on client machines and you are done.


    0 0

    Yes that works.  Thanks.


    0 0

    Hi,

     

    I have the problem that with the previous version of Windows Insider 16199 Bridging worked flawlessly for all of my virtual machines.

     

    Under my networks I could see a VMware Network Adapter. This I don't see anymore under 16199.

     

    Since Build 16199 no chance to get it to work.

     

    I'll already tried a reset of network in VMWare Workstation Pro 12.5.6 --> no success

     

    I can't even add the service VMWare Bridge Protocol --> Access denied

     

    I'll already deinstalled and reinstalled the software --> no success

     

    Has anybody of you the same problem?


    0 0
  • 06/03/17--02:52: Re: NSX Edge Gateways
  • You can use edge HA


    0 0
  • 06/03/17--03:02: Re: script
  • hi

    thanks alot, wht does upgradeAtPowerCycle mean

     

    This will not restart the servers right?

    My plan is to shutdown the servers after installing vmware tools


    0 0
  • 06/03/17--03:41: Redeploy Controllers
  • We have removed the controller VM after attempting to delete them from NSX. Now all 4 controllers are in a disconnected state and we have no way of deploying new controllers as the IP pool states that the IP is already in use. We have modified the IP pool so that it uses the IP not us use but still we cannot deploy a new controller while the controller cluster is in a disconnected state.

     

    We have tried to remove them but receive the error - cannot remove using this API.

     

    We have tried removing them using the REST API but still no dice.

     

    As the controller VMS are no longer there how can we deploy new Controllers or remove the old ones.


older | 1 | .... | 5498 | 5499 | (Page 5500) | 5501 | 5502 | .... | 5577 | newer