Updating the Windows agent in Software Creation ANSI/AIM Code 39 in Software Updating the Windows agent

How to generate, print barcode using .NET, Java sdk library control with example project source code free download:

Updating the Windows agent using software todevelop barcode 39 for web,windows application GS1 Standards Knowledge Centre First, let"s 3 of 9 for None cover the typical agent updating process on Windows operating systems. As mentioned earlier, we have at least the following two methods of updating the agents. Which one we choose depends on our OCS-NG setup.

If we use the agent set up as a Windows service, then we can use the package deployment mechanism of OCS-NG. The other option is using the OcsLogon launcher to force an update. Either way works fine.

. [ 208 ]. 8 . The package d eployment method requires us to create an archive (.zip) with the update file titled OcsAgentSetup.exe.

This setup is the latest agent client that we download from the official OCS-NG website"s Downloads section. We pick the execute kind of package when we create the package (remember, deployment package types from 6, Package Deployment through OCS-NG). Moving on, we execute the executable with the necessary arguments as follows:.

OcsAgentSetup.exe /S /UPGRADE /NOSPLASH /SERVER:ocs_serv_address /DEBUG Feel free to include additional arguments, if need be such as /NP (no proxy), /PNUM: xxx (port no), and so on. Refer to 2, Setting up an OCS Inventory NG Management Server for the complete list of switches supported by agents. Another option is specifying the /DEPLOY:version via OcsLauncher.

The version number stands for those 4-digit version numbers, for example, 4061 (latest). This way, the client will download and install the appropriate version number agent from the server. Let"s not forget that we can use the web-based administration console of OCS-NG to upload agent version archives (.

zip) to the communication server. These are called

As in the previous example, xxxx represents the version number. As another extra modality, we can use PsExec to update the clients. The same agent setup can be launched via PsExec remotely as long as the switches are similar to the one we created earlier when we opted for the package deployment function.

. Updating the UNIX agent On Linux oper ating systems, the process might be a little more time consuming as there are no practical remote "reinstall" or "upgrade" solutions. Almost all of the possibilities focus on deploying the package onto the machine and then running the agent installer script manually.

As of the latest agent version (1.0+), we have package deployment functionality under Linux as well. This means that we can generate the same package as we did under Windows.

However, there is one difference. We will execute the install script via those command-line switches that we require.

This way, the updating can become unattended. If this option fails, we can force a remote uninstall of the agent. Once that is done, we can use our methods to get the installer script deployed onto the machine and then run it via our command-line switches.

In a nutshell, all that we want is just getting the installer script to be executed via our arguments on the Linux machine. The rest are just details..

[ 209 ]. Best Practices on Inventorying with OCS-NG Updating OCS- Software Code 39 NG central server (when needed). OCS Inventory NG is a healthy project that is still supported and has a dedicated small team of developers behind it. While updates are not that frequent, this doesn"t mean that there are no updates. There are rarely major updates concerning the OCS management server or communication server.

However, when that happens, we need to know how to install the update. First of all, let"s consider a safety tip. We need to back up our database.

Yes, back it up! NOW! Read that sentence again. This is crucial as newer updates always bring a little bit of schema update and change the structure of our OCS database (ocsweb, in our case). The steps for backing up the database were explained at the beginning of this chapter.

Moving on, we download the latest OCS-NG central server archive and extract it into the /var/www/ocsreports/ folder depending on our configuration (or \xampp\ ocsreports\). We overwrite our files and move on. From this step, there are two little distinctions comparing a Linux OS versus Windows Server (with XAMPP).

In the case of Linux based operating systems, we need to follow the instructions of the install script. As expected, we will skip the Perl modules and all of these preliminary steps, unless they are specifically required to be updated as well. Either way, the install script will know what to do.

Once it is done, we navigate to http://ocs-server/ocsreports. The same old page loads up when we started our OCS-NG installation for the first time. It will automatically update the database schema and other table-specific information if required and finally verifies if everything is fine and ready to go.

Then it asks the user to input the MySQL database information. As a final step, the updating is already finished! Under Windows operating systems, we launch the OCS setup wizard. By default, it should auto-detect that there is an already existing OCS installation on the computer.

Therefore, it will not select the XAMPP components and also completes the path of the OCS installation directory. Verify these and only if they"re fine, move on. Keep in mind, it is pointless to update and mess with XAMPP components if we update only OCS-NG.

The rest of the procedure is the same. It updates the database schema and everything else. The process is verbosely logged within your web browser via dynamically-generated PHP pages.

Should there be errors, their reason is clearly pointed out. But if you are updating, you should not encounter any of them. The final step asks for MySQL information.

. [ 210 ].
Copyright © . All rights reserved.