InstallNotesPIOptionsenUS
InstallNotesPIOptionsenUS
Parallel installation 2
3
SIMATIC HMI Licensing
Starting installation 6
Programming and Operating Manual
Displaying the installed
software 7
Modifying or updating
installed products 8
Repairing installed
products 9
Starting to uninstall 10
Installing updates and
support packages 11
Installing support packages
automatically 12
Installing and uninstalling
the migration tool 13
Installing and uninstalling
the TIA project server 14
06/2021
Legal information
Warning notice system
This manual contains notices you have to observe in order to ensure your personal safety, as well as to prevent
damage to property. The notices referring to your personal safety are highlighted in the manual by a safety alert
symbol, notices referring only to property damage have no safety alert symbol. These notices shown below are
graded according to the degree of danger.
DANGER
indicates that death or severe personal injury will result if proper precautions are not taken.
WARNING
indicates that death or severe personal injury may result if proper precautions are not taken.
CAUTION
indicates that minor personal injury can result if proper precautions are not taken.
NOTICE
indicates that property damage can result if proper precautions are not taken.
If more than one degree of danger is present, the warning notice representing the highest degree of danger will
be used. A notice warning of injury to persons with a safety alert symbol may also include a warning relating to
property damage.
Qualified Personnel
The product/system described in this documentation may be operated only by personnel qualified for the specific
task in accordance with the relevant documentation, in particular its warning notices and safety instructions.
Qualified personnel are those who, based on their training and experience, are capable of identifying risks and
avoiding potential hazards when working with these products/systems.
Proper use of Siemens products
Note the following:
WARNING
Siemens products may only be used for the applications described in the catalog and in the relevant technical
documentation. If products and components from other manufacturers are used, these must be recommended
or approved by Siemens. Proper transport, storage, installation, assembly, commissioning, operation and
maintenance are required to ensure that the products operate safely and without any problems. The permissible
ambient conditions must be complied with. The information in the relevant documentation must be observed.
Trademarks
All names identified by ® are registered trademarks of Siemens AG. The remaining trademarks in this publication
may be trademarks whose use by third parties for their own purposes could violate the rights of the owner.
Disclaimer of Liability
We have reviewed the contents of this publication to ensure consistency with the hardware and software
described. Since variance cannot be precluded entirely, we cannot guarantee full consistency. However, the
information in this publication is reviewed regularly and any necessary corrections are included in subsequent
editions.
Automatic installation
A description of automated installation is available on the product DVD in the directory
"Documents\Readme\<Language directory>".
Parallel use
If the term "Combo" appears in the name or license key of the software after installation, the
use of the following products/versions is permitted in accordance with paragraph 4.3 of the
General Terms and Conditions (see also setup text):
• With the license "STEP 7 Professional Combo": older versions of STEP 7 (STEP 7
Professional 2006 - STEP 7 Professional V17)
• With the license "WinCC V17 Comfort Combo": WinCC flexible 2008 Standard
• With the license "WinCC V17 Advanced Combo": WinCC flexible 2008 Advanced
Availability of licenses
The licenses for the products of the TIA Portal are usually supplied on an installation data
medium.
Before you uninstall the TIA Portal, you must transfer and back up the licenses still required.
Use the Automation License Manager for this purpose.
Note
For additional information on how to manage your licenses with the Automation License
Manager , refer to the documentation supplied with the Automation License Manager .
See also
Notes on the system requirements (Page 39)
Starting installation (Page 59)
Displaying the installed software (Page 63)
Modifying or updating installed products (Page 65)
Repairing installed products (Page 67)
Starting to uninstall (Page 69)
Installation log (Page 57)
Introduction
You require a License Key to license the following STEP 7 editions:
• STEP 7 Basic
• STEP 7 Professional
You can install the corresponding License Key for STEP 7 using the
Automation License Manager after the installation has been completed.
Note
The licensee also recognizes that the software (SW) from the Microsoft Corporation or
subsidiaries contains licensed software. The licensee hereby agrees to be bound by and
comply with the terms of the attached license agreement between Microsoft SQL Server and
End User.
Licenses
The following licenses with the corresponding License Keys are available:
• STEP 7 Basic
• STEP 7 Professional
• STEP 7 Professional Combo
• WinCC Basic
• WinCC Comfort
• WinCC Comfort Combo
• WinCC Advanced
• WinCC Advanced Combo
• WinCC Professional
• WinCC Professional Combo
• WinCC Unified Comfort Engineering
• WinCC Unified PC Engineering
• WinCC RT Advanced
• WinCC RT Professional
• WinCC Unified PC Runtime
WinCC Runtime
See also
Handling licenses and license keys (Page 31)
3.3.1 Logging
Logging
You have two options for logging your data in WinCC Unified:
• File-based logging
• Database-based logging
File-based logging
File-based logging allows you to log up to 5000 logging tags in an SQL Lite database.
Requirement
WinCC Unified Comfort Panel:
• You need a WinCC Unified Engineering System (ES) license for configuring.
• No license is required for logging.
WinCC Unified PC:
• You need a WinCC Unified Engineering System (ES) license for configuring.
• You need a WinCC Unified Runtime (RT) license for logging.
Licensing
To log up to a maximum of 5000 logging tags you need one or more licenses depending on
the number of tags to be logged. To do this, refer to the licenses in the table below.
Upgrade
You do not need an upgrade license for logging when you upgrade the system.
Trial
If you do not have a valid license, you can configure the logging tags in trial mode.
Database-based logging
Database-based logging allows you to log all logging tags up to the high limit in an MS SQL
database.
Requirement
WinCC Unified Comfort Panel:
• Not available
WinCC Unified PC:
• You need a WinCC Unified Engineering System (ES) license for configuring.
• You need a WinCC Unified Runtime (RT) license for logging.
Licensing
Besides the functionality, database-based logging also includes an MS SQL server. Therefore,
you need the "WinCC Unified Database Storage" license.
You also need one or more license(s) according to the number of tags to be logged. To do
this, refer to the licenses in the table below.
File-based or database-based licenses
The license(s) required for the number of tags to be logged can be found in the table below:
Upgrade
Depending on the MS SQL server, an upgrade license for WinCC Unified Database Storage
may be required when upgrading the system.
Trial
No trial mode is available for database-based logging.
Parameter sets
Requirement
WinCC Unified Comfort Panel:
• You need a WinCC Unified Engineering System (ES) license for configuring.
WinCC Unified PC:
• You need a WinCC Unified Engineering System (ES) license for configuring.
• You need a WinCC Unified Runtime (RT) license for use in runtime.
Licensing
To use parameter sets on a Runtime PC, you need a license:
Upgrade
The license is version dependent and requires the corresponding upgrade license for the
upgrade.
Trial
If you do not have a valid license, you can configure the parameter sets in trial mode.
3.3.3 Client
Licensing
For remote access, you need a license depending on the number and type of accesses. The
required license is listed in the table below:
Upgrade
The license is version independent and does not require any upgrade to a new version.
Trial
If you do not have a valid license, you can configure the client in trial mode.
3.3.4 Reporting
Reporting
Requirement
WinCC Unified PC:
• You need a WinCC Unified Engineering System (ES) license for configuring.
• You need a WinCC Unified Runtime (RT) license for use in runtime.
Licensing
You do not need a license to configure the Reporting option.
License
The option license "Configuration and manual Report Execution" is included in the WinCC
Unified ES and WinCC Unified RT licenses.
You need the "WinCC Unified Report Execution" license for automatic execution of Reporting
(time, event).
Upgrade
The license is version dependent and requires the corresponding upgrade license for the
upgrade.
Trial
If you do not have a valid license, you can configure the Reporting option in trial mode.
3.3.5 Openness
Openness
Requirement
WinCC Unified PC:
• You need a WinCC Unified Engineering System (ES) license for configuring.
• You need a WinCC Unified Runtime (RT) license for use in runtime.
Licensing
No license is required for the Openness option.
Upgrade
No license is required for the upgrade.
Trial
If you do not have a valid license, you can configure the Openness option in trial mode.
Unified Collaboration
Requirement
WinCC Unified Comfort Panel:
• You need a WinCC Unified Engineering System (ES) license for configuring.
WinCC Unified PC:
• You need a WinCC Unified Engineering System (ES) license for configuring.
• You need a WinCC Unified Runtime (RT) license for use in runtime.
Licensing
You do not need a license to configure the Unified Collaboration option.
You need a license for each device involved to use the Unified Collaboration option.
Upgrade
The license is version dependent and requires the corresponding upgrade license for the
upgrade.
Trial
If you do not have a valid license, you can configure the Unified Collaboration option in trial
mode.
3.3.7 Audit
Audit
Requirement
WinCC Unified PC:
• You need a WinCC Unified Engineering System (ES) license for configuring.
• You need a WinCC Unified Runtime (RT) license for use in runtime.
Licensing
You do not need a license to configure the Audit option.
You need a license to use the Audit option in runtime.
License
You need the "WinCC Unified Audit Basis" license for the Audit option in WinCC Runtime.
Upgrade
The license is version dependent and requires the corresponding upgrade license for the
upgrade.
Trial
If you do not have a valid license, you can configure the Audit option in trial mode.
3.4.1 Calendar
Calendar
Requirement
WinCC Unified PC:
• You need a WinCC Unified Engineering System (ES) license for configuring.
• You need a WinCC Unified Runtime (RT) license for the Calendar PI option in Runtime.
Licensing
You do not need an additional license to configure the Calendar PI option.
You need the following licenses to use the Calendar PI option in Runtime:
License Description
WinCC Unified Calender Base Per server:
• Three independent basic calendars
• Unlimited number of derived calendars
• Unrestricted use of the option
• Version-based
Example:
WinCC Unified Calender Base + WinCC Unified Calender Extension (1) → 3 + 1 = 4
Upgrade
When upgrading to the next higher version you need a WinCC Unified Calender Base Upgrade
license.
On the other hand, the WinCC Unified Calender Extension (1) license is version-independent.
Trial
If you do not have a valid license, you can configure the Calendar PI option in trial mode.
Performance Insight
Requirement
WinCC Unified PC:
• You need a WinCC Unified Engineering System (ES) license for configuring.
• You need a WinCC Unified Runtime (RT) license for the Performance Insight PI option in
Runtime.
Licensing
You do not need any additional license to configure the Performance Insight PI option.
You need the following licenses to use the Performance Insight PI option in Runtime:
License Description
WinCC Unified Performance Per server:
Insight Base
• Three analyzed plant objects
• Unrestricted use of the option
• Version-based
WinCC Unified Performance • 10 additional analyzed plant objects
Insight Extension (10)*
WinCC Unified Performance • 30 additional analyzed plant objects
Insight Extension (30)*
WinCC Unified Performance • 100 additional analyzed plant objects
Insight Extension (100)*
WinCC Unified Performance • 300 additional analyzed plant objects
Insight Extension (300)*
Example:
WinCC Unified Performance Insight Base + WinCC Unified Performance Insight Extension(10)
→ 3 + 10 = 13
WinCC Unified Performance Insight Base + WinCC Unified Performance Insight Extension (10)
+ WinCC Unified Performance Insight Extension (30) → 3 + 10 + 30 = 43
Upgrade
When upgrading to the next higher version you need a WinCC Unified Performance Insight
Base Upgrade license.
On the other hand, the WinCC Unified Performance Insight Extension licenses are version-
independent.
Trial
If you do not have a valid license, you can configure the Performance Insight PI option in trial
mode.
3.4.3 Sequence
Sequence
Requirement
WinCC Unified PC:
• You need a WinCC Unified Engineering System (ES) license for configuring.
• You need a WinCC Unified Runtime (RT) license for the Sequence PI option in Runtime.
Licensing
You do not need an additional license to configure the Sequence PI option.
You need the following licenses to use the Sequence PI option in Runtime:
License Description
WinCC Unified Sequence Base Per server:
• 3 concurrent sequences
• Unrestricted use of the option
• Version-based
WinCC Unified Sequence Exten- • 5 additional concurrent sequences
sion (5)*
Example:
WinCC Unified Sequence Base + WinCC Unified Sequence Extension(5) → 3 + 5 = 8
WinCC Unified Sequence Base + WinCC Unified Sequence Extension (5) + WinCC Unified
Sequence Extension (5) → 3 + 5 + 5 = 13
Upgrade
When upgrading to the next higher version you need a new WinCC Unified Sequence Base
Upgrade license.
On the other hand, the WinCC Unified Sequence Extension (5) license is version-independent.
Trial
If you do not have a valid license, you can configure the Sequence PI option in trial mode.
Line Coordination
Requirement
WinCC Unified PC:
• You need a WinCC Unified Engineering System (ES) license for configuring.
• You need a WinCC Unified Runtime (RT) license for Line Coordination PI option in Runtime.
Licensing
You do not need an additional license to configure the Line Coordination PI option.
You need the following licenses to use the Line Coordination PI option in Runtime:
License Description
WinCC Unified Line Coordination Per server:
Base
• 3 units
• Unrestricted use of the option
• Version-based
WinCC Unified Line Coordination • 5 units
Extension (5)*
WinCC Unified Line Coordination • 10 units
Extension (10)*
WinCC Unified Line Coordination • 50 units
Extension (50)*
Example:
WinCC Unified Line Coordination Base + WinCC Unified Line Coordination Extension (5)
→3+5=8
WinCC Unified Line Coordination Base + WinCC Unified Line Coordination Extension (5) +
WinCC Unified Line Coordination Extension (10)
→ 3 + 5 + 10 = 18
Upgrade
When upgrading to the next higher version you need a new WinCC Unified Line Coordination
Base Upgrade license.
On the other hand, the WinCC Unified Line Coordination Extension licenses are version-
independent.
Trial
If you do not have a valid license, you can configure the Line Coordination PI option in trial
mode.
Introduction
You need a valid License Key in each case to use STEP 7 Basic, STEP 7 Professional as well as
WinCC Engineering System, options for WinCC Engineering System and WinCC Runtime.
NOTICE
Destruction of license keys by copying
A License Key cannot be copied. The copy protection prevents the License Keys from being
copied. If you attempt to copy a License Key, it will be destroyed.
Trial License
If you start the TIA Portal without a valid License Key, the system alerts you that you are
working in non-licensed mode. You can activate a trial license once. The trial license expires
after 21 days.
When the trial license has expired, the TIA Portal only runs with restrictions. For the full
version of the TIA Portal, you need to purchase the corresponding license.
Note
Following installation, always keep the original storage location of the License Keys.
Note
Following installation, always keep the original storage location of the License Keys.
NOTICE
Destruction of license keys on PCs
First, uninstall all License Keys if you do one of the following:
• Format the hard disk
• Compress the hard disk
• Restore the hard disk
• Start an optimization program that moves fixed blocks
• Install a new operating system
Read the description of Automation License Manager ("Start > Siemens Automation >
Documentation"). Observe all warnings and notices.
NOTICE
Destruction of license keys on non-PC-based HMI devices
License keys transferred as a result of backup/restore operations are destroyed in the case of
the following HMI devices:
• 270 series
• 370 series
Carry out the following before beginning a restore operation:
• Use the Automation License Manager and ProSave to check if there are License Keys on
the HMI device.
• Transfer the existing License Keys from the HMI device.
After restoring has been carried out, transfer the License Keys back to the HMI device.
Defective license
A license is defective in the following cases:
• If the License Key is no longer accessible at the storage area.
• If the License Key disappears during its transfer to the destination drive.
Note
If you reset the system date to an earlier time, all licenses are invalidated.
You can use the Automation License Manager to repair the defective license. Use the
"Restore" function or the "Restore wizard" of the Automation License Manager for this
purpose. Contact Customer Support to restore them. You can find more detailed information
on the Internet: http://support.automation.siemens.com
(https://support.industry.siemens.com/cs/de/en/)
Note
Runtime can also be operated without errors if the license is missing or defective. The system
alerts you at brief intervals that you are working in non-licensed mode.
See also
Licensing STEP 7 and WinCC (Page 10)
License key
In order to license non-PC-based HMI devices with License Keys, the
"SIMATIC HMI License Manager Panel Plugin" add-on is needed.
WinCC Setup installs this add-on by default. You open the License Manager Panel Plugin in
the Automation License Manager with the "Edit > Connect Target System > Connect HMI
Device" menu command.
If WinCC is not installed, an installation of ProSave 7.2 or higher is required.
Non-licensed mode
Runtime add-ons can be used for a short time without restrictions without a valid license.
Non-licensed mode is indicated every 10 minutes by a window, which you must
acknowledge.
License key
With PC-based HMI devices, you require a license key for the following:
• WinCC Runtime with 128 tags, for example.
• WinCC add-ons
You can install the license key for WinCC Runtime during the installation of WinCC. You
transfer licenses for the WinCC add-ons after installation with the Automation License
Manager.
Note
Productive operation of the software is only permitted with a valid Certificate of License
which specifies the respective version.
Non-licensed mode
WinCC Runtime and the Runtime add-ons can be used freely without license. Non-licensed
mode is indicated every 10 minutes by a window, which you must acknowledge.
Introduction
If you are using WinCC Runtime in an Asian language, a dongle is used additionally for the
validation of the required license. The dongle comes in the form of a certified USB stick
together with the required license key for WinCC Runtime Professional Asian. The license key
is stored on the certified USB flash drive.
Information system
The information system for PC-CP available in STEP 7 describes the full scope of STEP 7
functions. You should therefore remember that the functions are restricted to the
configuration of the previously listed device groups.
See also
Notes on licenses (Page 9)
Starting installation (Page 59)
Displaying the installed software (Page 63)
Modifying or updating installed products (Page 65)
Repairing installed products (Page 67)
Starting to uninstall (Page 69)
Hardware/software Requirement
Processor Intel® Core™ i3-6100U, 2.30 GHz
RAM 8 GB
Hard disk S-ATA with at least 20 GB available space
Network From 100 Mbit
Screen resolution 1024 x 768
Operating systems * Windows 10 (64-bit)
• Windows 10 Home Version 1909 **
• Windows 10 Home Version 2004 **
• Windows 10 Home Version 2009/20H2 **
• Windows 10 Professional Version 1909
• Windows 10 Professional Version 2004
• Windows 10 Professional Version 2009/20H2
• Windows 10 Enterprise Version 1909
• Windows 10 Enterprise Version 2004
• Windows 10 Enterprise Version 2009/20H2
• Windows 10 Enterprise 2016 LTSB
• Windows 10 Enterprise 2019 LTSC
Windows Server (64-bit)
• Windows Server 2016 Standard (full installation)
• Windows Server 2019 Standard (complete installation)
* Including all security updates up to Microsoft Security Bulletin Summary for March 2021
(MS21-MAR). For more detailed information on operating systems, refer to the help on
Microsoft Windows or the Microsoft Web site.
** Only for Basic editions
Some protocols might also support additional Windows versions. You can find more
information in the product-specific requirements or check the compatibility with the
compatibility tool. The compatibility tool is available on the Internet at
https://support.industry.siemens.com/kompatool/pages/main/index.jsf?
(https://support.industry.siemens.com/kompatool/pages/main/index.jsf?).
Recommended PC hardware
The following table shows the recommended hardware requirements:
Hardware/software Requirement
Computer SIMATIC FIELD PG M6 Comfort or higher (or comparable PC)
Processor Intel® Core™ i5-8400H (2.5 to 4.2 GHz; 4 cores + Hyper-threading; 8 MB Smart Cache)
RAM 16 GB or more (32 GB for large projects)
Hard disk SSD with at least 50 GB available memory space
Network 1 GBit (for multiuser)
Monitor 15.6" Full HD Display (1920 x 1080 or higher)
Operating system VMware vSphere Hy- VMware Work- VMware Player Microsoft Hy-
pervisor (ESXi) station per-V
Windows Server 2019 Standard - - - x
(complete installation)
Windows 10 Professional Version x x x -
1909, 2004 and 2009/20H2
Windows 10 Enterprise Version x x x -
1909, 2004 and 2009/20H2
Windows 10 Enterprise 2016 LTSB x x x -
Windows 10 Enterprise 2019 LTSC x x x -
The following guest operating systems are recommended for installation within the selected
virtualization platform:
Operating system VMware vSphere Hy- VMware Work- VMware Player Microsoft Hy-
pervisor (ESXi) station per-V
Windows Server 2016 Standard (full x - - x
installation)
Windows Server 2019 Standard x - - x
(complete installation)
Windows 10 Professional Version x x x x
1909, 2004 and 2009/20H2
Windows 10 Enterprise Version x x x x
1909, 2004 and 2009/20H2
Windows 10 Enterprise 2016 LTSB x x x x
Windows 10 Enterprise 2019 LTSC x x x x
Note
• The same hardware requirements apply to the host operating system as for the respective
TIA products.
• The plant operator must ensure that sufficient system resources are available for the host
operating systems.
• The hardware certified by the manufacturers is recommended for the use of HyperV server
and ESXi.
• When you use Microsoft Hyper-V, accessible stations cannot be displayed.
Note
Make sure that your virus scanner and its databases are always up-to-date.
See also
Notes on licenses (Page 9)
Starting installation (Page 59)
Checking availability of updates and support packages and installing them (Page 71)
Displaying the installed software (Page 63)
Modifying or updating installed products (Page 65)
Repairing installed products (Page 67)
Starting to uninstall (Page 69)
Uninstalling WinCC
If you have already installed an update for WinCC Unified V16 and want to install WinCC V17,
proceed as follows:
1. Open the Control Panel.
2. Start the uninstallation of SIMATIC WinCC Unified PC V16.0 UPDx.
3. When selecting the components, select "SIMATIC WinCC Update 16.0 UPDx" for
uninstallation.
4. After completing this uninstallation, uninstall all desired components of WinCC V16 via the
installation medium.
The information is contained in the readme under "Important notes (WinCC Unified)".
Hardware/software Requirement
Processor type Intel Core i3
RAM 4 GB
Free hard disk space 10 GB, 8 GB CF
Note
Number of supported clients and connections
Desktop operating systems support a maximum of 5 clients. In server operating systems,
more than 5 clients can connect to the server.
Windows limits the number of incoming connections on desktop operating systems to 20.
This limits the number of possible accesses to runtime.
Compatible browsers
Ports
When a Windows firewall is used, the installation routine of WinCC Unified Runtime sets up
the following ports:
• HTTP: 80
• HTTPS: 443
• TIA administrator: 8888
If your system uses a different firewall solution, make sure the ports are set up accordingly.
Virtualization
You can install the "SIMATIC WinCC Runtime Unified" software package on a virtual machine.
For this purpose, use one of the following virtualization platforms:
• VMware vSphere Hypervisor (ESXi) 6.7 (or higher)
• VMware Workstation 12.5.5 and VMware Workstation 15.5.0 (or higher)
• VMware Player 12.5.5 and VMware Player 15.5.0 (or higher)
• Microsoft Hyper-V Server 2019
In a virtualization platform, all approved operating systems can be used as host operating
system.
Note
• Note that terminal and PLC networks must be separated on the host system by using
separate network adapters (dedicated, physically separated network adapters).
• The same hardware requirements apply to the host operating system as for the respective
TIA products.
• The plant operator must ensure that sufficient system resources are available for the host
operating systems.
• The hardware certified by the manufacturers is recommended for the use of HyperV server
and ESXi.
Note
If you are using an anti-virus scanner, make sure that the computer has sufficient system
resources.
Note
Microsoft SQL for Unified PC
• WinCC Unified PC uses SQLite as the default database type. To use Microsoft SQL, the
system provides an installation option with a setup package. Logging with SQLite is not
possible after the installation of Microsoft SQL.
Existing SQLite files are retained, but they cannot be accessed in runtime.
• No backup can be created for SQLite.
• Microsoft SQL Server 2017 is used as of TIA Portal V17. SQL Management Studio is no
longer part of the Microsoft SQL Server installation package and is therefore not included
in the TIA Portal installation. You can install SQL Management Studio separately if needed.
Contents
A new WinCC SQL 2017 instance is installed with the installation of WinCC V17.
If you have already installed a version of WinCC Runtime Professional, you must either
• first install WinCC Runtime Professional V17, or
• uninstall older instances of "WINCC" on the SQL Server before you install WinCC
Professional V16.
Note
By removing WinCC Runtime Professional or WinCC Professional you do not remove the
instance of the SQL server.
6. In the "Select Instance" dialog, select the "WINCC" instance and click "Next".
7. In the "Select Features" dialog, click "Select All" and then "Next".
8. In the "Removal Rules" dialog, click "Next".
9. In the "Ready to Remove" dialog, click "Remove".
10.After removal is complete, click "Close" in the "Complete" dialog.
The procedure for uninstalling an older version of the SQL server instance is similar.
Introduction
You can install the TIA Portal Teamcenter Gateway as follows:
• Together with the installation of the TIA Portal
Note
Administrator rights are required for the server installation.
Note
If TCCS was installed as "standalone", you must also install "Microsoft Visual C++ 2013 –
Redistributable". This ensures that you can establish a connection between TIA Portal and
TIA Portal Teamcenter Gateway.
Note
• After a reinstallation or a restart, check whether a connection is available from
FCC/FMS (FileClientCache/FileManagementSystem) to the "Teamcenter Server 11.2 or
higher".
• After a reinstallation or a restart, check the registry key. You can find additional
information on checking the registry key in the "TIA Portal Teamcenter Gateway" online
help in the section Installing and uninstalling TIA Portal Teamcenter Gateway" >
"Checking the installation of TIA Portal Teamcenter Gateway".
• After a re-installation or restart, check whether you can save an item type in
Teamcenter and if you can add a dataset to the item revision. Additional information
on saving element types is available in the "TIA Portal Teamcenter Gateway" online
help in the chapter "Managing TIA Portal projects with TIA Portal Teamcenter Gateway"
in the section "Saving a TIA Portal project as new item in Teamcenter".
• After a reinstallation or a restart, check that a data transfer from Teamcenter Rich
Application Client to the Teamcenter server is possible.
• The supplied data model consisting of several files must be installed on the Teamcenter
server.
Installation path
Do not use any UNICODE characters (for example, Chinese characters) in the installation
path.
Antivirus programs
During the installation, read and write access to installed files is necessary. Some antivirus
programs block this access. We therefore recommend that you disable antivirus programs
during the installation of the TIA Portal Teamcenter Gateway and enable them again
afterwards.
See also
Notes on licenses (Page 9)
Starting installation (Page 59)
Checking availability of updates and support packages and installing them (Page 71)
Displaying the installed software (Page 63)
Modifying or updating installed products (Page 65)
Repairing installed products (Page 67)
Starting to uninstall (Page 69)
Requirement
• Hardware and software of the programming device or PC meet the system requirements.
• You have administrator privileges on your computer.
• All running programs are closed.
Procedure
To install the software packages, follow these steps:
1. Insert the installation medium in the relevant drive.
The setup program starts automatically unless you have disabled Autostart on the
programming device or PC.
2. If the setup program does not start up automatically, start it manually by double-clicking the
"Start.exe" file.
The dialog for selecting the setup language opens.
3. Choose the language in which you want the setup program dialogs to be displayed.
4. To read the information on the product and installation, click "Read Notes" or "Installation
Notes".
The help file containing the notes opens.
5. Once you have read the notes, close the help file and click "Next".
The dialog for selecting the product languages opens.
6. Select the languages for the product user interface, and click "Next".
Note
"English" is always installed as the basic product language.
8. If you want to create a shortcut on the desktop, select the "Create desktop shortcut" check
box.
9. Click "Browse" if you want to change the target directory for the installation.
Note
Please note the following:
• The length of the installation path must not exceed 89 characters.
• You can only change the installation path if no other product from the software
package which you intend to install, has been installed, yet.
• To increase security, select a directory that is protected by administrative rights as the
target directory.
10.Click "Next".
The dialog for the license terms opens.
11.To continue the installation, read and accept all license agreements and click "Next".
If changes to the security and permission settings are required in order to install the TIA
Portal, the security settings dialog opens.
12.To continue the installation, accept the changes to the security and permissions settings,
and click "Next".
The next dialog displays an overview of the installation settings.
13.Check the selected installation settings. If you want to make any changes, click "Back" until
you reach the point in the dialog where you want to make changes. Once you have
completed the desired changes, return to the overview by clicking on "Next".
14.Click "Install".
Installation is started.
Note
If no license key is found during installation, you have the chance to transfer it to your PC.
If you skip the license transfer, you can register it later with the Automation License
Manager.
Following installation, you will receive a message indicating whether the installation was
successful.
15.It may be necessary to restart the computer. If this is the case, select the "Yes, restart my
computer now.". Then click "Restart".
16.If the computer does not reboot, click "Exit".
Result
The TIA Portal along with the products and licenses you have ordered and the Automation
License Manager have been installed on your computer.
See also
Installation log (Page 57)
Notes on the system requirements (Page 39)
Notes on licenses (Page 9)
Displaying the installed software (Page 63)
Modifying or updating installed products (Page 65)
Repairing installed products (Page 67)
Starting to uninstall (Page 69)
Procedure
To display an overview of the software installed, follow these steps:
1. Click "Installed software" in the "Help" menu.
The "Installed software" dialog opens. You will see the installed software products in the
dialog. Expand the entries to see which version is installed in each case.
2. If you would like to display additional information on the installed automation software,
click the link on the "Detailed information about installed software" dialog.
The "Detailed information" dialog opens.
3. Chose the topic you want more information about in the area navigation.
See also
Notes on the system requirements (Page 39)
Notes on licenses (Page 9)
Starting installation (Page 59)
Modifying or updating installed products (Page 65)
Repairing installed products (Page 67)
Starting to uninstall (Page 69)
Installation log (Page 57)
Requirement
• Hardware and software of the programming device or PC meet the system requirements.
• You have administrator privileges on your computer.
• All running programs are closed.
Procedure
To modify or update installed products, follow these steps:
1. Insert the installation medium in the relevant drive.
The setup program starts automatically unless you have disabled Autostart on the
programming device or PC.
2. If the setup program does not start up automatically, start it manually by double-clicking the
"Start.exe" file.
The dialog for selecting the setup language opens.
3. Choose the language in which you want the setup program dialogs to be displayed.
4. To read the information on the product and installation, click the "Read Notes" or
"Installation Notes" button.
The help file containing the notes opens.
5. Once you have read the notes, close the help file and click the "Next" button.
The dialog for selecting the installation variant opens.
6. Select the "Modify/Upgrade" option button and click the "Next" button.
The dialog for selecting the product languages opens.
7. Select the check boxes of the product languages that you want to install. You can remove
previously installed product languages by clearing the corresponding check boxes.
Note
Note that the product language "English" cannot be removed.
Note
Note that you cannot change the target directory because the existing installation is being
modified.
If changes to the security and permission settings are required in order to install the TIA
Portal, the security settings dialog opens.
11.To continue the installation, accept the changes to the security and permissions settings,
and click the "Next" button.
The next dialog displays an overview of the installation settings.
12.Click the "Modify" button.
This starts the installation of the additional components.
Note
Following installation, you will receive a message indicating whether the existing
installation was successfully changed.
13.It may be necessary to restart the computer. If this is the case, select the "Yes, restart my
computer now." option button. Then click "Restart".
14.If the computer does not reboot, click "Exit".
Result
The existing installation has been modified on your computer.
See also
Notes on the system requirements (Page 39)
Notes on licenses (Page 9)
Starting installation (Page 59)
Displaying the installed software (Page 63)
Repairing installed products (Page 67)
Starting to uninstall (Page 69)
Installation log (Page 57)
Requirement
• Hardware and software of the programming device or PC meet the system requirements.
• You have administrator privileges on your computer.
• All running programs are closed.
Procedure
To repair installed products, follow these steps:
1. Insert the installation medium in the relevant drive.
The setup program starts automatically unless you have disabled Autostart on the
programming device or PC.
2. If the setup program does not start up automatically, start it manually by double-clicking the
"Start.exe" file.
The dialog for selecting the setup language opens.
3. Choose the language in which you want the setup program dialogs to be displayed.
4. To read the information on the product and installation, click the "Read Notes" or
"Installation Notes" button.
The help file containing the notes opens.
5. Once you have read the notes, close the help file and click the "Next" button.
The dialog for selecting the installation variant opens.
6. Select the "Repair" option button, and click the "Next" button.
The next dialog displays an overview of the installation settings.
7. Click the "Repair" button.
This starts the repair of the existing installation.
Note
Following installation, you will receive a message indicating whether the existing
installation was successfully repaired.
8. It may be necessary to restart the computer. If this is the case, select the "Yes, restart my
computer now." option button. Then click "Restart".
9. If the computer does not reboot, click "Exit".
Result
The installed products have been reinstalled.
See also
Notes on the system requirements (Page 39)
Notes on licenses (Page 9)
Starting installation (Page 59)
Displaying the installed software (Page 63)
Modifying or updating installed products (Page 65)
Starting to uninstall (Page 69)
Installation log (Page 57)
Note
The Automation License Manager will not be removed automatically when you remove the
software packages, because it is used for the administration of several license keys for
products supplied by Siemens AG.
See also
Installation log (Page 57)
Notes on the system requirements (Page 39)
Notes on licenses (Page 9)
Starting installation (Page 59)
Displaying the installed software (Page 63)
Modifying or updating installed products (Page 65)
Repairing installed products (Page 67)
Note
Updates and support packages from TIA Portal V13 or higher are supported.
Or:
1. Select the "Settings" command in the "Options" menu.
The "Settings" window is displayed in the work area.
2. Select the "General > Software Updates" group in the area navigation.
3. Click "Check for updates now".
The TIA Administrator opens.
4. Click on the "Manage software" tile.
The available updates are displayed.
Or:
1. Open the TIA Administrator via "Start > All Programs > Siemens Automation > TIA
Administrator".
2. Click on the "Manage software" tile and on the "Check for updates" button there.
The available updates are displayed.
See also
Installation log (Page 57)
Introduction
Using a corporate server, you can place selected updates / support packages on a local server
and make them available to users, e.g. for different production lines. This has the advantage
that users do not have to access the Internet, but can install updates via the intranet, an
external hard disk, etc. Since users do not need direct access to the Internet, the protection
against trojans or malicious software that contacts the Internet from the internal company
network is significantly increased.
Introduction
To provide available updates and support packages to users from a central location, you must
configure a corporate server. Use the Microsoft Server Manager to do this.
The following is an example of the steps required to create and configure the server using the
TIA Updater Corporate Configuration Tool (with the Microsoft Server 2016 operating system).
Further settings which may be required for operation in your company are not covered in this
description!
Note
Please note that the structure of the start menu and the storage location of the programs
may vary depending on the different operating systems.
For more detailed information on configuration and operating the Server Manager, refer to
the Microsoft help.
Requirement
You must have administrator rights.
Create website
1. In the navigation area, click "IIS" and right-click in the "Servers" area and select "Internet
Information Services (IIS) Manager".
2. In the "Connections" area, click "Sites" and then "Default Web site".
3. Right-click to select the "Add Virtual Directory..." option.
4. In the dialog that opens, enter a display name in the "Alias" field, for example,
"TIAPortalUpdates".
5. In the "Physical path" field, enter the physical path of the folder in which the website is
located or click the button to browse (...), in order to search for the folder in the file system.
6. Click "Test Settings..." to check whether the settings are correct.
7. Click "OK".
Introduction
In the TIA Updater Corporate Configuration Tool, you can set a corporate server on which the
available updates/support packages are stored and can be made available to the users.
Requirement
You must have administrator rights.
A corporate server can only be set up on a Microsoft server operating system, because it
requires the operation of the BITS IIS service and a running IIS sever.
Server options
In the dialog "TIA Automation Software Update Server", click "Settings" to determine the
following:
1. Under "Server path", specify the folder in which the downloads are to be saved. You can
select either a local drive or a network drive.
Note
When you work directly on the server, the target directory is the same as the provision
directory on the server. All changes are applied directly. This procedure is not
recommended, as conflicts can occur with active downloads.
We recommend that you work on another computer; the target directory can be any
directory. The content of this directory must then still be copied to the provision directory.
Here, also, make sure that no conflicts occur with active downloads.
2. Select the check box "Always run server in background (icon is shown in the taskbar)", if the
server is to always run in the background.
3. Confirm your entries with "OK".
See also
Properties and advantage of a corporate server (Page 74)
Configuring a corporate server for updates (Page 75)
Introduction
As of V15.1, you can use the Support Package Installer to install or upgrade all support
packages automatically via the command line; these include HSPs (hardware support
packages) that are compatible with the installed version of the TIA Portal (e.g. isp.15_1).
Requirement
• Hardware and software of the programming device or PC meet the system requirements.
• You have administrator privileges on your computer.
• All running programs have been closed.
Procedure
To start the installation with the desired options directly via the command line, proceed as
follows:
1. Open the Windows command prompt with "Start > Run > cmd".
2. Switch to the directory that contains the "Siemens.Automation.SupportPackageInstaller.exe"
file. This is the installation directory of your installed TIA Portal.
3. In the command prompt, enter the following command:
%Installation directory% > Siemens.Automation.SupportPackageInstaller.exe <Support
Package(HSP)-storage directory> [-l <Name of log file>] [-warnaserror]
<Support Package-storage_directory>
Mandatory directory containing the support package files (*.isp). This can be either a local
folder or a Remote Share.
-l <Storage location of log file>
This parameter is optional and specifies the path to the log file. If it is not set, the log file is
created in the binary directory. However, you need to have write permissions in the storage
folder.
-warnaserror
This parameter is optional and indicates that every message that would usually have been
reported as a warning will be reported as an error instead. If a HSP does not meet the
necessary conditions, for example, a corresponding return value/abort value is output to the
command line and the affected HSP is skipped.
-?
This parameter is optional and shows the Help.
Note
• If the storage directory or the name of the log file contains spaces, you need to place the
name in quotation marks.
• Only support packages located directly in the storage directory are considered;
subdirectories are ignored. This means that the *.isp files must be located directly in the
storage directory.
See also
Return values from the installation process (Page 82)
Log file (Page 83)
Core statement
The following table shows the return values and their descriptions:
Code Description
0 The installation was successful.
1 The installation was successful and a restart is required.
-1 The installation failed.
-2 The installation failed: The TIA Portal is still running.
-3 The installation failed: Another installation is already run-
ning.
-4 The installation failed: You do not have sufficient rights. The
installation requires administrator rights.
-6 The installation failed: Insufficient memory space.
-7 The installation failed: A restart is required before the instal-
lation can start.
See also
Installing support packages automatically (Page 81)
Log file (Page 83)
See also
Installing support packages automatically (Page 81)
Return values from the installation process (Page 82)
Procedure
To install the migration tool, proceed as follows:
1. Download the installation file from the Siemens Industry Online Support, or use the
installation file from the "Support" directory of the installation DVD of the TIA Portal to
perform the installation.
2. Run the installation file.
The setup program for the migration tool will open.
3. First, select the language in which the setup should be displayed and click "Next".
The page for selecting the software language is displayed.
4. Since the migration tool is provided exclusively in English, you cannot choose any other
language for the installation. Therefore, click "Next" to proceed to the next step.
The page for selecting the product is displayed.
5. The migration tool consists solely of a software component. Therefore, the migration tool is
already selected. Click "Next".
The page for confirming the licensing terms is shown.
6. Click on the entries in the list of license terms to read the license terms and security
information. If you agree to the license terms, select the check box "I accept all terms of the
listed license agreement(s)" and "I confirm that I have read and understood the security
information on the safe operation of the products".
7. Then click "Next".
An overview of the installation is displayed.
8. Click "Install".
The installation is performed with the displayed settings.
A restart of the computer is required after the installation of the migration tool.
Procedure
To remove the migration tool, follow these steps:
1. Open the Control Panel.
2. Double-click on "Programs and Functions" in the control panel.
The "Uninstall or Change a Program" dialog opens.
3. Select the entry for the migration tool in the "Uninstall or Change a Program" dialog, and
click "Uninstall".
A security prompt appears.
4. Click "Yes" to confirm this prompt.
The setup program starts.
5. Select the installation language and click "Next".
6. Select the migration tool to uninstall and click "Next".
7. Click "Uninstall".
The migration tool will be removed.
8. Click on "Exit" to close the setup program.
Introduction
Installation of the multiuser server enables you to use the Multiuser Engineering
functionality.
You can install the multiuser server as follows:
• Together with the installation of the TIA Portal.
• As standalone installation by means of a separate installation process without TIA Portal.
Note
Administrator rights are required for the server installation.
Installation path
Do not use any UNICODE characters (for example, Chinese characters) in the installation
path.
Antivirus programs
During the installation, read and write access to installed files is necessary. Some antivirus
programs block this access. We therefore recommend that you disable antivirus programs
during the installation of the multiuser server and enable them again afterwards.
See also
Installing a project server (Page 91)
Uninstalling a project server (Page 93)
Introduction
The project server can be installed as part of the installation of TIA Portal or as standalone. If
the project server is installed with TIA Portal, the version of the project server installed will
always correspond to that of TIA Portal.
A description of automated installation is also available on the product DVD in the directory
"Documents\Readme\<language directory>".
Note
New installation before uninstallation
Make sure that you install the new project server first and then uninstall the older version
of the project server.
In this way, you ensure that the user authorizations for the server can be taken over for the
new server. If all existing project servers are completely deleted before the new installation,
the user settings are lost and must be created again.
Installation rules
Multiple versions of the project server can be installed on a computer and can use different
project versions of TIA Portal.
Usable project versions:
Note
Notes on the compatibility of the project server
The newly added server functionality for the current version is only available if the current
version of TIA Portal is also installed.
If you are still working with an older version of TIA Portal or an older version of the project
server, only the functionality included in the respective product version is available.
Multiuser Engineering does not upgrade the project versions.
Result
The project server was installed on your computer together with TIA Portal.
Result
The project server has been installed on your computer.
See also
Notes on installing the project server (Page 89)
Uninstalling a project server (Page 93)
Introduction
You can use the Control Panel to remove the project server.
Note
New installation before uninstallation
Make sure that you install the new project server first and then uninstall the older version
of the project server.
In this way, you ensure that the user authorizations for the server can be taken over for the
new server. If all existing project servers are completely deleted before the new installation,
the user settings are lost and must be created again.
Result
The project server has been uninstalled from your computer.
See also
Notes on installing the project server (Page 89)
Installing a project server (Page 91)