How to fix Error 1919 on Windows 11

by

Why This Error Happens

Error 1919 combined with “No site name is available for this machine” typically occurs when a client machine cannot resolve its assignment to a management site—most commonly seen in System Center Configuration Manager (SCCM/ConfigMgr) environments or IIS virtual directory creation processes. The root cause is usually a missing or corrupted boundary group configuration, a failure in Active Directory Schema extension lookup, or the client’s inability to query the Management Point (MP) due to WMI repository corruption. In some IIS-specific cases, this error surfaces when the World Wide Web Publishing Service lacks the correct permissions to write to the metabase during virtual directory creation.

Step-by-Step Resolution Guide

Step 1: Verify Boundary Group and Site Assignment

  • Open the SCCM Console and navigate to Administration > Overview > Hierarchy Configuration > Boundary Groups.
  • Confirm the client’s subnet or Active Directory site is correctly mapped to a Boundary Group.
  • Check that the Boundary Group has an associated Management Point assigned under References.

Step 2: Repair the WMI Repository on the Client

  • Open Command Prompt as Administrator on the Windows 11 machine.
  • Run winmgmt /verifyrepository to check for corruption.
  • If corrupted, run winmgmt /salvagerepository followed by a system restart.

Step 3: Re-run the Client Push or Reinstall the Client Agent

  • Navigate to C:\Windows\ccmsetup\ccmsetup.log and review recent entries for site code errors.
  • Manually trigger installation using: ccmsetup.exe /mp:<MP_ServerName> SMSSITECODE=<YourSiteCode>
  • Ensure the correct site code is passed explicitly rather than relying on auto-discovery.

Step 4: Check IIS Permissions (If Applicable)

  • Open IIS Manager and navigate to the affected site under C:\inetpub\wwwroot.
  • Right-click the folder, go to Properties > Security, and confirm IIS_IUSRS has Read & Execute permissions.
  • Restart the World Wide Web Publishing Service via services.msc.

Alternative or Verification Steps

  • Open C:\Windows\ccmsetup\ccmsetup.log or ClientIDManagerStartup.log and confirm the line reading “Successfully created a new SMS BIOS UUID/GUID” followed by a valid site code assignment.
  • If the issue persists, delete the client’s record from SCCM (Devices > Delete), restart the Boundary Groups service, and re-push the client installation using the SMS Provider.