Assigning Variable Values to Remote Machines

Use triple equals to avoid type coercion. Also, you say it runs fine on one machine but not remote machines. Did you put a breakpoint in your script and check the values of the variables to compare and see what you are getting?

What happens when the script fails on the remote machines, do you get the log message in your else statement?

I am also wondering if your Sys.HostName is what you expect on the remote machines?

function assignVariables(varName)
{
var machineName = aqString.Replace(Sys.HostName, "-", "");
var concVar = varName + "_" + machineName;
if (Project.Variables.VariableByName(varName)=== concVar){
    Log.Message(Project.Variables.VariableByName(varNa​me) + " now equals " + Project.Variables.VariableByName(varName + "_" + machineName) )
  }else
  { Log.Message(VarName + " not assigned.")
  }
}

Use triple equals to avoid type coercion.

"you have used "=" operator instead of "==". Is this by accident??"

Not an accident, that's on purpose. Most operations return a 1 if they're successful, so writing it that way allows an error catch. It performs the operation as desired, and if true logs a success, but if false logs a failure.

Thanks for the feedback! 

Put some logging in your test to write the machine name and VarName to your test log to see what they are when test execute runs it.Perhaps also do the same for your project variables.
Also, I think you could simplify the way you do your logging message in the if statement. You've already verified that it matches the project variable so just write the project variable to the log rather than build the string again.

function AssignVariables(VarName)
{
var MachineName = aqString.Replace(Sys.HostName, "-", "");
Log.message(MachineName);

var ConcVar = VarName + "_" + MachineName;
Log.message(ConcVar);

if (Project.Variables.VariableByName(VarName) === Project.Variables.VariableByName(ConcVar))
{
Log.Message(Project.Variables.VariableByName(VarName) + " now equals " + Project.Variables.VariableByName(ConcVar) )
}
else
{
Log.Message(VarName + " not assigned.")
}
}

"Run Test Complete on your remote machine"

I wish I could, that would solve the issue altogether. I could run the automation once on each new machine that will run the tests and use the GUI to assign the local values of the needed variables.

Unfortunately, we only have the one node-locked license for TC and several licenses for TE for the remote machines, so I have to work out "creative methods" for getting the local values for the project variables right.

> You can't assign the value of a persistent variable to a persistent variable, it seems. But you can assign a temporary variable to one.

Huh?  I don't think so.  You can easily verify that you can assign the value of a persistent variable to a persistent variable.  I think it is more likely that the variable named by ConcVar contains the empty string.  Assignment of an empty string evaluates to 'false' so the following:

if (Project.Variables.VariableByName(VarName)= Project.Variables.VariableByName(ConcVar))
  {
    ...
  }
else
  {
    Log.Message(VarName + " not assigned.")
  }
}

assigns the empty string to the variable named by VarName, and then falls to the else clause.