ANAVEM
Languagefr
Windows Active Directory management console showing computer account properties and security audit information
Event ID 4743InformationMicrosoft-Windows-Security-AuditingWindows

Windows Event ID 4743 – Microsoft-Windows-Security-Auditing: Computer Account Changed

Event ID 4743 logs when a computer account is modified in Active Directory, tracking changes to computer objects including attributes, group memberships, and security settings.

Emanuel DE ALMEIDAEmanuel DE ALMEIDA
18 March 20269 min read 0
Event ID 4743Microsoft-Windows-Security-Auditing 5 methods 9 min
Event Reference

What This Event Means

Event ID 4743 represents a fundamental security audit event in Windows Active Directory environments, specifically designed to track modifications to computer account objects. When any change occurs to a computer account in Active Directory, whether through administrative tools, PowerShell commands, or automated processes, this event captures the modification details and logs them to the Security event log on the relevant domain controller.

The event structure includes comprehensive information about the change, including the security identifier (SID) of the account that made the modification, the target computer account that was changed, the specific attributes that were modified, and timestamp information. This granular tracking enables administrators to maintain detailed audit trails for computer account management activities, which is essential for security compliance frameworks like SOX, HIPAA, and PCI-DSS.

Computer account changes tracked by Event ID 4743 include modifications to standard attributes such as description, location, operating system information, and service principal names. The event also captures changes to security-related properties like account control flags, password settings, and group memberships. Advanced scenarios include tracking changes made by automated processes, service accounts, and third-party management tools that interact with Active Directory computer objects.

The event generates on the domain controller that processes the modification request, making it essential to monitor all domain controllers in multi-DC environments. Event correlation across multiple domain controllers provides complete visibility into computer account management activities throughout the Active Directory forest.

Applies to

Windows Server 2019Windows Server 2022Windows Server 2025Windows 10Windows 11
Analysis

Possible Causes

  • Administrator modifying computer account properties through Active Directory Users and Computers console
  • PowerShell cmdlets like Set-ADComputer changing computer account attributes
  • Automated scripts or scheduled tasks updating computer account information
  • Group Policy processing that modifies computer account attributes
  • Third-party Active Directory management tools making computer account changes
  • Service accounts with permissions modifying computer objects programmatically
  • Computer account password changes initiated by the computer itself
  • Changes to computer account group memberships or organizational unit placement
  • Modifications to service principal names (SPNs) associated with computer accounts
  • Updates to computer account control flags or security settings
Resolution Methods

Troubleshooting Steps

01

Review Event Details in Event Viewer

Start by examining the specific details of Event ID 4743 to understand what was changed and by whom.

  1. Open Event Viewer on the domain controller where the event occurred
  2. Navigate to Windows LogsSecurity
  3. Filter for Event ID 4743 using the filter option in the Actions pane
  4. Double-click on the event to view detailed information
  5. Review the following key fields in the event details:
    • Subject: Shows who made the change (Security ID, Account Name, Domain)
    • Target Account: Identifies the computer account that was modified
    • Changed Attributes: Lists specific attributes that were modified
    • Additional Information: Provides context about the change
  6. Note the timestamp and correlate with any known administrative activities
Pro tip: Use the XML view tab to see all event data in structured format, which is helpful for identifying specific attribute changes.
02

Query Events with PowerShell for Pattern Analysis

Use PowerShell to query and analyze Event ID 4743 occurrences across multiple domain controllers for patterns and trends.

  1. Open PowerShell as Administrator on a domain controller or management workstation
  2. Query recent Event ID 4743 occurrences:
    Get-WinEvent -FilterHashtable @{LogName='Security'; Id=4743} -MaxEvents 50 | Select-Object TimeCreated, Id, LevelDisplayName, Message
  3. Filter events for specific computer accounts:
    Get-WinEvent -FilterHashtable @{LogName='Security'; Id=4743} | Where-Object {$_.Message -like "*COMPUTERNAME*"} | Select-Object TimeCreated, Message
  4. Query events from multiple domain controllers:
    $DCs = Get-ADDomainController -Filter *
    foreach ($DC in $DCs) {
        Write-Host "Checking $($DC.Name)..."
        Get-WinEvent -ComputerName $DC.Name -FilterHashtable @{LogName='Security'; Id=4743} -MaxEvents 10 -ErrorAction SilentlyContinue
    }
  5. Export events to CSV for analysis:
    Get-WinEvent -FilterHashtable @{LogName='Security'; Id=4743} -MaxEvents 100 | Select-Object TimeCreated, Id, LevelDisplayName, @{Name='ComputerAccount';Expression={($_.Message -split '\n' | Where-Object {$_ -like '*Account Name:*'})[0]}}, @{Name='ModifiedBy';Expression={($_.Message -split '\n' | Where-Object {$_ -like '*Subject:*'})[1]}} | Export-Csv -Path "C:\Temp\Event4743_Analysis.csv" -NoTypeInformation
