s7sfc en-EN

PRELIMINARY - DRAFT Commissioning Guide
White Paper – ROC Server Application

Title
ROC Server Application
Commissioning Guide
Date: Publishing Department:

May 2009 I IA AS CS2 PA
Intention
To operate and control a plant remotely from a Remote Operation Center, a special Remote
Operation Center Server (in the following ROC Server) is needed onsite at the plant. The
present White Paper can be helpful during configuration, commissioning and troubleshooting of
the ROC Server application.
NOTE: This White Paper is intended for use only during the ROC Server application phase
09/05/06 Page 1 of 77 I IA AS CS 2 PA
preliminary For internal use only V1.1
Content
1 Introduction .........................................................................................................................4
1.1 Plant Overview ......................................................................................................................4
1.2 Architecture of the ROC Server ............................................................................................5
2 Delivery condition / Integration premises - ROC Server .................................................6
2.1 Delivery condition ROC Server .............................................................................................6
2.1.1 Hardware...............................................................................................................................6
2.1.2 Software ................................................................................................................................6
2.2 Integration premises..............................................................................................................6
3 Configuration and commissioning - ROC Server ............................................................7
3.1 Basic settings during Windows Setup Wizard.......................................................................7
3.2 Basic settings in Windows 2003............................................................................................7
3.3 Windows User Administration .............................................................................................13
3.4 VM Ware Settings ...............................................................................................................15
3.5 Auto start of VMware Player and Sessions .........................................................................16
3.6 Security Settings .................................................................................................................17
4 Setup of VM Ware Sessions on the Host System ..........................................................19
4.1 Copy and adapt basic VM Ware session ............................................................................19
4.2 Configuration of the VM Session.........................................................................................22
5 Setup of the virtual OS Client System.............................................................................27
5.1 Basic settings in Windows XP.............................................................................................27
5.2 Windows User Administration .............................................................................................34
5.3 Security Settings .................................................................................................................37
6 Licensing ...........................................................................................................................39
6.1 PCS 7 OS Client Licensing .................................................................................................39
6.2 Windows Licensing on PCS 7 OS Server ...........................................................................41
7 Deploying the PCS 7 project files to the ROC Server ....................................................42
7.1 OS Client Application ..........................................................................................................42
7.2 WinCC AutoStart for OS Client ...........................................................................................54
8 Remote Terminal ...............................................................................................................55
8.1 RDP Configuration at the Remote Terminal PCs ................................................................55
8.1.1 Setup of RDP ......................................................................................................................55
8.2 TSAddin ..............................................................................................................................59
8.2.1 Setup of TSAddin on ROC PCs ..........................................................................................60
9 Remote Administration of ROC Server ...........................................................................61
9.1 Access Tools .......................................................................................................................61
9.1.1 Windows NetMeeting ..........................................................................................................61
9.2 ROC Server - Start-up procedure .......................................................................................74
9.3 ROC Server - Shutdown or Restart procedure ...................................................................74
9.4 VM Sessions – Manual Start/Stop procedure .....................................................................74
9.4.1 Manual Start/Stop of VM Session by access the Host system ...........................................74
9.4.2 Manual Start/Stop of VM Session with RDP connection .....................................................76
10 Backup and Restore .........................................................................................................77
10.1 Host System Backup ...........................................................................................................77
10.2 Host System Restore ..........................................................................................................77
10.3 VM Sessions Backup ..........................................................................................................77
10.4 VM Session Restore ...........................................................................................................77
1 Introduction
The ROC (Remote Operation Center) Server is a special Siemens industrial PC
installed at a remote site (plant) to allow multiple remote operation connections.
1.1 Plant Overview
Description:
The ROC server connects the Plant (local) to the Remote Operation Center.
Standard PCs act as Remote Terminals (RT) which connect to the ROC server via
Remote Desktop Protocol (RDP). Each RT, when connected, has full PCS7 OS Client
access to operate the plant.
You connect up to four RTs, depending on your requirements.
1.2 Architecture of the ROC Server
Description:
The ROC Server is a Siemens IL547x computer with Windows 2003 Server Operating
System. This environment is the host operating system for VM-Ware. Except for the
Automation License Manager software, no additional Siemens software is installed on
the VMware host.
VMware is used to create four independent virtual PC instances which are running in
parallel (guest operating systems).
The four instances behave like actual physical computers and use the hardware of the
host system. Each instance (VClient) utilizes an approved operating system for the
PCS 7 OS Client installation (see PCS 7 readme). For example, Windows XP
Professional SP2 for PCS 7 V 6.1 SP1
Each VClient has two virtual network cards (VNIC). This virtual network cards are
connected to the two, independent, virtual networks (VMNet x). All VClients are
connected to the related VMNets.
The VMNets are bridged through the physical network cards of the host PC to
establish the connections from the virtual network to the physical network. The physical
network cards of the host PC are only transparent gateways. No IP configuration is
necessary for it.
The TCP/IP communication from local terminal bus and the remote network directly
addresses the VNIC’s of the VClients.
Each VClient contains a PCS7 OS client and like any regular OS client gets process
data from the OS Server.
For remote connection, an RT is connected to one VClient by using Windows Remote

