Trend Deep Security agentless windows 2016 protection

Even-though the 9.6 Service pack 1 was supporting the agentless protection which was tested in our lab, it was not officially supported by Trend and from the latest version Deep Security 9.1 Update Release (9.6 ServicePack 1 Patch1 Update 15) it started supporting now.

As per the Trend support team the EPSECLib 6.3.3 packaged into the RedHat agent version that goes into the DSVA to properly support Windows 2016 servers.

Also another issue which got fixed by this patch is when doing vMotion of many simultaneous VMs, some of the VMs may appear as Anti-Malware Engine Offline after it moves to the new host. This occurred because the DSM checked the status of the VMs during heartbeat before the vMotion is finished. It looks like from this patch it will do another check status or waiting for the next heartbeat will fix the status.


Posted in Trend Deep Security Manager - ( DSM ), Trend Micro Deep Security, Trend Micro Deep Security 9.5 ( Deep Security Agent ), Trend Micro Deep Security 9.5 ( VDI Environment-Agentless Protection ), Windows | Tagged , , , | Leave a comment

Useful links about Meltdown and Spectre

Everyone is  working on to fix the Meltdown and Spectre so just thought of sharing few links which will help to handle the issue efficiently .


Today HP has released update for System ROM and we can find below link to download and information.


On addition to the NOV Patch , VMware has released today the below link which have to be updated.



AWS Linux,



Trend has released the useful link for the Deep Security Protection and also office scan.







Citrix XenServer


Other Links

Below Links will help to verify and more info on the issue.

Validating compliance of VMSA-2018-0002 and BIOS update


Posted in Dell, ESXi issue, ESXi Patches, ESXi Tools, Firmware upgrade, HP, Trend Micro Deep Security, VCSA6.5, VMware, Windows | Tagged , , | Leave a comment

Looking back on 2017

Just want to register my memory on 2017 , It has been wonderful journey with lot of happiness and also some bad memories .

So after doing almost six years of consultant job , I joined as the full time employee around mid 2016  and it was totally different  experience .When I was doing the consultant job , had lot of time for outside activity other than my daily responsibilities, like preparing and learning new stuff to improve my skills ,writing blog but after joining full time job the story is totally different and in my personal life my kids also now needed lot of time from me. On all these changes, I somehow managed to post at least one blog on each month.

2017 I have done some significant project like designing DR and Implemented the VMware SRM  and worked in the project to setup internal cloud in our environment. This year VMworld was so informative and had chance to meet some top personalities in the market. Year-end was not so good because of the recent layoff which affected lot of my close friends in the office. It is really nightmare for everyone and now lot of pressure to project our-self to show that we are worth for the company growth. Even though the vision of the company is to move to external cloud but one positive note is company are still showing interest on internal infrastructure  so the goal on 2018 is to learn open stack and AWS to improve the skills. I know 2018 going to be very challenging because of VISA issues in US and the new vision of our company. It will be very interesting and as i said challenging  year to prepare myself to respond for the situation in up-coming months..


Wishing everyone a very happy new year and hope will spend more time on writing the blogs with helpful information ..

Posted in year 2017 | Tagged | Leave a comment

VCSA 6.5 upgrade\Installation issues and fixes

Recently I have started upgrading the VC6.0 U3 ( VCSA ) to 6.5 U1 and encountered few issues  so  same like by previous blogs on VC6.0  issues , planned to do it for VC6.5 also and  find the old blogs below.

vCSA 6.0 Installation issues 


We have around 25 different vCenters to be upgraded and will update the blog accordingly .

Issue 1.

Invalid Appliance (OS) root password

So while upgrading the appliance we need to provide the SSO Password and also source VC\PSC appliance root password and it was failing with the OS root password is invalid. I have verified  the password which is correct and later found that SSO and OS password is same which fails to accept . Once I have changed the OS password, issue got fixed.

Issue 2.

Unable to retrieve the migration assistant extension on source vCenter server.

So as per the KB 2148400 , environment which is not using the VUM , we need to remove the com.vmware.vcIntegrity extension. KB 1025360 will guide the steps.

