I am attempting to deploy a .exe. that is dependant on the O/S version, i.e. x32 vs x64. I have the two .exe files sitting on our netlogon share- I chose not to upload to BF because the task sits there at pending download even after 3 days. I am using “if” “then” to determine the O/S version which is working but the command I am using to deploy it is failing because of “illegal characters”.I attempt to run this in the Fixlet Debugger and it i get tons of “illegal character: ‘’” errors. I thought these were OK to use but i guess i was wrong. A copy of the script is below. I did this so any assistance is greatly appreciated.
If ((name of it = “Win2003” AND x64 of it) of operating system) then
Are you a TEM Lifecycle Management customer? All of this can very easily be accomplished using the software delivery tools within TEM LM. This includes adding relevance for proper targeting etc. The only caveat is you will want/need to upload the packages to the TEM server to deploy. TEM does not natively support deployment via UNC. If you insist on deploying via UNC, you should probably create a batch or vbs file that will do the deployment silently and then execute that batch file via TEM.
Again, your best bet is to upload to the server and use the native download features of TEM. If you are having a problem where it shows pending downloads, then we should troubleshoot that issue and resolve. Entries from the client log can help, also the process you used to upload the files and create the task.
You’ll have problems with share access permissions since our service runs as the “Local System” account.
Consider putting the file up on any http so you can use the download command.
If you want to use our relay infrastructure, use the “download” or “download as” command. If you want endpoints to go directly to the http server skipping our relay infrastructure, use the “download now as”.
Also I notice your using relevance substitution in your “if” statement. Remember to wrap that up with { } and not just simple ( ) brackets.