<div>
If you give us more background, like exactly what you're trying to accomplish with this task, we may either have a better idea of how to do it or an easier time solving this issue.
</div>


If you give us more background, like exactly what you're trying to accomplish with this task, we may either have a better idea of how to do it or an easier time solving this issue.

<div>
We are using the immediate task to update the signature in outlook on every GP refresh. The task calls an exe with parameters depending on what OU the user is in. The update pulls info from AD to fill the signature.
</div>


We are using the immediate task to update the signature in outlook on every GP refresh. The task calls an exe with parameters depending on what OU the user is in. The update pulls info from AD to fill the signature.

<div>
Do the users have admin privileges on the machines?
</div>


Do the users have admin privileges on the machines?

<div>
<div class="content wysiwyg-content">
I have a GPO that is pushing an immediate task, which runs fine on most computers. However, on the computers that have the same name as the username the task gets scheduled but it is set to run as a local user instead of a domain user. Typically it runs as domain\username but on these particular computers it sets to run as computername\username. I tried setting it to run in user context with the same result. I also tried a regular scheduled task with the same result.<br />
The task runs as expected when logging in as a different user. The task also cannot not be run under a different user because of the nature of the task.<br />
Any one know why this is happening?
</div>
</div>


I have a GPO that is pushing an immediate task, which runs fine on most computers. However, on the computers that have the same name as the username the task gets scheduled but it is set to run as a local user instead of a domain user. Typically it runs as domain\username but on these particular computers it sets to run as computername\username. I tried setting it to run in user context with the same result. I also tried a regular scheduled task with the same result.
The task runs as expected when logging in as a different user. The task also cannot not be run under a different user because of the nature of the task.
Any one know why this is happening?

Group Policy Preferences - Scheduled Tasks

Active Directory (AD) is a Microsoft brand for identity-related capabilities. In the on-premises world, Windows Server AD provides a set of identity capabilities and services, and is hugely popular (88% of Fortune 1000 and 95% of enterprises use AD). This topic includes all things Active Directory including DNS, Group Policy, DFS, troubleshooting, ADFS, and all other topics under the Microsoft AD and identity umbrella.

Active Directory

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).