XML file is internal only and not for customer public use.. Customer would need to use ServiceNow production instance with their HI creds to install the itsm app. please check the installation guide documentation
Thanks Maher, it was very informative.. But, though we go for distributed deployment, still, there is a single point of failure for vRSLCM which is required to enable Multi-Tenancy and also to create new Tenants.
Very Good Video. Thank you for all your time. quick question. Does the new plugin support "Deployment Count" from SNOW? Or can we just do one deployment at a time from SNOW?
It is updated only in Custom Tables. Update in ServiceNow tables is planned for Q4 of this year - by dec 2021 The base Configuration Item table is cmdb_ci. cmdb_ci.list in the navigator
Hi Maher - great video and blog. I am running vRA 8.2 in a lab getting ready for prod and having issues with cloud-init. Followed your video to the T (even started with same Ubuntu 18.04.2 ISO) but I cannot get vRA 8 to attach an ISO/OVF to the VM. It just makes no attempt and then in the guest cloud-init logs complain about no datasource. Have you had this happen?
In 29:43 you show 2 scripts, and say that enabling_cloud-init.sh is the one executed by the cron job. But, in crontab you reference another file "prepare_cloud-init.sh". How is this working?
If I need to keep inventories in sync (blueprints and workflows) for a few tenants (or possibly all) I guess Git integration is the way to go. Could they all use the same repo. Given that any type of security sensitive info is not part of the blueprints and workflows. Or maybe this is a sign that multitenacy is not a fit.
Hi, i am getting error while adding ad to vidm "connector communication failed because invalid data: problem connecting to directory host" any idea why i am getting this error
You need to make sure that your domain controller is reachable from vIDM . so make sure that you can resolve the AD host from vIDM or simply try using the IP instead.. i m assuming you are trying to add AD directly in vIDM based on your question. in my case i added the domain in LCM under identity and Tenant management - > Directory management
@@vmwarelab yes I am trying to add from vidm, i tried with LCM but no luck as you suggested i tried with ip too same error. How can test the connector connectivity from vidm?
@@shardatiwari5267 simply ssh to the vidm appliance and do a simple nslookup or ping to your domain controller by FQDN and IP to test the connection. also make sure you're using a domain admin user and the right information in the join domain details and bind user details sections in vIDM. i would need to see a screenshot of the add directory page with all the setting your are using to pin point any issues.
@@vmwarelab i think there issue with vidm ovf 8.1 I deployed through easy installer and there is error message on the vidm when i open it on vmrc that the deployment failed however the entire workflow deployment through easy installer was success in on LCM. Also i tried deploying vidm 8.1 individually through the ovf it still shows deployment failed error, I think i need to use 8.0. 1 vidm ovf and deploy it and import it to 8.1, that's possible right? Where can I send you screen shots?
Loved the video. Originally I had 8.0 installed, integrated with vrops. So when I looked at my deployments I could monitor the VM through vRA. Now I followed your video and set up vra 8.1 with the master tenant and tenant 1. Master tenant was the original 8.0 configuration and had vrops integration. When trying to set up integration of vrops with the tenant 1, I cannot do it as vrops is already associated with the organisation master tenant. As a service provider we have a global vrops and want all tenant VMs to be monitored in it. Looks like vrops 8.1 doesn't understand multitenancy in vra
Naveed Liaquat correct, every tenant has to have its own vrops instance for now. That is something that is on the roadmap for federation. So you can connect multiple tenants to one shared vROPs instance
Very good video. Is the procedure similar for IDM with multiple Windows Connectors? Are there any additional steps? Maybe you could prepare new video describing such scenario..? :D
Assuming I understood the question correctly , no additional steps with vIDM as you can have more than windows domain directory added to vIDM that can be mapped to one or more tenants.
Dear Eng. Maher can i use vRealize suite LCM or this product need lic's from VMware , We already have already have vRealize suite lic pack will it cover this or we need some thing else Best Regards
