Hi,

We have this OO flow for C: clean-up. However for ESX servers, the OO flow always fails. Just checked the log & found this. Could see few access not granted

______

WriteData (or AddFile): Not granted
AppendData (or AddSubdirectory or CreatePipeInstance): Not granted
WriteEA: Not granted
ReadAttributes: Granted by ACE on parent folder D:(A;;0x1301bf;;;BA)
WriteAttributes: Not granted

______

Kindly suggest what to do ?

Well, this is the event from the log::

Log Name: Security
Source: Microsoft-Windows-Security-Auditing
Date: 8/26/2015 10:49:01 PM
Event ID: 4656
Task Category: File System
Level: Information
Keywords: Audit Failure
User: N/A
Computer: inkerperum01
Description:
A handle to an object was requested.

Subject:
Security ID: ****\a16992167-3
Account Name: a16992167-3
Account Domain: ****
Logon ID: 0x36c0a555

Object:
Object Server: Security
Object Type: File
Object Name: C:\Windows\System32\ServerManager.msc
Handle ID: 0x0

Process Information:
Process ID: 0x2c50
Process Name: C:\Windows\System32\mmc.exe

Access Request Information:
Transaction ID: {00000000-0000-0000-0000-000000000000}
Accesses: READ_CONTROL
SYNCHRONIZE
WriteData (or AddFile)
AppendData (or AddSubdirectory or CreatePipeInstance)
WriteEA
ReadAttributes
WriteAttributes

Access Reasons: READ_CONTROL: Granted by D:(A;;0x1200a9;;;BA)
SYNCHRONIZE: Granted by D:(A;;0x1200a9;;;BA)
WriteData (or AddFile): Not granted
AppendData (or AddSubdirectory or CreatePipeInstance): Not granted
WriteEA: Not granted
ReadAttributes: Granted by ACE on parent folder D:(A;;0x1301bf;;;BA)
WriteAttributes: Not granted

Access Mask: 0x120196
Privileges Used for Access Check: -
Restricted SID Count: 0

Hi,

We have this OO flow for C: clean-up. However for ESX servers, the OO flow always fails

I don't quite understand the meaning of "OO flow", anyway if it is a permitted process in your environment, according from the event message itself, it seems like that Write permissions are not assigned.

You may assign Write permissions to the account which is running under the "OO flow" process, the process then should succeed.

Best Regards,

HP OO is HP Operations Orchestration - used to automate processes

Regarding the write permission, where do we check for this?

 We have a separate account for HO OO flow, so need to check whether that account has the said permissions