ServiceNow ITSM Plug-in 8.6 released for vRA Integration  

ITSM 8.6 Features 

• Enhancement around debug Loggers.
• Reduce the delete operation on question_choice table
• Minor bug fixes

Below are the additional features/functionalities in the ITSM application

• Limit the scheduled job to run on a limited number of threads
• Improvement to the load time of Catalog Item Request form
• Toggle switch for form loader
• Additional Loggers and improvement around try/catch logging
• Fix for Project/Endpoint reference empty on deployments/resources
• Compatible with IPAM integration plugin installed on vRA
• Provisioning Catalog items and Day 2 actions catalog items entitlement across ServiceNow users through user criteria
• Resource visibility based on ownership within ServiceNow
• Reconcile of CMDB
• Email Notification
• Provision to configure Multi-Level Approvals within request workflow
• Auto re-trigger of Catalog item request if Mid-Server goes down and comes up
• Configurable vRA Cloud region base URL
• ServiceNow Incident ticket for failed deployment request
• Condition field visibility support with equals and not equals parameter
• Support of deployment name field with an external source 
• Support of custom loader on catalog item form(Native UI)
• Enhancement around reconciliation of deployment, resources, and day-2 actions,
• UI enhancement on catalog item form 

Supported ServiceNow Releases

        Paris, Quebec, and Rome

Supported vRealize Automation Version

        vRA 8.5, vRA 8.5.1, vRA8.6, vRA 8.6.1, vRA8.6.2, and vRA Cloud

VMware NSX for vSphere 6.4.x is EoGS January 16, 2022.

 VMware NSX for vSphere 6.4.x is EoGS January 16, 2022.

There is an additional one year of Technical Guidance which ends on January 16, 2023. Limited support during this year is documented below (see Resources).

Resources

https://kb.vmware.com/s/article/85706

https://www.vmware.com/products/nsx/migrate-to-nsx-t.html

https://www.vmware.com/support/services/extended.html

https://www.vmware.com/support/policies/lifecycle.html

During the Technical Guidance phase, VMware will not offer new hardware support, server/client/guest OS updates, new Security patches or bug fixes unless otherwise noted.

Renaming VMware Virtual Machine and its files

Renaming VMware Virtual Machine and its files 

There are some situations where you need to rename the Virtual Machine, but renaming Virtual Machine within vCenter will not rename the folder and Virtual Machine files, this may cause confusions in the future that VM name is different and folder and file names of different from the the current VM name.

There is way to come out situation easily by performing the sVmotion (Storage vMotion) of  the Virtual Machine to different Datastore from the current datastore, This action will rename the folder and and Virtual Machine files.

There comes a situation that you are cluster is on vSAN storage and there is no other shared storage in that cluster, No worries move the Virtual Machines to local datastore of the one of the host and move them back to vSAN storage