TNMS Core

14.0 10

Installation Manual (IMN)

Issue: 2 Issue date: July 2013

A50023-K1027-X040-02-76D1

Nokia Siemens Networks is continually striving to reduce the adverse environmental effects of
its products and services. We would like to encourage you as our customers and users to join
us in working towards a cleaner, safer environment. Please recycle product packaging and
follow the recommendations for power use and proper disposal of our products and their
components.
If you should have questions regarding our Environmental Policy or any of the environmental
services we offer, please contact us at Nokia Siemens Networks for any additional information.
 Installation Manual (IMN)

The information in this document is subject to change without notice and describes only the
product defined in the introduction of this documentation. This documentation is intended for the
use of Nokia Siemens Networks customers only for the purposes of the agreement under which
the document is submitted, and no part of it may be used, reproduced, modified or transmitted
in any form or means without the prior written permission of Nokia Siemens Networks. The
documentation has been prepared to be used by professional and properly trained personnel,
and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomes
customer comments as part of the process of continuous development and improvement of the
documentation.
The information or statements given in this documentation concerning the suitability, capacity,
or performance of the mentioned hardware or software products are given "as is" and all liability
arising in connection with such hardware or software products shall be defined conclusively and
finally in a separate agreement between Nokia Siemens Networks and the customer. However,
Nokia Siemens Networks has made all reasonable efforts to ensure that the instructions
contained in the document are adequate and free of material errors and omissions. Nokia
Siemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues which
may not be covered by the document.
Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NO
EVENT WILL NOKIA SIEMENS NETWORKS BE LIABLE FOR ERRORS IN THIS DOCUMEN-
TATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT,
INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT
LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS
OPPORTUNITY OR DATA,THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR
THE INFORMATION IN IT.
This documentation and the product it describes are considered protected by copyrights and
other intellectual property rights according to the applicable laws.
The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark
of Nokia Corporation. Siemens is a registered trademark of Siemens AG.
Other product names mentioned in this document may be trademarks of their respective
owners, and they are mentioned for identification purposes only.
Copyright © Nokia Siemens Networks 2013. All rights reserved.

f Important Notice on Product Safety

This product may present safety risks due to laser, electricity, heat, and other sources
of danger.
Only trained and qualified personnel may install, operate, maintain or otherwise handle
this product and only after having carefully read the safety information applicable to this
product.
The safety information is provided in the Safety Information section in the “Legal, Safety
and Environmental Information” part of this document or documentation set.

The same text in German:

f Wichtiger Hinweis zur Produktsicherheit

Von diesem Produkt können Gefahren durch Laser, Elektrizität, Hitzeentwicklung oder
andere Gefahrenquellen ausgehen.
Installation, Betrieb, Wartung und sonstige Handhabung des Produktes darf nur durch
geschultes und qualifiziertes Personal unter Beachtung der anwendbaren Sicherheits-
anforderungen erfolgen.
Die Sicherheitsanforderungen finden Sie unter „Sicherheitshinweise“ im Teil „Legal,
Safety and Environmental Information“ dieses Dokuments oder dieses Dokumentations-
satzes.

2 A50023-K1027-X040-02-76D1
Issue: 2 Issue date: July 2013
Installation Manual (IMN)

Table of Contents
This document has 136 pages.

1 Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.1 Intended audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.2 Structure of this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
1.3 Symbols used in this manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
1.4 CE conformity declaration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.5 Available documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

2 Protective measures and handling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

2.1 Safety precautions when the unit is open . . . . . . . . . . . . . . . . . . . . . . . 14
2.1.1 Protection against excessive contact voltages . . . . . . . . . . . . . . . . . . . 14
2.2 Handling modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

3 Preparation for commissioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

3.1 Component delivery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
3.2 Hardware recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
3.2.1 Virtualization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
3.2.2 Installation and cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
3.2.3 Mirror disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
3.2.4 Standby Server and standby NetServer . . . . . . . . . . . . . . . . . . . . . . . . 18
3.3 Required software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
3.3.1 Installation software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
3.3.2 HW/SW configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
3.4 Installation sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
3.5 Operating system prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

4 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
4.1 Before you begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
4.2 Microsoft Windows Server 2008 R2 SP1. . . . . . . . . . . . . . . . . . . . . . . . 29
4.2.1 BEFORE you begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
4.2.1.1 Licensing information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
4.2.1.2 Protocol information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
4.2.2 Installation process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
4.2.2.1 Windows Server 2008 R2 terminal services . . . . . . . . . . . . . . . . . . . . . 32
4.2.3 Post installation configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
4.2.3.1 User Account Control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
4.2.3.2 Firewall configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
4.2.3.3 Firewall port setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
4.2.3.4 FTP server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
4.2.3.5 Component Services configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
4.2.3.6 Local security settings / local policies . . . . . . . . . . . . . . . . . . . . . . . . . . 41
4.2.4 The file WinHlp32.exe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
4.3 Microsoft Windows 7 Professional SP1 . . . . . . . . . . . . . . . . . . . . . . . . . 44
4.3.1 Hardware configuration under Windows 7 . . . . . . . . . . . . . . . . . . . . . . . 45
4.3.1.1 Installing the PCI I/O Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
4.3.2 User Account Control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
4.3.3 Firewall configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

A50023-K1027-X040-02-76D1 3
Issue: 2 Issue date: July 2013
 Installation Manual (IMN)

4.3.4 Firewall port setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

4.3.5 Post installation configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
4.3.5.1 Component Services configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
4.3.6 The file WinHlp32.exe. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
4.3.7 FTP configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
4.4 Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
4.4.1 .NET 3.5 / .NET 2.0. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
4.4.2 MSXML 4.0 SP2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
4.4.3 MS SQL Server 2005 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
4.4.3.1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
4.4.3.2 Standard Edition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
4.4.3.3 Express Edition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
4.4.3.4 SQL server configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
4.4.3.5 Service Pack 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
4.4.3.6 Uninstalling MS SQL Server 2005 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
4.4.4 Adobe Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
4.4.5 Java JRE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
4.4.6 TNMS Core Server component installation. . . . . . . . . . . . . . . . . . . . . . . 69
4.4.7 PLET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
4.4.8 TCOA proxy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
4.4.8.1 BEFORE you proceed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
4.4.8.2 3rd-party software for TCOA proxy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
4.4.8.3 Configuring TCOA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
4.4.8.4 Configuring TCOA proxy external interface . . . . . . . . . . . . . . . . . . . . . . 74
4.4.9 TCOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
4.4.9.1 TCOM installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
4.4.9.2 TCOM installation for SXC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
4.4.9.3 TCOM EML Server Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
4.4.9.4 TCOM DCN Management configuration . . . . . . . . . . . . . . . . . . . . . . . . . 83
4.4.10 Waveline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
4.4.11 NetViewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
4.4.11.1 Installing NetViewer Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
4.4.11.2 Installing NetViewer Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
4.4.11.3 Configuring TCOM DCN channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
4.5 NetServer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
4.5.1 OSI Stack installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
4.5.2 OSI stack configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
4.5.3 OSI Light installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
4.5.4 Uninstalling OSI stack. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
4.5.5 TNMS Core NetServer component installation . . . . . . . . . . . . . . . . . . . . 91
4.5.6 Configuring a Common Netserver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
4.5.7 CopSSH installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
4.5.7.1 Installation of CopSSH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
4.5.7.2 Configuration and use of CopSSH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
4.5.8 SSL Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
4.6 Backup Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
4.6.1 TNMS Core Backup Server component installation . . . . . . . . . . . . . . . . 96

4 A50023-K1027-X040-02-76D1
Issue: 2 Issue date: July 2013
Installation Manual (IMN)

4.7 Standby Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

4.8 Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
4.8.1 Adobe Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
4.8.2 MSXML 4.0 SP2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
4.8.3 Citrix XenApp 6.5 (for Windows Server 2008 R2) . . . . . . . . . . . . . . . . . 98
4.8.3.1 Operating System build Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . 98
4.8.3.2 Remote Desktop Services Licensing setup . . . . . . . . . . . . . . . . . . . . . . 98
4.8.3.3 Configuring Remote Desktop Session Host. . . . . . . . . . . . . . . . . . . . . . 99
4.8.3.4 Adding Remote Desktop License Server details on Remote Desktop clients
100
4.8.3.5 Installing XenApp roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
4.8.3.6 Joining an existing Farm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
4.8.3.7 Setup secure client-server communication . . . . . . . . . . . . . . . . . . . . . 102
4.8.3.8 Install hotfixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
4.8.3.9 Citrix License Server Reinstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
4.8.3.10 Installing IIS Management console . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
4.8.3.11 Configuring Web Interface (V5.4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
4.8.3.12 Post installation configuration tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . 107
4.8.3.13 Using group memberships to control access . . . . . . . . . . . . . . . . . . . . 107
4.8.3.14 Configuring TNMS Published Applications . . . . . . . . . . . . . . . . . . . . . 109
4.8.4 Installing TNMS Core Client component . . . . . . . . . . . . . . . . . . . . . . . 110
4.9 System Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
4.9.1 System Administration component installation . . . . . . . . . . . . . . . . . . 111
4.10 NetServer installation in Windows Server 2003 as guest for Windows Serv-
er 2008 R2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
4.10.1 Hyper-V prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
4.10.2 Hyper-V role installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
4.10.3 Configure a virtual network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
4.10.4 Create and set up a virtual machine . . . . . . . . . . . . . . . . . . . . . . . . . . 114
4.10.5 Guest operating system, integration services and TNMS Core installation
115
4.11 Anti-virus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
4.11.1 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
4.11.2 Useful considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
4.11.2.1 Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
4.11.2.2 Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
4.11.2.3 Firewall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
4.12 Uninstalling TNMS Core . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
4.13 Adding/removing individual TNMS Core components . . . . . . . . . . . . . 118
4.14 Active Directory configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
4.14.1 Active Directory configurations in Windows Server 2008 R2. . . . . . . . 119
4.14.1.1 Active Directory based COM security . . . . . . . . . . . . . . . . . . . . . . . . . 119
4.14.1.2 Active Directory based COM security with Windows Domain Authentication
121
4.14.2 Active Directory configurations in Windows 7 . . . . . . . . . . . . . . . . . . . 123
4.14.2.1 Active Directory based COM security with Windows Domain Authentication
123
4.14.3 Authentication extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

A50023-K1027-X040-02-76D1 5
Issue: 2 Issue date: July 2013
 Installation Manual (IMN)

5 Upgrade to TNMS Core 14.0 10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

6 Measures after commissioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

6.1 Documentation installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
6.2 Initial TNMS Core configuration using System Administration . . . . . . . 126
6.3 Routing settings for machines with multiple network adapters . . . . . . . 132

7 System expansion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

7.1 Adding clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
7.2 Adding NetServers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

8 Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

6 A50023-K1027-X040-02-76D1
Issue: 2 Issue date: July 2013
Installation Manual (IMN)

List of Figures
Figure 1 Labeling of electrostatic-sensitive devices (ESD symbol) . . . . . . . . . . . 14
Figure 2 A typical HW/SW configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Figure 3 How to set the TNMS Core installer to run with administrator rights in Win-
dows 7 and Windows Server 2008 R2. . . . . . . . . . . . . . . . . . . . . . . . . . 28
Figure 4 "Component Services" window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Figure 5 "My Computer Properties" window from "Component Services" window 38
Figure 6 "Access Permission" window from "Component Services" window . . . . 38
Figure 7 “Windows Security - Enter Network Password” window . . . . . . . . . . . . 39
Figure 8 "My Computer Properties" window from "Component Services" window 39
Figure 9 In "Launch Permission" window, select "Add" . . . . . . . . . . . . . . . . . . . . 40
Figure 10 "Select Users or Groups" window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Figure 11 "Launch Permission" window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Figure 12 "Local Security Settings - Audit Policy" window. . . . . . . . . . . . . . . . . . . 42
Figure 13 "Local Security Settings - Security Options" window . . . . . . . . . . . . . . . 43
Figure 14 “Network access: Let everyone...” window . . . . . . . . . . . . . . . . . . . . . . 43
Figure 15 "Component Services" window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Figure 16 "My Computer Properties" window from "Component Services" window 48
Figure 17 "Access Permission" window from "Component Services" window . . . . 48
Figure 18 “Windows Security - Enter Network Password” window . . . . . . . . . . . . 49
Figure 19 "My Computer Properties" window from "Component Services" window 49
Figure 20 In "Launch Permission" window, select "Add" . . . . . . . . . . . . . . . . . . . . 50
Figure 21 "Select Users or Groups" window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Figure 22 "Launch Permission" window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Figure 23 “Microsoft SQL Server 2005 Setup - Registration Information” window 55
Figure 24 Feature Selection window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Figure 25 “Microsoft SQL Server 2005 Setup - Instance name” window . . . . . . . . 58
Figure 26 “Microsoft SQL Server 2005 Setup - Service Account” window. . . . . . . 59
Figure 27 “Microsoft SQL Server 2005 Setup - Collation Settings” window. . . . . . 60
Figure 28 “SQL Server Configuration Manager - Protocols for MSSQLSERVER” win-
dow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Figure 29 “SQL Server Configuration Manager - TCP/IP Properties” window . . . . 62
Figure 30 “SQL Server Configuration Manager - Client Protocols” window. . . . . . 62
Figure 31 “Microsoft SQL Server 2005 Setup - Collation Settings” window. . . . . . 64
Figure 32 “SQL Server Configuration Manager - Protocols for MSSQLSERVER” win-
dow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Figure 33 “SQL Server Configuration Manager - TCP/IP Properties” window . . . . 66
Figure 34 “SQL Server Configuration Manager - Protocols for MSSQLSERVER” win-
dow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Figure 35 Add Channel for TCOM NetServer in the “DCN Management” Window 78
Figure 36 Select TCOM Channel as the channel type in “Select Type” window . . 78
Figure 37 Enter the ID Name for the Channel on the “General” tab in the “DCN” win-
dow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Figure 38 “DCN” window - “Scheduled Startup” tab. . . . . . . . . . . . . . . . . . . . . . . . 80
Figure 39 “DCN” window - “EMS Properties” tab (TMF 814 2.0) . . . . . . . . . . . . . . 80
Figure 40 “DCN” window - “Performance Management” tab . . . . . . . . . . . . . . . . . 81
Figure 41 Enter Data on the “GUI Cut Through” tab in “DCN” window . . . . . . . . . 82

A50023-K1027-X040-02-76D1 7
Issue: 2 Issue date: July 2013
 Installation Manual (IMN)

Figure 42 Status is "Connecting”. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Figure 43 Browse for the DCN objects of a channel in “DCN Management” window .
83
Figure 44 Select a DCN object from the “DCN Objects” list in the “Browse on Chan-
nel...” window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Figure 45 "General” tab of a DCN object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Figure 46 “NE Properties” tab of a DCN object. . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Figure 47 “DCN Management” window - SL64 in "Deactivated” state . . . . . . . . . . 85
Figure 48 “TNMS Core System Administration Login” window . . . . . . . . . . . . . . . 127
Figure 49 “SNMP Proxy Properties” window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Figure 50 “New Principal” window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

8 A50023-K1027-X040-02-76D1
Issue: 2 Issue date: July 2013
Installation Manual (IMN)

List of Tables
Table 1 Structure of this manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Table 2 Hardware and Operating System recommendations for Server, NetServer
and Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Table 3 Minimum partitions recommendations for TNMS Server, NetServer and
Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Table 4 TNMS Core installation components and sequence . . . . . . . . . . . . . . . 24
Table 5 Operating System prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Table 6 TNMS Core components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Table 7 Firewall rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Table 8 Group membership (groups in bold are built-in groups) . . . . . . . . . . . 108
Table 9 Published applications and group relationship . . . . . . . . . . . . . . . . . . 108
Table 10 Affected connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

A50023-K1027-X040-02-76D1 9
Issue: 2 Issue date: July 2013
 Installation Manual (IMN)

10 A50023-K1027-X040-02-76D1
Issue: 2 Issue date: July 2013
Installation Manual (IMN) Preface

1 Preface
TNMS Core is a telecommunications network management system comprising four
applications: Client, System Administration, Server and NetServer.
Before you begin commissioning, read the release notes, the general notes on docu-
mentation in the Technical Description (TED) as well as chapters 3 and 2 of this manual.

g To protect TNMS Core against viruses, you should install one of the supported anti-
viruses on all TNMS Core machines. Refer to the software release notes to see the sup-
ported versions.

1.1 Intended audience

This document is intended to guide users with installation responsibilities through the
installation of TNMS Core. These users should fulfill the following personnel require-
ments :
• Training to service technician level or equivalent training in communications engi-
neering
• Sound knowledge of transmission systems
• Appropriate, device-related training by the manufacturer (including required device
and system knowledge for the planned activity)
• Detailed PC knowledge, additional knowledge of operating Microsoft Windows
• Familiarity with LANs/WANs
• Basic knowledge of measurement systems
• Knowledge of operating electrostatic-sensitive devices
• Knowledge of handling optical fibers and laser light sources

A50023-K1027-X040-02-76D1 11
Issue: 2 Issue date: July 2013
Preface Installation Manual (IMN)

1.2 Structure of this document

This document, also referred to as manual, is structured as follows:

Chapter Title Subject

Chapter 1 Preface Provides an introduction to this docu-
ment.
Chapter 2 Protective measures and handling Provides information on handling
electrical components on TNMS Core
installation.
Chapter 3 Preparation for commissioning Provides information on the initial
installation.
Chapter 4 Installation Provides a guide to the TNMS Core
full system update to the latest
version.
Chapter 5 Measures after commissioning Specifies TNMS Core’s initial config-
uration
Chapter 6 System expansion Provides information about the
addition of Clients and/or NetServers.
Chapter 7 Abbreviations Contains a list of acronyms used in
the manual.
- Index

Table 1 Structure of this manual

1.3 Symbols used in this manual

The following symbols are used in this manual:
Notes
Notes provide useful information about specific situations that require your attention.
Example:

g The combination of name and address must be unambiguous to the server.

Warnings
Warnings give you important information which must be followed in order to avoid
negative occurrences (for example data loss).
Example:

f Perform the procedure as described. Failure to do so causes malfunction.

If you do not follow the directions, you will be responsible for any such malfunction.

12 A50023-K1027-X040-02-76D1
Issue: 2 Issue date: July 2013
Installation Manual (IMN) Preface

1.4 CE conformity declaration

The CE conformity declaration for the product is fulfilled if installation and cabling are
carried out in accordance with the documentation supplied. Where necessary, project-
specific documents should be taken into account.
Deviations from the specifications, or modifications during installation such as the use
of cable types with lower shielding dimensions may violate CE protection requirements.
In such cases, the conformity declaration is invalidated. Responsibility for any subse-
quent problems lies with the person responsible for the deviation.

1.5 Available documentation

In addition to the documentation listed in the Technical Description (TED) the following
information is available:

• Release notes:
These provide an overview of the hardware, software and documentation delivered.

• Documentation from the O&M Center:

On request, Nokia Siemens Network Technical Sales can supply project documen-
tation which provides specific information about the installation. These planning doc-
uments are available to the customer after installation work is completed.

• Protocols:
During commissioning, an acceptance protocol should be maintained. The accep-
tance protocol supplied must be completed and signed by Nokia Siemens Networks
service personnel and the customer to prove correct commissioning of the system
and to provide a record of the initial configuration in case of later queries.

• Field test protocols:

To help ensure successful commissioning, you can also consult the official field test
protocol. These provide information on the values used in system testing, and can
be obtained from Nokia Siemens Networks Technical Sales.

A50023-K1027-X040-02-76D1 13
Issue: 2 Issue date: July 2013
Protective measures and handling Installation Manual (IMN)

2 Protective measures and handling

Protective measures and information on handling electrical components in the TNMS
Core installation is provided here.

g As a general rule, you should always note the manufacturer’s instructions when
handling devices such as PCs, monitors, printers and tape drives, or when installing
modules such as network cards.

2.1 Safety precautions when the unit is open

Before opening the unit, remove the power cable.
Once the unit is open, live connector pins are freely accessible. To prevent electric
shocks, make sure that these pins do not come into contact any conductive material.

2.1.1 Protection against excessive contact voltages

When dealing with the power supply, observe the safety precautions as specified by the
German DIN standard VDE 0105 (operation of high-voltage systems). This standard
defines, in detail, the steps to be taken by the operators of electrical installations and the
users of electrical equipment to ensure the safe maintenance of electrical installations
and equipment.

2.2 Handling modules

Modules labeled as shown below are equipped with electrostatic-sensitive components.

Figure 1 Labeling of electrostatic-sensitive devices (ESD symbol)

All modules with ESD components have an outer grounding edge which is connected to
the module ground and can be used when gripping the circuit board.
Modules are fully protected if they are enclosed in a shielded, unopened housing.
Nevertheless, the following basic safety precautions should always be followed when
handling ESD components:
• Always use a grounding bracelet connected to a grounding socket when unpacking,
packing, touching, unplugging or plugging modules bearing the ESD (German EGB)
symbol. This will ensure that the modules do not get damaged.
• Avoid touching the component connections, connector contacts or conductor tracks
(even if you are properly grounded).
• When unplugging and plugging modules, make sure you use the provided handles.
• If modules are only gripped by the handles for plugging/unplugging, they should not
be transported in a horizontal position (danger of breakage).

14 A50023-K1027-X040-02-76D1
Issue: 2 Issue date: July 2013
Installation Manual (IMN) Protective measures and handling

• When you remove the module from its subrack, place it on an antistatic mat.
• Make sure that all measuring equipment used is grounded.
• If you are using ungrounded measuring equipment, briefly connect the measuring
probe to ground (discharge) it before performing measurements on components and
modules.
• Ensure that the modules are installed in the correct slots.

g European standard EN50082-1 contains detailed information on the correct handling of

electrostatic-sensitive devices.

A50023-K1027-X040-02-76D1 15
Issue: 2 Issue date: July 2013
Preparation for commissioning Installation Manual (IMN)

3 Preparation for commissioning

3.1 Component delivery

Before installation, be sure that:
• the delivery is complete and in accordance with the delivery units specified in the
delivery note (hardware, software and documentation).
• the components are not damaged in any way.

3.2 Hardware recommendations

The table below gives a rough overview of the hardware recommendations for installing
TNMS Core; running TNMS Core may require different specifications depending on
parameters such as network architecture (number of Clients, NetServers) or operation
policies (backup, logs). The final hardware specifications and configuration must be
planned specifically for each customer. Ask Nokia Siemens Networks Technical Sales
for more information.

Server Server NetServer Client Client over Citrix

(medium configu- (large configura-
ration) tion)
Fujitsu machines
CPU: Xeon E5620 CPU: (2 x) Xeon CPU: Intel® Core™ CPU: Intel® G6950 CPU: (2 x) Xeon
4C/8T 2.40 GHz, 12 E5620 4C/8T 2.40 i3-2100 2C/4T 3.10 2C 2.80 GHz 3 MB E5620 4C/8T 2.40
MB GHz, 12 MB GHz, 3 MB GHz, 12 MB
Multiprocessor oper- Multiprocessor oper- Multiprocessor oper-
ation supported ation supported ation supported
RAM: 4 GB RAM: 12 GB RAM: 4 GB RAM: 4 GB RAM: 32GB
minimum
Hard Disk: (2 x) 500 Hard Disk: (2 x) 146 Hard Disk: 250 GB Hard Disk: HD SATA Hard Disk: (2 x) 146
GB HD SATA 3G GB HD SAS 6G 10K HD SATA 3G 7.2K 3G 160GB 7.2K GB HD SAS 6G 10K
7.2K
HP machines
CPU: Intel® Xeon® CPU: (2 x) Intel® CPU: Intel® Xeon® CPU: Intel® Xeon® CPU: Intel® Xeon®
E5649 (6 core, 2.53 Xeon® X5675 E5606 (4 core, 2.13 E5606 (4 core, 2.13 E5606 (4 core, 2.13
GHz, 12MB L3, (3.06GHz/6- GHz, 8MB, 80W) GHz, 8MB, 80W) GHz, 8MB, 80W)
80W) core/12MB/95W
(perf))
RAM: 8GB (2 x 4GB) RAM: 24GB (6 x RAM: 4GB (2 x 2GB) RAM: 4GB (2 x 2GB) RAM: 4GB (2 x 2GB)
4GB)

Table 2 Hardware and Operating System recommendations for Server, NetServer and Client

16 A50023-K1027-X040-02-76D1
Issue: 2 Issue date: July 2013
Installation Manual (IMN) Preparation for commissioning

Server Server NetServer Client Client over Citrix

(medium configu- (large configura-
ration) tion)
Hard Disk: (2 x) HP Hard Disk: (2 x) HP Hard Disk: HP Hard Disk: HP Hard Disk: HP
146GB 6G SAS 15K 146GB 6G SAS 15K 146GB 6G SAS 15K 146GB 6G SAS 15K 146GB 6G SAS 15K
2.5in DP ENT HDD 2.5in DP ENT HDD 2.5in DP ENT HDD 2.5in DP ENT HDD 2.5in DP ENT HDD

General features
DVD-ROM drive DVD-ROM drive DVD-ROM drive DVD-ROM drive DVD-ROM drive
Ethernet card Ethernet card Ethernet card, 2x Ethernet card Ethernet card
RAID controller RAID controller - - RAID controller
DAT streamer for DAT streamer for - -
backup backup
- - - PCI I/O, optional
Color monitor 19” Color monitor 19” Color monitor 19” Color monitor 21” Color monitor 21”
Operating system: Operating system: Operating system: Operating system: Operating system:
Microsoft Windows Microsoft Windows • Microsoft • Microsoft Microsoft Windows
Server 2008 R2 SP1 Server 2008 R2 SP1 Windows Server Windows 7 Pro- Server 2008 R2 SP1
(x64) Standard or (x64) Standard or 2008 R2 SP1 fessional or (x64) Standard or
Enterprise Enterprise (x64) Standard Ultimate SP1 Enterprise
or Enterprise (x86)
(Recom- (Recom-
mended) mended)
• Microsoft • Microsoft
Windows Server Windows Server
2003 R2 SP2 as 2008 R2 SP1
guest for (x64) Standard
Windows Server or Enterprise
2008 R2
Netserver can also
be installed in PC
units. In this case,
the supported oper-
ating systems are
Microsoft Windows 7
Professional or
Ultimate SP1 (x86).

Table 2 Hardware and Operating System recommendations for Server, NetServer and Client (Cont.)

g Hyper-threading is not supported for NetServer and is recommended to be switched off

for Client and Server.

A50023-K1027-X040-02-76D1 17
Issue: 2 Issue date: July 2013
Preparation for commissioning Installation Manual (IMN)

3.2.1 Virtualization
TNMS Core supports virtualization using VMware ESXi 4.1. However Nokia Siemens
Networks does not provide neither is responsible for stability limits or performance in
these circumstances.
The requisites of the virtual machines are similar to those presented in Table 2 except
for the CPU that only requires comparable CPU resources.

3.2.2 Installation and cabling

Before installing the operating system, the following steps should be completed:
• The Client, NetServer and Server PCs should be set up and cabled in accordance
with the project-specific installation documents supplied.
• The applicable recommendations for screen-based workstations should be
observed.
• To guarantee 24-hour operation, an uninterrupted power supply must be available.

3.2.3 Mirror disks

The TNMS Core Server PC is provided with a RAID system and two additional mirror
disks which are monitored by a SCSI RAID controller. The SCSI RAID controller ensures
automatic data synchronization between the active hard disk and the mirror disks, so if
the active hard disks develops a fault, a mirror disk takes over and the system is not
affected. The faulty disk can be replaced by a new disk of the same type without shutting
down the Server. The RAID controller then copies the data from the active hard disk to
the newly installed hard disk.

3.2.4 Standby Server and standby NetServer

TNMS Core allows you to configure a warm standby server in the system deployment.
The warm standby server is a second server machine with exactly the same hardware
and software configuration as the active server. The operator registers the warm
standby server at the active TNMS Core Server and activates the database replication
mechanism of TNMS Core. Should a failure occur, the operator simply switches
manually to the warm standby server and starts the TNMS Core Server process on the
warm standby system. See 4.7 Standby Server for a description on how to install and
configure a Standby Server.
A cold standby TNMS Core NetServer is also supported. The standby NetServer is a
machine with exactly the same hardware and software configuration as an active
NetServer. The standby NetServer is deemed cold since there is no database replica-
tion. Follow the instructions in 4.5 NetServer for a description on how to install a
NetServer.
The instructions on how to switch to a standby system can be found in the TNMS Core
System Administration online help.

3.3 Required software

All software parts mentioned in section 3.3.1 must be released for the appropriate TNMS
software version. This holds for the initial installation and for service or upgrade package
installations as well.

18 A50023-K1027-X040-02-76D1
Issue: 2 Issue date: July 2013
Installation Manual (IMN) Preparation for commissioning

g If additional software, not required by TNMS Core, is installed, the correct functionality
of TNMS Core cannot be guaranteed.

3.3.1 Installation software

The following software is generally required for the installation. The corresponding DVD
order numbers are provided in the TNMS Core release documentation.
More information on the installation sequence is provided in section 3.4.
1. ServerView:
If you are using the Fujitsu Siemens PRIMERGY server system, the ServerView
DVD provides the necessary utility programs and drivers for configuring and install-
ing the server machine.
2. Microsoft Windows 7 Professional SP1 or Microsoft Windows Server 2008 R2
SP1 (x64):
Citrix XenApp 6.0 is the version supported by TNMS Core installation over Microsoft
Windows Server 2008 R2 SP1 (x64).
Further installation instructions for operating systems are provided in chapters
4.2 Microsoft Windows Server 2008 R2 SP1, and 4.3 Microsoft Windows 7 Profes-
sional SP1; however, pre-installed machines can also be used.

g Any mentions in this manual to Windows 7 or Windows Server 2008 always

refer to the specific versions above. The use of these abbreviated names is
meant to improve the text’s readability.

3. Internet Explorer 8.0:

This must be installed on the NetServer and on the Client machine. If this is not
already pre-installed, it can be downloaded from the Internet.
4. TNMS Core:
This DVD contains the following software components for installation:
• Integrated TNMS Core software installation package:
This installation program includes the Server, NetServer, Backup Server, and
Client components. These can be installed either individually or together as
required.
The EML packages for QB3M, ELI, EMOS, Generic SNMP, PDH and UNO are
also available for selection, if registered, during the TNMS Core installation. The
EML packages are installed on the Server, NetServer and Client PC.
More information on installing TNMS Core is provided in chapter 4.

The following 3rd-party software components are included on this DVD:

• Adobe Reader:
The customer documentation for TNMS Core is provided in PDF format. The
Adobe Reader should be installed on the Server and Client machines so that the
documentation files can be opened.
• Java Runtime Environment (JRE):
More information on installing JRE is provided in section 4.4.5.
• Microsoft .NET:
This installation is required to run applications developed specifically for .NET
Framework.
• Microsoft XML parser and SDK:
The XML parser and SDK is installed on the client machine so that the TNMS

A50023-K1027-X040-02-76D1 19
Issue: 2 Issue date: July 2013
Preparation for commissioning Installation Manual (IMN)

Core system can support the export and import of network configuration data in
XML format. More information on installing the XML parser and SDK is provided
in section 4.8.2.
• OSI stack 2.1.2.6:
If QB3 is to be used, OSI stack software must be installed on NetServer PCs
before the NetServer software itself. More information on installing the OSI stack
is provided in section 4.5.1.
• Microsoft SQL Server 2005 SP4 Express Edition for small- or medium-sized
TNMS Core configuration and Standard Edition for large configuration.
The installation is described in section 4.4.3. Contact Nokia Siemens Networks
Technical Sales for further information.
5. Waveline:
Waveline is an optional EML package, installed on the Server, NetServer and Client
machine if Waveline network elements are to be installed. More information on
installing Waveline is provided in section 4.4.10.
6. PLET:
PLET is an optional tool, installed on the TNMS Core Server, used for exporting per-
formance management information. More information is provided in section 4.4.7.
7. TCOM:
TCOM is an optional EML package, installed on the TNMS Core NetServer, used for
connecting OEM network elements.
More information is provided in chapter 4.4.9.
8. TCOA proxy:
The TCOA proxy is an optional component to install on the Server and System
Administration components. It is used to connect TNMS Core with an umbrella man-
agement system. The TCOA proxy installation can be selected during the TNMS
Core installation.
More information on installing the TCOA proxy is provided in section 4.4.8.
9. 3rd-party software for TCOA proxy:
If the TCOA proxy is to be installed, the following software products are also
required:
• Java Runtime Environment 1.5.0_06 (32 bits)
• Java Runtime Environment 1.6.0_35 (32 bits)
• TCOA_DS
• TAO 1.4.1 (installed with TCOA_DS)
• Corba Notification Service 4.2 (containing JacORB and also installed with
TCOA_DS)
More information on installing the 3rd-party software is provided in section 4.4.8.
10. SNMP proxy:
The SNMP proxy is an optional component which is installed on the Server and
System Administration components. It is used to connect TNMS Core with an
umbrella management system. The SNMP proxy installation can be selected during
the TNMS Core installation.
11. Hummingbird Exceed:
This is used with TNMS Client for the integration of the TNMS SX and EMOS man-
agement systems. This software is not provided with TNMS.

g DirectX9c has to be installed on Server, Netserver and Client.

20 A50023-K1027-X040-02-76D1
Issue: 2 Issue date: July 2013
Installation Manual (IMN) Preparation for commissioning

Software DVD overview

The software is delivered on DVD-ROMs. Type and content of the necessary CDs
depends on the specific planned and delivered configuration. The operating system,
delivered together with the hardware, is not included.
The deliverable DVD-ROMs are listed below:
• Exceed 2006
• ULAF+ Library
• TNMS Core 14.0 10 - SW for SNMP Interface
• TNMS Core 14.0 10 - SW for Waveline Equipment
• TNMS Core 14.0 10 - Application Software
• TNMS Core 14.0 10 - TMF CORBA Manager Configuration Files
• TNMS Core 14.0 10 - OEM Software for TMF CORBA Manager
• TNMS Core 14.0 10 - TMF CORBA Manager
• TNMS Core 14.0 10 - TMF CORBA Agent
• TNMS Core 14.0 10 - OEM Software for TMF CORBA Agent
• OEM Software Internet Browser

UNEC
The Universal Network Element Control - UNEC, is a code based customization tool
available from NSN. This tool is used to create customized NECs that allows other NES
to be managed by TNMS Core (by other NEs, it is meant NEs out of the officially
released list).
UNEC code base is available on request, please contact NSN customer team for addi-
tional information.

3.3.2 HW/SW configuration

Figure 2 shows a typical configuration of a TNMS Core system. Limitations are given
below. If other configurations are needed, such as standby server, contact Nokia
Siemens Networks Technical Sales for further information.

A50023-K1027-X040-02-76D1 21
Issue: 2 Issue date: July 2013
Preparation for commissioning Installation Manual (IMN)

Figure 2 A typical HW/SW configuration

Limitations and recommendations for HW/SW configuration

• The maximum number of PCs is given in Figure 2.
• For small systems the NetServer Components may be installed on the Server PC.
• The TNMS Core System Administration components may be installed on the Server
PC (recommended) and on the Client PC(s). However, a maximum of 10 System
Administration are allowed to be run simultaneously.
• The Client components must always be installed on a separate PC, except in small
configurations, where the Client is also installed in the Server machine.
• Run few clients in each Client PC.
• PageFile should have a fixed size and be configured with 1.5 the size of the physical
memory.
• Hyper-threading should be disabled.
• Physical Address Extension (PAE) should be disabled.
• Use TNMS Log tool to restrict the memory for SQL Server (especially in large TNMS
configurations).
• The DCN and the LAN must be stable and problem-free.
• Use the Scaled StartUp feature in DCN Management.
• “ArchivedAlarmLog” should be configured with a maximum of 20000 entries.
• The system performance and stability are enhanced by the usage of partitions with
Raid. The following table gives the minimum partition values.

22 A50023-K1027-X040-02-76D1
Issue: 2 Issue date: July 2013
Installation Manual (IMN) Preparation for commissioning

Server (2 x 250GB or 2 NetServer (1 x 160 GB) Client (1 x 160GB)

Disk x 160GB)) No Raid => Total 160 No Raid => Total 160
Raid 1 *=> Total 160 GB GB GB
C: 100 GB for Microsoft 100 GB for Microsoft 100 GB for Microsoft
Windows, TNMS and Windows, TNMS and Windows, TNMS and
OEM OEM OEM
D: 30 GB for customer data 30 GB for customer data 30 GB for customer data
E: 30 GB for Pagefile 30 GB for Pagefile 30 GB for Pagefile
*RAID 1: Redundant Array of independent disks using “Mirroring”