Desktop functionality using desktop shortcuts for ease of use.
2 Delivery condition / Integration premises - ROC Server
2.1 Delivery condition ROC Server

Delivery condition of an ROC Server for use with PCS 7 Vx
Depending on the used PCS 7 Version, the version of the installed operating system is
different. Please refer to PCS 7 documentation to see the released operating system of
the used PCS 7 version.
2.1.1 Hardware
Siemens Rack PC 547 x with RAID 1 System and physical memory expansion to 4 GB
DDR2 RAM.
Further information you will find in PCS 7 Catalog.
2.1.2 Software
Operating System: Windows Server 2003 (SysPrep) 1

VM Ware Player: Version 2.5.1
VM Ware Sessions: Windows XP SPx professional (SysPrep) 1

PCS 7 V6.x OS Client pre-installed or
PCS 7 V7.x OS Client pre-installed
2.2 Integration premises
• ROC Server: UPS2
• PCS 7 Project: Plant wide the same PCS 7 version must be

installed (PCS 7 Version 6.1 SP1)
• Remote Terminal PC: Operating System Windows XP or 2003 Server

RDP 5.1 or higher
NOTE: There are different RDP client versions depending on the operating system
with small changes in configuration and functionality.
Windows XP SP2 -> RDP Client 5.x
Windows 2003 Server -> RDP Client 6.x
1
After the first start of the system, the Windows Setup Wizard will start. Now the basic
parameters of the operating system will be set up (Company Name, License,
Computer name, Network settings).
2
To prevent disruption from power failure it is mandatory to back up ROC Server
power with a UPS. Power failures could cause unexpected system effects, loss
and corruption of data, and irreparable system and data conditions.
3 Configuration and commissioning - ROC Server

As delivered, the ROC Server is pre-installed
3.1 Basic settings during Windows Setup Wizard

During the initial start of the system, the Windows Setup Wizard will commence. As
with any new PC, basic parameters of the operating system are set up (Company
Name, License, Computer name, Network settings). Follow the screens and enter
configurations similar to chapter “4.1.2 Basic settings in Windows XP”.
3.2 Basic settings in Windows 2003

After the Windows Setup Wizard finished, Windows 2003 will start.
Now you have to configure the following settings:
NOTE: After you finished the system setup you have to reboot the PC station
Performance Options:
Start -> Settings -> Control Panel -> System -> Tab “Advanced” -> Performance
Settings ->Tab “Visual Effects” -> “Adjust for best performance”
Settings -> Tab “Advanced”
Set Processor scheduling to “Adjust for best performance of: Background services”
Set Memory usage to “Adjust for best performance of: Programs”
Settings ->Tab “Advanced” -> Virtual memory -> change
Change the virtual memory. Select “Custom size”, set 8192 MB and press Set
Network settings:
If the Terminal Bus and the Remote Network is the same network in your plant, you
have to disable the “LAN Connection #2 – Extern Bus”
Note: Logical connection names could be different. Disable the LAN Connection
#2 which is assigned to the Intel® PRO/1000 GT Desktop adapter
Start -> Settings-> Network Connections
Network settings, (TCP/IP):
These settings will be determined by your own company IT department or Control

System standards
Start -> Settings -> Network Connections -> select the connection you want to
configure and make a “double-click” on it.
Choose Tab “General” and open “Properties”
Select “Internet Protocol (TCP/IP) and open Properties.
Set the TCP/IP parameters corresponding to your Plant
Enable Remote Desktop:
You must enable Remote Desktop functionality to connect to the ROC Server via RDP.
Start -> Settings -> Control Panel -> System -> Tab “Remote”
3.3 Windows User Administration
If you create a new windows user, the system uses the default windows settings if you
log-in with the new user. Please adapt the system parameters and settings like
described in chapter 3 and make following, additional settings:
Set color schemes font sizes and Display settings
The settings for the color scheme font size and display can sometimes change
automatically when other programs are installed. Correct the settings if necessary.
Procedure:
1. Select the menu command Start > Settings > Control Panel > Display.
The "Display Properties" dialog box opens.
Color scheme:
1. Select the "Appearance" tab.
2. Make the following settings:
Select "Windows Classic" in the "Windows and Buttons" drop-down list.
Select "Windows Classic" in the "Color Scheme" drop-down list.
Click "Apply".
Click "Advanced".
The "Advanced Appearance" dialog box opens.
Select "Active Title Bar" in the "Item" drop-down list box.
Select the dark blue menu area in the "Color 1" list.
Click "OK".
Font size
1. Select "Normal" in the "Font Size" drop-down list.
Options
1. Click "Effects".
The "Effects" dialog box opens.
2. Disable the "Show window contents while dragging" check box.
3. Double-click "OK".
Display options and Screensaver

