Install 2 hosts. Install vcenter 6.7. Install VMRC on my mac. Put in /etc/vmware/config lines:

vmx.fullpath = "/bin/vmx"

isolation.tools.copy.disable="FALSE"
isolation.tools.paste.disable="FALSE"

But copy paste not work, what I'm do wrong?

I am using an iMac mid 2011 running High Sierra. This machine does does not meet the tech requirements for OSX 10.14 (Mojave). Is there any significant reason for me to upgrade to Fusion 11 since some of the features (tech specs) require a newer machine (similar to the spec requirements for OSX 10.14)?

Hi All,

Could any body, please provide me valid suggestions on how can we map the SSH to a Centralized application. Our scenario is to block the SSH sessions to vCenter and hosts,  as of now we are able to do the same from VAMI or from the vCenter for hosts (to enable SSH).

If we want to do the SSH to vCenter (VCSA) or hosts,  is it should be routed from the centralized application only?

Kindly suggest,

I upgraded to macOS Mojave on then 25:th of September and run Fusion 10 without any problem, then I upgraded to Fusion 11 and all of a sudden VMware Tools Core Service constantly keeps crashing (Windows 7 as guest OS).

I have tried to uninstall VMware Tools and reinstall it but it still crash. Really annoying, I shouldn’t have upgraded to Fusion 11

I've just updated to Mojave and installed Fusion 11 as a trial. With that said, perhaps I'm doing something wrong, but it looks more like a bug.

