Fix SCCM Extend AD Schema Error Code 1355

 While extending the Active Directory schema for SCCM, I encountered the AD Schema Error Code 1355. In this article, I will cover the solutions to resolve “failed to extend the Active Directory Schema Error Code = 1355”.


One of the important steps that you perform before installing SCCM is creating the system management container and extending the AD Schema. You should only move forward with installation after effectively extending the AD schema for Configuration Manager.

http://forum.silverlakesl.com/viewtopic.php?t=13146

http://forum.silverlakesl.com/viewtopic.php?t=10401

http://forum.silverlakesl.com/viewtopic.php?f=2&t=3996

http://www.izolacniskla.cz/forum-detail.php?dt_id=22365

http://tnd-mafia.de/viewtopic.php?f=10&t=19657

http://tnd-mafia.de/viewtopic.php?f=10&t=15780

http://tnd-mafia.de/viewtopic.php?t=7762

http://mappingaset.bnpb.go.id/new/public/asset/335/index.html

http://wiki.wonikrobotics.com/AllegroHandWiki/index.php/Mounting_Information

https://kusbaz.ru/viewtopic.php?t=19995

https://kusbaz.ru/viewtopic.php?t=72706

https://kusbaz.ru/viewtopic.php?t=74176

https://kusbaz.ru/viewtopic.php?t=19831

http://forums.sateamedia.com/showthread.php?tid=6897

When you extend the Active Directory schema for Configuration Manager, you introduce new structures to Active Directory. Configuration Manager sites use these new structures to publish key information in a secure location where clients can easily access it.


In general, when you extend Active Directory Schema for SCCM, it’s successful. However, in some cases, you may encounter errors such as failed to extend the Active Directory Schema Error Code = 1355.


Fix SCCM Extend AD Schema Error Code 1355

The AD schema error 1355 translates to ERROR_NO_SUCH_DOMAIN. This means the specified domain could not be contacted or does not exist. In the below image, we see the error “failed to extend the Active Directory schema” when you use extadsch.exe to extend the AD schema for SCCM. The error details are logged in C:\ExtADSch.log.


Upon reviewing the ExtADSch.log, we see the following errors.

https://mariospad.boardhost.com/viewtopic.php?id=79474

https://mariospad.boardhost.com/viewtopic.php?id=78798

https://www.tnfnorth.com/viewtopic.php?t=3403

http://www.tnfnorth.com/viewtopic.php?t=5324

https://www.tnfnorth.com/viewtopic.php?t=3431

http://159.69.110.221/viewtopic.php?f=4&t=8828

http://159.69.110.221/viewtopic.php?f=4&t=12773

http://vrn.best-city.ru/forum/thread540060266/

http://molbiol.ru/forums/index.php?showtopic=659579&langid=en

http://users.atw.hu/handsupforum/viewtopic.php?p=196014

http://users.atw.hu/handsupforum/viewtopic.php?p=195088

http://users.atw.hu/handsupforum/viewtopic.php?p=194172

https://www.cakeresume.com/me/shikha-sharma-5969bf

http://codepad.org/users/ComputerCargo45

http://ledger-git.dyne.org:3000/ComputerBytes63

http://warhammer.world.free.fr/viewtopic.php?t=311

http://warhammer.world.free.fr/viewtopic.php?t=278

We will now look for possible solutions to resolve the SCCM extend AD schema error code 1355.


Solution 1: Examine the Event Viewer for Domain Availability errors

The Windows Event Viewer shows a log of application and system messages, including errors, information messages, and warnings. In the event of error 1355, if the Configuration Manager server fails to contact the domain controller, the event viewer should log these errors.


Launch the event viewer on the computer on which you are encountering error code 1355 and expand Windows logs and select System. If you see Event ID 5719, it means your domain isn’t available. Either the machine is unable to find the domain controller or there are DNS issues in the setup.


Remember that whenever your server is unable to reach the domain or has authentication problems, you’ll not be able to extend the AD schema for SCCM. This may result in AD schema error code 1355.


To resolve this issue, you can restart the server once and attempt to extend the schema again. If you still see the NETLOGON errors, contact your system administrator and perform the troubleshooting.


Solution 2: Perform NSLookup To Troubleshoot DNS Issues


The second troubleshooting step that you can perform to fix the SCCM AD Schema Error 1355 is to perform NSLookup. This is the best tool for troubleshooting DNS resolution issues. By using Nslookup, you can look up any website’s IP address and get detailed information about all the DNS records associated with a particular domain name.

Comments

Popular posts from this blog

The 10 Best Apartment Websites of 2019

The 10 Best Sites for Free Stock Images

How to get Amazon Prime for free for Prime Day