In BMC-IT we have defined an Extended Object;
Name = Domain Role
OS = Windows
Command/Script = cmd /c “echo QUIT | wmic ComputerSystem get Domain,DomainRole /value”
Execution Type = Remote
Grammar File = name = value grammar (nsvp.gm)
Domain Controllers should return a value of 4 for DomainRole
did you copy/paste that ? the double quotes might not actually be double quotes. try typing those in ?
i tried that same eo definition and i typed it in instead of copy/paste and it worked.
Hey Dan. Want to submit this as a ZipKit?
There is a registry key that will tell you if it's a Domain Controller or a Member Server.
WinNT = workstation
LanmanNT = domain controller
ServerNT = member server
You guys all missed the purpose of his question, which is to create a smartgroup to find domain controllers. If you need to create a smartgroup, there's no way to do it using out of the box properties. You would need to create a custom server property, and fill it with a script every day for example, which is where you can use one of the many ways to define if a server is a DC or not. An extended object won't be of any help here as you can't reference it in a server smartgtoup.
That was it….works now.
Create the EO.
Create a template that discovers on the existence of the EO or the ‘domainrole=5’
Create a server smart group based on TEMPLATE* = the template.
Can I use this in a discovery job to build a component smartgroup. If not, what’s the best way to set a property value with domain controller “true”?
You can but you don’t need to – you can do the server smart group w/ the existence of the component. you don’t need a server property.
Can you help me define a component template using this extended object?
discovery signature tab:
create a discovery job w/ the template and run it
server smart group condition
when you select the 'TEMPLATES*' on the left-hand side of the condition, you'll get a grey'd out box on the right hand side w/ a ... to click on which brings up a navigation page in the templates space where you select the template.
Joe is right I think, registry exists to determine this, so EO is not REALLY needed!
Bill is right, create a CT with Discovery rules to detect the registry value for Domain Controllers, run Discovery and then create a Server Smart Group that matches servers with that Component!
I did the same here, and here's a few screen shots on the definition of the Server Smart Group once the CT that I named Domain Controller is built and the Discovery Job for the CT run;
And here is the same rule when saved (display is slightly different);
As Bill noted, this should work like a champ.
In this case, no need to create yet another EO or Server Property.
More in line with the way BSA was designed to be used here...