When I select a file in Fusion and right click "open with," or for that matter, when I select a Mac application (I've tried Photoshop and just the Calendar app) that I've added to the Windows 7 start menu, it will not open. I can see the quick flash of an icon on the end of the Mac dock as it tries to open, but it closes immediately, even before I see a window on the mac desktop.

I've looked through the console but didn't see anything obvious.

I've searched a bunch of different terms Googling this, but all I get back are entries on Fusion not starting, which is not the issue here.

Any suggestions on what to try?

We are on vSphere 6.5 and our Storage is HPE 3PAR 7400 SAN with Fiber-Channel (FC) and Near-Line (NL) type storage volumes.

I am creating and resizing existing Datastores to more standardized format. I am not sure what is the best size recommended when creating Datastore. I got to know from our Technical vendor that VMware best practice says Datastore size should 2TB. We have many VMs in existing VMFS5 Datastores, and if we are creating new VMFS6 Datatores with just 2TB each, then we will be needing many Datastores, each of those will only be able to hold few VMs. We also need to make sure there are a minimum recommended free space available (say 15%) all the time, so the more small Datastores, the more waste of storage. There are some VMs even that wont fit in one 2TB Datastore, rather will need few.

Our previous Datastores of VMFS5 type are in different sizes, between 2TB and 10TB, based on similar types of VMs present in one single Datastore. For example, for an application's production Environment, if there are 6 VMs, Datastore was created for that purpose and all VMs are in that. Off course over time it was expanded as VMs grew. While I don't think a 10TB is a good choice, neither a 2TB.

I have gone through " vSphere Storage - VMware vSphere 6.5 - VMware Docs" and "Performance Best Practices for VMware vSphere 6.5", haven't seen anything specific to what I am looking for if not missed.

Also need to know recommendations for HPE 3PAR SAN Virtual-Volume side.

What is best practice regarding the port groups the NSX Manager and vCenter should live on? Traditional VLAN or can they be on a Logical Switch?

Hi,

I'm looking for an exact script to generate CSV file for extracting the date and time of all VMs that has been created since last 2015. Sorry, I'm not familiar on PowerCLI commands.

Thank you in advance.

Recently our existing vCenter got crashed because of vpxd is not running. Unable to connect to the vCenter we didn't manage to troubleshoot it or get the coredump. We decided to create a new vCenter. After I created new vCenter, since it doesn't have anything, so need to create cluster, datastores and vlans. My question is, if I disassociate the hosts from the faulty vCenter, will the Production VM path of the OS Linux to the Datastore and to the LUNs (Nimble). will be disconnected? Same also if the VM is connected the VLANs.

My client wants to know, what is the difference of vSphere with Operation Manager and vRealize Operation Manager. I've gathered some info from the product overview, it seems that it is very much alike, aside from VROPS that have integrated with Log Insight and Business for Cloud.

Thanks

Hi there,

Is it possible to extend an existing 500GB virtual hard disk to 2TB for VMware vRealize Log Insight 4.6.1 or 4.5.1?

Will it be usable as every article found is suggesting to add as a new 1TB or 2TB virtual hard disk for a total of 4TB?

Thanks in advance!

Why is this happening on a an upgrade to the lates version on the latest version of Macos....

Any clues

I am getting fed up with these sort of issues with VMware when Parallels works perfectly...

????

i have a dell R720 server which was running ESXi 5.1.

i tried to upgrade to ESXi 5.5 before going to ESXi 6.5.

i am using localstore, no NAS or SAN storage.

after upgrading from 5.5 to 6.5, i encountered missing datastore. my VM cannot be seen.

i re-scan the datastore and then rebooted the server, it went back to ESXi 5.5 version.

my ESXi 5.5 version is 3029944.

the ESXi 6.5 version that i am trying to upgrade to is 7388607

Hello to everyone, i have this problem and i can't figure it out how can i resolve it.

Maybe it's a Elementary OS problem... i don't know.

I running VMware Workstation (Trial version) on my Elementary OS, and when i try to power on any virtual machine, it doesn't anything except messed up the screen of Workstation:

I followed every installation guide but everytime this problem occur.

My version of VMware Workstation is: 14.0.0 build-6661328 - Workstation pro 14

My system detail: Intel Core i7 - 2.0 ghz - RAM 8gb - 16.04.1-Ubuntu

This problem occured everytime with every guest os.

Can someone help me to understand why this occured and how i can resolve it?

I ask you apology for my english.

Hi, this issue started 2 days ago when I attempted to update from 6.5.0.20100 to "VC-6.5.0U2b-Appliance-FP" (6.5.0.21000 Build Number 8815520) in the vSphere Appliance Management. It stopped at 60% and prompted with an error code about "not being able to contact the server...". I then restarted the Appliance and from there it went down hill.

I figured out if I ran the command "Service vami-lighttp start" and  it came up again, but after some time I couldn't authenticate etc.. seems as some services aren't running.

I did find this discussion in a different thread and noticed it was the exact same issue I have -> vCenter 6.5 - vcenter appliance stops working out of the blue, AGAIN!!

I will post the same output and hopefully figure this out. (I did notice those 4 commands, but haven't used those yet since I don't quite understand what they do)

service-control --status
Running:
 applmgmt lwsmd pschealth vmafdd vmcad vmdird vmdnsd vmonapi vmware-cis-license vmware-cm vmware-content-library vmware-eam vmware-perfcharts vmware-psc-client vmware-rhttpproxy vmware-sca vmware-sps vmware-sts-idmd vmware-stsd vmware-updatemgr vmware-vapi-endpoint vmware-vmon vmware-vpostgres vmware-vpxd vmware-vpxd-svcs vmware-vsan-health vmware-vsm vsphere-client vsphere-ui
Stopped:
 vmcam vmware-imagebuilder vmware-mbcs vmware-netdumper vmware-rbd-watchdog vmware-statsmonitor vmware-vcha

service-control --start vmware-vpxd-svcs
Perform start operation. vmon_profile=None, svc_names=['vmware-vpxd-svcs'], include_coreossvcs=False, include_leafossvcs=False
2018-07-18T17:45:49.534Z   Service vpxd-svcs state STARTED
Successfully started service vpxd-svcs

systemctl list-unit-files | grep vmware
vmware-bigsister.service               static
vmware-cis-license.service             masked
vmware-cm.service                      masked
vmware-content-library.service         masked
vmware-eam.service                     masked
vmware-firewall.service                enabled
vmware-imagebuilder.service            masked
vmware-mbcs.service                    masked
vmware-netdump.service                 masked
vmware-perfcharts.service              masked
vmware-pschealth.service               masked
vmware-rbd-watchdog.service            masked
vmware-rhttpproxy.service              masked
vmware-sca.service                     masked
vmware-sps.service                     masked
vmware-statsmonitor.service            masked
vmware-updatemgr.service               masked
vmware-vapi.service                    masked
vmware-vcha.service                    masked
vmware-vmon.service                    enabled
vmware-vmonapi.service                 masked
vmware-vpostgres.service               masked
vmware-vpxd-svcs.service               masked
vmware-vpxd.service                    masked
vmware-vsan-health.service             masked
vmware-vsm.service                     masked
vmware-bigsister.timer                 disabled

After running the "service-control --start vmware-vpxd-svcs" the Appliance Manager came up again.

systemctl list-unit-files | grep masked
applmgmt.service                       masked
vmcam.service                          masked
vmware-cis-license.service             masked
vmware-cm.service                      masked
vmware-content-library.service         masked
vmware-eam.service                     masked
vmware-imagebuilder.service            masked
vmware-mbcs.service                    masked
vmware-netdump.service                 masked
vmware-perfcharts.service              masked
vmware-pschealth.service               masked
vmware-rbd-watchdog.service            masked
vmware-rhttpproxy.service              masked
vmware-sca.service                     masked
vmware-sps.service                     masked
vmware-statsmonitor.service            masked
vmware-updatemgr.service               masked
vmware-vapi.service                    masked
vmware-vcha.service                    masked
vmware-vmonapi.service                 masked
vmware-vpostgres.service               masked
vmware-vpxd-svcs.service               masked
vmware-vpxd.service                    masked
vmware-vsan-health.service             masked
vmware-vsm.service                     masked
vsphere-client.service                 masked
vsphere-ui.service                     masked
ctrl-alt-del.target                    masked

/etc/systemd/system ]# ls -lisa
total 108
180710 4 drwxr-xr-x 24 root root 4096 Jul 17 17:01 .
180226 4 drwxr-xr-x  7 root root 4096 May 31 15:04 ..
183069 0 lrwxrwxrwx  1 root root    9 Jun  6  2017 applmgmt.service -> /dev/null
183110 4 drwxr-xr-x  2 root root 4096 Jun  6  2017 applmgmt.service.d
182577 0 lrwxrwxrwx  1 root root   40 Feb  3  2017 default.target -> /usr/lib/systemd/system/runlevel3.target
180712 4 drwxr-xr-x  2 root root 4096 May 31 15:03 getty.target.wants
183131 4 drwxr-xr-x  2 root root 4096 Jun  6  2017 halt.target.wants
188806 4 drwxr-xr-x  2 root root 4096 Feb  3  2017 local-fs.target.wants
182743 4 drwxr-xr-x  2 root root 4096 Jul 17 23:17 lwsmd.service.d
180714 4 drwxr-xr-x  2 root root 4096 Jul 17 19:58 multi-user.target.wants
180718 4 drwxr-xr-x  2 root root 4096 May 31 15:03 network-online.target.wants
183133 4 drwxr-xr-x  2 root root 4096 Jun  6  2017 poweroff.target.wants
183129 4 drwxr-xr-x  2 root root 4096 Jun  6  2017 reboot.target.wants
182530 4 -rw-r--r--  1 root root  268 Jun  7  2016 sendmail.service
183127 4 drwxr-xr-x  2 root root 4096 Jun  6  2017 shutdown.target.wants
182483 4 -rw-r--r--  1 root root  476 Mar  1 19:03 snmpd.service
180720 4 drwxr-xr-x  2 root root 4096 May 31 15:03 sockets.target.wants
180722 4 drwxr-xr-x  2 root root 4096 May 31 15:03 sysinit.target.wants
182042 0 lrwxrwxrwx  1 root root   39 Feb  3  2017 syslog.service -> /usr/lib/systemd/system/rsyslog.service
182708 4 -r-xr-xr-x  1 root root  470 Jun 13 09:50 vcha-hacheck.service
232102 4 drwxr-xr-x  2 root root 4096 Jul 17 23:17 vmafdd.service.d
320650 4 drwxr-xr-x  2 root root 4096 Jul 17 23:17 vmcad.service.d
183086 0 lrwxrwxrwx  1 root root    9 Jun  6  2017 vmcam.service -> /dev/null
182854 4 drwxr-xr-x  2 root root 4096 May  7 12:12 vmcam.service.d
320579 4 drwxr-xr-x  2 root root 4096 Jul 17 23:17 vmdird.service.d
320789 4 drwxr-xr-x  2 root root 4096 May  7 12:12 vmdnsd.service.d
182138 4 drwxr-xr-x  2 root root 4096 Feb  3  2017 vmtoolsd.service.requires
182905 0 lrwxrwxrwx  1 root root    9 Jun  6  2017 vmware-cis-license.service -> /dev/null
182904 0 lrwxrwxrwx  1 root root    9 Jun  6  2017 vmware-cm.service -> /dev/null
183082 0 lrwxrwxrwx  1 root root    9 Jun  6  2017 vmware-content-library.service -> /dev/null
183083 0 lrwxrwxrwx  1 root root    9 Jun  6  2017 vmware-eam.service -> /dev/null
183104 0 lrwxrwxrwx  1 root root    9 Jun  6  2017 vmware-imagebuilder.service -> /dev/null
183076 0 lrwxrwxrwx  1 root root    9 Jun  6  2017 vmware-mbcs.service -> /dev/null
183072 0 lrwxrwxrwx  1 root root    9 Jun  6  2017 vmware-netdump.service -> /dev/null
183105 0 lrwxrwxrwx  1 root root    9 Jun  6  2017 vmware-perfcharts.service -> /dev/null
182906 4 drwxr-xr-x  2 root root 4096 Jul 17 23:18 vmware-psc-client.service.d
183073 0 lrwxrwxrwx  1 root root    9 Jun  6  2017 vmware-pschealth.service -> /dev/null
183084 0 lrwxrwxrwx  1 root root    9 Jun  6  2017 vmware-rbd-watchdog.service -> /dev/null
182903 0 lrwxrwxrwx  1 root root    9 Jun  6  2017 vmware-rhttpproxy.service -> /dev/null
182916 0 lrwxrwxrwx  1 root root    9 Jun  6  2017 vmware-sca.service -> /dev/null
183087 0 lrwxrwxrwx  1 root root    9 Jun  6  2017 vmware-sps.service -> /dev/null
183074 0 lrwxrwxrwx  1 root root    9 Jun  6  2017 vmware-statsmonitor.service -> /dev/null
183118 4 drwxr-xr-x  2 root root 4096 Jul 17 23:18 vmware-stsd.service.d
183122 4 drwxr-xr-x  2 root root 4096 Jul 17 23:17 vmware-sts-idmd.service.d
183093 0 lrwxrwxrwx  1 root root    9 Jun  6  2017 vmware-updatemgr.service -> /dev/null
183060 0 lrwxrwxrwx  1 root root    9 Jun  6  2017 vmware-vapi.service -> /dev/null
182878 0 lrwxrwxrwx  1 root root    9 Jun  6  2017 vmware-vcha.service -> /dev/null
183067 0 lrwxrwxrwx  1 root root    9 Jun  6  2017 vmware-vmonapi.service -> /dev/null
183114 4 drwxr-xr-x  2 root root 4096 Jul 17 23:18 vmware-vmon.service.d
183075 0 lrwxrwxrwx  1 root root    9 Jun  6  2017 vmware-vpostgres.service -> /dev/null
183081 0 lrwxrwxrwx  1 root root    9 Jun  6  2017 vmware-vpxd.service -> /dev/null
182872 0 lrwxrwxrwx  1 root root    9 Jun  6  2017 vmware-vpxd-svcs.service -> /dev/null
183094 0 lrwxrwxrwx  1 root root    9 Jun  6  2017 vmware-vsan-health.service -> /dev/null
183103 0 lrwxrwxrwx  1 root root    9 Jun  6  2017 vmware-vsm.service -> /dev/null
183077 0 lrwxrwxrwx  1 root root    9 Jun  6  2017 vsphere-client.service -> /dev/null
183080 0 lrwxrwxrwx  1 root root    9 Jun  6  2017 vsphere-ui.service -> /dev/null

