>Yesterday, I created a thread about executing a file, in this case schtasks.exe, to enable or disable a task from the Windows Scheduler. By putting Local System in the application pool, this was bypassing the ASP.NET restriction and was allowing the Web site to execute that process.
>
>However, one of the task that we need to handle is on another server. So, the Local System account cannot bypass the server's limit. Anyone would have an idea on what I should do to achieve this challenge?

Using LocalSystem for the application pool seems a bit of a drastic solution. You could use temporary impersonation or delegation only where required.

See http://msdn.microsoft.com/en-us/library/ff647404.aspx#paght000023_impersonatingusinglogonuser for an overview. (It also has a #C example of impersonation using LogonUser.)

If there is a user name and password on the remote machine that exactly matches the impersonating account then you should get the same permissions as that remote user.