instructions_connectsrv_connectspawnr_start.txt=<h3><a name="Start your SAS/CONNECT Spawner">Start your SAS/CONNECT Spawner</a></h3>

instructions_connectsrv_connectspawnr_start_Windows.txt=<p>The SAS Configuration Wizard has attempted to start the SAS/CONNECT Spawner for you.  If the Server is not currently running (this may be checked by checking for an instance of <b>sas.exe</b> in your process list via the Task Manager), use the shortcut that has been created for you in your Start Menu at: Programs &gt; SAS &gt; Configuration &gt; ${server.shortcut.folder.display.name} &gt; <b>${spawner.connectsrv.shortcut.start.name}</b>.</p>

instructions_connectsrv_connectspawnr_start_Unix.txt=<p>Start the SAS/CONNECT Spawner by executing the following command: </p> ${line.separator}\
<p><strong>${connectspawner.script} start</strong></p> ${line.separator}\

instructions_connectsrv_connectspawnr_start_locale_head.txt=<p>Note: The locale you have chosen requires an additional setup step before starting the server.&nbsp; The details are:</p> ${line.separator}\
${line.separator}\
<ol> ${line.separator}\
  <li>In the SAS Management Console, on the Plug-ins tab, select &quot;+&quot; to expand the Server Manager node.&nbsp;</li> ${line.separator}\
  <li>Highlight the node, <strong>${connectspawner.name}</strong>. Using the right mouse button, select <strong>Properties</strong>.</li> ${line.separator}\
  <li>On the General tab, note the value of the <b>ID:</b> entry.</li> ${line.separator}\
  <li>Using a text editor, edit the file <b>${spawner.connectsrv.cmd}.</b></li> ${line.separator}\

instructions_connectsrv_connectspawnr_start_locale_Windows.txt=<li>Change the value of the variable "SPWNNAME", ex set SPWNNAME=${connectspawner.name}, to use an explicit identifier reference, ex. <b>set SPWNNAME=<i>identifier</i></b>, where <b><i>identifier</i></b> is replaced with the value from the ID: entry noted above.</li></ol>

instructions_connectsrv_connectspawnr_start_locale_Unix.txt=<li>Change the value of the variable "SPWNNAME", ex SPWNNAME=${connectspawner.name}, to use an explicit identifier reference, ex. <b>SPWNNAME=<i>identifier</i></b>, where <b><i>identifier</i></b> is replaced with the value from the ID: entry noted above.</li></ol>

instructions_connectsrv_server_head.txt=<h3>${server.connectsrv.name}</h3> ${line.separator}\

instructions_connectsrv_head_migrated.txt=<h3>SAS Connect Server</h3> ${line.separator}\

instructions_connectsrv_server_details_table_head.txt=<table class="detailTable" border=0 cellPadding=0 cellSpacing=0> ${line.separator}\

instructions_connectsrv_server_details_host.txt=<tr> ${line.separator}\
      <td class="detailLabel">Host machine</td> ${line.separator}\
      <td class="detailContent">${spawner.connectsrv.host}</td> ${line.separator}\
   </tr> ${line.separator}\
   <tr> ${line.separator}\
      <td class="detailLabel">Port</td> ${line.separator}\
      <td class="detailContent">${server.connectsrv.port}</td> ${line.separator}\
   </tr> ${line.separator}\
   
instructions_connectsrv_server_details_migrated_host.txt=<tr> ${line.separator}\
      <td class="detailLabel">Host machine</td> ${line.separator}\
      <td class="detailContent">${spawner.connectsrv.host}</td> ${line.separator}\
   </tr> ${line.separator}\
   <tr> ${line.separator}\
      <td class="detailLabel">Port</td> ${line.separator}\
      <td class="detailContent">${migrated.servers.ports}</td> ${line.separator}\
   </tr> ${line.separator}\

instructions_connectsrv_server_details_logging.txt=<tr> ${line.separator}\
      <td class="detailLabel">Log directory</td> ${line.separator}\
      <td class="detailContent"><a href="${connectsrv.logs.dir}">${connectsrv.logs.dir}</a> ${line.separator}\
       <br class="br">For more details about the initial logging configuration and how to modify it, see "Administering Logging for SAS Servers" in the <em>SAS Intelligence Platform: System Administration Guide</em> at <a href="http://support.sas.com/94administration" target="_blank">http://support.sas.com/94administration</a>.</td> ${line.separator}\
   </tr>  ${line.separator}\
   
