Well, this is another fun day with Microsoft crapware. I am trying to do something that appears to have worked in the past (the tasks were succesfully deployed): run a task that requires Administrator privileges from the SYSTEM account on the local
computer. Trying to use the wizard from RSAT on Windows 7 x86, it always references BUILTIN\SYSTEM as the name of the principal. It is quite clear that is now working. I get the same error over and over.
Log Name: Application
Source: Group Policy Scheduled Tasks
Date: 3/15/2011 1:00:46 PM
Event ID: 4098
Task Category: (2)
Level: Warning
Keywords: Classic
User: SYSTEM
Computer: hostname.addomain.adparent.domain.tld
Description:
The computer 'Daily Profile Cleanup' preference item in the 'OU Policies {3182C8BC-024A-48B4-B856-BE2446DFF53A}' Group Policy object did not apply because it failed with error code '0x80041316 The task XML contains an unexpected node.' This error was suppressed.
I noticed by looking at the raw XML the first time the runAs parameter had NT AUTHORITY unquoted. I obviously was not so careful, and just wrote in NT AUTHORITY\SYSTEM, assuming it would work like before. Unforunately, using the change User or
Group functionality no longer allows me to pick the proper principal, or at least using a name that gives me the right SID. I used the wizard, and it will only let me use BUILTIN\SYSTEM; it says NT AUTHORITY\SYSTEM is unknown. However, the client
now has a different type of error.
Log Name: Application
Source: Group Policy Scheduled Tasks
Date: 3/15/2011 2:04:23 PM
Event ID: 4098
Task Category: (2)
Level: Warning
Keywords: Classic
User: SYSTEM
Computer: hostname.addomain.adparent.domain.tld
Description:
The computer 'Daily Profile Cleanup' preference item in the 'OU Policies {3182C8BC-024A-48B4-B856-BE2446DFF53A}' Group Policy object did not apply because it failed with error code '0x80070534 No mapping between account names and security IDs was done.' This
error was suppressed.
So, I used Sysinternals PsGetSID. Not surprisingly, BUILTIN\SYSTEM does not return a SID. What I really need is NT AUTHORITY\SYSTEM, which does (S-1-5-18). When I try adding this through the wizard "the old way" (opening up the Select
User or Group wizard, changing the location from the domain to the technician workstation I use, input NT AUTHORITY\SYSTEM, and confirm with Check Names), this worked. Now, it fails. If I just put in SYSTEM, it retrieves BUILTIN\SYSTEM, which obvious
is not correctly translating to the proper SID. Good thing this program allows me to input the desired user by SID. Oh wait! It doesn't. I have now tried BUILTIN\SYSTEM, BUILTIN\Local Service, BUILTIN\Network Service (even though it
is a local WMIC command in batch and does not need network access, theoretically). None of them work. I made a backup copy of the XML, then tried manually editing it to use NT AUTHORITY\SYSTEM. The end result, yet another dead end.
Log Name: Application
Source: Group Policy Scheduled Tasks
Date: 3/15/2011 2:25:56 PM
Event ID: 8194
Task Category: (2)
Level: Error
Keywords: Classic
User: SYSTEM
Computer: hostname.addomain.adparent.domain.tld
Description:
The client-side extension could not apply computer policy settings for 'OU Policies {3182C8BC-024A-48B4-B856-BE2446DFF53A}' because it failed with error code '0x8007000d The data is invalid.' See trace file for more details.
So I reverted back to the original, and lo and behold the same old error. Does anyone know how to achieve what I want to accomplish, or is the ability to do that long gone. Below is the XML as it is now, which generates the SID mapping error.