1. Select the "Settings" tab
Select the screen resolution (recommended for PCS 7: 1280x1024).
A higher resolution allows you to better utilize the display features of the PCS 7
software, e.g., for the online operation of faceplates from the libraries. Please
ensure that you have installed appropriate drivers and are using suitable
monitors.
Open the "Screen Saver" tab.
In the "Screen saver" area, select "[None]" from the drop-down list box.
In the "Monitor power" area, click the "Power..." button.
In the "Settings for Home/Office Desk power scheme" area, select "Never"
in all the drop-down list boxes.
Click "OK" to close the dialog box.
Auto login:
To start-up the system without user interaction you can configure the host system to
auto login.
NOTE: This is not mandatory on the host system. All necessary application starting as
service, without a user locked in.
Start -> Run -> “control userpasswords2”
Uncheck “User must enter a user name and password to use this computer” and press
ok. Afterwards another window opens. Here you have to configure the username and
password for the user which should be used for the auto login.
3.4 VM Ware Settings
Preferences:
Start VM Ware player to set up the basic parameters.
VMware Player -> Preferences:
Exit behavior -> select “Power off the virtual machine”

Web update -> un-check “Check the web for updates on startup”
3.5 Auto start of VMware Player and Sessions
The configuration for the auto start of the VMware player and the VM Sessions as
service in the operating system is set in the delivered condition.
The VMware Player must be installed under C:\Program Files\VMware.

All VM Sessions must be located under D:\VMSessions\VMn (n=1-n)
Under C:\VMWare_as_Service you will find the file Vmstart.cmd.

Open the file for editing by right click -> Edit
rem **********************************************************************************
rem ** Set Path to vmware.exe first, because of blanks at the
directory name **
set path=%path%;C:\Program Files\VMware\VMware Player
rem ** Start in the same window **
start vmplayer.exe -x "D:\VMSessions\VM1\VM1.vmx"
rem **********************************************************************************
Copy and replicate the highlighted line, depending on the number of VM Sessions for
your system. Replicate only the storage location (directory) and file name of the
highlighted file.
3.6 Security Settings
Port Number
To reach a higher level of security for the remote connection you can configure a
defined TCP Port for RDP connections. After this it is only possible to access the
remote PC by entering the IP address plus the related TCP port.
Start Registry Editor: Start -> Run -> “regedit”
Locate and then click the following registry subkey:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\
TerminalServer\WinStations\RDP-Tcp\PortNumber
On the Edit menu, click Modify, and then click Decimal.

Type the new port number, and then click OK.
Now you have to use IP Address plus TCP Port to access the remote PC via RDP
e.g.: 172.20.10.1:800
Port Number = 800
After you change the default Port of RDP (Port 3389), you have to enable this Port in
the Windows Firewall settings, if the Windows Firewall is activated.
Start -> Settings -> Control Panel -> Windows Firewall -> Tab “Exceptions”
Press “Add Port” and edit Port Parameters corresponding to you defined RDP Port.
Virus Scanner
It is suggested to use virus scanner which are approved for the used PCS 7 Version,
like Trend Micro Office Scan, Symantec AntiVirusTM or McAfee® VirusScan®
For Further information on approved versions, refer to related PCS 7 documentation.
Firewall
The Windows Firewall should be activated (ON) on the Host system (Windows 2003
Server).
Automatic Updates
The automatic update functionality of Windows must be deactivated.
4 Setup of VM Ware Sessions on the Host System

You have to configure the VMware sessions on the Windows 2003 Server host system.
In the delivered condition there is a base configured VM Ware session file folder
located in D:\Default_V6OSC on the Windows 2003 host system. This folder will be
used to create your VM Session files.
4.1 Copy and adapt basic VM Ware session