Hello everybody!

- vSphere VCSA 6.5.0.20000 Build 9451637

- VMware ESXi, 6.5.0, 8935087

- vSAN 6.6

- NSX 6.4.3 Build 9927516

Immediately after upgrading from NSX 6.4.0 to 6.4.3, problems arose: at random, different virtual machines stopped responding (hang). It is impossible to connect to them via RDP or through the console. Then after a while they again work in normal mode, then hang again.

Shutting down the NSX-manager and Guest Introspection immediately solves the problem.

Any ideas?

When I used WS14 Player and Window 10 with an Ubuntu virtual machine, evrything works fine.

I could resize the Player window and Ubuntu got the new resoltuion from the new window size.
But now I have upgraded to WS15 Pro and when I want to resize the VmWare Window the Ubuntu resultion is not adapted.

It still remains with the old resolution.

Hi community memebers,

I have been searching for the vCloud Director SDK in .NET, and I am only able to find the SDK released for 8.1 in the link below. I am aware that VMware released python SDK, but I am only looking for .NET version particularly.

VMware vCloud Director for Service Providers

Could someone point me to potential location or contact that can help to get the .NET SDK for vCloud Director?

Thanks in advance.

Fu

Let me mention that I've never used PowerCLI before, but I am familiar with PowerShell. If it matters, this is all in context of VMware View 6.2.2.

