Posts

In order to enable SSH access you will have to first enable root access To enable root access, you need to secure the vRealize Operations Manager Console. More information here: http://pubs.vmware.com/vrealizeoperationsmanager-61/topic/com.vmware.vcom.core.doc/GUID-CBF43396-7161-4F26-9F09-4E2829AFACF0.html To enable ssh, login as root and run the following commands: Start the SSH service by running the command: service sshd start Configure SSH to start automatically: chkconfig sshd on

Recently, a hosting company wanted to know if their customers can have VMware View running on hosted vCenter/ESXi hosts. The hosted vCenter Server was a shared resource and had many clusters that were used by other customers as well. The vcenter credentials used in VMware View cannot have permissions to all other clusters. In summary: VMware View will be running in the customer’s domain vCenter Server will be in the hosting company’s domain Customers cannot have permissions at a vCenter Server level View Composer cannot be co-installed on the vCenter Server Solution:...

When vMA is added to active directory, be default, all users will be able to login to the appliance. In order to restrict the login to certain users or groups, we need to manually edit the Likewise configuration file located in /etc/likewise/lsassd.conf Look for the following section, uncomment “require-membership-of” and provide a comma seperated list of users, groups and sid’s that you would like to restrict access to. # Allow only the following users and groups...

My VIO lab broke after a power failure. I powered on and brought back the vsphere infrastructure, Openstack Manager and the VIO VM’s, however I was unable to login to Openstack. So I decided to do a clean shut down/start up of the VIO deployment from the VIO plugin in the vsphere web client. The VIO deployment shut down fine. However, powering on the deployment failed with an error pointing to the DB-01 VM....

Was setting up VMware Horizon Daas for the first time and clearly it looks like I missed a configuration step. The desktop was prepared, agents installed, firewall disabled, local administrator enabled, certificated imported, etc. i.e. the desktop looked good from a config perspective. From the Daas Agent logs at C:\Program Files (x86)\DaaS Agent\service\DaaSAgent 2015-05-21 19:19:59 \[INFO \] DaaSAgent - \*\*\*\*\*\*\*\*\*\* Starting DaaS Agent 6.1.0, Build-22158.1 \*\*\*\*\*\*\*\*\*\* 2015-05-21 19:19:59 \[INFO \] DaaSAgent - System Info: Windows7\_64(6....