Create a folder D:\VMSessions. In this folder create as much subfolders as you have
VClients and named VMn, n=> 1 to n.
Copy all files located in D:\Default_V6OSC into each VMn folder
Rename the .vmx file to the VMn.vmx
Open the VMn.vmx file with Notepad and change the “displayName” to VMn
-> e.g. VM1
To startup the system, it is necessary to create a boot sequence for the virtual
operating systems. This sequence is realized by an individual boot delay of each
operating system inside of the VMware player.
To adapt the time for the boot delay and create a boot sequence of the virtual
operating systems, open the VMn.vmx file with Notepad and change the parameter “n”
of the entry: bios.bootDelay="n" (n=time[ms].
Suggested times for parameter “n” are:

VM1= 20000 ms
VM2= 120000 ms
VM3= 220000 ms
VM4= 320000 ms
4.2 Configuration of the VM Session

Open VM Ware Player -> select “Open” -> browse to the file location and open
VMn.vmx file
Select “I copied it” at the following Pop-Up window
After this the Windows XP Setup Wizard will start. Go on with Next
Accept the license agreement and go on with Next
If necessary adapt “Regional and Language Options” and go on with next
Type in company name or organization and go on with Next
Type in your Product Key and go on with Next

Note: The Product Key will be delivered by Siemens.
Adapt Date and Time Settings and go on with Next
For Networking Settings select “Typical settings” and go on with Next
Depending if you are using a Workgroup or a Computer Domain select the related
option
Completing the Windows Setup Wizard with Finish
5 Setup of the virtual OS Client System
5.1 Basic settings in Windows XP
Now you are configuring the virtual PC. The virtual PC act like a real, independent PC
station.
After the Windows Setup Wizard finished, Windows XP is starting.
Now execute following settings:
NOTE: After you finished the system setup you have to reboot the virtual PC station
Performance Options:
Settings ->Tab “Visual Effects” -> “Adjust for best performance”
Settings ->Tab “Advanced”
Set Processor scheduling to “Adjust for best performance of: Programs”
Set Memory usage to “Adjust for best performance of: Programs”
Start -> Settings-> Control Panel -> System -> Tab “Advanced” -> Performance
Settings ->Tab “Advanced” -> Virtual memory -> change
Change the virtual memory. Select “Custom size”, set 1024 MB and press Set
Network settings:
Start -> Settings-> Network Connections
Network settings, (TCP/IP):
These settings will be determined by your own company IT department or Control

System standards
Start -> Settings -> Network Connections -> select the connection you want to
configure and make a “double-click” on it.
Choose Tab “General” and open “Properties”
Select “Internet Protocol (TCP/IP) and open Properties.
Set the TCP/IP parameters corresponding to your Plant

Then click “Advanced” (each VM session must be unique).
Select Tab “WINS” and activate “NetBIOS”
If SIMATIC Shell Window pops up, select the network card which is connected to the
terminal bus.
Enable Remote Desktop:
You have to enable Remote Desktop functionality to connect to the ROC Server via
RDP.
Start -> Settings -> Control Panel -> System -> Tab “Remote”
5.2 Windows User Administration
If you create a new windows user, the system uses the default windows settings if you
log-in with the new user. Please adapt the system parameters and settings like
described in chapter 5 and make following, additional settings:
Set color schemes font sizes and Display settings
The settings for the color scheme font size and display can sometimes change
automatically when other programs are installed. Correct the settings if necessary.
Procedure:
1. Select the menu command Start > Settings > Control Panel > Display.
The "Display Properties" dialog box opens.
Color scheme:
1. Select the "Appearance" tab.
2. Make the following settings:
Select "Windows Classic" in the "Windows and Buttons" drop-down list.
Select "Windows Classic" in the "Color Scheme" drop-down list.
Click "Apply".
Click "Advanced".
The "Advanced Appearance" dialog box opens.
Select "Active Title Bar" in the "Item" drop-down list box.
Click "OK".
Font size
1. Select "Normal" in the "Font Size" drop-down list.
Options
1. Click "Effects".
The "Effects" dialog box opens.
2. Disable the "Show window contents while dragging" check box.
3. Double-click "OK".
Display options and Screensaver

1. Select the "Settings" tab
Select the screen resolution (recommended for PCS 7: 1280x1024).
A higher resolution allows you to better utilize the display features of the PCS 7
software, e.g., for the online operation of faceplates from the libraries. Please
ensure that you have installed appropriate drivers and are using suitable
monitors.
Open the "Screen Saver" tab.
In the "Screen saver" area, select "[None]" from the drop-down list box.
In the "Monitor power" area, click the "Power..." button.
In the "Settings for Home/Office Desk power scheme" area, select "Never"
in all the drop-down list boxes.
Click "OK" to close the dialog box.
Setup of user groups and users for PCS 7
For PCS 7, additional groups and user settings must be made, after setting up a new
user. Please refer to the related PCS 7 documentation for configuration and
authorization of PCS 7 systems.
Auto login:
To start-up the system without user interaction you can configure the host system to
auto login.
Start -> Run -> “control userpasswords2”
Uncheck “User must enter a user name and password to use this computer” and press
ok. Afterwards another window opens. Here you have to configure the username and
password for the user which should be used for the auto login.
Sharing the project folder
You must share the project folder D:\Project which will be the target for downloading
the OS Client project from the ES station.
Set all permissions for this folder.
Adapt Name of Desktop Symbol “My Computer”
It is helpful to change the name of Desktop Symbol “My Computer” into the VM
Session name so that it is clear which Virtual Machine you are looking at (when
troubleshooting).
5.3 Security Settings
Port Number
To reach a higher level of security for the remote connection you can configure a
defined TCP Port for RDP connections. After this it is only possible to access the
remote PC by entering the IP address plus the related TCP port.
Locate and then click the following registry subkey:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\TerminalServer\Win
Stations\RDP-Tcp\PortNumber
On the Edit menu, click Modify, and then click Decimal.

Type the new port number, and then click OK.
Now you have to use IP Address plus TCP Port to access the remote PC via RDP
e.g.: 172.20.10.1:800
Port Number = 800
After you change the default Port of RDP (Port 3389), you have to enable this Port in
the Windows Firewall settings, if the Windows Firewall is activated.
Press “Add Port” and edit Port Parameters corresponding to you defined RDP Port.
Virus Scanner:
Use virus scanner which are approved for the used PCS 7 Version, like Trend Micro
Office Scan, Symantec AntiVirusTM or McAfee® VirusScan®
Further information on approved versions, refer to the related PCS 7 documentation
Firewall:
PCS 7 6.x:
The Windows Firewall must be deactivated (OFF) on the VClients, because activation
of the windows firewall is not approved for PCS 7 6.x.
PCS 7 V7.x
The Windows Firewall should be activated (ON) on the VClients.
Automatic Updates
The automatic update functionality of Windows must be deactivated
6 Licensing
6.1 PCS 7 OS Client Licensing
The Automation License Manager application is installed on the Windows 2003 Server
host system and on each PCS 7 OS Client (virtual machine). This is needed to store
the PCS 7 OS Client licenses in a central place (host system). The Automation License
Manager on the PCS 7 OS Client gets the licenses over the internal VMNet from the
host system.
Install all PCS 7 OS Client Licenses and SFC Visu License for the VClients, central, on
the Windows 2003 server host system by using the Automation License Manager.
Further information you will find at the PCS 7 manual.
Adapt Automation License Manager on the Windows 2003 server host system
Edit -> Settings -> Tab “General”
Now open the Automation License Manager on the VClient and connect it to the host
system. This enable the function to access the license keys which are stored on the
host system. You have to proceed following steps on each VClient.
Edit -> “Connect Computer…”
Browse to the Computer name of the ROC Server host system, set the checkboxes
and go on with ok
Afterwards you will see the connected computer at the navigation window
6.2 Windows Licensing on PCS 7 OS Server
Check Windows 2003 licensing mode on your OS Server.

The licensing mode should be “Per Device or Per User”
Start -> Settings -> Control Panel -> Licensing
7 Deploying the PCS 7 project files to the ROC Server

Note: To integrate the ROC server into your existing plant, the PCS 7 project must be
an OS multiple-station system with client-server architecture.
7.1 OS Client Application

Inside of your existing PCS 7 project you must add additional OS client applications,
matching on your amount of virtual clients in the ROC Server.
Each VClient acts as a real PCS 7 OS Client.
NOTE: It is recommended to use Reference Clients with PCS 7 V7.0 and above.
Further information you will find in the PCS 7 manuals.
Insertion of an OS Client Application
• On the ES, in the component view of SIMATIC Manager, select the project
where you want to add the additional operator stations.
• Select the Insert > Station > SIMATIC PC Station command. A new SIMATIC
PC station is inserted into the selected project.
• Select the new SIMATIC PC station, select the menu command Edit > Object
Properties and enter the required name (such as “VM1”).
• Select the SIMATIC PC station in the component view and open HW Config by
double-clicking the "Configuration" object in the detail view. The hardware
configuration of the SIMATIC PC station opens
• If the hardware catalog is not visible, select the View > Catalog command to
open the hardware catalog.
• Under "SIMATIC PC Station > HMI" in the hardware catalog, select the
“WinCC Application Client” which will add the client to the window on the left.
• Select the menu command Station > Save
Enter destination path for OS clients
From the Simatic Manager Component View, Select OS Client Application -> right
mouse click -> Object Properties
Select Tab “Target OS” -> Search -> Network -> Browse the Network for the
destination folder of the related VClient.
When browsing for the Target OS, this destination folder, is it located on the VMn
computer at D:\Project
Generating and Downloading of Server Data
Select OS Server -> right mouse click -> Generate Server Data
Select OS Client Application -> right mouse click -> Assign OS Server
Select the check boxes of the OS servers whose server data you want to assign to the
OS Client
The program starts the server data download and opens the message dialog which
contains the progress bar.
Once the download operation has finished successfully, click "OK".
Assign the Standard Server for OS Client
Assign standard servers for the components "Alarms" and "SSM (Split Screen
Manager)" for OS clients.
• Open OS Client Application (which starts WinCC Explorer), Select the "Server
Data" editor in the WinCC Explorer tree view, and then select the Standard
Server command from the shortcut menu.
• Select the component entry in the "Symb. computer name" column.
• Select the standard server from the drop-down list box.
• Repeat steps for "Alarm", "SSM”.
Horn Editor
Configure the Horn editor similar to the configuration of your local OS Clients
Further information you will find in the PCS 7 manuals and WinCC online help.
Sound re-direction of PCS 7 audible alarms
To redirect the sound of the PCS 7 audible alarms in a proper way thru RDP, you have
to set up a global script which will be triggered by the log in of the WinCC user.
After you connect to the OS Client (VM Session) by RDP, you have to login the WinCC
operator. This will redirect the WinCC audible alarm to the Remote Terminal PC.
The redirection is only necessary after a restart of the ROC server, or a reboot of the
VMware session.
Setup the Global Script for Horn restart of OS Client:

