ModusOne. ModusOne Setup. Version: 5.2

Transcription

1 ModusOne ModusOne Setup Version: 5.2 Written by: Product Documentation, R&D Date: February 2013

2 2012 Perceptive Software. All rights reserved ModusOne is a trademark of Lexmark International Technology SA, registered in the U.S. and other countries. Perceptive Software is a stand-alone business unit within Lexmark International Technology SA. All other brands and product names mentioned in this document are trademarks or registered trademarks of their respective owners. No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, photocopying, recording, or any other media embodiments now known or hereafter to become known, without the prior written permission of Perceptive Software.

3 Table of Contents Technical Specifications... 1 Update... 2 Update from ModusOne to ModusOne Backward Compatibility... 6.Net Setup... 6 General... 6 Starting the Installation... 7 Installation Procedure... 7 ModusOne Setup... 7 Windows Operating System... 7 Start the Installation... 7 Installation Procedure... 7 Permission Configuration... 8 Restart Windows... 8 User Language... 9 Choose the User Language... 9 Help Files Odin/MWS Database Setup Oracle MS SQL Server Repository Setup General Starting the Installation Installation Procedure Modify ModusOne Configuration General Special Settings for Windows Server 2008 / Windows Modify UserRepository.config Modify Modus_MWS.exe.config Specify Normal.dotm Modify ModusClient.exe.config Modify ModusStudio.exe.config Start the ModusOne Core Service iii

4 Table Of Contents Start Modus Studio Enter Connection Data for the Odin/Mws Database in the Configuration Start ModusOne Services iv

5 Technical Specifications Server Hardware Min. 2 CPUs with 2 GHz Min. 4 GB RAM Max. 3 GB available hard disk space for the installation of: -.Net Framework 3.5 SP1 - ModusOne complete Further hard disk space depending on the volume of documents Client Hardware Pentium D or higher Min. 512 MB RAM for the Modus Client Min. 2 GB RAM for the Modus Studio Max. 3 GB available hard disk space for the installation of: -.Net Framework 3.5 SP1 - ModusOne complete (Client 40 MB) - Microsoft Word Supported Operating Systems Windows XP SP3 Windows Vista SP2 Windows 7 SP1 Windows 2003 Server SP2 Windows 2003 Server R2 SP2 Windows 2008 Server SP2 Windows 2008 Server R2 SP1 Note for 64bit Systems: On a 64bit System, ModusOne is executed in 32bit compatibility mode(wow64). Supported Databases MS Sql-Server version 2005, 2008 and 2008 R2 Oracle version 10g and 11g. The installation of the 32bit Oracle client is necessary for the Modus server and the Modus Studio to access an Oracle database. Supported Word Versions Word 2007 SP1 with installed VBA Word 2010 with installed VBA 1

6 Supported LDAP Products Active Directory Novell edirectory SUN Directory Server Oracle Internet Directory Open LDAP Microsoft ADAM (Active Directory Application Mode) Virtualization Our applications support deployment in virtual environments running the operating systems mentioned above as long as these operating systems themselves have been officially approved for use in a virtual environment. The only prerequisite for deployment is that virtual environments are correctly configured. Virus Scanners Virus scanner activities can have adverse effects on ModusOne production environments. These adverse effects may result in reduced processing performance or even in the termination of critical transactions. To rule out the eventuality of disruption to operations, it is imperative that the effective range of virus scanner activity is configured to ensure as minimal an impact as possible. Update Update from ModusOne to ModusOne Complete the following steps in the order stated to update an existing ModusOne Version installation to Version Close applications ModusOne Client / ModusOne Studio Close the desktop program. ModusOne Server Close all ModusOne Studios and Clients accessing the Modus Server. Stop all ModusOne Windows services. 2. Run Update520.exe ModusOne Client / ModusOne Studio / ModusOne Server Execute the file Update520.exe - the following actions will run automatically: All files in the Modus program directory with the suffix.config are saved to the directory Admin/Update520/Backup. 2