Warning: Querying large Security logs can impact domain controller performance. Use -MaxEvents parameter to limit results and run during maintenance windows.
03

Configure Advanced Audit Policies for Better Tracking

Ensure proper audit policy configuration to capture comprehensive computer account change information.

  1. Open Group Policy Management Console on a domain controller
  2. Navigate to the Default Domain Controllers Policy or create a new GPO
  3. Edit the policy and go to Computer ConfigurationPoliciesWindows SettingsSecurity SettingsAdvanced Audit Policy Configuration
  4. Expand Account Management and configure:
    • Audit Computer Account Management: Enable Success and Failure
    • Audit Other Account Management Events: Enable Success
  5. Apply the policy and force update on domain controllers:
    gpupdate /force
  6. Verify audit policy settings using auditpol:
    auditpol /get /subcategory:"Computer Account Management"
  7. Configure Security log size to accommodate increased logging:
    wevtutil sl Security /ms:1073741824
Pro tip: Consider implementing SIEM integration to automatically collect and analyze Event ID 4743 across all domain controllers for centralized monitoring.
04

Investigate Specific Computer Account Changes

Perform detailed investigation of computer account modifications using Active Directory tools and PowerShell.

  1. Identify the target computer account from the Event ID 4743 details
  2. Check current computer account properties:
    Get-ADComputer -Identity "COMPUTERNAME" -Properties * | Select-Object Name, Description, OperatingSystem, LastLogonDate, PasswordLastSet, MemberOf
  3. Review computer account attribute history using repadmin:
    repadmin /showattr DC=domain,DC=com "CN=COMPUTERNAME,CN=Computers,DC=domain,DC=com" /allvalues
  4. Check for recent password changes:
    Get-ADComputer -Identity "COMPUTERNAME" -Properties PasswordLastSet | Select-Object Name, PasswordLastSet
  5. Examine group membership changes:
    Get-ADPrincipalGroupMembership -Identity "COMPUTERNAME$" | Select-Object Name, GroupCategory, GroupScope
  6. Review Service Principal Names (SPNs) if applicable:
    Get-ADComputer -Identity "COMPUTERNAME" -Properties ServicePrincipalNames | Select-Object Name, ServicePrincipalNames
  7. Cross-reference with other security events around the same timeframe:
    Get-WinEvent -FilterHashtable @{LogName='Security'; StartTime=(Get-Date).AddHours(-2); EndTime=(Get-Date)} | Where-Object {$_.Message -like "*COMPUTERNAME*"} | Select-Object Id, TimeCreated, Message
05

Implement Automated Monitoring and Alerting

Set up automated monitoring for Event ID 4743 to detect unauthorized or suspicious computer account changes.

  1. Create a scheduled task to monitor for Event ID 4743:
    $Action = New-ScheduledTaskAction -Execute "PowerShell.exe" -Argument "-File C:\Scripts\Monitor-Event4743.ps1"
    $Trigger = New-ScheduledTaskTrigger -Once -At (Get-Date) -RepetitionInterval (New-TimeSpan -Minutes 15) -RepetitionDuration (New-TimeSpan -Days 365)
    $Settings = New-ScheduledTaskSettingsSet -AllowStartIfOnBatteries -DontStopIfGoingOnBatteries -StartWhenAvailable
    Register-ScheduledTask -TaskName "Monitor-Event4743" -Action $Action -Trigger $Trigger -Settings $Settings -User "SYSTEM"
  2. Create the monitoring script at C:\Scripts\Monitor-Event4743.ps1:
    # Monitor-Event4743.ps1
    $LastCheck = (Get-Date).AddMinutes(-15)
    $Events = Get-WinEvent -FilterHashtable @{LogName='Security'; Id=4743; StartTime=$LastCheck} -ErrorAction SilentlyContinue
    
    if ($Events) {
        foreach ($Event in $Events) {
            $Message = "Computer account change detected: $($Event.Message)"
            Write-EventLog -LogName Application -Source "Custom-Monitor" -EventId 1001 -EntryType Warning -Message $Message
            # Add email notification or SIEM integration here
        }
    }
  3. Configure Windows Event Forwarding (WEF) to centralize Event ID 4743 collection:
    wecutil cs C:\Config\Event4743-Subscription.xml
  4. Create event subscription XML configuration for centralized collection
  5. Set up custom event log source for monitoring alerts:
    New-EventLog -LogName Application -Source "Custom-Monitor"
  6. Test the monitoring system by making a test computer account change and verifying alert generation
