#PS - instead of using $tdmClientRegisterToken, you can use a WATS username and password that has the RegisterClient permission $tdmapi.RegisterClient($tdmURL, "", $tdmClientRegisterToken) $tdmapi.SetupAPI($tdmDataFolder, $tdmLocation, $tdmPurpose, $true) $tdmDataFolder=::GetFolderPath(::CommonApplicationData) "\Virinco\WATS" #$tdmDataFolder is the full path to the location to the WATS folder containing settings, logs and offline reports $tdmdll=::LoadWithPartialName("").Location #The next statements locates the installed TDM assembly, and makes it available to PowerShell. $tdmClientRegisterToken="cmVnaXN0ZXJDbGllbnRUb2tlbjpmbjVuNGthZTQ5bnJkYW11eHhrZ2Zy" #The Client register token is received when you register your account To setup and configure the client, you can use this Powershell script: #Url to your wats instance When combining this command with the powershell scripts below, it should look like this, to make the script wait until the installation is complete: start-process msiexec -Wait -ArgumentList '/i "WATSClient_6.0.240_圆4.msi" LAUNCHMODE=NEVER /passive' Connect WATS Client to WATS Set REMOVE to ensure a feature is not installed.Įxample: msiexec /i "WATSClient_6.0.240_圆4.msi" LAUNCHMODE=NEVER /passive Except features added this version are default installed. Set license type to Production if WATS Client is used in production or to Development if it is used to develop tests.ĭefault is to update installed optional features and not update not installed optional features. NEVER will never open the window after install, ALWAYS will always open the window after install.ĭefault Production. When installing the WATS Client without user interaction you can set some properties to use instead of their defaults: Propertyĭefault opens WATS Client Configurator window on first install, not on upgrade. To install the WATS Client without user interaction, use this command (WATSClient_6.0.240_圆4.msi is an example): msiexec /i "WATSClient_6.0.240_圆4.msi" /passive Installer properties You can find a download link at Install the WATS Client The first step is to download the installer package (.msi) to a location where the client can reach it. This article describes how to perform an unattended setup of a WATS Client using a Powershell script.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |