Windows

If these are NT Workstations, I assume it is probably erroring out because of a permissions issue. In particular, when triggered by AT, the script is probably running in the context of the logged-on user and unless that user has local administrative authority on that machine, an un-install program would be expected to choke because of inability to write to the registry.

You might have better luck running it as a logon script.

paul

You could try running the AT command with a /interactive switch in the command line as it will use the logged in users rights which may resovle the problem.

You could try running the AT command with a /interactive switch in the command line as it will use the logged in users rights which may resovle the problem.

What account is the schedule (AT) service using?
If you using the local or system accounts for the service it may not have enough rights to run you script/uninstall.

The local/system accounts can't valiated by the domain controller so they will not be able to access network resources.

To verify it isn't an authority problem & to allow access to network resources, change the schedule service account to logon with a domain administrators account and restart the service.

Is the uninstallapplication 16 bit?
Cause unless 16bit apps have access to
the interactive desktop, i.e. /interactive, they most likely will not start as they are required run under Ntvdm.


Re-enter your AT command with /interactive and test.

Good luck, Mike.

If you are wanting to do specialized batches that are not part of a regularly scheduled job you might look into the rclient command. This will allow you to remotely logon to the remote computer with a command prompt and run a job as if you were at the remote computer. Hope this helps.