7 ModusOne setup is configured to prevent existing configuration files in the program directory from being overwritten. If a configuration file should be overwritten, it can be restored from the backup directory. To ensure the following configuration files are updated, they are deleted from the program directory: - ModusSuite.Runtime.ConsoleHost.exe.config - ModusSuite.Runtime.WindowsServiceHost.exe.config - MonalisaEngine.exe.config - RepositorySetup.exe.config A folder named Update520 is created below the Admin directory containing the following files: - MSSql_Mws_Update_510_To_520.sql - MSSQL_Odin_Update_510_To_520.sql - MSSql_Rep_DB_Schema_Update_510_To_520.sql - ORA_Mws_Update_510_To_520.sql - ORA_Odin_Update_510_To_520.sql - Ora_Rep_Create_Schema_Update_510_To_520.sql - restoreconfiguration.cmd - updateconfiguration.cmd Logging The following log files are created: - Config_Restore-Log.txt - Config_Backup-Log.txt These files can be found in the directory %modusdir%\admin\update520\backup. Alternative: Complete the following steps if Update520.exe does not function as described above: 1. Unpack the content of the zip file Update520.zip in the Modus program directory so that the directory structure described above is created. 2. Change to the folder Admin/Update520/Backup and execute the command file ModusOne520.Config-Saver.cmd. 3. Run setup ModusOne Client / ModusOne Studio / ModusOne Server Depending on the operating system installed, complete one of the following actions: Operating System Windows Server 2008 / Windows 7 / Windows Vista: Operating System Windows Server 2003 / Windows XP: Run the file ModusOneSetup2008.msi. Run the file ModusOneSetup.msi Please note: When prompted, enter the path to the existing ModusOne version as the installation directory in the setup dialog. After running the MSI file all exe-files and dlls have been updated to version Unattended setup for ModusOne Client 3

8 It is possible to start the ModusOne MSI file with parameters so that no user interaction is required. Command switch to install the client: msiexec.exe /i "c:\modusonesetup.msi" /L*V "%Temp%\setup.log" /passive ADDLOCAL="ModusBasic,ModusClient,x86Components" APPLICATIONFOLDER="c:\modus" The following entries must be modified for each individual customer environment: /i "c:\modusonesetup.msi" Name of the ModusOne MSI file APPLICATIONFOLDER The directory (path) ModusOne is to be installed to 4. Updating the ModusOne Configuration ModusOne Client / ModusOne Studio / ModusOne Server Change to the folder Admin\Update520 and run the following command file: restoreconfiguration.cmd: Restores ModusOne configuration files saved when executing Update520.exe or ModusOne520-Config-Saver.cmd. 5. Replace renamed ModusOne exe-files with new versions ModusOne Client / ModusOne Studio / ModusOne Server If you have copied and renamed the files ModusStudio.exe or ModusClient.exe in your environment, you will have to replace these copies with newer versions from this release. Example: You have renamed ModusStudio.exe to ModusStudio_TST.exe. Please replace the file ModusStudio_TST.exe with ModusStudio.exe from Release This can be done using the following DOS copy command: copy ModusStudio.exe ModusStudio_TST.exe Replace ModusSuite.Runtime.WindowsServiceHost.exe If you are using Modus processes as Windows services you will have copied the file ModusSuite.Runtime.WindowsServiceHost.exe and renamed it. Please replace the renamed exe-file with the file ModusSuite.Runtime.WindowsServiceHost.exe from Release as this file has been modified. Example: To run Odin processes you have copied and renamed the file ModusSuite.Runtime.WindowsServiceHost.exe to OdinService.exe and registered it as a Windows service. Please replace the file OdinService.exe with the new file ModusSuite.Runtime.WindowsServiceHost.exe from Release This can be done using the following DOS copy command: 4

9 copy ModusSuite.Runtime.WindowsServiceHost.exe odinservice.exe Hint: To keep administration time for later updates to a minimum, we recommend putting all copy commands in a single cmd-file. 6. Updating Modus database schemas ModusOne Server Please note: We recommend backing up all databases before updating their schemas. Preconditions: The following SQL scripts require schema version or a more recent patch. The SQL scripts are designed to be run more than once on the same schema without problems. Odin DB-Schema Please run the following SQL scripts on all Odin databases to update the schema: For Oracle databases Admin\Update520\ORA_Odin_Update_510_To_520.sql For SQL Server databases Admin\Update520\MSSql_Odin_Update_510_To_520.sql MWS DB-Schema Please run the following SQL scripts on all MWS databases to update the schema: For Oracle databases Admin\Update520\ORA_Mws_Update_510_To_520.sql For SQL Server databases Admin\Update520\MSSql_Mws_Update_510_To_520.sql Repository DB-Schema Please run the following SQL script(s) on all Modus Repository databases to update the schema: For Oracle databases Admin\Update520\Ora_Rep_Create_Schema_Update_510_To_520.sql Admin\Oracle\Ora_Rep_CreatePackage.sql For SQL Server databases Admin\Update520\MSSql_Rep_DB_Schema_Update_510_To_520.sql 7. Update translations ModusOne Client / ModusOne Studio / ModusOne Server 5