instructions_connectsrv_server_details_log_dirs.txt=<tr> ${line.separator}\
      <td class="detailLabel">Log directories</td> ${line.separator}\
      <td class="detailContent"> ${migrated.servers.log.dirs} ${line.separator}\
       <br class="br">For more details about the initial logging configuration and how to modify it, see "Administering Logging for SAS Servers" in the <em>SAS Intelligence Platform: System Administration Guide</em> at <a href="http://support.sas.com/94administration" target="_blank">http://support.sas.com/94administration</a>.</td> ${line.separator}\
   </tr> ${line.separator}\
   
instructions_connectsrv_details_migrated_servers.txt=<tr> ${line.separator}\
      <td class="detailLabel">Servers Migrated</td> ${line.separator}\
      <td class="detailContent">${migrated.servers.names}</td> ${line.separator}\

instructions_connectsrv_server_details_validation.txt=<tr> ${line.separator}\
      <td class="detailLabel">Validation steps</td> ${line.separator}\
      <td class="detailContent">${line.separator}\
         <ol> ${line.separator}\
            <li>In the SAS Management Console, on the Plug-ins tab, select "+" to expand the Server Manager node.</li> ${line.separator}\
            <li>Expand ${server.connectsrv.servercontext.name}.</li> ${line.separator}\
            <li>Expand ${server.connectsrv.logical.name}.</li> ${line.separator}\
            <li>Highlight the ${server.connectsrv.name}.</li> ${line.separator}\
            
instructions_connectsrv_details_validation_migrated.txt=<tr> ${line.separator}\
  <td class="detailLabel">Validation steps</td> ${line.separator}\
  <td class="detailContent">${line.separator}\
     <ol> ${line.separator}\
     For example, validate ${migrated.server.name}, using these steps: ${line.separator}\
   <li>In the SAS Management Console, select "${migrated.server.repository.name}" repository.</li> ${line.separator}\
   <li>On the Plug-ins tab, select "+" to expand the Server Manager node.</li> ${line.separator}\
   <li>Expand ${migrated.server.context}.</li> ${line.separator}\
   <li>Expand ${migrated.server.logical.name}.</li> ${line.separator}\
<li>Highlight the ${migrated.server.name}.</li> ${line.separator}\
                           
instructions_connectsrv_server_details_validation_sasdemo.txt=<li>Right mouse click this server and select Validate (you can enter ${oma.person.demo.login.userid} for the user ID). You should see a <i>Validation Successful</i> message.</li> ${line.separator}\

instructions_connectsrv_server_details_validation_sassrv.txt=<li>Right mouse click this server and select Validate (you can enter the SAS Spawned Servers account for the user ID). You should see a <i>Validation Successful</i> message.</li> ${line.separator}\

instructions_connectsrv_server_details_validation_sasdemosassrv.txt=<li>Right mouse click this server and select Validate (you can enter ${oma.person.demo.login.userid} or the SAS Spawned Servers account for the user ID). You should see a <i>Validation Successful</i> message.</li> ${line.separator}\

instructions_connectsrv_server_details_validation_novaliduser.txt=<li>Right mouse click this server and select Validate. You can enter a user ID and password that meet all of these requirements: ${line.separator}\
   <ol> ${line.separator}\
      <li>the account is known to the host of the connect server. (An ID that ends in @saspw does not meet this requirement.)</li> ${line.separator}\
      <li>the account has the Windows right Log on as a batch job (if the server is on Windows).</li> ${line.separator}\
      <li>the account has a corresponding metadata identity.</li> ${line.separator}\
   </ol> ${line.separator}\
You should see a <i>Validation Successful</i> message.</li> ${line.separator}\

instructions_connectsrv_server_details_validation_tail.txt=</ol> ${line.separator}\
      <b>NOTE</b>: To successfully validate a CONNECT server, the associated spawner must be configured with option ${line.separator}\
      <i>Signon Scripts Allowed</i> set to <i>Yes</i>. ${line.separator}\
      </td> ${line.separator}\
   </tr>  ${line.separator}\


