Shulou(Shulou.com)06/01 Report--

This article will explain in detail what the unattended installation return code of Windows Server2008 active Directory means. The editor thinks it is very practical, so I share it with you for reference. I hope you can get something after reading this article.

The return code for the unattended installation of Windows Server2008 active Directory. When the unattended installation is complete, Dcpromo returns one of the following codes to indicate the installation status to the user. Unused numbers will be reserved for later use.

1-10 = return code indicating success

11-100 = return code indicating failure

Return code indicating success

The code in the following table indicates that the AD DS installation or removal operation completed successfully.

Value

Situation

Description

The 1ExitSuccess operation was successful. The 2ExitSuccessNeedReboot operation was successful, but the server must be manually restarted. The 3ExitSuccessWithNonCriticalFailure operation succeeded with errors, such as DNS installation or authorization configuration failure. Check the Dcpromoui record file and study it in depth. The 4ExitSuccessWithNonCriticalFailureNeedReboot operation succeeded with errors, such as DNS installation or authorization configuration failure. The server needs to be restarted manually. Check the Dcpromoui record file and study it in depth.

A return code indicating a failure

The code in the following table indicates that the AD DS installation or removal operation failed.

Value

Situation

Description

11ExitAlreadyRunningDcpromo is already running. The 12ExitMustBeAdministrator user must be the administrator of the local computer. The 13ExitCertSvcInstalled active Directory Certificate Service is installed. The 14ExitInSafeBootMode server runs in safe mode. A 15ExitRoleChangePending role change is in progress or requires that the server be restarted. The 16ExitIncorrectPlatform server is running on the wrong platform. 17ExitNeedNTFS5Drive has no drives formatted as NTFS5. 18ExitInsufficient WinDirSpace% windir% does not have enough space. The 19ExitNameChangeNeedsReboot computer name change is pending and the computer must be restarted. The 20ExitBadComputerName computer name uses illegal characters. The operating host role of 21ExitHoldsFSMOs local domain controller Sunna is a global catalog server or DNS server. 22ExitNeedToInstallTcpIpTCP/IP must be installed or TCP/IP is not working properly. The 23ExitNeedToConfigDnsFirstDNS client must be configured first. The credentials provided by 24ExitBadCredentials are invalid or the necessary parts are missing. The domain controller for the domain specified by 25ExitDcNotFound cannot be located. 26ExitUnableReadDomainList was unable to read the domain list from the forest. Missing 27ExitMustSpecifyDomain domain name (parent, child, tree or forest) invalid 28ExitBadDomainName domain name 29ExitParentDomainNotExists parent domain does not exist. 30ExitDomainNotInForest could not find the specified domain in the forest. The 31ExitChildDomainExists subdomain already exists. The 32ExitBadNetbiosDomainNameNetBIOS name is invalid. The 33ExitBadIFMPathIFM (Install from Media) file path is not valid. The 34ExitBadIFMDatabaseIFM database is corrupt. 35ExitNoSyskeyForIFM requires the system key of the IFM database. The 37ExitBadDBPath database or database log file path is invalid. The 38ExitInsuffSpaceForDB volume does not have enough space to accommodate the database and the database log file 39ExitBadSysVolPathSYSVOL path is invalid. The 40ExitBadSiteName station roll call is invalid. 41ExitMustSpecifySafeModePwd you must specify a safe mode password. The 42ExitBadSafeModePwd secure mode password does not meet the complexity standard. The 43ExitBadAdminPwd administrator password does not meet the miscellaneous standard. The forest name specified by 44ExitBadForestName is invalid. A forest with the name specified by 45ExitForestExists already exists. The tree name specified by 46ExitBadTreeName is invalid. A tree with the name specified by 47ExitTreeExists already exists. The name of 48ExitTreeNotFitInForest tree does not conform to the forest structure. The 49ExitDomainNotExists specified domain does not exist. 50ExitLastDcMismatch although it is indicated that this is the last domain controller, this is not the last domain controller, or this is the last domain controller, but it is not indicated that this is the last domain controller. 51ExitUnconfirmedAppPartitions has no recognized application partitions that exist on the domain controller. Unattended installation parameters in the 52ExitRequiredParameterMissing answer file or on the command line are not provided. (missing required parameters) 53ExitPromoDemotFailedNeedReboot installation or removal failed and the server must be restarted. Failed to install or remove 54ExitPromoDemotFailed. Installation or removal of 55ExitPromoDemoteFailedBecauseUserCancelled failed due to cancellation by the user. Installation or removal of 56ExitPromoDemotFailedBecauseUserCancelledNeedReboot failed due to cancellation by the user. The computer must be restarted to return to its previous state. 57ExitDomainReadOnlyReplicaGroupNotSpecified operator (operator) specified necessary RODC (allow / deny) group failed 58ExitDomainReadOnlyReplicaSiteNotSpecified operator (operator) failed to specify site name for RODC. The 59ExitLastDnsServer domain controller is the last DNS server in all its AD integration areas. 61ExitInstallDNSNotAllowed you cannot use DNS in the current domain to install AD DS. The 62ExitAnswerFileMissingSectionName answer file does not have a [DCInstall] section. The functional level of 63ExitInsufficientForestFunctionalLevelForRodc forest is lower than Windows Server 2003. The forest functional level must be equal to or higher than Windows Server 2003 to add RODC to the forest. 64ExitPromoFailedBecauseComponentBinaryDetectionFailed installation failed because the binary installation file for AD DS on the server could not be determined. 65ExitPromoFailedBecauseComponentBinaryInstallationFailed installation failed because AD DS binaries could not be installed. 66ExitPromoFailedBecauseOSDetectionFailed installation failed because operating system installation options (either "Server Core" mode installation or full installation) could not be determined. Invalid 68ExitInvalidReplicationPartner replication partner. The 69ExitRequiredPortInUse request port has been used by other programs. The first 70ExitForestRootDcMustBeGc forest root domain controller must be a global catalog server. The 71ExitDnsAlreadyInstalledDNS service is installed. 72ExitIsAppServer installation failed because the server is a Terminal Services application server. (Terminal Services application server) the forest functional level specified by 73ExitInvalidForestFunctionalLevel is invalid. The domain function level specified by 74ExitInvalidDomainFunctionalLevel is invalid. 75ExitDefaultPasswordReplicationPolicyCannotBeDetermined was unable to determine the default password replication policy. The allow and deny security groups specified by 76ExitInvalidPasswordReplicationPolicy for the password replication policy are invalid. The 77ExitInvalidArgument specified parameter is invalid. 78ExitForestCheckFailed installation failed because the AD forest could not be checked. 79ExitRodcNDNCNotPreppedRODC cannot be installed because adprep / rodcprep has not been executed yet. 80ExitDomainNotPrepped installation failed because adprep/domainprep has not been executed yet. 81ExitForestNotPrepped installation failed because adprep/forestprep has not been executed yet. 82ExitForestSchemaMismatch installation failed because of a matching error in the forest schema. 83ExitUnsupportedSku installation failed because the operating system version does not support AD DS. 84ExitDcAccountDetectionFailed was unable to detect the domain controller account. 85ExitDcAccountSelectionFailed was unable to select a domain controller account that can be associated with the server. 86ExitStage2Required you must associate the server to an existing account. The 87ExitDcAccountConflictingType read-only or writable domain controller account already exists in the domain, but does not match the type of domain controller you want to install. The installation cannot continue. The RODC server administrator specified by 88ExitServerAdminInvalid is invalid. 89ExitRidMasterOffline specifies that the RID host for the domain is offline. The 90ExitDNMasterOfflinedomain naming host is offline. 91ExitWow64ProcessDetectionFailed detection failed if the process is Wow64. The 92ExitWow64ProcessNotSupportedWow64 process is not supported. 93ExitDcServiceNotRunningForRegularDemotionAD DS removal failed because the AD DS service is not running. The 94ExitBadLocalAdminPwd local administrator password does not meet the complexity requirements. It is possible that the password is empty or does not meet the Lord's request. 95ExitCannotDemoteLastLHDC cannot demote the last Windows Server 2008 domain controller in the domain when an actionable RODC exists. Installation of 96ExitComponentBinaryUninstallFailedAD DS binaries failed. On the "Windows Server2008 active Directory unattended installation return code means" this article is shared here, I hope the above content can be of some help to you, so that you can learn more knowledge, if you think the article is good, please share it out for more people to see.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.