Lösungen zur Verwaltung von Windows Active Directory-Domänen

Some information about distributions

How to create a new distribution?

How to create a new distribution?

Once a distribution server is added, you can create new distributions.

To create a new distribution, select the Distribution menu, then Create a new distribution or you can also click the icon on the toolbar.

According to the defined open mode, IDEAL Dispatch Console displays a simplified single window or a wizard for creating a distribution in 10-steps.

• Case of a simplified single window mode:

• Case of Wizard mode:

Each of these steps is detailed below:

• Step 1 : Name and description of the distribution

Enter the name and description of the new distribution. These informations enable you to clearly identify it in IDEAL Dispatch Console. The description is optional.

You have access to all the saved or previously implemented distribution in the dropdown.
So you can easily load their settings.

 

• Step 2: User account for running of the distribution agents

Enter the user account to be used for starting distribution agents (IDispatchAgent). This user account must have the Domain Admins privileges on all servers and workstations. The account must be entered in the form DOMAIN\Administrator.

By default, it is suggested that you use the same account used to start the distribution server.

You can view and edit the properties of an account using ().

• Step 3: Distribution agents setup

Set the date for installation of distribution agents on servers and workstations. This only applies to the installation of agents and no their execution. You can also configure the maximum number of simultaneous installations. This will lessen, if necessary, the traffic generated by the installations on your network.

It is recommended to limit the number of concurrent installations during the local execution or copy a large file on a large number of target computers.

Advanced:

• Agents will attempt to install for:

This option determines the maximum period during which IDEAL Dispatch Server will try to install the distribution agent on a workstation. This period is in minutes and can be set between 10 and 9999. IDEAL Dispatch Server uses this option to try a new installation of the distribution agent if there is a failure, making it possible to manage workstations that have not been started up, those which are being started up and those which have not yet been connected to the network (nomadic workstations or others). By default, this period is 120 minutes.

After this time, the distributions are placed in the stand-by distributions folder.

• Wait time between two attempts will be:

Sets the period in seconds between two connection attempts on a workstation where an installation failure has occurred. By default, this period is 120 seconds.

• Force stopping of the agent after a certain period of waiting:

Force stopping the agent after a certain waiting time, and thus interrupting the current execution on a target computer. Allows to stop actions pending a response or interaction. By default, this period is 100 minutes.

• Process priority in running distribution agent installation:

Each installation is run by a separate process. This makes it possible to carry out all the installations simultaneously. You have the option to set the priority the system gives the processes: Low, Normal or High. If the installation must be carried out on a large number of workstations, we advise you to select a Low priority, allowing you to place the minimum load on the system. By default, the priority is Normal.

• Create the shared administrative directory ADMIN$ if absent:

IDEAL Dispatch Server installs the Windows IDispatchAgent service agents on client workstations using the shared administrative directory ADMIN$. If this does not exist on the workstations, the agent cannot be installed properly. Authorizing IDEAL Dispatch Server to create the administrative directory ADMIN$ means the installation can go smoothly. By default, this option is on.

• Start up the RemoteRegistry service if stopped:

  IDEAL Dispatch Server may need to access client workstation registries. To do this, the Windows RemoteRegistry service must be started up on these workstations. Authorizing IDEAL Dispatch Server to start up this service if it is stopped or suspended prevents it from being impossible for certain agent installations to be carried out properly. By default, this option is on.

• Ping before installation:

Before trying to access a client PC's registry or installing agents, IDEAL Dispatch Server carries out a "ping" aimed at the client PCs. This allows faster processing if a target machine is not available. However, you must authorise an incoming echo request in the ICMP parameters of the SP2 XP firewall.

• Run the command Wake on LAN:

Runs the command Wake on LAN if the target computer is not detected and if the necessary information to Wake on LAN are indicated in the distribution server table.

• Use the IP address of the distribution server:

Distribution agents contact the distribution server using the IP address selected>. Useful in certain cases where the distribution server and the target computers are located on remote domains.

• Step 4: Execution of distribution agents

Set the date and time of execution of distribution agents on servers and workstations in your network. The execution of agents corresponds to the execution of actions that you have defined.

It is recommended to limit the number of concurrent executions in the remote execution of a large file on a large number of target computers.

• Run date:

You have the option to set a run date for distribution agents. This is optional. By default the agents run the set script or program when the Windows IDispatchAgent is started up.

• Limit the number of simultaneous runs:

As for installing agents, you can define the maximum number of agents run simultaneously. Using this option, you can regulate the traffic caused on the network by the running of a script or the updating of software, so as not to create a bottleneck. By default the number of runs is unlimited.

Advanced:

• Stop the execution of an action after a certain period:

  Allows to stop the execution of an action after a certain period and thus ends the action in waiting of a response or interaction. If this option is unchecked, the execution is never interrupted. By default, this period is 120 minutes.

• Assign one or more return code(s) relating to success when a script or program is run:

Using this option, you can define a value corresponding to the return code relating to success.

By default, an action is identified as successful if its return code is 0.

• Run actions using the current session user account:

Using this option, you can run actions using the current session account on the target computer instead of the agent start-up account.

• Stop the execution if an error is encountered:

Using this option, you can stop running the distribution as soon as an error is encountered. The following actions are not executed.