10 If ModusOne is run in a language other German, the corresponding language resources must be updated. Download the required files from the directory /ModusOne/V5_2_0/LanguageResources/ on the Modus FTP Server (extranet.modus-suite.net). For more information, see chapter Choose the User Language. 8. Update Modus Web Client The signature certificate for the ModusWebClient has been modified. To ensure the automatic update functions correctly, please uninstall a previously installed Out-of- Browser Client and reinstall it fresh. You also need to install the new certificate to be able to use Word automation when launching the ModusWebClient from a browser. To do this, execute the file ModusOneSL5Setup.msi on each individual client computer. Backward Compatibility Please note: Objects in ModusOne 5.2 systems are not compatible with earlier versions. For this reason, it is not possible to transfer objects from a Version 5.2 repository to systems based on older repository versions such as 5.1 or 5.0.4, for example..net Setup General This setup only has to be run if.net Framework 3.5 SP1 is not already installed. Note for the Windows 2008 Server family Windows Server 2008 R2 already contains.net Framework 3.5 Service Pack 1. Windows Server 2008 contains.net Framework 3.0 Service Pack 1, which needs to be extended with the features in.net Framework 3.5 SP1 by running the.net Framework installation package. Important: In both cases, the.net Framework features have to be activated first. This is done either in the server manager GUI in the Features section or by running the command at the command line servermanagercmd -i Net-Framework If the Application server role is already installed on the server on which ModusOne will be installed,.net Framework will already have been activated. 6

11 Starting the Installation Download the file DotNetFX35SP1.zip from the Modus Extranet and unpack it. Start the installation by double-clicking the file dotnetfx35setup.exe in this folder. Installation Procedure 1. License terms In the first window, you must confirm that you agree to the license agreement for the installation to start. The download indicated at the bottom of the window will not start because the required files are already available. This means that the programme can be installed without a network connection. 2. Installation status The below window informs you about the installation's progress. 3. Completing the Installation The last window confirms the successful installation. ModusOne Setup Windows Operating System Operating System Windows Server 2008 / Windows 7 /Windows Vista Use the file ModusOneSetup2008.msi to install ModusOne. Other Operating systems Use the file ModusOneSetup.msi to install ModusOne. Start the Installation Start the installation by double clicking the file ModusOneSetup.msi or ModusOneSetup2008.msi. Setup first checks whether.net Framework 3.5 is installed. If it is not installed, a corresponding message is displayed and setup is terminated. Run.Net Setup before installing ModusOne. Installation Procedure 1. Choose the components In this step, you will choose the components you want to install. You can choose from the following components: Components Contents 7

