Forums on Intune, SCCM, and Windows 11
Welcome to the forums. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your topics and posts, as well as connect with other members through your own private inbox!
PENDING CcmSetup failed with error code 0x80004005
- Thread starter mahinsa
- Start date
- Replies 7
- Views 477
- Messages
- 5,068
- Solutions
- 147
- Reaction score
- 984
- Points
- 413
There are multiple solutions listed for this error 0x80004005 while installing configmgr client - https://forums.prajwaldesai.com/threads/ccmsetup-failed-error-code-0x80004005.213/
Use the search feature in the forum to get more details about 0x80004005
Use the search feature in the forum to get more details about 0x80004005
- Thread Starter
- #3
I have checked firewall. it is switched off. and also there is already created Boundary created with clients IP' range in SCCM console. I can not install MP agin because this is production environment. please help me to resolve.
- Messages
- 5,068
- Solutions
- 147
- Reaction score
- 984
- Points
- 413
Is this issue on all the clients or a single machine?
Harshit Pandey
Well-Known Member
- Messages
- 307
- Solutions
- 8
- Reaction score
- 9
- Points
- 18
I think the issue is with boundary and boundary groups. Are you using IP ranges to create boundary?
yuishchenko
New Member
- Messages
- 1
- Reaction score
- 0
- Points
- 1
Hi
I encountered the same error when installing the client on a non-domain laptop. The installation log returned error code 0 (everything was essentially fine).
Reinstalling didn't help. Out of desperation, I decided to delete the CCM system folders (CCM, ccmsetup, ccmcache) from the Windows folder and restart the installation. This helped. The laptop appeared in the console, I authorized it, and it became active and manageable. This isn't practical or IT-friendly, but maybe it will help someone else.
I encountered the same error when installing the client on a non-domain laptop. The installation log returned error code 0 (everything was essentially fine).
Reinstalling didn't help. Out of desperation, I decided to delete the CCM system folders (CCM, ccmsetup, ccmcache) from the Windows folder and restart the installation. This helped. The laptop appeared in the console, I authorized it, and it became active and manageable. This isn't practical or IT-friendly, but maybe it will help someone else.