instructions_connectsrv_details_validation_migrated_1.txt=<br> ${line.separator}\
	<br> Repeat all the above steps for the following servers\
	<br><table border=1><tr><th>Repository </th><th>Server Context</th><th> Logical Server</th><th> Server Component</th></tr>\
	${migrated.servers.pairs}</table>\
      
instructions_connectsrv_server_details_table_tail.txt=</table>  ${line.separator}\


instructions_connectsrv_spawner_head.txt=<h3>${spawner.connectsrv.name}</h3> ${line.separator}\

instructions_connectspawner_head_migrated.txt=<h3>Connect Spawner</h3> ${line.separator}\

instructions_connectsrv_spawner_details_table_head.txt=<table class="detailTable" border=0 cellPadding=0 cellSpacing=0> ${line.separator}\

instructions_connectspawner_details_migrated_servers.txt=<tr> ${line.separator}\
      <td class="detailLabel">Connect Spawner Migrated</td> ${line.separator}\
      <td class="detailContent">${migrated.spawner.names}</td> ${line.separator}\

instructions_connectsrv_spawner_details_host.txt=<tr> ${line.separator}\
      <td class="detailLabel">Host machine</td> ${line.separator}\
      <td class="detailContent">${spawner.connectsrv.host}</td> ${line.separator}\
   </tr> ${line.separator}\
   <tr> ${line.separator}\
      <td class="detailLabel">Port</td> ${line.separator}\
      <td class="detailContent">${spawner.connectsrv.operator.port}</td> ${line.separator}\
   </tr> ${line.separator}\
   
instructions_connectsrv_spawner_details_migrated_host.txt=<tr> ${line.separator}\
      <td class="detailLabel">Host machine</td> ${line.separator}\
      <td class="detailContent">${spawner.connectsrv.host}</td> ${line.separator}\
   </tr> ${line.separator}\
   <tr> ${line.separator}\
      <td class="detailLabel">Port</td> ${line.separator}\
      <td class="detailContent">${migrated.operator.ports}</td> ${line.separator}\
   </tr> ${line.separator}\


instructions_connectsrv_spawner_details_services.txt=<tr> ${line.separator}\
      <td class="detailLabel">Execution type</td> ${line.separator}\
      <td class="detailContent">Windows service ${line.separator}\
         <br class="br">${spawner.connectsrv.service.name}</td> ${line.separator}\
   </tr>  ${line.separator}\
   
instructions_connectsrv_spawner_details_migrated_services.txt=<tr> ${line.separator}\
      <td class="detailLabel">Execution type</td> ${line.separator}\
      <td class="detailContent">Windows service ${line.separator}\
         <br class="br">${migrated.servers.services}</td> ${line.separator}\
   </tr>  ${line.separator}\

instructions_connectsrv_spawner_details_scripts_Windows.txt=<tr> ${line.separator}\
      <td class="detailLabel">Execution type</td> ${line.separator}\
      <td class="detailContent">Batch script ${line.separator}\
         <br class="br">${connectspawner.script}</td> ${line.separator}\
   </tr>  ${line.separator}\

instructions_connectsrv_spawner_details_scripts_Unix.txt=<tr> ${line.separator}\
      <td class="detailLabel">Execution type</td> ${line.separator}\
      <td class="detailContent">Shell script ${line.separator}\
         <br class="br">${connectspawner.script}</td> ${line.separator}\
   </tr> ${line.separator}\
   
instructions_connectsrv_spawner_details_scripts_Unix_migrated.txt=<tr> ${line.separator}\
      <td class="detailLabel">Execution type</td> ${line.separator}\
      <td class="detailContent">Shell script ${line.separator}\
         <br class="br">${migrated.servers.unixshell}</td> ${line.separator}\
   </tr> ${line.separator}\

instructions_connectsrv_spawner_details_shortcuts_Windows.txt=<tr> ${line.separator}\
      <td class="detailLabel">Shortcuts</td> ${line.separator}\
      <td class="detailContent">Programs &gt; SAS &gt; Configuration &gt; ${server.shortcut.folder.display.name}</td> ${line.separator}\
   </tr>  ${line.separator}\

instructions_connectsrv_spawner_details_logging.txt=<tr> ${line.separator}\
      <td class="detailLabel">Log directory</td> ${line.separator}\
      <td class="detailContent"><a href="${connectspawner.logs.dir}">${connectspawner.logs.dir}</a> ${line.separator}\
       <br class="br">For more details about the initial logging configuration and how to modify it, see "Administering Logging for SAS Servers" in the <em>SAS Intelligence Platform: System Administration Guide</em> at <a href="http://support.sas.com/94administration" target="_blank">http://support.sas.com/94administration</a>.</td> ${line.separator}\
   </tr>  ${line.separator}\
   
