Which files do you have issues with? If these files are .vmdk files, I'm afraid you'll need to find a way to get access to the files.
Did you - after backing up the system - check the HDD(s) for logical/physical errors using e.g. the chkdsk command line utility?
André
As a system admin
1. Go to CI Class Manager and select the class you want the field to be created in. For example, in the applications class, Virtual Machine Instances class, or a parent class so that it is inherited into both classes.
2. Create the field as a Date type and Save. Take note of the column_name of the field to use in the resource mapping.
3. Go to an existing resource of that class and configure the resource form layout so that you see the field on those resources.
4. Go to Resource Mappings and click on the the resource mapping of the resource. Add "lease.end":"column_name" to the Payload CI_Details and click Update
5. Go to Properties and click on the ResourcesAndCMDBImportLastRuntime system property. Clear the Value field and Update. This will update existing resources when the scheduled import is run. If you don't, only new resources will get updated.
6. Go to Scheduled Imports and Execute the importResourcesAndCMDB scheduled import. Wait for it to be processed in Scheduled Import Queues.
7. Add the field to your resource summary screens. Your resource will have the date from vRA populated with time as 00;00;00.
So something I found today was the service that installs with the plugin was not starting even though it was set to start Automatically. Service is called VMware CIP Message Proxy Service. I changed startup type to Automatic (delayed start) and it's working for me now.
See if this helps:
$doathing = $false # <Set this to $true to do a thing! set to $false to see what it would do!
$vmGroups = @{'Group01'='dc0'
'Group02'='file0' 'Group03'='fs0' 'Group04'='web'}
$i = 1
do
{
#decipher what things we are doing things to! $groupNumber = "{0:D2}" -f [int]$i $groupName = "Group" + $groupNumber $groupVms = Get-VM | where {$_.Name -match $vmGroups.$groupName -and $_.powerstate -eq 'PoweredOff'} #start the Vms! foreach ($Vm in $groupVms) { Write-Host "Starting $($Vm.Name)" if ($doathing -eq $true){$Vm | Start-VM}else{Write-Host "Didn't start VM $($Vm.Name) because doathing is false!"} } #wait for tools on each Vm! foreach ($Vm in $groupVms) { Write-Host "Waiting for tools on $($Vm.Name)" if ($doathing -eq $true){$Vm | Wait-Tools}else{Write-Host "Didn't wait for tools on VM $($Vm.Name) because doathing is false!"} } $i++
}
while($i -le $vmGroups.Count)Don't worry... your both vCenter servers can run simultaneously without affect each other.
Both vCenters should be at the same major version, see: https://storagehub.vmware.com/#!/vsphere-replication/vsphere-replication-faq/introduction-and-general-information-4
Can I use vSphere Replication to replicate a VM between vCenters running different versions of vSphere Replication (eg. VR 5.5 to 6.0)?
To replicate between vCenters, vSphere Replication requires the same major version (eg. 5.5.x > 5.5.x) of vCenter and vSphere Replication at both source and target. This is the only officially tested and supported configuration. Check the VMware Product Interoperability Matrix if you have any questions about matching vCenter and vSphere Replication versions.
OK, you need to modify the scripting code of action createVirtualDiskFlatVer2ConfigSpec. As the action is sealed/non-editable, you need to duplicate it. Just launch vRO client, find this action in action tree view, right-click on it and select Duplicate action menu. Give it some name, eg. createVirtualDiskFlatVer2ConfigSpecEager and click Submit button.
After that, open the duplicated action for edit, and add the following line after the line diskBackingInfo.thinProvisioned = thinProvisioned;
diskBackingInfo.eagerlyScrub = true;
and the click Save and close button.
Next, you have to modify the workflow Create custom virtual machine to use the new action instead of the original one. It is also sealed, so you need to duplicate it, open the duplicated copy for edit, and replace the call to createVirtualDiskFlatVer2ConfigSpec with call to createVirtualDiskFlatVer2ConfigSpecEager. Click Save and close button, and launch the modified workflow.
That's it, the modified workflow will now create eager zeroed disk. If you want, you can improve the above steps a bit, eg. instead of hard-coding the value of eagerlyScrub you can make it an input boolean parameter to the modified scripting action (much like the existing thinProvisioned parameter) and expose it in the workflow presentation so the user will be able to choose either eager zeroed or lazy zeroed disks.
Hi
I was wondering if anyone has captured bizagi before with appvolumes, and was able to still use non persistent linked clones. The problem with the software is it won't let you use unc paths, mapped drives, and I even tried to create a symlink. If you have please share any solutions you may have used, I'm trying to stay away from persistent desktops, but I don't think I can with this software
http://www.bizagi.com/en/products/bpm-suite/studio
Thanks
I turned off the top tick box for rd "and other data" and quick testing indicates this has fixed the problem.
Thanks
Trying to backup a standalone vSphere host from a Windows 10 workstation. Found this:
Says to use the vSphere CLI. Downloaded and installed v6.5. Downloaded and installed Perl from Perl Solutions | ActiveState.
vicfg-cfgbackup.pl --server=myserver --username=root -s myserver.bak
Got:
Can't locate XML/LibXML.pm in @INC (you may need to install the XML::LibXML module)
(@INC contains: C:\Program Files\VMware\VMware vSphere CLI\Perl\lib C:/Perl/site/lib C:/Perl/lib .) at C:\Program Files\VMware\VMware vSphere CLI\Perl\lib/VMware/VICommon.pm line 11.
BEGIN failed--compilation aborted at C:\Program Files\VMware\VMware vSphere CLI\Perl\lib/VMware/VICommon.pm line 11.
Compilation failed in require at C:\Program Files\VMware\VMware vSphere CLI\Perl\lib/VMware/VIRuntime.pm line 15.
Compilation failed in require at C:\Program Files\VMware\VMware vSphere CLI\bin\vicfg-cfgbackup.pl line 6.
BEGIN failed--compilation aborted at C:\Program Files\VMware\VMware vSphere CLI\bin\vicfg-cfgbackup.pl line 6.
C:\Program Files\VMware\VMware vSphere CLI\Perl\lib contains two folders:
VMware
WSMan
C:\Perl\lib contains a folder called XML but it does not contain LibXML.pm.
Never used Perl but clearly something didn't get installed because LibXML.pm is nowhere to be found.
Found XML-LibXML-2.0128.tar.gz on The CPAN Search Site - search.cpan.org. Unpacked it.
Now what?
How do I install this?
Why wasn't this installed?
Is this the ONLY way to backup a vSphere host?
Don't they test these installers on prisoners before posting them?
Tony Perovic
Compumation, Inc.
Can you confirm is there is no any Update Manager extension registered in your vCenter? If yes, see how to remove them: Cannot remove or disable unwanted plug-ins from vCenter Server and vCenter Server Appliance (1025360) | VMware KB
I have some clue on this now.
I allocated 80GB to one virtual machine, and the memory usage on that virtual machine
(according to look at the property of that folder) is 76MB, and actually, as far as I can think,
I built several large image which may exceeded the memory limit of that virtual machine.
I normally will see 1-2 lines message after power up: like
piix4_smbus host smbus controller not enabled... (or something
related to piix4 bus). Now I don't see that any more.
Seem that some hardware got damaged due to the memory corruption.
Ok, I figured it would be something relatively simple. A weekend away and fresh eyes/brain cells helped!
I'm running a distributed vswitch. Turns out I missed the fact that the uplink port group I created is apparently automatically created as a trunk port.
So I simply changed my (physical) cisco switch ports (that are associated with that uplink port group) from a access to trunk ports, and now all the network tests pass and I have my first working vsan Datastore.
Whew...
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 60
switchport mode trunk
I need to setup a new infrastructure, and I try confirmation about my choices.
i have the following infrastructure:
4 different site connected in MPLS
Site 1 with 13 host
Site 2 with 13 host
Site 3 with 2 host
Site 4 with 2 host
my idea is to install 2 vCenter (Site 1 and 2) Enhanced Linked Mode with external PSC, and manage the site 3 from site 1, and site 4 from site 2.
I'm not sure if this is the best possible solution, you see a different solution?
Hi everyone.
We are implementing a new VDI environment, it is Windows 7 Enterprise N with SP1, XenDesktop 7.11 hosted on VMware vSphere 6.0. We are using VMware UEM 9.1 as our workspace management tool. We currently have an issue whereby intermittently UEM doesn't properly create the user environment. The user is still logged in but they don't get any of their Persona built. No shortcuts, printers or profile etc.
I have followed the implementation guide closely and confirmed the user has permissions to the profile, archives and UEM General folders. Users also have access to the registry, and we are not blocking Regedit in group policy. Group policy is running and the UEM Policy is applying (as verified by GPRESULT). Also the UEM log files do not contain any errors (I've enabled debug mode). It is rather puzzling! Any assistance greatly appreciated.
S.
Here is an online one I just created: GitHub - DoubleCloudInc/powercli-sketchpad: Sketchpad for VMware PowerCLI It's open sourced under MIT license. To use it:
I recently upgraded to Fusion 8.5.3 and use a Windows 10 platform in full screen on an external monitor. No matter what I do to set the display sleep time in the Power settings, it seems to go to sleep after 5min, whether on battery or plugged in. Any thoughts on how I can extend this? Not critical, but it's rather irritating. Thanks.
Rick !
Before creating an OVA file, in vSphere right click on the VM, open Settings, click on CD/DVD drive, check if Device Type is selected as Datastore ISO. If so, select Client Device. Save settings by clicking OK. Export OVA file, and then deploy.
i change the CD-DVD ISO path to local device and export again in OVA format. After the Import was OK in vSphere 5.1.
Thanks, HwyHobo! Thanks, VIMSupport!
That fixed the problem PERFECTLY!
Hello,
I was using a virtual machine then I suspended it. Now I'm trying to use it again and it keeps showing this error.
The others virtual machines I have doesn't returns this error.
Some things I've tried already and didn't work:
- Rename the vmplayer.exe file;
- Restart vmware services;
- Restart windows management instrumentation service;
- Tried to delete .lck file (couldn't find it inside the folder);
Someone has any other suggestion for me to try?
Thanks
Or your other option is to deploy 2 vRO's, using llian's models (one for vCenter and one for vRA) and then synchronize them using the Multi-node plugin.
Carl L.