ThinManager Knowledge Base - User contributions [en]

Common Configuration Problems

2023-05-01T20:51:43Z

Toddgarmon: /* Graphical ACP Logo is shown, but boot process stops */

[[Category:Troubleshooting]]
[[Category:Windows_Settings]]
Below is a list of common configuration problems, ordered from thin client power on to Terminal Server Login.
==Powering on the Thin Client==
No Power
*Check power cable, power supply and outlets.
No Video
*Check video cable, monitor power cable and outlets.
==Booting - Network Boot Loader==
Cannot get IP address using DHCP
*Is the ThinManager Ready thin client set to DHCP? They are set to DHCP by default, but can be changed.
*Is the Thin Client on the same side of the router as the DHCP server?
*Does the DHCP server have addresses to give out?
Cannot get IP address using Static IP menu
*Certain models like PXE boot ThinManager Compatible thin clients cannot use static IP.
*Static IP hasn't been set. Use the spacebar when the "Select any Key to Configure IP Settings" is displayed and set the client IP address
A Non-ThinManager Ready (PXE) Client Will Not Boot.
*PXE-E32: TFTP open timeout
**Verify that there is not a firewall preventing the client from downloading the boot file
**Check that acpboot.bin is located in the [https://kb.thinmanager.com/index.php/ThinManager_Installation ThinManager Installation] directory (default of %PROGRAMFILES%\Rockwell Software\ThinManager)
**If using a standard DCHP server with boot options
***Verify option 67 is set to acpboot.bin in the DHCP server scope
*PXE-E51: No DHCP or proxyDHCP offers were received
**Make sure the client has a connection to the network with where the DHCP server resides
**If "Using Standard DHCP server with boot options":
**Check that there is not a firewall preventing the DHCP requests from reaching the DHCP server
**If the DHCP server is on a different subnet, make sure DHCP helpers (DHCP forwarding) are configured
**If "Using Standard DHCP server":
***Check that there is not a firewall preventing the DHCP requests from reaching the DHCP server or the ThinManager servers
***If the DHCP server or ThinManager server is on a different subnet, make sure DHCP helpers (DHCP forwarding) are configured
**If "Not using a Standard DHCP server":
***Check that there is not a firewall preventing the DHCP requests from reaching the ThinManager servers
***If the ThinManager server is on a different subnet, make sure DHCP helpers (DHCP forwarding) are configured
*PXE-E52: proxy DHCP offers were received. No DHCP offers were received.
**Verify that the standard DHCP server is functioning correctly
**If you do not have a standard DHCP Server, configure the ThinManager PXE Server to "Not using Standard DHCP Server".
*PXE-E53: No boot filename received.
**Using a relay agent: verify that the relay agent is configured properly
**Using a standard DHCP server with boot options: verify that option 67 in the DHCP Server is set to acpboot.bin
*PXE-E55: ProxyDHCP service did not reply to request on port 4011
**Install the latest service pack for your version of ThinManager
*PXE-E61: Media test failure, check cable
**Make sure the client has a physical connection to the network

==Cannot Load Firmware==
Is Thin Client connecting to the ThinManager Server?
*Using DHCP
**Has Option 066 been set to the ThinManager Server IP Address?
**Is there a link light on the network port?
**Check router address, IP Addresses, and Subnet Mask
*Using Static IP
**Has the ThinManager Server IP Address been entered in the IP Configuration Menu?
**Check router address, IP Addresses, and Subnet Mask
Is the network blocked?
*ThinManager Ready thin client that communicate through routers, gateways, or firewalls may need some [[ports]] opened to allow data flow through these devices. See the [[Ports]] Page for a complete list of [[ports]] utilitized by ACP Products.
Loads firmware intermittently/slowly
*Check for IP conflicts
*Check cable connections
*Make sure ThinManager Server CPU usage is below 100%

==Thin Client Loads Firmware but fails to load configuration==
"Please Define on Server"
*Enter ThinManager and define the terminal.
"License Not Available"
*Check your license usage in ThinManager. You are out of an ACP-supplied License.
*The Installation ID may come from the motherboard serial number, the MAC address on the network cards, or the GUID from the operation system. Don't change or disable the network cards after licensing to prevent changing the Installation ID, which can affect the validity of the license.
"This Terminal Disabled"
*A ThinManager administrator has disabled this terminal. Re-enable it.
"Network Error - Check Network Connections"
*Check the network cable, link light, and network.
Was Disabled, but did not go on when re-enabled.
*Reboot the thin client.
Is [[WinTMC]] Loaded on ThinManager Server?
*Make sure that the [[WinTMC]] client is not installed on the ThinManager Server. The [[WinTMC]] client will try to open the 2031 port that ThinManager needs to communicate with thin clients, causing a port conflict. [[WinTMC]] is for PCs, not servers. Uninstall the [[WinTMC]] client if it is present.
Terminal Selection menu is shown, but keyboard does not work
*Check keyboard and reboot
*Use PS/2 splitter if the unit has only one PS/2 port
*Switch the mouse and the keyboard if plugged into a PS/2 splitter.

==Graphical ThinManager Logo is shown, but boot process stops==
Does not attempt to connect to the terminal server
*Check Terminal Configuration Wizard to make sure a terminal server is specified
Cannot Connect to Server xxx (0.0.0.0)
*The terminal server doesn't have an IP address configured in the [[Terminal Server Configuration]] Wizard.
*If using DNS, check the terminal server's registration.
*If you are using a Citrix Published Application, you may need to specify the ICA browser.
Cannot Connect to Server xxx (w.x.y.z)
*Check the event viewer on the terminal server. If it says "Could not issue client license", you need a Microsoft Terminal Server Client Access License (MS TS CAL) and/or a Microsoft Terminal Server Licensing server.
*Check the Subnet Mask in the ACP Boot Loader on the thin client. If it is set to 255.255.255.255 instead of 255.255.255.0, it will fail to connect to the terminal server.
Reboot the thin client and use the spacebar when the "Select any Key to Configure IP Settings" is displayed. Change the subnet mask in the ACP Boot Loader menu.
*Error 50 - Disconnected
*Check the event viewer on the terminal server. If it says "Could not issue client license", you need a MS TS Cal / MS TS Licensing server.

==Attempts to connect to terminal server, but dies==
*Some servers (Dell and its Dellwall.bmp, for example) load a complex bitmap background that can interfere with loading. Find the offending wallpaper file on the console session and rename it so that it doesn't load at login

==Connects to connect to terminal server, but cannot login==
*Is the user a valid user? Is the password correct?
*Does the user have permission to connect through Terminal Services (user properties in the User Manager)
*Is the user a member of the Administrators or Remote Desktop Users Group?
*Check the event viewer. If it says "Could not issue client license", you need a Microsoft TS Cal and or a Microsoft TS Licensing server.
*When terminal server is in 2 domains and an administrator logs into the console with a domain account, it sets that as the default domain. If the terminals are configured to use the other domain they will be unable to login. Login to the console with the domain of the terminals to reset the default domain.
*Is [[NLA]] turned on? Support for [[NLA]] was released with Firmware 7.1.113 found in Firmware Package 7.1.3.

==Login to Terminal Server prompts for password even though the username and password are filled in ThinManager==
*The password may be entered wrong in ThinManager.
*Always Prompt for Password may be setup and should be disabled:
**Start > Programs > Administrative Tools > Terminal Services Configuration (2003, 2008) or Remote Desktop Session Host Configuration (2008 R2)
**Double click on RDP-tcp Properties in the right-hand window.
**Uncheck the Always Prompt for Password checkbox on the Login Settings tab.
***Note: In 2012, this must be done via Group Policy or Registry Key.
***Computer Configuration > Policies > Administrative Template > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Security > Always prompt for password upon connection change to false.
***HKLM\Software\Policies\Microsoft\Windows NT\TerminalServices create a new 32-bit DWORD key fPromptForPassword with a value of 0.

==After the session is established, it will disconnect randomly==
*Make sure each user is logging on with a unique user name. Windows will only allow one session per name by default.
*Check the physical network connection.
*Check for a different computer (e.g. a laptop) with the same IP address.
*Slow down the Monitoring Interval on the Monitoring Connection page of the Terminal Configuration Wizard by increasing the timeout and retry values.

==Mouse works but the application is unresponsive==
Application on terminal server is locked up - kill the application and let the thin client reconnect to terminal server and restart the application.

==Sound doesn't work==
*Make sure that Audio Mapping is allowed on the Client Settings of the RDP-tcp Properties in the [[Terminal Server Configuration]] Console (2003, 2008) or Remote Desktop Session Host Configuration (2008 r2).
*Make sure that you are using a ThinManager Ready thin client that has [[sound]] capability.
*Use the [[Sound]] Module for that specific thin client.
*Connect a powered speaker to the "Line Out" plug. Line Out isn't amplified so it requires a powered speaker.
*Properly working [[sound]] will play a [[sound]] at boot and at login.

==The touch screen doesn't work==
*Make sure you are using the right Touch Screen Module for the touch screen controller.
*Make sure that the serial cable is plugged into the correct serial port
*Make sure that the Touch Screen Module is using the correct baud rate.
*Use the USB Touch Screen Module if the touch screen is USB, or set the Connection Type to USB on the regular touch screen module.

==The touch screen mouse doesn't match the touches==
*Calibrate the touch screen by highlighting the unit in the ThinManager tree and select Tools > Calibrate Touch Screen.
*If the touches are 180 degrees out of phase, enable the "Swap XY Coordinates" parameter on the touchscreen module.

==Changes to the configuration in ThinManager don't show up on the thin client==
*Restart or Reboot the thin client. Changes are only sent to a thin client at bootup.

==The configuration of the primary ThinManager Server and the secondary ThinManager Server are different==
*Enable automatic [[synchronization]] by selecting Manage > ThinManager Server List or manually synchronize the configurations by selecting Manager >Synchronize in the ThinManager menu bar.

==The terminals in the tree on the primary ThinManager Server show green while the terminals on the secondary are all red==
*Enable automatic [[synchronization]] by selecting Manage > ThinManager Server List or add both ThinManager Servers to the ThinManager Server Monitor List in the Terminal Configuration Wizard. Reboot the terminals and synchronize the ThinManagers as above.

==The client is showing the time of the terminal server in a different time zone and not the local time==
*Use the Time Zone Redirection Module on the client with the local time zone selected.
*Make sure that the security policy of the terminal server or domain allows it:
**Start > Run > secpol.msc > OK
**Expand: Computer Configuration > Administrative Templates> Windows Components > Terminal Services > Client/Server data redirection > Allow Time Zone Redirection
**Change to Enabled

==When "Terminal Servers" is highlighted in the ThinManager tree, the Details pane doesn't show OK for the connections==
“No login information supplied”
*Run the Terminal Server List Wizard and add an administrative user name and password on the Terminal Server Name page of the Terminal Server List Wizard.
“User specified does not have permission to connect”
*This indicates that the Terminal Server had an invalid username and password added on the Terminal Server Name page of the Terminal Server List Wizard. Run the Terminal Server List Wizard and change to an administrative user name and password on the Terminal Server Name page of the Terminal Server List Wizard.
*Use the domain in the Domain field on the Terminal Server Name page of the Terminal Server List Wizard.
*If not in a domain, try using the terminal server name in the Domain field on the Terminal Server Name page of the Terminal Server List Wizard.
WTSAPI32.dll connection failed
*This occurs when the terminal server is off or unreachable. Try pinging the terminal server.
*For additional information regarding WTSAPI32.dll errors, see the [[DCOM_Errors]] Page.

==The Users, Sessions, and Processes tabs don't show data for a terminal server==
*Shorten the name of the terminal.
**Microsoft truncates the terminal names to 15 characters. The Process information won't display for terminals with a name longer than 15 characters.

==The Users and Sessions tabs show data for a terminal server, but the Processes tabs shows no data==
*Shorten the name of the terminal.
**Microsoft truncates the terminal names to 15 characters. The Process information won't display for terminals with a name longer than 15 characters.

==When shadowing a client the mouse doesn't work in the shadowed session==
*The user must be logged into the [[shadowing]] computer as an administrator, or as a ThinManager Administrator, or member of a security group that is given permission to use interactive [[shadowing]] in the [[ThinManager Server Configuration]] Wizard.
*The interactive shadow must be checked in RemoteView on the ThinManager menu.
*A terminal using the Share Keyboard and Mouse module will only be interactive if the mouse is active in that session.

Common Configuration Problems

2023-05-01T20:51:03Z

Toddgarmon: /* Booting - ACP Network Boot Loader */

[[Category:Troubleshooting]]
[[Category:Windows_Settings]]
Below is a list of common configuration problems, ordered from thin client power on to Terminal Server Login.
==Powering on the Thin Client==
No Power
*Check power cable, power supply and outlets.
No Video
*Check video cable, monitor power cable and outlets.
==Booting - Network Boot Loader==
Cannot get IP address using DHCP
*Is the ThinManager Ready thin client set to DHCP? They are set to DHCP by default, but can be changed.
*Is the Thin Client on the same side of the router as the DHCP server?
*Does the DHCP server have addresses to give out?
Cannot get IP address using Static IP menu
*Certain models like PXE boot ThinManager Compatible thin clients cannot use static IP.
*Static IP hasn't been set. Use the spacebar when the "Select any Key to Configure IP Settings" is displayed and set the client IP address
A Non-ThinManager Ready (PXE) Client Will Not Boot.
*PXE-E32: TFTP open timeout
**Verify that there is not a firewall preventing the client from downloading the boot file
**Check that acpboot.bin is located in the [https://kb.thinmanager.com/index.php/ThinManager_Installation ThinManager Installation] directory (default of %PROGRAMFILES%\Rockwell Software\ThinManager)
**If using a standard DCHP server with boot options
***Verify option 67 is set to acpboot.bin in the DHCP server scope
*PXE-E51: No DHCP or proxyDHCP offers were received
**Make sure the client has a connection to the network with where the DHCP server resides
**If "Using Standard DHCP server with boot options":
**Check that there is not a firewall preventing the DHCP requests from reaching the DHCP server
**If the DHCP server is on a different subnet, make sure DHCP helpers (DHCP forwarding) are configured
**If "Using Standard DHCP server":
***Check that there is not a firewall preventing the DHCP requests from reaching the DHCP server or the ThinManager servers
***If the DHCP server or ThinManager server is on a different subnet, make sure DHCP helpers (DHCP forwarding) are configured
**If "Not using a Standard DHCP server":
***Check that there is not a firewall preventing the DHCP requests from reaching the ThinManager servers
***If the ThinManager server is on a different subnet, make sure DHCP helpers (DHCP forwarding) are configured
*PXE-E52: proxy DHCP offers were received. No DHCP offers were received.
**Verify that the standard DHCP server is functioning correctly
**If you do not have a standard DHCP Server, configure the ThinManager PXE Server to "Not using Standard DHCP Server".
*PXE-E53: No boot filename received.
**Using a relay agent: verify that the relay agent is configured properly
**Using a standard DHCP server with boot options: verify that option 67 in the DHCP Server is set to acpboot.bin
*PXE-E55: ProxyDHCP service did not reply to request on port 4011
**Install the latest service pack for your version of ThinManager
*PXE-E61: Media test failure, check cable
**Make sure the client has a physical connection to the network

==Cannot Load Firmware==
Is Thin Client connecting to the ThinManager Server?
*Using DHCP
**Has Option 066 been set to the ThinManager Server IP Address?
**Is there a link light on the network port?
**Check router address, IP Addresses, and Subnet Mask
*Using Static IP
**Has the ThinManager Server IP Address been entered in the IP Configuration Menu?
**Check router address, IP Addresses, and Subnet Mask
Is the network blocked?
*ThinManager Ready thin client that communicate through routers, gateways, or firewalls may need some [[ports]] opened to allow data flow through these devices. See the [[Ports]] Page for a complete list of [[ports]] utilitized by ACP Products.
Loads firmware intermittently/slowly
*Check for IP conflicts
*Check cable connections
*Make sure ThinManager Server CPU usage is below 100%

==Thin Client Loads Firmware but fails to load configuration==
"Please Define on Server"
*Enter ThinManager and define the terminal.
"License Not Available"
*Check your license usage in ThinManager. You are out of an ACP-supplied License.
*The Installation ID may come from the motherboard serial number, the MAC address on the network cards, or the GUID from the operation system. Don't change or disable the network cards after licensing to prevent changing the Installation ID, which can affect the validity of the license.
"This Terminal Disabled"
*A ThinManager administrator has disabled this terminal. Re-enable it.
"Network Error - Check Network Connections"
*Check the network cable, link light, and network.
Was Disabled, but did not go on when re-enabled.
*Reboot the thin client.
Is [[WinTMC]] Loaded on ThinManager Server?
*Make sure that the [[WinTMC]] client is not installed on the ThinManager Server. The [[WinTMC]] client will try to open the 2031 port that ThinManager needs to communicate with thin clients, causing a port conflict. [[WinTMC]] is for PCs, not servers. Uninstall the [[WinTMC]] client if it is present.
Terminal Selection menu is shown, but keyboard does not work
*Check keyboard and reboot
*Use PS/2 splitter if the unit has only one PS/2 port
*Switch the mouse and the keyboard if plugged into a PS/2 splitter.

==Graphical ACP Logo is shown, but boot process stops==
Does not attempt to connect to the terminal server
*Check Terminal Configuration Wizard to make sure a terminal server is specified
Cannot Connect to Server xxx (0.0.0.0)
*The terminal server doesn't have an IP address configured in the [[Terminal Server Configuration]] Wizard.
*If using DNS, check the terminal server's registration.
*If you are using a Citrix Published Application, you may need to specify the ICA browser.
Cannot Connect to Server xxx (w.x.y.z)
*Check the event viewer on the terminal server. If it says "Could not issue client license", you need a Microsoft Terminal Server Client Access License (MS TS CAL) and/or a Microsoft Terminal Server Licensing server.
*Check the Subnet Mask in the ACP Boot Loader on the thin client. If it is set to 255.255.255.255 instead of 255.255.255.0, it will fail to connect to the terminal server.
Reboot the thin client and use the spacebar when the "Select any Key to Configure IP Settings" is displayed. Change the subnet mask in the ACP Boot Loader menu.
*Error 50 - Disconnected
*Check the event viewer on the terminal server. If it says "Could not issue client license", you need a MS TS Cal / MS TS Licensing server.

==Attempts to connect to terminal server, but dies==
*Some servers (Dell and its Dellwall.bmp, for example) load a complex bitmap background that can interfere with loading. Find the offending wallpaper file on the console session and rename it so that it doesn't load at login

==Connects to connect to terminal server, but cannot login==
*Is the user a valid user? Is the password correct?
*Does the user have permission to connect through Terminal Services (user properties in the User Manager)
*Is the user a member of the Administrators or Remote Desktop Users Group?
*Check the event viewer. If it says "Could not issue client license", you need a Microsoft TS Cal and or a Microsoft TS Licensing server.
*When terminal server is in 2 domains and an administrator logs into the console with a domain account, it sets that as the default domain. If the terminals are configured to use the other domain they will be unable to login. Login to the console with the domain of the terminals to reset the default domain.
*Is [[NLA]] turned on? Support for [[NLA]] was released with Firmware 7.1.113 found in Firmware Package 7.1.3.

==Login to Terminal Server prompts for password even though the username and password are filled in ThinManager==
*The password may be entered wrong in ThinManager.
*Always Prompt for Password may be setup and should be disabled:
**Start > Programs > Administrative Tools > Terminal Services Configuration (2003, 2008) or Remote Desktop Session Host Configuration (2008 R2)
**Double click on RDP-tcp Properties in the right-hand window.
**Uncheck the Always Prompt for Password checkbox on the Login Settings tab.
***Note: In 2012, this must be done via Group Policy or Registry Key.
***Computer Configuration > Policies > Administrative Template > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Security > Always prompt for password upon connection change to false.
***HKLM\Software\Policies\Microsoft\Windows NT\TerminalServices create a new 32-bit DWORD key fPromptForPassword with a value of 0.

==After the session is established, it will disconnect randomly==
*Make sure each user is logging on with a unique user name. Windows will only allow one session per name by default.
*Check the physical network connection.
*Check for a different computer (e.g. a laptop) with the same IP address.
*Slow down the Monitoring Interval on the Monitoring Connection page of the Terminal Configuration Wizard by increasing the timeout and retry values.

==Mouse works but the application is unresponsive==
Application on terminal server is locked up - kill the application and let the thin client reconnect to terminal server and restart the application.

==Sound doesn't work==
*Make sure that Audio Mapping is allowed on the Client Settings of the RDP-tcp Properties in the [[Terminal Server Configuration]] Console (2003, 2008) or Remote Desktop Session Host Configuration (2008 r2).
*Make sure that you are using a ThinManager Ready thin client that has [[sound]] capability.
*Use the [[Sound]] Module for that specific thin client.
*Connect a powered speaker to the "Line Out" plug. Line Out isn't amplified so it requires a powered speaker.
*Properly working [[sound]] will play a [[sound]] at boot and at login.

==The touch screen doesn't work==
*Make sure you are using the right Touch Screen Module for the touch screen controller.
*Make sure that the serial cable is plugged into the correct serial port
*Make sure that the Touch Screen Module is using the correct baud rate.
*Use the USB Touch Screen Module if the touch screen is USB, or set the Connection Type to USB on the regular touch screen module.

==The touch screen mouse doesn't match the touches==
*Calibrate the touch screen by highlighting the unit in the ThinManager tree and select Tools > Calibrate Touch Screen.
*If the touches are 180 degrees out of phase, enable the "Swap XY Coordinates" parameter on the touchscreen module.

==Changes to the configuration in ThinManager don't show up on the thin client==
*Restart or Reboot the thin client. Changes are only sent to a thin client at bootup.

==The configuration of the primary ThinManager Server and the secondary ThinManager Server are different==
*Enable automatic [[synchronization]] by selecting Manage > ThinManager Server List or manually synchronize the configurations by selecting Manager >Synchronize in the ThinManager menu bar.

==The terminals in the tree on the primary ThinManager Server show green while the terminals on the secondary are all red==
*Enable automatic [[synchronization]] by selecting Manage > ThinManager Server List or add both ThinManager Servers to the ThinManager Server Monitor List in the Terminal Configuration Wizard. Reboot the terminals and synchronize the ThinManagers as above.

==The client is showing the time of the terminal server in a different time zone and not the local time==
*Use the Time Zone Redirection Module on the client with the local time zone selected.
*Make sure that the security policy of the terminal server or domain allows it:
**Start > Run > secpol.msc > OK
**Expand: Computer Configuration > Administrative Templates> Windows Components > Terminal Services > Client/Server data redirection > Allow Time Zone Redirection
**Change to Enabled

==When "Terminal Servers" is highlighted in the ThinManager tree, the Details pane doesn't show OK for the connections==
“No login information supplied”
*Run the Terminal Server List Wizard and add an administrative user name and password on the Terminal Server Name page of the Terminal Server List Wizard.
“User specified does not have permission to connect”
*This indicates that the Terminal Server had an invalid username and password added on the Terminal Server Name page of the Terminal Server List Wizard. Run the Terminal Server List Wizard and change to an administrative user name and password on the Terminal Server Name page of the Terminal Server List Wizard.
*Use the domain in the Domain field on the Terminal Server Name page of the Terminal Server List Wizard.
*If not in a domain, try using the terminal server name in the Domain field on the Terminal Server Name page of the Terminal Server List Wizard.
WTSAPI32.dll connection failed
*This occurs when the terminal server is off or unreachable. Try pinging the terminal server.
*For additional information regarding WTSAPI32.dll errors, see the [[DCOM_Errors]] Page.

==The Users, Sessions, and Processes tabs don't show data for a terminal server==
*Shorten the name of the terminal.
**Microsoft truncates the terminal names to 15 characters. The Process information won't display for terminals with a name longer than 15 characters.

==The Users and Sessions tabs show data for a terminal server, but the Processes tabs shows no data==
*Shorten the name of the terminal.
**Microsoft truncates the terminal names to 15 characters. The Process information won't display for terminals with a name longer than 15 characters.

==When shadowing a client the mouse doesn't work in the shadowed session==
*The user must be logged into the [[shadowing]] computer as an administrator, or as a ThinManager Administrator, or member of a security group that is given permission to use interactive [[shadowing]] in the [[ThinManager Server Configuration]] Wizard.
*The interactive shadow must be checked in RemoteView on the ThinManager menu.
*A terminal using the Share Keyboard and Mouse module will only be interactive if the mouse is active in that session.

License Activation with FactoryTalk Activation

2023-05-01T20:47:34Z

Toddgarmon:

'''Updated at: https://rockwellautomation.custhelp.com/app/answers/answer_view/a_id/1083531'''

----

ThinManager integrated the FactoryTalk Activation in ThinManager 11. This will show how to activate ThinManager. FactoryTalk Activation

[[Category:ThinManager]]
[[Category:Licensing]]
===For instructions with pictures see [https://kb.thinmanager.com/images/2/2d/UsingFactoryTalkActivationWithThinManager01.pdf Using FactoryTalk Activation With ThinManager01.pdf]===

This document covers several steps:
Installing the FactoryTalk Activation Manager using the ThinManager Install program
Activating the ThinManager licenses with the FactoryTalk Activation Manager
Applying the FactoryTalk Activation to ThinManager

===Steps to Use FactoryTalk Activation with ThinManager:===
# Launch the ThinManager v.11.0 installer.
# Once the Common Installer launches, click the Customize button.
# From the Customize page of the Common Installer, check the FactoryTalk Activation Manager checkbox, keep the default 32-bit manager option selected for ThinManager, and then click the Next button.

===Using ThinManager with FactoryTalk Activation requires FactoryTalk Activation Manager 4.03.03 or newer.===
# From the ThinServer Service Account page of the Common Installer, select the This account option button, and fill in the user credentials for the ThinServer service. Click the Install button. This user account should have a non-expiring password and should be a member of the Local Administrators group on the machine where ThinManager is being installed. If deploying ThinManager in a Redundant configuration, it is recommended to use this same username/password for the ThinServer service on the Redundant ThinManager installation.
# Review the End User License Agreements page and click the Accept all button.
# Once the installation is complete, click the Close button.
# Launch FactoryTalk Activation Manager.
# Click the Get New Activations button.

===If the ThinManager machine has access to the Internet:===
# If the machine on which you installed ThinManager has access to the Internet, you can enter the Serial Number and Product Key directly in FactoryTalk Activation Manager, followed by clicking the Validate Activation button.
# From the Validate Activation page of the wizard, notice the # to Download. This number does not represent the number of ThinManager Terminal Connections, it simply represents the number of installs of ThinManager that will be licensed by this activation. Notice the Available column which shows the number of installs available for this activation. For non-redundant licenses, this value will typically be 1. For redundant licenses, this value will typically be 2 – one activation for your Primary ThinManager installation and one for your Secondary ThinManager installation. Enter the # to Download, followed by clicking the Download Activation > button.
# To verify the activation transferred correctly, click the Find Available Activations tab, followed by the Refresh Activations button. You should see 2 new rows in the Available activations table, one is the actual ThinManager activation (highlighted with the arrow below), and the other is for partial rehosting (the row with an Activation of TM.FTA.1), which can be ignored, as this is not supported by ThinManager. Also note the Total column (5 in the example below), which for ThinManager activations represents the number of Terminal Connections associated with the activation.

'''''Note: Unlike ThinManager Master Licensing, if you are using ThinManager Redundancy with FactoryTalk Activation, you will need to separately activate the Primary ThinManager Server and the Secondary ThinManager Server.'''''

With traditional ThinManager Master Licensing, a single license is automatically shared between the Primary ThinManager Server and the Secondary ThinManager Server.
If you have purchased a FactoryTalk Activated Redundant ThinManager license, you will receive a single serial number and product key pair that can be activated 2 times – once for the Primary ThinManager Server and once for the Secondary ThinManager Server.

===If the ThinManager machine does not have access to the Internet:===

# I need to start the activation process by creating a data file option button. Click the Specify Data File > button.
# From the Specify Data File page of the wizard, specify a File Location and File Name and then click the Get Bindings button.
# From the Get Bindings page of the wizard, check the desired binding for the activation, and click the Create Data File > button.
# Transfer the created Data File to a machine with Internet access and from the web browser, navigate to https://activate.rockwellautomation.com.
# Click the Get Activation button.
# Login to the activation website.
# Enter the Serial Number and Product Key, then select the Version and Number of Activations. Browse to the Data File transferred from the previous steps. Click the Download button.
# Transfer the downloaded file back to the machine on which ThinManager is installed and return to FactoryTalk Activation Manager.
# From FactoryTalk Activation Manager, click the Get New Activations tab.
# Select the I have downloaded activation files and need to move them to this computer option button. Click the Specify File Location button.
# From the Specify File Location page of the wizard, select the File Location and click the Move Files button.
# To verify the activation transferred correctly, click the Find Available Activations tab, followed by the Refresh Activations button. You should see 2 new rows in the Available activations table, one is the actual ThinManager activation (highlighted with the arrow below), and the other is for partial rehosting (the row with an Activation of TM.FTA.1), which can be ignored, as this is not supported by ThinManager. Also note the Total column (5 in the example below), which for ThinManager activations represents the number of Terminal Connections associated with the activation.

'''''Note: For remote FactoryTalk Activation Manager servers, the Run Network Server option should be checked under Advanced --> Configure CodeMeter Server.'''''
See 1083669 - FactoryTalk Activation Manager: taking CodeMeter license from Server for more details.

===Assign Activation(s) to ThinManager:===
# Now that the FactoryTalk Activation Manager which is installed on your ThinManager machine has a valid ThinManager activation, you can assign it to your ThinManager installation. To do so, open the ThinManager Admin Console.
# Upon first opening the Admin Console, you will be prompted with a message box indicating: Server RDS1 has no valid terminal connection licenses . Click the OK button.
# From the Admin Console, click the Install ribbon, followed by the License Mode icon.
# From the License Mode window, select the FactoryTalk Activation option button and click the OK button.

'''''Note: ThinManager will only support one License Mode at a time – either ThinManager Master Licensing or FactoryTalk Activation. You cannot use both simultaneously.'''''

# With the License Mode changed to FactoryTalk Activation, now click the Licenses icon in the Install ribbon. From the ensuing FactoryTalk Activations window, click the Add Activations button.
# From the Add Activations to ThinManager window, select the Serial Number you would like to assign to this installation of ThinManager and click the OK button.
# The assigned Serial Number should now be displayed in the FactoryTalk Activations window. Click the OK button.
# To validate that the license has been properly recognized by ThinManager, click the ThinManager Server button bar. From the ThinManager Server tree, select your ThinManager Server (RDS1 in the example provided). Click the Licenses tab. You should see your license's details listed.

License Activation with FactoryTalk Activation

2023-05-01T20:45:54Z

Toddgarmon:

'''Updated at: https://rockwellautomation.custhelp.com/app/answers/answer_view/a_id/1083531'''
 

----

ThinManager integrated the FactoryTalk Activation in ThinManager 11. This will show how to activate ThinManager. FactoryTalk Activation

[[Category:ThinManager]]
[[Category:Licensing]]
===For instructions with pictures see [https://kb.thinmanager.com/images/2/2d/UsingFactoryTalkActivationWithThinManager01.pdf Using FactoryTalk Activation With ThinManager01.pdf]===

This document covers several steps:
Installing the FactoryTalk Activation Manager using the ThinManager Install program
Activating the ThinManager licenses with the FactoryTalk Activation Manager
Applying the FactoryTalk Activation to ThinManager

===Steps to Use FactoryTalk Activation with ThinManager:===
# Launch the ThinManager v.11.0 installer.
# Once the Common Installer launches, click the Customize button.
# From the Customize page of the Common Installer, check the FactoryTalk Activation Manager checkbox, keep the default 32-bit manager option selected for ThinManager, and then click the Next button.

===Using ThinManager with FactoryTalk Activation requires FactoryTalk Activation Manager 4.03.03 or newer.===
# From the ThinServer Service Account page of the Common Installer, select the This account option button, and fill in the user credentials for the ThinServer service. Click the Install button. This user account should have a non-expiring password and should be a member of the Local Administrators group on the machine where ThinManager is being installed. If deploying ThinManager in a Redundant configuration, it is recommended to use this same username/password for the ThinServer service on the Redundant ThinManager installation.
# Review the End User License Agreements page and click the Accept all button.
# Once the installation is complete, click the Close button.
# Launch FactoryTalk Activation Manager.
# Click the Get New Activations button.

===If the ThinManager machine has access to the Internet:===
# If the machine on which you installed ThinManager has access to the Internet, you can enter the Serial Number and Product Key directly in FactoryTalk Activation Manager, followed by clicking the Validate Activation button.
# From the Validate Activation page of the wizard, notice the # to Download. This number does not represent the number of ThinManager Terminal Connections, it simply represents the number of installs of ThinManager that will be licensed by this activation. Notice the Available column which shows the number of installs available for this activation. For non-redundant licenses, this value will typically be 1. For redundant licenses, this value will typically be 2 – one activation for your Primary ThinManager installation and one for your Secondary ThinManager installation. Enter the # to Download, followed by clicking the Download Activation > button.
# To verify the activation transferred correctly, click the Find Available Activations tab, followed by the Refresh Activations button. You should see 2 new rows in the Available activations table, one is the actual ThinManager activation (highlighted with the arrow below), and the other is for partial rehosting (the row with an Activation of TM.FTA.1), which can be ignored, as this is not supported by ThinManager. Also note the Total column (5 in the example below), which for ThinManager activations represents the number of Terminal Connections associated with the activation.

'''''Note: Unlike ThinManager Master Licensing, if you are using ThinManager Redundancy with FactoryTalk Activation, you will need to separately activate the Primary ThinManager Server and the Secondary ThinManager Server.'''''

With traditional ThinManager Master Licensing, a single license is automatically shared between the Primary ThinManager Server and the Secondary ThinManager Server.
If you have purchased a FactoryTalk Activated Redundant ThinManager license, you will receive a single serial number and product key pair that can be activated 2 times – once for the Primary ThinManager Server and once for the Secondary ThinManager Server.

===If the ThinManager machine does not have access to the Internet:===

# I need to start the activation process by creating a data file option button. Click the Specify Data File > button.
# From the Specify Data File page of the wizard, specify a File Location and File Name and then click the Get Bindings button.
# From the Get Bindings page of the wizard, check the desired binding for the activation, and click the Create Data File > button.
# Transfer the created Data File to a machine with Internet access and from the web browser, navigate to https://activate.rockwellautomation.com.
# Click the Get Activation button.
# Login to the activation website.
# Enter the Serial Number and Product Key, then select the Version and Number of Activations. Browse to the Data File transferred from the previous steps. Click the Download button.
# Transfer the downloaded file back to the machine on which ThinManager is installed and return to FactoryTalk Activation Manager.
# From FactoryTalk Activation Manager, click the Get New Activations tab.
# Select the I have downloaded activation files and need to move them to this computer option button. Click the Specify File Location button.
# From the Specify File Location page of the wizard, select the File Location and click the Move Files button.
# To verify the activation transferred correctly, click the Find Available Activations tab, followed by the Refresh Activations button. You should see 2 new rows in the Available activations table, one is the actual ThinManager activation (highlighted with the arrow below), and the other is for partial rehosting (the row with an Activation of TM.FTA.1), which can be ignored, as this is not supported by ThinManager. Also note the Total column (5 in the example below), which for ThinManager activations represents the number of Terminal Connections associated with the activation.

'''''Note: For remote FactoryTalk Activation Manager servers, the Run Network Server option should be checked under Advanced --> Configure CodeMeter Server.'''''
See 1083669 - FactoryTalk Activation Manager: taking CodeMeter license from Server for more details.

===Assign Activation(s) to ThinManager:===
# Now that the FactoryTalk Activation Manager which is installed on your ThinManager machine has a valid ThinManager activation, you can assign it to your ThinManager installation. To do so, open the ThinManager Admin Console.
# Upon first opening the Admin Console, you will be prompted with a message box indicating: Server RDS1 has no valid terminal connection licenses . Click the OK button.
# From the Admin Console, click the Install ribbon, followed by the License Mode icon.
# From the License Mode window, select the FactoryTalk Activation option button and click the OK button.

'''''Note: ThinManager will only support one License Mode at a time – either ThinManager Master Licensing or FactoryTalk Activation. You cannot use both simultaneously.'''''

# With the License Mode changed to FactoryTalk Activation, now click the Licenses icon in the Install ribbon. From the ensuing FactoryTalk Activations window, click the Add Activations button.
# From the Add Activations to ThinManager window, select the Serial Number you would like to assign to this installation of ThinManager and click the OK button.
# The assigned Serial Number should now be displayed in the FactoryTalk Activations window. Click the OK button.
# To validate that the license has been properly recognized by ThinManager, click the ThinManager Server button bar. From the ThinManager Server tree, select your ThinManager Server (RDS1 in the example provided). Click the Licenses tab. You should see your license's details listed.

License Activation with FactoryTalk Activation

2023-05-01T20:44:49Z

Toddgarmon:

License Activation with FactoryTalk Activation

2023-05-01T20:40:18Z

Toddgarmon:

'''https://rockwellautomation.custhelp.com/app/answers/answer_view/a_id/1083531'''

ThinManager integrated the FactoryTalk Activation in ThinManager 11. This will show how to activate ThinManager. FactoryTalk Activation

[[Category:ThinManager]]
[[Category:Licensing]]
===For instructions with pictures see [https://kb.thinmanager.com/images/2/2d/UsingFactoryTalkActivationWithThinManager01.pdf Using FactoryTalk Activation With ThinManager01.pdf]===

This document covers several steps:
Installing the FactoryTalk Activation Manager using the ThinManager Install program
Activating the ThinManager licenses with the FactoryTalk Activation Manager
Applying the FactoryTalk Activation to ThinManager

===Steps to Use FactoryTalk Activation with ThinManager:===
# Launch the ThinManager v.11.0 installer.
# Once the Common Installer launches, click the Customize button.
# From the Customize page of the Common Installer, check the FactoryTalk Activation Manager checkbox, keep the default 32-bit manager option selected for ThinManager, and then click the Next button.

===Using ThinManager with FactoryTalk Activation requires FactoryTalk Activation Manager 4.03.03 or newer.===
# From the ThinServer Service Account page of the Common Installer, select the This account option button, and fill in the user credentials for the ThinServer service. Click the Install button. This user account should have a non-expiring password and should be a member of the Local Administrators group on the machine where ThinManager is being installed. If deploying ThinManager in a Redundant configuration, it is recommended to use this same username/password for the ThinServer service on the Redundant ThinManager installation.
# Review the End User License Agreements page and click the Accept all button.
# Once the installation is complete, click the Close button.
# Launch FactoryTalk Activation Manager.
# Click the Get New Activations button.

===If the ThinManager machine has access to the Internet:===
# If the machine on which you installed ThinManager has access to the Internet, you can enter the Serial Number and Product Key directly in FactoryTalk Activation Manager, followed by clicking the Validate Activation button.
# From the Validate Activation page of the wizard, notice the # to Download. This number does not represent the number of ThinManager Terminal Connections, it simply represents the number of installs of ThinManager that will be licensed by this activation. Notice the Available column which shows the number of installs available for this activation. For non-redundant licenses, this value will typically be 1. For redundant licenses, this value will typically be 2 – one activation for your Primary ThinManager installation and one for your Secondary ThinManager installation. Enter the # to Download, followed by clicking the Download Activation > button.
# To verify the activation transferred correctly, click the Find Available Activations tab, followed by the Refresh Activations button. You should see 2 new rows in the Available activations table, one is the actual ThinManager activation (highlighted with the arrow below), and the other is for partial rehosting (the row with an Activation of TM.FTA.1), which can be ignored, as this is not supported by ThinManager. Also note the Total column (5 in the example below), which for ThinManager activations represents the number of Terminal Connections associated with the activation.

'''''Note: Unlike ThinManager Master Licensing, if you are using ThinManager Redundancy with FactoryTalk Activation, you will need to separately activate the Primary ThinManager Server and the Secondary ThinManager Server.'''''

With traditional ThinManager Master Licensing, a single license is automatically shared between the Primary ThinManager Server and the Secondary ThinManager Server.
If you have purchased a FactoryTalk Activated Redundant ThinManager license, you will receive a single serial number and product key pair that can be activated 2 times – once for the Primary ThinManager Server and once for the Secondary ThinManager Server.

===If the ThinManager machine does not have access to the Internet:===

# I need to start the activation process by creating a data file option button. Click the Specify Data File > button.
# From the Specify Data File page of the wizard, specify a File Location and File Name and then click the Get Bindings button.
# From the Get Bindings page of the wizard, check the desired binding for the activation, and click the Create Data File > button.
# Transfer the created Data File to a machine with Internet access and from the web browser, navigate to https://activate.rockwellautomation.com.
# Click the Get Activation button.
# Login to the activation website.
# Enter the Serial Number and Product Key, then select the Version and Number of Activations. Browse to the Data File transferred from the previous steps. Click the Download button.
# Transfer the downloaded file back to the machine on which ThinManager is installed and return to FactoryTalk Activation Manager.
# From FactoryTalk Activation Manager, click the Get New Activations tab.
# Select the I have downloaded activation files and need to move them to this computer option button. Click the Specify File Location button.
# From the Specify File Location page of the wizard, select the File Location and click the Move Files button.
# To verify the activation transferred correctly, click the Find Available Activations tab, followed by the Refresh Activations button. You should see 2 new rows in the Available activations table, one is the actual ThinManager activation (highlighted with the arrow below), and the other is for partial rehosting (the row with an Activation of TM.FTA.1), which can be ignored, as this is not supported by ThinManager. Also note the Total column (5 in the example below), which for ThinManager activations represents the number of Terminal Connections associated with the activation.

'''''Note: For remote FactoryTalk Activation Manager servers, the Run Network Server option should be checked under Advanced --> Configure CodeMeter Server.'''''
See 1083669 - FactoryTalk Activation Manager: taking CodeMeter license from Server for more details.

===Assign Activation(s) to ThinManager:===
# Now that the FactoryTalk Activation Manager which is installed on your ThinManager machine has a valid ThinManager activation, you can assign it to your ThinManager installation. To do so, open the ThinManager Admin Console.
# Upon first opening the Admin Console, you will be prompted with a message box indicating: Server RDS1 has no valid terminal connection licenses . Click the OK button.
# From the Admin Console, click the Install ribbon, followed by the License Mode icon.
# From the License Mode window, select the FactoryTalk Activation option button and click the OK button.

'''''Note: ThinManager will only support one License Mode at a time – either ThinManager Master Licensing or FactoryTalk Activation. You cannot use both simultaneously.'''''

# With the License Mode changed to FactoryTalk Activation, now click the Licenses icon in the Install ribbon. From the ensuing FactoryTalk Activations window, click the Add Activations button.
# From the Add Activations to ThinManager window, select the Serial Number you would like to assign to this installation of ThinManager and click the OK button.
# The assigned Serial Number should now be displayed in the FactoryTalk Activations window. Click the OK button.
# To validate that the license has been properly recognized by ThinManager, click the ThinManager Server button bar. From the ThinManager Server tree, select your ThinManager Server (RDS1 in the example provided). Click the Licenses tab. You should see your license's details listed.

License Activation

2023-05-01T20:39:08Z

Toddgarmon:

'''https://rockwellautomation.custhelp.com/app/answers/answer_view/a_id/1083531'''

[[Category:ThinManager]]
[[Category:Licensing]]
===For instructions with pictures see [https://kb.thinmanager.com/images/b/b3/Licensing.pdf Licensing.pdf]===

After you receive your Product Code from your Authorized Vendor, licensing is generally completed in 4 steps. If you are upgrading from ThinManager 3.3 or below, see our article on [[Upgrading_from_ThinManager_3.x| Upgrading from ThinManager 3.x and below]]
The ThinManager license website is found at [https://licensing.thinmanager.com '''https://licensing.thinmanager.com''']

==Creating a Master License==
The purpose of a Master License is to hold each individual product license so that only one license needs to be activated and managed instead of multiple independent product [[licenses]]. Master [[Licenses]] are free to create, although only one is needed per ThinManager server or synchronized pair of ThinManager servers. 
To create a Master License: 
#Create an account within the [https://licensing.thinmanager.com ThinManager Licensing Website]
#Your password will be emailed to you at the address specified during sign up, use this to login and change your password if desired.
#Click the [https://licensing.thinmanager.com/MasterLicense/Create Create Master License] link on the right of the page and fill out all requested fields.

===Considerations for Integrators===
When creating an account for a customer, put their contact information in. After the project has been implemented, please call ACP at +1-877-239-4282 to have ownership of the Master License changed to someone at the customer's site. The user who will take ownership of the license must have created an account on the licensing website. The new user will not have to create a new Master License.

==Populating the Product Licenses into the Master License==
After the Master License is created, individual product [[licenses]] will need to be added into the Master License. 
#Select your Master License Number
#Click [Add Product License]
#Enter your Product [[Licenses]] exactly as shown either in the CD case or as provided by the vendor.
==Activating the Master License==
[[Activation]] of a license requires the Installation ID from the primary ThinManager server and, if applicable, the Installation ID from the secondary ThinManager server. These IDs are unique and generated from the hardware on the ThinManager Server(s). Licensing does not have to be done from the ThinManager Server, but the IDs must come from the server. 
Installation IDs are found within ThinManager by going to: Install > [[Licenses]]. They will be at the bottom of the window. 
To activate the License: 
#Click the [Activate License] or [Reactivate License] link.
#Populate all required fields and click Submit.
#Download and install the license via Install > [[Licenses]].
----
'''Note''': The ThinManager Licensing system may utilize the MAC address as the basis for the Installation ID. If the MAC address changes, then the Installation ID changes, which would in turn require re-[[activation]] of the license. As an alternative, the Show All button can be clicked on the ThinManager Licensing window to display the MAC address-based Installation ID as well as an OS-based Installation ID. Either can be used when activating the Master License. We recommend the end user to select the one that is less likely to change.
----
===Without Internet Access===
If you do not have Internet access on the ThinManager Server is installed on, you can activate the license on a computer that has does have Internet access and then transfer the license file to the ThinManager Server. 
You will need to write down the installation IDs from the ThinManager Server in order to have your license file generated. Once the license is generated from the Licensing Site, you may transfer it via whatever means is most convenient (USB drive, Network, etc).

==Installing the Master License==
After the Master License has been activated, you will be prompted with a download link to a TMLicense(master license number).lic file. 
#Download this file and transfer it to the ThinManager Server.
#Install the License by going to Install > [[Licenses]], then clicking the "Install License" button.
#Select the .lic file and press Open.
==Post Licensing Best Practices==
It is STRONGLY recommended that a backup of both the license and ThinManager Configuration be made and placed along with all of your other backups. This will prevent having to re-license the software (assuming that no hardware changes have been made) and setting up your Terminals again.
To make a backup of the ThinManager Configuration, go to: Manage > Backup Configuration.
===For instructions with pictures see [https://kb.thinmanager.com/images/b/b3/Licensing.pdf Licensing.pdf]===

MediaWiki:Sidebar

2023-05-01T19:52:35Z

Toddgarmon:

* navigation
** mainpage|mainpage-description
** https://thinmanager.com/latest | Latest Release Info
** https://thinmanager.com/pinpoint | ThinManager Logix PinPoint
** {{fullurl:{{FULLPAGENAME}}|printable=yes}}|Printable Version
*Events
** https://thinmanager.com/webinars | Webinars
** https://thinmanager.com/roadshow | SI Roadshow
** https://thinmanager.com/training/ | Training

MediaWiki:Sidebar

2023-05-01T19:50:25Z

Toddgarmon:

* navigation
** mainpage|mainpage-description
** https://thinmanager.com/latest | Latest Release Info
** {{fullurl:{{FULLPAGENAME}}|printable=yes}}|Printable Version
*Events
** https://thinmanager.com/webinars | Webinars
** https://thinmanager.com/roadshow | SI Roadshow
** https://thinmanager.com/training/ | Training

MediaWiki:Sidebar

2023-05-01T19:49:43Z

Toddgarmon:

* navigation
** mainpage|mainpage-description
** https://thinmanager.com/latest | ThinManager Latest Release
** {{fullurl:{{FULLPAGENAME}}|printable=yes}}|Printable Version
*Events
** https://thinmanager.com/webinars | Webinars
** https://thinmanager.com/roadshow | SI Roadshow
** https://thinmanager.com/training/ | Training

MediaWiki:Sidebar

2023-05-01T19:17:18Z

Toddgarmon:

* navigation
** mainpage|mainpage-description
** randompage-url|randompage
** {{fullurl:{{FULLPAGENAME}}|printable=yes}}|Printable Version
*Events
** https://thinmanager.com/webinars | Webinars
** https://thinmanager.com/roadshow | ThinManager Roadshow
** https://thinmanager.com/training/ | Training

IFIX and Terminal Services

2023-05-01T17:18:33Z

Toddgarmon: Toddgarmon moved page Private:IFIX and Terminal Services to IFIX and Terminal Services

{{lowercase}}
==Introduction==
iFix is a SCADA (System Control and Data Acquisition) software. It was developed by Intellution and is now part of the GE Fanuc Proficy series of industrial software. 
This Wiki Article is a simplified deployment guide for ThinManager users. Although it was prepared with the help of iFix users and specialists, it is a mere aid and not the definitive source for information. '''Please refer to official iFix documentation for questions and details.''' 
A special thanks goes to Scott Crider of Advantage Industrial Automation.
===Topics===
*Network Configuration
*Deployment Choices
*Microsoft Pre-planning
*iFix Installation
*iFix Licensing
*iFix System Configuration
*Profile Manager
*Launching from within ThinManager
*Additional Microsoft Configurations
==Network Configuration==
IFix is designed to pull data out of PLCs and factory-level sensors, present the data in a form usable by humans, and save the data for further usage. iFix is designed to function with a “two-box” system.
*The first box is a SCADA (Systems Control And Data Acquisition) computer. This is a PC that gathers the I/O and data from the PLCs and machinery and runs the iFix database. This computer provides the data and values to the system.
*The second box is a View Node. This is a computer that pulls the data from the SCADA node and displays it on screens for the operator.
In a terminal services environment the terminal server acts as the View node. Each client that connects to a terminal server will start a session and launch a view node within the session. The sessions on the terminal server run the operator screens populated with data from the SCADA node.
<center>[[File:Ifix1.png|Sample iFix Network with Thin Clients]] ''Sample iFix Network with Thin Clients'' </center>
In a ThinManager system dual terminal servers can be setup to provide [[redundancy]] and failover. This allows the operator screens to keep running with current data if a terminal server fails.
==Deployment Choices==
How iFix will be deployed and used influences how iFix is
*Generic Deployment Model– All users use a common SCU file to launch a commonly configured application.
*Specialized Deployment Model – Each user runs a unique environment and each user requires a specially configured SCU file.
This article will assume a generic deployment but will point out where changes need to be made to deploy a specialized configuration. 
The generic deployment can be designed to launch a Main Menu with navigational buttons to allow the user to select the needed screens or the welcome screen can have scripts added that launch the desired screens based on the node name of the client. 
Consult your iFix documentation for details. 

==Microsoft Pre-planning==
There are a few configuration changes that iFix may require on the Microsoft operating system, especially if legacy applications are needed to be upgraded to run on the new system. Consult your iFix documentation for details.
===Relaxed Security===
IFix requires the Relaxed Security setting. This can be applied by opening the '''Terminal Services Configuration''' console by selecting '''Start > Programs > Administrative Tools > Terminal Services Configuration'''. Select the '''Server Setting''' folder and change the '''Permission Compatibility''' setting to '''Relaxed Security'''. 
<center>[[File:Ifix2.png|Terminal Services Configuration – Server Settings]] ''Terminal Services Configuration – Server Settings'' </center>
===Disable DEP (Data Execution Prevention)===
The DEP may need to be disabled for the terminal server to recognize USB license keys. The iFix documentation says:
<pre style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word">
“iFIX Does Not Start After Install Due to DEP Access Restriction (Proficy HMI/SCADA – iFIX [[Release Notes]] VERSION 4.0)
“When you start iKeyDiag or iFIX 4.0 for the the first time, an access violation may occur. You will not be able to start iFIX. This can occur due to hardware enforced DEP (Data Execution Protection) settings within Windows Server 2003 SP1 or Window XP SP2. To remedy this issue, you can selectively add the iFIX program to the DEP exception list or shut down the feature. iFIX will then run normally. For more information, refer to "DEP Support Statement For GE Fanuc Products Using Proficy Common Licensing" article on the GlobalCare site for more information:
http://globalcare.gefanuc.com/kc/kb/glbCarekbinfo.asp?objid=1553203&id=268450132 ”
- iFix Documentation
</pre>
Right Click on the '''My Computer''' Icon and choose '''Properties'''. Select the '''Advanced''' tab, then the '''Settings''' button in the '''Startup and Recovery''' section. Select the (manual) '''Edit''' button on the '''Startup and Recovery Properties''' Window. 
Set the bootloader information to:
<pre style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word">
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINNT="Windows Server 2003, Standard" /fastdetect /NoExecute=alwaysoff
</pre>

===Application Compatibility Script===
The following information is from the iFix e-books under Installing and Configuring iFIX with Windows Terminal Server. Also as a separate Document, it can be found at: 
C:\Program Files\GE Fanuc\ProficyDoc\1033\iFIX\TM.CHM 
Before you begin installing and configuring iFIX on a Terminal Server, it is recommended that you complete the following Windows administrative tasks: 
*Run chkroot.cmd from the C:\Windows\Application Compatibility Script folder. This creates the RootDrv2.cmd file.
*In Notepad or another text editor, open the RootDrv2.cmd file from the C:\Windows\Application Compatibility Script folder. At the end of the file, on the Set RootDrive= line, add a driver letter. For example: Set RootDrive=W:
*Save the RootDrv2.cmd file.
*Run the RootDrv2.cmd file.
*Verify that your Terminal Server is set up and functioning.

==iFix Installation==
The iFix software, like all software, should be installed on a terminal server in the '''Install Mode'''. Do this by selecting '''Start > Settings > Control Panel > Add/Remove Programs > Add New Programs''' and follow the installation wizard.
<center>[[File:Ifix3.png|Terminal Services Installation Warning]] ''Terminal Services Installation Warning'' </center>
A warning will be displayed if you try to install on a terminal server without using the '''Add/Remove Programs''' function.
<center>[[File:Ifix4.png|Setup Type Window]] ''Setup Type Window'' </center>
During the install a Setup Type window will be displayed. 
The Complete selection is the normal choice unless the install is going to run Fix32 graphics using the Fix Desktop. 
<center>[[File:Ifix5.png|Proficy iFix Configure Wizard]] ''Proficy iFix Configure Wizard'' </center>
Proficy iFix Configure Wizard allows the terminal to be configured as a '''View Node'''. It also will be Networked, as shown in the picture. 
The '''SCADA''' radio button will be selected when installing the SCADA node of the system. 
The '''NodeName''' can be left as the default. 
<center>[[File:Ifix6.png|Remote SCADA Node List]] ''Remote SCADA Node List'' </center>
The '''Remote SCADA Node List''' allows the SCADA nodes to be identified. This can be done now or later in the SCADA section of the Systems Configuration Utility.
===Restart after Installation===
Do not do an automatic restart at the end of the installation on a Windows 2003. Instead let the installation finish and then restart the computer manually. This allows the completion of the full install.

==iFix Licensing==
The iFix installation on the terminal server should be licensed before configuration begins. Consult your iFix documentation for details. 
The License Viewer can be launched by selecting '''Start > Programs > Proficy Common > License Viewer'''.
<center>[[File:Ifix7.png|License Viewer]] ''License Viewer'' </center>
The '''Proficy License Viewer''' will display the number of terminal connections that the license allows along with other details.
===Virtual Keyboard===
iFIX provides a virtual keyboard that allows you to work in touch-screen environments or to use a mouse to enter passwords and other data. Install the virtual keyboard on the terminal server to make it available to each client licensed for iFIX. 
To install the virtual keyboard:
*Double-click the LICENSE.EXE file in the Proficy iFIX directory on your terminal server. The IMG License Manager dialog box appears.
*Click Install Service to install the virtual keyboard licenses.
*Click Administration Options & Help. The Terminal Server Administration Option dialog box opens.
*Click Copy Global Settings to All User Folders, then click Yes to confirm.
*Click OK to return to the IMG License Manager dialog box.
*Click Start Service to activate the virtual keyboard for all licensed clients.

==iFix System Configuration for Terminal Services==
iFix is configured with the System Configuration Utility (SCU). The SCU tool allows the selection of startup options and file directories. 
In iFix 3.0 and earlier, each terminal server user had to have a separate SCU (System Configuration Utility) file to allow each user to launch a unique instance of the program. The System Configuration Utility could be run once, then copied into a folder for each user. An additional IP address was need per session. 
In iFix 4.0, a '''Profile Manager''' speeds the configuration process by allowing user settings to be based on the original configuration. 
*If deploying using the Generic Deployment model create one SCU file in the SCU program and then use the Profile Manager to define the additional nodes.
*If deploying using the Specialized Deployment model create a SCU file for each node to define to program.
===Launch iFix===
The first step to configuration is verifying that iFix was installed properly and will run.
Launch the iFix workspace by selecting '''Start > Programs > Proficy HMI SCADA – iFix 4.0 > iFix 4.0'''. It will launch the '''Proficy iFix Startup''' program.
<center>[[File:Ifix8.png|Proficy iFix Startup Window]] ''Proficy iFix Startup Window'' </center>
Select the icon in the '''Proficy iFix''' section to launch the workspace to make sure that iFix will run. 
<center>[[File:Ifix9.png|iFix Workspace]] ''iFix Workspace'' </center>
Once you have verified that the iFix workspace will run it can be closed. 
Launch the SCU tool by selecting '''Start > Programs > Proficy HMI SCADA – iFix 4.0 > System Configuration'''. It will launch the '''Proficy iFix Startup''' program. 
<center>[[File:Ifix10.png|Proficy iFix Startup Window]] ''Proficy iFix Startup Window'' </center>
Select the icon in the SCU section to launch the SCU tool. 
An '''iFix System Information''' window will be launched to allow the path to the SCU files to be chosen. 
<center>[[File:Ifix11.png|iFix System Information]] ''iFix System Information'' </center>
The default path is normally fine. Select the '''OK''' button to proceed.
<center>[[File:Ifix12.png|System Configuration Utility]] ''System Configuration Utility'' </center>
The System Configuration Utility (SCU) allows the components of the project to be defined.
===SCADA Configuration===
SCADA node configuration is managed by selecting '''Configure > SCADA…''' in the System Configuration Utility (SCU) to launch the '''SCADA Configuration.'''
<center>[[File:Ifix13.png|SCADA Configuration]] ''SCADA Configuration'' </center>
The terminal server is not a SCADA node so the '''SCADA Support''' should be disabled on the terminal server. The other features will be grayed out. 
When configuring the SCADA node the SCADA Support is enabled and the database and I/O drivers can be defined. 
Select '''OK''' to accept the configuration.
===Path Configuration===
Select '''Configure > Paths''' in the System Configuration Utility (SCU) to configure the file locations.
<center>[[File:Ifix14.png|Path Configuration]] ''Path Configuration'' </center>
The defaults are usually fine for the Generic Deployment Model. 
If this system will use the Specialized Deployment Model then the '''Local''' path will need to point to where the SCU file will be stored. 
===Network Configuration===
Select '''Configure > Network''' in the System Configuration Utility (SCU) to configure the network.
<center>[[File:Ifix15.png|Network Configuration]] ''Network Configuration'' </center>
The Network configuration window allows the network and SCADA nodes to be defined. 
Select the '''TCP/IP''' radio button for the '''Network'''. 
The SCADA servers are defined by entering their name in the '''Remote Node Name''' filed and selecting the '''Add''' button. 
<center>[[File:Ifix16.png|Defined SCADA Nodes]] ''Defined SCADA Nodes'' </center>
If a SCADA node has a backup SCADA server it can be defined by highlighting the SCADA node and selecting the '''Configure''' button.
<center>[[File:Ifix17.png|Remote Node Configuration]] ''Remote Node Configuration'' </center>
The Primary and Backup SCADA servers that make up the node can be entered to form a logical node. Select OK to accept changes.
<center>[[File:Ifix18.png|Configured Remote Nodes]] ''Configured Remote Nodes'' </center>
When all the SCADA nodes used by the View nodes are defined select '''OK''' to accept the changes.
Save the SCU file by selecting '''File > Save''' or using '''CTRL+S'''.
----
Note: Saving the SCU file is important.
----

==Profile Manager==
Once a SCU file is created and saved it can be applied to many nodes with the Profile Manager. 
----
Note: The Windows user accounts must be created before configuring users in the Profile Manager.
----
iFix must be running to launch Profile Mananger. Select '''Start > Programs > Proficy HMI SCADA – iFix 4.0 > iFix 4.0''' to launch the '''Proficy iFix Workspace'''.
<center>[[File:Ifix19.png|iFix Workspace]] ''iFix Workspace'' </center>
Launch Profile Manager by selecting the Profile Manager icon on the menu or by selecting '''Start > Programs > Proficy HMI SCADA – iFix 4.0 > Startup Profile Manager'''.
<center>[[File:Ifix20.png|Profile Manager Button]] ''Profile Manager Button'' </center>
The Profile Manager button shows two heads in profile against a monitor.
<center>[[File:Ifix21.png|Startup Profile Manager]] ''Startup Profile Manager'' </center>
The '''Startup Profile Manager''' lists the defined profiles. Select the '''Add''' button to configure a profile.
<center>[[File:Ifix22.png|Add Startup Profile]] ''Add Startup Profile'' </center>
Enter the user information in the '''Add Startup Profile''' window.
<center>[[File:Ifix23.png|Configured User]] ''Configured User'' </center>
Enter the Windows user account that the node will use in the '''Window User''' field. 
Enter the iFix node name in the '''iFix Nodename''' field. This can be the ACP ThinManager thin client’s name. 
Select the SCU file that the user will use by selecting the button with three periods. The same SCU file will be used if using the Generic Deployment Model while a different SCU file will be used for each user when using the Specialized Deployment Model. 
Unselect the '''Allow user to run Sample System''' and the '''Allow User to Modify Nodename and SCU''' checkboxes. 
Select '''Add Profile''' to accept the changes. 
Create a profile for each terminal. 
<center>[[File:Ifix24.png|Profile Manager]] ''Profile Manager'' </center>
The '''Profile Manager''' will list the configured nodes with their Windows user name when finished.

==Launching from within ThinManager==
ThinManager can be configured to launch the iFix program automatically. Full details are available in the [http://www.thinmanager.com/wiki/index.php?title=Category:ThinManager ThinManager Category] of this Wiki.
*First create an AppLink Display Client for the iFix Launch program.
*Second, add the iFix Display Client to the terminal and enter a username and password on the Login Information page.
===Configuring a Display Client with iFix===
Right click on the Terminal Services branch of the [[Display Clients]] in the ThinManager tree and select '''Add Display Client'''.
*Name the Display Client.
*Select the '''Application Link''' checkbox on the '''Terminal Services Display Client Options''' page.
*Add the terminal servers with iFix installed on '''the Display Client Members''' page.
*Add the path to the iFix Launch program in the '''Program Path and Filename''' field of the '''AppLink''' page.
The default path is '''C:\Program File\GEFanuc\Proficy iFix\launch.exe'''.
<center>[[File:Ifix25.png|AppLink Page with iFix Launch in Path]] ''AppLink Page with iFix Launch in Path'' </center>
This configures iFix to run when the Display Client is launched.
===Configuring a Terminal to use the iFix Display Client===
The terminal needs to be configured to automatically login and use the iFix Display Client.
*Open the '''Terminal Configuration Wizard''' for the desired terminal by double-clicking on it in the ThinManager tree.
*Select the '''Use [[Display Clients]]''' checkbox on the '''Terminal Mode Selection''' page.
*Add the iFix display client to the '''Selected Display Client List''' on the '''Display Client Selection''' page.
*Add a valid user name and password on the the '''Log in Information''' page of the wizard.
*Select Finish and turn on the terminal.
When the thin client boots it will automatically login to the terminal server and launch iFix with the configuration that was defined by the SCU specified in the Profile Manager for that user.

===Hide the Startup Screen===
Once the system is setup and the users and node are configured the Proficy Startup screen can be turned off so that iFix launches without displaying this window and making the user select iFix from the Startup window.
Open the Startup windows by selecting '''Start > Programs > Proficy HMI SCADA – iFix 4.0 > iFix 4.0'''. It will launch the '''Proficy iFix Startup''' program.
<center>[[File:Ifix26.png|Proficy iFix Startup]] ''Proficy iFix Startup'' </center>
Check the '''Don’t show this dialog box again; always start Proficy iFix''' checkbox. This will launch iFix without requiring the user select iFix from the Startup window.

==Additional Microsoft Configurations==
There are a few Microsoft tweaks that will make the system more efficient. This is a guide. Please refer to iFix and Microsoft documentation for details.
===Add Users to Remote Desktop Group===
User accounts for terminal servers need to be added to the Remote Desktop Users group in Windows. Open the Computer Management console by selecting '''Start > Programs > Administrative Tools > Computer Management'''.
<center>[[File:Ifix27.png|Computer Management Console]] ''Computer Management Console'' </center>
Highlight '''System Tools > Groups''' and double-click on the '''Remote Desktop Users''' group to launch the properties window.
<center>[[File:Ifix28.png|Remote Desktop Users Properties Window]] ''Remote Desktop Users Properties Window'' </center>
Add all the users who will be logging onto the terminal server and select OK.
===End Disconnected Sessions===
Sessions that are disconnected and left on the terminal server should be configured to be logged off when they are disconnected. This can be done by user account or by terminal server.
====User Account====
Configure the desired user accounts by opening the Computer Management console by selecting '''Start > Programs > Administrative Tools > Computer Management'''
<center>[[File:Ifix29.png|Computer Management]] ''Computer Management'' </center>
Highlight '''System Tools > Users''' and double-click on the desired user to launch the user properties.
<center>[[File:Ifix30.png|User Properties – Sessions Tab]] ''User Properties – Sessions Tab'' </center>
Select the '''Sessions''' tab. Set the '''End a disconnected session''' to '''1 minute'''. 
Set the '''When a sessions limit is reached or connection is broken setting''' to '''End Session'''. 
Select '''OK''' to save the changes. 
====Terminal Server Settings====
The terminal server can be configured to have all the sessions logged off after a disconnect in the '''RDP-tcp properties'''. Open the Terminal Services Configuration console by selecting '''Start > Programs > Administrative Tools > Terminal Services Configuration'''.
<center>[[File:Ifix31.png|Terminal Services Configuration Console]] ''Terminal Services Configuration Console'' </center>
Highlight '''Connections''' and double-click on '''RDP-tcp''' to launch the '''RDP-tcp Properties''' window.
<center>[[File:Ifix32.png|RDP-tcp Properties]] ''RDP-tcp Properties'' </center>
Select the '''Sessions''' tab. Check the '''Override user settings''' checkbox and set the '''End a disconnected session''' to '''1 minute'''.
Check the '''Override user settings''' checkbox and set the '''When a sessions limit is reached or connection is broken setting''' to '''End Session'''.
Select '''OK''' to save the changes.
This will make every remote RDP user logoff when they disconnect.
===Set Relaxed Security===
Windows 2000 and Windows 2003 have a Full Security option that can interfere with HMI/SCADA operation. When the 200/2003 Full Security model is used all HMI users will need to be administrators. To allow users to run without being an administrator, set the terminal server to the Relaxed Security based on the NT 4.0 security model.
Open the Terminal Services Configuration console by selecting '''Start > Programs > Administrative Tools > Terminal Services Configuration'''.
<center>[[File:Ifix33.png|Terminal Services Configuration Console]] ''Terminal Services Configuration Console'' </center>
Highlight the '''Server Settings''' on the left and double-click the '''Permission Compatibility''' on the right. 
Select the '''Relaxed Security''' radio button and select '''OK'''. 
===Apply Group Permissions===
An iFix Users group must be created and the iFix users must be added and be granted access permission. It is recommended that iFix users be members of the '''Power User''' group.
Open the Computer Management console by selecting '''Start > Programs > Administrative Tools > Computer Management'''.
<center>[[File:Ifix34.png|Computer Management]] ''Computer Management'' </center>
Right-click on '''Groups''' and select '''New Group'''.
<center>[[File:Ifix35.png|Add New Group]] ''Add New Group'' </center>
Name the group and add members.
<center>[[File:Ifix36.png|Name the group and add members.]] ''Name the group and add members'' </center>
Use the '''Add''' button to add users. 
Add the group to the RDP settings in the '''Terminal Services Configuration''' console. 
Open the Terminal Services Configuration console by selecting '''Start > Programs > Administrative Tools > Terminal Services Configuration'''.
<center>[[File:Ifix31.png|Terminal Services Configuration.]] ''Terminal Services Configuration'' </center>
Double-click on '''RDP-tcp''' to open the '''RDP-tcp Properties'''.
<center>[[File:Ifix38.png|RDP-tcp Properties.]] ''RDP-tcp Properties'' </center>
Select the '''Permissions''' tab. '''Add''' the new group by selecting the Add button. 
Highlight the new group and set the '''Full Control, User Access,''' and '''Guest Access''' to '''Allow'''. 
Select '''OK''' to accept changes.

ThinManager Database Tool

2023-05-01T16:32:27Z

Toddgarmon: Toddgarmon moved page ThinManager Database Tool to Private:ThinManager Database Tool without leaving a redirect

The ThinManager Database Tool is a utility that allows the end user to modify certain values in the configuration database from a command line instead of through the ThinManager interface.

===Examples===
{|cellpadding="3"
|'''[[TMDBT]] --terminal-restart Paint1'''||Connects to the local ThinServer and restarts the terminal that's not in a group named Paint1.
|-
|'''[[TMDBT]] --server 10.50.10.20 Administrator Password --terminal-restart Paint1'''||Same as the above example except the program will connect to the ThinServer at 10.50.10.20 using the specified credentials.
|-
|'''[[TMDBT]] --file commands.csv'''||Parses the file commands.csv for any number of commands.
|-
|'''[[TMDBT]] --terminal-setwindowscredentials Paint1 User1 Password --terminal-restart Paint1'''||Sets the credentials for terminal Paint1 to User1 Password and then restarts it.
|}

===Behavior Notes===
====Credentials====
Wherever new credentials are specified there as three different defined behaviors.
{|cellpadding="3"
|'''UserName'''||Sets the username and leaves the domain field unchanged.
|-
|'''Domain\UserName'''||Sets the username and domain.
|-
|'''.\UserName'''||Sets the username and removes the domain.
|}

====Names and Group Names====
When specifying a Terminal name or a Location name the whole path including groups must be specified.

{|cellpadding="3"
|'''Terminal1'''||Refers to an terminal named Terminal1 that is not a part of any group.
|-
|'''Painting\Paint1'''||Refers to a terminal named Paint1 in the Painting group.
|-
|'''BaseLocation\Room302\PaintBooth'''||Refers to the PaintBooth location that is in the Room302 group that is in the BaseLocation group.
|}

[[Display Client]] names, Terminal Server names, and TermSecure User names are all unique; Only the name is specified.

===Commands===
====Program Behavior====
=====Output=====
By default only errors will be printed to the command prompt. Using one of the below settings will modify this behavior. This argument must be listed first or it will be ignored.
::{|cellpadding="3"
|'''--quiet'''||Suppresses all messages.
|-
|'''--verbose'''||Outputs information from all commands as well as errors.
|}

=====Connection=====
Omitting this parameter will cause the program to connect to the local ThinServer. This argument must be listed first or only be preceded by --quiet / --verbose or it will be ignored.
::{|cellpadding="3"
|'''--server IPAddress User Password'''||Connects to the server specified by IPAddress using the UserName/Password specified.
|}

=====Database Password=====
Provides a password to encrypt the database (ThinManager 11.2 and newer). This is only required when connecting to new installations, upgrades from 11.1 and older, or when restoring a database. This argument must be listed first or only be preceded by --quiet / --verbose / --server or it will be ignored.
::{|cellpadding="3"
|'''--password Password'''||Provides a password to ThinServer to use for configuration database encryption.
|-
|'''--newpassword Password [CurrentPassword]'''||When the require new password flag is set this sets the new database password to Password. CurrentPassword is required if the TMDBT user does not have the Administer ThinServer permission.
|}

=====CSV File=====
Comma delimited CVS file(s) can be specified to make passing commands easier. Any number of files can be specified and intermixed with command-line arguments.
::{|cellpadding="3"
|'''--file FileName'''||Specifies a CSV file to parse for commands. The file must be in the same directory as this program or the full file path must be specified.
|}

====Global====
::{|cellpadding="3"
|'''--restartall WaitTime'''||Restarts all online terminals waiting the specified WaitTime in milliseconds between each.
|-
|'''--rebootall WaitTime'''||Reboots all online terminals waiting the specified WaitTime in milliseconds between each.
|-
|'''--calibratealltouchscreens'''||Initiates the touchscreen calibration on all online terminals.
|-
|'''--replaceallwindowscredentials OldUser NewUser NewPassword'''||Replaces all instances of OldUserName with NewUser and NewPassword.
|-
|'''--clearmacall'''||Clears all terminals IDs. Dissociates the terminal defined in ThinManager from the thin client.
|-
|'''--listcustomvariables [show]'''||Lists all configured custom variables as object name, variable name, visibility. Show is optional to include the custom variable's value.
|}

====ThinServer====
::{|cellpadding="3"
|'''--thinserver-enablesync'''||Enables automatic [[synchronization]]. Requires a primary and secondary ThinManager server to be specified.
|-
|'''--thinserver-disablesync'''||Disables automatic [[synchronization]].
|-
|'''--thinserver-waitforsync [timeout]'''||Waits until the ThinManager server pair has successfully synchronized. The timeout parameter can be optionally added to specify the time in seconds to wait, 15 seconds if not specified. Returns 1 if timeout is reached.
|-
|'''--thinserver-setprimarytmserver ServerName ServerIP'''||Sets ServerName as the the Primary ThinManager server.
|-
|'''--thinserver-setsecondarytmserver ServerName ServerIP'''||Sets ServerName as the Secondary ThinManager server.
|-
|'''--thinserver-addadditionaltmserver ServerName ServerIP'''||Adds ServerName as an additional ThinManager server. Not involved in [[synchronization]].
|-
|'''--thinserver-removetmserver ServerName'''||Removes ServerName as a ThinManager server.
|-
|'''--thinserver-addsecuritygroup GroupName'''||Adds a Windows security group GroupName to manage the ThinManager system.
|-
|'''--thinserver-removesecuritygroup GroupName'''||Removes security group GroupName.
|-
|'''--thinserver-setsecuritygrouppermissions GroupName [[Permissions]]'''||Sets the ThinManager [[permissions]] for GroupName to [[Permissions]]. Comma Delimited list of [[permissions]].
|-
|||e.g. [[TMDBT]] --thinserver-setsecuritygrouppermissions "Local Admins" "Connect,Shadow,Interactive Shadow"
|-
|||Available [[permissions]] vary depending on the installed version of ThinServer. The complete list for a specific system can be found on the [[ThinManager Security Groups]] page of the [[ThinManager Server Configuration]] Wizard.
|-
|'''--thinserver-requirenewdatabasepassword'''||Require a new configuration database password the next time ThinManager is run.
|-
|'''--thinserver-updatedatabasepassword Database Password [CurrentPassword]'''||Sets the specified database password. Database should be 'main' in most cases. CurrentPassowrd is required when the user running the command does not have ThinManager Administration permission.
|-
|'''--thinserver-addscheduledbackup Database OutputFile Repeating TimePeriod [Time]'''||Adds a scheduled backup to the system schedule.
|-
|||Database - 'configuration' or 'biometric'
|-
|||OutputFile - 'auto' or the desired filename to use
|-
|||Repeating - 0 for Once, 1 for Weekly, 2 for Monthly, 3 for Yearly, 4 for Timed
|-
|||TimePeriod - One of the following, based on the value of Repeating:
|-
|||(Once, Yearly) - "YYYY/MM/DD" formatted date
|-
|||(Weekly) - Days - bitfield starting at Sunday - Sun = 1, Mon = 2, Tue = 4, etc. e.g. 127 for every day of the week.
|-
|||(Monthly) - Day of the month - 1-31
|-
|||(Timed) - Minutes. e.g. 3000 for once every 50 hours.
|-
|||Time - Optional 24 hour format "HH:MM" time to run the schedule. Uses the current time if omitted.
|-
|'''--thinserver-addscheduledreport ReportFile OutputFile Repeating TimePeriod [Time]'''||Adds a scheduled report to the system schedule.
|-
|||ReportFile - Filename of the desired report. e.g. TerminalSessionEventsTemplate.csv
|-
|||OutputFile - 'auto' or the desired filename to use
|-
|||Repeating - 0 for Once, 1 for Weekly, 2 for Monthly, 3 for Yearly, 4 for Timed
|-
|||TimePeriod - One of the following, based on the value of Repeating:
|-
|||(Once, Yearly) - "YYYY/MM/DD" formatted date
|-
|||(Weekly) - Days - bitfield starting at Sunday - Sun = 1, Mon = 2, Tue = 4, etc. e.g. 127 for every day of the week.
|-
|||(Monthly) - Day of the month - 1-31
|-
|||(Timed) - Minutes. e.g. 3000 for once every 50 hours.
|-
|||Time - Optional 24 hour format "HH:MM" time to run the schedule. Uses the current time if omitted.
|-
|'''--thinserver-setdns ServerIPs Domain [SearchDomain]'''||Adds a semi-colon delimited list of IP addresses from ServerIPs.
|-
|'''--thinserver-removedns'''||Removes DNS information. Returns system back to 'not using DNS server' state.
|}

====Security====
::{|cellpadding="3"
|'''--security-addgroup GroupName'''||Adds an Access Group named GroupName.
|-
|'''--security-addwindowsgroup GroupName'''||Adds Domain Group as an access group. The domain group must be specified as a path starting with the domain. e.g. ThinManager.com/Users/Engineering
|-
|'''--security-removegroup GroupName'''||Removes GroupName as an Access Group. Removes all [[permissions]] that relies on the GroupName Access Group.
|-
|'''--security-addmemberterminal GroupName TerminalName [inherit]'''||Adds GroupName Access Group to TerminalName. if TerminalName is a terminal group, the inherit parameter can be optionally added to apply to all terminals in that group.
|-
|'''--security-addmemberdisplayclient GroupName DisplayClientName'''||Adds GroupName Access Group to DisplayClientName.
|-
|'''--security-addmemberuser GroupName UserName [inherit]'''||Adds GroupName Access Group to Relevance User UserName. This command is not valid for AD linked users. if UserName is a user group, the inherit parameter can be optionally added to apply to all users in that group.
|-
|'''--security-addmemberlocation GroupName LocationName [inherit]'''||Adds GroupName Access Group to LocationName. The inherit parameter can be optionally added to apply to all sub-locations.
|}

====PXE====
::{|cellpadding="3"
|'''--pxe-enable'''||Enables ThinManager PXE Server.
|-
|'''--pxe-disable'''||Disables ThinManager PXE Server.
|-
|'''--pxe-setmode [AdapterIP] ModeNumber'''||Sets the PXE Mode to ModeNumber. ModNumber: 0 - Using Standard DHCP, 1- with Boot Options, 2 - Not using standard DHCP. AdapterIP can be optionally specified to modify the setting for that adapter only.
|-
|'''--pxe-allownew [AdapterIP]'''||Allow unknown PXE clients to boot from ThinManager. AdapterIP can be optionally specified to modify the setting for that adapter only.
|-
|'''--pxe-disallownew [AdapterIP]'''||Disallow unknow PXE clients. AdapterIP can be optionally specified to modify the setting for that adapter only.
|-
|'''--pxe-addiprange StartIP EndIP RouterIP NetMask'''||Adds IP address range from StartIP to EndIP with a router of RouterIP and subnet mask of NetMask. Only used when PXE mode is set to not using standard DHCP.
|-
|'''--pxe-removeiprange StartIP'''||Removes IP address range starting with StartIP.
|}

====Terminal====
::{|cellpadding="3"
|'''--terminal-restart TerminalName'''||Restarts the terminal with the name TerminalName.
|-
|'''--terminal-reboot TerminalName'''||Reboots the terminal with the name TerminalName.
|-
|'''--terminal-poweroff TerminalName'''||Turns off the terminal with the name TerminalName.
|-
|'''--terminal-disable TerminalName'''||Disables the terminal with the name TerminalName.
|-
|'''--terminal-enable TerminalName'''||Enables the terminal with the name TerminalName.
|-
|'''--terminal-calibratetouchscreens TerminalName'''||Calibrates all touchscreens connected to the terminal with the name TerminalName.
|-
|'''--terminal-calibratetouchscreen TerminalName ScreenNumber'''||Calibrates all touchscreens connected to screen ScreenNumber on the terminal with the name TerminalName.
|-
|'''--terminal-replacewindowscredentials OldUser NewUser NewPassword'''||Replaces all instances of OldUser with NewUser and NewPassword for all terminals.
|-
|'''--terminal-setwindowscredentials TerminalName NewUser NewPassword'''||Sets the credentials for the specified TerminalName to NewUser and NewPassword.
|-
|'''--terminal-setmac TerminalName TerminalMAC'''||Sets the primary TerminalID (MAC) to TerminalMAC for the terminal with the name TerminalName.
|-
|'''--terminal-clearmac TerminalName'''||Clears the TerminalID for terminal TerminalName.
|-
|'''--terminal-sendmessage TerminalName MessageTitle MessageText'''||Creates a message box on terminal TerminalName with MessageTitle as the title and MessageText as the body of the dialog.
|}

====Display Client====
::{|cellpadding="3"
|'''--displayclient-replacewindowscredentials OldUser NewUser NewPassword'''||Replaces all instances of OldUser with NewUser and NewPassword for all [[display clients]].
|-
|'''--displayclient-setwindowscredentials TerminalName DisplayClientName NewUser NewPassword'''||Sets the credentials for the specified DisplayClientName under TerminalName to NewUser and NewPassword.
|}

====Terminal Server====
::{|cellpadding="3"
|'''--terminalserver-disable ServerName'''||Disables the terminal server with the name ServerName.
|-
|'''--terminalserver-enable ServerName'''||Enables the terminal server with the name ServerName.
|-
|'''--terminalserver-replacewindowscredentials OldUser NewUser NewPassword'''||Replaces all instances of OldUser with NewUser and NewPassword for all terminal servers.
|-
|'''--terminalserver-setwindowscredentials TerminalServerName NewUser NewPassword'''||Sets the credentials for the specified TerminalServerName to NewUser and NewPassword.
|-
|'''--terminalserver-getconnectedterminals TerminalServerName'''||Returns a comma separated list of terminal names of terminals connected to TerminalServerName.
|-
|'''--terminalserver-getconnectedterminalsall TerminalServerName'''||Returns a comma separated list of terminal names of terminals connected to TerminalServerName including background sessions for terminals using Instant Failover.
|-
|'''--terminalserver-addrds ServerName IPAddress [ Username Password ] [ [[SmartSession]] ]'''||Creates an RDS server named ServerName with an IP of IPAddress. Username and Password are optional to enable data collection. [[SmartSession]] is optional to enable [[SmartSession]].
|}

====Relevance User (TermSecure)====
::{|cellpadding="3"
|'''--termsecure-setcardnumber Username CardNumber'''||Sets the card id to CardNumber for the specified TermSecure user username.
|-
|'''--termsecure-setcardnumberbywindowsuser WindowsUsername CardNumber'''||Sets the card id to CardNumber for a TermSecure user using a unique Windows username WindowsUsername.
|-
|'''--termsecure-replacewindowscredentials OldUser NewUser NewPassword'''||Replaces all instances of OldUser with NewUser and NewPassword for all TermSecure users.
|-
|'''--termsecure-setwindowscredentials TermSecureUser NewUser NewPassword'''||Sets the credentials for the specified TermSecureUser to NewUser and NewPassword.
|-
|'''--termsecure-setstoredpassword ADUser [ Password ]'''||Allows ThinManager to store ADUser's password. Password is optional, if omitted the password will be collected and stored at next user login.
|-
|'''--termsucure-disablestoredpassword ADUser'''||Disables and removes ADUser's stored password.
|-
|'''--termsucure-setcardlogin Username [ "Password" ] [ "PIN" ]'''||Sets password and/or PIN required for card logins for Username.
|-
|'''--termsucure-setbiometriclogin Username [ "Password" ] [ "PIN" ] '''||Sets password and/or PIN required for biometric logins for Username.
|-
|'''--termsucure-setmanuallogin Username [ "Password" ] [ "PIN" ]'''||Sets password and/or PIN required for manual logins for Username.
|-
|'''--termsucure-setrequirepinchange Username'''||Requires Username to change their PIN at next login.
|-
|'''--termsucure-setpin Username PIN'''||Sets the PIN for Username. Does not verify that the supplied PIN conforms to length or complexity requirements.
|}

====Relevance Location====
::{|cellpadding="3"
|'''--location-replacewindowscredentials OldUser NewUser NewPassword'''||Replaces all instances of OldUser with NewUser and NewPassword for all locations.
|-
|'''--location-setwindowscredentials LocationName NewUser NewPassword'''||Sets the credentials for the specified LocationName to NewUser and NewPassword.
|}