keepcalculator

06 Numbers and Powers

iSCSI Initiator Service Event Log Permissions

Card No. 06·82583 · Updated · Standard formula, shown below

The iSCSI Initiator service logs events to the Windows Event Log, and to read or manage those logs you need the appropriate permissions. This article explains what those permissions are, how to check and grant them, and how to troubleshoot common access-denied errors when viewing iSCSI-related events.

What the iSCSI Initiator Service Logs

The Microsoft iSCSI Initiator service (service name MSiSCSI) records operational events in the System log and, on newer Windows versions, in a dedicated Microsoft-Windows-iSCSITarget/Operational log. These events include connection successes, login failures, target discovery results, and session terminations. For administrators troubleshooting storage connectivity, these logs are the first place to look.

Default Permissions on Event Logs

By default, the System log grants Read access to Administrators, Operators, and (on some versions) the Everyone group for reading. The dedicated iSCSI operational log, however, is more restrictive. Only members of the local Administrators group and the SYSTEM account have full access. Standard users typically cannot read the operational log, and even some service accounts may be denied.

How to Check Current Permissions

To see who can access the iSCSI event log, use the wevtutil command or the Event Viewer GUI. For the dedicated log, run:

wevtutil gl Microsoft-Windows-iSCSITarget/Operational

This outputs the log configuration, including the channelAccess string that defines the security descriptor. To view the actual ACL in a readable format, use:

wevtutil gl Microsoft-Windows-iSCSITarget/Operational /f:xml

Look for the channelAccess element. A typical value might be O:BAG:SYD:(A;;0x1;;;AU) which grants Read (0x1) to Authenticated Users (AU). If the string lacks that entry, only administrators can read it.

Granting Read Permissions to a User or Group

If a monitoring agent or a support user needs to read the iSCSI log without being a full administrator, you can modify the channel access. Use the wevtutil command with the /ca parameter. For example, to grant Read access to a domain group called StorageMonitors:

  1. Open an elevated Command Prompt.
  2. Run: wevtutil sl Microsoft-Windows-iSCSITarget/Operational /ca:O:BAG:SYD:(A;;0x1;;;AU)(A;;0x1;;;DOMAIN\StorageMonitors)
  3. Replace DOMAIN with your actual NetBIOS domain name.
  4. Restart the Event Log service or the iSCSI Initiator service for the change to take effect.

Be careful: this replaces the entire security descriptor, so include the existing entries you want to keep. The 0x1 value grants read access; 0x2 would be write access, which is rarely needed for normal monitoring.

Common Access-Denied Errors and Fixes

When you try to open the iSCSI operational log and see “Error: Access is denied”, the cause is usually one of the following:

  • User is not in the required group. Add the user to the local Administrators group, or grant explicit read access as shown above.
  • User Account Control (UAC) filtering. Even an administrator may be denied if the Event Viewer is not elevated. Run Event Viewer as Administrator.
  • Group Policy overrides. Domain policies may restrict event log access. Check the relevant GPO under Computer Configuration → Administrative Templates → Windows Components → Event Log Service.
  • Corrupted log file. If the log is corrupted, you may get access errors. Try clearing the log (if you have permission) or restarting the service.

Using PowerShell to Check and Modify Permissions

PowerShell provides a more scriptable way to manage event log permissions. Use the Get-WinEvent cmdlet to read events, but note that it does not expose the ACL. To modify the ACL, you can use the wevtutil command from PowerShell, or use the .NET classes in the System.Diagnostics.Eventing.Reader namespace. A simple approach is to use the wevtutil command as shown above, since it works in PowerShell as well.

To test if a user can read the log, run as that user:

Get-WinEvent -LogName Microsoft-Windows-iSCSITarget/Operational -MaxEvents 1

If it returns an event, the user has read access. If it throws an UnauthorizedAccessException, the permissions are insufficient.

Frequently Asked Questions

Why can’t I see the iSCSI operational log in Event Viewer?

The log may not be enabled. By default, the operational log is disabled until the iSCSI service starts and logs its first event. If the service is not running or no events have occurred, the log may not appear. Start the iSCSI Initiator service and attempt a connection to generate events.

How do I grant read access to a service account?

Use the same wevtutil command, but specify the service account’s username in the security descriptor. For example, NT SERVICE\MyService or DOMAIN\svc_monitor. Ensure the account has no other restrictions that prevent logon or read access.

Does changing permissions affect the security of the system?

Granting read access to event logs exposes operational details to the granted users. This is generally low risk, but it can reveal IP addresses, target names, and connection patterns. Only grant access to trusted accounts that need this information for monitoring or troubleshooting.

Can I read the iSCSI events from the System log instead?

Yes, many iSCSI events are also written to the System log with source iScsiPrt or iSCSI. The System log is more permissive and may be sufficient for basic troubleshooting. However, the dedicated operational log contains more detailed events, such as login failures with specific error codes.

What if I accidentally lock everyone out of the log?

If you replace the security descriptor with one that excludes Administrators, you can still recover by running wevtutil as SYSTEM (e.g., using PsExec with -s) or by booting into Safe Mode, where the local Administrators group is granted access by default. Always keep an entry for Administrators in the descriptor.

Best Practices for Managing iSCSI Event Log Permissions

  • Grant read access only to accounts that genuinely need it, such as monitoring services or support staff.
  • Use domain groups rather than individual users to simplify management.
  • Document the original security descriptor before modifying it, so you can restore it if needed.
  • Test the access after changes by viewing a single event as the target user.
  • Regularly audit who has access to event logs as part of your security review.

By understanding and controlling event log permissions, you ensure that iSCSI troubleshooting remains effective without compromising security.

Related

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.

More cards in this drawer

The whole Numbers and Powers drawer →