|
First to Kent. I have tried those two forms, with the first one being copied directly from their site, with modification to your_server_name, of course, with no luck. And on my system, SHELL in the logon script always causes an error.
To Glenn, I did something very similar to what you show. I found it in one of the forums (fori, fora?) but I don't think I tried the comspec peice, just created the CMD to be '"\\yuponas\ezaudit\ezstart.exe" /auto' and ran the command. The message "about to run \\yuponas\...." shows up fine, but again, the actual program never runs.
Some explanation of the environment: the logon script runs on our domain controller, and just before the attempt to run ezaudit, the script adds yuponas as a mapped drive. The messages saying yuponas has been added always show up. The next command is the run.
Question about the KiXtart script: could the issue be about where the two objects reside? I am assuming that the script basically runs locally on the PC that's logging on, which has access to yuponas by the time the run command is supposed to be executed. Nothing in the ezaudit literature says I have to have any executable on the PC's themselves. Just kind of rambling here, but ezaudit folks say they've got 10,000 users and have very few calls to their support desk, so I'm missing something here.
| 
