System-A Steam: C:\Program Files\Steam\Steam.exe
System-B Steam: C:\Games\Steam\Steam.exe

I've added system variables to both types of systems, where %GAMES% points to the corresponding path, ie:

System-A Variable: %GAMES% = C:\Program Files
System-B Variable: %GAMES% = C:\Games

From a command line this works perfectly on both systems if I want to launch Steam with autologin:

System-A: %GAMES%\Steam\Steam.exe -login USERNAME PASSWORD
System-B: %GAMES%\Steam\Steam.exe -login USERNAME PASSWORD

But if I enter the above command into the licensing in smartlaunch as follows:

%GAMES%\Steam\Steam.exe -login %license%

only the executable is run and all arguments are left out (it does not input the username or the password) even though the licenses entered below have the username and password. I've even manually typed in a username and password under licensing just for test as follows:

%GAMES%\Steam\Steam.exe -login USERNAME PASSWORD

and it still does not input the arguments when running this from Smartlaunch. Are system variables not usable under licensing or does it disable argument usage?

Bummer.

It's probably related to why you can't use native commands in license management like "COPY" or "MOVE" but instead actual .exe's liek XCOPY will work.

Anyhow, this would have saved me about another months worth of work and a full day or two worth of downtime in my gaming center by reloading/cloning the systems once they do match the same directories. But it will be nice to have the same directories in general (I'm definetely for the C:\Games\ instead of default C:\Program Files) and this will also give me a chance to make it a uniform Vista 64-bit across all systems instead of a mix.