instructions_connectsrv_spawner_details_log_dirs.txt=<tr> ${line.separator}\
      <td class="detailLabel">Log directories</td> ${line.separator}\
      <td class="detailContent"> ${migrated.spawner.log.dirs} ${line.separator}\
       <br class="br">For more details about the initial logging configuration and how to modify it, see "Administering Logging for SAS Servers" in the <em>SAS Intelligence Platform: System Administration Guide</em> at <a href="http://support.sas.com/94administration" target="_blank">http://support.sas.com/94administration</a>.</td> ${line.separator}\
   </tr> ${line.separator}\
   

instructions_connectsrv_start_Zos.txt=<tr> ${line.separator}\
      <td class="detailLabel">Started task</td> ${line.separator}\
      <td class="detailContent">${zos.high.level.qualifier}.${ENC2}.SRVPROC(${spawner.connectsrv.stcname})</td> ${line.separator}\
   </tr> ${line.separator}\

instructions_connectsrv_started_tasks_Zos.txt=<tr> ${line.separator}\
      <td class="detailLabel">Started task</td> ${line.separator}\
      <td class="detailContent">${migrated.servers.stcnames}</td> ${line.separator}\
   </tr> ${line.separator}\
   
instructions_connectsrv_spawner_details_refresh.txt=<tr> ${line.separator}\
      <td class="detailLabel">Spawner Refresh <i>(Required)</i></td> ${line.separator}\
      <td class="detailContent">${line.separator}\
         The '${server.connectsrv.name}' was added to the existing '${connectspawner.name}'. In order to activate this connect server the ${line.separator}\
         following steps must be completed to refresh the spawner configuration. ${line.separator}\
         <ol> ${line.separator}\
            <li>In the SAS Management Console, on the Plug-ins tab, select "+" to expand the Server Manager node.</li> ${line.separator}\
            <li>Highlight '${connectspawner.name}'.</li> ${line.separator}\
            <li>Right mouse click this spawner and select <i>Connect</i>.</li> ${line.separator}\
            <li>Once connected, right mouse click this spawner again and select <i>Refresh Spawner</i>.</li> ${line.separator}\
         </ol> ${line.separator}\
         This will add '${server.connectsrv.name}' configuration to the existing spawner. ${line.separator}\
      </td> ${line.separator}\
   </tr> ${line.separator}\

instructions_connectsrv_spawner_details_table_tail.txt=</table>  ${line.separator}\

warnings_connectsrv_migrated_spawner_oport_conflict.txt=<li>'${connectspawner.name}' had a conflicting operator port configured, <b>${spawner.connectsrv.operator.port.conflict}</b>. This misconfiguration is typically seen when multiple spawners that did not previously have an operator port defined are migrated. The conflict was automatically resolved and the operator port for '${connectspawner.name}' was reconfigured to use port number <b>${spawner.connectsrv.operator.port}</b>.</li>

warnings_connectsrv_migrated_spawner_oport_conflict_unresolved.txt=<li>'${connectspawner.name}' had a conflicting operator port configured, <b>${spawner.connectsrv.operator.port.conflict}</b>. This misconfiguration is typically seen when multiple spawners that did not previously have an operator port defined are migrated. The conflict could not be automatically resolved and the operator port for '${connectspawner.name}' remains configured to use port number <b>${spawner.connectsrv.operator.port}</b>. <b>NOTE</b>: Until the port conflict is resolved this spawner will fail to start.</li>

warnings_connectsrv_services.txt=<li><b>WARNING:</b> One or more issues were encountered during the creation of the service <b>${spawner.connectsrv.service.name}</b>.  Typically this is seen when a service with the same name already exists.  It is important to note though that the dependency chain for this service, and any other services that might depend on it, could be compromised.  Use the Services Manager to check the properties of this service to insure they are correct.  In the event they are not, uninstall this configuration and reconfigue.</li>

