right now, as the script is:

---start---

Dim $CCMSetupProg, $CCMVersion

set $CCMSetupProg = @lserver+"\sysvol\ccmsetup.exe"

if EXIST("c:\windows\system32\ccm\ccmexec.exe")
$CCMVersion = GETFILEVERSION("c:\windows\system32\ccm\ccmexec.exe")
if $CCMVersion = "2.50.3174.1152"

else
shell $CCMSetupProg + " /SLP=SERVER /Advcli /AdvCliCmd SMSCACHESIZE=1024"
? "Found, but out of date - Installing: " @SERROR ?
endif
else
run $CCMSetupProg + " /SLP=SERVER /Advcli /AdvCliCmd SMSCACHESIZE=1024"
? "Not Found - Installing: " @SERROR ?
endif

---end---

the script runs through just fine, but still ccmsetup.exe is not indicated as running at all! Uitilizing RUN I get the following:

Not Found - Installing: The operation completed successfully.

... although utilizing the SHELL command instead, i get:

Not Found - Installing: Incorrect function.

Now, Ive looked into the differences between RUN and SHELL, and what ive found is that I would rather use RUN, becuase it executes the application and moves on right away, which is what would be preferred, becuase ccmsetup.exe is not a quick process and it designed to finish up running in the background anyways; I dont want the script waiting for ccmsetup.exe to finish. SHELL, on the other hand, does wait for the application to finish before it moves onto the next line, and that would not be recommended, although at least getting an error, whether it pertain to syntax or anything, is nice becuase its something i can work with... i get no errors and no results the other way! How should the syntax of SHELL be used in this script?

The reason I want to test this out is becuase everything else thats involved in this script has been scrutinized and there are no hurdles. The ccmsetup.exe is located, you'll notice, on the sysvol share on the DC. There should not be any permissions issues. Checksum on the executable prooves to me that it is a good copy, and as well I have used parent copies of the same execuatable, so i know for sure that it works. As well i have copied the ccmsetup.exe to my own box and ran the script under my administrative credentials of the local box and network, still to no avail. Additionally I check the access stamp attributes of the ccmsetup.exe that I am attempting to use, and they dont change! Furthermore, using the same exact copy of ccmsetup.exe i can manually install the client on machines! Im figuring it is something with the script?! If it is, I dont care, I just want it done with! The rest of the logon script works, but this new section that I am working on. (contemplates a new field!)