[Music] please subscribe to my channel and click on the bell icon to get the regular updates of my channel and do not forget to like comment and share hello everyone welcome back to sas with servicenow this session is part of servicenow discovery training and is also part of section discovery applications and modules and the section is running a quick discovery we will run a quick discovery in our instance and discover our own mid server machine which is a windows server servicenow already has access to this machine so there should not be any kind of issue fetching information of this machine let's see how discovery runs and complete a cycle of running discovery in different phases before i run discovery i will just validate mid servers of my instance because that's a prerequisite for running discovery in service now so i will go to mid servers click on servers over here you will see these two mid servers which we installed on one windows machine that is windows server 2012. you must have seen installation of these mid servers in my previous video which was part of the section of mid server now both the mid servers are up and running and they are also validated let's open one racket and we will see whether this mid server is enabled for discovery feature or not how we will see that you go to this related list supported applications now as of now all is already selected which means all types of applications can use this mid server including discovery so i don't have to select discovery application separately in this related list now let's go to windows machine where mid servers are installed so here's our windows machine where we have installed mid server let me ask a question how discovery will be able to connect to internal network machines we know it got access via mid server however how discovery will come to know what machine it has to discover now all the machines in the network will always have one unique thing and that is address and that address is ip address so discovery uses ip address which is a unique address of different machines and devices so we will find the ip address of this machine first before we run the discovery you have to specify that ip address in your servicenow instance so that discovery can be launched for that particular ip address so let's go to command prompt so we have command prompt on the server and let's try to look for ip address of this particular machine so i will just type ip config and i will press enter now here is the ip address this ipv4 this one this is the ip address of this particular machine now as this is a mid server machine you can see same ip address on mid server racket as well so if you will go to mid server record in your instance you will see the same ip address over here as well now we need to discover this particular ip address we have to fetch all the information about this ip address what device we have as of now we don't know we don't have that information in our this particular instance but how we will come to know about it because we will run the discovery so let's run a quick discovery on this instance so i will go to discovery application i will click on discovery schedules you will find this button over here that is quick discovery click on it you will see this pop where you have to provide the ip address of that particular machine now we are just running the quick discovery so i will provide one ip address and that is 172 maybe we can just take a look 16.220 and then we have dot three now here i can select the mid server that with mid which mid server i want to run this discovery so if i click on this it will give me those two mid server i can select any one let's select this one and if i will click on ok this will run the discovery so if i will click on ok i will see a new racket created in this particular list that is discovery status and which says active as of now so i will click on this record that means discovery has been launched and you can see in this new record we have a state as active now discovery process has started so it has started running and now it will go into different phases of discovery and try to fetch different information of that particular device the device for which you have provided the ip address now here you can see some logs some other details as well for this discovery which is running currently so here we have logs you can see discovery got started and it says it started it found something because it is it is trying to connect with this ip address now it is trying to classify and if i go to devices you can see it has found this device as of now it is trying to classify it so we have provided that ip address it has populated the ip address but it has not populated other details yet it is still trying to find more details on that particular machine because discovery is still running so as of now you can see we have two activities one is completed so if i let's say i reload it so you can see three got started two got completed what exactly that two so now you can see here it has identified that is a windows server you can see here automatically i have not mentioned that detail i just provided the ip address to in servicenow instance that's it in discovery configuration that's it but system automatically found that that is a windows server machine which you can see over here so it has now classified it that means system has classified that hey is it a unix machine is it a windows machine so now it has classified it is a windows server machine the class is windows server but as of now cmdb is not populated yet now if i go to the next related list that is eccu which shows the logs of input and output messages which are going via mid server so you can see all different logs and activities happening via mid server and i can click on refresh as well it will try to refresh all other logs as well i think as of now it's still trying to run so you can see the third log in this particular discovery log here you can see uh now classifying so classification is already done and now it is trying to identify that okay i got i got to know about this the classification is windows server but now i need to identify it hey what machine is it what's its name what kind of information it has what kind of files it has what kind of software it has it will auto populate all those informations in cmdb automatically with the help of discovery this will take little bit i would say a little bit time as it trying to gather all the information from that particular machine if i refresh the record you can see it says completed which means this discovery has processed all the rackets and it is done with all the phases of discovery now if i will go to devices you can see this field cmdb ci is populated you can see a racket over here this is a reference field and you can see this racket which was empty before when we were running the discovery this was empty but now it has created a new ci in cmdb and you can see here as well it says completed activity created ci and if i go to logs you can see it try to search a lot of different information with the help of different patterns probes and it is keep on running keto keep on checking different rules and then at last discovery got completed and it populated those information and it created that ci that means this ci was not available in my instance so if i go here and i click on this racket so whatever records whatever devices discovery will try and try to discover you can see this kind of records so here you can see we have cmdbci if i will click this button it will basically open that particular ci with all the information of that windows machine which is a vmware machine absolutely so you can now understand the power of discovery application i didn't put any information that whether it is installed on the vm server where exactly it is installed what's the model id what's the name what operating system it has installed you can see it automatically went to that system and automatically populated all those information even the operating system even os version id name and if i go the interesting part comes here because if i go little bit bottom you can see all other information as well for your machine and that is the very important powerful feature of discovery that it tried to find that machine however it also additionally it tried to find other information as well like starting with network adapter so we have one network adapter in that virtual machine that is ethernet 0 then if i go to storage device how many storage we have so it is saying just one storage sas and which is 60 gb so we created basically i created that windows machine with 60 gb of storage and that's what it is showing over here then i go to file system that how many file system we have so there if i go to that machine quickly and i go to maybe here you can see we have c drive we have d drive which is a cd drive and if i come over here you can see it is a cdn dvd and this one is fixed and another one is system reserved whenever you will install windows machine you will always have this file system as well which which gets created automatically by windows then i go to in software installed and this is also powerful feature that whatever softwares are installed in that machine discovery will automatically populate that detail as well as of now it has internet explorer version as well and it has this windows operating system that is windows 2012 r2 operating system then on windows machine you have a lot of processes which runs on on that particular machine you can see that information as well what all processes are running you can see in this particular related list then we have serial numbers then we have ci ips what exactly the ipv we have you can see it says ip address we have also the subnet of that particular ip machine that is 255.255.255.0 it is also showing you the nick that what kind of nic card you have that that network adapter which you can see over here as well then we have memory module in that machine we have added 2gb of memory that is ram and you can see it has ram slot 2gb that is 248 mb 2048 mb then we have tcp connections and the last one is tracked configuration file in windows machine in that particular windows machine whatever configuration files you have system is populating that so discovery is also able to fetch those configuration files information as well now there is a different module which shows that data separately as well we learned about it and that is tracked configuration file so all those four rackets you will see here as well and if you will open it you can see the information about those configuration files it is also showing that on what machine these configuration files are available so this is how you can run a discovery in servicenow and populate data in cmdb now as i have this cmdb racket so if i click this again i can create any incident racket maybe problem bracket change racket because this is now aci and if i have to raise any incident or a change or a problem i can create it by tagging this particular configuration item and if i see which table it got created if i talk about class perspective i just go to let's say table basically it's a windows server so you can see the label is windows server cmdbci wind server which is basically extended from server so overall this got created in windows server class thanks for watching this video and have a great day