warnings_connectsrv_shortcuts.txt=<li><b>WARNING:</b> One or more shortcuts for the SAS/CONNECT Spawner were not created. Verify the following: </li> ${line.separator}\
  <ul> ${line.separator}\
    <li>${error.command} exists</li> ${line.separator}\
    <li><b>${error.commandline}</b> is correct and any files specified exist</li> ${line.separator}\
  </ul> ${line.separator}\

warnings_connectsrv_seassignprimarytokenprivilege.set.txt=<li><p>You indicated that security policies could be modified by the SAS Deployment Wizard. As a result, the user <b>${os.localhost.userid}</b> was granted the local security policy <b>Replace a process level token (SeAssignPrimaryTokenPrivilege)</b>. This policy allows a user to initiate a process to replace the default token associated with a started subprocess and is needed by the SAS/CONNECT Spawner when it spawns SAS/CONNECT Servers.</p> ${line.separator}\
<p>The policy will take effect the next time <b>${os.localhost.userid}</b> authenticates against the operating system.  Therefore, if <b>${os.localhost.userid}</b> is currently logged on to the system and has not previously had this seceurity policy applied to their account, a reboot will be needed so this user can make use of the SAS/CONNECT Spawner.</p></li>

warnings_connectsrv_seassignprimarytokenprivilege.noset.txt=<li><p>You indicated that security policies could not be modified by the SAS Deployment Wizard. As a result, the user <b>${os.localhost.userid}</b> has not been granted the local security policy <b>Replace a process level token (SeAssignPrimaryTokenPrivilege)</b>. This policy is required to use the SAS/CONNECT Spawner to spawn SAS/CONNECT Servers and allows a user to initiate a process to replace the default token associated with a started subprocess.</p> ${line.separator}\
<p>To set this policy now, open the Local Security Policy application via the Control Panel (classic view): Administrative Tools &gt; <b>Local Security Policy</b> or the Control Panel (category view): Performance and Maintenance &gt; Administrative Tools &gt; <b>Local Security Policy</b>.  From the Local Security Policy application, select <b>Replace a process level token</b> and add the user <b>${os.localhost.userid}</b>.</p> ${line.separator}\
<p>The policy will take effect the next time <b>${os.localhost.userid}</b> authenticates against the operating system.  Therefore, if <b>${os.localhost.userid}</b> is currently logged on to the system, a reboot will be needed so this user can make use of the SAS/CONNECT Spawner.</p></li>

warnings_connectsrv_seassignprimarytokenprivilege.set.failed.txt=<li><p>You indicated that security policies could be modified by the SAS Deployment Wizard. However, an error occurred during the attempt to grant the user <b>${os.localhost.userid}</b> the local security policy <b>Replace a process level token (SeAssignPrimaryTokenPrivilege)</b>. This policy allows a user to initiate a process to replace the default token associated with a started subprocess and is needed by the SAS/CONNECT Spawner when it spawns SAS/CONNECT Servers.</p> ${line.separator}\
<p>To attempt to set this policy now, open the Local Security Policy application via the Control Panel (classic view): Administrative Tools &gt; <b>Local Security Policy</b> or the Control Panel (category view): Performance and Maintenance &gt; Administrative Tools &gt; <b>Local Security Policy</b>.  From the Local Security Policy application, select <b>Replace a process level token</b> and add the user <b>${os.localhost.userid}</b>.</p> ${line.separator}\
<p>The policy will take effect the next time <b>${os.localhost.userid}</b> authenticates against the operating system.  Therefore, if <b>${os.localhost.userid}</b> is currently logged on to the system, a reboot will be needed so this user can make use of the SAS/CONNECT Spawner.</p></li>

errors_connectsrv_head.txt=<h3>SAS/CONNECT Server failed to deploy successfully</h3> ${line.separator}\

errors_connectsrv_list_head.txt=<ol> ${line.separator}\

errors_connectsrv_list_tail.txt=</ol> ${line.separator}\

errors_connectsrv_configDirExists.txt=<li><p>A config directory already exists for the connect spawner. This indicates that you are attempting to add a second instance of the spawner or you are attempting to reconfigure the original spawner. You should either choose a unique spawner name to add an additional spawner instance or unconfigure the spawner before trying to reconfigure the spawner.</p></li>