Open OS Client Application (which starts WinCC Explorer), Select "Global Script" -> C-
Editor” in the WinCC Explorer tree view. This will open the Global C-Script editor.
Select Actions -> Global actions -> right mouse click -> new.
Insert following C-Script
Compile the script by using the framed button
Configure the trigger for the c-script by using the framed button
Select Tab “Trigger” -> choose “Tag” -> select “Add”

Then browse for the “Tag name”
Browse for the Internal tag: “@CurrentUserName” and press OK
Set the “Standard cycle” to “Upon change” by right mouse click
Save the new c-script function and leave the Global C-Script editor
Time Synchronization
If you use Time Synchronization in your project adapt it in each OS Client Project of
the VM Sessions.
OS Project editor
Adapt project parameters (Screen Resolution etc.) and run OS Project Editor once for
each OS Client at the VM Sessions
Download OS Client Project

From Simatic Manager, select OS Client Application -> right mouse click -> PLC ->
Download
7.2 WinCC AutoStart for OS Client
You have to configure the WinCC AutoStart at each VClient.
For adding your OS Client project to the WinCC AutoStart, go to
Start -> SIMATIC -> WinCC -> AutoStart
• Browse to the storage location of the OS Client project and select *.*mcp file.
• Set “Activate Project at Startup”
• Press “Add to AutoStart”
8 Remote Terminal
The Remote Terminal PCs are located at the central remote operation centre and used
to operate and control a plant remotely.
Each Remote Terminal PCs connecting directly to one virtual PCS 7 OS client of the
ROC server by RDP and allow to operate and control the plant like a regular OS client.
NOTE: The operator have to close an active RDP session to a VClient by using
“Disconnect”. If he use “Log Off” the WinCC application will shutdown.
8.1 RDP Configuration at the Remote Terminal PCs

