By using this site, you agree to the Privacy Policy.
Accept
EnterinITEnterinITEnterinIT
  • HOME
  • IT PRO
  • TECH
  • MICROSOFT
    • Azure
    • ConfigMgr/SCCM
    • DPM
    • Orchestrator
    • Hyper-V
    • Microsoft Edge Insider
    • MSI
    • Office 365
    • Office Insider
    • Power BI
    • Skype
    • SQL Server
    • Teams
  • WINDOWS
    • Windows Admin Center
    • Windows Client
    • Windows Server
  • SCCM Query Collection List
Reading: SCCM Error 0x87d00269: Failed to Run Task Sequence due to Management Point Not Found
Font ResizerAa
EnterinITEnterinIT
Font ResizerAa
  • HOME
  • IT PRO
  • TECH
  • MICROSOFT
  • WINDOWS
  • SCCM Query Collection List
Search
  • HOME
  • IT PRO
  • TECH
  • MICROSOFT
    • Azure
    • ConfigMgr/SCCM
    • DPM
    • Orchestrator
    • Hyper-V
    • Microsoft Edge Insider
    • MSI
    • Office 365
    • Office Insider
    • Power BI
    • Skype
    • SQL Server
    • Teams
  • WINDOWS
    • Windows Admin Center
    • Windows Client
    • Windows Server
  • SCCM Query Collection List
Configuration Manager Query Collection List
ConfigMgr

SCCM Error 0x87d00269: Failed to Run Task Sequence due to Management Point Not Found

Published February 11, 2024
2 Min Read
SHARE

SCCM Error 0x87d00269: Failed to Run Task Sequence due to Management Point Not Found. Required management point not found. Error: 0x87d00269. At any point during OSD when the TS fails you examine smsts.log file. In this case, the smsts.log had an error 0x87d00269. So looking at the error, the initial assumption is the client is unable to contact the management point.

Further investigation using ClientLocation.log suggests Location detection issues:

Current Management Point is <empty>.
Workgroup client is in Unknown location.
Local machine is not a member of an AD domain.

LocationServices.log is littered with errors again suggesting that there are connectivity issues:

Unable to find lookup MP(s) in Registry, AD, DNS and WINS.
Workgroup client is in Unknown location.
Attempting to retrieve lookup MP(s) from DNS.
DNS Suffix not specified.
No lookup MP(s) from DNS.
Failed to resolve 'SMS_SLP' from WINS.
No lookup MP(s) in Registry, AD, DNS, and WINS.
Won't send a client assignment fallback status point message because the last assignment error matches this one.

The client is unable to find the MP in the Registry, AD, DNS, or WINS. Attempting to ping the management point server from the command line of the client also failed, but pinging the FQDN of the server worked.

Edit the task sequence. Click Setup Windows and ConfigMgr step and add SMSMP=sccm server FQDN.

TAGGED:System CenterSystem Center Configuration ManagerTechnical PreviewWindowsWindows 10
Previous Article Configuration Manager Query Collection List Configuration Manager an error occurred while retrieving policy for this computer 0x80004005
Next Article Microsoft To-Do app gets new snooze options
Leave a Comment Leave a Comment

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Translation

English中文(简体)DanskNederlandsFrançaisDeutschItaliano한국어PolskiPortuguêsRomânăEspañolУкраїнська
by Transposh - translation plugin for wordpress

Popular Posts

System Requirements for Windows Server 2016
Windows Server
Configuration Manager Query Collection List
Configuration Manager Query Collection List
ConfigMgr
Structured/Managed Navigation enabled on Modern Pages in Classic Team Sites
Tech
SCCM Failed to get DP locations as the expected version from MP
ConfigMgr

Recent Posts

Installing and Configuring Fail2ban for SSH Protection on Ubuntu 24.04
Linux
Enabling and Configuring FirewallD on AlmaLinux
Linux
User Creation and SSH Key Setup in AlmaLinux
Linux
How to reset password on AlmaLinux
Linux

© 2023 EnterinIT

Go to mobile version
adbanner
Welcome Back!

Sign in to your account

Username or Email Address
Password

Lost your password?