errors_connectsrv_validatePorts.txt=<li><p>SAS/CONNECT Server failed on host ${spawner.connectsrv.host}, port ${server.connectsrv.port}. ${line.separator}\
   <ul> ${line.separator}\
      <li>Error log file: <a href="${error.logfile}" type="text/plain" target="_blank">${error.logfile}</a></li>  ${line.separator}\
      <li>SAS/CONNECT server logs: <a href="${connectsrv.logs.dir}" target="_blank">${connectsrv.logs.dir}</a></li>  ${line.separator}\
      <li>SAS/CONNECT spawner logs: <a href="${connectspawner.logs.dir}" target="_blank">${connectspawner.logs.dir}</a></li>  ${line.separator}\
  </ul></p>  ${line.separator}\

errors_connectsrv_backup.txt=<li><p>Backup of files in both ${error.srcdir} and ${error.deploydir} failed. ${line.separator}\
   <ul> ${line.separator}\
      <li>Error log file: <a href="${error.logfile}" type="text/plain" target="_blank">${error.logfile}</a></li>  ${line.separator}\
      <li>SAS/CONNECT server logs: <a href="${connectsrv.logs.dir}" target="_blank">${connectsrv.logs.dir}</a></li>  ${line.separator}\
      <li>SAS/CONNECT spawner logs: <a href="${connectspawner.logs.dir}" target="_blank">${connectspawner.logs.dir}</a></li>  ${line.separator}\
  </ul></p>  ${line.separator}\
   
errors_connectsrv_moveOrigFiles.txt=<li><p>The copying and configuring of files from ${error.srcdir} to ${error.deploydir} failed. ${line.separator}\
   <ul> ${line.separator}\
      <li>Error log file: <a href="${error.logfile}" type="text/plain" target="_blank">${error.logfile}</a></li>  ${line.separator}\
      <li>SAS/CONNECT server logs: <a href="${connectsrv.logs.dir}" target="_blank">${connectsrv.logs.dir}</a></li>  ${line.separator}\
      <li>SAS/CONNECT spawner logs: <a href="${connectspawner.logs.dir}" target="_blank">${connectspawner.logs.dir}</a></li>  ${line.separator}\
  </ul></p>  ${line.separator}\

errors_connectsrv_loadMetadata.txt=<li><p>Information about the SAS/CONNECT server could not be loaded into the metadata server. ${line.separator}\
   <ul> ${line.separator}\
      <li>Error log file: <a href="${error.logfile}" type="text/plain" target="_blank">${error.logfile}</a></li>  ${line.separator}\
      <li>SAS/CONNECT server logs: <a href="${connectsrv.logs.dir}" target="_blank">${connectsrv.logs.dir}</a></li>  ${line.separator}\
      <li>SAS/CONNECT spawner logs: <a href="${connectspawner.logs.dir}" target="_blank">${connectspawner.logs.dir}</a></li>  ${line.separator}\
  </ul></p>  ${line.separator}\

errors_connectsrv_installShortcuts.txt=<li><p>SAS/CONNECT spawner shortcuts were not created.  Verify the following: ${line.separator}\
   <ul> ${line.separator}\
      <li>${error.command} exists </li> ${line.separator}\
      <li>${error.commandline} is correct and any files specified exist </li> ${line.separator}\
   </ul></p>  ${line.separator}\
</li>  ${line.separator}\
  
errors_connectsrv_installServices.txt=<li><p>The SAS/CONNECT spawner could not be installed as a service.  Verify the following: ${line.separator}\
   <ul> ${line.separator}\
      <li>${error.command} exists</li> ${line.separator}\
      <li>${error.commandline} is correct and any files specified exist </li> ${line.separator}\
   </ul></p>  ${line.separator}\
</li>  ${line.separator}\

errors_connectsrv_startConnectSpawner.txt=<li><p>No SAS/CONNECT spawner listener was detected on the specified host (${spawner.connectsrv.host}) and port (${server.connectsrv.port}). ${line.separator}\
   <ul> ${line.separator}\
      <li>Error log file: <a href="${error.logfile}" type="text/plain" target="_blank">${error.logfile}</a></li>  ${line.separator}\
      <li>SAS/CONNECT server logs: <a href="${connectsrv.logs.dir}" target="_blank">${connectsrv.logs.dir}</a></li>  ${line.separator}\
      <li>SAS/CONNECT spawner logs: <a href="${connectspawner.logs.dir}" target="_blank">${connectspawner.logs.dir}</a></li>  ${line.separator}\
  </ul></p>  ${line.separator}\
