question

Lulu-4452 avatar image
0 Votes"
Lulu-4452 asked Lulu-4452 published

SCCM client install : FAILED TO CONNECT TO MACHINE POLICY NAMESPACE. 0X8004100E

Hi everyone,

I'm writing to you because I'm loosing my mind and running out of solutions.
My company had SCCM few years ago and decided to have it back.

Architecture:
Running SCCM CB 2101
We have 3 AD forest non-trusted between each other :
Domain MNG
15 clients
Primary Standalone Website installed 2101
Domain A
80 clients
DP/MP/SU installed from the primary site
Domain B
200 clients
DP/MP/SU installed from the primary site

For the installation and debugging, I did the following :
- Re-extended the AD schema
- using domain admin account for each domain to allow the primary site connection
- added each domain in AD forest on SCCM
- Install on DP/MP/SUP servers of Domains A and B the client SCCM to make DP working
- Configure the BD groups with subnets and AD site discovered
- All is configured in HTTP
- Auto approval of unknown computers
- allow anonymous client to contact the DPs
- No Windows Firewall enabled on clients / servers
- Checked the network firewall and look like nothing is blocked.
- review the IIS features and looks ok
- No relevant error on the site status

So far I have been able to install the client only on the sccm site servers manually and get them working.

When I try to install the client by push or manually, it install it, return code 0 at the end but show following error in ccmsetup.log : Failed to connect to machine policy namespace. 0x8004100e
On the clients, the software center is not present (weird?) but in the control panel I have access to the CM settings.

Here few lines of the log before and after the error :
93888-image.png


My questions are :

1) Does my architecture is ok ? Or I should install a CAS on MNG and deploy Primary sites on each domain ?
2) Any ideas regarding this issue ?
3) The clients where i'm testing are W10x64 Enterprise LTSC 2019 (1809)

Thanks in advance !
/Lulu


mem-cm-general
image.png (72 B)
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

SunnyNiu-MSFT avatar image
0 Votes"
SunnyNiu-MSFT answered Lulu-4452 commented

@Lulu-4452

Does my architecture is ok ? Or I should install a CAS on MNG and deploy Primary sites on each domain ?

Based on my experience, there is no problem with the architecture, and no other changes are needed.

When I try to install the client by push or manually, it install it, return code 0 at the end but show following error in ccmsetup.log : Failed to connect to machine policy namespace. 0x8004100e

This "error" is the result of ccmsetup checking to see if the agent was previously installed or not. It's perfectly valid for the namespace to not exist.
Just because there is an error within the log doesn't mean that the install failed. There are several errors which are normal within the install, this is normal and expected.

In addition, Error 0x8004100e= "Unvalid Namespace - Source:WMI"
We may kindly check if our boundary and boundary group and MP are configured correctly. Then reboot the machine and try to install client again.

If the response is helpful, please click "Accept Answer"and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.


· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hey,

Thanks for your answer.

So here what I did so far :

I deleted manually the entries of the System Manager container and uninstall the DP/MP/SUP of the Domain A. I tried to trigger installation but it didn't worked. Just the next day, Surprise, clients started to works.
Also deleted all BG and recreated them and everything looks good.

So I decided to reinstall this DP/MP, and now still experiencing issues.

For example, the client that is install on the DP/MP of the Domain A isn't working anymore (Software Center opening in white then after a while closing).

Which log should I look at ?

Thanks,

/Lulu

0 Votes 0 ·
PraveenPoulose avatar image
0 Votes"
PraveenPoulose answered Lulu-4452 commented

check below steps,

Install KB2552033

• Start Service - Background Intelligent Transfer Service (BITS)
• Start Service - Windows Management Instrumentation
• Disabled the Firewall on local system.
• Silver Light must be installed.


  • then install ccmsetup

  • then run sccm client

@Lulu-4452




· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Install KB2552033 - Not relevant for me, my SCCM servers are under WS 2019 LTSC.

  • BITS OK

  • WMI OK

  • Fw already disabled on client and server side

  • Client finally worked after removing the DPMP of the domain A


0 Votes 0 ·
Lulu-4452 avatar image
0 Votes"
Lulu-4452 answered Lulu-4452 published

LocationsServices.log of the DPMP client

 <![LOG[Status Agent hasn't been initialized yet. Attempting to create pending event.]LOG]!>
         <![LOG[Raising pending event:
         instance of CCM_CcmHttp_Status
         {
          ClientID = "GUID:11";
    
          HostName = "swintccm01.domainA.com";
          HRESULT = "0x00000000";
          ProcessID = 6404;
          StatusCode = 0;
          ThreadID = 8168;
         };
         ]LOG]!><time="16:20:40.795-180" date="05-09-2021" component="LocationServices" context="" type="1" thread="8168" file="Event.cpp:909">
         <![LOG[1 assigned MP errors in the last 10 minutes, threshold is 5.]LOG]!>
         <![LOG[2 assigned MP errors in the last 10 minutes, threshold is 5.]LOG]!>
         <![LOG[3 assigned MP errors in the last 10 minutes, threshold is 5.]LOG]!><time="16:20:51.717-180" date="05-09-2021" component="LocationServices" context="" type="2" thread="7444" file="lsutils.cpp:3243">


5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.