Table 3 Minimum partitions recommendations for TNMS Server, NetServer and

Client

Further hints are given within the chapters describing the installation details.
The installation sequence is described within section 3.4. It is highly recommended to
follow this instructions otherwise problem may occur during installation.

3.4 Installation sequence

This chapter is intended to guide you in a totally new installation.

g Before installing any software component, have a look at the associated readme file.
Here you can find the latest informations concerning installation.
The displayed screenshots within this manual are examples only and the contents may
differ depending from the actual situation.

The individual stages in the commissioning process must be logged using the forms
supplied for the transfer protocol. The transfer protocol documents the completeness of
the delivery, tests performed and the test results.

Java Runtime Environment

During the software installation, the JRE versions necessary to TNMS Core are Java
Runtime Environment 1.5.0_06 (32 bits) and Java Runtime Environment 1.6.0_35 (32
bits).

g Since more than one component require the JRE installation, it might be asked more
than once, during the installation procedure, if Java should be installed:
Answer YES only the first time the question is asked.
Not following this procedure might corrupt the components installation.

Installation Sequence
The following table describes which software is needed for each TNMS Core compo-
nent. Attend to the fact that the table also shows the order that components should be
installed. Starting in the Operating System. The system should be commissioned as
follows:

A50023-K1027-X040-02-76D1 23
Issue: 2 Issue date: July 2013
Preparation for commissioning Installation Manual (IMN)

Applica- Server NetServer Client System Backup

tions/ Com- Administra- Server
ponent tor
Operating Microsoft Depending on Microsoft Microsoft Microsoft
System Windows the hardware Windows 7 Windows 7 Windows
Server 2008 either Micro- Professional Professional Server 2008
R2 SP1 (x64)/ soft Windows SP1/ SP1/ R2 SP1 (x64)/
Server 2008 Microsoft Microsoft
R2 SP1 (x64) Windows Windows
or Microsoft Server 2008 Server 2008
Windows 7 R2 SP1 (x64) R2 SP1 (x64)/
Professional
SP1
.NET Mandatory Pre-Requi-
MSXML Mandatory Mandatory Mandatory Mandatory sites

SQL Server Mandatory