Warning: Ensure monitoring scripts have appropriate permissions and error handling to prevent service disruption. Test thoroughly in a lab environment before production deployment.

Overview

Event ID 4743 fires whenever a computer account object is modified in Active Directory. This security audit event captures changes to computer accounts, including modifications to attributes like description, location, operating system version, service principal names, and group memberships. The event generates on domain controllers when administrators or automated processes alter computer account properties through Active Directory Users and Computers, PowerShell cmdlets, or programmatic interfaces.

This event is part of Windows advanced audit policy for account management and requires Object Access auditing to be enabled. Domain controllers log this event in the Security log when computer account changes occur, providing administrators with detailed tracking of modifications to computer objects. The event includes information about who made the change, which computer account was modified, and what specific attributes were altered.

Understanding Event ID 4743 is crucial for security monitoring, compliance auditing, and troubleshooting computer account issues in Active Directory environments. The event helps track unauthorized changes, monitor automated processes that modify computer accounts, and maintain an audit trail for computer object management activities.

Frequently Asked Questions

What does Event ID 4743 mean and when does it occur?+
Event ID 4743 indicates that a computer account was changed in Active Directory. This event fires whenever any modification is made to a computer account object, including changes to attributes like description, operating system information, group memberships, service principal names, or security settings. The event is generated on the domain controller that processes the change and is logged to the Security event log as part of Windows security auditing.
How can I determine what specific changes were made to the computer account?+
The Event ID 4743 details include a 'Changed Attributes' section that lists the specific attributes that were modified. You can view this information in Event Viewer by double-clicking the event and reviewing the event details. For more detailed analysis, use PowerShell to extract the event message content or switch to the XML view in Event Viewer to see structured data. The event also includes before and after values for changed attributes when available.
Why am I seeing multiple Event ID 4743 entries for the same computer account?+
Multiple Event ID 4743 entries for the same computer account can occur for several reasons: each attribute change generates a separate event, automated processes like Group Policy or computer account password changes create regular events, replication between domain controllers can trigger additional events, or third-party management tools may make multiple attribute changes in sequence. This is normal behavior and indicates active management of the computer account.
Can Event ID 4743 help detect unauthorized computer account modifications?+
Yes, Event ID 4743 is valuable for detecting unauthorized computer account changes. By monitoring these events, you can identify modifications made outside of normal administrative processes, changes made by unauthorized users, or suspicious patterns like bulk computer account modifications. Implement automated monitoring to alert on unexpected changes, especially those occurring outside business hours or made by accounts that shouldn't have computer account management permissions.
What should I do if I see Event ID 4743 events I cannot explain?+
If you encounter unexplained Event ID 4743 events, first check the event details to identify who made the change and what was modified. Cross-reference the timestamp with known administrative activities, scheduled tasks, or automated processes. Review the permissions of the account that made the change to ensure it's authorized. Check for corresponding events in other logs that might provide context. If the change appears unauthorized, investigate immediately by reviewing the computer account's current state, checking for other suspicious activities, and potentially resetting the computer account if security is compromised.
Documentation

References (2)

Emanuel DE ALMEIDA
Written by

Emanuel DE ALMEIDA

Senior IT Journalist & Cloud Architect

Microsoft MCSA-certified Cloud Architect | Fortinet-focused. I modernize cloud, hybrid & on-prem infrastructure for reliability, security, performance and cost control - sharing field-tested ops & troubleshooting.

Discussion

Share your thoughts and insights

You must be logged in to comment.

Loading comments...