Finding your Way through OCS-NG Features in Software Display 39 barcode in Software Finding your Way through OCS-NG Features

Finding your Way through OCS-NG Features using software toinclude ansi/aim code 39 with web,windows application Web app Working with the inventory As obvious as it seems, we have built and want to maintain a full-fledged inventory platform with the ability to gather and store data in a centralized solution. Ultimately, that is the goal of inventorying and asset management. The OCS-NG agents, are pulling out a huge amount of information that is stored in the central database.

Through the OCS-NG web interface we have a user-friendly manner to access and work with this data. Imagine how hard it would be to generate SQL queries inside some database interpreter. That would not really be a seamless inventory interface.

The web interface does all of these behind the scenes. We just need to learn its functions and features. Besides those five query functions that we talked about earlier, which are present on the blue toolbar on the left, the inventory is much more capable of performing other functions as well.

As mentioned earlier, every time we click on a hyperlink, such as a hostname, a new browser tab is opened up. This tab loads up plenty of relevant information about the said host. Here"s a quick screenshot:.

The previous screenshot is Software 3 of 9 a brief summary. We have the following options in the next screenshot:. [ 120 ]. 4 . 1. Processor(s) 2. Memory 3.

Storage 4. Disk(s) 5. Video Card 6.

Sound 7. Network(s) 8. Controller(s) 9.

Slot(s) 10. Port(s) 11. Administrative Data 12.

Customization 13. BIOS 14. Software 15.

Deployment 16. Registry 17. Monitor(s) 18.

Input Device(s) 19. Printer(s) 20. Modem(s) We can surf through every component and find out every tidbit of information that the agent was able to pull out regarding that.

On the bottom of every page, we find these two icons:. The first function pops up barcode 3 of 9 for None the print window. It"s useful when we want to print the kind of information that is displayed. On the other hand, the second icon means "show everything".

This is really useful. The query is really fast, and it barely takes a few milliseconds as long as you don"t mind scrolling down through long pages. This way we can see all of the inventoried data regarding that host displayed on the screen, without being limited to specific areas.

. [ 121 ]. Finding your Way through OCS-NG Features Summary. The focus of this chapter Software Code 39 was to achieve familiarity with the user interface of the OCS web console. First, we explained what each toolbar icon does, the kind of functionalities that are hidden beyond those tiny images, and so on. Practically, we can do almost anything inside the web console; even tune server-side variables that affect the behavior of the inventory.

It"s important to take some time to be comfortable surfing through toolbars. We then elaborated on some configuration best practices and tips. We learned how to set up new users with privileged access rights.

Then we introduced and explained the concept of TAG-based repartition. In case of medium-to-large organizations, this is a huge need, but if it"s implemented appropriately it helps in case of small infrastructures as well. If the functionality is incorporated into OCS-NG, why not learn to use it the right way Practice has taught us that some preventive measures are to be taken in order to maintain a clean and ordered inventory.

We not only discussed the techniques of eliminating redundancies, but we also understood why they happened, and how to solve other common pitfalls. Furthermore, we got into overviewing the Registry query function. While the inventory agent does a great job on locating software on client machines, sometimes we want to be able to track specific registry keys and values.

The examples we brought were mainly software based, but technically, we can track any field inside the registry. Moving ahead, we also learned where to import the inventory data of hosts that are not networked. Once this is done and supposedly our inventory is clean, we got to spend some time understanding how to carry out common tasks.

We elaborated tiny bits of how to search for software, generate reports, find out the hardware specs of inventoried hosts, and so on. After all, this is why we wanted to set up an inventory solution from the start! In the next chapter, we will get into the depths of IpDiscover. We plan to go beyond the inventorying mechanism in order to fully comprehend how elevation happens.

After these, we are able to make well-thought decisions on how to tune the retrieving process.. [ 122 ].
Copyright © . All rights reserved.