In doing research for another issue, I found that PowerCLI allows you to automate pool creation. Great! More digging found the basics of how to go about getting that done, but the parameters given were sparse. Even more diffing found that Get-Pool gives me a ton of info on all of my pools; 58 columns worth of data per pool. I'm not sure all of that is needed in pool creation, but I know that some of it is very pertinent to our environment.

My first question is: Am I limited to the few parameters given in the example? They are:

Get-ViewVC -serverName servername| Get-ComposerDomain -domain domainname | Add-AutomaticLinkedClonePool

-pool_id H-VDI-HVAC

-displayName "H-VDI-HVAC"

-namePrefix "H-VDI-HVAC-{n:fixed=2}"

-parentVMPath /Location/vm/Masters/Labs/H-VM-VT2

-parentSnapshotPath /9-28-18/9-28-18-2

-vmFolderPath /Location/vm/Discovered virtual machine/H-VDI-HVAC

-resourcePoolPath /Location/host/Servers/Resources

-datastoreSpecs [Aggressive,OS,data]/Location/host/Servers/VM-VDI-3 

-minimumCount 2

-maximumCount 2

I'd like to add the following parameters. Can they be added after maximumCount, or do they have specific places?

-enabled TRUE

-multiSessionAllowed TRUE

-userResetAllowed FALSE

-assignOnFirstLogon TRUE

-desktopSource SVI

-powerPolicy AlwaysOn

-refreshPolicy type=Never;

-uservSphereMode TRUE

-organizationalUnit OU=VDI

-networkLabelSpecs disabled

-UseSeSparseFormat TRUE

-seSparseThreshold 0

-useVSAN FALSE

-provisionEnabled TRUE

-provisionSuspendOnError TRUE

-postProvisionState READY

-startClone TRUE

-calculatedValues FALSE

-deletePolicy Default

-headroomCount 1

-persistence NonPersistent

-autoLogoffTime Immediately

-poolType SviNonPersistent

-protocol PCOIP

-allowProtocolOverride FALSE

-flashQualityLevel NO_CONTROL

-flashThrottlingLevel DISABLED

Am I missing any parameter to make this work? And lastly, every example I saw lists parentSnapshotPath, however, Get-Pool lists it as parentVMSnapshotPath. Which is correct when creating a pool?

Hi all,

I'm trying to login to multiple vCenters at the same time -- and I'm losing my mind, because this code logs into each vCenter but at the end, I'm only logged into the last vCenter in the CSV.

What am I doing wrong?