We recently migrated to 2008 R2 from 2003 and in porting our deployment scripts over have run into an issue with one of our VBS scripts. The script runs locally on the 2008 server under an admin user, UAC has been completely disabled through editing the
local sec policies. We've logged in locally with the admin user account and verified all access across all resources manually (DB, file access, local access, share access etc.). The scripting host has been changed from WScript to CScript.
Instead of boring you with a ton of script the run down is the following:
1. Checks a proprietary database getting necessary information (works flawlessly).
2. Uses information from Step 1, and enumerates information from Active Directory (works flawlessly).
3. Uses the enumerated data from Step 2, and a local resource to generate necessary command lines that run against a local service on the system (works flawlessly).
4. Runs the generated command lines (the issue).
A service invokes the script, which then takes the action above. We've eliminated the service as a functionality issue as we iteratively logged the actions above to a log.
When we run the script manually as the admin account on the server everything runs perfectly, and command lines get executed. When we automate the script we've gotten it to step 4 where it is breaking. We were using a objWMIService.Create(strCMD,...) to invoke the command line actions. We tested this with an objshell.run(strCMD,...) and both yield the same result. Any action that makes calls to the cmd interface gets neutered. We even went as far to redirect standard out to a log and we see no action of the command being executed.
The current thought even with UAC/Admin Mode off, is that any calls to cmdline are running without elevated privileges. Any ideas/suggestions are appreciated.
Thanks,
Easy_Coy