Issue 3.

The Installer is unable to connect to the vCenter Appliance Management Interface.

So my source VC was running in one cluster and trying to implement the upgrade 6.5 appliance on different cluster . Since the network is different it got failed on the end of the Stage 1 . Once I pointed the upgrade 6.5 appliance to the same cluster issue got fixed.

Issue 4.

Could not reach the given source vCenter Server address on port 22

Lot of blogs are pointed to check the SSH on the source appliance but in my case it was already enabled so I just restarted all the services before the upgrade and the issue got fixed on the next try.




Posted in ESXi issue, VC6.0 Appliance Installation Issue, Vcenter Appliance, vCSA 6.0, VCSA6.5, VMware | Tagged , , | Leave a comment

Options to check and alert the vcenter certificate expiration

Last week one of our vCenter went down because of the machine certificate got expired and it took some time to find out the issue so I thought it will be helpful to show the options to verify the certificate and make sure to enable the alarm.

Since the certificate as expired most of the services will fail to work properly since it cannot function/use the certificate it is assigned to use.

In our case, we are unable to vMotion because the service to vMotion (vmware-sps) is unable to connect to vpxd due to “server certificate chain not verified.”

Below is the log path to verify .


com.vmware.vim.vmomi.client.exception.SslException: com.vmware.vim.vmomi.core.exception.CertificateValidationException: Server certificate chain not verified

Below is the command to verify the Machine certificate.

/usr/lib/vmware-vmafd/bin/vecs-cli entry list –store MACHINE_SSL_CERT –text |less

Solution certificate

/usr/lib/vmware-vmafd/bin/vecs-cli entry list –store machine –text |less

Also we can check the same using the web-browser  .

Using the “ /usr/lib/vmware-vmca/bin/certificate-manager” Replace the certificates on the vCenter via option 3 (just the MACHINE_SSL) or if it is with internal CA then follow the steps here.

So to make the alarm configured for the certificate expiration, already by default 30 days threshold is configured in the vcenter and You can change how soon you are warned with the vpxd.cert.threshold advanced option.

  1. Log in to the vSphere Web Client.
  2. Select the vCenter Server object, the select the Manage tab and the Settings subtab.
  3. Click Advanced Settings, select Edit, and filter for threshold.
  4. Change the setting of vpxd.cert.threshold to the desired value and click OK.

Also make sure under Alarm settings – Certificate Status – Enable this alarm is active so that according to the threshold  we will get the alarm notification when the issue occurred.

Reference :

Posted in Certificate, ESX command, Replacing vCenter 6.0 SSL Certificate, Vcenter Appliance, vCSA 6.0, VCSA6.5, VMware, vSphere 6.0 Template. | Tagged , , , | Leave a comment

Bug in NFS mount while using SRM

We were configuring the SRM with Tintri storage and while configuring the Array pairing in storage replication , SRM was failed to mount the Tintri datastore.

So as per Tintri we need to create the service group in the production site and it will automatically create the folder in the destination for the replication. Once the storage part is done, we started configuring the Array Pair in the SRM and it got completed without any error but in the below array pair column it was showing only the service group without the datasotre mapping.By the result of this we cant create the protection group which need datastore  groups mapping.


By the help of Tintri support we have tried lot of options like deleting the service group and re-creating it but nothing helped. At last found it is known  SRM issue with NFS datastore having mounted in the ESXi using the FQDN. ( KB 2009622 )

Site Recovery Manger cannot match the Fully Qualified Domain Name (FQDN) or short name of the NFS server that is used to mount the source NFS volumes on the ESX/ESXi hosts with the StoragePort information that is reported in the SRA response to the discoverdevices command.

Finally we remounted all the datastore with IP address and the issue got resolved



Posted in SRM, VMware | Tagged , , , , | Leave a comment

Mind-Map for dvSwitch.

My flight got delayed after the VMworld and have to spend few hours in the airport so just to make something interesting made this Mind-map for dvSwitch . Hope it will be helpful for the certificate preparation.


Posted in Vcenter Appliance, vCSA 6.0, VMware | Leave a comment