%@ Language=VBScript %>
![]() |
|||
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Upgrade InstructionsIf you already have OCS Inventory installed, MAKE A COPY of your database (and, if you have modified it, the Global.asa file of the Web Manager folder). Follow the installation instructions and select the same setup folder as your previous installation. Then, run OCS Inventory Manager, log in under an Administrator account and import your old configuration to the new database with the command "Import from another DB" of the "File" menu. If your are using Web Manager, restore your previous Global.asa file if needed and restart the web server.
Setup InstructionsUnzip the OCSInventory_Setup.zip file in a folder and run setup.exe on a file server (web server if you want to use the Web Manager) of your network. OCS Inventory Setup will create the following sub folders.
OCSInventory.mdb, OCSInventory.exe, OCSInventoryManager.exe files MUST be kept in the same directory ! This is because when the Agent or Manager runs it uses the current path to attach to the database.
1. Running the Agent.The Agent is a simple application that runs on all of the clients. NB. The Agent was hard coded to only run once per day ! This is so you can leave it in a login script and it only runs in the morning, Not after every re-boot or login. Share the Application folder and make sure it is accessible to everyone (Authenticated
users if you are running Windows NT4 SP 4 or higher or Windows 2000/XP) and that everyone
has Read/Write access. If, for example, you put the files in \\MYSERVER\MYSHARE\INVENTORY,
then all you need to do to run the agent is put \\MYSERVER\MYSHARE\INVENTORY\OCSInventory.exe
in the default login script ! Their may be a lot of hard disc activity for 1 or 2 minutes when the agent run. Once the Agent has run open the OCS Inventory Manager or Web Manager file and check the reports to see what it has found.
Its as simple as that. So let me know what you think ! NB: If you encounter error while running the Agent, see HELP - FAQ page.
1.1. Using Daniel Arbour's BiosInfo tool to retrieve informations from BIOS.Daniel Arbour (Daniel.Arbour@Abbott.com) has build a 16 bits tool in DOS mode to bypass Win32 protected mode to access the BIOS. You can use this tool to retrieve informations from BIOS and store them to a CSV file. You can call this with the following without argument, and it will display informations to screen, or you can call it with the computer name as first argument, and optionally a filename as secong argument and it will store BIOS informayions to a CSV file. If called without filename as argument, the file is created in the current execution folder with the name "ComputerName.CSV", otherwise the tool uses the filename passed in the command line to store the informations. Next, you just have to call the Agent with the "/BIOS" or "-BIOS" command line switch to tell it to import the results (see the Usage page). You can find a sample script to run OCSInventory with this tool in the file named "run_ocs.bat". Just edit the first lines to match your needs and call it from your logon script with a command like "Call run_ocs.bat".
1.2. Setting up the WinIO driver to retrieve informations from BIOS.Caution ! This is an experimental tool. It does not work on all computers, especially under Windows 95 and Windows NT4. However, it works great on my LAN with Windows 98 SE and Windows 2000 SP2. I recommend that you ensure it is working on all your computers type and/or configuration with the DumpDMI.exe tool before you deploy it. OCS Inventory V2.00 is able to retrieve informations from DMI tables of a DMI/SMBios compliant BIOS. Because of Win32 protected mode, it requires a system level driver to be setup on the client computer. OCS inventory uses "WinIO" Version 2.00 driver from Yariv Kaplan (http://www.internals.com). Setup of the WinIO driver is done by "SetupWinIO.exe" tool in the "Application\Drivers" folder. Use "SetupWinIO.exe -h" to display usage of this tool. Under Windows 9X/Me, just run on each computers the "SetupWinIO.exe" executable from "Application\Drivers" folder. This will copy the file "WinIO.VxD" to the system directory. You can use the login script to deploy this driver on computers with the following commands: REM Check if Windows NT 2000 XP Under Windows NT4/2000/XP, the driver must be setup under an Administrator account, because it is launched at system startup as a Windows NT driver service. So, run on each computers the "SetupWinIO.exe" executable from "Application\Drivers" folder. This will copy the file "WinIO.sys" to the system directory and register the driver in the system level services. NB : There is 2 way to get DMI tables.
Once you've setup the driver, you can use the "DumpDMI.exe" tool in "Application\Drivers" folder to display in a console the content of DMI tables. Use "DumpDMI.exe -h" to display online help for this tool. This tool works like SMBios2 tool from IBM Corp.
2. Viewing reports and managing configuration.There is 2 way to view database content.
2.1. Running OCS Inventory Manager Windows GUI.Just run the OCSInventoryManager.exe file and enter authentication informations (default is "Admin" as Operator ID and "Admin" as Password). You can run OCS Inventory Manager from a client computer by running \\MYSERVER\MYSHARE\INVENTORY\OCSInventoryManager.exe. OCS Inventory Windows Manager require DAO 3.5 to be setup. See HELP - FAQ page on how to setup DAO 3.5.
2.2. Running OCS Inventory Web Manager through an ASP 2.0 Enabled Web Server.OCS Inventory Web Manager has been tested on Windows NT 4 + IIS 4 web server. It's buid in ASP 2.0 and must work on ASP 2.0 compliant web servers. Following instructions applies to IIS 4 and higher web server.
NB:
|