Forum Replies Created
Yes, I’ll try to explain better, when I duplicate a job I change both the unique name and the realm:
But for example, not all jobs are working with this configuration. If I duplicate and change the name and the realm of this jobs:
find_ICMP_socket_weekly_MX -> Works
find_SNMP_MX -> Works
find_WMI_MX -> Works
find_PowerShell_MX -> Not working
find_SSH_MX -> Not working
I get this error on the “find_PowerShell_MX” but the strange things is I don’t have “Config groups” for the default realm either.
2021-12-15 10:40:20.111315 info Prepare job: ‘findEndpoints.find_PowerShell_MX’
2021-12-15 10:40:20.123316 error loadPlatformSettings: No entry found in table “class ‘database.schema.platformSchema.ConfigGroups'” for realm ‘Mexico’
I was finally able to make it work (I was using the process and software as well) and the problem was I changed the “localhost” configuration of the “apiIpAddress” by the real IP on the globalSetting thinking this will make it reachable from the outside of the server, and that caused the API calls fail, so the jobs never updated the view. Since I see on the system the services/ports are up just listening on localhost, I was thinking if I change this configuration to the real IP, then the “apiIpAddress” will expose on the network and will be reachable from outside so I can use the adminconsole directly from my machine, but seems this its not the way…
Thank you for reach me out with your awesome ideas and tips, any word its just a light in the dark!
I already setup the contact with my company email requesting some information about the pricing plans and all that.
Regarding my current problem with the views, I think you’re referring the UniversalJob (run on CMD and active on the AdminConsole) and then the section “logicalModels” with the 2 jobs “build_application_via_process” and “build_application_via_software”, both are active and running plus I change the Trigger Type to “inverval” every minute to see if this solves this issue but seems no change… All the jobs on every section under UniversalJob are active right now, but still no “information” or “map” showing on the view screen section…
For the metadata app, I follow the videoguide on CMS, building the same as shown with 2 different domains and 2 different locations (throw ip address) with the same regular expressions and only 1 filter on Discoverable Object, so “”I think”” this part its “OK”…
Maybe I missing something? Maybe I build something wrong?
I was playing with the platform all this time and I finally manage to landscape the project to our company. And I was wondering if you know how can we hire the “services” and if you (personally you) would be interested on some “learning days”, just 2 or 3 days to teach us how to fully interact with the platform, maybe we can build screenplay or a “guide” just to know how many thing we’re interested to learn…
For example, I’m dealing with the “Metadata” and “Views” options, when I build a view (with all the process is shown on a video on the section “Modeling”) with some process, software or something to build and see the view, this doesn’t show on the screen, is just white… I can’t found any errors on logs or so, so I just don’t know why isn’t showing the diagram…
I finally be able to setup the dinamicDiscovery throw FQDN and with the last update you done on Github now works flawlessly. This is amazing!! I chose the rebuild option of the platform since my OCP server was full of test and things I wanted to delete, by now is clean and showing the required information plus I completed my 2 initial goals 🙂
“Yes, the software discovery in this tool is far more powerful than anything available with big-vendor proprietary ITSM discovery products. Not to mention it’s agent-less and doesn’t require a software database.”
I’m totally agree with this, its such an amazing feature, on a few clicks and typing, you can build a complete database of software installed on your infrastructure, not only software plus services (or headless dependencies too).
How can I thank you the useful information and guidance you gave me?
Wow, so there’s a bug on that job…
Is there any global option (maybe on the OS Parameters config) where I can change the “default” option to execute this type of jobs and discoveries throw FQDN instead of IP? Like *always* do throw FQDN assuming on my environment things based on IP are not possible or not working as expected as the normal functioning of this awesome tool…
Thank you so much!! I will dig about the consulting services to see more about this if I get this tool working on that I want to see… Since this will be my “landscape” to the powerful engine this tool has…
Hello again! Sorry for bother with another question but I’m so so close to achieve my 2 goals!
Finally I could setup find_powershell job to get it done and resolve all of the Kerberos problems, but now I’m facing the same error with the IPAddress on New-PSSession on the “powershell_app_components_base” job on dynamicDiscovery. As the previous message, if I put the same “connectViaFQDN” option on the “inputParameters” on the job, I can see on the Statistics (or logs) section the PS calls are doing throw IPAddress instead of the FQDN, so the New-PSSesion get failed over and over again…
Is there any other option or maybe I missing something?
Thank you so much for your support and your help!
That parameter you gave me works flawlessly, now the connections are made by FQDN (and now I’m dealing with some kerberos issues with the New-PSSesion).
I was wondering, how can I know if there are more parameters like that which might be helpful for tuning the jobs? Is it there any documentation or something where I can refer the available options or this I’m asking isn’t on the iNET and its private-related?
Thank you so much for your help!
OMG such a nice and deep information!
Thank you so much for sharing you’re knowledge with me (and the world).
Its late on my country right now, so tomorrow I will test all this new information you give me! I’ll update just to let you know your instructions gave some light to a lost worker 🙂
Thank you so much for your help, I appreciated so so much!