To get remote access to the virtual OS Clients “Remote Desktop” by Microsoft will be
used in Version 5.1 or higher.
NOTE: There are different RDP client versions depending on the operating system
with small changes in configuration and functionality.

Windows 2003 Server -> RDP Client 6.x
8.1.1 Setup of RDP
The following setup shows RDP Client 6.x as an example
Open Remote Desktop

Start -> Programs -> Accessories -> Communications -> Remote Desktop Connection
Set IP Address plus TCP port of the VMware session where you want to connect to.
Adapt following Tabs depending on your system needs
8.2 TSAddin
TSAddin tool is used to generate an audible alarm, if RDP detects an loss of
broadband connection. If the RDP connection breaks down, the TSAddin will notify the
operator at the Remote Operation Center with an audible alarm.
The TSAddin uses the API interface of RDP. The sound signal is connected to the
visual signalization of RDP.
If RDP recognize a break in the communications, it tries to re-establish the connection
20 times and notifies the operator with a “connection lost” symbol and TSAddin plays
the sound. If the re-establishing fails, RDP generates a message. At this point the
connection must be re-connected manually.
“Connection lost symbol” of RDP
RDP message after 20 unsuccessful reconnects
If you acknowledge the RDP message with OK the connection must be re-establish
manually
8.2.1 Setup of TSAddin on ROC PCs
The TSAddin tool must be integrated on each Remote Terminal (RT) computer.
Create a folder D:\TSAddinSound and copy the *.*wav file, which is used as sound
annunciation for RDP connection loss, into it.
TSAddin consist of two files:
TSAddinSound.dll
Depending on your operating system you have to copy this to
C:\WINDOWS\system32 or C:\WINNT\system32
TSAddinSound.reg
Copy the file TSAddinSound.reg into D:\TSAddinSound.
Configure the *.*reg file: Select file -> right mouse-click -> edit
Adapt following parameters in the *.*reg file