12 ModusOne Basic System ModusOne Studio ModusOne Client ModusOne Server This component is always required and cannot be removed from the installation. Contains the complete design environment that is needed by Modus administrators. These components enable employees to create, forward and print documents. Installs the server components. Click the Browse button to change the default installation directory. Important: Avoid installing Modus in a directory that contains parentheses (e.g. 'C:\Program Files (x86)'). Several versions of the Oracle client do not correctly parse directories that contain parentheses. The following error message is displayed: ORA 'TNS:could not resolve service name'. (See also Oracle error # or Oracle Note ) 2. Start the Installation In the next step, you will start the installation by clicking the button Install. 3. Status display The status provides information about the installation's progress. 4. Completing the Installation The last window confirms the successful installation of ModusOne. Permission Configuration On the computer that is running the ModusOne server services, the following security settings need to be made for the ModusOne programme directory: The user group Users must be assigned Full control. No special permissions are required for computers on which only Modus Client and/or Modus Studio is installed. No manual changes have to be made. Restart Windows Restart Windows so the environment variable ModusDir that was created by the Modus installation is available in Windows services. You need to restart the system because changes to environment variables are not visible until Windows is restarted. 8

13 See also: Microsoft Support, Article ID: User Language Choose the User Language The user interface of the ModusOne Studio and Client is currently available in the following languages: German (default) English (GB) English (US) French Italian Dutch Portuguese (BR) Spanish Follow the below steps to choose a language other than German: 1. Download files From the directory /ModusOne/V5_2_0/LanguageResources/ on the Modus FTP server (extranet.modus-suite.net) download the appropriate zip file: EN-GB_ModusOne.zip for English (GB) EN-US_ModusOne.zip for English (US) FR_ModusOne.zip for French IT_ModusOne.zip for Italian NL_ModusOne.zip for Dutch PT_ModusOne.zip for Portuguese ES_ModusOne.zip for Spanish 2. Create subdirectories In the Studio or Client installation directory, create the directory: en-gb for English (GB) en-us for English (US) fr for French it for Italian nl for Dutch pt-br for Portuguese es for Spanish 9

14 Example: Modus was installed in the directory c:\program files\modusone and the English (US) language resources are to be used. Create the directory c:\program files\modusone\en-us 3. Extract files from the zip file Extract the contents of the zip file to the directory you created in Step Set the language for the Odin views To display the strings in English (GB), go to the table ODIN_SETTING and change the value in the field OD_ISO_LANG_CODE to en-gb. To display the strings in English (US), change the value in the field OD_ISO_LANG_CODE to enus. To display the strings in French, change the value in the field OD_ISO_LANG_CODE to fr. To display the strings in Italian, change the value in the field OD_ISO_LANG_CODE to it. To display the strings in Dutch, change the value in the field OD_ISO_LANG_CODE to nl. To display the strings in Portuguese, change the value in the field OD_ISO_LANG_CODE to pt-br. To display the strings in Spanish, change the value in the field OD_ISO_LANG_CODE to es. 5. Start programs If you wish to use ModusOne in a different language to the one defined in the Windows system settings, you must start ModusOne Studio and ModusOne Client with a command line switch. Sample files can be found on the Modus FTP server in the directory /ModusOne/V5_2_0/LanguageResources/: DE_ModusClient.cmd / DE_ModusStudio.cmd EN-GB_ModusClient.cmd / EN-GB_ModusStudio.cmd EN-US_ModusClient.cmd / EN-US_ModusStudio.cmd ES_ModusClient.cmd / ES_ModusStudio.cmd FR_ModusClient.cmd / FR_ModusStudio.cmd IT_ModusClient.cmd / IT_ModusStudio.cmd NL_ModusClient.cmd / NL_ModusStudio.cmd Help Files ModusOne help files can be downloaded from the directories /ModusOne/V5_2_0/CurrentHelp/DE 10

15 /ModusOne/V5_2_0/CurrentHelp/EN-GB /ModusOne/V5_2_0/CurrentHelp/EN-US /ModusOne/V5_2_0/CurrentHelp/ES /ModusOne/V5_2_0/CurrentHelp/FR /ModusOne/V5_2_0/CurrentHelp/IT /ModusOne/V5_2_0/CurrentHelp/NL /ModusOne/V5_2_0/CurrentHelp/PT-BR on the Modus FTP server (extranet.modus-suite.net). Odin/MWS Database Setup Oracle Database user The Oracle user must have the following roles and permissions: Roles Connect Resource System permissions Create table Create view Create procedure Create sequence A corresponding Oracle user can be created by running the script Ora_Odin_CreateUser.sql. Both scripts can generate error messages such as ORA Table or View does not exist ORA Sequence does not exist These messages can be ignored. They occur because the SQL scripts contain DROP instructions for objects that do not exist in the database. Database schema The directory \Admin\Oracle contains the files Ora_Odin5.sql and Ora_Mws.sql, which are used to create the Odin and Mws schemas. MS SQL Server Database schema 11

16 The directory \Admin\MS-SQL contains the files MSSql_Odin5.sql and MSSql_Mws.sql which are used to create the Odin and MWS schemas. Important: Run both of the scripts from the SA administrator account! You may have to create SQL Server databases to run the scripts. You can give the databases any name you want. Write down the name. You will need it later during the configuration. Database user A database user with the following rights must be created for each database used. This user enables subsequent access to the ModusOne schemas mentioned above: Object Tables Views Stored Procedures Rights INSERT, SELECT, UPDATE, DELETE SELECT EXECUTE The directory \Admin\MS-SQL contains an SQL script template MSSql_CreateUser.sql. This script can be tailored to create a user and SQL Server login for a ModusOne database on an SQL Server. The script contains standard parameters to set values for login name, password and default database for the DB user. For ease of use, simply run the script in SQL Server Management Studio (SSMS). All the information needed on how to perform this action is contained in the script header. The script must be used to create a login for every database catalog used. Only one login is required if both schemas are created in the same database catalog. Repository Setup General The repository setup installs a first Modus system on a database. Oracle and MS SQL Server are currently supported. Important: This application must be run on the computer on which the ModusOne server services will be run. 12

17 Run the repository setup from a user account that has write permission for the ModusOne installation directory! Before running the repository setup, the following must be in place: License If you do not have a valid license, please send an to ModusOne support: support@perceptivesoftware.com and ask for the license file for your environment. Copy the license file to the ModusOne programme directory and make sure the file name is Modus.lic. MS SQL Server An empty database for the Modus repository DB schema. The SQL Servers authentication mode must be active. The SA users password is used to run setup. Oracle Run the Ora_Rep_CreateUser.sql script to create an Oracle user for the database in which the Modus DB schema is to be installed. The script is in the Admin\Oracle\ directory. You must have SYSDBA permissions to run the script. Starting the Installation To start the repository setup, run the RepositorySetup file in the ModusOne directory. Installation Procedure 1. Select the database First define whether the ModusOne repository is to be installed on an SQL Server or an Oracle database. 1.1 SQL Server The following information is needed to install the repository on an SQL Server: Server: Database: User: Password: Name of the SQL Server instance Name of the SQL Server database in which the ModusOne repository database schema is to be installed Database user that is used to create the database schema. Please log in as SA user! Database users password Click Test Database Connection to test whether a connection to the database can be established using the entered data. 13

18 1.2 Oracle To install the repository on an Oracle database, enter the required information in this window. Server: User: Password: SqlPlus Path: Name of the Oracle server instance. Database user that is used to create the database schema. Please use a user that was created by the script Ora_Rep_CreateUser.sql because the user must have specific permissions. Password of the database user Enter the path to the Oracle application SqlPlus.exe. The setup routine will automatically look for this path. SqlPlus.exe is needed to execute the Oracle SQL scripts. Click Test Database Connection to test whether a connection to the database can be established using the entered data. 2. Create the Modus System In the next step, specify the name and the ID of the Modus system to be created. Enter a unique ID for the new system and write it down. You will need it later during the configuration. 3. Start the installation Start the installation in the last window by clicking on the Start Installation button. The information in the log file window informs you about the installations progress. If you are running the installation on an Oracle database, the SqlPlus output is written to the Ora_Rep_Create_Schema.log Ora_Rep_CreatePackage.log Ora_modus_rep_lookup.log files. These files are in the ModusOne programme directory and should be checked for error messages. Modify ModusOne Configuration General After the repository setup has successfully completed, the System Object ID that was entered during the repository setup has to be entered in a number of configuration file. 14

19 Special Settings for Windows Server 2008 / Windows 7 Please note that the program ModusConfig must be run with explicit administrator permissions in order to be able to save any changes made. To do this, perform the following steps: 1. Open the Explorer and change to the ModusOne installation folder. 2. Select the file ModusConfig.exe and then select the context menu item Run as administrator. The application now has explicit administrator permissions and therefore is able to execute write access on the ModusOne installation folder. User Account Control in Windows 7 If User Account Control, UAC is activated under Windows 7, programs are always run using the permissions of a standard user, even if the user is an administrator. This is why a user does not have the rights assigned to the Administrator role when ModusOne Studio is started. To grant the user the rights of the Administrator role, ModusOne Studio must explicitly be started with run as Administrator or UAC must be deactivated. Modify UserRepository.config 1. Start ModusConfig from the Modus programme directory. 2. Select the menu item File - Open configuration to open the UserRepository.config file. 3. In the upper table, choose System Object ID and enter the system object ID you entered during setup. 4. Select the menu item File - Save configuration to save your changes. Modify Modus_MWS.exe.config 1. Start ModusConfig from the Modus programme directory. 2. Select the menu item File - Open configuration to open the modus_mws.exe.config file. 3. In the upper table, choose System Object ID and enter the system object ID you entered during setup. 4. Select the menu item File - Save configuration to save your changes. Specify Normal.dotm Copy Normal.dotm to the Modus installation directory that you created in the step Choose components. Modify ModusClient.exe.config 1. Start ModusConfig from the Modus programme directory. 2. Select the menu item File - Open configuration to open the ModusClient.exe.config file. 3. In the upper table, choose Odin View System Object ID and enter the system object ID you entered during setup. 15

20 4. The corresponding URL will have to be changed based on whether a service is running on a different computer. Choose the desired service and enter the changed URL. The change usually consists of replacing the local IP address (or localhost) with the IP address (or hostname) of the server on which the service is run. Specifically, the URLs localhost entry needs to be changed on the specific server host name/ip address for the following entries: - Security Token Service - Login Service - Modus User Service - Modus Web Service Repository - Modus Web Service - Data Provider Service - Odin Web Service - License Service Example: If the Modus Server service is on the ModServer host, the Security Token Services URL has to be changed from to 5. Select the menu item File - Save configuration to save your changes. Modify ModusStudio.exe.config 1. Start ModusConfig from the Modus programme directory. 2. Select the menu item File - Open configuration to open the ModusStudio.exe.config file. 3. The corresponding URL will have to be changed based on whether a service is running on a different computer. Choose the desired service and enter the changed URL. The change usually consists of replacing the local IP address (or localhost) with the IP address (or name) of the server on which the service is run. ' Specifically, the URLs localhost entry needs to be changed on the specific server host name/ip address for the following entries: - Security Token Service - Login Service - Data Provider Service - Odin Web Service - Repository Service - Modus Web Service Repository - License Service Example: If the Modus Server service is on the ModServer host, the Security Token Services URL has to be changed from 16

21 to 4. Select the menu item File - Save configuration to save your changes. Start the ModusOne Core Service The configuration has been changed such that the ModusOne service can start. Open Windows Services and start the Modus_Core service. Start Modus Studio If the service started successfully, Modus Studio can be started: Start -> ModusOne -> ModusOne Studio Tip: If Modus Studio is being started for the first time, important controls, such as the Navigator, are not visible. The Navigator and other controls are displayed by clicking on the respective buttons in the Studio - Windows ribbon. The Navigator is displayed by clicking on the globe: Enter Connection Data for the Odin/Mws Database in the Configuration In Modus Studio, click the Select System button at the top left to select the active system. This displays the Select System dialog in which you can enter your selection. In Studio, go to the Administration tab and click the DB Alias Administration icon. The DB aliases Mws and Odin are displayed in the DB alias administrator interface. The Mws or Odin database connection is configured as follows: 1. Double-click Mws or Odin. The dialog for the DB connection settings opens. 2. Select the appropriate DB product in the Data Provider field: - Native SQL for MS SQL Server or - Microsoft Oracle for an Oracle database 3. In the SQL Template field, click the Default Value button the default value is read from the configuration and entered. 4. In the SQL Field Template field, click the Default Value button the default value is read from the configuration and entered. 5. In the Connection String area, click the button with the ellipsis. The product-specific connection dialog opens. 6. Enter the connection information for the DB user previously created for the respective schema using the script Ora_Odin_CreateUser.sql or MSSql_CreateUser.sql. 17

22 7. Make sure the option Allow saving password is checked. 8. Click OK to confirm your entry. 9. Make the described change for the Odin and Mws DB alias. 10. Save your changes in the DB alias administrator. Start ModusOne Services Open Windows Services and start the following services: Modus_Core Modus_Mws Modus_Ows 18

23 Index B Backward Compatibility... 6 C Choose... 9 Config... 15, 16 Configuration E Enter Connection Data G General... 6, 12, 14 H Help Files I Installation... 7, 13 Installation Procedure... 7, 13 M ModusOne Core Service MS SQL Server Mws Database N Normal.dotm O Odin Oracle P Permission Configuration... 8 R Restart Windows... 8 S Special Settings Start... 7, 17 Start Modus Studio Start ModusOne Services T Technical Specifications... 1 U User Language... 9 W Windows Windows Operating System... 7 Windows Server