• Deactivate UAC during execution of the distribution:

Using this option, you can deactivate UAC on the remote computer during the execution of the distribution. When running is over, UAC is set back to it's previous configuration.

• Block user's mouse/keyboard during the execution:

Using this option, you can lock mouse and keyboard on the remote computer during the execution of the distribution. When running is over, mouse and keyboard are automatically unlocked.

• Step 5: Selection of servers and workstations

This step allows you to select servers and workstations for which the implementation of the actions must be programmed. It represents the basic selection. In fact, when you create a new action, it will be the default selection.


Three types of selection are possible: select the servers and client workstations according to their type or their name (NetBIOS or Active Directory) or their IP address or following an organizational unit.

• Selecting computers according to their type:

List of types available: All computers, All servers, All workstations, VISTA, Windows Vista, Windows 2008 Server, 2003 Server, Windows 2000 Server, Windows NT 4 Server, Windows NT 3.x Server, Windows 2000 Professional, Windows XP Professional, Windows NT 4 Workstation.

NOTICE: When you make a selection based on the operating system, IDEAL Dispatch Server retrieves the list of computers in the domain or workgroup server distribution.

• Selecting computers by name:

You can generate your list of names in two ways, using:

Netbios:

You add a computer to your selection:
- from a domain's list of computers using the (<-) button or with a double-click.
- by entering its name or IP address and then confirming with "Add".

Active Directory:
You can list the computers on a domain from your current user account or another account. In this case, you must enter the account name and its password

In these two cases, you can save or load a list of computers.

• Selecting an organization unit:

Select the organization unit corresponding to your computer selection.

If you have already defined actions, you can apply the new selection to the checked actions.

• Step 6: Filter selection

This step allows you to create the list of filters. When you create an action, your filtering is applied by default.

There are two types of filter:

Predefined filters: These are filters whose values and conditions are already filled in: OS Version,
OS Type, Version of Internet Explorer, Service Pack, Processor, Language, and Computer.

Customized filters: you can create your own filters by clicking on ( ).
The "advanced filtering properties" allow you to alter the interaction between the filters as well as select the computers involved in the filtering.

The "Test Filters" button allows you to identify the computers selected after filtering
is applied.

If you have already defined actions, you can apply the new filters selection to the
checked actions.

• Step 7: Selecting actions

This step ensures the actions are selected before being run on the services and client workstations. Several actions can be run in the same operation.

By confirming with the "Add" button, you can choose between different types of action:

"Executable" action: Allows you to run a local or remote executable file (.bat, .cmd, VB Script, .exe,
.com, etc.).

"Command" action: Allows you to run a command.

"VBScript" action: Allows you to run a local or remote VBScript file (.vbs).

"Software update" action: Allows you to install service packs or software updates.

"MSI" action: Allows you to install,repair, remove and announce a MSI file (.msi)

"Uninstall" action: Allows you to uninstall software in silent mode.

"File" action: Allows you to copy, move, delete, edit or print files and directories.

"System" action: Allows you to close a session, restart, shut down, lock, put the computer into extended
standby or cancel a stop action.

"Post a message" action: Displays a message on the target computer.

"Send Email" action: Allows you to send an email and attach files.

"Event log" action: Enables to write a message into a specific event log.

"Process" action: Allows to stop a process by it's name or PID.

"Services" action: To stop or restart a service on a target computer.

When an action is created, it will be applied by default to all the selected/filtered computers.
However, you can easily change the selection of computers or the filtering of an
action:

- from the menu, which can be opened with a right click.
- using the window "Advanced action option" () which can be opened by clicking on
the "Advanced" button.

If several actions are presented, you can organize the launch order by moving an
action up () or down () the list.

• Step 8: Procedure after running

Once the running of the script or program as been completed, you can decide to:

Do nothing

Close the session

Restart the computer

Stop the computer

If you choose to restart the computer or to shut it down, you can display an alert message to warn users. This message may be displayed for a certain period, in seconds.

You can also configure the removal of the Windows IDispatchAgent and IDispatchAgentInt services from the client workstation, as well as the "IDispatchAgent" directory.
The removal of the services allows you to leave no trace on the client workstation, but it prevents Stand-by distributions from being processed.

NOTICE: A copy of the file is made on the distribution server before it is deleted.

• Step 9: Distribution characteristics

This dialog box picks up all the distribution parameters in a literal way.
You have the option to edit them or print them.

• Step 10: Save or schedule the distribution

This last step consists of setting the storage mode for your distribution.
You have the choice between:

• Save this distribution:

When you decide to save a distribution, it is placed in a particular directory and it is therefore not scheduled for future installation and running. The point of storing a distribution is that it can be edited and copied as you wish.

• Program this distribution:

When a distribution is programmed, IDEAL Dispatch Server will not allow it to be
edited. This distribution is processed on the day and at the time scheduled, or immediately
if you have not set the date. A programmed distribution can be deleted provided its
installation date has not been passed.

• Schedule this distribution:

When a scheduled task is created, you can then edit, rename, delete or run it, or display the properties of this distribution with a simple right click of the mouse.

You must then give it a valid name.

You can then configure your scheduled task, based on your specific requirements.