Citrix Optional Optional
XenApp
Adobe Mandatory Mandatory Mandatory Mandatory Mandatory
Reader
OSI Stack Mandatory
OSI Light Mandatory (in
OSI DCNs
with SNMP
controlled
NE's)
Java JRE Mandatory Mandatory Mandatory
TCOA DS Mandatory if
TCOA proxy is
to be installed
TNMS Core Mandatory. Mandatory. Mandatory. Mandatory. Mandatory.
Install the Install the Install the Install the Install the
Server com- TNMS Core TNMS Core System TNMS Core
ponent NetServer Client compo- Administrator Backup
component nent component Server com-
ponent
CopSSH Mandatory

Table 4 TNMS Core installation components and sequence

24 A50023-K1027-X040-02-76D1
Issue: 2 Issue date: July 2013
Installation Manual (IMN) Preparation for commissioning

Applica- Server NetServer Client System Backup

tions/ Com- Administra- Server
ponent tor
PLET Optional
TCOA Proxy Optional Optional
TCOM Optional Optional Optional Additional
TNMS Core
SNMP Proxy Optional Optional
Software
Waveline Optional (If Optional (If Optional (If
chosen it is chosen it is chosen it is
mandatory to mandatory to mandatory to
install on install on install on
Server, Server, Server,
NetServer and NetServer and NetServer and
Client) Client) Client)
Netviewer Optional (if
Radio NEs are
installed

Table 4 TNMS Core installation components and sequence (Cont.)

1. Set up and cable the PCs, as described in section 3.2.2 above.

2. Install the operating system and additional hardware components, and configure the
system as described in chapters 4.2 Microsoft Windows Server 2008 R2 SP1 and
4.3 Microsoft Windows 7 Professional SP1.
3. Install the anti-virus software as described in 4.11.
4. To enable import and export of XML data, install the XML parser MSXML 4.0 SP2
as described in section 4.4.2.
5. Install Microsoft SQL Server 2005 as described in 4.4.3.
6. Install Citrix XenApp 6.0 as described in section 4.8.3 (optional)
7. If QB3 is to be used, install the OSI stack on the NetServer PCs as described in
section 4.5.1.
8. Install the TNMS Core software components on the corresponding machines as
described in chapter 4:
• TNMS Core Client
• TNMS Core Server
• TNMS Core NetServer
• TNMS Core Backup Server
• TNMS Core EML Packages
• Additional TNMS software, such as PLET or the optional EML packages

g In case of specific EML packages selected during the TNMS Core installation, the
Java Runtime Environment is installed automatically

9. If the TNMS SX and EM-OS element managers are to be integrated, install Hum-
mingbird Exceed.
10. Configure the TNMS Core components and connect network elements as described
in chapter 6.

A50023-K1027-X040-02-76D1 25
Issue: 2 Issue date: July 2013
Preparation for commissioning Installation Manual (IMN)

11. Perform system testing in accordance with the test cases described in the accep-
tance test protocol. For more information, contact Nokia Siemens Networks Techni-
cal Sales.

3.5 Operating system prerequisites

The following table describes the Windows configuration prerequisites

Windows Server NetServer Client System Backup Server

configurations Administration
(prerequisites)
User Account X X X X X
Control
Firewall X X X X X
Firewall ports X X X X X
IIS install X X
FTP Server configu- X
ration
DCOM / Active X X X X X
Directory
Local security X X X X X
settings
Security policy X X X X X
Authentication X X X X X
extensions
WinHlp32 X X
Terminal Services / X X X X X
RDP
PCI I/O cards X

Table 5 Operating System prerequisites

26 A50023-K1027-X040-02-76D1
Issue: 2 Issue date: July 2013
Installation Manual (IMN) Installation

4 Installation
This chapter guides you through the installation of TNMS Core 14.0 10 in a clean
machine.
Although TNMS Core 14.0 10 can be deployed on a machine with already installed oper-
ating system and prerequisites, it is recommended to install TNMS Core 14.0 10 on a
clean machine.

g Note that “Clean Machine” in TNMS Core context is a formatted or new machine
without any kind of information on the hard drives.

The (mandatory) installation sequence for all software parts is described in 3.4. Note
that if that order is not followed TNMS Core might not work properly.
Third-party software is delivered on a separate DVD (for the order number see the
release document).
If after this installation procedure TNMS Core is not correctly installed in your machine,
contact Nokia Siemens Networks’ Technical Support for further assistance.
If you have a previous TNMS Core version installed:
• you must uninstall it before installing TNMS Core 14.0 10. No update (installing over
a previous version) is possible.
• install all MIcrosoft Windows security patches referred in the Release Note.
• check the TNMS Core 14.0 10 Upgrade Manual (UPMN) for guidance on how to
handle your database, so it can be used in TNMS Core 14.0 10.
The UPMN can be ordered with the TNMS Core V14.0 10.

g Throughout this and the following chapters the designation of the several operating
systems is often abbreviated to allow for better readability. Refer to chapter 3 for the
exact versions supported for TNMS Core.

4.1 Before you begin

When installing TNMS Core the following information must be taken into account:
• When you run the installer’s (setup.exe) for installing TNMS Core on Windows 7, be
sure to run it in Windows XP-compatible mode.
Opposite-click setup.exe and click Properties.

• It is advisable that every machine has all the operating systems’ security patches,
rated by Microsoft as “critical” and “important”, installed.

• Windows User Account Control must be disabled in order to continue with the instal-
lation. According to your Windows version, the procedure may vary. Typically, it can
be disabled under Control Panel -> User Accounts -> Change User Account Control
Settings -> Never Notify.

• In order to install TNMS Core you must have Administrator rights. Please note
that in case you install in Windows 7 or Windows Server 2008 R2, although you have
administrator privileges, the setup will run with limited access. For those operating
systems you must enforce the installation to “Run as Administrator” (Figure 3).

A50023-K1027-X040-02-76D1 27
Issue: 2 Issue date: July 2013
Installation Installation Manual (IMN)

Figure 3 How to set the TNMS Core installer to run with administrator rights in
Windows 7 and Windows Server 2008 R2.
• The integrated TNMS Core software installation consists of the components:

Components EML Database Tools

Packages
Server Can be installed in the same Must be SQL Server must be
machine. installed installed and running
NetServer Must be
installed
Backup Can be installed in any PC. However, it must have the same con-
Server figuration as the Server.
Client Recommended to be Must be Microsoft Data Access
installed in a separate PC. installed Components (MDAC)
are required and auto-
matically installed by
the TNMS installer
System Can be installed in any PC -
Administra- with any of the other TNMS
tion Core components.

Table 6 TNMS Core components

• Up to 40 Clients can be managed simultaneously support distributed operation.

• Up to 10 NetServer PCs can be managed simultaneously depending on the number

of the NEs.

• The Server must be installed on the server PC. Depending on the security concept,
the System Administration software can also be installed on the Server PC with an
additional monitor where possible. This enables administration of the TNMS Core
system to continue uninterrupted, even if the data flow between the Client and
Server PC is disrupted.

• If TCOA proxy or TCOM is to be installed, the relevant 3rd-party software must also
be installed on the Server PC.

• If one or more PCs in the TNMS Core system are equipped with two network adapt-
ers, routing settings must be configured as specified in Section 6.3 to avoid delays
during connection setup between PCs.

28 A50023-K1027-X040-02-76D1
Issue: 2 Issue date: July 2013
Installation Manual (IMN) Installation

• Ports:
To see which Ports should be open in the Firewall please see chapter 4.3.4 Firewall
port setup.

• Client network latency:

In case the network latency between the Client and Server is greater than 6ms, you
should install the Citrix Online Plug-in in these Client machines and the Citrix
XenApp Server with the TNMS-Client Application should be located nearby the
TNMS Core Server with minimum latency.
It is recommended that network latency is kept low, for example, under 2ms to
minimize GUI update delays.
Refer to section 4.8.3 Citrix XenApp 6.5 (for Windows Server 2008 R2) for further
details.

4.2 Microsoft Windows Server 2008 R2 SP1

The following chapters guide you through the installation and configuration of Windows
Server 2008 R2 SP1 (x64) (recommended operating system for TNMS Core Server
machines), which is referred to as Windows Server 2008 R2.

4.2.1 BEFORE you begin

Before you install Windows Server 2008 R2, complete the following steps:
• If you wish to pre-install a SCSI RAID system make sure the TNMS Core Server
hard disks are formatted using the NTFS file system.
• Check the system requirements.
• Determine the licensing mode to be used.
• Determine the file system to be used.
• Determine the partition to be used for the installation, or if a new partition is required.
• Determine the components to be installed.
• Determine how the network, IP addresses and TCP/IP name management are to be
handled.
• Determine the domains or workgroups for the servers, if required.
• Save all data and files before an initial installation of the operating systems. This
does not apply if there are no files on the computer or the existing operating system
files are damaged. You can save the files on disk, on tape or on another computer
in your network.
• Decompress all DriveSpace and DoubleSpace data carriers.
• Installation may only be carried out on a compressed drive if this drive was com-
pressed with the compression program of the NTFS file system.
• Disable all UPS devices.
• If the target computer is protected by an uninterrupted (UPS), remove the serial
cable before performing the setup. Windows Server 2008 R2 setup automatically
tries to identify the devices at the serial interfaces. UPSs may cause problems here.

4.2.1.1 Licensing information

The system license number is requested during the installation. Find it on the back cover
of the operating system CDs.

A50023-K1027-X040-02-76D1 29
Issue: 2 Issue date: July 2013
Installation Installation Manual (IMN)

Microsoft provides two licensing modes for Windows:

• Per workplace:
Licensing per workplace requires a separate client access license for each computer
accessing Windows. With a single client access license, a client computer can
establish connections to as many Windows 7 or Windows Server 2008 R2 as
required. This licensing method should be used if you are running several Windows
7 or Windows Server 2008 R2.
• Per server:
Licensing per server requires a client access license for every simultaneous connec-
tion established to this server. This means that the corresponding Windows 7 or
Windows Server 2008 R2 supports a fixed number of client connections. There are
no additional licenses required for these computers. Per server licensing should be
used if you are running a single Windows 7 or Windows Server 2008 R2.
Use per server licensing if you are not sure which mode to use, since it is possible to
switch later at no extra cost from per server to per workplace licensing.
Use per workplace licensing if you want to use Internet Connector license terminal ser-
vices, both for remote administration and for an application server.
More information is provided in section 4.8.3 Citrix XenApp 6.5 (for Windows Server
2008 R2).

4.2.1.2 Protocol information

Microsoft Windows operating systems use TCP/IP as the standard network protocol.
You may wish to use other protocols and the corresponding network adapters.
TCP/IP needs one IP address for every server:
• A dynamic address which is assigned by the software automatically.
or
• A static address, where the address is fixed.
IP addresses although provided in the form of numbers, using name resolution, it can
also be assigned a name to a server IP address. This enables user access via server
names instead of via IP addresses which can be difficult to remember. The following
methods are required for this operation:
• DNS (Domain Naming Service):
DNS is a distributed Internet directory service that is used mostly to translate
between domain names (server hosts) and IP addresses. It facilitates name resolu-
tion for clients under Microsoft Windows operating systems.
• DHCP (Dynamic Host Configuration Protocol):
DHCP allows dynamic assignment of IP addresses to network devices. These
devices are generally servers and workstations, but other devices are also possible,
for example, printers and scanners. DHCP does not require the definition or admin-
istration of static IP addresses, except in the case of Intranet servers which support
DHCP, DNS and/or WINS.
• WINS (Windows Internet Naming Service):
WINS facilitates name resolution for clients running Windows NT and older Microsoft
operating systems.

30 A50023-K1027-X040-02-76D1
Issue: 2 Issue date: July 2013
Installation Manual (IMN) Installation

4.2.2 Installation process

For instructions on how to install the Windows Server 2008, refer to its Microsoft docu-
mentation.
However, if you are using a FSC / Fujitsu Primergy computer as your TNMS Core
Server, Windows Server 2008 R2 must be installed using the Primergy ServerView
Suite DVD. The following description is related to ServerView version 10.11. Contact
Nokia Siemens Networks for the most updated version of the ServerView DVD.

g UniGATE must not be installed on the same computer as the TNMS Core Server and
must not be run parallel in the network.

Microsoft Windows Server 2008 R2 SP1 installation through ServerView

Below a typical installation process using ServerView 10.11 is described. Please refer
to Fujitsu’s ServerView Installation Manager documentation for any additional details on
how to use this software.
1. Insert the ServerView DVD into the DVD-ROM drive.
– reboot the system
– press F12 and select “Boot from CD/DVD”. Press “Enter”.

2. In Windows Boot Manager select “ServerView Installation Manager”

A “Starting Windows” screen is displayed.

3. “Language Selection” window

– select the GUI language by clicking on one of the languages presented.

4. “Installation Manager - StartUp” window

– select the keyboard layout and leave the remaining default settings. Click “Con-
tinue”.

5. “Welcome to ServerView Installation Manager” window

– click on “Deployment”.

6. “Installation Manager Deployment Process Selection” window

– select “Typical” to install using the default values and click “Next”.

7. “Configure your Unattended Operating System Installation” window

– select “Create a new configuration file.”
– select the version, edition and service pack corresponding to Windows Server
2008 R2.
– click “Next”.

8. “Configuration” window
Typical configurations to define or enter:
– Mass storage > Configuration - configuration of disks and RAID controllers.
– MS Windows 2008 R2 > Basic Settings - User Name (should be identical to the
name of the owner of the Windows Server 2008 R2 license), Organization,
Computer Name, Admin Password.

A50023-K1027-X040-02-76D1 31
Issue: 2 Issue date: July 2013
Installation Installation Manual (IMN)

– click “Next”.

9. “Configuration” window - Summary

Check the configurations you have chosen. Click “Back” to go back and change any
configuration or “Start Installation” to begin the unattended installation.

10. If you have selected a local drive as the source device, Installation Manager will
prompt you to insert the DVD. Insert the DVD and click “OK”.

11. “License Agreement” window

Read the EULA's content and if you agree, click “Apply”.

The system will reboot several times during the unattended installation process.

4.2.2.1 Windows Server 2008 R2 terminal services

The Windows Server 2008 R2 Terminal Services installation is performed the same way
as the standard installation. To facilitate installation, the first partition must have at least
3 GB or the hard disk must not be partitioned at all. More information is provided in the
Windows Server 2008 R2 Terminal Services documentation.
To install Windows Server 2008 R2 Terminal Services, proceed as follows:
1. Open Start > Administrative tools > Server Manager > Roles.
2. Click “Add roles” to open the “Add Roles” Wizard and click “Next”.
3. In Select Server Roles, select "Remote Desktop Services” and click “Next”.
4. In Remote Desktop Services, click “Next”.
5. In Select Role Services, select “Remote Desktop Session Host” & “Remote Desktop
Licensing" and click “Next”.
6. In Uninstall and Reinstall Applications for Compatibility, click “Next”.
7. In Specify Authentication Method for Remote Desktop Session Host, select “Require
Network Level Authentication” and click “Next”.
8. In the following screens select the most suitable option for your system and click
“Next”.
9. In Confirmation, select “Install” and “Close”.
10. Reboot your computer.

4.2.3 Post installation configurations

After installing the Operating System some configurations must be done to have a per-
fectly functional TNMS Core. The following chapters guides you through those configu-
rations.

4.2.3.1 User Account Control

Windows User Account Control must be disabled in order to continue with the installa-
tion. It can be disabled under Control Panel -> User Accounts -> Change User Account
Control Settings -> Never Notify.
Restart the machine after performing this change.

32 A50023-K1027-X040-02-76D1
Issue: 2 Issue date: July 2013
Installation Manual (IMN) Installation

4.2.3.2 Firewall configuration

The Windows Server 2008 R2 firewall must be configured as follows:
1. Open the Windows Firewall Settings via Start > Administrative Tools > Windows
Firewall with Advanced Security.
2. "Windows Firewall" window:
• Select "Windows Firewall Properties".
• On the Domain Profile tab, change the Firewall state option to Off (not recom-
mended).
• On the Private Profile tab, change the Firewall state option to Off (not recom-
mended).
• On the Public Profile tab, change the Firewall state option to Off (not recom-
mended).
• Click "OK" to accept the changes.
This disables the Windows Server 2008 R2 Firewall services.

g This should be done only if there is an external firewall in the system. If no external
firewall exists, keep the Windows Firewall on.

w Nokia Siemens Networks does not recommend the deployment of a firewall between
the NetServer and the NE network. This scenario is not tested and therefore is not
officially supported. In case the costumer needs to deploy one due to topology/secu-
rity reasons, the ports listed for NetServer <-> NE communication in this manual are
just an example for the hiT7300 and hiT7100 NEs. Other supported NEs may need
different/additional ports/protocols. Please refer to the specific NE's manual to
gather the required information to configure your firewall.

4.2.3.3 Firewall port setup

Before installing TNMS Core, the following ports must be opened in your firewall
(whether it is Windows’ or an external firewall):

A50023-K1027-X040-02-76D1 33
Issue: 2 Issue date: July 2013
Installation Installation Manual (IMN)

Host address Service Action Responsi-

ble SW
Source Destina- Port Transport Applica- Description
layer
tion layer tion Layer
Firewall between CITRIX clients and CITRIX server (if deployed)
TNMS Core WebGUI 1494 TCP ICA Only when Citrix is Accept CITRIX
user work- user work- used. Server
station station
2598 TCP ICA Optional. For Secure-
(CITRIX ICA. Only when Citrix
Server)
is used.
Any Any Any Drop -
Firewall between TNMS Core clients / CITRIX server (if deployed) and TNMS Core Server
TNMS Core TNMS Core 1494 TCP ICA Only when Citrix is Accept TNMS Core
user work- server used. Server
station
2598 TCP ICA Optional. For Secure- Accept
ICA. Only when Citrix
is used.
135 TCP/UDP MS-RPC Microsoft RPC Accept
137 TCP NBT Microsoft NetBIOS Accept
over TCP/IP name
service
TNMS Core TNMS Core 135 TCP/UDP MS-RPC Microsoft RPC Accept
server user work- 137 TCP NBT Microsoft NetBIOS Accept
station
over TCP/IP name
service
WebGUI TNMS Core 1494 TCP ICA Only when Citrix is Accept
user work- server used.
station
2598 TCP ICA Optional. For Secure- Accept
(CITRIX
ICA. Only when Citrix
Server)
is used.

Any Any Any Drop -

Firewall between TNMS Core server and TNMS Core netserver
TNMS Core TNMS Core dyna TCP/UDP DCOM Ports are dynamic, Accept TNMS Core
server netserver mic / but restricted port Netserver
con- ranges can be ucon-
figure figured.
d
Any Any Any Drop -

Table 7 Firewall rules

34 A50023-K1027-X040-02-76D1
Issue: 2 Issue date: July 2013
Installation Manual (IMN) Installation

Host address Service Action Responsi-

ble SW
Source Destina- Port Transport Applica- Description
layer
tion layer tion Layer
Firewall between TNMS Core server and Customer Network
Admin TNMS Core 22 TCP SSH SecureShell connec- Accept TNMS Core
Console server tions for server server
administration.
TNMS Core DNS server 53 TCP DNS DNS server Accept
server NTP server 123 TCP NTP NTP server Accept
Any Any Any Drop -
Traffic between TNMS Core and NE Network (firewall not recommended)
Example for hiT7300 / hiT7100
TNMS Core NE/GNE 1000 TCP SNMP SNMP multiplexing Accept TNMS Core
netserver manage- - ports (NAPT) for NetServer
ment inter- 13999 embedded CT; target
face NE
161 TCP SNMP SNMP managers Accept
NE/GNE TNMS Core 22 TCP SSH / SCP Secure Copy (secure Accept
manage- netserver copy over SSH)
ment inter-
face
Any Any Any Drop -

Table 7 Firewall rules (Cont.)

A50023-K1027-X040-02-76D1 35
Issue: 2 Issue date: July 2013
Installation Installation Manual (IMN)

4.2.3.4 FTP server

To install the FTP server proceed as follows:
1. Open Start > Administrative tools > Server Manager > Roles.
2. Click “Add Roles” to open the “Add Roles” Wizard and click “Next”.
3. In Server Roles, select "Web Server (IIS)” and click “Next”.
4. In Web Server (IIS) click “Next”.
5. In Role Services, select the top end following services from the tree:
• Web Server
• Common HTTP Features
• Static Content
• Default Document
• Directory Browsing
• HTTP Errors
• Health and Diagnostics
• HTTP Logging
• Request Monitor
• Security
• Request Filtering
• Performance
• Static Content Compression
• Management Tools
• IIS Management Console
• IIS Management Scripts and Tools
• Management Service
• FTP Server
• FTP Service
• FTP Extensibility
6. Click “Next”.
7. In Confirmation, click “Install”.
8. In Results, select “Close”.
9. Reboot your computer.
To configure the FTP server:
1. Start > Administrative Tools > Internet Information Services (IIS) Manager.
2. In the left pane tree, expand the Default Computer > Sites.
3. In the right pane tree, select “Add FTP Site”. This opens the Add FTP Site window.
4. Enter the FTP site name.
5. In Physical Path, change the folder to “C:\inetpub\ftproot”, click OK and Next.
6. In “Binding and SSL Settings” step, configure the IP Address or leave as default.
7. In SSL, select “Allow SSL”. Click Next.
8. In “Authentication and Authorization Information” step, select “Authentication as
Basic”.
9. In Authorization - Allow access to “All users”, permissions “Read” and “Write”.
10. Click Finish.

36 A50023-K1027-X040-02-76D1
Issue: 2 Issue date: July 2013
Installation Manual (IMN) Installation

4.2.3.5 Component Services configuration

The Windows component services must be configured in one of three different ways.
The following chapter provides you guidance on the default configuration. Two other
configurations are described under 4.14.1 Active Directory configurations in Windows
Server 2008 R2. Although Active Directory based COM security is recommended, select
the configuration that best suites your needs.

COM security using default configuration

If you do not want to adopt neither Active Directory Based COM security nor Active
Directory Based COM security with Windows domain authentication, use the following
COM security in your Windows Operating System:
1. Open the Component Services settings via Start menu/button > Control Panel >
Administrative tools > Component Services icon.

2. "Components" window:
• Go to the tree pane and select "Computers".
• In the “Computers” pane, right click and select "Properties".

Figure 4 "Component Services" window

A50023-K1027-X040-02-76D1 37
Issue: 2 Issue date: July 2013
Installation Installation Manual (IMN)

3. "My Computer Properties" window:

"Com Security" tab
• In "Access Permissions" group, select "Edit Limits...".

Figure 5 "My Computer Properties" window from "Component Services" window

4. "Access Permission" window:
• Select "ANONYMOUS LOGON".
• Select "Allow" in the Remote Access

Figure 6 "Access Permission" window from "Component Services" window

• Continue with "OK".

38 A50023-K1027-X040-02-76D1
Issue: 2 Issue date: July 2013
Installation Manual (IMN) Installation

5. Enter the user name and password for the domain and click OK to continue.

Figure 7 “Windows Security - Enter Network Password” window

6. "My Computer Properties" window:
"Com Security" tab
• In "Launch and Activation Permissions" group, select "Edit Limits...".

Figure 8 "My Computer Properties" window from "Component Services" window

A50023-K1027-X040-02-76D1 39
Issue: 2 Issue date: July 2013
Installation Installation Manual (IMN)

7. "Launch Permission" window:

• Select "Add" to create the Anonymous Logon user.

Figure 9 In "Launch Permission" window, select "Add"

This opens the "Select Users and Groups" window.
8. "Select Users or Groups" window
• Type the user "ANONYMOUS LOGON" in the available text box.

Figure 10 "Select Users or Groups" window

• Continue with "OK".

40 A50023-K1027-X040-02-76D1
Issue: 2 Issue date: July 2013
Installation Manual (IMN) Installation

9. "Launch Permission" window:

• Allow all permissions by selecting "Allow" in all check boxes.

Figure 11 "Launch Permission" window

• Finish with "OK" in all opened windows.

4.2.3.6 Local security settings / local policies

Audit Policy and Security Options are configured in the Local Security Settings window.

Audit policy
To enable auditing locally in the installed OS:
1. Open the Local Security Policy settings via Start menu/button > Control Panel >
Administrative tools > Local Security Policy icon.
2. In the tree pane, select "Audit Policy".

A50023-K1027-X040-02-76D1 41
Issue: 2 Issue date: July 2013
Installation Installation Manual (IMN)

Figure 12 "Local Security Settings - Audit Policy" window

3. In the details pane double-click the following policy settings to open the properties
window:
• Audit Account Logon Events, to track user’s logon and logoff - select the
check boxes ‘Success’ and ‘Failure’.
• Audit Account Management, to report changes to user account - select the
check boxes ‘Success’ and ‘Failure’.
• Audit Directory Service Access, to report access and changes to the directory
service - No auditing (no check box selected).
• Audit Logon Events, to report success/failure of any local or remote access-
based logon - select the check boxes ‘Success’ and ‘Failure’.
• Audit Object Access, to report file and folder access - select the check boxes
‘Success’ and ‘Failure’.

g The auditing configuration for the individual object (file or folder) must be set
within its properties.

• Audit Policy Change, to report group policies changes - select the check boxes
‘Success’ and ‘Failure’.
• Audit Privilege Use, to report when permissions (read, write...) are used -
select only the check box ‘Failure’.
• Audit Process Tracking, to report when process and programs fail (not security
related) - No auditing (no check box selected).
• Audit System Events, to report standard system events (not security related) -
select the check boxes ‘Success’ and ‘Failure’.

Security policy
For “TNMS Active Directory based COM security”, the security policy “Network Access:
Let Everyone permissions apply anonymous users”, should be set to disabled.
For “Com security with default configuration”, the security policy “Network Access: Let
Everyone permissions apply anonymous users”, should be set to enabled as per the fol-
lowing description.
1. Open the Local Security Policy settings via Start menu/button > Control Panel >
Administrative tools > Local Security Policy icon.
2. "local Security Settings" window:

42 A50023-K1027-X040-02-76D1
Issue: 2 Issue date: July 2013
Installation Manual (IMN) Installation

• In the tree pane, select "Security Options".

• In the Policy pane, right click in "Network Access: Let Everyone permissions
apply anonymous users" and select "Properties".

Figure 13 "Local Security Settings - Security Options" window

3. "Network access: Let everyone..." window:
• With TNMS COM security using default configuration, select "Enable".
With TNMS Active Directory based COM security, select “Disable”.

Figure 14 “Network access: Let everyone...” window

• Continue with "OK".
• Close the "Local Security Settings" window
• Restart the computer.

A50023-K1027-X040-02-76D1 43
Issue: 2 Issue date: July 2013
Installation Installation Manual (IMN)

4.2.4 The file WinHlp32.exe

Windows Server 2008 R2 does not include WinHlp32.exe, a prerequisite for TNMS
Core's online help system to work. While Microsoft no longer authorizes developers to
distribute the file, it makes it publicly available at the Microsoft Download Center under
http://support.microsoft.com/kb/917607. The file must therefore be downloaded and
installed. Installation may occur either before (preferably) or after (optionally) installing
TNMS Core itself, which runs correctly in any case.

4.3 Microsoft Windows 7 Professional SP1

The following chapters guide you through the installation and configuration of Windows
7 Professional SP1 (recommended operating system for TNMS Core Client machines),
which is referred to as Windows 7, is installed using the Windows 7 DVD.
During installation, the system license number is requested which is provided on the
back cover of the DVD case.
Before installing Windows 7 please note that:
• The Aero user interface mode is not supported, see section Post installation config-
urations.
• UDP port 55555 should be free to make TNMS taskbar icons visible.
Proceed the installation as follows:
1. Insert the Windows 7 Professional DVD into the DVD-ROM drive.

2. Reboot the PC from the DVD.

A black screen informs you that the Windows 7 files are being loaded.

3. "Language" window:
• Select the ”Language to install” from the drop down menu.
• Select “Time and currency format” from the drop down menu.
• Select the “keyboard or input method” from the drop down menu.
• Review your choices and press “Next”.

4. “Install Now” window:

Click on “Install Now”.
5. "Licensing Agreement" window:
• Check the ”I accept the license agreement” checkbox.
• Press "Next" to agree.
6. “Type of installation” window:
Choose "Custom (advanced)", that is, new installation.
7. “Where to install” window:
• Choose the partition were you want to install the OS. By Clicking in “Drive
options (advanced)” you have available some disk management options.
• Click “Next”.

8. “Installing Windows" window:

• This window shows you the progress of the installation. No action required from
user.
• Some black windows can appear during the installation process.

44 A50023-K1027-X040-02-76D1
Issue: 2 Issue date: July 2013
Installation Manual (IMN) Installation

g If one or more black screens stating “Press any Key to boot from CD or DVD”
appear, ignore it and wait until “Starting Windows” with a Windows logo appears.

9. In the “Windows 7” window provide a Username (for example, Administrator) and a

Computer Name. Then click “Next”.

10. "In the “Set a password for your user account” window:
• Enter a password.
• Retype your password.
• Type a password hint.
• Continue with "Next".

11. "“Type your Product Key for activation" window:

• Enter the product ID from the back cover of the DVD.
• Continue with "Next".

12. "Review your Time and Date Settings" window:

• Change the date, time and time zone, if required.
• Specify whether changing from summer time to winter time automatically.
• Continue with "Next".

13. "Select your computer’s current location" window:

• Select the type of network that suites you best.
• A new window appears. Choose what suites you best.

14. "Do you want to create a homegroup?” window:

• If you chose this option, choose what suites you best.
• Continue with "Next".

15. "Windows is finalizing your settings" window:

A message window informs you about the final installation operations.

16. "Welcome " window:

A welcome message is displayed. Then a message stating “Preparing your desktop”
appears. After this Windows 7 is installed.

4.3.1 Hardware configuration under Windows 7

Once Windows 7 has been installed, all additional hardware and software components
must be configured/installed under Windows 7.
This includes:
• Graphics cards: Set the font size to "Small Fonts": Start > Control Panel: Double
click on "Display", the "Display Properties Window" opens; press button "Advanced"
choose tab "Common" and set the value "Display/Font Size" to "Small Fonts".
Restart the computer if necessary.
• Printers
• Modems (remote login)

A50023-K1027-X040-02-76D1 45
Issue: 2 Issue date: July 2013
Installation Installation Manual (IMN)

• UPS
Installation should be completed in accordance with the relevant installation instructions.

4.3.1.1 Installing the PCI I/O Card

The PCI I/O card is installed on the TNMS Core Client PC and enables external signal-
ing.

g Before opening the antistatic envelope, make sure you are familiar with the regulations
for electrostatic-sensitive devices (ESD) provided in chapter 2.

• Switch off the PC and disconnect it from the power supply.

• Open the PC.
• Insert the PCI I/O card into a free slot.
• Close the PC.
• Switch on the PC.
• Install suitable drivers by double-clicking the Setup.exe file on the floppy disk sup-
plied.
• Start the TNMS Core Client after installing the drivers.
More information is provided in the I/O card documentation.

4.3.2 User Account Control

Windows User Account Control must be disabled in order to continue with the installa-
tion. It can be disabled under Control Panel -> User Accounts -> Change User Account
Control Settings -> Never Notify.
Restart the machine after performing this change.

4.3.3 Firewall configuration

If you have an external firewall in the system, the Windows 7 firewall must be turned
off. To turn the Windows firewall off proceed as follows:
1. Open Windows 7 firewall settings via Start menu > Control Panel > System and
Security > Windows Firewall > Customize Settings.
2. Click “Turn Windows Firewall on or off” in the left pane.
3. Click “Turn off Windows Firewall” under all network locations.
4. Click OK.
This disables the Windows 7 Firewall services.
5. A pop up balloon appears in the Windows desktop notification area, stating that the
Windows Firewall is off. Do not click this balloon as it would turn it on again.
Instead install and configure your external firewall and Windows 7 automatically rec-
ognizes the system is protected.

4.3.4 Firewall port setup

Before installing TNMS Core, the ports listed in Firewall port setup must be opened in
your firewall (whether it is Windows’ or an external firewall).

46 A50023-K1027-X040-02-76D1
Issue: 2 Issue date: July 2013
Installation Manual (IMN) Installation

4.3.5 Post installation configurations

After installing the operating system, the graphical user interface must be defined for
best performance. Proceed as follows:
1. Go to Start > Control Panel > System and select “Advanced system settings”
2. Choose the "Advanced" tab.
3. In “Performance” click “Settings”.
4. In the "Visual effects" tab, choose "Adjust for best performance".
5. Click “OK”.
You must also set the Windows theme to “Classic”:
Go to Start > Control Panel > Personalization and select “Windows Classic”.

4.3.5.1 Component Services configuration

The following chapter provides you guidance on the default configuration for the
Windows component services.

COM security using default configuration

If you do not want to adopt neither Active Directory Based COM security nor Active
Directory Based COM security with Windows domain authentication, use the following
COM security in your Windows Operating System:
1. Open the Component Services settings via Start menu/button > Control Panel >
Administrative tools > Component Services icon.

2. "Components" window:
• Go to the tree pane and select "Computers".
• In the “Computers” pane, right click and select "Properties".

Figure 15 "Component Services" window

A50023-K1027-X040-02-76D1 47
Issue: 2 Issue date: July 2013
Installation Installation Manual (IMN)

3. "My Computer Properties" window:

"Com Security" tab
• In "Access Permissions" group, select "Edit Limits...".

Figure 16 "My Computer Properties" window from "Component Services" window

4. "Access Permission" window:
• Select "ANONYMOUS LOGON".
• Select "Allow" in the Remote Access

Figure 17 "Access Permission" window from "Component Services" window

• Continue with "OK".

48 A50023-K1027-X040-02-76D1
Issue: 2 Issue date: July 2013
Installation Manual (IMN) Installation

5. Enter the user name and password for the domain and click OK to continue.

Figure 18 “Windows Security - Enter Network Password” window

6. "My Computer Properties" window:
"Com Security" tab
• In "Launch and Activation Permissions" group, select "Edit Limits...".

Figure 19 "My Computer Properties" window from "Component Services" window

A50023-K1027-X040-02-76D1 49
Issue: 2 Issue date: July 2013
Installation Installation Manual (IMN)

7. "Launch Permission" window:

• Select "Add" to create the Anonymous Logon user.

Figure 20 In "Launch Permission" window, select "Add"

This opens the "Select Users and Groups" window.
8. "Select Users or Groups" window
• Type the user "ANONYMOUS LOGON" in the available text box.

Figure 21 "Select Users or Groups" window

• Continue with "OK".

50 A50023-K1027-X040-02-76D1
Issue: 2 Issue date: July 2013
Installation Manual (IMN) Installation

9. "Launch Permission" window:

• Allow all permissions by selecting "Allow" in all check boxes.

Figure 22 "Launch Permission" window

• Finish with "OK" in all opened windows.

4.3.6 The file WinHlp32.exe

Windows 7 does include WinHlp32.exe, a prerequisite for TNMS Core's online help
system to work. While Microsoft no longer authorizes developers to distribute the file, it
makes it publicly available at the Microsoft Download Center under http://support.micro-
soft.com/kb/917607. The file must therefore be downloaded and installed. Installation
may occur either before (preferably) or after (optionally) installing TNMS Core itself,
which runs correctly in any case.

4.3.7 FTP configuration

To configure the FTP in Windows 7 proceed as follow:
1. Open Start > Control Panel > Programs and features > Turn Windows features
on or off.
2. Select the top end following services from the tree:
• Internet information Services
• FTP Server
• FTP Service
• FTP Extensibility

A50023-K1027-X040-02-76D1 51
Issue: 2 Issue date: July 2013
Installation Installation Manual (IMN)

• Web Management Tools

• IIS 6 Management Compatibility
• IIS 6 Management Console
• IIS Management Scripts and Tools
• Management Service
3. Click “OK” and confirm.
4. After the installation go to Control Panel > Administrative Tools > Internet Informa-
tion Services (IIS) Manager.
5. In the default PC go to the FTP area and click on FTP Authentication. Then in the
window right click in both Anonymous and Basic Authentication and click Enable on
both cases.
6. Still in the default PC go to the FTP area and click on FTP SSL Settings. Then in the
window enable the Allow SSL connections.
7. In the right pane tree, select "Add FTP Site". This opens the Add FTP Site window.
8. Enter the FTP site name, default.
9. In Physical Path, change the folder to "C:\inetpub\ftproot", click OK and Next.
10. In "Binding and SSL Settings" step, configure the IP Address or leave as default.
11. In SSL, select "Allow SSL". Click Next.
12. In “Authentication and Authorization Information” step, select “Authentication as
Basic”.
13. In Authorization - Allow access to "All users", permissions "Read" and "Write".
14. Click Finish.
15. Then expand the tree in the left pane until default FTP. In the default FTP Home area
click on FTP Authentication. Then in the window right click in both Anonymous and
Basic Authentication and click Enable on both cases.
16. Click on default FTP to go back to the default FTP Home panel. There click on FTP
Authorization Rules. In the window, right click on the existing option and then choose
Edit.... Then select All Anonymous Users and click OK.
17. Go back to the default FTP Home panel and click FTP SLL Settings. In the window
enable the Allow SSL connections.
18. Close the Internet Information Services (IIS) Manager and the FTP is now config-
ured.

4.4 Server
In this chapter you will find detailed step to step information on how to install TNMS Core
Server in a clean machine. The next chapters will give you, in order of installation, the
instructions to install all needed components.

4.4.1 .NET 3.5 / .NET 2.0

.NET 3.5 is installed with Windows Server 2008 R2, but requires activation. To activate
.NET 3.5, proceed as follows:
1. Go to Administrative Tools > Server Manager > Features.
2. Click Add Features.
3. Select .NET Framework 3.5.1 features.

52 A50023-K1027-X040-02-76D1
Issue: 2 Issue date: July 2013
Installation Manual (IMN) Installation

4.4.2 MSXML 4.0 SP2

MSXML 4.0 is an XML parser. It must be installed on the system so that network config-
uration data can be imported and exported in XML format.
To install MSXML 4.0 SP2 on all operating systems, proceed as follows:
1. Reboot the PC (if not already done, see above).

2. Double-click the msxml4sp2.msi file in the MSXML directory on the TNMS Core
software DVD.

3. A welcome window is now displayed. Press Next to continue.

4. In the "End-User License Agreement” window, accept the terms of the license
agreement, and press Next to continue.

5. In the "Customer Information” window, enter a user name and the name of your
company in the appropriate fields. Press Next to continue.

6. In the ”Choose Setup Type” window, press Install Now.

7. The window "Installing Microsoft XML Parser and SDK” window is now displayed.
The progress of the installation is indicated by the progress bar.

8. Once the installation is complete, the window "Completing the Microsoft XML Parser
and SDK Setup Wizard” is displayed. Press Finish to complete the installation.

In case the security update 832894 is applied to Internet Explorer, run the
KB832414_MSXML4.0_x86.exe file in the MSXML directory on the TNMS Core soft-
ware.

Uninstalling MSXML
To uninstall the MSXML, open Start > Control Panel > Add/Remove Programs:
• Select the MSXML from the software list.
• Click the Change/Remove button.
• Select the Remove option.
• Confirm the uninstall process with Finish and restart your computer.

4.4.3 MS SQL Server 2005

To install MS SQL Server 2005, proceed as follows:

4.4.3.1 Prerequisites
For Windows Server 2008 R2:
• MSI 3.1; (MSI 3.1 is part of Windows Server 2008 R2 installation package)
• MS .NET 3.5 (.NET 3.5 is part of Windows Server 2008 R2 installation package, but
requires activation - see 4.4.1)
• Web Server (IIS) support (see Web Server (IIS) support).

A50023-K1027-X040-02-76D1 53
Issue: 2 Issue date: July 2013
Installation Installation Manual (IMN)

Web Server (IIS) support

The following description details the installation of “Web Server (IIS) support” on
Windows Server 2008 R2. Proceed as follows:
1. Go to Start > Control Panel > Administrative tools > Server Manager.
2. On the left pane right click "Roles" and choose "Add Roles".
3. Click “Next” on the "Before You Begin" windows.
4. On the "Select Server Roles" window choose "Application Server" and "Web Server
(IIS)". Click the "Add Required Features" button in the pop-up window. Then click
"Next".
5. Click "Next" in the "Application Server" window.
6. Select "Web Server (IIS) Support" in the "Select Role Services" window and click the
"Add Required Role Services" button in the pop-up window. Then click "Next".
7. Click "Next" in the "Web Server (IIS)" window.
8. Select “IIS6 Scripting Tools” in the "Select Role Services" window.
9. Click “Add Required Role Services”.
10. Click “Next” in the "Select Role Services" window.
11. Click "Install" in the "Confirmation" window and "Close" in the "Installation Results"
window.
After the IIS installation, the following configurations are required:
1. Go to Start > Control Panel > Administrative tools > Internet Information Services
(IIS) Manager.
2. In the “Connections” pane, on the left side, expand the server name and click in
“Application Pools”.
3. In the “Actions” pane, on the right side, click “Set Application Pool Defaults...”.
4. In the “General” section, set the “Enable 32-Bit Applications” option to “True” and
click “OK”.

4.4.3.2 Standard Edition

MS SQL Server 2005 must be installed on the system so that data can be integrated,
managed and secured. The standard edition is recommended for large configurations.
1. The "Installing Prerequisites” window displays the components required to be
installed. When the indication of successfully installation appears, press Next to
continue.

2. A welcome window is now displayed. Press Next to continue.

3. When the “System Configuration Check” window shows that all actions were com-
pleted with success, press Next to continue.

g If the installation is done on a 64-bit system a warning shows up in the ASP.Net

version Field.
These warning messages are harmless and related with asp.net framework version-
ing and registration information. This does not affect TNMS Core.

54 A50023-K1027-X040-02-76D1
Issue: 2 Issue date: July 2013
Installation Manual (IMN) Installation

4. In the "Customer Information” window, in the appropriate fields, enter a user name
and the name of your company.
Uncheck the option Hide Advanced Configuration Options.
Press Next to continue.

Figure 23 “Microsoft SQL Server 2005 Setup - Registration Information” window

A50023-K1027-X040-02-76D1 55
Issue: 2 Issue date: July 2013
Installation Installation Manual (IMN)

5. In the "Components to Install” window click Advanced.

6. A “Feature Selection” window appears, with the default settings.

In Client Components select Management Tools.
In Database Services select Data Files, Replication and Shared Tools.

56 A50023-K1027-X040-02-76D1
Issue: 2 Issue date: July 2013
Installation Manual (IMN) Installation

g The Replication allows SQL to copy the database from the active server into the
standby server.

Figure 24 Feature Selection window

Press Next.

A50023-K1027-X040-02-76D1 57
Issue: 2 Issue date: July 2013
Installation Installation Manual (IMN)

7. In the “Instance Name” window select Default Instance. If an installation of MSDE

exists, this procedure results in an upgrade with the current installation options.
Press Next.

Figure 25 “Microsoft SQL Server 2005 Setup - Instance name” window

8. In the "Service Account” window select Local system as the built-in system
account, add SQL Server Agent (signaling the check mark) to the starting services
at the end of setup and click Next.
SQL Server Agent executes jobs, monitors SQL Server, fires alerts and allows auto-
mation of some administrative tasks.

g The default setting of “Network service” is not suitable, because it has insufficient
right assignments to TNMS.

58 A50023-K1027-X040-02-76D1
Issue: 2 Issue date: July 2013
Installation Manual (IMN) Installation

Figure 26 “Microsoft SQL Server 2005 Setup - Service Account” window

9. In the "Authentication Mode” window, select Mixed Mode. For a proper MS SQL
Server Standard Edition installation and successful operation with TNMS Log Tool,
the password should be given. Press Next.

g Setup does not allow providing an empty password for the account “sa”.

A50023-K1027-X040-02-76D1 59
Issue: 2 Issue date: July 2013
Installation Installation Manual (IMN)

10. In the "Collation Settings” window, select SQL collations and press Next.

Figure 27 “Microsoft SQL Server 2005 Setup - Collation Settings” window

11. In the ”User Instances” window, leave the default settings and click Next.

12. In the ”Error and Usage Report Settings” window, leave the default settings and
press Next.

13. In the “Ready to Install” window, click Install.

14. Once the installation is complete, reboot your system.

15. After the system reboot it is necessary to configure MS SQL Server 2005, using the
tool “SQL Server Configuration Manager”.

60 A50023-K1027-X040-02-76D1
Issue: 2 Issue date: July 2013
Installation Manual (IMN) Installation

Tool “SQL Server Configuration Manager”

To modify or check some additional settings using “SQL Server Configuration Manager”:
1. Click Windows Start button.

2. Click All Programs.

3. Select Microsoft SQL Server 2005.

4. Click Configuration Tools.

5. Click SQL Server Configuration Manager.

6. Select Protocols for MSSQLSERVER, in SQL Server 2005 Network Configuration.

7. Set the protocol “TCP/IP” and “Named Pipes” to Enabled.

Figure 28 “SQL Server Configuration Manager - Protocols for MSSQLSERVER”

window

A50023-K1027-X040-02-76D1 61
Issue: 2 Issue date: July 2013
Installation Installation Manual (IMN)

8. Right-click “TCP/IP” and select Properties. Go to IP Addresses tab and, for all IPs,
for fields Active and Enabled, select “Yes”.

Figure 29 “SQL Server Configuration Manager - TCP/IP Properties” window

9. Select Client Protocols, in SQL Native Client Configuration.

Figure 30 “SQL Server Configuration Manager - Client Protocols” window

10. Order sequentially “Shared Memory”, “TCP/IP” and “Named Pipes”, and select the
value Enabled to each.

11. Reboot the system to finish the configuration procedure.

The installation and configuration of MS SQL Server 2005 Standard Edition are finished.

62 A50023-K1027-X040-02-76D1
Issue: 2 Issue date: July 2013
Installation Manual (IMN) Installation

4.4.3.3 Express Edition

MS SQL Server 2005 must be installed on the system so that data can be integrated,
managed and secure. The express edition is recommended for small or medium config-
uration.
To install MS SQL Server 2005 Express Edition, proceed as follows:
1. Run the SQL installation file. In the “End User License Agreement” window check
the “I accept the licensing terms and conditions” option. Press Next to continue.

2. The "Installing Prerequisites” window, displays the components needed to be

installed. Press Install to continue.

3. When all the components are installed, press Next to continue.

4. A welcome window is now displayed. Press Next to continue.

5. When the “System Configuration Check” window shows that all actions were com-
pleted with success, press Next to continue.

g If the installation is done on a 64-bit system, a warning shows up in the ASP.Net

version Field.
These warning messages are harmless and related with asp.net framework version-
ing and registration information. This does not affect TNMS Core.

6. In the "Registration Information” window, enter a user name and the name of your
company in the appropriate fields. Uncheck the “Hide advanced configuration
options” and press Next to continue.

7. In the “Feature Selection” window, in Database Services select Replication, by

selecting in the drop down menu the option “will be installed on local hard drive”.
In Client Components select Management Studio Express.
Press Next.

8. In the “Instance Name” window select Named Instance and enter

MSSQLSERVER. If an installation of MSDE exists, this procedure results in an
upgrade with the adoption of the existing options. Press Next.

9. In the "Service Account” window, select Local system as the built-in system
account, add SQL Server (signaling the check mark) to the starting services at the
end of setup and press Next.

g The default setting of “Network service” is not suitable, because it has insufficient
right assignments to TNMS. SQL Server must be running for TNMS Core to
function properly.

10. In the "Authentication Mode” window, select Mixed Mode. For a proper MS SQL
Server Express Edition installation and successful operation with TNMS Log Tool,
the password for system administrator should be specified and confirmed. Press
Next.

A50023-K1027-X040-02-76D1 63
Issue: 2 Issue date: July 2013
Installation Installation Manual (IMN)

g Setup does not allow providing an empty password for the account “sa”.

11. In the "Collation Settings” window, select SQL collations and press Next.

Figure 31 “Microsoft SQL Server 2005 Setup - Collation Settings” window

12. In the ”Configuration options” window, leave the default settings and press Next.

13. In the ”Error and Usage Report Settings” window, leave the default settings and
press Next.

14. Once the installation is complete Reboot your system.

15. After the system reboot, it is necessary to configure MS SQL Server 2005, using the
tool “SQL Server Configuration Manager”.

64 A50023-K1027-X040-02-76D1
Issue: 2 Issue date: July 2013
Installation Manual (IMN) Installation

Tool “SQL Server Configuration Manager”

To modify or check some additional settings using “SQL Server Configuration Manager”:
1. Click Windows Start button.

2. Click All Programs.

3. Select Microsoft SQL Server 2005.

4. Click Configuration Tools.

5. Click SQL Server Configuration Manager.

6. Select Protocols for MSSQLSERVER, in SQL Server 2005 Network Configuration.

7. Set the protocol “TCP/IP” and “Named Pipes” to Enabled.

Figure 32 “SQL Server Configuration Manager - Protocols for MSSQLSERVER”

window

A50023-K1027-X040-02-76D1 65
Issue: 2 Issue date: July 2013
Installation Installation Manual (IMN)

8. Right-click “TCP/IP” and select Properties. Go to IPAddresses tab and, for all IPs,
for fields Active and Enabled, select “Yes”.

Figure 33 “SQL Server Configuration Manager - TCP/IP Properties” window

9. Select Client Protocols, in SQL Native Client Configuration.

Figure 34 “SQL Server Configuration Manager - Protocols for MSSQLSERVER”

window

10. Order sequentially “Shared Memory”, “TCP/IP” and “Named Pipes”, and select the
value Enabled to each.

11. Reboot the system to finish the configuration procedure.

The installation and configuration of MS SQL Server 2005 Express Edition are finished.

66 A50023-K1027-X040-02-76D1
Issue: 2 Issue date: July 2013
Installation Manual (IMN) Installation

g The default setting of “Network service” is not suitable, because it has insufficient right
assignments to TNMS.

4.4.3.4 SQL server configuration

However the following procedures are not mandatory, those are recommended after
installing the MS SQL Server 2005. These are part of an enhanced security feature set
and are both applicable to Standard and Express edition.
Installing the SQL server database using a separated system partition
In this scenario and for security reasons, the SQL Server data files (also referred as
database) should be installed in different drive or partition than the SQL Server installa-
tion files.
Removing all sample databases and users from the SQL Server
In case there is any existing sample database or users, they should be removed as
follows:
In the SQL console (command line) use the following commands:
Drop database {database name};
Drop user {user name};
Enforce password policy and expiration
1. Open and log to MS SQL Server Management Studio
2. In Object Explorer, expand “Security” > “Logins”
3. Right click the SQL user “TNMS” and select “Properties”
4. In “Select a page” > “General”, enable the options “Enforce password policy” and
“Enforce password expiration”.
5. Press OK
The above can also be performed via the SQL console (command line) using the follow-
ing commands:
• ALTER LOGIN TNMS WITH CHECK_POLICY = ON;
• ALTER LOGIN TNMS WITH CHECK_EXPIRATION=ON;

4.4.3.5 Service Pack 4

g In case of SQL Server 2005 Standard Edition, install SQL Service Pack 4.
In case of SQL Server 2005 Express Edition, SQL Service Pack 4 is automatically
installed.

The MS SQL SP4 can be found in Microsoft official media.

To install MS SQL Service Pack 4 (SP4), proceed as follows:
1. Double-click the installation file.

2. The setup looks for instances of SQL Server.

A50023-K1027-X040-02-76D1 67
Issue: 2 Issue date: July 2013
Installation Installation Manual (IMN)

3. In the “Welcome” window press Next.

4. In the "License Terms” window, select I accept the agreement and press Next.

5. In the "Feature Selection” window, select the features to update (selecting a feature
allows viewing it’s details). Press Next.

6. In the "Error and Usage Reporting Settings” window, press Next, without selecting
any option.

g Install the MSXML 6.0 but make sure that MSXML 4.0 SP2 is already installed in the
machine. If not the MSXML 4.0 SP2 needs to be installed before installing MSXML
6.0.

7. In the ”Authentication” window:

• Check “Apply selection to all instances”.
• Choose “SQL Authentication” in the Authentication field.
• Enter the user name and password for the “sa” account.
• Press Test.
The status is “Success”. Press Next to continue.

8. In the ”Running Processes” window, a list of locked files that SP4 must update is dis-
played, if it is empty press Next.

9. In the ”Ready to Install” window press Install.

10. The ”Installation Progress” window displays the status of the products’ installation.
When the Service pack is completed the Next button becomes active. Press Next.

11. The ”Installation Complete” window allows to consult the installation summary.
Press Next.

12. The “Additional Information” window displays several notes.

Press Finish.

4.4.3.6 Uninstalling MS SQL Server 2005

To uninstall MS SQL Server 2005 Standard Edition or Express Edition, proceed as
follows:
1. Stop the SQL server (MSSQLSERVER) process via:
Start > All Programs > Microsoft SQL Server 2005 > Configuration Tools > SQL
Server Configuration Manager, right-click the service and select Stop.
2. Go to Control Panel and uninstall Microsoft SQL Server 2005.
3. In the Uninstall wizard, select Remove SQL Server 2005 instance components
and select all instances.
Select also Remove SQL Server 2005 common components > Workstation Compo-
nents. Click Next.
4. Uninstall (one at a time) the components SQL Client, SQL Server Setup Support
Files and VSS Writer. The uninstallation of these components is automatic.

68 A50023-K1027-X040-02-76D1
Issue: 2 Issue date: July 2013
Installation Manual (IMN) Installation

4.4.4 Adobe Reader

You can either download the latest Adobe Reader from the Adobe website (recom-
mended) or use the version included in the Prerequisites folder.
To install Adobe Reader just follow the standard options show in the Reader installer.
Any specific information on this, see the Adobe Reader documentation.

4.4.5 Java JRE

To install the Java Runtime Environments just follow the default installation procedure.
If any issue appear during installation see the Oracle Java documentation.

g Make sure that Java is installed in the following sequence:

Java j2re-1.5.0_06 (32 bits)
Java j2re-1.6.0_35 (32 bits)

In case of a 64bit system installation, additionally to the previous two java releases,
youalso need to install the Java j2re-1.6.0_35 64-bit.
Disable all Java automatic updates on the machines that Java is installed. If Java auto-
matic update is enabled the system might not work properly.

4.4.6 TNMS Core Server component installation

1. Run the setup.exe of TNMS Core 14.0 10 DVD.
2. In the Welcome window click Next.
3. In the License Agreement window click Yes.
4. In the Customer Information window insert the desired User Name and Company
Name and click Next.
5. In the NSN Wallpaper installation window select the desired option and click Next.
6. In the Choose Destination Location window choose the destination folder and then
click Next.
7. In the Select TNMS Core components window choose Server and click Next.
8. In the TNMS Basic License window insert a license or check I will enter... after your
selection click Next.
9. In the Location of Server Database Files window click Next.
10. In the Select the required EML Packages window, select the packages you want to
install and then click Next.
11. In the required interface packages window, select what you want to install and click
Next.

g If you install SNMP proxy on the Server, on a distributed installation, you must install
it also on the System Administration machine, so the SNMP interface can be acti-
vated on the System Administration application.

12. In the Start Copying Files window, review your installation list and if everything is ok,
click Next.
13. If the SA password is asked during the installation enter the password and press OK.
14. In the Install Wizard Complete window, click Finish to end the installation and to
restart the machine.

A50023-K1027-X040-02-76D1 69
Issue: 2 Issue date: July 2013
Installation Installation Manual (IMN)

4.4.7 PLET
PLET is an optional tool used for exporting performance logs, alarm logs, network event
logs and system message logs. It is installed on the TNMS Core Server.
To install PLET, proceed as follows:
1. Double-click the file TNMS-PLET.exe provided on the PLET software CD.
The files required for the PLET installation are extracted.

2. A welcome window is now displayed. Press Next to continue.

3. An "Information” window is now displayed.

Although this window indicates that the installation of MDAC is prerequisite for the
installation, the MDAC is installed automatically during the TNMS Core installation.
Press Next to continue.

4. In the "Choose Destination Location” window, a default installation directory is

offered. Press Next to continue.

5. In the "Select Program Folder” window, a default program folder is offered. Press
Next to continue.
A progress bar is now displayed indicating the progress of the installation.

6. The window "InstallShield Wizard Complete” is now shown. Select the option for
restarting the computer, and press Finish to complete the installation.

To uninstall PLET, open Start > Control Panel > Add/Remove Programs:
• Select PLET from the software list.
• Click the Change/Remove button.
• Select the "Remove” option.
• Confirm the uninstall process with Finish and restart your computer.

4.4.8 TCOA proxy

The TCOA proxy, along with SNMP proxy, is an optional component which is installed
on the TNMS Core Server and on System Administration. The proxy is used to connect
TNMS Core to an umbrella management system.
The installation process for the proxy consists of the following parts:
• 4.4.8 TCOA proxy
• 3rd-party software for TCOA proxy

g The TCOA proxy requires the installation of a suitable TNMS license key.

4.4.8.1 BEFORE you proceed

This section is relevant only if you chose to install TNMS Core 14.0 10 while reusing a
previously installed machine, that is, if you uninstalled your earlier TNMS Core version
and are reusing the installed operating system and prerequisites. In this case, to

70 A50023-K1027-X040-02-76D1
Issue: 2 Issue date: July 2013
Installation Manual (IMN) Installation

upgrade the TCOA proxy, a new version of TCOA_DS must be installed. To do so,
proceed as follows:
• Stop the TNMS Core Server.
Check the processes in the task manager and if still running, stop the following ser-
vices: TNMSTelec, TNMSNetw, TNMSMan, TNMSSyst and Widget.exe.
If necessary repeat this after each reboot request during the following uninstallation
steps.
• Uninstall the current TCOA proxy.
• Uninstall the current TCOA_DS.
Look for its folder: <root drive>:\Program Files\Coriant\TNMS-C\TCOA_DS\NoSE\
bin on 32-bit machines; C:\TCOA_DS\NoSe\bin on 64-bit machines.
If the folder exists, delete it.
• Locate ...\TNMS-CORE_appl-SW_V140_10_xxx_0\Install_TNMS-Prerequisites\
TCOA_DS\TCOA_DS_Installer.exe from TNMS Core’s installation disc.
Right-click TCOA_DS_Installer.exe and choose “Run as”. The “Which user account
do you want to use to run this program” window is displayed.
Choose the option “The following user” and type:
- User Name: Administrator
- Password: <Administrator password>
You can install to the proposed default folder on 32-bit machines;
You must install to C:\TCOA_DS on 64-bit machines.
• Install the TCOA proxy.
Run ...\TNMS-CORE_appl-SW_V140_10_xxx_0\Install_TNMS-Core\TCOAProxy\
Setup.exe from TNMS Core’s installation disc.
• Start the TNMS Core Server.

4.4.8.2 3rd-party software for TCOA proxy

Prerequisites for TCOA 3rd-party software
To install the TCOA proxy the following 3rd-party software is required:
• Java Runtime Environment 1.5.0_06 (32 bits) and Java j2re-1.6.0_35 (32 bits)
• TCOA_DS - includes TAO 1.4.1.1 and Corba Notification Service 4.2.3 (containing
JacORB 2.1.3.4)
For the exact software version see section 3.3.1.
If a TCOA proxy is to be installed and GUI Cut Through is used, a separate PC and
MetaFrame is necessary. More information is provided in 4.8.3.
If multiple LAN cards are configured on a system with TCOA proxy the following instruc-
tions should be completed before the installation of the TCOA Deployment Software:
• Open Start > Control Panel > Network Connections.
• Select from the menu bar Advanced > Advanced Settings...
• Select Adapters and Bindings.
• In the Connections window identify the LAN connection that is used for the commu-
nication between TCOA and NMS. If this connection is not at the first position in the
list, select this connection and use the arrows at the right side of this window to set
this LAN connection to the first position in the list.

A50023-K1027-X040-02-76D1 71
Issue: 2 Issue date: July 2013
Installation Installation Manual (IMN)

g If you use more than one LAN card you have to complete the earlier instruction for a cor-
rectly working system. Otherwise it may be that the NMS does not receive any notifica-
tion emitted by the TCOA via Notification Service.

TCOA 3rd-party software installation overview

The "TCOA_DS" CD contains the 3rd-party software in the directory "Product_CDs" and
the "main setup" in the root directory of the CD. This launches and controls setup of the
3rd-party software. The main setup also configures the 3rd-party software after installa-
tion to operate together with TNMS Core.
The MetaFrame software must be installed separately as described in 4.8.3.

Installing TCOA 3rd-party software

The software must be installed on the TNMS Core Server machine.
1. Insert the TCOA_DS CD in the DVD-ROM drive.

2. Open the Windows Explorer.

3. Navigate to the root directory of the CD folder and run the "TCOA_DS_Setup.exe”.

4. Proceed as described in the setup windows:

"Welcome" window: Confirm with Next.
5. "License Agreement" window
• Choose "I accept the terms of License Agreement".
• Confirm with Next.
6. "Choose Install Set" window:
• Confirm with Next.
• Choose ”Full” as the type of installation.
7. "Choose Install Folder" window:
• Enter the installation directory or select it from "Browse" dialogue.
• Confirm with Next.
8. "Notification Service Configuration" window
Select the following options:
• "Contact with IMR on every server start-up" - “off” (default option).
• "Choose level of verbosity" - "fatal errors only" (default option).
• "Choose details for compact Typecodes" - “off” (default option).
• "Disable indirection encoding" - “on” (default option).
• "Please enter port number for Notification Service" - “17289” (default option).
• "Please choose maximum Java heap size for Notification Service" - choose one
of the three available values. Default is 256 MB.
• Confirm with Next.
9. “Select TAO Naming Service" window
• Choose whether to install the TAO Naming Service. Default is Yes.
• Use the default port number (10005) for Naming Service.
• Confirm with Next.
10. “Select Service mode" window
• Choose "File Persistence" mode.
• Confirm with Next.

72 A50023-K1027-X040-02-76D1
Issue: 2 Issue date: July 2013
Installation Manual (IMN) Installation

11. "Select Environment Variable" window

• Select “No”.
• Confirm with Next.
12. “"ACI process settings" window
• Select "Yes" (default option) to allow the ACI processes to use the naming
service.
• Confirm with Next.
13. “"Pre-Installation Summary" window
Check if the installation options are correct and confirm with Next to install.
14. “Install complete” window
• You computer must be restarted to complete the installation.
• Confirm with Finish.
After rebooting, proceed as follows:
• Go to C:\Program Files\Coriant\TNMS-C\TCOA_DS\NoSe\bin and run the “Object
Viewer” by double-clicking the manager.bat file. For 64-bit machines, the path is:
"C:\TCOA_DS\NoSe\bin"
• Locate the “localhost” of OpenFusion object, right-click and then click “Start” in the
context-menu. In case of already started, this step is to be skipped.
• This changes the state to started.
Ensure the services are started through Start > Control Panel > Administrative Tools >
Services.
The following services must exist and be in state “Started”:
• JacORB IMR
• TAO NT Naming Service, and
• OpenFusion.NotificationService 4.2.3

Uninstalling TCOA 3rd-party software

• In the taskbar select: Start > Control Panel.
• Double-click "Add/Remove programs".
• From the list, select: "TCOA_DS”.
• Click “Remove”.
The "InstallAnywhere Wizard” is displayed.
• Select “Uninstall”.
• Click “OK” on the "InstallShield" pop up window.
• Click “Finish” in the next window to complete TAO uninstallation.
• Click “Done” to complete TCOA_DS uninstallation.
After finishing the "InstallAnywhere" Wizard, restart the system and delete the
TCOA_DS folder from the system.

4.4.8.3 Configuring TCOA

The following chapter describes a set of configuration steps that are performed in TMF
CORBA Agent for a TNMS Core installation. The purpose of this configuration is to
provide additional stability to the system such as optimizing memory usage and inactiv-
ity intervals.

A50023-K1027-X040-02-76D1 73
Issue: 2 Issue date: July 2013
Installation Installation Manual (IMN)

These configurations are not mandatory, however recommended, and may vary with
specific hardware configurations.

TMF CORBA Agent Configuration Steps

The TCOA proxy Properties page allows the user to define the behavior of the TMF
CORBA Agent. The following properties should be set in the Notification Tab.
• Notification Service Factory IOR File Name
This value is the location of the NotificationSingleton.ior file used by the TMF
CORBA Agent to connect to Notification Service, for example, (the actual path
depends of the path where Open Fusion is installed):
%OpenFusionNotifServ%\NotificationSingleton\NotificationSingleton.ior
• Notification Service Config. Event Lifetime:
Use the default value: 86400.
• Notification Service Alarm Lifetime:
Use the default value: 1800
• Notification Service Channel Event Lifetime:
Use the default value: 0.
• TCOA Notif. Buffer max. Queue Length:
Use the default value: 100.
• Notification Service maximum Queue Length:
Represents the maximum number of notifications that can be stored without lost of
any notification while there is a connection problem between TNMS Core and the
TC-TNMS application. This value depends of the Memory Heap Size configured in
OpenFusion. For a Max Memory Heap Size of 512 Mbyte on the Notification Service
this value must be configured to 9000.
• Notification Service max Memory Usage:
For a Max. Memory Heap Size of 512 Mbyte on the Notification Service, this value
must be configured to 209715200.

4.4.8.4 Configuring TCOA proxy external interface

The following configurations must be done in the TNMS Core machine:
1. Create the “C:\ior” folder on the TNMS Core machine.
2. In TNMS Core System Administration, open the TCOA proxy properties. Select the
“Notifications” tab and insert “C:\Program files\Coriant\TNMS-C\TCOA_DS\NoSe\
domains\OpenFusion\NotificationService\NotificationSingleton\NotificationSingle-
ton.ior” file path.
For 64-bit machines, the path is: "C:\TCOA_DS\NoSe\domains\OpenFusion\local-
host\NotificationService\NotificationSingleton\NotificationSingleton.ior
3. Select the “StandardConf” tab. In the “EMS Session Factory IOR File Name” field
insert the “C:\ior\emsSessionFactory.ior” path (generated automatically). Define
“Company Name” as “Nokia Siemens Networks AG” and “EMS Name” as “TNMS-
C”.
4. Select the “Naming” tab. In the “Naming Service Context IOR File Name” field insert
the “C:\ior\NamingService.ior” path (generated automatically).
5. Start TCOA proxy in TNMS Core System Administration.

74 A50023-K1027-X040-02-76D1
Issue: 2 Issue date: July 2013
Installation Manual (IMN) Installation

4.4.9 TCOM
TCOM is optional software for TNMS Core supporting the TMF CORBA Manager and
allows managing of internal applications and NEs, such as:
• Radio NEs (RNS)
• Silvx, for example, SN16000

g TCOM for SXC requires a specific separate installation. For more information, contact
Nokia Siemens Networks Technical Sales.

Prerequisites
The following prerequisites must be met before you can begin installing the TCOM
software package:
• TNMS Core is installed on the Server and NetServer(s) machines.
The OSI stack does not need to be installed on the TCOM NetServer.
• If the FTP Server software must be installed during the installation process the latest
security hotfixes and service packs for the installed operation system are required.
The setup program may also require the original operating system installation DVD-
ROM.
If you do not want to install the FTP Server it restricts you from getting any historical
performance data from network elements.

g Deactivate the TNMS Core NetServer(s) and stop the TNMS Core Server; close all
TNMS applications and stop all TNMS Windows services.

In addition to the installation steps described for the TNMS Core component, the follow-
ing installation steps are required for TCOM operation:
• Installation of the TCOM software package, also called TCOM EML Server package,
on the Server, NetServer and System Administration machine(s)
• Configuration of the NetServer, DCN channels and NEs for this server
The complete TCOM installation process in fact consists of:
• TCOM installation
• TCOM EML Server Setup
• TCOM DCN Management configuration

4.4.9.1 TCOM installation

1. To begin installation, double-click the setup.exe provided on the TCOM CD. Do this
for the Server, NetServer and System Administration machines. The setup program
prepares the InstallShield Wizard, which guides you through the rest of the setup
process.
In the Server, Setup installs the TCOM channel only.
In the Netserver, Setup installs the TCOM channel and the NECs.

2. When Welcome window of the InstallShield Wizard appears, press "Next” to con-
tinue.

3. The License Agreement window is now displayed. Read the license agreement and
press “Yes” to accept the licensing terms and conditions and to continue.

A50023-K1027-X040-02-76D1 75
Issue: 2 Issue date: July 2013
Installation Installation Manual (IMN)

4. The Customer Information window is now displayed. Enter the user name and the
name of the company for which this copy of TCOM is registered, and press “Next”
to continue.

5. When installing TCOM on a NetServer environment and if the FTP Server is not yet
installed, you are asked if you want to install the “FTP Publishing Service”.
Click Yes if you want to install it now, otherwise click No.
After completing the FTP installation you must then install the latest security hotfixes
and service packs for the operating system.
After the installation, some service parameters are automatically set to properly
execute with the TCOM software. The only exception is related with setting the write
attribute of the FTP default root directory. This requires a system reboot followed by
an installation repair.

g Repairing the installation before the reboot, leads to improper attribute settings.

6. In the Choose Destination Location window you can select the destination folder to
install the EML-TCOM. Select the Browse button and choose the destination folder
for the installation. Then continue with Next.

7. Before the files are copied, the InstallShield Wizard displays the installation settings.
If you wish to modify any of these settings, press Back. Otherwise, you can continue
with Next.

8. The InstallShield Wizard now begins the installation. The status of the installation is
indicated by a progress bar.
During the installation also the embedded FTP Server installation on the NetServer
are carried out, if “Yes” was chosen before. After successful installation the Install
Wizard Complete window is displayed. Press Finish to complete the installation.

TCOM Software Package: Modify Installation

The “Modify” mode allows the user to add or remove components to/from the currently
installed TCOM package.
1. Double-click the setup.exe provided on the TCOM CD. The setup program prepares
the InstallShield Wizard, which guides you through the rest of the setup process.
2. In the Welcome window select “Modify” and click the Next button to continue.
3. The Start Copying Files window appears. Click Next to continue.
4. During the modification of the TCOM software, the Setup Status window appears.
5. After the successful modification of the TCOM software, the Maintenance Complete
window appears. Click Finish to complete the modification procedure.

TCOM Software Package: Repair Installation

To repair the TCOM software package execute the setup.exe file.
1. Double-click the setup.exe provided on the TCOM CD. The setup program prepares
the InstallShield Wizard, which guides you through the rest of the setup process.
2. In the Welcome window select “Repair” and click the Next button to continue.
3. During the mending of the TCOM software, the Setup Status window appears.

76 A50023-K1027-X040-02-76D1
Issue: 2 Issue date: July 2013
Installation Manual (IMN) Installation

4. Finally the Maintenance Complete window appears. Click Finish to complete the
repair procedure.

TCOM Software Package: Remove Installation

To remove the TCOM software package execute the setup.exe file and proceed as
described below: During the uninstallation process you are asked whether you would
also like to uninstall the configuration software.
1. Double-click the setup.exe provided on the TCOM CD. The setup program prepares
the InstallShield Wizard, which guides you through the rest of the setup process.
2. As TCOM is already installed a Welcome window with selection criteria opens.
Select Remove at the bottom of the window.
3. A dialog box is displayed. You are asked whether you want to remove the TCOM
software application with all its TCOM components. Confirm this dialog box by
clicking OK.
4. Finally the Maintenance Complete window appears. Click Finish to complete the
removal procedure.

4.4.9.2 TCOM installation for SXC

To enable the usage of TCOM for SXC, a specific version of TNMS Core and TCOM
must be installed under Windows Server 2008 R2 operating system.
This installation is exclusively used by TCOM for SXC and no other EML Package is
allowed.
For more information and specific installation software, contact Nokia Siemens
Networks Technical Sales.

4.4.9.3 TCOM EML Server Setup

g Before starting with the TCOM EML Server Setup, open TNMS Core System Adminis-
tration application and start all TNMS Core Windows services.

1. To proceed with the TCOM EML Server Setup open the "DCN Management”
window under TNMS Core System Administration and add a channel for the TCOM
NetServer:

A50023-K1027-X040-02-76D1 77
Issue: 2 Issue date: July 2013
Installation Installation Manual (IMN)

Figure 35 Add Channel for TCOM NetServer in the “DCN Management” Window

2. Select the channel type from the list below. The channel to be used depends on the
EMS to which a connection is to be established.

Figure 36 Select TCOM Channel as the channel type in “Select Type” window

3. In the "General” page of the "TCOM Channel Properties” window enter the unique
ID Name for the TCOM channel. You can also enter text in Description.

g Detailed information on the fields of the "General” page can be obtained by clicking
the Help button in the window.

78 A50023-K1027-X040-02-76D1
Issue: 2 Issue date: July 2013
Installation Manual (IMN) Installation

Figure 37 Enter the ID Name for the Channel on the “General” tab in the “DCN”
window

A50023-K1027-X040-02-76D1 79
Issue: 2 Issue date: July 2013
Installation Installation Manual (IMN)

4. If you want to control the DCN load during the system startup, you can choose
“Enable Scheduled Startup” and define the maximal number of network elements to
be simultaneously initialized (Figure 38).

Figure 38 “DCN” window - “Scheduled Startup” tab

5. After selecting the TCOM channel the "EMS Properties” page is displayed.

Figure 39 “DCN” window - “EMS Properties” tab (TMF 814 2.0)

80 A50023-K1027-X040-02-76D1
Issue: 2 Issue date: July 2013
Installation Manual (IMN) Installation

g Detailed information on the fields of the "EMS Properties” page can be obtained by
clicking the Help button in the window.

6. Next, if required, select the "Performance Management” register and enable the per-
formance management check box and fill in the required fields.

g Detailed information on the fields of the "Performance Management” page can be

obtained by clicking the Help button in the window.

Figure 40 “DCN” window - “Performance Management” tab

A50023-K1027-X040-02-76D1 81
Issue: 2 Issue date: July 2013
Installation Installation Manual (IMN)

7. Finally you must enter the data for the GUI Cut Through to be able to open the EMS
GUI in the TNMS Core GUI, if required by the EMS.

g Detailed information on the fields of the "Gui Cut Through” page can be obtained by
clicking the Help button in the window.

Figure 41 Enter Data on the “GUI Cut Through” tab in “DCN” window

8. Having entered these configuration data the status "Running” are displayed in the
"DCN Management” window if:
• the DCN Connections check box was activated before.
• the NetServer has been started.
• the TCOM EML Server check box was activated.
• a physical connection to the EMS exists, the EMS has been started and is ready
for communication.

Figure 42 Status is "Connecting”

82 A50023-K1027-X040-02-76D1
Issue: 2 Issue date: July 2013
Installation Manual (IMN) Installation

4.4.9.4 TCOM DCN Management configuration

1. In the "DCN Management” window of TNMS Core System Administration select the
TCOM channel (in this example, it is the channel "Shanghai”) and invoke the context
menu with a right mouse click.
Select the "Browse...” menu command to browse for the available DCN objects:

Figure 43 Browse for the DCN objects of a channel in “DCN Management”

window

2. Select the desired DCN object from the object list as shown below:

Figure 44 Select a DCN object from the “DCN Objects” list in the “Browse on
Channel...” window

A50023-K1027-X040-02-76D1 83
Issue: 2 Issue date: July 2013
Installation Installation Manual (IMN)

3. By selecting the NE and clicking the Adopt button with the left mouse tab, the
selected NE are adopted into the TNMS Core. The properties window for this NE
opens showing the "General” page. In this example, a SL64 is used.

Figure 45 "General” tab of a DCN object

Enter the ID Name; if required you can change the NE Name and enter user-defined
text into the User Text fields and click Apply to save your settings.

84 A50023-K1027-X040-02-76D1
Issue: 2 Issue date: July 2013
Installation Manual (IMN) Installation

4. You can click the "NE Properties” register below to show the "NE Properties” page.

g Do not change the field "EMS Management Element Id” in the NE Properties page.

Figure 46 “NE Properties” tab of a DCN object

Exit the window with Close.

5. In the "DCN Management” window, the DCN object (in the example below it is a
SL64) is now displayed in the state "Deactivated”.
Activate the DCN object by clicking the check box. As a result, the DCN object
changes its state to "Starting Up” and finally to “Running”.

Figure 47 “DCN Management” window - SL64 in "Deactivated” state

The TCOM DCN Management configuration is now complete. The TCOM network
element which was chosen to be configured is ready for use.

A50023-K1027-X040-02-76D1 85
Issue: 2 Issue date: July 2013
Installation Installation Manual (IMN)

4.4.10 Waveline
Waveline is an optional EML package which must be installed on the TNMS Core Client,
Server and NetServer if Waveline network elements are to be installed. The following
steps have to be performed:

g If you are reusing the operating system and prerequisites from a previous TNMS Core
release, you must uninstall the earlier version of Waveline and then install the latest
Waveline version.

To install Waveline, proceed as follows:

1. Double-click the file Setup.exe provided on the Waveline software CD.

2. A welcome window is now displayed. Press Next to continue.

3. In the "License Agreement" window, select "I accept the license agreement" and
press Next.

4. In the "Customer Information” window, enter a user name and the name of your
company in the appropriate fields. Press Next to continue.

5. In the "Choose Destination Location” window, a default installation directory is

offered. Press Next to continue.

6. In the "Start Copying Files" window, ensure that the settings displayed are correct,
and if so, press Next to continue.

7. The "Setup Status” window which is now displayed indicates the progress of the
installation.
Various LCTs are installed now as well.

8. You are now asked whether you wish to install TransXpress WaveLine. Press Yes
to continue.

9. The window "InstallShield Wizard Complete” is now shown. Select the option for
restarting the computer, and press Finish to complete the installation.

To uninstall Waveline, open Start > Control Panel > Add/Remove Programs:
• Select Waveline from the software list.
• Click the Change/Remove button.
• Select the Remove option.
• Confirm the uninstall process with Finish and restart your computer.

86 A50023-K1027-X040-02-76D1
Issue: 2 Issue date: July 2013
Installation Manual (IMN) Installation

4.4.11 NetViewer
NetViewer is an optional tool in case Radio network elements are to be installed. Net-
Viewer is composed of NetViewer Server and NetViewer Client.
This procedure is intended to provide a brief description on the NetViewer Server V10.2
and NetViewer Client V10.2 installation. For details, check the available NetViewer
V10.2 Operating Manual provided with the product package.
NetViewer Server V10.2 runs on Windows Server 2008 R2 and is installed in a machine
that has the TNMS Core Server and cannot have the TNMS Core Client. It is possible
to start NetViewer through TNMS Core Client using the context menu of a radio NE.
NetViewer Server implements all the management functions of the network and of the
NEs, including the communication with the NEs and has a database to collect all the
events (for example, alarms, status changes), performances, configuration data of the
NEs and the inventory.
NetViewer Client implements the graphical user interface for the management of the
network and of the NEs. For every NE type, a specific plug-in is provided which allows
NetViewer the control and configuration of supported equipment.

g Remove any earlier NetViewer installation before installing NetViewer 10.2.

Prerequisites for NetViewer Server Software

Before the installation of the NetViewer Server you must uninstall its earlier version.
To install the NetViewer Server, the following 3rd-party software is required:
• Microsoft Server SQL 2005 Standard Edition
• Windows Server 2008 R2 (IIS Internet Information Services must be installed)
• Java Runtime Environment 1.5.0_06 (32 bits) and Java j2re-1.6.0_35 (available on
the NetViewer CD-ROM).

Prerequisites for NetViewer Client Software

If you are reusing the operating system and prerequisites from a previous TNMS Core
release, you must uninstall the earlier version of NetViewer Client and then install the
latest NetViewer Client version.
NetViewer Client software must be installed in a different machine from the NetViewer
Server. To install the NetViewer Client, the following 3rd-party software is required:
• Microsoft Windows Server 2008 R2 SP1 (x64);
• Java Runtime Environment 1.5.0_06 (32 bits) and Java j2re-1.6.0_35 (available on
the NetViewer CD-ROM)

4.4.11.1 Installing NetViewer Server

To install NetViewer Server V10.2 proceed as follows:
1. Open the "Add/Remove Programs" window via Start > Control Panel > Add/Remove
Programs and press the Add/Remove Windows Components button. Install the
“Internet Information Service (IIS)” (required services: FTP, HTTP).
2. Open the SQL2005 package and run the setup.bat file. Follow the installation routine
selecting the Mix Authentication Mode. Reboot the machine.
3. Open the NetViewer 10.2 EU2 package and run the setup.exe file. Use the default
settings during the installation routine. When finished, reboot the machine.

A50023-K1027-X040-02-76D1 87
Issue: 2 Issue date: July 2013
Installation Installation Manual (IMN)

4. Stop the NetViewer services. To stop the NetViewer services, in the Windows
control panel, open the “Administrative Tools” window. Open the services list
through the “Services” option. Find the NetViewer services in the provided list and
in the context menu select “properties” to open the properties window. In the prop-
erties window define “Startup type” as “Manual”. Click Ok when finished, and close
the opened windows.
5. Open the NAUP 10.2 EU2 package and run the setup.exe file.
6. Open the NetViewer 10.2 EU3 package and run the setup.exe file. Use the default
settings during the installation routine. When finished, reboot the machine.
7. Open the NV Plug-ins package (physical plug-ins) and choose the appropriate sub-
folders to install the required NV Plug-ins. Further plug-ins must also be installed
when using different NEs. Always use the default settings during the installation
routine for the different plug-ins.
8. Open the TNMS_NV 11.4 package and run the setup.exe file. Use the default
settings during the installation routine and insert the local IP address when
prompted.
9. Insert the USB Hardware Key in the USB port of the computer machine and install
the Hardware Key located in the folder
“C:\netviewer\Netviewer_10.2_x.x\Netviewer_10.2_x.x\Hardkey.drv\usb”.
NetViewer V10.2 Server installation is now complete.

4.4.11.2 Installing NetViewer Client

To install NetViewer Client V10.2 proceed as follows:
1. Open the “NetViewer 10.2 EU2” package and run the “setup.exe” file. Use the
default settings during the installation routine. When finished, reboot the machine.
2. Open the “NetViewer 10.2 EU3” package and run the “setup.exe” file. Use the
default settings during the installation routine. When finished, reboot the machine.
3. Stop the NetViewer services. To stop the NetViewer services, in the Windows
control panel, open the “Administrative Tools” window. Open the services list
through the “Services” option. Find the NetViewer services in the provided list and
in the context menu select “properties” to open the properties window. In the prop-
erties window define “Startup type” as “Manual”. Click “Ok” when finished, and close
the opened windows.
4. Install the required NV plug-ins (physical plug-ins).
NetViewer V10.2 Client installation is now complete.

4.4.11.3 Configuring TCOM DCN channel

The following configurations must be done in the TNMS Core machine:
1. Create the folder “C:\iors”. Copy the .ior files generated automatically by NetViewer
Server to the TNMS Core machine.
2. Create a TCOM channel in the DCN management window of TNMS System Admin-
istration.
3. Open TCOM properties window through the context menu.
4. In the “EMS Properties” tab locate the “EMS Identification” area and define
“Company Name” as “Nokia Siemens Networks” and “EMS Name” as “NetViewer”.

88 A50023-K1027-X040-02-76D1
Issue: 2 Issue date: July 2013
Installation Manual (IMN) Installation

In the “EMS Address” area define “EMS Session Factory IOR File Name” with the
“C:\ior\Siemens_Netviewer-”IPof the NetViewer server”.ior” file path.
5. Click “Apply” when finished.

4.5 NetServer
TNMS Core NetServer operates as a mediation device for the DCNs connected to it. It
processes large volumes of data imported from the DCN and relays this information to
the Server in compressed form. The NetServer supports all NE-specific functions,
except for the element managers included with TNMS Core Client.
If you want to install only the TNMS Core NetServer proceed as follow:
1. Install the operating system as explained in previous chapters for other TNMS Core
components.

g The suitable operating system depends on the chosen hardware:

• For x86 server Primergy hardware (or equivalent) install Windows Server 2008
R2 (see 4.2 Microsoft Windows Server 2008 R2 SP1);
• For PC units install Windows 7 (see 4.3 Microsoft Windows 7 Professional SP1).

2. Install the Java JRE as explained in 4.4.5 Java JRE.

3. Install the MSXML 4.0 as described in 4.4.2 MSXML 4.0 SP2.
4. If QB3 protocol is going to be used, install OSI Stack as explained in 4.5.1 OSI Stack
installation.
5. If OSI Light is to be installed follow the instructions described in 4.5.3 OSI Light
installation.
6. You may need to configure the Active Directory as described in 4.14.1.2 Active
Directory based COM security with Windows Domain Authentication.
7. Install the TNMS Core NetServer component as described in 4.5.5 TNMS Core
NetServer component installation.
8. Install CopSSH if there are hiT 7100, hiT 7300 or ADVA NEs in your network as
described in 4.5.7 CopSSH installation

4.5.1 OSI Stack installation

If QB3 is to be used, an OSI stack must be installed on the NetServer PCs before the
NetServer software.
To install an OSI stack, proceed as follows:
1. In the TNMS Core software DVD, go to OsiStack directory, right-click the file
"setup.exe” and click “Run as administrator”.
2. A welcome window is now displayed. Press Next to continue.
3. In the "Choose Destination Location" window which is now displayed, a default
installation directory is offered for the OSI stack. Press Next to continue.
4. In the "Please select:" window, select the NSAP address option best suited to your
company’s network and press Next.
5. In the "Getting NSAP" window, enter the MAC address of the network card to
complete the local NSAP address and press Next.
6. In the "Start Copying Files" ensure that the settings displayed are correct, and if so,
press Next to continue.

A50023-K1027-X040-02-76D1 89
Issue: 2 Issue date: July 2013
Installation Installation Manual (IMN)

7. A setup status window is now displayed, showing the progress of the OSI stack
installation.
8. In the “InstallShield Wizard Complete” window select the option for restarting the
computer and press Finish to complete the OSI stack installation.

4.5.2 OSI stack configuration

Once finished the OSI stack installation and the computer rebooted, you need to
proceed with the following set of configurations:
1. Open OSI stack as administrator via
Start > Control Panel > OSI Stack, right-click OSI Stack and select “Run as admin-
istrator”.
2. Activate the following options:
• In “Bind to Network Interface Card”, activate all network interfaces.
• In “OpWin Configuration”, activate "Open Stack, when Operator starts”.
• Activate “Start stack as service".
• Click “ES-IS” Stack parameter to enter the “ES-IS configuration” and disable
“Enable emission of ES hello”.
3. Exit the OSI Stack Configuration.
In case you have to check the environment variable OSIPIPE:
1. Click Start button > Configuration > Control panel.
2. Double-click the System icon and open the "Advanced" tab.
3. Click the button "Environment variables"
4. In the lower list (user variables), search for OSIPIPE variable.

4.5.3 OSI Light installation

OSI Light must be installed if you have an OSI DCN with SNMP (= IP) controlled NEs.
OSI Light allows the SNMP DCN traffic between TNMS and the SNMP NE to be done
over OSI. The IP traffic inside the OSI DCN becomes transparent.
OSI Light must be installed only after the installation of OSI Stack.
After installing OSI Stack go to your prerequisites DVD to OSI Light folder and run the
ip2clnp.exe file. Then follow the default procedure, to install OSI Light.

g If a warning appears during installation select “Continue Anyway”.

After the installation, configure the OSI Light interface IP according to your network
setup.
You must also define the network interfaces priorities, as described below:
1. Go to Network Connections in Windows’ Control Panel.
2. Identify which network interface connects to the NEs, opposite-click on Properties,
select Internet Protocol Version 4 (TCP/IPv4) and click on Properties.
3. In the Internet Protocol Version 4 (TCP/IPv4) window, click Advanced.
4. In the Advanced TCP/IP settings window, disable Automatic Metric and define a
metric value (recommended 1 - 10).
5. Repeat steps 2 to 4 for all the other network interfaces that connect to the NEs if any,
except the OSI Light interface.

90 A50023-K1027-X040-02-76D1
Issue: 2 Issue date: July 2013
Installation Manual (IMN) Installation

6. Identify the OSI Light interface, opposite-click on Properties, select Internet

Protocol Version 4 (TCP/IPv4) and click on Properties.
7. In the Internet Protocol Version 4 (TCP/IPv4) window, click Advanced.
8. In the Advanced TCP/IP settings window, disable Automatic Metric and define a
metric value (recommended 11 - 20).

w The metric for the OSI Light interface must be higher than those defined for all other
network interfaces connecting to the NEs.

4.5.4 Uninstalling OSI stack

To uninstall the OSI stack, open Start > Control Panel > Add/Remove Programs:
1. Close the OSI stack application openwin.exe.
2. Open Start > Control Panel > Add/Remove Programs.
3. Now close the Control Panel, otherwise the "OSI Stack" icon cannot be removed.
(Any attempts to reinstall the OSI Stack would fail and report the error number -115.)
4. Select the OSI stack from the software list.
5. Click the Change/Remove button.
6. Select the Remove option.
7. Confirm the uninstall process with Finish and restart your computer.

4.5.5 TNMS Core NetServer component installation

To install the Netserver component proceed as follow:
1. Double-click the "setup.exe” file provided on the TNMS Core 14.0 10 software DVD.
2. In the Welcome window click Next.
3. in the License Agreement window click Yes.
4. In the Customer Information window insert the desired User Name and Company
Name and click Next.
5. In the NSN Wallpaper installation window select the desired option and click Next.
6. In the Choose Destination Location window choose the destination folder and then
click Next.
7. In the Select TNMS Core components window choose NetServer and click Next.
8. In the Select the required EML Packages window, choose the packages you want
to install and then click Next.
9. In the Start Copying Files window, review your installation list and if everything is ok,
click Next.
10. In the Install Wizard Complete window, click Finish to end the installation and to
restart the machine.

4.5.6 Configuring a Common Netserver

The Common Netserver configuration is required if a same machine is simultaneously
used as Netserver by TNMS and TNMS Core and you use the UDP protocol to connect
the DCN to an NE (a list of supported NEs is available in the Customer Release Notes).
In such hybrid scenarios a special configuration of the Netserver machine is required in
order to allow multiple connections without traffic interference. Moreover you should
consider a specific configuration of the DCN while using TNMS and TNMS Core clients.

A50023-K1027-X040-02-76D1 91
Issue: 2 Issue date: July 2013
Installation Installation Manual (IMN)

No common Netserver configuration is necessary if:

• you use the TCP protocol to connect the DCN to an NE both in TNMS Core and
TNMS.
• the Netserver machine is used explicitly by either TNMS Core or TNMS only.

w The Common Netserver can be configured any time after installation. However the con-
figuration must be done prior to connecting TNMS Core and TNMS to same network
element via UDP, otherwise you will get an inconsistent network state representation.

w Using both UDP and TCP protocols to connect to the same network element is not
allowed and will result in an inconsistent network state representation.

The configuration of a common Netserver is done in:

• The operating system
• TNMS
• TNMS Core
You must complete all of the following three sets of instructions for the configuration to
be complete.

To configure the operating system in the Netserver machine, proceed as follows:

1. Go to Start > Control Panel.
2. Select Network and Sharing Center.
3. Change Adapter Settings.
4. In Network Connection select the Use connection.
5. Select Internet Protocol Version 4 (TCP/IPv4) and click Properties.
Make sure the IP is statically defined and not by DHCP server. Note down the
defined Primary IP, as it will be necessary at later stage.
6. Choose Advanced tab.
7. In IP Setting tab add the Secondary IP in order to be used in the common server.
Note down the Secondary IP address, as it will be necessary later on.
8. Restart the Netserver.

TNMS Core and TNMS must use different IPs to communicate with each NE via
UDP protocol. If you configure the Primary IP in TNMS you must configure the Second-
ary IP in TNMS Core and vice versa. Those IPs are configured in the Bind IP Address
field.

In TNMS proceed as follows:

1. Go to the DCN Management window.
2. Create a new SNMP channel.
3. In the General tab:
3.1 If you want to use the Primary IP leave the Automatic IP Address checked. In
the field IP Address enter the Primary IP.
3.2 If you wish to use the Secondary IP:
• Uncheck the Automatic IP Address.
• In the field IP Address enter the Primary IP.

92 A50023-K1027-X040-02-76D1
Issue: 2 Issue date: July 2013
Installation Manual (IMN) Installation

• In the field Bind IP Address enter the Secondary IP.

The connection to the NetServer is performed using the Primary IP and the con-
nection to the NEs will be established using the Secondary IP.

w Remember you must use different IPs in TNMS and in TNMS Core. If you use the
Primary IP in TNMS you must use the Secondary IP in TNMS Core and vice versa.

4. Click OK and activate the channel.

In TNMS Core proceed as follows:

1. In System Administration go to DCN.
2. In DCN Connections add a Netserver.
3. Choose the Netserver you created and add a new SNMP channel.
4. In the Channel Properties tab, in UDP Connection Settings group:
4.1 If you want to use the Primary IP leave the Automatic IP Address checked. In
the field IP Address enter the Primary IP.
4.2 If you wish to use the Secondary IP:
• Uncheck the Automatic IP Address.
• In the field IP Address enter the Primary IP.
• In the field Bind IP Address enter the Secondary IP.
The connection to the NetServer is performed using the Primary IP and the con-
nection to the NEs will be established using the Secondary IP.

w Remember you must use different IPs in TNMS and in TNMS Core. If you used the
Primary IP in TNMS you must use the Secondary IP in TNMS Core and vice versa.

5. Click OK and activate the channel.

4.5.7 CopSSH installation

CopSSH is a Secure Shell (SSH) File Transfer Protocol (SFTP) and Secure Copy (SCP)
server used for transferring data to and from some types of NEs.
CopSSH installation is only required if there are hiT 7100, hiT 7300 or ADVA NEs in
your network. CopSSH is used for transferring data to and from these NEs, namely SW
management data (MIB upload and SW download operations) and performance data.

g SFTP / SCP use is recommended since it is more secure than FTP.

CopSSH has the following security limitations that you should bear in mind:
• you cannot change the default installation path (TNMS will not work with CopSSH if
you do);
• it is impossible to limit the user activities to a specific folder within the default folder,
C:\Program Files (X86)\ICW.

4.5.7.1 Installation of CopSSH

To install CopSSH 4.1.0 proceed as follows (same procedure for all supported operating
systems):

A50023-K1027-X040-02-76D1 93
Issue: 2 Issue date: July 2013
Installation Installation Manual (IMN)

1. Copy the file

TNMS Install_TNMS-Prerequisites\CopSSH\Copssh_4.1.0_installer.zip to the
netserver machine.
2. Unzip the file Copssh_4.1.0_installer.zip, right-click the file
Copssh_4.1.0_installer.exe and click “Run as administrator”.
3. The setup wizard’s Welcome window is shown. Click Next.
4. In the License Agreement window click I Agree.
5. Accept the default installation folder by clicking Next.
6. Accept the default service account credentials (user: SvcCOPSSH and the installer
generated password, for example: HTC4c6wNnl5k73) and keep the password. Click
Install.

g If TNMS Core is installed on Windows Server 2008 R2 the installer generated

password must be used.

g In operating systems other than Windows Server 2008 R2, if you choose a new
password it has to meet the following minimum requirements:
• Passwords cannot contain the user’s account name or parts of the user’s full
name that exceed two consecutive characters.
• Passwords must be at least six characters in length.
• Passwords must contain characters from three of the following four categories:
– English uppercase characters (A through Z).
– English lowercase characters (a through z).
– Base 10 digits (0 through 9).
– Non-alphabetic characters (for example, !, $, #, %).

7. The installation starts. Click Show Details to see the details of the installation.
8. Click Close to finish the installation.
9. Restart the server machine.
Still in the installation DVD, open the patch installation.txt and proceed as
described in the file (extract the zip and copy the file to the folder described above).

4.5.7.2 Configuration and use of CopSSH

As a security measure, CopSSH’s default user cannot be used to access the machine.
Therefore, new users must be created.
Configuring users in CopSSH:
1. Create a user with limited privileges machine operating system. This user will be
used to perform the SFTP / SCP.
2. Go to Start > Programs > CopSSH, opposite-click on CopSSH Control Panel and
click Run as administrator.
3. In the Status tab, check if the service is running (green button). If not, click on the
red button to start it.
4. Go to the Users tab and click Add.
5. Click Forward to begin the CopSSH User Activation wizard.
6. Choose the current machine for domain and the user you created earlier. Click
Forward.
7. Select Shell access type:

94 A50023-K1027-X040-02-76D1
Issue: 2 Issue date: July 2013
Installation Manual (IMN) Installation

• For ADVA NEs select “Linux Shell and SCP”.

• For hiT 7100 and hiT 7300 select “Sftp”.
and uncheck "Allow PKA authentication" and "Allow TCP forwarding". Only "Allow
password authentication” must remain checked.
Click Forward.
8. Click Apply to activate the user.
9. Go to Properties of C:\Program Files (X86)\ICW (or the installation path, if different
from the default), add the user created in 1. and give the user modify permissions.
10. Restart the machine.
11. Go to Start > Programs > CopSSH > CopSSH Control Panel and in the Status
tab, check that the CopSSH service is running (green color). If not:
11.1 Go to (Windows) Control panel > Administrative tools > Services.
11.2 Opposite-click the service "Openssh SSHD" and select Properties.
11.3 In the Log On tab, select Local System account.
11.4 Click OK.
11.5 Start the Openssh service.
12. Go to the DCN Management in System Administration.
13. Opposite-click NE and select Properties.
14. Go to tab FTP Settings and select SFTP as Transfer mode.
15. Fill the remaining fields in. Click Help for detailed instructions on each field and how
to fill it in.
16. Click OK.
For ADVA NEs, if you wish to further restrict the CopSSH's user privileges by making
connections via interactive shell impossible, do as follows:

f Note that, if you run the CopSSH's GUI after the procedure below, all the changes to the
passwd file will be reset.

1. Go to <CopSSH installation path>\etc\ and edit the passwd file.

2. Edit the line (example) from
reguser:unused:11010:10513:reguser,U-TSVM41\TestPL,S-1-5-21-
2769772405-123357289-3683661142-1010:/home/reguser:/bin/bash
to
(...)/bin/false
3. Save the file.

4.5.8 SSL Installation

TNMS Core supports Secure Sockets Layer (SSL) strong cipher in order to connect to
hiT7500 NEs in version 3.45 and above.
This feature requires dedicated licenses.
The SSL strong cipher is available as an installation package and is required for
NetServer machines in order to use TNMS Core with a SSL V3 Strong Encryption
Package supporting the following cipher types:
• DHE-RSA-AES128-SHA
• DHE-DSS-AES128-SHA
• AES128-SHA
• DHE-DSS-RC4-SHA

A50023-K1027-X040-02-76D1 95
Issue: 2 Issue date: July 2013
Installation Installation Manual (IMN)

• RC4-SHA
• RC4-MD5
To install the SSL strong cipher, follow the instruction below:
1. Locate the file SecPack_Strong.zip
2. Extract and run the executable file.
The SSL is then installed in the Netserver machine. Additionally, you must run the fol-
lowing batch file in both TNMS Core Client and TNMS Core System Administration:
Run_in_Client_and_SysAdmin(SSL_patch).bat.
In Windows 7 installation choose Run as Administrator mode.

4.6 Backup Server

To install the TNMS Core Backup Server, follow the instructions below:
1. Install the Operating System. For Microsoft Windows Server 2008 R2 SP1 see
4.2 Microsoft Windows Server 2008 R2 SP1.
2. Install the Java JRE as described in 4.4.5 Java JRE.
3. You may need to configure the Active Directory as described in 4.14.1.2 Active
Directory based COM security with Windows Domain Authentication.
4. Install the TNMS Core Backup Server component as described in 4.6.1 TNMS Core
Backup Server component installation.

4.6.1 TNMS Core Backup Server component installation

To install the Backup Server component proceed as follow:
1. Run the setup.exe of TNMS Core 14.0 10 DVD.
2. In the Welcome window click Next.
3. in the License Agreement window click Yes
4. In the Customer Information window insert the desired User Name and Company
Name and click Next.
5. In the NSN Wallpaper installation window select the desired option and click Next.
6. In the Choose Destination Location window choose the destination folder and then
click Next.
7. In the Select TNMS Core components window choose Backup Server and click
Next.
8. In the Start Copying Files window, review your installation list and if everything is ok,
click Next.
9. In the Install Wizard Complete window, click Finish to end the installation and to
restart the machine.

4.7 Standby Server

The Standby Server is not part of the main Server installation sequence, instead, it is a
parallel installation of a TNMS Core Server.

w Initialization of the standby mechanism during the startup phase of the active server is
explicitly not allowed as to avoid adding the database replication to the heavy system
load.

96 A50023-K1027-X040-02-76D1
Issue: 2 Issue date: July 2013
Installation Manual (IMN) Installation

w Initialization of the database replication requires an actual backup of the active data-
base. Therefore, this initialization cannot be simultaneous with the manual or automatic
creation of a backup set.

To install and configure a Standby Server:

1. Install the Standby Server machine as described in 4.4 Server.
Note that the hardware must be the same as used for the Active Server.
2. On the Standby Server, go to Start > Control Panel > Administrative Tools > Ser-
vices, stop the TNMS server process and configure its start-up type as “manual”.
3. On the Active Server, start the data replication to the standby server from the
TNMS Core System Administration:
3.1 Go to the System Administration tree (beneath Server > DataBase in the com-
ponent tree) and click on Data Replication.
3.2 Click on Data Replication and enter the name of the standby server or select
one via the button …
3.3 Click Start to activate the replication process.
The status of the replication process is displayed in the Data Replication
window. When the replication is in progress the status is activated.When repli-
cation is complete, press Close to exit the window.
3.4 Log out of System Administration by pressing the Logoff icon in the main
toolbar. The connection to the TNMS Core Server will now be terminated.
4. On the Standby Server:
4.1 Open the TNMS Core System Administration and click Login in the main menu.
4.2 Enter the name of the Standby Server and the credentials and click OK.
Once you are logged in, notice that the replication feature is the only one dis-
played in the component tree.
4.3 Opposite-click Replication and select from the context menu Validate Connec-
tion to check the connection between the working server and the standby
server. The result of the check is displayed in a separate message box.
The Standby Server is now running and ready to replace the Active Server should it fail
or require maintenance.
Refer to the TNMS Core System Administration online help for instructions on how to
switch to the Standby Server as well as troubleshooting.

4.8 Client
You can install the TNMS Core Client on the following operating systems:
• Microsoft Windows 7 Professional or Ultimate SP1. Microsoft Windows 7 Profes-
sional SP1 is recommended for Client machines. For information on how to install
this operating system see Microsoft Windows 7 Professional SP1.
• Microsoft Windows Server 2008 R2 SP1. For information on how to install this oper-
ating system see Microsoft Windows Server 2008 R2 SP1.

4.8.1 Adobe Reader

To install Adobe Reader, run the .exe delivered with the TNMS Core CDs and follow the
standard installation procedure.

A50023-K1027-X040-02-76D1 97
Issue: 2 Issue date: July 2013
Installation Installation Manual (IMN)

4.8.2 MSXML 4.0 SP2

To instal MSXML 4.0 SP2, proceed as described in 4.4.2 MSXML 4.0 SP2.

4.8.3 Citrix XenApp 6.5 (for Windows Server 2008 R2)

Citrix XenApp is used to enable remote access to specific software applications on a
networked computer.

g This is only valid for operating system Windows Server 2008 R2. If you have your
target machine is installed with Windows 7 ignore this step and jump to 4.8.4 Installing
TNMS Core Client component.

4.8.3.1 Operating System build Prerequisites

It is assumed that the following server prerequisites have been completed:
• Operating System is Windows Server 2008 R2
• All Critical and Recommended Microsoft patches are installed
• Java Runtime 1.6.0_35 installed
• All servers are members of a Microsoft Active Directory domain (refer to Microsoft’s
documentation for further info on how to configure)
• DNS resolution for all servers in the Active Directory is operating correctly
• Installer user account has the Domain Administrative rights
• In case you are using a Citrix remote access to the server computer, you may expe-
rience difficulties in exporting DCN objects using the Save as function. To overcome
this, locate and open the file hosts, typically in C:\Windows\System32\
drivers\etc, and enter the server IP and hostname at the end of the file, for
example, 10.0.2.2 hostname.

4.8.3.2 Remote Desktop Services Licensing setup

At least one Remote Desktop Server Licensing Server must exist in the Domain, typi-
cally this role is installed on each Domain Controller and Remote Desktop Server
(RDS) Client Access Licenses (CAL) split across both Licences Servers.If an existing
server is to provide Remote Desktop Server Licensing management then the Remote
Desktop Server Licensing component can be omitted.The Windows Server 2008 R2
requires Remote Desktop Services to be installed to support the XenApp Server appli-
cation.
To install RDS licensing:
1. Go to Start > Administrative Tools > Server Manager.
2. Click Roles in the tree to display the roles summary.
3. Click Add Roles.
4. Select Remote Desktop Server from the list of roles and click Next.
5. Click Next to continue.
6. Select Remote Desktop Licensing from the list of role services and click Next.
7. Check Configure a discovery scope for this license server and select
The forest. Click Next.
8. Verify the details and click Install.
9. Click Close to finish the installation of the new role.

98 A50023-K1027-X040-02-76D1
Issue: 2 Issue date: July 2013
Installation Manual (IMN) Installation

To configure the RDS Client Access License (CAL):

1. Go to Start > Remote Desktop Services > Remote Desktop Licensing Manager.
2. Select the server name.
3. Go to Menu bar > Action > Activate Server.
4. In the “Activate Serve” wizard click Next.
5. In “Connection Method” leave the default option (Automatic selection) selected
and click Next. The wizard continues.
6. Enter the required Company Information and click Next.
7. Optionally enter additional company information. Click Next.
8. In “Completing the Activate Server Wizard” check Start Install Licenses Wizard
now and click Next.
9. The “Install Licenses Wizard” starts. Verify the License Server Settings and click
Next.
10. In “License Program” select License Pack (Retail Purchase) and click Next.
11. In “License Code” enter the Remote Desktop licenses and click Add. Click Next
once all the licenses were added.
12. Click Finish to complete the RDS licences activation.
13. A green tick is shown by the server name in RD Licensing Manager.

4.8.3.3 Configuring Remote Desktop Session Host

Perform the following on all the CITRIX XenApp Servers:
1. Go to Start > Administrative Tools > Server Manager.
2. Click Roles in the tree to display the roles summary.
3. In “Roles Summary” click Add Roles to begin the “Add Roles Wizard”.
4. Select Remote Desktop Server from the list of roles and click Next.
5. Click Next to continue.
6. Select Remote Desktop Session Host from the list of role services and click Next.
7. Click Next to continue.
8. In “Specify Authentication Method for RDS Host” select Require Network Level
Authentication and click Next.
9. In “Specify Licensing Mode” select Per User or Per Device, depending on your
licenses.
10. In “Select User Groups Allowed Access To This RD Session Host Server” click Add
to add the CITRIX User Group and allow users to connect remotely.
11. In the Select Users, Computers or Groups window enter “citrix” and click Check
Names.
12. Select CITRIX-Users and click OK.
13. Click OK.
14. Click Next to continue with the Add Roles Wizard.
15. In “Configure Client Experience” use the default settings. Click Next.
16. Verify the details and click Install.
17. Click Close.
18. Restart the server.
19. Click Close to finish the installation.

A50023-K1027-X040-02-76D1 99
Issue: 2 Issue date: July 2013
Installation Installation Manual (IMN)

4.8.3.4 Adding Remote Desktop License Server details on Remote Desktop

clients
On all CITRIX Servers add the Remote Desktop License server details as following:
1. Go to Start > Remote Desktop Services > Remote Desktop Session Host Con-
figuration.
2. Click on Remote Desktop license servers.
3. Click Close on the warning.
4. Go to the Licensing tab, select Per User mode and click Add.
5. Select the known license servers (on the left pane) and click Add to add them to the
list of specified license servers.
6. Once all available license servers are added, click OK.
7. Click Apply and OK to finish.
On “Remote Desktop Session Host Configuration”, “Remote Desktop license
servers” are now updated to Specified.
8. Click on Licensing Diagnosis in the left pane’s tree.
9. Expand the licensing details (Licensing Diagnosis Information and Remote
Desktop Services License Server Information) by clicking the arrows on the right.
Check if the configuration is correct.

4.8.3.5 Installing XenApp roles

After completing all the pre-requisites for CITRIX XenApp Server, continue with the
installation as follows:
1. Select the installation source:
• Direct CD install - insert the Citrix XenApp Server for Windows Server 2008 R2
CD.
• Network Drive CD Image - ensure a Drive Mapping has been created to point
directly to the required build version directory tree.
2. In the installation wizard, select Install XenApp Server.
3. Accept all installation requests made by the installation wizard.
4. In the window that appears, select Add server roles.
5. In the “Select a XenApp edition” window, select Advanced Edition.
6. In the “License Agreement” window, check “I accept the license agreement” then
click Next.
7. In the “Choose XenApp roles” window, select License Server, XenApp and Web
interface then click Next.

g In the Geo-Redundant CITRIX XenApp Server (secondary server) we uncheck the

License Server option.
If your farm has 3 or more members, install only the Web interface on 2 (preferably
Geo-Redundant) servers.

8. In the “Choose role subcomponents” window, select XenApp Management and

XML Service IIS Integration and click Next.
9. In the “Review prerequisites” window, click Next.
10. In the “Ready to install” window, check the details and click Install.
If any pop up appears during installation, click Yes.
11. In the “Requisite requires restart” window, click Finish to Reboot.

100 A50023-K1027-X040-02-76D1
Issue: 2 Issue date: July 2013
Installation Manual (IMN) Installation

12. After reboot run XenApp Server Role Manager. This should be available from the
windows Start button. If any User Account Control pop up appears, click Yes.
13. In the window that appears, select “Resume Install”.
14. In the “Ready to install” window, click Install.
15. After installation is complete, click Finish.

Configuring CITRIX Licence Server

1. Run the “Citrix XenApp Server role manager” and, below License Server, click Con-
figure.
2. In the “License Server Configuration window” use the default ports and enter a
password for the “admin” user.

g When configuring the Licence Server password do NOT use the “%” character as
this will cause the server to not allow login.

g If you get an error that Port 8082 is already in use, check if the Citrix License Service
is already running on the server; if it is running, stop the service and try again.

Configuring XenApp
Once the CITRIX License server is configured, the next step is to configure the XenApp
in the Citrix XenApp Server Role Manager:
1. Run the “Citrix XenApp Server role manager” and, below XenApp, click Configure.
2. If this is the first server in the Farm, you must create a new farm; otherwise add the
server to an existing farm as described in 4.8.3.6 Joining an existing Farm.
Create a new server farm on the Primary XenApp Server by proceeding as follows:
2.1 In the window “Choose a task to perform” click on Create a new server farm.
2.2 In the “Enter basic information...” window proceed as follows:
• Enter the desired farm name on New XenApp Server farm name.
• On First Citrix administrator account, use the windows administrator
account “COMPUTERNAME\Administrator”, where “computername” is the
name of the computer on your network.
After this actions click Next.
2.3 In the “Enter Citrix License Server information” select “Use an existing license
server” and enter the License Server name. Click Next.
2.4 In the “Choose a database for the new server farm”, select New database.

g For all secondary CITRIX XenApp servers in the Farm select Existing Micro-
soft SQL Server database.

2.5 In the “Windows Security” window enter the database account details.
Note down the details for later use. The same loging password will be used while
installing secondary CITRIX XenApp servers in the Farm
2.6 In the “Configure shadowing” window select Allow shadowing of user
sessions on this server and Force a shadow acceptance popup. Click Next.

A50023-K1027-X040-02-76D1 101
Issue: 2 Issue date: July 2013
Installation Installation Manual (IMN)

2.7 In the “Specify advanced server settings” window keep the default settings for
Zone, XML Service and Online plug-in.
On Remote Desktop Users uncheck Add Anonymous Users and Add the list
of users from the Users group.
Click Next.
2.8 In the “Ready to configure” window click Apply to start the Database installation.
2.9 After the server configuration finishes, click Finish to reboot the server.

4.8.3.6 Joining an existing Farm

On the Geo-redundant XenApp server, to join an existing farm proceed as follows:

g Before Installing XenApp on the Secondary Server, please see 4.8.3.5 Installing
XenApp roles for the procedure required before the following steps for the secondary
server.

1. In the window “Choose a task to perform” click on Join an existing server farm.
2. In “Choose a database for the new server farm”, select Existing Microsoft SQL
Server Express database.
3. In “Enter database credentials and test database connection” click Enter Creden-
tials.
4. In “Configure the connection to the existing server farm” enter the server name of
the existing XenApp SQL database server.
5. In the “Windows Security” window enter the database login credentials.
The existing XenApp SQL database credentials are those given before, while install-
ing the primary CITRIX XenApp server's database.
6. In “Enter database credentials and test database connection” click Test Connec-
tion. Click OK once the test is successfully completed.
7. In the “Configure shadowing” window select Allow shadowing of user sessions
on this server and Force a shadow acceptance popup. Click Next.
8. In the “Specify advanced server settings” window keep the default settings for Zone,
XML Service and Online plug-in.
On License Server enter the Primary CITRIX License server details.
On Remote Desktop Users uncheck Add Anonymous Users and Add the list of
users from the Users group.
Click Next.
9. In “Ready to configure”, review the settings and click Apply to continue.
10. In “Configuring server”, after the server is configured successfully, click Finish.
11. In the “Server Configuration Tasks”, under XenApp, click Reboot.
After the reboot the XenApp is configured.

4.8.3.7 Setup secure client-server communication

Follow the official procedure that can be found at Citrix's support site:
http://support.citrix.com/proddocs/topic/xenapp6-w2k8-admin/ps-securing-sec-clsrv-
conn.html.

102 A50023-K1027-X040-02-76D1
Issue: 2 Issue date: July 2013
Installation Manual (IMN) Installation

4.8.3.8 Install hotfixes

g Reboot only after all the hotfixes are installed.

1. Go to the CITRIX website: http://support.citrix.com/article/CTX132122.

2. Download and install the following hotfix:
• Citrix Hotfix XAE650W2K8R2X64R01 (Hotfix Rollup Pack 1 for Citrix XenApp
6.5 for Microsoft Windows Server 2008 R2)
3. Reboot.

4.8.3.9 Citrix License Server Reinstallation

After the hotfix installation the licence server stops working. This is an identified issue
mentioned in the Hotfix documentation. Therefore, the license server on the primary
CIRTIX XenApp server must be reinstalled:
1. Download the Citrix License server V11.9 from CITRIX download website.
2. Install the License Server V11.9 using all the default settings.

g The CITRIX License Server role can only be installed on one server in the CITRIX
Farm. Typically it is installed on the CITRIX FARM Master (only on primary License
Server).

3. Add Administrator user on CITRIX license server:

3.1 Go to Start > Citrix > Management Consoles > License Administration
Console.
3.2 In the “User Configuration” tab, click on New User.
3.3 Add Administrator user, select role Administrator and click Save.
4. Load the license file into CITRIX license server:
4.1 Open the License Server console.
4.2 Click Administration.
4.3 Go to Vendor Daemon Configuration tab and click on Import License.
4.4 Click Browse and select the license file.
4.5 Click Import License.

4.8.3.10 Installing IIS Management console

The following procedure must be performed in all the CITRIX XenApp Servers.
1. Go to Start > Server Management.
2. In the tree on the left pane, click on Server Management > Roles > Web Server
(IIS).
3. Click Add Role Services.
4. Go to Management Tools (already installed) and select IIS Management Console
and Management Services.
Click Next.
5. Confirm the Installation Selection and click Install to add the new role.

A50023-K1027-X040-02-76D1 103
Issue: 2 Issue date: July 2013
Installation Installation Manual (IMN)

4.8.3.11 Configuring Web Interface (V5.4)

The following procedure must be performed in each XenApp server in the Farm that is
running the CITRIX Web interface. In a Windows Active Directory Domain, although a
XenApp Farm may have 3 or 4 servers, typically only two sites need to be configured for
redundancy purposes. In a Windows Workgroup each server should have its own site.
Pre-requisites for XenApp Web Sites
Before publishing any XenApp website please verify the Microsoft Visual J# .NET 2.0
SE (vjredisdt64) is installed on the CITRIX XenApp Server. If missing, install it as
follows:
1. Install Microsoft Visual J# .NET 2.0 SE (vjredisdt64) from CITRIX DVD directory
\Support\JSharp20_SE.
2. Install IIS 6 Metabase Compatibility role.
3. Install IIS ASP.NET role.
4. Run the installer WebInterface.

Upgrade CITRIX WebInterface to Version 5.4

The WebInterface must be upgraded to version 5.4 on the CITRIX XenApp servers. To
upgrade, run installer "WebInterface (v5.4).exe" and follow the prompts.
1. In the “Select Language” window, click OK.
2. Click Next.
3. In “License Agreement” select “I accept the license agreement” and click Next.
4. In “Installation Location” use the default location and click Next.
5. In “Location of Clients” select Copy the clients to this computer and specify the
location of locally available clients. Click Next to continue.
6. In “Ready to Install” click Next.
7. Click Finish to complete the upgrade of the WebInterface.

Configuring XenApp Web Sites

Run the "CITRIX Web Interface Management" tool on each server that you want to set
up a web interface.
1. Go to Start > Citrix > Management Consoles > CITRIX Web Interface Manage-
ment.

g Each server must have IIS Management Console and the CITRIX Web Interface
component installed.

2. Create XenApp Web Site:

2.1 Right-click Citrix Web Interface > XenApp Web Sites and select Create Site.
2.2 In “Specify IIS Location” select Set as the default page for the IIS site and
keep the remaining default settings.
2.3 In “Specify Point of Authentication select At Web Interface. Click Next.
2.4 Confirm the settings for the new site and click Next.
2.5 In “Creating Site” check Configure the site now and click Next.

104 A50023-K1027-X040-02-76D1
Issue: 2 Issue date: July 2013
Installation Manual (IMN) Installation

2.6 In “Specify Server Farm” enter the Farm name and click Add to specify the
Member Servers.
In the XML Service Port enter “80” and choose “HTTP” for Transport type.
Click Next to continue.
2.7 In “Configure Authentication Methods”, check Explicit and click Next.
2.8 In “Domain Restriction” select Restrict domains to the following and click
Add.
Enter the Logon domain and click OK.
Click Next.
2.9 In “Specify Logon Screen Appearance” select Full and click Next.
2.10 In “Select Published Resource Type” select Online and click Next.
2.11 Confirm settings and click Finish.

3. Create XenApp Services Interface (For On-line Client Agents):

3.1 Right-click Citrix Web Interface > XenApp Services Sites and select Create
Site.
3.2 In the “Specify IIS Location” confirm the settings and click Next.
3.3 In “Creating Site” check Configure the site now and click Next.
3.4 In “Specify Server Farm” enter the Farm name and click Add to specify the
Member Servers.
In the XML Service Port enter “80” and choose “HTTP” for Transport type.
Click Next to continue.
3.5 In “Configure Authentication Methods”, check Explicit and click Properties.
3.6 In “Properties”, Explicit > Authentication Type, select Windows or NIS (UNIX)
and Domain user name and UPN.
Click Settings.
3.7 In “Settings” select Hide Domain box. Click OK.
3.8 In “Properties”, Explicit > Password Settings, check Allow users to change
password and select At any time and Do not remind.
Click OK.
3.9 Click OK.

4. Customise XenApp Web Interface:

4.1 To configure the authentication methods
Select Citrix Web Interface > XenApp Web Sites and select on the right pane
XenApp - Edit Settings > Authentication Methods.
4.2 In “Configure Authentication Methods - XenApp” select Explicit and click Prop-
erties.
4.3 In “Properties”, Explicit > Authentication Type, select Windows or NIS (UNIX)
and Domain user name and UPN.
Click Settings.
4.4 In “Settings” select Hide Domain box. Click OK.
4.5 In “Properties”, Explicit > Password Settings, check Allow users to change
password and select At any time and Do not remind.
Click OK to finish configuring the authentication methods.
4.6 To customize the web site appearance:
Select Citrix Web Interface > XenApp Web Sites and select on the right pane
XenApp - Edit Settings > Web Site Appearance.

A50023-K1027-X040-02-76D1 105
Issue: 2 Issue date: July 2013
Installation Installation Manual (IMN)

4.7 In “Customize” Web Site Appearance click Content.

4.8 In “Content” click Add.
4.9 In “Select a Language” select Standard language code and choose English
(en).
Click Next.
4.10 In “Select Text to Customise” check Logon screen text and click Next.
4.11 In “Customise Logon Screen Test” add text to the several sections. Click
Finish.
4.12 Click OK to finish customizing the web site appearance.
4.13 To configure the plug-in deployment:
Select Citrix Web Interface > XenApp Web Sites and select on the right pane
XenApp - Edit Settings > Client Deployment.
4.14 In “Manage Plugin Deployment” check Native plugin and click Properties.
4.15 In General > Plugin Detection check Perform plugin detection at logon and
Offer upgrades for plugins. Click OK.
4.16 Click OK to finish configuring the plug-in deployment.
4.17 To Configure Workspace Control:
Select Citrix Web Interface > XenApp Web Sites and select on the right pane
XenApp - Edit Settings > Workspace Control.
4.18 In “Manage Workspace Control”:
• Check Enable workspace control;
• Check Automatically reconnect to sessions when users log on and
select Reconnect only to disconnected sessions.
• UNcheck Allow users to customize.
• Check Enable Reconnect button and select Reconnect only to discon-
nected sessions.
• UNcheck Allow users to customize.
• UNcheck Log off active sessions when users log off from the Web Inter-
face and Allow users to customize.
4.19 To Configure Client-Side proxy:
Select Citrix Web Interface > XenApp Web Sites and select on the right pane
XenApp - Edit Settings > Client-Side Proxy.
4.20 In “Edit Client-Side Proxy” click Edit to edit the default rule.
4.21 In “Edit default rule” select None and click OK.
4.22 Select Citrix Web Interface > XenApp Web Sites and select on the right pane
XenApp - Edit Settings > Session Settings.
4.23 In “Manage Session Preferences”, General > Persistent URLs, check Enable
users to access resources using browser bookmarks.
4.24 Click OK.

Configuring HTTPS
There are 3 options for SSL certificates:
• Local Certification Authority (CA) - If the Website is part of a domain with a Domain
CA installed.
• Enterprise CA - If the customer enterprise has it's own CA and this server is not part
of that domain.
• Self signed - For WebServers that are standalone.

106 A50023-K1027-X040-02-76D1
Issue: 2 Issue date: July 2013
Installation Manual (IMN) Installation

The procedure below generates the Domain Certificate and then bind it to the CITRIX
Web Interface
Generate the Server Certificate using the fully qualified domain name on both primary
and secondary CITRIX Web Interface Servers.
To generate the Domain Certificate proceed as follows:
1. Request Certificate (Local CA)
1.1 Go to Start > Administrative tools > Server Manager
1.2 In the tree in the left pane go to Server Manager > Roles > Web Server (IIS) >
Internet Information Services (IIS) Manager.
1.3 Under “Connections” select the server and click Server Certificates in the right
pane.
1.4 Under “Actions” click Create Domain Certificate.
1.5 In “Create Certificate - Distinguished Name Properties” add the details for the
new certificate. Click Next.
1.6 In “Online Certification Authority” specify the CA and the friendly name for the
certificate. Click Finish.
2. Configure https for CITRIX Website:
2.1 In Server Manager, under “Connections” go to Server name > Sites > Default
Web Site.
2.2 Under “Actions” click Bindings.
2.3 In “Site Bindings” click Edit.
2.4 In “Edit Site Bindings” select https in Type and the certificate under SSL certif-
icate. Click OK.
2.5 Click Close.
2.6 Under SSL Settings, check Require SSL. Click Apply.

4.8.3.12 Post installation configuration tasks

After installing CITRIX XenApp, the XenApp farm and the relevant servers, they must
be configured and customized to support the TNMS Applications.

4.8.3.13 Using group memberships to control access

Users are assigned membership to one or more groups to control access to the
Windows, XenApp and TNMS application environment.
By default all new users have membership of group "Users" or "Domain Users". TNMS
Users must also be a member of the "TNMS Core Users" Group, which gives the users
read/write access to the TNMS Directories.
TNMS Users must be granted membership of a set of CITRIX Groups to make the
relevant XenApp Published applications visible to them. For each user, assign group
membership according to the following table:

A50023-K1027-X040-02-76D1 107
Issue: 2 Issue date: July 2013
Installation Installation Manual (IMN)

Group name Characteristics Default visibility of published

applications
Users (Workgroup) Normal User access to Windows. None
Domain Users (Domain) No administrative access

TNMS Users Read/Write Access to TNMS Direc- None

tories
CITRIX - TNMS SysAdmin Users Access to TNMS SysAdmin Client TNMS SysAdmin - Production
(Prod) (used by CITRIX WEB and Program TNMS SysAdmin - <hostname>
Neighbourhood)
CITRIX - TNMS Client Users (Prod) Access to TNMS Client (used by TNMS Client - Production
CITRIX WEB and Program Neigh- TNMS Client - <hostname>
bourhood)
CITRIX - Desktop Users (Prod) Access to Windows Desktop via Desktop
XenApp (used by CITRIX WEB and
Program Neighbourhood)
CITRIX - RAdmin Users (Prod) Access to Radmin via XenApp RADMin - Production
(used by CITRIX WEB and Program RADMin - <hostname>
Neighbourhood)
Administrators (Workgroup) Access to whole system. None
Domain Admins (Domain) (Allocate to appropriate groups)

Table 8 Group membership (groups in bold are built-in groups)

Published Application Names Comments Groups with access rights

TNMS Client - Production Load Balanced TNMS User Client - TNMS Core Users
GUI. - CITRIX - TNMS Client Users
TNMS Client - <hostname> Specific Server TNMS User Client (Prod)
GUI. - Administrators
TNMS SysAdmin - Production Load Balanced TNMS Admin Client - TNMS Core Users
GUI. - CITRIX - TNMS SysAdmin Users
TNMS SysAdmin - <hostname> Specific Server TNMS Admin Client (Prod)
GUI. - Administrators
TNMS Desktop Load Balanced Windows Server - TNMS Core Users
2008 R2 Desktop - CITRIX - Desktop Users (Prod)
TNMS Desktop - <hostname> Specific Server Windows 2008 R2 - Administrators
Desktop

Table 9 Published applications and group relationship

108 A50023-K1027-X040-02-76D1
Issue: 2 Issue date: July 2013
Installation Manual (IMN) Installation

Published Application Names Comments Groups with access rights

RADMin - Production Server Console access via RADMin - Administrators
RADMin - <hostname>

Table 9 Published applications and group relationship (Cont.)

4.8.3.14 Configuring TNMS Published Applications

Setting up Windows Groups to control access:
1. Go to “Active Directory Users and Computers”.
2. In the left pane tree go to Groups > Production.
3. Right-click each domain security group and edit their Properties.
4. In “Properties” select Global in “Group scope” and Security in “Group type”.

Adding TNMS Core Users to Local Remote Desktop Users Group to allow access
To enable XenApp access to non-administrators, all members of the "TNMS Core
Users" group must be added to the local "Remote Desktop Users" group on each
XenApp host:
1. Go to Start > Administrative tools > Server Manager.
2. In the left pane tree go to Server Manager > Configuration > Local Users and
Groups > Groups.
3. From the list of groups right-click Remote Desktop Users and select Properties.
4. Click Add and add “CITRIX-Users” to remote desktop user group.

Applying group privileges to TNMS directories

1. Navigate in Windows Explorer to the TNMS folder.
2. In the folder tree, right-click the TNMS folder and select Properties.
3. In the Security tab, add the “TNMS Core Users” group to the directory security and
allow the following permissions: Modify, Read & Execute, List Folder Contents,
Read, Write.

Publishing Applications
The TNMS Applications must be "Published" so XenApp Users can access them.
1. Go to Start > Citrix > Management Consoles > Citrix Delivery Services
Console.
2. Create a Published Application folder:
2.1 Go to Citrix Resources > Presentation Server > <server name> > Applica-
tions.
2.2 Under Common Tasks, click New and select Create folder.
2.3 Enter the folder name and check Copy permissions from the parent folder.
2.4 Click OK.
3. Create a Published application:
3.1 Under Common Tasks, click New and select Publish Application.
3.2 In the “Publishing Application” welcome screen, click Next.

A50023-K1027-X040-02-76D1 109
Issue: 2 Issue date: July 2013
Installation Installation Manual (IMN)

3.3 In the “Name” screen enter the Application name, according to Table 9. Click
Next.
3.4 In the “Type” screen select the published application type. Click Next.
3.5 In the “Location” screen enter the location of the Command line and Working
directory.
Click Next.
3.6 In the “Servers” screen Add the servers that will host the application.
Click Next.
3.7 In the “Users” screen configure the users that may access the application.
In the “Select Users or Groups” select CITRIX in “Look in”. Select the users and
click Add.
Click Next.
3.8 In the “Shortcut presentation” screen configure the application shortcuts. Click
Next.
3.9 In the “Publish immediately” screen click Finish.
4. Modify a Published application:
4.1 Go to Citrix Resources > Presentation Server > <server name> > Applica-
tions.
4.2 Right-click the application and select Modify application properties > Modify
all properties.
4.3 Select the properties to modify from the left pane tree.
4.4 Click OK.

4.8.4 Installing TNMS Core Client component

To install the TNMS Core Client application proceed as follows:
1. Run the setup.exe of TNMS Core 14.0 10 DVD.
2. In the Welcome window click Next.
3. in the License Agreement window click Yes.
4. In the Customer Information window insert the desired User Name and Company
Name and click Next.
5. In the NSN Wallpaper installation window select the desired option and click Next.
6. In the Choose Destination Location window choose the destination folder and then
click Next.
7. In the Select TNMS Core components window choose Client and click Next.
8. In the Select the required EML Packages window, choose the packages you want
to install and then click Next.
9. In the Start Copying Files window, review your installation list and if everything is ok,
click Next.
10. If a alert stating that “Support of SQL processing is missing on this machine” appear,
click Yes to install the MDAC.
10.1 In the End User License Agreement window click Next.
10.2 In the Installing the software window click Finish to begin the installation.
10.3 In the Setup is complete window click Close to finish the installation and to go
back to the TNMS Core Client installation.
11. If the Install additional component window appear, install the JRE 1.5.0_06 (32 bits)
by clicking Next.
11.1 In the License Agreement window click Accept.

110 A50023-K1027-X040-02-76D1
Issue: 2 Issue date: July 2013
Installation Manual (IMN) Installation

11.2 In the Installation Completed window, click Finish.

12. If the Install additional component window appear, install the JRE 1.6.0_35 (32 bits)
by clicking Next.
12.1 In the Install additional component window click Next.
12.2 In the welcome to Java window click Accept.
12.3 In the Installation Completed window, click Finish.
13. If any Java installation appear during the installation choose Don’t run this setup
now and click Next.
14. If a warning about the FTP Services appear click, OK to continue the installation.
15. In the Install Wizard Complete window, click Finish to end the installation and to
restart the machine.

4.9 System Administration

To install the TNMS Core System Administration, proceed as follow:
1. Install the Operating System as described in 4.8 Client.
2. Install the MSXML as described in 4.4.2 MSXML 4.0 SP2.
3. Instal the Java JRE as described in 4.4.5 Java JRE.
4. Install the Adobe Reader as described in 4.4.4 Adobe Reader.
5. Install the System Administration component as described in 4.9.1 System Admin-
istration component installation.

4.9.1 System Administration component installation

To install the System Administration component proceed as follow:
1. Run the setup.exe of TNMS Core 14.0 10 DVD.
2. In the Welcome window click Next.
3. in the License Agreement window click Yes
4. In the Customer Information window insert the desired User Name and Company
Name and click Next.
5. In the NSN Wallpaper installation window select the desired option and click Next.
6. In the Choose Destination Location window choose the destination folder and then
click Next.
7. In the Select TNMS Core components window select System Administration and
click Next.
8. In the Select the required EML Packages window, select the packages you want to
install and then click Next.
9. In the Select the required interface packages window, select what you want to install
and click Next.

g If you install SNMP proxy on the Server, on a distributed installation, you must install
it also on the System Administration machine, so the SNMP interface can be acti-
vated on the System Administration application.

10. In the Start Copying Files window, review your installation list and if everything is ok,
click Next.
11. If a alert stating that “Support of SQL processing is missing on this machine” appear,
click Yes to install the MDAC.

A50023-K1027-X040-02-76D1 111
Issue: 2 Issue date: July 2013
Installation Installation Manual (IMN)

11.1 In the End User License Agreement window click Next.

11.2 In the Installing the software window click Finish to begin the installation.
11.3 In the Setup is complete window click Close to finish the installation and to go
back to the TNMS Core Client installation.
12. In the Install Wizard Complete window, click Finish to end the installation and to
restart the machine.

4.10 NetServer installation in Windows Server 2003 as guest

for Windows Server 2008 R2
The following procedure is only required for new installations of TNMS Core and for
networks where legacy NEs exist which cannot be connected to a NetServer running
Windows Server 2003 (either by lack of license or hardware support to that operating
system).
For this purpose the NEs considered to be legacy (require connection running Windows
Server 2003) are listed in red in the Customer Release Note, chapter 4. SUPPORTED
NE RELEASES.
To overcome this issue, you can set up a virtualized server computing environment, in
which you can create a virtual machine where another operating system can be installed
and run. Windows Server 2008 R2 supports virtualization through the addition of the
Hyper-V server role.
The following instructions detail the installation of the Hyper-V role and creation and con-
figuration of a virtual machine with Windows Server 2003 R2 Standard Edition SP2.
It is assumed that you have a full installation of the Windows Server 2008 R2 SP1. For
other versions of Windows Server 2008 please refer to
http://technet.microsoft.com/en-us/library/cc732470(v=ws.10).aspx#BKMK_reqs

4.10.1 Hyper-V prerequisites

To install and use the Hyper-V role, the following are required:
• An x64-based processor. Hyper-V is available in x64-based versions of Windows
Server 2008 Standard, Windows Server 2008 Enterprise and Windows Server 2008
Datacenter.
• Hardware-assisted virtualization*. This feature is available in processors that
include a virtualization option - specifically, Intel Virtualization Technology (Intel VT)
or AMD Virtualization (AMD-V). These settings are usually found as processor
options in the computer’s BIOS configuration. Make sure that they are enabled.
• Hardware-enforced Data Execution Prevention* (DEP) must be available and
enabled. Specifically, you must enable the Intel XD bit (execute disable bit) or AMD
NX bit (no execute bit). These settings are usually found as security options in the
computer’s BIOS configuration.
• Some hardware features may prevent Hyper-V from loading. Check if the following
BIOS options exist and are disabled:
• Intel V-d
• Trusted Execution
• Sufficient memory (at least 512MB available) to provide services such as I/O vir-
tualization, snapshot and management to support the virtual machines in addition to
the memory assigned to each virtual machine.

112 A50023-K1027-X040-02-76D1
Issue: 2 Issue date: July 2013
Installation Manual (IMN) Installation

• HDD capacity to store the virtualization server’s software in addition to the HDD
requirements for each virtual machine.

g * If you modify the settings for hardware-assisted virtualization or hardware-enforced

DEP, you need to turn the machine’s power off and then turn it back on. Restarting the
computer may not apply the changes to the settings.

4.10.2 Hyper-V role installation

In the Windows Server 2008 R2 SP1 machine, proceed as the following:
1. Go to Start > Server Manager.
2. Go to Action > Add Roles.
3. In the Add Roles Wizard:
3.1 select Server Roles and check Hyper-V.
3.2 select Confirmation and click Install.
4. Restart the computer.
5. After the computer restarts, wait until the Resume Configuration wizard completes
the installation.
6. Click Close to finish the wizard.

4.10.3 Configure a virtual network

In order for a virtual machine to communicate with a physical network, an external virtual
network is required under Windows Server 2008 R2 SP1. This is done by creating an
association to a physical network adapter on the virtualization server. As a best practice,
it is recommended that the physical computer has more than one physical network
adapter - one network adapter for all network communications with the management
operating system (the management operating system runs the Hyper-V role), including
remote access to the Hyper-V role and one (or more) physical network adapter to
provide virtual machines with an external virtual network, including remote access to the
virtual machines.
When you create an external virtual network, it affects how networking is configured on
the physical network adapter. After installation, the management operating system uses
a virtual network adapter to connect to the physical network. When you look at Network
Connections in the management operating system, you will see the original physical
network adapter and a new virtual network adapter. The original physical network
adapter has nothing bound to it except the Microsoft Virtual Network Switch Protocol,
and the virtual network adapter now has all of the standard protocols and services bound
to it. The virtual network adapter that appears under Network Connections has the same
name as the virtual network with which it is associated. Networking will get disrupted for
a short period of time on the network adapter when a virtual network is created or
deleted.
To create an external virtual network:
In the Windows Server 2008 R2 SP1 machine, proceed as the following:
1. Go to Start > Hyper-V Manager.
2. From the Actions pane, click Virtual Network Manager.
3. In the Virtual Network Manager window, select New virtual network.
4. In the Create Virtual Network pane, select External and click Add.

A50023-K1027-X040-02-76D1 113
Issue: 2 Issue date: July 2013
Installation Installation Manual (IMN)

5. In the New Virtual Network pane:

5.1 assign a name.
5.2 under Connection Type, select the physical network adapter to use.
6. Click OK to create the virtual network and close Virtual Network Manager.

4.10.4 Create and set up a virtual machine

To create a virtual machine to host the TNMS Core NetServer component, you will be
requested the following:
• Where to store the virtual machine and what to name it.
• What media is available for installing the operating system on the virtual machine.
You can use physical media, a remote image server, or an ISO file. The method you
want to use determines how you should configure the virtual machine.
• How much virtual memory needs to be allocated to the virtual machine.
As a best practice, it is recommended to factor in sufficient memory overhead for
each VM, namely 32 MB for the first 1 GB of virtual RAM plus another 8 MB for each
additional GB of virtual RAM.
Example to create a 4 GB VM: Use 32 MB (for the first GB) + (8x3) MB (8 MB per
each additional GB), results in 32 + 24 = 56 MB. Therefore, the total amount of
memory to allocate to the VM is 4056 MB.
Example to create a 8 GB VM: Use 32 MB (for the first GB) + (8x7) MB (8 MB per
each additional GB), results in 32 + 56 = 88 MB. Therefore, the total amount of
memory to allocate to the VM is 8088 MB.
• The size of the virtual hard disk to be allocated to the virtual machine.
To create and set up a virtual machine in the Windows Server 2008 R2 SP1 machine:
1. Go to Start > Administrative Tools > Hyper-V Manager.
2. From the Action pane click New and then Virtual Machine.
3. Go to the Specify Name and Location page and type the name of the virtual
machine and where you want to store it.
4. Go to the Assign Memory page and specify the amount of memory to allocate.
5. Go to the Configure Networking page and connect the network adapter to an
existing virtual network if you want to establish network connectivity at this point.

g If you want to use a remote image server to install an operating system on your test
virtual machine, select the external network.

6. On the Connect Virtual Hard Disk page, type the name, location, and size of the
virtual hard disk.
7. On the Installation Options page, choose how to install the operating system
Windows Server 2003 R2 Standard Edition SP2:
• from a boot CD/DVD-ROM. You can use either physical media or an image file
(.iso file).
• from a boot floppy disk.
• from a network-based installation server. To use this option, you must configure
the virtual machine with a legacy network adapter connected to an external
virtual network. The external virtual network must have access to the same
network as the image server.
8. Click Finish.

114 A50023-K1027-X040-02-76D1
Issue: 2 Issue date: July 2013
Installation Manual (IMN) Installation

4.10.5 Guest operating system, integration services and TNMS Core instal-
lation
To install the operating system in a virtual machine, in the Windows Server 2008 R2 SP1
machine, proceed as the following:
1. Go to Start > Administrative Tools > Hyper-V Manager.
2. Under Virtual Machines, select the virtual machine to install the operating system
(Windows Server 2003) and Connect.
3. From the Action menu in the Virtual Machine Connection window, click Start.
4. Proceed with the installation of the operating system.
Consult the TNMS Core 13.2 Installation Manual for the TNMS Core NetServer
operating system requirements.
5. After the operating system is installed, proceed with installation of the integration
services. From the Action menu in the Virtual Machine Connection window, click
Insert Integration Services Setup Disk.

g If Autorun does not start the installation automatically, you can start it manually. Use
the method that is appropriate for the guest operating system to start the installation
package from the disk drive.

After the integration services are installed, proceed with any post installation configura-
tions and the installation of the TNMS Core NetServer component as described in the
TNMS Core 13.2 Installation Manual.

4.11 Anti-virus
Both F-secure and Trend Micro Office Scan are supported. Refer to the Release Notes
for the supported versions.
The anti-virus software should be installed in all component machines.

4.11.1 Installation
1. Start the installer.
2. Follow the on-screen instructions.
3. Use the local installation with default configuration.
4. Do not include in the exclusion list any files or folders not recommended by the
installer.

g For further detailed information refer to the anti-virus software documentation.

4.11.2 Useful considerations

Some information on updates, policies and firewall.

4.11.2.1 Updates
TNMS systems must run on a private network. Automatic updates for the anti-virus will
not be possible, since the computers would not be connected to the Internet. Manual
update of the anti-virus is recommended, by using any of the following methods:
• using installation media with new signature files.

A50023-K1027-X040-02-76D1 115
Issue: 2 Issue date: July 2013
Installation Installation Manual (IMN)

• temporarily (and periodically) stopping the TNMS server, connecting the computer
to the Internet for update, and then disconnecting the computer from the Internet and
starting the TNMS server again.

g Since this opens a window of vulnerability, it is expected that the download of new
signature files takes only a few seconds, thus reducing this window of vulnerability
to a minimum. This is the least recommended of both methods.

4.11.2.2 Policies
If a centralized policy-based management installation is intended refer to the anti-virus
software documentation.

4.11.2.3 Firewall
If firewalls are deployed in the system, then refer to the anti-virus software documenta-
tion on how to configure them.

g To see which Ports should be open in the Firewall please see chapter 4.2.3.3 Firewall
port setup.

4.12 Uninstalling TNMS Core

TNMS Core can be uninstalled using the Windows control panel. The following informa-
tion is removed during uninstallation:
• All information used by the TNMS Core application from the Windows Registry
• All program files of the TNMS Core components
• All empty TNMS Core component directories
• The TNMS Core database
Shared files such as OLE-Dlls are not removed.
Before uninstalling TNMS Core, perform the following steps:
1. Create a backup of the current TNMS Core database. Do not use the default backup
path, since the installation folder are removed during the uninstall procedure (if unin-
stallation is not explicitly prohibited by the operator).

2. Store the local NSAP address of the Server in a text file.

3. Close all open element managers.

4. Close any open TNMS Client sessions.

5. Log off the TNMS System Administration software from the server, and exit System
Administration.

6. Stop all TNMS services on the Server and NetServer under

Start > Control Panel > Administrative Tools > Services.
The following services are possible:
TNMS Backup Server, TNMS Data Provider, TNMS NetServer, TNMS Telecommu-
nication Network Management System.

116 A50023-K1027-X040-02-76D1
Issue: 2 Issue date: July 2013
Installation Manual (IMN) Installation

You should also check the Windows Task Manager for running services and end
these processes where possible.

The software can now be uninstalled as follows:

1. Open the "Add/Remove Programs" window via Start > Control Panel> Add/Remove
Programs.

2. Select TNMS Core Vx and press “Change/Remove”.

3. The preconditions for uninstalling are checked and a welcome window is displayed.
Select "Remove” and press "Next” to continue.

4. In the "Confirm File Deletion” window, press OK to activate uninstallation. The unin-
stallation starts and information windows displays the software parts, which are cur-
rently uninstalled. This will take some minutes.

5. Depending on the programs that have been installed you may be prompted to
confirm the deletion of further files.

6. You will also be asked whether you wish to delete the directory containing your
backup files:
• If you have stored the backup files in the default directory, that is,
"C:\Program Files\Coriant\TNMS-C\data\Archive”, do not delete the directory.
• If you have stored the backup files in a different directory, you may delete the
default directory.

7. The "Maintenance Complete” window is now displayed. If certain folders could not
be deleted, this is indicated here. Press "Finish" to complete the uninstallation
process.

8. Restart the PC.

9. Delete any remaining folders manually in the Windows Explorer, for example,
C:\Program files\Coriant\TNMS\Data, C:\Program files\Coriant\TNMS-C,
C:\Program files\Coriant.

10. Check that the TNMS services listed above are removed from the services list.

A50023-K1027-X040-02-76D1 117
Issue: 2 Issue date: July 2013
Installation Installation Manual (IMN)

4.13 Adding/removing individual TNMS Core components

If individual TNMS Core components (for example, specific EML packages) are to be
installed or removed, proceed as follows:

g This chapter applies only to main versions that did not undertake any update/upgrade
yet. If the version installed is an update (minor version, EP or MP) on top of a main
version, then adding new components is not possible, only updating already installed
components.

1. Insert the installation DVD-ROM into the DVD-ROM drive.

2. Logoff and exit all client machines.

3. Logon to System Administration.

4. Stop the Server using System Administration.

5. Logoff and exit System Administration.

6. If necessary, close all other active applications.

7. Stop all TNMS services on the Server and NetServer under

Start > Control Panel > Administrative Tools > Services.
The following services are possible:
TNMS Backup Server, TNMS Data Provider, TNMS NetServer, TNMS Telecommu-
nication Network Management System.
You should also check the Windows Task Manager for running services and end
these processes where possible.

g If the QB3M service is running while the OSI stack service is being closed down, you
are also asked to close the QB3M service.

8. Start the installation/uninstallation procedure via Start > Control Panel >
Add/Remove Programs. Select "TNMS Core Vx." and click the "Change/Remove"
button.

9. In the "Welcome” window, select "Modify".

10. In the “Select TNMS Core components" window, the components already installed
are displayed. Select the components you wish to install or uninstall and press
"Next” to continue.

11. In the "Select the required EML packages” window, select the components you wish
to install or uninstall, and press "Next” to continue.

12. The "Setup Status” window, which is now displayed, indicates the progress of the
procedure.

118 A50023-K1027-X040-02-76D1
Issue: 2 Issue date: July 2013
Installation Manual (IMN) Installation

13. Once the selected components are installed or uninstalled, the "Maintenance Com-
plete" window is displayed. Press "Finish” to complete the process.

14. Restart the PC to update your installation.

4.14 Active Directory configurations

Active Directory is a directory service created for windows domain networks that
provides a central location for network administration and security. It authenticates and
authorizes users and computers in a windows domain type network, assigning and
enforcing security policies for computers and software. When a user logs into a
computer that is part of a windows domain, the Active Directory verifies the password
and specifies its role in the system.
The following chapters provide descriptions on how to configure in the Active Directory
machine and in the TNMS Core Server machine.
TNMS Core uses different components (Server, Netserver, Standby Server and Clients)
that can be located in different machines. The components communicate between
themselves by using this authentication.

4.14.1 Active Directory configurations in Windows Server 2008 R2

4.14.1.1 Active Directory based COM security

If you want to use the TNMS COM security configuration without windows domain
authentication adopt the following COM security in your Windows Operating System:
1. All computers that have TNMS Core components installed must be made members
of the same Active Directory domain.

2. Two groups must be created in the Active Directory with the following names:
• TNMS Users
• TNMS Server Computers
These groups must have these exact names to ensure that COM permissions to the
TNMS Components are granted.

3. All user accounts that are used to run TNMS Core Client or System Administration
must be Active Directory accounts and also must be made members of the TNMS
Users group.

4. All computers that have a TNMS Core Server components (Server, NetServer or
Backup Server) installed must be made members of the TNMS Server Computers
group (computers that will only run TNMS Core Client or System Administration do
not need to be added to the TNMS Server Computers group).

5. In TNMS Core components machines (Client, System Administration, Server,

NetServer or Backup Server), remove "ANONYMOUS LOGON" from "Launch and
Activation Permissions" limits.

A50023-K1027-X040-02-76D1 119
Issue: 2 Issue date: July 2013
Installation Installation Manual (IMN)

5.1 Open "Component Services"

In Windows Server 2008 R2 (and Windows 7), go to "Start" > in search box type
dcomcnfg and click "dcomcnfg.exe"
5.2 In the "Component Services" window, expand "Component Services" and
"Computers".
5.3 Right click "My Computer" and select "Properties".
5.4 In "My Computer Properties" window, select "COM Security" tab
5.5 In "Launch and Activation Permissions" group, select "Edit Limits".
5.6 Remove "ANONYMOUS LOGON" if present.

g In “Access Permissions” limits, "ANONYMOUS LOGON" should not be removed

as this is a windows default.

6. In TNMS Core components machines (Client, System Administration, Server,

NetServer or Backup Server), check COM Security limits for "Distributed COM
Users" group
6.1 Open "Component Services"
In Windows Server 2008 R2 (and Windows 7), go to "Start" > in search box type
dcomcnfg and click "dcomcnfg.exe"
6.2 In "Component Services" window, expand "Component Services" and then
"Computers"
6.3 Right click "My Computer" and select "Properties".
6.4 In “My Computer Properties" window, select “COM Security" tab.
6.5 In "Access Permissions" group, select "Edit Limits"
Check that "Distributed COM Users" is allowed "Local Access" and "Remote
Access".
6.6 In "My Computer Properties" window, select "COM Security" tab.
6.7 In "Launch and Activation Permissions" group, select "Edit Limits"
Check that "Distributed COM Users" is allowed "Local Launch", "Remote
Launch", "Local Activation" and "Remote Activation".

7. Add TNMS Users and TNMS Server Computers as members of Distributed COM
Users. In order to do it proceed as follows:
7.1 Go to Administrative Tools > Computer Management.

7.2 Expand "Local Users and Groups", select “Groups”, right click the Distributed
COM Users group and select “Add to Group”.

7.3 In “Distributed COM Users Properties" window, add the TNMS Users and TNMS
Server Computers to the Members, click “OK”.

The following steps must be done only after the TNMS Core Components are installed.
8. After TNMS Core installation, run the TNMS COM Security Configuration tool in
every computer where a TNMS Core component is installed.
8.1 TNMSComSecConf.exe, must be run as Administrator in every computer
where a TNMS Core component is installed. The tool is available on TNMS
Core’s installation directory under Tools folder.
8.2 Execute the tool and click ”Enable”.

120 A50023-K1027-X040-02-76D1
Issue: 2 Issue date: July 2013
Installation Manual (IMN) Installation

g If in the future you want to remove, add components or patch TNMS Core you must
first run the TNMS COM Security Configuration tool and click “Disable”. Then enable
it again after your modification.

4.14.1.2 Active Directory based COM security with Windows Domain

Authentication

g Due to system restrictions, if the domain controller is in a Windows 2000 compatibil-

ity/mixed mode, the Windows Domain groups required for TNMS, including for user
classes, must be created as Global and not as Local ones.
In order to use Local Groups (due to simpler configuration or to allow users from trusted
domains) the Active Directory Domain Forrest must be in Windows Server 2003 mode.

Adopt the following COM security in your Windows Operating System:

1. All computers that have TNMS Core components installed must be made members
of the same Active Directory domain.

2. Two groups must be created in the Active Directory with the following names:
• TNMS Users
• TNMS Server Computers
These groups must have these exact names to ensure that COM permissions to the
TNMS Components are granted.

3. All user accounts that are used to run TNMS Core Client or System Administration
must be Active Directory accounts and also must be made members of the TNMS
Users group.

4. All computers that have a TNMS Core Server component installed must be made
members of the TNMS Server Computers group. Computers that will only run TNMS
Core Client or TNMS Core System Administration do not need to be added to the
TNMS Server Computers group.

5. In TNMS Core components machines (Client, System Administration, Server,

NetServer or Backup Server), remove "ANONYMOUS LOGON" from "Launch and
Activation Permissions" limits.
5.1 Open "Component Services"
In Windows Server 2008 R2 (and Windows 7), go to "Start" > in search box type
dcomcnfg and click "dcomcnfg.exe"
5.2 In the "Component Services" window, expand "Component Services" and
"Computers".
5.3 Right click "My Computer" and select "Properties".
5.4 In "My Computer Properties" window, select "COM Security" tab
5.5 In "Launch and Activation Permissions" group, select "Edit Limits".
5.6 Remove "ANONYMOUS LOGON" if present.

g In “Access Permissions” limits, "ANONYMOUS LOGON" should not be

removed, as this is a windows default.

A50023-K1027-X040-02-76D1 121
Issue: 2 Issue date: July 2013
Installation Installation Manual (IMN)

6. In TNMS Core components machines (Client, System Administration, Server,

NetServer or Backup Server), check COM Security limits for "Distributed COM
Users" group
6.1 Open "Component Services"
In Windows Server 2008 R2 (and Windows 7), go to "Start" > in search box type
dcomcnfg and click "dcomcnfg.exe"
6.2 In "Component Services" window, expand "Component Services" and then
"Computers"
6.3 Right click "My Computer" and select "Properties".
6.4 In “My Computer Properties" window, select “COM Security" tab.
6.5 In "Access Permissions" group, select "Edit Limits"
Check that "Distributed COM Users" is allowed "Local Access" and "Remote
Access".
6.6 In "My Computer Properties" window, select "COM Security" tab.
6.7 In "Launch and Activation Permissions" group, select "Edit Limits"
Check that "Distributed COM Users" is allowed "Local Launch", "Remote
Launch", "Local Activation" and "Remote Activation".

7. Add TNMS Users and TNMS Server Computers as members of Distributed COM
Users. In order to do it proceed as follows:
7.1 Go to Administrative Tools > Computer Management.

7.2 Expand "Local Users and Groups", select “Groups”, right click the Distributed
COM Users group and select “Add to Group”.

7.3 In “Distributed COM Users Properties" window, add the TNMS Users and TNMS
Server Computers to the Members, click “OK”.

The following steps must be done only after the TNMS Core Components are installed.
8. After TNMS Core installation, run the TNMS COM Security Configuration tool, in
every computer where a TNMS Core component is installed.
8.1 TNMSComSecConf.exe, must be run as Administrator in every computer
where a TNMS Core component is installed. The tool is available on TNMS
Core’s installation directory under Tools folder.
8.2 Execute the tool and click ”Enable”.

g If in the future you want to remove, add components or patch TNMS Core you must
first run the TNMS COM Security Configuration tool and click “Disable”. Then enable
it again after your modification.

9. After configuring DCOM security, create the following groups in Active Directory
server machine, Administrative Tools > Active Directory Users and Computers:
• TNMS UserClass Administration
• TNMS UserClass Configuration
• TNMS UserClass Operation
• TNMS UserClass Maintenance
• TNMS UserClass Supervision

122 A50023-K1027-X040-02-76D1
Issue: 2 Issue date: July 2013
Installation Manual (IMN) Installation

• TNMS Group TNMS superuser

If additional TNMS groups are to be used for restricted access or other setting also
add them to the Active Directory Users and Computers.
10. In the Active Directory server machine, each user that will access to TNMS (previ-
ously added to the TNMS Users group) shall also be added to appropriated User-
Class Group (for example, TNMS UserClass Operation for the normal Operators).
Add the user to the TNMS Group TNMS superuser if this was also expected to be
granted to the concrete user and to any other groups that he should be a member.
Make sure at least one user is configured as member of TNMS UserClass Adminis-
tration and part of the TNMS Group TNMS superuser.
11. Login to a TNMS Core System Administration, open the “Account Policy” on TNMS
Core System Administration and change the Authentication Mode to Windows
Domain.

g Do not logout System Administration at this point. The built in Administrator account
is no longer authorized to login on TNMS as the account is not part of the Windows
Domain.

12. Open a TNMS Core System Administration with Active Directory COM Security con-
figuration and with a user that is member of TNMS UserClass Administration.
Fill in the Server name address (“.” for localhost) check the “Use Single Sign On”
and press the Login button.
The user shall login to TNMS and new TNMS account is created with the following
syntax, username@domain.
13. Once the login is done and confirmed that the Administrator user is correctly part of
the TNMS UserClass Administration, the original TNMS Core System Administra-
tion window can now be closed.

g In order to use the SSO (Single Sign On) feature, TNMS Administrator must first login
to the machine containing the System Administration component using a Domain
account, and then login into TNMS System Administration and change the "Authentica-
tion mode" into one of the existing "Windows Domain..." configurations via the Account
Policy window > General Login tab > Authentication Mode.

4.14.2 Active Directory configurations in Windows 7

4.14.2.1 Active Directory based COM security with Windows Domain

Authentication
You may need to configure the Active Directory as described in 4.14.1.2 Active Directory
based COM security with Windows Domain Authentication.

4.14.3 Authentication extensions

The following procedures are recommended after configuring the Active Directory based
COM security settings. These are part of an enhanced security feature set.
1. Go to Start > Administrative Tools > Group Policy Management.
2. In the Group Policy Management console (GPMC) tree, expand Group Policy
Objects (GPO) and the domain containing the GPO that you want to edit.
3. Right-click the GPO that you want to edit, and then click Edit.

A50023-K1027-X040-02-76D1 123
Issue: 2 Issue date: July 2013
Installation Installation Manual (IMN)

4. In the Group Policy Management Editor window, expand in the console tree
Computer Configuration > Windows Settings > Security Settings > Account Policies
and then click Password Policy.
5. In Password Policy set the following values:
• Enforce password history value to 10
• Maximum password age value to 60
• Minimum password age value to 1
• Minimum password length value to 14
• Enable the Passwords must meet complexity requirements option.

124 A50023-K1027-X040-02-76D1
Issue: 2 Issue date: July 2013
Installation Manual (IMN) Upgrade to TNMS Core 14.0 10

5 Upgrade to TNMS Core 14.0 10

If you have a previous TNMS Core version installed, first of all refer to the TNMS Core
14.0 10 Upgrade Manual (UPMN) for detailed instructions on how to upgrade to Core
14.0 10(migration included). The UPMN can be ordered with TNMS Core 14.0 10.
Note that no update (installing over a previous version) is possible and therefore you
must install TNMS Core 14.0 10 in a clean machine, as instructed in
Chapter 4 Installation.

A50023-K1027-X040-02-76D1 125
Issue: 2 Issue date: July 2013
Measures after commissioning Installation Manual (IMN)

6 Measures after commissioning

After the TNMS Core software and relevant 3rd-party software have been installed, the
TNMS Core installation must be configured using the System Administration application.

6.1 Documentation installation

To install the TNMS Core documentation, proceed as follows:
1. Insert the Documentation CD.
2. Start the documentation installer through Start > Nokia Siemens Networks >
TNMS > Install Documentation.
3. The installer opens the TNMS Documentation window. Click Next.

g The installation can be canceled throughout this sequence by clicking Cancel.

4. From the displayed list select the drive for the TNMS Documentation CD. Click Next.

g If the wrong location is selected, a warning indicates the need of a new location.
Click Ok and repeat step 4.

5. The default install folder is C:\Program Files\Coriant\TNMS-C or C:\Program Files

(x86)\Coriant\TNMS-C, depending on whether the operating system is 64-bits or 32
bits.
If that was the folder where TNMS Core was installed click Next, or Choose to select
the path to the folder where TNMS Core was installed.

g The documentation and TNMS Core must be installed in the same folder.

6. Verify the pre-installation summary.

Click Install to continue or Previous to update the install folder.
7. Click Done after the indication of successful installation.

6.2 Initial TNMS Core configuration using System Administra-

tion
Once TNMS Core software has been installed and the computer restarted, the TNMS
Core system can be configured. The main steps to be completed during configuration
are listed below. Additional information is provided in the online help under Initial config-
uration - TNMS Core. This section of the help also provides links to detailed instructions
for each step to be completed.

1. Start System Administration

Start the TNMS Core System Administration interface via Start > Programs > Nokia
Siemens Networks > TNMS > System Administration.

2. login
Log onto TNMS Core System Administration via the displayed login dialog.

126 A50023-K1027-X040-02-76D1
Issue: 2 Issue date: July 2013
Installation Manual (IMN) Measures after commissioning

Figure 48 “TNMS Core System Administration Login” window

• In the field Server, enter the name of the machine where the TNMS Core Server is
installed. If you are logging in directly to the machine where the TNMS Core Server
is installed, enter ".".
• In the field User name enter the default value Administrator. This account is created
automatically during the installation of TNMS Core.
• When you log on for the first time, the field Password does not have to be completed.
• After confirming the entry via the login button, change the password for the default
administrator account as requested.

g The TNMS Core Server is still inactivate at this time.

Do not activate it until step 6 below has been completed.

3. Configure user accounts

A default administrator account is created during installation. Additional accounts can
now be created as required. Global account settings can also be edited at any time.

4. Check license availability

First of all, enter the Basic License via TNMS System Administration to be able to start
the Server. Then check whether licenses are available for the required range of func-
tions and add them.

5. Define log configuration settings

You can determine the available size of the various log files on the hard disk. Settings
can be entered for the size of the alarm log, system message log, network event log,
security event log and custom log. Performance logs can only be created if sufficient
space is reserved for custom logs.
All log files are installed in the directory <TNMS installation path>..\Logs. On the HD par-
tition where the TNMS is installed there should be at least 1 GB free disk space during
operation. If the log file size is changed (expanded) check the necessary disk space
again.

A50023-K1027-X040-02-76D1 127
Issue: 2 Issue date: July 2013
Measures after commissioning Installation Manual (IMN)

6. Configure database backup options

In TNMS Core, you can choose whether to schedule an automatic backup or to imple-
ment a manual backup. Settings are provided for the backup host, backup file path name
and for the time and frequency of archiving in System Administration.

7. Start the TNMS Core Server

To configure DCN objects and to set cost factors for automatic routing, you must start
the TNMS Core Server. Press the Start Server button in the System Administration
toolbar and confirm with OK.

8. Add NetServers
After TNMS Core installation, the NetServer computers must be linked up to the TNMS
Core via the DCN Management dialog.

g The OSILLC protocol driver must not run on more than one ethernet card.
The driver should therefore be disabled on any other cards using Start > Control Panel
> Network > Network and Dial-up connections on the NetServer.

9. Configure and activate DCN channels

DCN channels are also configured in the DCN Management dialog. Once configured,
the channel settings should be checked, for example, for scheduling communication.

10. Configure network elements

You can now add the required network elements by opposite-clicking the DCN channel
and selecting Add. Select the required network element type from the list, and complete
each tab page as described in the online help.
For SXEM and PDH network elements, you must also start the corresponding LCT once,
before starting the element manager in TNMS Core. This provides you with administra-
tor access rights to the PDH/SXEM network element. This procedure must be com-
pleted for each client after the installation of the TNMS Core Client software.

g NE names of more than 39 characters can cause problems when starting the Element
Manager. In this case, enter an NE name of less than 39 characters.

g Once you have configured NetServers, DCN channels and network elements (steps 8-
10), the status of these objects is shown in the DCN Management window.

11. Configure GNE list handling

g The configuration of GNE list handling is only necessary for hiT 7300 NEs.

At the NE Property Pages set two additional variables:

• Number of GNE list retries before holding on
This variable defines the number of attempts to connect to the NE via the alternative
route before holding on. The default number of attempts should be three (3).
• Hold on time before next GNE list retries
This variable defines the time the system should wait before reattempting to connect
to the NE via the list of GNEs. The default should be one minute (1 min).

12. Configure the SNMP proxy

If the SNMP Proxy has been installed, you can now activate it. Then configure and start
SNMP Proxy.

128 A50023-K1027-X040-02-76D1
Issue: 2 Issue date: July 2013
Installation Manual (IMN) Measures after commissioning

1. Open the SNMP Proxy Properties window.

Figure 49 “SNMP Proxy Properties” window

2. Select the tab SNMP Config.
3. Click on the button New.
4. In the Properties tab specify the:
• Username
• SNMP Version
• Authentication and Privacy (only relevant if SNMPv3 is used)
If Authentication and Privacy are used, it’s also necessary to specify the Authen-
tication and Privacy Passwords.

A50023-K1027-X040-02-76D1 129
Issue: 2 Issue date: July 2013
Measures after commissioning Installation Manual (IMN)

Figure 50 “New Principal” window

5. In the Access List tab configure the:
• Permission
• IP Address/Mask
6. In the Trap List tab, define if you want to allow traps and then specify the destination
IP. For trap communities the IP must be followed by the port number.
7. In the Inform List tab, define if you want to allow informs and specify the destination.

13. Configure the TCOA proxy

If the TCOA Proxy has been installed, follow the instructions in 4.4.8.4 Configuring
TCOA proxy external interface.

14. Synchronize the computer date and time

For event logging, all TNMS Core computers must have the same settings. Date and
time need to be taken from the server to the other computers and the clients have to
forward these settings to the network elements.

15. Start the TNMS Client

The login procedure is the same as for System Administration, however, you must login
using the new Administrator password, configured when you logged onto System
Administration for the first time.

130 A50023-K1027-X040-02-76D1
Issue: 2 Issue date: July 2013
Installation Manual (IMN) Measures after commissioning

16. Create the Network Plan

The network plan can now be created using TNMS Client. This must be done on the
basis of planning data (when installing the system the first time) or by migration of data
used in formerly software versions (in case of software updates).

17. Configure SSU-2000e Administration via TNMS Core (optional)

The Synchronization Supply Unit SSU-2000e from Symmetricom can be connected
with TNMS Core. With this connection, alarms are displayed in TNMS Current Alarm
Lists, and the LCT TimeCraft can be started by a double click on the SSU icon in TNMS
Core Client. To connect the SSU 2000e with TNMS Core, proceed as follow:
1. Create a SNMP Channel or add an NE to a existing one.
2. Add a Generic SNMP FM-CM in the Add NE option.
3. In the Init-Script tab choose SSU2000e from the drop down menu.
4. On the SNMP settings tab use the following settings:
• IP Address - Use the SSU IP address.
• Polling Interval - This is the polling interval for the SSU alarms.

g TNMS is not receiving any spontaneous alarm traps although it is configured in

SSU trap table. TNMS is always polling alarms according polling interval config-
ured in that SSU in DCN Management. The default value is 10 minutes. With this
it is normal behavior, that SSU alarms are visible in TNMS Alarm Log with a
delay of at most these 10 minutes.

• Specific Element Manager - Define your path, for example c:\Programs\Sym-

metricom\TimeCraft\start.bat.
• Check Use Specific Element Manager as Default EM.
5. On every TNMS Core Client machine you need to install Time Craft as the Element
Manager of SSU. Time Craft needs to be installed in every machine in the same path
that you defined as the Specific Element Manager. Using the earlier example you
always need to install Time Craft c:\Programs\Symmetricom\TimeCraft\.
To install it you have to create a batch file, called Start.bat with the following content:
c:
cd c:\Programs\Symmetricom\TimeCraft
start runSynCraftNT2k.bat

g Note that every TNMS Core Client must have an IP connection to the SSU.

6. Also some configurations are needed in the SSU. The Time Craft needs to be con-
figured. To do it proceed as follow:
• Choose New Connection.
• In the IP Address use the SSU IP Address.
• Create a User and a Password.
In the NE on the SNMP V2 parameters tab under Trap Reporting insert your
Netserver IP address.

18. Configure Windows Domain Authentication with Single Sign On (optional)

If you have configured an Active Directory and you want to enable Single Sign On refer
to the instructions in4.14 Active Directory configurations.

A50023-K1027-X040-02-76D1 131
Issue: 2 Issue date: July 2013
Measures after commissioning Installation Manual (IMN)

6.3 Routing settings for machines with multiple network

adapters
If one or more machines in your TNMS Core system have multiple network adapters (for
networking protocols in addition to TCP/IP), delays may occur in connection setup
between the various TNMS Core machines.
For example:
• computer A has one network adapter (for the LAN segment to computer B).
• computer B has two network adapters (one for the LAN segment to computer A and
one for an external LAN segment).
Because computer B has two network adapters, it also has two IP addresses.
When establishing communication with computer A, computer B transmits both IP
addresses. If the first IP address sent by computer B is the address for the common LAN
segment, communication can be established without any problems. But if the first IP
address sent by computer B is the address for the external LAN segment, and a gateway
computer with routing information is not available, timeout cycles result in delayed com-
munication.
The following connections may then be affected:

Connection Affected Task

Client > NetServer Starting the LCT application from a Client
Server > NetServer Communication with NetServers/NEs
Server > Standby Server Starting database replication
Server > Client Starting the Client or System Administration applications

Table 10 Affected connections

The problem can be solved by defining the sequence in which IP address information is
transmitted in the network settings for each machine as follows:
1. Opposite-click the icon My Network Places on your desktop. In the menu that
appears, select the item Properties.
2. In the Network and Dial-Up Connections window that appears, click Advanced on
the toolbar, and from the list that appears select Advanced Settings...
3. The Advanced Settings window is now displayed. In the Connections list, select
Local Area Connection. The list beneath (called Bindings for Local Area Connection)
shows the preferred order in which protocols are used.
4. Select the item Internet Protocol (TCP/IP) from the list and then click on the up arrow
on the right side of the window. Do this until Internet Protocol (TCP/IP) is the first
item in the list under File and Printer Sharing for Microsoft Networks.
5. Repeat the procedure in step four for all of the other clients listed in the window.
6. After changing the settings for all of the clients listed, click the tab Provider Order.
7. Select Microsoft Windows Network from the Network providers field, then click on
the up arrow on the right side of the screen to move it to the top of the list.
8. Click OK to save the changes and then reboot the computer.

132 A50023-K1027-X040-02-76D1
Issue: 2 Issue date: July 2013
Installation Manual (IMN) System expansion

7 System expansion

7.1 Adding clients

Up to 40 clients can be operated on one server simultaneously. If new clients are to be
added as part of system expansion, the same software version must be installed as
provided on existing clients.
Proceed as follows:
• Install and cable the new computers as described in Section 3.2.2.
• Install operating system as described in Section 4.3.
• Install the Client and/or System Administration software as described in Chapter 4.8.
• Test the system in accordance with the test cases described in the acceptance test
protocol. For more information, contact Nokia Siemens Networks Technical Sales.
• Enter the relevant details in the field test protocol and acceptance protocol.

7.2 Adding NetServers

Up to 10 NetServers can be operated on one server simultaneously. If new NetServers
are added as part of system expansion, the same software version must be installed as
provided on existing NetServers.
Proceed as follows:
• Install and cable the new computers as described in Section 3.2.2.
• Install operating system as described in Section 4.5.
• Install an OSI stack as described in Section 4.5.1.
Note that every NetServer must have its own specific NSAP address provided by
planning.
• Install the NetServer software as described in Chapter 4.5.
• Add the NetServer via in the "DCN Management" window in System Administration .
• Test the system in accordance with the test cases described in the acceptance test
protocol. For more information, contact Nokia Siemens Networks Technical Sales.
• Enter the relevant details in the field test protocol and acceptance protocol.

A50023-K1027-X040-02-76D1 133
Issue: 2 Issue date: July 2013
Abbreviations Installation Manual (IMN)

8 Abbreviations
CE Communauté Européenne

CORBA Common Object Request Broker Architecture

DAT Digital Audio Tape

DB Database

DCN Data Communication Network

EM Element Manager

EML Element Management Layer

EM-OS Element Manager Operations System

EMS Element Management System

FICON Fiber Connection

FTP File Transfer Protocol

GNE Gateway Network Element

GUI Graphical User Interface

IMN Installation Manual

LAN Local Area Network

LCT Local Craft Terminal

MDAC Microsoft Data Access Components

MIB Management Information Base

MSDE Microsoft SQL Server Desktop Engine

NE Network Element

NEC Network Element Controller

OGL Operator Guidelines

OSI Open System Interconnection

PDH Plesiochronous Digital Hierarchy

PLET Performance Log Export Tool

RAID Redundancy Array of Independent Disks

SDH Synchronous Digital Hierarchy.

SNMP Simple Network Management Protocol

SSL Secure Sockets Layer

TCOA TMF CORBA Agent

134 A50023-K1027-X040-02-76D1
Issue: 2 Issue date: July 2013
Installation Manual (IMN) Abbreviations

TCOM TMF CORBA Manager

TED Technical Description

TMF Telecommunication Management Forum

TNMS Telecommunication Network Management System

TP Termination Point

UNO Universal Network Object

WAN Wide Area Network

XML Extended Markup Language

A50023-K1027-X040-02-76D1 135
Issue: 2 Issue date: July 2013
 Installation Manual (IMN)

Index R
Routing settings 132

A S
Additional clients 133
Safety precautions
Additional NetServers 133
Antistatic mat 15
Antistatic mat 15
Electrostatic-sensitive devices 14
ESD symbol 14
B Grounding bracelet 14
Basic information Labeling 14
commissioning 11 Measuring equipment 15
Personnel requirements 11 Modules 14
Voltage 14
C Supplementary documentation
Field test protocols 13
CE conformity 13
Planning documents 13
Commissioning
Release notes 13
Basic information 11
System expansion
Final tasks 126
Additional clients 133
Additional NetServers 133
E
Electrostatic-sensitive devices 14 T
ESD symbol 14
TCOM
DCN management configuration 83
G EML server setup 77
Grounding bracelet 14 Third-party software
MS SQL Server 2005 54, 63, 67
I OSI stack 89
XML parser 53
Initial configuration
TNMS Core
TNMS-Core 126
Installation 27
Installation
Uninstalling 116
MS SQL Server 2005 54, 63, 67
TNMS-Core
OSI stack 89
Initial configuration 126
TNMS Core 27
XML parser 53
Installation\tPCI I/O card 46 U
Uninstalling
M TNMS Core 116
Measures after commissioning
Initial configuration 126 X
Routing settings 126 XML parser
Measuring equipment 15 Installation 53
Modules 14
MS SQL Server 2005
Installation 54, 63, 67

O
OSI stack
Installation 89

P
Protective measures 14

136 A50023-K1027-X040-02-76D1
Issue: 2 Issue date: July 2013