NetMan Desktop Manager Quick-Start Guide This document describes the procedure for installing NetMan Desktop Manager. The example given here presents a standard installation scenario. For details on all options, please refer to the full documentation. The following descriptions are applicable for Windows Server 2003 and 2008 with active terminal services. If you need more information on these prerequisites, refer to the following in our PDF database: Setting up an NDM Server. Contents 1. Preparing the Installation 2 2. Installation 2 3. Entering the License Code 4 4. Installing the NetMan Desktop Client (NDC) on the Server 5 5. Rolling Out the NetMan Desktop Client in the LAN 6 6. NDM Web Interface: Basics 7 7. NDM Web Interface: Setup 9
1. Preparing the Installation Windows Server terminal server must be switched to installation mode before the installation can begin. To activate the installation mode in Windows Server 2008, open a command prompt and enter "change user / installer". Note: The Windows Server 2003 switches to installation mode automatically when a file called setup.exe or installer.exe is executed. 2. Installation The next step is to run the NDM Setup.exe file. After a brief introduction, the two installation options are described. Afterwards, accept the license agreement to continue with the installation. The next two dialogs prompt you to select the folder for installation of NetMan Desktop Manager and the name of the share. 2
Then the name for the NetMan Web Services share is prompted. This is generally stored "C:\NDM4\WebSrv\hh\*.*". The two subsequent dialogs prompt you to enter registration data (name and company) and select a language. The next step is to configure the NetMan server and the NetMan web server. This is where the ports used by NetMan Desktop Manager are defined. With the default settings, these are ports 9201/9200, and 80/443. Once these settings have been configured, installation starts. 3
3. Entering the License Code With the default settings, the Registration Wizard launches automatically on the conclusion of installation. Once the license data has been entered, it is displayed in the License Management program. Afterwards, the NetMan Services are automatically restarted. Please keep in mind that if licenses are registered later (e.g. when adding supplementary licenses), the system must be restarted by hand. 4
4. Installing the NetMan Desktop Client (NDC) on the Server Client installation starts automatically as soon as registration is completed. Enter the server data in the first client-setup dialog. If the client setup was launched directly by the server, the required data is entered automatically. In the subsequent dialog you can define whether the client starts automatically when the computer is started up. Select the "Add NetMan Desktop Client to system tray" option to have the NDC icon shown in the system tray. You can start and stop the NetMan Desktop Client using this icon. After client components have been installed, you can define whether universal printer support is installed as well. This concludes the installation procedure. The client is now launched on the server: 5
5. Deploying the NetMan Desktop Client in the LAN After the server components and the NetMan Desktop Client have been installed on the server, the client must be installed on the workstations. Method 1 The client can be installed by running the client setup, which is stored in the server share: \\<server name>\ndm4\config\client\setup\, directly on the workstation. If there is no automatic software distribution tool installed, the setup program must be executed on each computer individually. Method 2 (recommended) Using the NetMan Desktop Client Distributor to install the NDM client software is easier than Method 1 above. Before beginning the rollout with this method, make sure the Windows firewall is deactivated on all client machines. Furthermore, the account used to carry out the installation must have administrator rights on the client PCs. The main window of Desktop Client Distributor shows the existing domains, groups and stations in a tree diagram. Once the client has been installed on the workstation, the sample NetMan desktop is embedded in the Start menu and can be used to launch the sample applications. 6
6. NDM Web Interface: Basics As an alternative to the use of locally installed client software, published applications can be called using NDM's web interface. To do this, open a browser on the workstation and enter the IP address or URL for the server in the address line. Following successful login, the browser opens a web page containing the applications or information pages designated for that user. These are opened by mouse click. 7
NDM offers two launch methods for web access to applications. 1. NetMan RDP web client launch method (Windows 98 and later) To open a NetMan Desktop Manager session on the client machine using the RDP web client, the NetMan RDP web client must be installed on the workstation. If this launch method is selected in the server, the client is offered for download on the web page. The web client is compatible with Windows 98 and all later Windows versions. To install the web client, either the user at the workstation must have local administrator rights or the installation of the web client must be carried out by an administrator. Alternatively, the MSI package stored under %HHWebPath%\HTML-View\_download can be used for distribution over AD: nmrdpinst.msi 2. Java launch method The only prerequisite for opening a NetMan Desktop Manager session on the client machine over Java is Java Runtime Version 1.5 or later installed on the workstation (Windows, Mac or Linux). The Java client starts automatically when an application is called from the web interface. 8
7. NDM Web Interface: Setup Open the NetMan Web Services Settings to define the launch method and other client-dependent settings. In the "Launch Method for Access over HTML View" dialog, you can determine which web client is used by client PCs. With the default setting (*.*.*.*) the NetMan RDP web client is used as the launch method. You can link IP addresses, ranges of IP addresses, host names and domain ranges with the desired launch methods. The buttons in the upper right-hand corner let you edit the list of launch methods: In the example below, clients in the IP 192.168.1.70-100 launch with the Java RDP web client. All other clients launch with the NetMan RDP web client. You can assign launch methods according to other criteria than IP address; for example, by using the "browser agent" setting to designate a client operating system. In the example shown here, "*linux*" has been entered in the "Browser agent" field and linked to the Java RDP client launch method. The subsequent rule, on the other hand, launches the session with the NetMan web client. These mechanisms make it easy to ensure that each client is assigned the correct launch method. The "Rules for Launch and Settings" dialog also lets you configure far more complex rules for assigning launch methods. 9