Hi, Please disable the Remote UAC on Windows 7 machine to check the result: 1. Click Start, type regedit in the Start Search box, and then click regedit.exe in the Programs list. 2. Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\policies\system 3. Right-click the item, click Export, Save a backup file. 4. On the Edit menu, point to New, and then click DWORD Value. 5. Type LocalAccountTokenFilterPolicy for the name of the DWORD, and then press ENTER. 6. Right-click LocalAccountTokenFilterPolicy, and then click Modify. 7. In the Value data box, type 1, and then click OK. 8. Exit Registry Editor. For more information about Remote UAC, please refer to the following website: http://msdn2.microsoft.com/en-us/library/aa826699.aspxPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi, Please disable the Remote UAC on Windows 7 machine to check the result: 1. Click Start, type regedit in the Start Search box, and then click regedit.exe in the Programs list. 2. Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\policies\system 3. Right-click the item, click Export, Save a backup file. 4. On the Edit menu, point to New, and then click DWORD Value. 5. Type LocalAccountTokenFilterPolicy for the name of the DWORD, and then press ENTER. 6. Right-click LocalAccountTokenFilterPolicy, and then click Modify. 7. In the Value data box, type 1, and then click OK. 8. Exit Registry Editor. For more information about Remote UAC, please refer to the following website: http://msdn2.microsoft.com/en-us/library/aa826699.aspxPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi, i have a server (W2k3) in Domain A and a Windows 7 Client (Domain B). I'm unable to use the following command from the Windows Server 2003. schtasks /Create /S client.domain.b /U domain.b\user /P xxxxx /TN TestCalc /TR calc.exe /ST 12:00 /SD 11/11/2011 Is it unpossible to use the schtasks command from a 2003 Server to manage remotely the task from a Win 7 Client in a different domain? Thanks a lot Sven

Hi, thanks a lot for your reply and sorry for my late response. It's a very good hint and i will keep it in my mind, but the problem will not be solved. It's maybe a problem with the ACL settings and so i send the task to the network team. Regards Sven

Hi, thanks a lot for your reply and sorry for my late response. It's a very good hint and i will keep it in my mind, but the problem will not be solved. It's maybe a problem with the ACL settings and so i send the task to the network team. Regards Sven

The one point was the access rules between the two networks. This problem is solved. A scheduled task can be remotely created, but only when a authenticated connection is available. That means before schtasks /S ... /U ... will be run i had to create a connection to the client, for example \\server.domain.local an then run the schtasks. There will be a problem to use schtasks with the parameter /U or /RU. For me the case is closed. Thanks a lot. Sven