</li>  ${line.separator}\

unconfiguration_connectsrv_summary_head.txt=<h3>SAS/CONNECT</h3> ${line.separator}\

unconfiguration_connectsrv_spawner_summary_item.txt=<p>The SAS/CONNECT Spawner was removed.</p> ${line.separator} \
   <ul> ${line.separator}\
      <li>${connectspawner.name} was removed from metadata.</li> ${line.separator}\

unconfiguration_connectsrv_spawner_summary_Windows_services_item.txt=<li>The service named ${spawner.connectsrv.service.name} was stopped and removed.</li> ${line.separator}\
      <li>Shortcuts were removed.</li> ${line.separator}\

unconfiguration_connectsrv_spawner_summary_Windows_scripts_item.txt=<li>Shortcuts were removed.</li> ${line.separator}\
      <li>Because you selected to run as management scripts, the executable for the SAS/CONNECT Spawner could not be stopped and any configuration files in use could not be removed.  Please stop this executable (spawner.exe) yourself via the Task Manager and remove any unwanted files.</li> ${line.separator}\

unconfiguration_connectsrv_spawner_summary_tail.txt=</ul>

unconfiguration_connectsrv_server_summary_item.txt=<p>The SAS/CONNECT Server was removed.</p> ${line.separator} \
   <ul> ${line.separator}\
      <li>${unconfigured.server.name} was removed from metadata.</li> ${line.separator}\
   </ul> ${line.separator}\

unconfiguration_connectsrv_server_refresh_item.txt=<ul><li>Note: In order to activate this change, the following steps must be completed to refresh the spawner configuration. ${line.separator}\
   <ol> ${line.separator}\
      <li>In the SAS Management Console, on the Plug-ins tab, select "+" to expand the Server Manager node.</li> ${line.separator}\
      <li>Highlight '${connectspawner.name}'.</li> ${line.separator}\
      <li>Right mouse click this spawner and select <i>Connect</i>.</li> ${line.separator}\
      <li>Once connected, right mouse click this spawner again and select <i>Refresh Spawner</i>.</li> ${line.separator}\
   </ol></li></ul> ${line.separator}\
   
updatePasswords_connectsrv_summary_head.txt=<h3>SAS/CONNECT Spawner</h3> ${line.separator}\
   <ul> ${line.separator}\

updatePasswords_connectsrv_summary_sastrust_omrconfig_item.txt=<li>The password for ${oma.person.trustusr.person.display.name} (${oma.person.trustusr.login.userid}) was changed in ${connectspawner.config.dir}${file.separator}${spawner.connectsrv.omrconfig.file.name}. ${line.separator}\

updatePasswords_connectsrv_summary_tail.txt=</ul>

#=============================================================
#  changeHost target
#=============================================================
instructions_connectsrv_changeHost_manual_head.txt=<h4>Manual Instructions for SAS Connect Spawner</h4>

instructions_connectsrv_changeHost_manual_steps.txt=<ul><li>The SAS Connect Spawner has been updated with new host name values. Manually start the SAS Connect Spawner by issuing the command: <ul><li><b>${connectspawner.script} ${server.command.start.option}</b></li></ul></li></ul>

instructions_connectsrv_changeHost_manual_steps_zos.txt=<ul><li>The SAS Connect Spawner has been updated with new host name values. Manually start the SAS Connect Spawner using one of the following methods: ${line.separator}\
  <ol>${line.separator}\
    <li>If you are running the spawner from the USS shell, issue the command: ${line.separator}\
      <ul>${line.separator}\
        <li><b>${connectspawner.script} ${server.command.start.option}</b></li>${line.separator}\
      </ul>${line.separator}\
    </li>${line.separator}\
    <li>If you are running the spawner as a started task, start the task <b>${spawner.connectsrv.stcname}</b> from the start system command.</li>${line.separator}\
  </ol>${line.separator}\
</li></ul>${line.separator}\

warnings_connectspawnr_changeHost_shortcuts.txt=<ul><li><b>WARNING:</b> One or more shortcuts for the connect spawner were not created. Verify the following: </li></ul> ${line.separator}\
     <ul> ${line.separator}\
       <li>${error.command} exists</li> ${line.separator}\
       <li><b>${error.commandline}</b> is correct and any files specified exist</li> ${line.separator}\
     </ul>  ${line.separator}\
