SDL Trados Studio 2017 SR1. Enterprise Deployment Guide

Transcription

1 SDL Trados Studio 2017 SR1 Enterprise Deployment Guide

2 SDL (LSE:SDL) is the global innovator in language translation technology, services and content management. With more than 20 years of experience, SDL delivers transformative business results by enabling powerfully nuanced digital experiences with customers around the world. Are you in the know? Find out why 79 out of the top 100 global brands use SDL at SDL.com and follow us on Twitter, LinkedIn and Facebook. Copyright 2017 SDL plc. All Rights Reserved. All company product or service names referenced herein are properties of their respective owners.

3 Enterprise Deployment Guide SDL Trados Studio 2017 SR1 July 2017

4 ii Enterprise Deployment Guide

5 A Legal notice

6 0 Legal notice Copyright and trademark information relating to this product release. Copyright SDL Group. SDL Group means SDL PLC. and its subsidiaries and affiliates. All intellectual property rights contained hereinarethesoleandexclusiverightsofsdlgroup.allreferencestosdlorsdlgroupshallmeansdl PLC. and its subsidiaries and affiliates details of which can be obtained upon written request. All rights reserved. Unless explicitly stated otherwise, all intellectual property rights including those in copyright in the content of this website and documentation are owned by or controlled for these purposes by SDL Group. Except as otherwise expressly permitted hereunder or in accordance with copyright legislation, the content of this site, and/or the documentation may not be copied, reproduced, republished, downloaded, posted, broadcast or transmitted in any way without the express written permission of SDL. SDL Trados Studio is a registered trademark of SDL Group. All other trademarks are the property of their respective owners. The names of other companies and products mentioned herein may be the trademarks of their respective owners. Unless stated to the contrary, no association with any other company or product is intended or should be inferred. This product may include open source or similar third-party software, details of which can be found by clicking the following link: Acknowledgments on page 0. Although SDL Group takes all reasonable measures to provide accurate and comprehensive information about the product, this information is provided as-is and all warranties, conditions or other terms concerning the documentation whether express or implied by statute, common law or otherwise (including those relating to satisfactory quality and fitness for purposes) are excluded to the extent permitted by law. To the maximum extent permitted by law, SDL Group shall not be liable in contract, tort(including negligence or breach of statutory duty) or otherwise for any loss, injury, claim liability or damage of any kind or arising out of, or in connection with, the use or performance of the Software Documentation evenifsuchlossesand/ordamageswereforeseen,foreseeableorknown,for:(a)lossof,damagetoor corruption of data,(b) economic loss,(c) loss of actual or anticipated profits,(d) loss of business revenue, (e)lossofanticipatedsavings,(f)lossofbusiness,(g)lossofopportunity,(h)lossofgoodwill,or(i)any indirect, special, incidental or consequential loss or damage howsoever caused. All Third Party Software is licensed"as is." Licensor makes no warranties, express, implied, statutory or otherwise with respect to the Third Party Software, and expressly disclaims all implied warranties of non-infringement, merchantability and fitness for a particular purpose. In no event will Licensor be liable for any damages, including loss of data, lost profits, cost of cover or other special, incidental, consequential, direct, actual, general or indirect damages arising from the use of the Third Party Software or accompanying materials, however caused and on any theory of liability. This limitation will apply even if Licensor has been advised of the possibility of such damage. The parties acknowledge that this is a reasonable allocation of risk. Information in this documentation, including any URL and other Internet Web site references, is subject to change without notice. Without limiting the rights under copyright, no part of this may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means(electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of SDL Group. 4 Enterprise Deployment Guide

7 Contents 1 Legalnotice Introduction ListofcomponentsinSDLTradosStudio Automaticupdates Prerequisites Standard(non-silent)SDLTradosStudiodistributionpackage Non-IncludedPrerequisites IncludedPrerequisites InstallingSDLTradosStudiofromthecommandline DeployingSDLTradosStudio2017withactivedirectory Creatingadistributionpoint Creatingdistributionpointsforprerequisites CreatingdistributionpointsforSDLTradosStudio Configuringactivedirectory Creatinganautomaticinstallpolicyforeachinstallationpackage SDLTradosStudio2017silentinstallation Thingstocheckbeforestartingsilentinstallation Microsoft.NETFramework MicrosoftVisualC++2008RedistributableSP1withATLUpdate MicrosoftVisualC++2010Redistributable MicrosoftVisualC++2013Redistributable MicrosoftOffice OpenXMLSDK2.5ForMicrosoftOffice SDLTradosStudio SDLTradosLegacyCompatibilityModule SDLWorldServerComponents SilentRemoval SummaryforReference Locationsforfilescreatedduringinstallation Pre-configuringsettingsduringinstallation Enterprise Deployment Guide v

8 Perusersettings Enteringuserdetails Specifyingtheuserprofile Customerfeedbacksettingprompt Deployingthesampleproject Permachinesettings SpecifyingaLicenseServerduringinstallation Disablingthetelemetricscustomerfeedbacksystem DisablingAutoupdate Acknowledgments vi Enterprise Deployment Guide

9 1 Introduction

10 1 Introduction This document contains information for administrators wishing to perform a mass deployment of SDL Trados Studio, both in non-silent and silent mode. Given the variety of systems management products, the information provided in this document is limitedtoadescriptionofwhatneedstobedoneratherthanhowtodoitassuchinformationvaries significantly from product to product. However, this document does provide an example of how Trados Studio can be installed from Active Directory. A silent installation distribution is also available, and full details on silent installation are provided in this document. 2 Enterprise Deployment Guide

11 2 List of components in SDL Trados Studio 2017

12 2 List of components in SDL Trados Studio 2017 TobetterunderstandbothinstallationoptionsforSDLTradosStudio2017,itisusefultobeabletorefer to the exact list of all components required by Trados Studio(referred to as"prerequisites") as well as the Trados Studio 2017 itself. Name Type File Name Comments Microsoft.NET Framework Microsoft Visual C Redistributable SP1 Microsoft Visual C Redistributable Microsoft Visual C Redistributable Microsoft Office 2003 Primary Interop Assemblies Microsoft Office 2007 Primary Interop Assemblies Microsoft Open XML SDK v2.5 SDL Trados Studio 2017 Core Installer SDL Trados Legacy Compatibility Module SDL WorldServer Components Prerequisite NDP452-KB x86-x64- AllOS-ENU.exe Required for the Microsoft.NET components in SDL Trados Studio. Prerequisite 2008_SP1_vcredist_x86.exe Required for the C++ components in Trados Studio. Prerequisite 2010_vcredist_x86.exe Required for the C++ components in Trados Studio. Prerequisite 2013_vcredist_x86.exe Required for the C++ components in Trados Studio. Prerequisite o2003pia.msi This is o nly needed if Office 2003willbeusedwith Trados Studio. Office 2003 must be installed first for this component to be installed. Prerequisite o2007pia.msi This is only needed if Office 2007willbeusedwith Trados Studio. Office 2007 must be installed first for this component to be installed. Prerequisite OpenXMLSDKV25.msi Required for the *.sdlxliff Converter add-on for Trados Studio SDL Installer TranslationStudio5.msi SDL Installer TradosCompatibility2.msi Main installer for Trados Studio This is required for supporting the legacy file formatssuchasttxorthe translation memory format TMW. SDL Installer WorldServerComponents.msi This is required to connect to SDL WorldServer and to handle WorldServer packages. 4 Enterprise Deployment Guide

13 3 Automatic updates

14 3 Automatic updates SDL Trados Studio 2017 has an automatic update feature to keep the software up-to-date with all relevant enhancements as well as security and bug fixes. This feature involves contacting an update server at SDL, downloading an update and installing the downloadedupdate.ifyouwishtodisablethisfeature,youcandosobyusingagrouppolicyorona peruserbasis.formoreinformationonthis,refertothesoftwareupdateschapterinthesdltrados Studio Installation Guide that describes how to configure the Studio5AutoUpdate.adm file for use as a group policy. 6 Enterprise Deployment Guide

15 4 Prerequisites

16 4 Prerequisites Asyoucanseefromthelistabove,SDLTradosStudiodependsonanumberofthirdpartyproductsthat must be present on the target computers. If required, questions about deploying these products should be addressed to their respective manufacturers(microsoft) Answers will usually be found on the manufacturers' websites or knowledge bases. Note: The silent distribution package described later in this document(see" SDL Trados Studio 2017 Silent Installation") includes all prerequisites, including the Microsoft.NET Framework The standard Trados Studio Distribution Package behaves as described below under" Standard(Non-Silent) SDL Trados Studio Distribution Package". 8 Enterprise Deployment Guide

17 5 Standard(non-silent) SDL Trados Studio distribution package

18 5 Standard(non-silent) SDL Trados Studio distribution package In this section, we refer to the non-silent distribution package as"standard SDL Trados Studio distribution package". Use the information in this section to understand the basic workings of the standard Trados Studio installer when run by an administrator or end-user in non-silent mode. This information will be useful when looking at Active Directory as well as installing the silent distribution package later in this document. Non-Included Prerequisites The Microsoft.NET Framework and its direct dependency, the Windows Installer 4.5, are not included in the standard(non-silent) SDL Trados Studio 2017 distribution package. Normally, the setup executable(setup.exe) inside the standard Studio distribution package will download and install them if they are not already present on the target system. However, the setup program setup.exe, being an executable with downloading capabilities, is not necessarily suitable for mass deployment. Therefore, SDL strongly recommend that the system administrator downloads the prerequisites and ensures that they are installed on the target machines before installing the remaining components. Included Prerequisites The other prerequisites are all contained within the standard SDL Trados Studio 2017 distribution package. The installation package file name is SDLTradosStudio2017_[SRx_]nnnn.exe where x is the service release number and nnnn is the build number. This executable file is a self-extracting archive made with WinRar. Youcanunpackitbyeitherusingadecompressiontooltoextractthefilesorbyrunningitasanend user would, and then cancelling the installation process at the prompt requiring the user to acknowledge the end-user license agreement. After decompression, you will find the extracted files in the following folder: %ALLUSERSPROFILE%\Package Cache\SDL\SDLTradosStudio2017 This folder will typically contain the following folders and files: 10 Enterprise Deployment Guide

19 Standard(non-silent) SDL Trados Studio distribution package 5 If the compression utility used in your organization does not handle rar archives, a free utility called unrar.exe is available at The prerequisites installed by the standard SDL Trados Studio distribution package are the following: Microsoft Visual C Redistributable SP1 Microsoft Visual C Redistributable Microsoft Visual C Redistributable MicrosoftOffice2003PrimaryInteropAssemblies.ThisisonlyneededifOffice2003willbeused with Trados Studio. Office 2003 must be installed first for this component to be installed. Microsoft Office 2007 Primary Interop Assemblies. This is only needed if Office 2007 will be used with Trados Studio. Office 2007 must be installed first for this component to be installed. MicrosoftOpenXMLSDKv2.5 The order of installation is not important except that Microsoft Office, if it is used, must be installed before any of the MS Office Primary Interop Assemblies are installed. Note that these files are now in the folder C:\ProgramData\Package Cache\SDL\Dependencies AlsonotethatTradosStudionolongerneedsJavasince2014SP2. Enterprise Deployment Guide 11

20 5 Standard(non-silent) SDL Trados Studio distribution package Installing SDL Trados Studio from the command line The core SDL Trados Studio installer is a Microsoft Windows Installer Package(MSI) called TranslationStudio5.msi. It can be deployed to a distribution point by means of a standard administrative installation: msiexec /a <path to MSI dir>\translationstudio5.msi TARGETDIR="<path to distribution point dir>" The installation is per-machine and the value of ALLUSERS is hard-coded within the MSI and should not beaddedtothecommandline. You can specify the DESKTOPSHORTCUT=false property to stop the installation from creating a desktop shortcut: msiexec /a <path to MSI dir>\translationstudio5.msi TARGETDIR="<path to distribution point dir>" DESKTOPSHORTCUT=false YoucanalsospecifytheLICSERVERpropertytoaURLtotheSDLlicenseserveronyournetwork.Thiswill enable this feature and stop the licensing dialog prompts. There are no other command-line parameters. Deploying SDL Trados Studio 2017 with active directory It is assumed that the reader is familiar with mass deployment using Active Directory(AD). A basic introduction can be found at Creating a distribution point Create a Distribution Point location on your network and set appropriate permissions for AD deployment. You must use UNC syntax to refer to the distribution point, for example,\\ myserver\ myfolder\ GPSI\ SdlTrados Enterprise Deployment Guide

21 Standard(non-silent) SDL Trados Studio distribution package 5 Creating distribution points for prerequisites SDL Trados Studio relies on several dependencies that need to be installed prior to deployment as described above Most of these are Microsoft Windows Installer packages(msis) that can be placed in distribution points directly, or you can perform an administrative install to a distribution point for them. The C++ redistributable executables are ZIP archives and can be unpacked to the distribution point. For the Microsoft.NET Framework SDL recommends that you read the Microsoft article(see hyperlink below) for more information on best practices for Microsoft.NET deployment in AD contexts. Microsoft.net 4.5.2(deployment guide: Microsoft Visual C Redistributable SP1 Microsoft Visual C Redistributable Microsoft Visual C Redistributable Microsoft Office 2003 Primary Interop Assemblies Microsoft Office 2007 Primary Interop Assemblies MicrosoftOpenXMLSDKv2.5 Creating distribution points for SDL Trados Studio Procedure 1. Create a distribution point for the SDLTradosStudio2017 module by doing an admin install to a network location, for example, msiexec /a TranslationStudio5.msi TARGETDIR=\\myserver\myfolder\GPSI \SdlTrados2017\Studio 2. You will typically also want to apply the latest cumulative update(cu) patch to the distribution point. Note: this action will make the patch irremovable.(see In this example, we apply cumulative update 6 for Trados Studio 2017 SR1. msiexec /a \\MyServer\MyFolder\GPSI\SdlTrados2017\Studio \TranslationStudio5.msi /p TradosStudio msp Subsequent patches would need to be applied to the distribution point and then republished. 3. The Trados Studio distribution package also contains a compatibility module for SDL Trados This is required for supporting the legacy file formats such as*.ttx or the translation memory Enterprise Deployment Guide 13

22 5 Standard(non-silent) SDL Trados Studio distribution package format TMW. Create a distribution point for SDL Trados Legacy Compatibility Module by doing an admin install to a network location, for example, msiexec /a TradosCompatibility2.msi TARGETDIR=\\MyServer\MyFolder\GPSI \SdlTrados2017\Compat 4. The Trados Studio distribution package also contains a separate msi for the SDL WorldServer components. This is required to connect to WorldServer and to handle WorldServer packages. Create a distribution point for WorldServer Components by doing an admin install to a network location, for example, msiexec /a WorldServerComponents.msi TARGETDIR=\\MyServer\MyFolder\GPSI \SdlTrados2017\Worldserver 5. Also, create a distribution point for the SDL Studio Helper module if required by doing an admin install to a network location, for example, msiexec /a SDLStudioHelper.msi TARGETDIR=\\MYServer\MyFolder\GPSI \SdlTrados2017\Helper Configuring active directory In this example, we assume that our test domain controller is a computer running Windows 2012 Server. Other domain controllers may differ slightly. Procedure 1. On the Domain Controller, launch the Active Directory Users and Computers snap-in for Microsoft Management Console(MMC). Create an Organizational Unit(OU) in the Active Directory in which youwishtoplaceyourtestmachine. 14 Enterprise Deployment Guide

23 Standard(non-silent) SDL Trados Studio distribution package 5 2. CreateaTestVM(inourexample,weusedaWindows10machinehostedinHyper-V2012)andjoin it to the domain. Drag the computer account into the OU you created previously. Creating an automatic install policy for each installation package Procedure 1. Open the Group Policy Management MMC snap-in and locate the OU you created for this test. Right-clickontheOUandchooseCreateandlinkaGPOHere. Enterprise Deployment Guide 15

24 5 Standard(non-silent) SDL Trados Studio distribution package 2. Right-click on the link you created and choose Edit. This will open the Group Policy Object Editor. 3. Expand the Computer Configuration/Software Settings/Software Installation node. Right-click on the node and choose New > Package. 16 Enterprise Deployment Guide

25 Standard(non-silent) SDL Trados Studio distribution package 5 4. Enter the UNC path of one of your Distribution Points and choose an assigned installation. Again, it isimportanttouseauncpathandnotbrowsetothelocation. 5. Repeat this for each package you want to deploy automatically. The order of installation can be controlled by the link order in the group policy management tool. Higher link order numbers are installed first: 6. Makesurethepoliciesareenabled.Youarenowreadytorunyourtests. Enterprise Deployment Guide 17

26 5 Standard(non-silent) SDL Trados Studio distribution package 18 Enterprise Deployment Guide

27 6 SDL Trados Studio 2017 silent installation

28 6 SDL Trados Studio 2017 silent installation This section is aimed at administrators using a mass deployment system who need to repackage the modulesinthedistributionandwishtogetinformationonhowtoperformasilentinstallationofsdl Trados Studio SDL provides a distribution that installs silently. Its file name is SDLTradosStudio2017_SRx_nnnn_ Silent.exewherexistheservicereleasenumberandnnnnisthebuildnumber.Youcandouble-clickitor run it from the command line. Log files are created during installation for further reference of the actions taken during silent installation. The log file locations can be found below. In the remainder of this chapter, we document the contents and installation process in more detail to provide a better understanding of the silent installation package. This is designed to help administrators understand whattodoiftheywouldliketorepackagethesilentinstaller. The Studio silent installation package contains a number of individual installation packages. Many of these are third-party products and their manufacturers may provide further information and help in case of questions. Also, some of these third party components may already be installed on the target machines. While not intended to be viewed by end users, you may find the file TranslationStudio. Professional. Suite in the package cache location(%allusersprofile%\package Cache\SDL \SDLTradosStudio 2017) to be useful as it contains details on the packages, such as if they are installed and what conditions are used to detect their installation. Things to check before starting silent installation The installation package file name is SDLTradosStudio2017_SRx_nnnn_Silent.exe where x is the service release number and nnnn is the build number. The package contains installation modules, a"chainer" utility that runs each installation in turn and a bootstrapper(setup.exe) that installs the minimum number of modules required to run the chainer and starts the installation. Procedure 1. EnsurethatthetargetmachinesarerunningonWindows7,WindowsServer2012R2oralater operating system. 2. Extract the installation files by opening the self-extracting installation package with an archive utility capable of handling WinRar archives. If you have no compression utility that can handle rar archives, a free utility called unrar.exe is available at 3. Install the modules listed in the following sections. They are found in the"modules" or"dependencies" subdirectory of the archive. It is important to generate a log when installing silently in case thereareanyerrors.thewindowseventlogcanalsobeusedtodeterminethesuccessorfailureof a silent MSI installation. 20 Enterprise Deployment Guide

29 SDL Trados Studio 2017 silent installation 6 Microsoft.NET Framework It is not available by default on any operating system. The Microsoft.NET Framework is available on Windows Update. About this task This module is installed by the bootstrapper in the standard distribution. It must be installed before usingthetradosstudiochainerifthechaineristobeused.toinstallthismodule: Procedure 1. Run the following command: "<Path todir>\ndp452-kb x86-x64-allos-enu.exe" /q/norestart 2. For Log files, see the Troubleshooting section in the Administrators Guide. Microsoft Visual C Redistributable SP1 with ATL Update Instructions for installing the Microsoft Visual C Redistributable SP1 module. Procedure 1. Run the following command: "<Path todir>\2008_sp1_vcredist_x86.exe" /q ThiscommandreturnsastandardMSIreturncode.Thecommandmaynotworkwhenusedwith CreateProcess() but does work with ShellExecute(). 2. Ifthefirstcommanddoesnotwork,ensurethatthemoduleisrunfromacommandshell: "%COMSPEC%" /c "<Path todir>\2008_sp1_vcredist_x86.exe" /q Log files: %TEMP%\dd_vcredistMSInnnn.txt where nnnn is a 4-digit number. The original file name when downloaded from the Microsoft web site is vcredist_x86. exe. It is renamed in the distribution to avoid clashes with 2005 and 2010 runtimes. Microsoft Visual C Redistributable Instructions on installing the Microsoft Visual C Redistributable module. Enterprise Deployment Guide 21

30 6 SDL Trados Studio 2017 silent installation Procedure 1. Run the following command: "<Path todir>\2010_vcredist_x86.exe" /q /norestart ThiscommandreturnsastandardMSIreturncode.Thecommandmaynotworkwhenusedwith CreateProcess() but does work with ShellExecute(). 2. Ifthefirstcommanddoesnotwork,ensurethatthemoduleisrunfromacommandshell: "%COMSPEC%" /c <Path todir>\2010_vcredist_x86.exe" /q /norestart Microsoft changed the update strategy for C++ runtimes from side by side installations to upgradable installations. That means this command will fail if a version of or higher is already installed.inthiscase,thereshouldbenoneedtoinstallthe2010runtimes. Log files: %TEMP%\Microsoft Visual C x86 Redistributable Setup_<ISODate>_<Time>.html %TEMP%\Microsoft Visual C x86 Redistributable Setup_<ISODate>_<Time>-MSI_vc_red.msi.txt The original file name when downloaded from the Microsoft web site is vcredist_x86. exe. It is renamed in the distribution to avoid name clashes and confusion with 2008 and 2010 runtimes. Microsoft Visual C Redistributable Instructions to install this module. Procedure 1. Run the following command: "<Path todir>\2013_vcredist_x86.exe" /q /norestart ThiscommandreturnsastandardMSIreturncode.Thecommandmaynotworkwhenusedwith CreateProcess() but does work with ShellExecute(). 2. Ifthefirstcommanddoesnotwork,ensurethatthemoduleisrunfromacommandshell: "%COMSPEC%" /c <Path todir>\2013_vcredist_x86.exe" /q /norestart "%COMSPEC%" /c <Path todir>\2013_vcredist_x86.exe" /q /norestart 22 Enterprise Deployment Guide

31 SDL Trados Studio 2017 silent installation 6 Microsoft Office Install Microsoft Office at any time prior to installing the Microsoft Office Primary Interop Assemblies (PIAs). About this task SDL Trados Studio 2017 fully supports all Microsoft Office 2007 and 2010 file formats. An installation of Microsoft Office is required to use the preview features as well as Microsoft Word-based spell checking. Microsoft Word 2003 or later is required for processing RTF-based files and PDF files. Procedure 1. Install Microsoft Office 2003 Primary Interop Assemblies with the following command: if you have Microsoft Office 2003 installed: msiexec /i "<Path todir>\o2003pia.msi" /qn /l*v "<path to logfile>" if you have Microsoft Office 2007 installed: msiexec /i "<Path todir>\o2007pia.msi" /qn /l*v "<path to logfile>" Open XML SDK 2.5 For Microsoft Office Instructions for installing this module. Procedure 1. Run the following command: msiexec /i "<Path todir>\openxmlsdkv2.msi " /qn /l*v "<path to logfile>" SDL Trados Studio Instructions to install this module. Procedure 1. Run the following command: msiexec.exe /i "<Path todir>\translationstudio5.msi" /qn /l*v "<Path to logfile>" Setting the DESKTOPSHORTCUT property to anything other than 1 will prevent creation of a desktop shortcut.ifyoudonotincludetheproperty,thedefaultistocreateashortcut. SettingtheLICSERVERpropertytoaURLtotheSDLlicenseserveronyournetworkwillenablethis feature and stop the licensing dialog prompts. Enterprise Deployment Guide 23

32 6 SDL Trados Studio 2017 silent installation SDL Trados Legacy Compatibility Module Install the Legacy Trados compatibility module to enable Trados 2007 features such as TTX support and TMW updates. Procedure 1. Run the following command: msiexec.exe /i " "<Path todir>\tradoscompatibility2.msi " /qn /l*v "<Path to logfile>" SDL WorldServer Components Install the SDL WorldServer Components. This is required to connect to SDL WorldServer and to handle WorldServer packages. Procedure 1. To install this module, run the following command: msiexec.exe /i "<Path to dir>\worldservercomponents.msi" /qn /l*v "<Path to log file>" Silent Removal By default, SDL Trados Studio should be uninstalled using the Remove suite of products entry in the Add/Remove Programs panel. This command works in non-silent mode. However, this entry will not appear unless you are deploying SDL Trados Studio 2017 using the SDL Trados Studio Chainer. The product packages may need to be removed individually therefore. To silently remove an MSI, you can use the following command: msiexec /x "<path to msi file>"/qn Optionally, you can create an uninstallation log for the removal by appending /l*v " <path to log file> " to the command line. The following packages should be removed: SDL Trados Legacy Compatibility Module for Studio 2017 SDLTradosStudio2017 SDL WorldServer Components 24 Enterprise Deployment Guide

33 SDL Trados Studio 2017 silent installation 6 The prerequisites are third-party products and should not generally be removed, as it is not possible to knowifotherapplicationsonthemachineneedthem.ifyouarecertainthattheyarenotusedby anything else, you may remove them. Summary for Reference Thefollowingisalistofallthecommandlineslistedaboveforyourconvenience.Itshouldbecustomized as appropriate. "<Path todir>\2005_sp1_vcredist_x86.exe" /q:a /c:"msiexec /i vcredist.msi/qn /l*v %TEMP%\2005_vcredistLog.txt" "<Path todir>\ndp452-kb x86-x64-allos-enu.exe " /q/norestart "<Path todir>\2008_sp1_vcredist_x86.exe" /q "<Path todir>\2010_vcredist_x86.exe" /q /norestart "<Path todir>\2013_vcredist_x86.exe" /q /norestart rem Delete the following ifnot required. msiexec /i "<Path todir>\o2003pia.msi" /qn /l*v "<path to logfile>" rem Delete the following ifnot required. msiexec /i "<Path todir>\o2007pia.msi" /qn /l*v "<path to logfile>" msiexec /i "<Path todir>\openxmlsdkv25.msi " /qn /l*v "<path to logfile>" msiexec.exe /i "<Path todir>\translationstudio5.msi" /qn /l*v "<Path to logfile>" msiexec.exe /i " "<Pathto dir>\tradoscompatibility2.msi " /qn /l*v "<Path to logfile>" msiexec.exe /i "<Path to dir>\worldservercomponents.msi " /qn /l*v "<Path to log file>" Enterprise Deployment Guide 25

34 6 SDL Trados Studio 2017 silent installation Locations for files created during installation This section does not include the files installed by the third-party installers(msis and EXEs). For SDL products, the installers are all Microsoft Windows Installer packages(msis) and a list of deployed resources can be found in the MSI database tables using standard tools. Refer to the silent installation section above for the log file locations for the installation modules. The distribution package extracts all of its files to%allusersprofile%\package Cache\SDL\. The installation chainer creates a data file at%allusersprofile%\ SDL\ Chainer\ PackageTracking. xml. A set of chainer log files is also created in%allusersprofile%\ SDL\ Chainer\ Logs\. The silent installer package utilizes a different initial bootstrapper utility to the standard installation package and this initial process logs to%temp%\sdltradosstudiosilentinstaller.txt. 26 Enterprise Deployment Guide

35 7 Pre-configuring settings during installation

36 7 Pre-configuring settings during installation Whatever method of installation you choose to deploy SDL Trados Studio there are some techniques that you can use to minimize end user configuration. Per user settings Thesesettingswillneedtobeappliedbytheadministratorforeachuser.Youcouldusealogonscriptto set these. Entering user details Theuserdetailsareenteredintothesetupwizardonthisstep: The information entered here is put into the Windows registry at the following location: HKEY_CURRENT_USER\Software\SDL\Studio5\MachineSupport. The following string values are mandatory under this key: CurrentUserFullName(this is filled by the user entering their name in the Name field in the screenshot above), CurrentUser (this is filled by the user entering their name in the Address field in the screenshot above) and CurrentUserId. CurrentUserId(this is filled automatically with the current fullyqualifiedwindowsuseridoftheuserintheformatdomain\username). 28 Enterprise Deployment Guide

37 Pre-configuring settings during installation 7 If this prompt should be avoided during startup, import a.registry key into the HKEY_CURRENT_USER area of the registry with at least these three fields filled. Example.reg file An example.reg file would look as follows: Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\SDL\Studio5\MachineSupport] "CurrentUserId"="COMPANY\\tomtranslator" "CurrentUser "="tom.translator@company.com" "CurrentUserFullName"="Tom Translator" "CurrentUserPhoneNumber"="" "CurrentUserDescription"="" Specifying the user profile The default user profile is taken from the wizard step below: Enterprise Deployment Guide 29

38 7 Pre-configuring settings during installation The corresponding setting is not stored in the Windows registry, but rather a settings file in the following location(windows 7/8.1/10): "C:\Users\[USERNAME]\AppData\Roaming\SDL\SDL Trados Studio\ \ BaseSettings.xml" Toavoidtheprompt,theBaseSettings.xmlfileneedstohaveatleastoneentryasfollows: <?xml version="1.0"encoding="utf-8"?> <SettingsBundle> <SettingsGroupId="IUserSettingsService"> <Setting Id="CurrentUserProfileFilePath">C:\Users\USERNAME\AppData\Roaming\SDL \SDLTrados Studio\ \UserProfiles\Builtin\Default.sdlprofile</Setting> </SettingsGroup> </SettingsBundle> ThevalueforUSERNAMEneedstomatchtheactualusernamefortheuserwhoshouldnotseethe prompt. 30 Enterprise Deployment Guide

39 Pre-configuring settings during installation 7 Customer feedback setting prompt Thecustomerfeedbacksystemcanbesuppressedatthemachinelevel(seelater)butifyouwishto suppress the option appearing in the start-up wizard you can supply an answer to the wizard question. The corresponding setting is not stored in the Windows registry but rather a settings file in the following location(windows 7/8.1/10): C:\Users\[USERNAME]\AppData\ Roaming\SDL\SDL Trados Studio\ \ UserSettings.xml ThevalueforUSERNAMEneedstomatchtheactualusernamefortheuserwhoshouldnotseethe prompt. To avoid the prompt, the UserSettings.xml file needs to have at least one entry as follows: <?xml version="1.0" encoding="utf-8"?> <SettingsBundle> <SettingsGroup Id="CustomerExperienceFeedbackSettingsGroup"> <Setting Id="PromptToProvideCustomerExperienceFeedback">False</Setting> </SettingsGroup> </SettingsBundle> Enterprise Deployment Guide 31

40 7 Pre-configuring settings during installation Deploying the sample project Inthefinalstepofthesetupwizard,theusercandecidewhetherornottoinstallthesampleproject. (TheusercanalwaysdecidetocopythesampleprojectatalaterpointbyrunningthecommandOpen SampleProjectfromtheHomeviewinSDLTradosStudio.).Thepromptisasfollows: The corresponding setting is not stored in the Windows registry but rather a settings file in the following location(windows 7/8.1/10): C:\Users\[USERNAME]\AppData\ Roaming\SDL\SDL Trados Studio\ \ UserSettings.xml ThevalueforUSERNAMEneedstomatchtheactualusernamefortheuserwhoshouldnotseethe prompt. Toavoidtheprompt,theUserSettings.xmlfileneedstohaveatleastoneentryasfollows: <?xml version="1.0"encoding="utf-8"?> <SettingsBundle> <SettingsGroupId="SampleDataSettingsGroup"> <SettingId="ShouldInstallSamples">True</Setting> </SettingsGroup> </SettingsBundle> 32 Enterprise Deployment Guide

41 Pre-configuring settings during installation 7 Per machine settings ThesesettingscanbeappliedwhenyoudeploythesoftwareandareappliedbydefaultintheSDLsilent installer package. Specifying a License Server during installation IfyouareusingtheSDLlicenseservertosupplycommuterlicensestoasetofusersyoucansupplythe license server details during installation of the software. There is an optional property called LICSERVER thatyoucanpasstothemsi Disabling the telemetrics customer feedback system Set the following registry key to disable the customer feedback system: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Policies\SDL\Studio5 DWORD EnableCustomerExperienceFeedback = 0 Disabling Autoupdate Set the following registry key to disable the autoupdate system: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Policies\SDL\Studio5 DWORD EnableAutoupdate = 0 Enterprise Deployment Guide 33

42 7 Pre-configuring settings during installation 34 Enterprise Deployment Guide

43 8 Acknowledgments

44 8 Acknowledgments SDL Trados Studio includes open source or similar third-party software. #ziplib #ziplib(sharpziplib, formerly NZipLib) is a Zip, GZip, Tar and BZip2 library written entirely in C# for the.netplatform.itisimplementedasanassembly(installableinthegac),andthuscaneasilybe incorporated into other projects(in any.net language). Apache log4net TheApachelog4netlibraryisatooltohelptheprogrammeroutputlogstatementstoavarietyof output targets. log4net is a port of the Apache log4j framework to the Microsoft.NET runtime. Hunspell Hunspell is the spell checker of LibreOffice, OpenOffice.org, Mozilla Firefox 3& Thunderbird, Google Chrome, and it is also used by proprietary software packages, like Mac OS X, InDesign, MemoQ, Opera and SDL Trados Studio. ICU(International Components for Unicode) ICU is a mature, widely used set of C/C++ and Java libraries providing Unicode and Globalization support for software applications. ICU is widely portable and gives applications the same results on all platforms and between C/C++ and Java software. SafeNet Sentinel SafeNet's Sentinel software licensing products and software protection solutions provides software publishers control and visibility into how their applications are deployed and used. Spring.NET Spring.NET is an application framework that provides comprehensive infrastructural support for developing enterprise.net applications. It allows you to remove incidental complexity when using the base class libraries makes best practices, such as test driven development, easy practices. WiX The WiX toolset builds Windows installation packages from XML source code. The tool-set integrates seamlessly into build processes. Xerces-C++ Xerces-C++ is a validating XML parser written in a portable subset of C Enterprise Deployment Guide