hey everybody my name is david deich and i'm an advisory solution consultant with servicenow and i'm going to go through a quick tutorial today on how to discover your vcenter environment we're going to move pretty quickly in our ability to do this and we're going to see exactly what information servicenow can provide you within minutes by just discovering your vcenter environment i've got a fairly clean instance of servicenow that we're going to work with today and just to kind of set where we're at you can see we've got 23 configuration items in our system currently 20 relationships i've already gone ahead and set up a mid server that's in the same environment it's actually running on my vcenter and we'll see that and i've also gone ahead and activated the discovery plugins you can request those from the support portal and you're going to need those in order to run your discovery to discover our vcenter environment we're going to need the vcenter credentials so very quickly i have two examples of the credentials here one is the traditional username and password [Music] and i've actually deactivated those credentials because i'm going to use an external credentials store i have this instance of servicenow synchronized with cyberark which is providing my credentials they're under the idv center and since i've checked the external credentials store box servicenow is configured to go ask cyberark for the vcenter credentials all right let's go ahead and get started i'm going to do a new discovery schedule and i'll call this vcenter discovery there's a few options but in this case i'm going to discover configuration items i'm going to select a specific mid server i only have one configured it's the dvd-3 underscore mid server and i have a location configured it's david's house yes and i'll go ahead and hit submit i'll go back into the discovery and i need to tell servicenow what ip address the vcenter is located at one easy way to do that is with quick ranges and i could enter more but the key here is to only discover one ip address of our vcenter and see what information we can get back so i'm going to go ahead and make the ranges you can see that it's created now and my scan is set for on demand i will go ahead and discover now this should take about a minute to discover so i'm actually going to wait live just so we can see how long it takes we can see that servicenow is creating a discovery log it's noting what devices it finds it's creating an ecc queue and we'll go ahead and refresh and our discovery has actually been completed 28 seconds so let's go ahead and look at our previous tables in our ci relationships we now have 139 and our configuration items we have 98. in 28 seconds servicenow was able to figure out all of this one of those should be called david's house the data center and let's go ahead and look at this data vmware data center configuration item it has relationships with almost everything that servicenow discovered so this list is nice but it's a little hard to visualize so let's go ahead and bring up our dependency map and i'm going to zoom in because there's so much going on in the vcenter but we can see our vcenter instance with our data center an esx server the virtual machines the distributed ports our data stores our network adapters everything that's else that is going on in vcenter servicenow was able to create this map in under 30 seconds thank you all for watching my video and please stay on the alert for future videos that i might be able to put out