“Name”: must be the storage location of the TSAddinSound.dll, depending on you
operating system.
“Soundfile”: must be the storage location of the *.*wav file, which is used as sound
annunciation for RDP connection loss
9 Remote Administration of ROC Server
9.1 Access Tools
3rd Party software solutions are available that allow Remote Administrators the ability to
connect to the ROC Server as a host Administrator. Examples of this include
PCAnywhere, Net Meeting, RealVNC, etc. This software can be installed on the ROC
Server (Windows Server 2003 host) to allow users to perform administrative functions
such as:
- Manual Start/Stop of VM Sessions
- Server Troubleshooting and Maintenance
9.1.1 Windows NetMeeting
Windows NetMeeting can be used for remote administration and is embedded into
by default.
The following chapter describes how to configure NetMeeting on the ROC
Server Windows Host system to start as a service and accept calls from a
remote administrator station automatically.
Further, this chapter describes how to configure NetMeeting on the remote
administrator station.
To use NetMeeting and Administrator account on the ROC Server is needed.
Basic Configuration of NetMeeting:
Start -> Run -> “conf”
Follow the wizard step by step and adapt basic settings:
Go on with Next
You have to set up “First name”, “Last name” and “E-mail address”
and go on with Next
Go on with Next
Select your type of network and Go on with Next
Go on with Next
Go on with Next
Go on with Next
Go on with Next
Press Finish to finish the basic setup wizard of NetMeeting
After you finish the wizard, NetMeeting opens
Now following station specific settings have to be made:
Configuration of NetMeeting on the ROC Server:
Select “Tools” -> Options -> Tab “Security and activate options seen below
Select “Tools” -> Options -> Remote Desktop Sharing
“Enable Remote Desktop Sharing on this computer” and start the wizard
Follow the wizard step by step and adapt settings:
Go on with Next
Go on with Next
Go on with Next
Press Finish to finish the basic setup wizard of NetMeeting
Close NetMeeting by selecting “Call” -> “Exit and activate Remote Desktop Sharing”
Firewall settings on the ROC Server
After you activate NetMeeting on the ROC Server you have to enable it at the Windows
Firewall settings.
Press “Add Program” and browse to “mnmsrvc.exe” locate in C:\Windows\system32.
Now the configuration of NetMeeting is done. NetMeeting now will start as a

background service and will accept calls automatically.
Configuration of NetMeeting on the Remote Administration Station:
Select “Tools” -> Options -> Tab “Security and activate options seen below
To connect remotely to the ROC Server for administrative work, enter Computer name
or IP address into the address field and press “Place Call”
IP Address or Computer name
9.2 ROC Server - Start-up procedure
Depending on your configuration (e.g. auto start for host system), the system starts up
automatically. The VMware sessions start up in a defined order one by one. Because
there are several tasks running in parallel and multiple VM sessions utilize significant
system resources, the full system startup takes time. Wait until each project is
activated. This could take several minutes.
If you restart the system after a loss of power, the start-up time increases, because the
RAID system has to synchronize both hard drives in the background. Check the RAID
status of the host system at the Intel® Matrix Storage Console: Start -> Programs ->
Intel® Matrix Storage Manager -> Intel® Matrix Storage Console.
If there are any problems during the start up of any individual session, wait until the
other sessions become active and reboot the concerned VM session again.
9.3 ROC Server - Shutdown or Restart procedure
The described procedure is mandatory for a proper shutdown/ restart of the whole
system.
First stop the OS Runtime of the OS Client application of each VClient. Then shut
down the VM Sessions one by one. After all VM Sessions are down, shut down /restart
the host system.
If you try to shut-down the host system while a VMware Session is running, you get
following message and the host system will not shut down:
In this situation your not able to connect do the VMware Session by RDP, as long as
you have not confirmed the VMware message on the Windows 2003 Server host
system.
9.4 VM Sessions – Manual Start/Stop procedure
9.4.1 Manual Start/Stop of VM Session by access the Host system
After gaining access to the Windows Server 2003 host via 3rd party Remote Access
software (Administrator account), you will see the host Desktop. Normally, all VM
Sessions (up to four) will be running and visible in the taskbar at the bottom of the
screen (minimized).
- Shutting down a VM Session from the host system.

Proper procedure must be followed to shut down a VM Session.
First, the OS Client must be deactivated using the EXIT button

on the second page of icons at the bottom of the OS Client
screen.
Second, the Windows XP session must be properly shutdown.
This is done by clicking the Windows START button, and then
choosing “Shutdown”. The Window for this session will then
disappear.
Alternatively, a user may choose to RESTART the VM
Session after the OS Client is deactivated. This is done by
choosing Restart instead of Shutdown. This function will then
do an orderly re-boot of Windows XP followed by the autostart
of the OS Client.
NOTE: Since the VM Sessions have a built-in boot delay
(each one different to allow sequential startup) the user can
abort the delay by touching any key while the timer is visible in
the lower right of the VM Session boot window.
- Manually Starting a VM Session that has been shut down.
Proper procedure must be followed to start up a VM Session.
Open VM Ware Player by clicking the VM Ware Player icon in
the Quick Launch area.
From the VM Ware Player Menu choose “Open”.
Browse to the directory of the VM Session you want to start,
then highlight the .VMX file and select Open. The session will
auto-start in a new window
Note: Since the VM Sessions have a built-in boot delay (each
one different to allow sequential startup) the user can abort the
delay by touching any key while the timer is visible in the lower
right of the VM Session boot window.
9.4.2 Manual Start/Stop of VM Session with RDP connection
It is not intended that an operator got access to the operating system. Therefore all
short key functions of Windows XP are disabled in WinCC. That results that the
operator only can operate WinCC.
If a restart of a virtual session is necessary, this should be done by and administrator.
Alternative, depending on your rules and requirements

