Welcome!

Microservices Expo Authors: Liz McMillan, Elizabeth White, Pat Romanski, Gopala Krishna Behara, Sridhar Chalasani

Related Topics: Microservices Expo, Containers Expo Blog

Microservices Expo: Blog Post

Network Inventory Methods

All the inventory programs use approximately one scheme

A company's managers have to be aware of what hardware and software is on hand, where it is situated, know its quantity, and what is necessary to increase the employees' effectiveness and the whole network's stability. If the managers or system administrators do not have such information, it can lead to certain problems. First of all, it can be the cause of huge expenses on unnecessary software that is never used. Secondly, without inventory database, the system administrator can miss the date of antivirus software updates or hardware upgrades that can be dangerous for network safety. Thirdly, cracked programs or duplicated licenses can be installed by users, which is out of the Copyright Law. To prevent all these and many other problems, the system administrators have to manage the constant network inventory process.

For this purpose, the specialized software can be used. The program collects all the inventory data on the remote computers, keeps it, updates, notifies the system administrator on the network hardware and software changes, and allows him to generate a lot of various reports on the collected information.

All the inventory programs use approximately one scheme: the main program's module is to be installed on the administrator's computer, then the network scanning process starts. When all the network hosts are found, the program starts polling the remote PCs, collecting the necessary data, and creating the inventory database. But different network inventory programs can use different polling methods:

1. Using WMI technology (Windows Management Instrumentation). WMI is the computer system management tool that has a lot of advantages. This method does not require additional software or settings on remote computers. Besides, WMI does not create any additional load on monitoring PCs, and users without administrative rights cannot prevent the computers' polling. The main disadvantage of using the WMI is that the system administrator has to have the administrative rights on the remote machines to configure the security politics.

2. Using agents. This method is used if the security politics do not allow the system administrator to use WMI or if he does not have the administrative rights on the remote computers. In this situation the IT manager has to install agents on each computer on the network. However, the network inventory programs allow doing it remotely without distracting the employees.

3. Using clients. This method has the same disadvantage as the previous one - the system administrator needs to install clients on all the network PCs. But clients are used to poll the computers that are not on the network. Clients collect data automatically when users switch on their machines. The system administrator just exports the inventory database to a USB flash drive and then imports it in the main program's database.

Ideally, the network inventory program should give an opportunity to use all these three methods. It increases its reliability and widens its usability.

There is one fundamental fact: the network inventory process and its constant audit allows the system administrator and company's managers to make effective decisions on purchasing software and upgrading hardware. So in general, it helps to keep the network in actual and operable state.

More Stories By Dmitriy Stepanov

Dmitriy Stepanov is a CEO at 10-Strike Software, Network Inventory, Network Monitoring, Bandwidth Monitoring Software developer. 10-Strike Software is a software developing company. They offer their high quality networking products since 1999. 10-Strike Software specializes in producing Windows network software for corporate users.

Microservices Articles
Adding public cloud resources to an existing application can be a daunting process. The tools that you currently use to manage the software and hardware outside the cloud aren’t always the best tools to efficiently grow into the cloud. All of the major configuration management tools have cloud orchestration plugins that can be leveraged, but there are also cloud-native tools that can dramatically improve the efficiency of managing your application lifecycle. In his session at 18th Cloud Expo, ...
Traditional IT, great for stable systems of record, is struggling to cope with newer, agile systems of engagement requirements coming straight from the business. In his session at 18th Cloud Expo, William Morrish, General Manager of Product Sales at Interoute, will outline ways of exploiting new architectures to enable both systems and building them to support your existing platforms, with an eye for the future. Technologies such as Docker and the hyper-convergence of computing, networking and...
While some developers care passionately about how data centers and clouds are architected, for most, it is only the end result that matters. To the majority of companies, technology exists to solve a business problem, and only delivers value when it is solving that problem. 2017 brings the mainstream adoption of containers for production workloads. In his session at 21st Cloud Expo, Ben McCormack, VP of Operations at Evernote, discussed how data centers of the future will be managed, how the p...
Containers and Kubernetes allow for code portability across on-premise VMs, bare metal, or multiple cloud provider environments. Yet, despite this portability promise, developers may include configuration and application definitions that constrain or even eliminate application portability. In this session we'll describe best practices for "configuration as code" in a Kubernetes environment. We will demonstrate how a properly constructed containerized app can be deployed to both Amazon and Azure ...
As Enterprise business moves from Monoliths to Microservices, adoption and successful implementations of Microservices become more evident. The goal of Microservices is to improve software delivery speed and increase system safety as scale increases. Documenting hurdles and problems for the use of Microservices will help consultants, architects and specialists to avoid repeating the same mistakes and learn how and when to use (or not use) Microservices at the enterprise level. The circumstance w...
More and more companies are looking to microservices as an architectural pattern for breaking apart applications into more manageable pieces so that agile teams can deliver new features quicker and more effectively. What this pattern has done more than anything to date is spark organizational transformations, setting the foundation for future application development. In practice, however, there are a number of considerations to make that go beyond simply “build, ship, and run,” which changes how...
CloudEXPO New York 2018, colocated with DXWorldEXPO New York 2018 will be held November 11-13, 2018, in New York City and will bring together Cloud Computing, FinTech and Blockchain, Digital Transformation, Big Data, Internet of Things, DevOps, AI, Machine Learning and WebRTC to one location.
DevOpsSummit New York 2018, colocated with CloudEXPO | DXWorldEXPO New York 2018 will be held November 11-13, 2018, in New York City. Digital Transformation (DX) is a major focus with the introduction of DXWorldEXPO within the program. Successful transformation requires a laser focus on being data-driven and on using all the tools available that enable transformation if they plan to survive over the long term.
"We do one of the best file systems in the world. We learned how to deal with Big Data many years ago and we implemented this knowledge into our software," explained Jakub Ratajczak, Business Development Manager at MooseFS, in this SYS-CON.tv interview at 20th Cloud Expo, held June 6-8, 2017, at the Javits Center in New York City, NY.
Containers, microservices and DevOps are all the rage lately. You can read about how great they are and how they’ll change your life and the industry everywhere. So naturally when we started a new company and were deciding how to architect our app, we went with microservices, containers and DevOps. About now you’re expecting a story of how everything went so smoothly, we’re now pushing out code ten times a day, but the reality is quite different.