Two procedures for automating the import of computers and configurations (ADSI/WMI)

1- Procedure for automating the WMI inspection (task returning configuration information of all computers)

The WMI inspection program connects to each PC in order to read its configuration information.

When a PC is switched off, it is impossible for the program to get its configuration.

By automating the execution of the WMI program each day, most PCs will have been contacted over a period of one week.

The WMI inspection program is a “command line” program. The use of “Windows Scheduler” enables to automate the execution of the program.

Prerequisites:

The program must be executed on a server (the computer must always be running).
The Octopus application must be installed on the server upon which the program will be run.

Here are the steps to automate the execution of the program:

The details of the procedure by which to create a scheduled task vary from one version of Windows to another.

The procedure outlined below uses screenshots from Windows XP Professional.

Create a new task in Windows (Start > Settings > Control Panel > Scheduled Tasks > Add Scheduled Task).

Select the following executable file: "C:\Program Files\Octopus\ESI.HelpDesk.WMIUpdaterApp.exe".

Select the “Daily” option.

Specify the time (ex: 10:00 AM).

Input the authentication data of a network administrator Windows account.

Check the “Open advanced properties” box.

In the “Run” field, add the following to the end of the program’s name:

/Login:YourOctopusUserName

/Password:YourOctopusPassword

(see the example below).

For the Login parameter, you must specify the Octopus user name.

For the Password parameter, you must specify the Octopus password.

Note that it is possible to add two (2) other parameters on the same line, as needed.

The /NoUsersDetection parameter serves to deactivate the import of users which have connected to the computer.

The /NoDbUpdate parameter executes the application without updating the database.

The files generated during the import process are contained within the program’s directory, C:\Program Files\Octopus\.

If your environment consists of several domains and if the server from which you wish to execute the WMI inspection cannot “see” the computers in the other domains, you will then need to configure this task on a server within each domain.

2- Procedure for automating the integration with Windows NT / Active Directory (task returning the list of users, computers and printers)

The program for integration with Windows NT / Active Directory connects to your server and gets / syncs the list of users, computers and printers. By automating the WMI program each day, the moment a user, computer or printer is added to the network, it will be added within Octopus. Moreover, if you have automated the WMI inspection, the new computers will also be updated.

The program for integration with Windows NT / Active Directory is a “command line” program. The use of “Windows Scheduler” enables to automate the execution of the program.

Prerequisites:

The prerequisites are the same as for the WMI inspection program.

Here are the steps to automate the execution of the program:

The steps are the same as for the procedure for the WMI inspection program except:

· At step 2, the file to select is: "C:\Program Files\Octopus\ESI.HelpDesk.ADSIReaderApp.exe"

· At step 4, the time should be at least 30 minutes prior to the execution of the task for WMI.

· At step 7, in addition to specifying the Login and Password, it is also necessary to specify the Domain and Protocol parameters.

Examples:

If you have an NT domain called “MyDomain”,

then the additional parameters will be:

/Domain:MyDomain /Protocol:WinNT

If you have an ActiveDirectory called “MyDirectory”,

then the additional parameters will be:

/Domain:MyDirectory /Protocol:LDAP

Note that the /NoDbUpdate parameter, which executes the application without updating the database, may also be added, as needed.

The files generated during the import process are contained within the application’s directory, C:\Program Files\Octopus\.

If an environment consists of several NT domains or of combinations of NT domains and Active Directory, you must create as many automated tasks as you have Active Directory domains. Each task should be automated on a server that can “see” the NT domain or Active Directory to be read.

Location: Index > Configuration management module