• OS Client must be deactivated
• Windows XP session must be properly restarted (not shutdown)
- Alt+F4
- Start -> Settings -> Windows Security
NOTE: ROC Operator can not abort the boot delay via RDP
10 Backup and Restore
10.1 Host System Backup

After all basic system settings are made at the host operating system, it is suggested
to make an partition image of the system partition (C:\), before you install any
additional software like different kind of system utilities.
If you install additional software you can make another partition image of the system
partition (C:\) after the installation. You should store it in a separate folder and make a
backup copy at on an external device.
We have no recommended partition image software. You can use e.g. Symantec
Norton Ghost, Acronis True Image or others.
For more information on disk imaging, refer the documentation of your partition image
software.
10.2 Host System Restore
If the host operating system is corrupt or defect, use your latest system partition image
and restore it.
10.3 VM Sessions Backup

After you have made all settings and adaptations of a VM Session VMn, it is suggested
to save the complete VMn folder as a self-extracting WinZip file and store it in a
separate folder and additional store at on an external device. This can be used for
restoring individual VM Session files in the event of corruption in the future.
NOTE: WinZip is not included with the delivered ROC Server
If you do not use WinZip or other compressing tools, save a copy of each VMn folder in
a separate location. It is also good practice to save on a removable memory device
like a USB hard drive.
10.4 VM Session Restore
If you have a malfunctioning VMware session, this may be due to file corruption. From
the Windows 2003 Server delete the complete VMn folder contents and restore it from
your latest self-extracting *.*zip file.
If you do not use WinZip or other compressing tools, delete the complete VMn folder
and copy your latest backup VMn folder.

s7sfc en-EN

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

s7sfc en-EN

Hochgeladen von

Copyright:

Verfügbare Formate

PRELIMINARY - DRAFT Commissioning Guide

White Paper – ROC Server Application

Date: Publishing Department:

1.1 Plant Overview

1.2 Architecture of the ROC Server

For remote connection, an RT is connected to one VClient by using Windows Remote

2 Delivery condition / Integration premises - ROC Server

2.1 Delivery condition ROC Server

Operating System: Windows Server 2003 (SysPrep) 1

VM Ware Sessions: Windows XP SPx professional (SysPrep) 1

2.2 Integration premises

• ROC Server: UPS2

• PCS 7 Project: Plant wide the same PCS 7 version must be

• Remote Terminal PC: Operating System Windows XP or 2003 Server

3 Configuration and commissioning - ROC Server

3.1 Basic settings during Windows Setup Wizard

3.2 Basic settings in Windows 2003

Start -> Settings-> Network Connections

Network settings, (TCP/IP):

These settings will be determined by your own company IT department or Control

Set the TCP/IP parameters corresponding to your Plant

Enable Remote Desktop:

3.3 Windows User Administration

Set color schemes font sizes and Display settings

Display options and Screensaver

Start -> Run -> “control userpasswords2”

3.4 VM Ware Settings

Start VM Ware player to set up the basic parameters.

VMware Player -> Preferences:

Exit behavior -> select “Power off the virtual machine”

3.5 Auto start of VMware Player and Sessions

The VMware Player must be installed under C:\Program Files\VMware.

Under C:\VMWare_as_Service you will find the file Vmstart.cmd.

3.6 Security Settings

Start Registry Editor: Start -> Run -> “regedit”

Locate and then click the following registry subkey:

On the Edit menu, click Modify, and then click Decimal.

The automatic update functionality of Windows must be deactivated.

4 Setup of VM Ware Sessions on the Host System

4.1 Copy and adapt basic VM Ware session

Copy all files located in D:\Default_V6OSC into each VMn folder

Rename the .vmx file to the VMn.vmx

-> e.g. VM1

Suggested times for parameter “n” are:

4.2 Configuration of the VM Session

Select “I copied it” at the following Pop-Up window

Accept the license agreement and go on with Next

If necessary adapt “Regional and Language Options” and go on with next

Type in company name or organization and go on with Next

Type in your Product Key and go on with Next

Adapt Date and Time Settings and go on with Next

For Networking Settings select “Typical settings” and go on with Next

Completing the Windows Setup Wizard with Finish

5 Setup of the virtual OS Client System

5.1 Basic settings in Windows XP

Start -> Settings-> Network Connections

Network settings, (TCP/IP):

These settings will be determined by your own company IT department or Control

Set the TCP/IP parameters corresponding to your Plant

Select Tab “WINS” and activate “NetBIOS”

Enable Remote Desktop:

5.2 Windows User Administration

Set color schemes font sizes and Display settings

Adapt following parameters in the .reg file

First, the OS Client must be deactivated using the EXIT button