Seems you can’t receive direct twitter messages from anyone (privacy setting): @adamgudger can’t be messaged
Try to send me a message with your e-mail.
Seems you can’t receive direct twitter messages from anyone (privacy setting): @adamgudger can’t be messaged
Try to send me a message with your e-mail.
Hi Ted, please try again, should be sorted now
Does this mean you have VMs with the same DisplayName in vCenter1 and vCenter2?
If yes, use a Get-VM with the Server parameter pointing to vCenter1, to get the source in a variable (let's say $vm).
Then use that variable $vm on the VM parameter of the New-VM cmdlet.
I suspect that if you use Object By Name see about_obn), that it takes the VM in vCenter2.
No, they have different names. One is a template in vCenter1 and I use $TempSource = Get-Template -Name templatename -Location "SrcTemplates" -Server "vcenter1"
the resulting command acts like I’m using Get-VM on a VM in vCenter 2, with a completely separate name. I’m not even using -VM in the New-VM command which would be used to specify a VM to clone from.
Is this with the latest PowerCLI version?
In any case, you might be better off to open an SR, this sounds like a "feature".
Yeah this is the latest PowerCLI version. Are you aware of a way to move templates between vCenters that are linked with PowerCLI? I can do it through the GUI, but with the volume of templates and locations they need to be synced to it is very time consuming. Content library (OVF) doesn’t work well with using RunASync and for whatever reason using the VMTX format in content library is unreliable when syncing between locations.
Can we use Petasan for vmware production?
I used this one in the past, see Re: Mware -clone to template (from template) powercli
Not if you're smart and/or want support.
Hi Lieven,
While installing Office 365 for a client in stead of Office 2016 I noticed that Office 365 installs by default in %ProgramFiles%\Microsoft Office\root\Office16 whereas Office 2016 installs in %ProgramFiles%\Microsoft Office\Office16.
Therfore the shortcuts and conditions are different for Office 365 compared to Office 2016
That's right, and in DEM 9.9 we have updated the conditions in the Microsoft Office 2016 condition set accordingly:
Possibly some of the import/export config files are also different.
From our testing that does not seem to be the case. Are you aware of anything that's missing?
Hello,
We are looking to setup labs that are clones of each other within a single esxi instance. These virtual labs should be isolated from each other and will have the same IPs internally. We were looking to use vApps (rather than nested esxi) where each vApp (with all the VMs) has its own vSwitch. This would allow us to simply clone the whole vApp and redeploy it. Is it possible to make the vSwitch a part of that vApp? Or is there another way to make this work?
Thanks!
It depends on your system's CPU, not the OS. Check the CPU compatibility, please
Does anyone have a workaround for this issue?
nmp_ResetDeviceLogThrottling:3349: last error status from device naa.61866da0b5c68f00215bea28277f1f7c repeated 4 times
The vmkernel.log file has repeatedly this error from the mentioned device and seems to be related to adapter vmhba2:C2:T0:L0 (because it mentioned at the next line of each repeat). Can you check the location (storage) of installed ESXi and it's related log file path (scratch log) and I guess it's a SATA disk, not a SCSI ...
path "vmhba39:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data
If you check this error here, it will return the following results:
I added a shared folder virtual machine - host. However I cannot save files in the shared folder from software like Word. I guess is a permissions rights problem because the message "There has been a network or file permission error. The network connection may be lost" is displayed in word.
I went to the folder in the virtual machine -> right click -> Properties and it has the Attribute "Read-only". I already unselected it and applied the changes. However it gets selected again automatically.
Does anyone have had this issue and knows how to solve it?
That definitely seems to make sense. I will give that a try as soon as my machine stops backing up. Has been running almost 24 hours and is not even half way through.
Thanks
-Paul-
WebEx, GoToAssist, Go to Meeting all do not allow the remote user to access the mouse. This issue has existed since v14.
VMware, It's time to get this fixed
Hi there, I have prepared a simple script to do basic tasks on VMs and it works. However after all executes fine at the end I get the error below:
Get-VM : Cannot validate argument on parameter 'Name'. The argument is null or empty.
Again all works fine, here's the script by the way:
# retrieve list of VMs from txt file $vmList = Get-Content -Path "C:\Users\cavalloga\Desktop\VMs.txt" # convert list of VMs text in list of VMs objects foreach($txt in $vmList){ if((Get-VM -Name $txt -ErrorAction SilentlyContinue).Name -eq $null){ $otherVMs += "$txt `r`n" Write-Host "VM's name $txt is either mispelled or VM is in a different vCenter server" -ForegroundColor Black -BackgroundColor Yellow } else { $vmNames += Get-VM $txt } } $otherVMs | Out-File "C:\Users\cavalloga\Desktop\otherVMs.txt"
I removed PowerCLI 6.5 and installed the latest. If that is the reason maybe some 6.5 leftovers are bugging? Where can I find for its leftover in case that is the reason. Many thanks guys and have a good weekend!
I tried the old CLI command, I received
Deleting static route 192.168.0.0/21 from VMkernel
Error: Unable to find route 192.168.0.0/21 with gateway 192.168.100.1
I am able to ping from said gateway to the NIC on the esxi server holding an IP within the same subnet as the mentioned gateway NIC.
Did you check that $vmList is actually an array, without any empty elements in there?
Do a
Get-Content-Path "C:\Users\cavalloga\Desktop\VMs.txt"
And also a
(Get-Content-Path "C:\Users\cavalloga\Desktop\VMs.txt").Count
Did you remove all traces of the old PowerCLI version?
I would suggest to clean up everything, including the folders for the new PowerCLI version.
Then restart your station, and do a new install with