{"id":2255,"date":"2020-02-10T11:18:03","date_gmt":"2020-02-10T19:18:03","guid":{"rendered":"https:\/\/portal.staylinked.com\/sl\/kb\/?post_type=ht_kb&p=2255"},"modified":"2022-08-26T14:00:32","modified_gmt":"2022-08-26T21:00:32","slug":"server-administration","status":"publish","type":"ht_kb","link":"https:\/\/portal.staylinked.com\/sl\/kb\/knowledge-base\/server-administration\/","title":{"rendered":"Administrator User Guide – Server Administration"},"content":{"rendered":"\n

This section describes the various\nmeans provided to administer StayLinked servers. One or more servers can be\ndefined for each instance of the administrator application. The level of access\nto the server is controlled by Administrator user IDs and passwords that are\ndefined on each server. <\/p>\n\n\n\n

Defining Servers to the Administrator<\/h3>\n\n\n\n

From the Servers menu, you can Add, Edit or Delete server definitions for this administrator (note: this has no effect on the server itself). You can \u2018Quick Connect\u2019 to a server temporarily. There is an option to Import or Export Server Configuration Files, Print or Export the Server List and you can also log on or log off of a server. <\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Logging On and Logging Off of a Server<\/h3>\n\n\n\n

Each time you start the\nAdministrator, the list of defined servers will appear in the server tree. The\nfirst time you select a server from this list, you will be asked to log on to that\nserver. You will enter your administrator user ID and password for the selected\nserver and will be provided the level of access defined for that specific user\nID on that server. The default user ID for each server is \u2018administrator\u2019 and\nthe default password is \u2018esp\u2019. The default \u2018administrator\u2019 user ID has full\naccess to all of the functions of the StayLinked Administrator and Server.<\/p>\n\n\n\n

You can log off of a server by clicking the right mouse button over the server name and selecting the Log Off option. You will need to log back on again if you want to perform any administration. You will also need to log back on to a server if the server has been restarted since the time you logged on or if you modify any server licensing.<\/p>\n\n\n\n

Detailed information about Stay-Linked Administrator User Management can be found in the article on Administrator Management<\/a>.<\/p>\n\n\n\n

Quick Connect to a server<\/h3>\n\n\n\n

In an Enterprise environment, you might be charged\nwith managing dozens or even hundreds of StayLinked Servers distributed across\nyour wide-area network. You could add each server to the administrator where\nthey will be always available for selection. Or, you can simply \u2018Quick Connect\u2019\nto a server when needed and the server will remain in the servers list until\nyou exit the StayLinked Administrator. When you restart the Administrator, that\nserver will no longer be in the list.<\/p>\n\n\n\n

Export and Import the Server Configuration<\/h3>\n\n\n\n

You may wish to manually backup\nyour StayLinked Server configuration or transfer the configuration to another\nmachine running the StayLinked Server. Using the \u2018Configuration->Export\u2019 and\n\u2018Configuration->Import\u2019 menu options, you can perform these functions. If\nyour Administrator user account is allowed to edit \u2018Server Settings\u2019, then\nthese menu options will be available.<\/p>\n\n\n\n

Export Server Configuration
\n<\/strong>When you select to export the server configuration, you will be prompted\nfor a location to save the \u2018StayLinked Configuration (.slc)\u2019 file that has a\ndefault file name that matches the server name. The export function will create\nan SLC file at this location that contains the configuration files for \u2018Telnet\nHost Groups\u2019, \u2018Device Groups\u2019, \u2018Keyboard Maps\u2019, \u2018Tap Spots\u2019, \u2018Client Settings\u2019,\n\u2018Session Partnerships\u2019 and \u2018Scan2Command\/Configure Profiles\u2019 exported from the\ncurrent StayLinked server.<\/p>\n\n\n\n

Import Server Configuration
<\/strong>When you select to import the server configuration, you will be prompted for the location of the \u2018StayLinked Configuration (.slc)\u2019 file that you wish to import into the current StayLinked server. Once you select a valid SLC file, you will be presented with an \u2018Import\u2019 dialog that will allow you to select one or more of the various configuration files that are contained in the \u201cStayLinked Configuration (.slc)\u201d file:<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Using this dialog, you may\nselect\/deselect the configuration files that you wish to import into the current\nselected StayLinked Server. Once you have selected the desired configuration\nfiles for import, select the \u2018Process->Import\u2019 menu option and you will be\nprompted to confirm that you wish to proceed with the import of the selected\nconfiguration files. Then, a final confirmation will be offered to ensure that\nyou wish to alter the configuration of the current StayLinked Server by importing\nthe selected configuration files into that server. If you are absolutely sure\nthat you wish to proceed with the import, click the \u2018Yes\u2019 button. After the\nselected configuration files have been imported into the current StayLinked\nServer, any new StayLinked Sessions started on this server will be using the\nnewly imported configuration files.<\/p>\n\n\n\n

Printing and Exporting the Server List<\/h3>\n\n\n\n

Print List<\/strong> \u2013 This menu option will send the list of connected\ndevices to a report on your current Windows default printer. The report will\ninclude columns for Device Type, Device Name, MAC Address, IP Address, Client\nVersion and User\/Device ID.<\/p>\n\n\n\n

Export List<\/strong> \u2013 This menu option will export the list of connected\ndevices to a \u2018Comma Separated Variable\u2019 (.csv) file of your choice. The export\nwill include all of the connections and columns that are displayed in the\nConnections List. This format is appropriate for import into common\nspreadsheets and databases.<\/p>\n\n\n\n

Viewing Server Alerts<\/h3>\n\n\n\n

The StayLinked Server records information regarding server status and important events that occur during server operation. When you select \u2018Server Alerts\u2019 from the server tree or the Manage menu, the Server Alerts list will appear in the main display panel.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

The Server Alerts are classified as\none of three levels, Information, Warning and Critical. Each Alert records the\nAlert Level, Alert Date\/Time and the Alert Message. You may view more details\nof a selected alert by double-clicking or selecting the Alerts-Details menu\noption. The Details will usually recommend actions that can be taken to resolve\nWarning or Critical alert conditions. Clicking the right mouse button over an\nalert line will cause a small menu to appear with the following options:<\/p>\n\n\n\n

Details:<\/strong> This menu option displays the details of the selected alert item.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Clear Alerts:<\/strong> Select this option to clear the Server Alert Log that\nis stored on the server.<\/p>\n\n\n\n

Refresh:<\/strong> This menu option reloads the Server Alert listing with the most recent alerts.
<\/p>\n\n\n\n

Managing Server Licenses<\/h3>\n\n\n\n

At least one license must be installed before any clients will be able to start sessions on the StayLinked Server. The StayLinked Server is pre-loaded with a \u2018Demo Mode\u2019 license key. The Demo Mode license should be removed if the server will be used with Pre-Licensed devices.<\/em><\/strong><\/p>\n\n\n\n

When you select \u2018Server Licenses\u2019\nfrom the server tree or the Manage menu, a list of server licenses will appear\nin the main display panel, showing the type of key, serial number and number of\npermanent and temporary seats.<\/p>\n\n\n\n

Any installed temporary license\nkeys that are about to expire will trigger a warning dialog prompting the user\nto contact StayLinked Technical Support to acquire an extension or a permanent\nlicense. This list is color-coded with Green signifying active keys and Red\nsignifying inactive, invalid or expired keys.<\/p>\n\n\n\n

Right mouse click the Server\nLicenses function or anywhere on the main display panel when the list is shown\nto display a small menu. From this menu, you can add a new key, remove an\nexisting key or view license key details. If you select the Remove option, you\nwill be prompted to confirm. If you select the Add option, the Add License window\nwill appear. Using the license information provided to you, enter the Permanent\nClients Quantity, the Temporary Clients Quantity and then cut and paste the\nLicense Key into the field provided. Click \u2018Validate\u2019 and the dialog will be\nupdated to show your license information. Click \u2018Install License Key\u2019 button to\ncomplete the procedure. If the license is successfully installed, then it will\nbe added to the list of licenses for the current server. When a new key is\ninstalled, you will be automatically logged off the current server and then be\nrequired to logon again.<\/p>\n\n\n\n

A new key for the same product and serial number will overwrite an existing key, so it is not necessary to remove the existing key first. In fact, the new key can be entered at any time, and will take immediately take effect on the server (without having to stop and re-start the server).<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

With the release of Server version 15.3 build 214, licenses can be added for a server serial number that does not match the current serial number. This allows for licensing for a backup system to be installed allowing the simple replication of production configuration files between production and backup systems. Both the Server and Administrator must be at least build 214 or the licenses for the alternate system will fail validation.<\/p>\n\n\n\n

When installing a backup license, follow the process to add a license as normal, but click the serial number field to display an additional message.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

This will offer the option to change the default serial number.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Note that the production and backup systems must be a current StayLinked server version. Older StayLinked Server releases may not be able to parse the keys in the proper order, preventing the load or the proper license. Backup and migration keys will display in red as they do not validate on the installation machine and an additional dialogue will display.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Configuring Server Settings<\/h3>\n\n\n\n

When you select Server Settings from the server tree, the Manage Server list or the Manage menu, a window will appear that shows the current server settings and allows you to make changes.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Log File Settings:<\/strong> These options are used to control the server\nlogs. The server logs are used by technical support to analyze connectivity\nissues. This option should be set to \u2018No Logging\u2019 unless otherwise directed by\ntechnical support. The Max Log Size value controls the size of the log files.\nIf desired, you can control the devices that generate logs by specifying a low\nand high IP range. You can disable collection of StdOut and StdErr Java Log\nfiles by unchecking the \u2018Activate StdOut\/StdErr Logs\u2019 checkbox option. You can\nconfigure \u2018Purge Days\u2019 to have old logs purged after they have aged by some\nnumber of days that you can choose.<\/p>\n\n\n\n

Server Statistics Settings:<\/strong> These options have been moved to the\n\u2018Usage Tracking\u2019 feature set. More information on server statistics logging can\nbe found in the Technical Reference, Server Statistics Guide.<\/p>\n\n\n\n

Firewall Settings:<\/strong> If your devices are connecting to the StayLinked\nserver through a firewall, then you may need to restrict the ports that are\nassigned to devices and configure a server that is running behind one-to-one\nNAT.<\/p>\n\n\n\n

Use<\/strong> Fixed\n Port Range<\/strong>:<\/strong> You may enable this option and then\nspecify a range of ports that the server should use for device connections. You\nwill need to ensure that you specify a range that is large enough to\naccommodate the number of licenses that you are running. When there are no\nfurther open ports available, then devices will no longer be able to connect to\nthe server.<\/p>\n\n\n\n

Configure One-to-One NAT:<\/strong> If your server is behind One-to-One NAT\n(Static NAT), then you will need to use the \u2018Configure One-to-One NAT\u2019 dialog\nto specify the server\u2019s mapped external IP and its physical internal IP\naddress.<\/p>\n\n\n\n

Client Dynamic NAT Settings: <\/strong>If your devices are running Dynamic\nNAT behind a NAT Server, then you can configure the StayLinked Server to\nsupport this network architecture.<\/p>\n\n\n\n

Enable Server-Side Support for Client Dynamic NAT:<\/strong> Select this option\nto have the StayLinked Server identify and handle \u2018port re-assignment\u2019 events.\nThese events are generated by the NAT server when the port assignment\ncross-reference times-out due to inactivity. Typically, additional traffic from\nthe device will be re-assigned to a different port by the NAT server. This\nsetting will allow the server to identify these port re-assignments and handle\nthem appropriately.<\/p>\n\n\n\n

Use Public IP for Device Group Selection:<\/strong> This option only applies\nwhen the \u2018Server-side Support for Client Dynamic NAT\u2019 option is enabled. This\noption will cause the \u2018Public IP\u2019 of the NAT Server to be used for selecting\nDevice Groups, rather than using the private, internal IP of the device itself.<\/p>\n\n\n\n

One Session per IP: <\/strong>This option determines how existing sessions\nare handled when a device connects to the server. Check this option to ensure that\neach device consumes only one session. This option prevents duplicate sessions\nfor a single IP. This option only applies to devices running against single\nsession licenses. This option is automatically disabled and locked when the\n\u2018Server-side Support for Client Dynamic NAT\u2019 option is enabled.<\/p>\n\n\n\n

Enable Orphan Detection:<\/strong> Check this option to enable the server to\nidentify devices that have lost their \u2018Session ID\u2019 values. The server will then\ndetect and reconnect devices to any session that has been orphaned for that\ndevice based upon MAC address only. This setting will typically apply to\ndevices that store their \u2018Session ID\u2019 values in volatile memory on the device\nwhere it can easily be lost if the battery is removed for too long, or if the\nbattery is exhausted. This setting is only available if the server is running\n\u2018single session\u2019 licensing only and is not running any \u2018multi session\u2019 licenses.<\/p>\n\n\n\n

Enable User ID Prompt:<\/strong> This option will enable the collection of\nUser Identification information for each device. The User ID Prompt can be used\nto assist with Asset Management or for other purposes. When a device creates a\nnew connection, you will be prompted to enter an User ID value that will be\nvisible on the Connection List, recorded in the Device Identification Log file\nand recorded in the Usage Tracking database if User ID tracking is enabled. The\nvalue entered by the user can be accessed in subsequent scripting and\nsubstitution using the special [userid] mnemonic value.<\/p>\n\n\n\n

Pre-Telnet Timeout:<\/strong> Enter the number of seconds of inactivity,\nprior to starting a telnet session, before terminating the connection. This\ntimeout will work when the user is on the \u2018User ID Prompt\u2019, waiting to enter\nSSH credentials or sitting on a \u2018Select a Host\u2019 menu.<\/p>\n\n\n\n

Multi Sessions:<\/strong> This drop-down list provides for the configuration\nof the number of sessions that will be allowed per device when the server is\nlicensed for Multi Session TE. The valid values are from 2 sessions to 10\nsessions per device. This option will not be available if you do not have a\nMulti Session TE License installed on the server. The default value for this\nsetting is 2 sessions.<\/p>\n\n\n\n

JRE Encoding:<\/strong> This is a legacy setting that will only affect Servers\nprior to version 10. This setting selects the code page for Java string encoding\nused by the server. Generally, this value should be set to \u2018*default\u2019. This\nvalue may need to be set to match the code page of the machine upon which the\nserver is running. If running servers older than Version 10, and the session\nscreens on the devices are not displaying the expected characters, then you\nmight need to adjust this value. For instance, in order to properly render VT\nline-draw characters, we recommend setting this value to \u2018cp437\u2019. For servers\nrunning Version 10 and newer, you can get VT line-draw support by running your\nTelnet Host Entry with \u2018VT-UTF8\u2019 terminal emulation.<\/p>\n\n\n\n

Encryption:<\/strong> Select whether to enable encryption for all StayLinked\nsessions:<\/p>\n\n\n\n

None<\/strong> \u2013 No StayLinked packets will be encrypted.
Level 1<\/strong> \u2013 StayLinked data transferred between the Stay-linked Thin Client and the StayLinked Server will be encoded using a proprietary 64-bit encryption scheme.
Blowfish<\/strong> \u2013 StayLinked data transferred between the Stay-linked Thin Client and the Server will be encoded using the Blowfish\/CBC\/PKCS5Padding encryption algorithm.
Twofish<\/strong> \u2013 (v15.3) StayLinked data transferred between the Stay-linked Thin Client and the Server will be encoded using the Twofish\/CBC\/PKCS5Padding encryption algorithm.<\/p>\n\n\n\n

(See Secure Communications Guide\nfor details about Encrypted connections)<\/p>\n\n\n\n

Using Blowfish Encryption:<\/strong> Blowfish encryption provides high level data security for the StayLinked packets that are transmitted between the StayLinked Thin Client and the StayLinked Server. StayLinked Blowfish encryption is available only for PPC\/WM\/CE\/CE.Net devices that are running a StayLinked Client of at least Version 9.1.0. When you select \u2018Blowfish\u2019 as the StayLinked Encryption option, you are presented additional options in the Server Settings dialogue as described in the server settings and secure communications articles.<\/p>\n\n\n\n

Using Twofish Encryption:<\/strong> Twofish encryption provides expanded data security for the StayLinked packets that are transmitted between the StayLinked Thin Client and the StayLinked Server. StayLinked Twofish encryption is available only for devices that are running a StayLinked Client of at least Version 15.3. Android and iOS Clients may also utilize the Twofish\/GCM\/NoPadding encryption when running a server of at least build 214 and compatible Clients. When you select \u2018Twofish\u2019 as the StayLinked Encryption option, you are presented additional options in the Server Settings dialogue as described in the server settings and secure communications articles.<\/p>\n\n\n\n

Key 1, Key 2, Key 3 and Key 4:<\/strong> You may specify one to four blowfish\nkeys. Each key can be from 8 characters to 56 characters in length. The keys\nare case sensitive. The Encryption capabilities of the Java Runtime used by the\nserver will determine the maximum key length that can be used. If the Java\nRuntime does not support a key of the length that you have entered, that key\nwill be automatically trimmed until it can be used. The server will only use\nKey 1 unless you specify a \u2018Key Rotation Interval\u2019.<\/p>\n\n\n\n

Allow Unencrypted Sessions:<\/strong> This option will determine whether\nsessions will be allowed for clients that do not support Blowfish encryption.\nIf you have a mix of DOS and PPC devices and you want them all to be able to\nrun sessions, and you want to use Blowfish encryption for the PPC devices, then\nyou must check this option to allow the unencrypted sessions from the DOS\ndevices. In this case, the DOS devices will utilize the \u2018Level 1\u2019 encryption\ninstead of the Blowfish encryption. If you want to restrict your server to\nallow sessions only for devices that support Blowfish encryption, then uncheck\nthis option. In this case, any unsupported device that tries to start a session\nwill get a \u2018Device Not Allowed\u2019 message displayed when a session is started.\nThose devices that do not support Blowfish encryption will not be able to run\nany sessions.<\/p>\n\n\n\n

Key Rotation Interval (mins):<\/strong> If you enter more than one Blowfish key, then you may have the StayLinked Server automatically rotate between those keys at your specified interval in minutes. The valid range for the Key Rotation Interval in 5 minutes to 1440 minutes. The StayLinked Client and Server will automatically rotate between keys at each rotation interval during the entire duration of the StayLinked session.<\/p>\n\n\n\n

Maintenance Mode<\/h3>\n\n\n\n

With the release of Server version 15.3 build 214, servers will offer an option for Maintenance Mode. This allows management of the server, but prevents the creation of any new sessions. Devices attempting to connect to a server in this state will show the standard message 'Err: Host Timeout!' meaning that the device did not receive a response from the Server.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Selecting this option will require the user to provide the password for their credentials and an additional confirmation.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Selecting the option again will prompt the end maintenance mode and allow new sessions.<\/p>\n\n\n\n

Terminating a Running StayLinked Server<\/h3>\n\n\n\n

The Terminate Server option is used\nto disconnect all client sessions and terminate the server jobs. On the IBM i\nplatform, the server subsystem is not terminated by this command, but all\nsubsystem jobs are terminated. All client sessions will be sent a terminate\nmessage. Those devices that are asleep at this moment will not receive the\nterminate message. Upon waking, these devices will go to a [Session Ended]\nstate if the StayLinked Server is running or they will go into a [Linking]\nstate if the StayLinked Server is not running.<\/p>\n\n\n\n

When you select Terminate Server\nfrom the server tree or the Manage menu, you will be prompted for, and must\nenter your password in order to terminate the server.<\/p>\n","protected":false},"excerpt":{"rendered":"

This section describes the various means provided to administer StayLinked servers. One or more servers can be defined for each instance of the administrator application. The level of access to the server is controlled by Administrator user IDs and passwords that are defined on each server. Defining Servers to the…<\/p>\n","protected":false},"author":7,"comment_status":"open","ping_status":"closed","template":"","format":"standard","meta":[],"ht-kb-category":[23],"ht-kb-tag":[],"yoast_head":"\nAdministrator User Guide - Server Administration – StayLinked<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.staylinked.com\/knowledge-base\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Administrator User Guide - Server Administration – StayLinked\" \/>\n<meta property=\"og:description\" content=\"This section describes the various means provided to administer StayLinked servers. One or more servers can be defined for each instance of the administrator application. The level of access to the server is controlled by Administrator user IDs and passwords that are defined on each server. Defining Servers to the...\" \/>\n<meta property=\"og:url\" content=\"https:\/\/portal.staylinked.com\/sl\/kb\/knowledge-base\/server-administration\/\" \/>\n<meta property=\"og:site_name\" content=\"StayLinked\" \/>\n<meta property=\"article:modified_time\" content=\"2022-08-26T21:00:32+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/portal.staylinked.com\/sl\/kb\/wp-content\/uploads\/2020\/02\/UserAdminGuide_112-1024x588.jpg\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data1\" content=\"17 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebSite\",\"@id\":\"https:\/\/portal.staylinked.com\/sl\/kb\/#website\",\"url\":\"https:\/\/portal.staylinked.com\/sl\/kb\/\",\"name\":\"StayLinked Knowledge Base\",\"description\":\"Partner Portal Resources and Support\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":\"https:\/\/portal.staylinked.com\/sl\/kb\/?s={search_term_string}\",\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-US\"},{\"@type\":\"ImageObject\",\"@id\":\"https:\/\/portal.staylinked.com\/sl\/kb\/knowledge-base\/server-administration\/#primaryimage\",\"inLanguage\":\"en-US\",\"url\":\"https:\/\/portal.staylinked.com\/sl\/kb\/wp-content\/uploads\/2020\/02\/UserAdminGuide_112.jpg\",\"contentUrl\":\"https:\/\/portal.staylinked.com\/sl\/kb\/wp-content\/uploads\/2020\/02\/UserAdminGuide_112.jpg\",\"width\":1210,\"height\":695},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/portal.staylinked.com\/sl\/kb\/knowledge-base\/server-administration\/#webpage\",\"url\":\"https:\/\/portal.staylinked.com\/sl\/kb\/knowledge-base\/server-administration\/\",\"name\":\"Administrator User Guide - Server Administration – StayLinked\",\"isPartOf\":{\"@id\":\"https:\/\/portal.staylinked.com\/sl\/kb\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/portal.staylinked.com\/sl\/kb\/knowledge-base\/server-administration\/#primaryimage\"},\"datePublished\":\"2020-02-10T19:18:03+00:00\",\"dateModified\":\"2022-08-26T21:00:32+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/portal.staylinked.com\/sl\/kb\/knowledge-base\/server-administration\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/portal.staylinked.com\/sl\/kb\/knowledge-base\/server-administration\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/portal.staylinked.com\/sl\/kb\/knowledge-base\/server-administration\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/portal.staylinked.com\/sl\/kb\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Articles\",\"item\":\"https:\/\/portal.staylinked.com\/sl\/kb\/knowledge-base\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Administrator User Guide – Server Administration\"}]}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","_links":{"self":[{"href":"https:\/\/portal.staylinked.com\/sl\/kb\/wp-json\/wp\/v2\/ht-kb\/2255"}],"collection":[{"href":"https:\/\/portal.staylinked.com\/sl\/kb\/wp-json\/wp\/v2\/ht-kb"}],"about":[{"href":"https:\/\/portal.staylinked.com\/sl\/kb\/wp-json\/wp\/v2\/types\/ht_kb"}],"author":[{"embeddable":true,"href":"https:\/\/portal.staylinked.com\/sl\/kb\/wp-json\/wp\/v2\/users\/7"}],"replies":[{"embeddable":true,"href":"https:\/\/portal.staylinked.com\/sl\/kb\/wp-json\/wp\/v2\/comments?post=2255"}],"version-history":[{"count":4,"href":"https:\/\/portal.staylinked.com\/sl\/kb\/wp-json\/wp\/v2\/ht-kb\/2255\/revisions"}],"predecessor-version":[{"id":4091,"href":"https:\/\/portal.staylinked.com\/sl\/kb\/wp-json\/wp\/v2\/ht-kb\/2255\/revisions\/4091"}],"wp:attachment":[{"href":"https:\/\/portal.staylinked.com\/sl\/kb\/wp-json\/wp\/v2\/media?parent=2255"}],"wp:term":[{"taxonomy":"ht_kb_category","embeddable":true,"href":"https:\/\/portal.staylinked.com\/sl\/kb\/wp-json\/wp\/v2\/ht-kb-category?post=2255"},{"taxonomy":"ht_kb_tag","embeddable":true,"href":"https:\/\/portal.staylinked.com\/sl\/kb\/wp-json\/wp\/v2\/ht-kb-tag?post=2255"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}