Join the #BuildWithBuildAgent Challenge! Get recognized, earn exclusive swag, and inspire the ServiceNow Community with what you can build using Build Agent.  Join the Challenge.

Extend Windows OS - Servers Pattern

aginesh rajak
Tera Contributor

Hi Team,

I am not able to validate the last task for discovery simulator, 9th module part 3.

Any help is really appreciated.


9 REPLIES 9

There is no bug. I have done the whole course 3 times. If you follow the instructions properly then validation will go through.
Looks like you guys are missing on some step.

I was able to achieve it without manually setting the Description field value.

VikMach_0-1748353555947.png



Also, instruction is to update the discovered Windows Server Description field, NOT to create new new record in cmdb_ci_win_server. Manually setting the value will only clear the validation stage but that is wrong way to complete the validation and course.

VikMach_0-1748329436864.png

 

Hi @VikMach,

 

I was able to populate the Description field with the solution. It just does not match the value expected by the validation. I believe the solution is correct. The MID Server that was assigned to me for the training was not similar to what ServiceNow originally planned. There's was no way to fix the validation and I needed to complete the training.


I maybe wrong. It would be helpful if you could share your solution.

1) First, since you pointed at MID Server not being same. I am not sure what do you mean by that. You could RDP and login to the MID Server from your PC using the credentials provided on top of the course section and run the following command inside MID Server host to check what is the exact name of the Processor.

 

VikMach_0-1748349182907.png

This same name should populate in the Description field when you create the correct Pattern and run discovery against your MID Server.

Note - I guess everyone is given the access to same MID Server. I don't think ServiceNow will spin different Servers for different course takers.

My solution is same only difference is I added Filter Table step. I am guessing that was needed by the Validation to go through. Rest is same as you mentioned above.


 

I am  not sure why this bug is still existing and not fixed.  I felt like I cheated by putting the description in manually. Yes, it worked of course. I still think the bug should be fixed. IT seems like whenever I ran the test it seems to work but when ran the discovery it fails. My inclination towards this is there is an error in the existing Windows discovery pattern and for some reason there is an error with the baseline Windows OS. That needs to be addressed first. Actually there is no issue with the extension....

Hope whoever takes this test can benefit from this...