Migration Of WinCC Projects From V4 To V7
Migration of WinCCProjects from V4 to V7SIMATIC /view/44029132SiemensIndustryOnlineSupport
This entry is from the Siemens Industry Online Support. The following Terms ofUse shall apply (www.siemens.com/Terms of use). Siemens AG 2017 All rights reservedSecurityinformationSiemens provides products and solutions with industrial security functions thatsupport the secure operation of plants, systems, machines and networks.In order to protect plants, systems, machines and networks against cyberthreats, it is necessary to implement – and continuously maintain – a holistic,state-of-the-art industrial security concept. Siemens’ products and solutions onlyform one element of such a concept.Customer is responsible to prevent unauthorized access to its plants, systems,machines and networks. Systems, machines and components should only beconnected to the enterprise network or the internet if and to the extent necessaryand with appropriate security measures (e.g. use of firewalls and networksegmentation) in place.Additionally, Siemens’ guidance on appropriate security measures should betaken into account. For more information about industrial security, please mens’ products and solutions undergo continuous development to make themmore secure. Siemens strongly recommends to apply product updates as soonas available and to always use the latest product versions. Use of productversions that are no longer supported, and failure to apply latest updates mayincrease customer’s exposure to cyber threats.To stay informed about product updates, subscribe to the Siemens IndustrialSecurity RSS Feed under http://www.siemens.com/industrialsecurity.SIMATIC WinCC MigrationEntry ID: 44029132, 1.2, 07/20172
Table of Contents1General notes on migration . 51.11.21.31.41.51.61.71.81.8.11.8.21.8.32Importing from project versions lower than V4.02 SP3 to WinCC V5 . 112.12.22.32.4 Siemens AG 2017 All rights reserved3Requirements / conditions . 14Required software / licenses . 14Migration sequence . 15Migration of backup archives . 20Migration check . 20Project adaptations / system changes . 21Migration from SIMATIC WinCC V5.1 to SIMATIC WinCC V6.0/V6.2 . .9.55Requirements / conditions . 11Required software / licenses . 11Preparatory activities . 11Details on the conversion within SIMATIC WinCC V4 . 12Migration from SIMATIC WinCC V4.02 SP3 to SIMATIC WinCC V5.1 . 143.13.23.33.43.53.64Terms . 5Compatibility . 5Scripts and in-house developments . 5WinCC options . 5Project backup . 6WinCC database versions . 6Upgrading overview SIMATIC WinCC V3 to V7. 7Overview of the migration steps . 10Migration from WinCC V4 to V5 . 10Migration from WinCC V5 to V6 . 10Migration WinCC V6 to V7 . 10Requirements / conditions . 22Required software . 22Preparatory activities . 22License update . 24Migration sequence . 25Additional steps after the migration . 27Migration of backup archives . 28Migration check . 28Project adaptations / system changes . 29Significant differences compared to V5.1 . 29Changes in C functions . 30Significant differences compared to V6.0 . 31Communication channels . 31Upgrading within SIMATIC WinCC V6 (V6.0 V6.2) . 32Migration from SIMATIC WinCC V6.x to SIMATIC WinCC V7.4 SP1 . 335.15.25.35.45.55.65.75.85.95.105.11Requirements / notes . 33Required software . 33Preparatory activities . 34License update . 35Migration sequence . 36Additional steps after the migration . 40Migration of backup archives . 42Migration check . 42Migration diagnosis . 44Project adaptations / system changes . 44Upgrading within WinCC V7 (V7.0 V7.2/ V7.3SE/ V7.4) . 46SIMATIC WinCC MigrationEntry ID: 44029132, 1.2, 07/20173
5.11.15.11.25.11.35.125.136License overview / update licenses . 506.16.26.37Requirements / notes . 46WinCC V7.0 to WinCC V7.2 . 47WinCC V7.2 to WinCC V7.4 / V7.4 SP1 . 47Licensing of WinCC V7.3 SE / WinCC V7.4. 48Important differences compared to previous versions . 48Migration from WinCC V4 to V5 . 50Migration from WinCC V5 to V6 . 50Migration from WinCC V6 to V7 . 51Appendix . 52Service and support . 52Links and literature . 53Change documentation . 53 Siemens AG 2017 All rights reserved7.17.27.3SIMATIC WinCC MigrationEntry ID: 44029132, 1.2, 07/20174
1 General notes on migration1General notes on migration1.1TermsMigrationIn a migration, a WinCC project is ported from version X to version Y. Theconfiguration data and Runtime data are imported into the new version even if thenew version has a different database. From WinCC version V6 on, a projectmigration tool is provided for support.ConversionConversions affect parts of a project. This happens, for example, when changing toa new service pack. Here, for example only the WinCC Runtime pictures or thelibraries have to be converted.1.2Compatibility Siemens AG 2017 All rights reservedPlease consider the compatibility of SIMATIC WinCC with the operating systemused, incl. Service Pack, Step7 and other SIMATIC products.An overview of the compatibility of SIMATIC WinCC V5, V6 and V7 is available atthe following /view/64847781NoteIf you want to migrate a WinCC project from a different time zone to a morerecent SIMATIC WinCC version, it is absolutely necessary to set the migrationcomputer to the time zone from which the project originates.In WinCC, the UTC time is used in the databases. If the time zone is setincorrectly, this might result in a faulty calculation of this time here.1.3Scripts and in-house developmentsScripts and in-house developments might increase and impede the migrationexpenditure. These cannot be considered in this description.1.4WinCC optionsThis migration description does not consider any options. If you are using optionssuch as Advanced User Administrator, WebNavigator, etc., please note the versionreleases on the Service and Support pages.SIMATIC WinCC MigrationEntry ID: 44029132, 1.2, 07/20175
1 General notes on migration1.5Project backupProject backup via file compressionAlways create a backup of your WinCC project. When the WinCC project is notopen, you can, for example, pack the project with WinZip and back it up that way.Create a backup after each migration step (from version to version).NoteYou can use the scheduler function of the "Windows Backup", for example tocreate a daily or weekly backup of the WinCC project.The backups can also be stored on external data carriers or network drives.For each backup, a log file is created.The Runtime data in the WinCC project folder "ArchiveManager" are alsoarchived.1.6WinCC database versions Siemens AG 2017 All rights reservedTable 1-1WinCC versionDatabase V4.xSybase Anywhere 4V5.0Sybase Anywhere 5V5.1Sybase Anywhere 7V6.0SQL Server 2000V6.0 SP4SQL Server 2000 SP4V6.2SQL Server 2005 SP1V7.0SQL Server 2005 SP1V7.0 SP1SQL Server 2005 SP2V7.0 SP2SQL Server 2005 SP3V7.0 SP3SQL Server 2005 SP4V7.2SQL Server 2008 R2 SP2V7.3 SESQL Server 2008 R2 SP2/SP3V7.4SQL Server 2014 SP1V7.4 SP1SQL Server 2014 SP2SIMATIC WinCC MigrationEntry ID: 44029132, 1.2, 07/20176
1 General notes on migration1.7Upgrading overview SIMATIC WinCC V3 to V7The following graphic shows the intermediate steps to be taken in order to migrateWinCC projects from previous versions.NoteExperience shows that some customer projects cannot be upgraded with versionleaps from the history. In this case, an upgrade from version to version isreasonable, e. g. from V6 V7.0 V7.2 V7.4 Siemens AG 2017 All rights reservedFigure 1-1, upgrade from V3 to V4SIMATIC WinCC MigrationEntry ID: 44029132, 1.2, 07/20177
1 General notes on migrationFigure 1-2, upgrade from V5 to V6WinCC V5.0WinCC V5.0 SP1WinCC V5.0 SP2WinCC V5.1WinCC V5.1 SP1 Siemens AG 2017 All rights reservedWinCC V5.1 SP2WinCC V6.0 (SP1-SP4) oderWinCC 6.2 (SP2-SP3)Figure 1-3, upgrade from V6.x to V7.0WinCC V6.0WinCC V6.0 SP1WinCC V6.0 SP2WinCC V6.0 SP3WinCC V6.0 SP4WinCC V6.2WinCC V6.2 SP2WinCC V6.2 SP3WinCC V7.0WinCC V7.0 SP1WinCC V7.0 SP2WinCC V7.0 SP3SIMATIC WinCC MigrationEntry ID: 44029132, 1.2, 07/20178
1 General notes on migrationFigure 1-4, upgrade from V6.2 SP3 to V7.2/ V7.3 V7.4WinCC V6.2 SP3WinCC V7.0WinCC V7.0 SP1WinCC V7.0 SP2WinCC V7.0 SP3WinCC V7.2WinCC V7.3 SEWinCC V7.4 Siemens AG 2017 All rights reservedWinCC V7.4 SP1Figure 1-5, upgrade within V7.xWinCC V7.0WinCC V7.0 SP1WinCC V7.0 SP2WinCC V7.0 SP3WinCC V7.2WinCC V7.3 SEWinCC V7.4WinCC V7.4 SP1SIMATIC WinCC MigrationEntry ID: 44029132, 1.2, 07/20179
1 General notes on migration1.8Overview of the migration steps1.8.1Migration from WinCC V4 to V51. Backup of the SIMATIC WinCC V4 project2. SIMATIC WinCC V4 project check3. Software update4. License update5. Project migration6. Migration of the backup archives7. Migration check8. Project adaptations1.8.2Migration from WinCC V5 to V61. Backup of the SIMATIC WinCC V5 project2. Software update3. License update Siemens AG 2017 All rights reserved4. Project migration5. Migration of the backup archives6. Migration check7. Project adaptations1.8.3Migration WinCC V6 to V71. Backup of the SIMATIC WinCC V6 project2. Software update3. License update4. Project migration5. Migration check6. Project adaptationsNoteMigrated projects must be tested. It is the plant operator who is responsible for aperfect functioning!SIMATIC WinCC MigrationEntry ID: 44029132, 1.2, 07/201710
2 Importing from project versions lower than V4.02 SP3 to WinCC V52Importing from project versions lower thanV4.02 SP3 to WinCC V52.1Requirements / conditionsThe WinCC V3.x project must be migrated to at least V4.02 SP3/SP4.Before upgrading to a more recent version, in the case of multi-user projects itshould be ensured that the computer on which the upgrading is performed isactually registered as server in this project.If this is not the case, the project can be opened with an identical WinCC versionbefore the upgrading and the computer which performs the upgrading can beregistered as server.If in the User Administrator under V3.1, two or more users were registered whoonly differ in the use of capital and small letters, these are to be deleted except forone or renamed before the conversion to V4.x.2.2Required software / licensesTable 2-1 Siemens AG 2017 All rights reservedProductWinCC V4.02 SP3and the lastavailableupdate/hotfixNote2.3Order number6AV6381-1AA04-0EX4NoteThis package is no longer available.You only require the WinCC V4.02 SP3version to migrate the WinCC V3.Xproject to V4.02 SP3; if required, theCD can be sent to you via your localspecialist support.The WinCC V3 licenses are still valid in SIMATIC WinCC V4.Preparatory activitiesActivitiesIf you have created a project with the version 4.00, a picture conversion has to be carriedout.The API of the Report Designer has been revised and contains, among other things,much more functions. Users having used this API in older WinCC versions mustrecompile their application.The database is converted with the program "WinCC Database Upgrade".The picture data are converted with the Graphics Designer.If you are using the Basic Process Control option in an existing project, the following stepsare required to convert the project: Using the Split Screen Wizard Using the Alarm Logging Wizard Conversion of the global library Conversion of the project library Conversion of the pictures Opening the Tag Logging and closing with SaveSIMATIC WinCC MigrationEntry ID: 44029132, 1.2, 07/201711
2 Importing from project versions lower than V4.02 SP3 to WinCC V5Activities Opening Global Script and in the "Options" menuCompiling all functionsRegenerating the headerOpening the Picture Tree Manager and closing with SaveUnder the menu item "Options", "Completely recalculate group display hierarchyupon saving" must be set. Siemens AG 2017 All rights reservedWinCC system alarms (without using the Basic Process Control option) Some new WinCC system alarms have been added and the text and number ofalready existing system alarms has been adapted. To obtain these expansions/corrections in the system alarm window, the systemalarms must be reimported in existing projects. To do this, proceed as follows: Start the Editor Alarm Logging. From the “Tools" menu, select the item "WinCC system alarm.". In the dialog box "WinCC system alarm", activate "Create new system alarms,overwrite existing ones". Click the "Create" button.2.4Details on the conversion within SIMATIC WinCC V4When switching to a new version or after the installation of a Service Pack, theprojects must be converted.Table 2-2No.Procedure1.Conversion of the global libraryIn the Control Center, open the context menu of the Graphics Designer andactivate the entry "Convert global library".2.Conversion of the project libraryIn the Control Center, open the context menu of the Graphics Designer andactivate the entry "Convert project library".3.Conversion of picturesIn the Control Center, open the context menu of the Graphics Designer andactivate the entry "Convert pictures".4.Split Screen WizardIn the Control Center, open the context menu of the Split Screen Wizard in BaseData and activate the "Open" entry.5.Alarm Logging WizardIn the Control Center, open the context menu of the Alarm Logging Wizard andactivate the "Open" entry.6.Conversion of the user archivesThe conversion of the user archives is performed in two steps: Conversion of the archive structure Conversion of the Runtime dataTo convert the archive structure, proceed as follows: Start the "User Archive" editor in the Control Center. In the menu bar of the started editor, select "Project"/"Convert.". In the "Converting Old Archives" dialog window, select the user archive to beconverted and start the conversion via the "Converting" button.SIMATIC WinCC MigrationEntry ID: 44029132, 1.2, 07/201712
2 Importing from project versions lower than V4.02 SP3 to WinCC V5No.Procedure After completed conversion, leave the dialog window via the "Close" button.Save the converted archive structure. Siemens AG 2017 All rights reservedTo convert the Runtime data, proceed as follows: In the menu bar of the started editor, select "Project"/"Convert.". In the "Converting Old Archives" dialog box, open the "Migrating RT Data"dialog box via the "RT Data." button. Select the old and the new, converted archive and start the migration via the"Migrating" button. Close the "Migrating RT Data" dialog box via the "Close" button. Close the "Converting Old Archives" dialog box via the "Close" button.SIMATIC WinCC MigrationEntry ID: 44029132, 1.2, 07/201713
3 Migration from SIMATIC WinCC V4.02 SP3 to SIMATIC WinCC V5.13Migration from SIMATIC WinCC V4.02 SP3to SIMATIC WinCC V5.13.1Requirements / conditionsWinCC V4 project checkBefore upgrading, check your project for special characters in the names of: Archives Archive variables Graphs Trend windows Columns Table windowsIf necessary, the special characters must be removed from the names with WinCCV4.02 in the Tag Logging.Prerequisites Siemens AG 2017 All rights reservedLink to Online SupportWhen installing V5.1 SP2, please observe the Installation Notes.The released operating systems for SIMATIC WinCC V5.x can be found ew/64847781 .Note3.2Further information on permissible special characters is available in the systemoverview under "Configuration with WinCC" "Prohibited Characters".Required software / licensesTable 3-1ProductWinCC V5.1 SP2and the lastavailableupdate/hotfixNoteOrder numberNote6AV6381-1AA05-1CX4The SIMATIC WinCC V3 and V4 licenses are also valid in V5!SIMATIC WinCC MigrationEntry ID: 44029132, 1.2, 07/201714
3 Migration from SIMATIC WinCC V4.02 SP3 to SIMATIC WinCC V5.13.3Migration sequenceTable 3-2 Siemens AG 2017 All rights reservedNo.Procedure1.Open the WinCC V4 project on your WinCC V5.1 SP2 system.2.In the "Computer" editor, adapt the computer name. Open the Properties dialog of the server computer. Enter the name of your computer. Close the dialog.Close the WinCC Explorer and reopen the WinCC project.SIMATIC WinCC MigrationEntry ID: 44029132, 1.2, 07/201715
3 Migration from SIMATIC WinCC V4.02 SP3 to SIMATIC WinCC V5.1 Siemens AG 2017 All rights reservedNo.Procedure3.Conversion of the global library In the WinCC Explorer, open the context menu of the Graphics Designer andactivate the entry "Convert global library".4.Conversion of the project library In the WinCC Explorer, open the context menu of the Graphics Designer andactivate the entry "Convert project library".SIMATIC WinCC MigrationEntry ID: 44029132, 1.2, 07/201716
3 Migration from SIMATIC WinCC V4.02 SP3 to SIMATIC WinCC V5.1No. Siemens AG 2017 All rights reserved5.6.ProcedureConversion of pictures In the WinCC Explorer, open the context menu of the Graphics Designer andactivate the entry "Convert pictures". Confirm the warning note that the trend and alarm controls are replaced. All pictures of the WinCC project are converted to the new version.When converting pictures, the following restrictions apply: Pictures must only be converted if they do not contain any "Undefined Objects".These are picture objects whose associated object server is not installed, e. g.unregistered ActiveX Controls. Pictures must only be converted if they do not contain any grouped applicationwindows of Alarm Logging and Tag Logging. Before the conversion, the group mustbe dissolved and the picture must be stored.SIMATIC WinCC MigrationEntry ID: 44029132, 1.2, 07/201717
3 Migration from SIMATIC WinCC V4.02 SP3 to SIMATIC WinCC V5.1No. Siemens AG 2017 All rights reserved7.ProcedureConversion of user archives Conversion of the archive structure: Start the "User Archive" editor in the WinCC Explorer. In the menu bar of the started editor, select "Project"/"Convert.". In the "Converting Old Archives" dialog window, select the user archive to beconverted and start the conversion via the "Converting" button. After completed conversion, leave the dialog window via the "Close" button.Save the converted archive structure.Conversion of the Runtime data: In the menu bar of the started editor, select "Project"/"Convert.". In the "Converting Old Archives" dialog box, open the "Migrating RT Data" dialogbox via the "RT Data." button. Select the old and the new, converted archive and start the migration via the"Migrating" button. Close the "Migrating RT Data" dialog box via the "Close" button. Close the "Converting Old Archives" dialog box via the "Close" button.8.Representation in Runtime If data of a correctly imported user archive are not represented in Runtime, theconfiguration data must be relinked: Open the Graphics Designer. Relink the Controls table with the user archive.SIMATIC WinCC MigrationEntry ID: 44029132, 1.2, 07/201718
3 Migration from SIMATIC WinCC V4.02 SP3 to SIMATIC WinCC V5.1No.Procedure Siemens AG 2017 All rights reserved Save the picture.9.User archive (before WinCC V4.02) The conversion of user archives which were created with a WinCC version olderthan V4.02 is not possible if the archive and field names are longer than 20characters. In case of problems in connection with converted user archives, we recommendcreating user archives with the WinCC version V5.1 SP2.10.Persistence A persistence configured in Tag Logging will not be applied during the conversion.The persistence must be reconfigured in the converted project.11.Split Screen Wizard In the WinCC Explorer, open the context menu of the Split Screen Wizard in BaseData and activate the "Open" entry.12.Alarm Logging Wizard In the WinCC Explorer, open the context menu of the Alarm Logging Wizard inBase Data and activate the "Open" entry.13.If you used the Basic Process Control option in an existing project, the following stepsare required to convert the project: Using the Split Screen Wizard Using the Alarm Logging Wizard Conversion of the global library Conversion of the project library Conversion of the pictures Opening the Tag Logging and closing with Save Opening the Picture Tree Manager and closing with Save Under the menu item"Options", "Completely recalculate group display hierarchy upon saving" must beset.SIMATIC WinCC MigrationEntry ID: 44029132, 1.2, 07/201719
3 Migration from SIMATIC WinCC V4.02 SP3 to SIMATIC WinCC V5.1No.14.3.4ProcedureIf it is a multi-user project with multi-client connections, all packages on the serversshould be deleted, recreated and reloaded on the multi-clients.Migration of backup archivesSteps and notesConfiguration data and Runtime data can be imported from WinCC V5.0 Service Pack 1and Service Pack 2 to WinCC V5.1 SP2 without any additional processing. WinCCautomatically performs an upgrade for the Runtime data.If direct access to Runtime data was configured, please consider the following: From WinCC V5.0 Service Pack 1 on, Sybase Version 7.0.3 is used for the Runtimedatabase. Thereby, the name of the database tool "isql.exe" changed. The new name isdbisqlc.exe. While WinCC accesses a database, the parameter DSN DataSourceName must beused when calling dbisqlc. A call via a C program might look as follows:ProgramExecute (dbisqlc -q -b -c " uid dba; pwd sql; dsn CC test 01-0418 14:41:11R" select * from msarclong; output to c:\deldelde.txt) Siemens AG 2017 All rights reserved3.5Migration checkDuring migration/conversion, no log files are created. The migration can only bechecked in the configuration and Runtime environment.SIMATIC WinCC MigrationEntry ID: 44029132, 1.2, 07/201720
3 Migration from SIMATIC WinCC V4.02 SP3 to SIMATIC WinCC V5.13.6Project adaptations / system changesOnBtn. functions (in ActiveX Controls trend and message representation)The OnBtn. functions are no longer supported by WinCC and only provided forcompatibility reasons. For new projects, only use the AXC OnBtn. functions.Global Script Diagnose ControlThe Global Script Diagnose Control is no longer available from WinCC V5.0Service Pack 1 on. Use the Global Script application window instead.Function key F12 Siemens AG 2017 All rights reservedThe function key F12 must not be configured as system-wide hotkey.SIMATIC WinCC MigrationEntry ID: 44029132, 1.2, 07/201721
4 Migration from SIMATIC WinCC V5.1 to SIMATIC WinCC V6.0/V6.24Migration from SIMATIC WinCC V5.1 toSIMATIC WinCC V6.0/V6.24.1Requirements / conditionsWhen installing V6.2 SP2, please observe the Installation Notes.The released operating systems for SIMATIC WinCC V5.x can be found in theOnline Support at: /64847781.Installation of the Sybase database of the SIMATIC WinCC V5 version, for themigration.If you have been working with a WinCC version lower than V5.0 SP2 so far, youfirst have to migrate your project to WinCC V5.0 SP2 or WinCC V5.1.If in WinCC V6.2 you want to work with a project which was created with WinCCV5.0 Service Pack 2 or WinCC V5.1, you have to adapt the project datacorrespondingly in the migration. Siemens AG 2017 All rights reservedNotePictures and libraries from one WinCC version can only be converted via thenext main versions. If, for example, you want to convert pictures from WinCCV5.0 SP2 to V6.2, you first have to convert the pictures to WinCC V5.1, then toWinCC V6.0 and finally to WinCC V6.2.For this purpose, WinCC V6.2 provides the Project Migrator, which automaticallymigrates the configuration data, Runtime data and swapped-out data of a project.4.2Required softwareTable 4-1ProductOrder numberWinCC V5.1 SP2 CD6AV6381-1AA05-1CX4for Sybase database installationWinCC V6.2 SP3and the last s.com/Microsoft SQL server (is suppliedwith WinCC V6.x)MS Message Queuing4.3NotePart of the operating system, mayhave to be installed subsequentlyA detailed description of theinstallation is available in the WinCCInformation System "How to installMicrosoft Message Queuing".Preparatory activitiesPrerequisiteSybase 7 must be installed on the migration computer. Sybase SQL Anywhere 7can be installed subsequently via the Autorun program of the WinCC V6.2-DVD.The installation CD for WinCC V5.0 Service Pack 2 or WinCC V5.1 is required forthat.SIMATIC WinCC MigrationEntry ID: 44029132, 1.2, 07/201722
4 Migration from SIMATIC WinCC V5.1 to SIMATIC WinCC V6.0/V6.2InstallationNo.ProcedureStart the installation DVD of WinCC V6.2.2.In the "Further software" menu, select the entry "SQL Anywhere Studio 7". Followthe instructions in the setup of Sybase SQL Anywhere 7.3.When requested, insert the installation CD for WinCC V5.0 SP2 or WinCC V5.1 inthe CD drive.4.If Autorun function is active in your operating system, the inserted CD is started.However, the started Autorun program of WinCC V5 is not required for themigration. Quit the program with "Close".5.In the Sybase setup, click on the "Repeat" button. Sybase SQL Anywhere 7 isinstalled.6.Restart the computer! Siemens AG 2017 All rights reserved1.SIMATIC WinCC MigrationEntry ID: 44029132, 1.2, 07/201723
4 Migration from SIMATIC WinCC V5.1 to SIMATIC WinCC V6.0/V6.2 Note"Symantec Ghost Corporate Edition" is not compatible with Sybase 7 ofSTEP7/WinCC. The installation options "Console client", "Standalone client" and"Standard tools only" as well as the standard version "Norton Ghost" provided bySymantec are not affected by this incompatibility.Sybase 7 is no longer required after the migration and can be deinstalled. 4.4License updateThe licensing of WinCC V6.2 differs from the previous versions. You need new RTlicenses or RC licenses.NoteThe licensing can be updated during the installation of WinCC V6.2 orsubsequently. Detailed information is available in the WinCC Information Systemat "Licensing".If you got WinCC as upgrade V5.x - V6.2, you must upgrade the existingauthorizations. The same applies to the authorizations of communication driversand WinCC options. Siemens AG 2017 All rights reservedUpgrade to WinCC V6After an upgrade from WinCC V5 to WinCC V6, only one V6 license is available.This license is not recognized by WinCC V5.If WinCC V5 is
1 General notes on migration SIMATIC WinCC Migration Entry ID: 44029132, 1.2, 07/2017 5 G 7 d 1 General notes on migration 1.1 Terms Migration In a migratio
WinCC V7.4 DVD: WinCC V7.4 WinCC/WebNavigator V7.4 WinCC/DataMonitor V7.4 WinCC/Connectivity Pack V7.4 WinCC/Connectivity Station V7.4 SQL Server 2014 SP1 for WinCC V7.4 SIMATIC Logon V1.5 SP3 Automation License Manager V5.3 SP3 WinCC: General information and installation
4/4 HMI software in the TIA Portal 4/5 SIMATIC WinCC (TIA Portal) Engineering 4/9 SIMATIC WinCC (TIA Portal) Runtime 4/10 WinCC Runtime Advanced 4/14 WinCC Runtime Professional 4/19 WinCC Runtime Communication 4/25 SIMATIC WinCC (TIA Portal) options 4/26 WinCC Recipes 4/28 WinCC Logging 4
4/76 WinCC/User Archives 4/77 SIMATIC BATCH (for WinCC) 4/80 WinCC/ChangeControl & WinCC/Audit 4/82 SIMATIC Logon 4/83 WinCC/IndustrialX 4/84 WinCC/ODK 4/85 WinCC/Comprehensive Support 4/86 WinCC Premium Add-ons and partner management 4/88 SIMATIC ProAgent process diagnostics so
SIMATIC HMI WinCC V7.2 WinCC: Installation / Release Notes System Manual Online help printout 07/2013 A5E32316184-AB WinCC Release Notes 1 What's New in WinCC 2 . To support you in protecting your system, WinCC offers a structured user management: Protect your system against unauthorized access.
SIMATIC HMI WinCC V7.4 SP1 WinCC: Configurations System Manual Print of the Online Help 02/2017 A5E40842153-AA Multi-User Systems 1 File Server 2 WinCC ServiceMode 3 Redundant Systems 4. . WinCC: Configurations System Manual, 02/2017, A5E40842153-AA 5. 1.2 Client/Server Systems in WinCC
SIMATIC HMI WinCC V7.2 WinCC/WebNavigator System Manual Print of the Online Help 07/2013 A5E32316269-AB WinCC/WebNavigator Installation Notes 1 WinCC/WebNavigator
5. SIMATIC WINCC (SYSTEM PARAMETERS) 5.1 Do not use the WinCC DiagAgent (CCDiagAgent) application in production systems WinCC DiagAgent (CCDiagAgent) is used to control and diagnose Simatic WinCC, operating system, and DBMS. By default, the application does not require authorization, which may allow a remote attacker to
WinCC V7.4 SP1 SIMATIC S7-1200: up to 64 connections Supports full-text alarms - in the same way as WinCC Runtime Professional V14 Supports the S7-1500 software controller (S7-1507S) For more information, please refer to the following application example: Joint Operation of WinCC V7 or WinCC V14/15 RT Prof. and Software Controller
