| File name: | adamuninstall.exe.mui |
| Size: | 54784 byte |
| MD5: | 28476ad9d040182937ded57b8b2fbba9 |
| SHA1: | 9b8012c7d79985b07df24eb372e3957490d6362c |
| SHA256: | 92c05e5ce853992677c92a550d359aa713a4f868567882ebc7a7773cb73d07cb |
| Operating systems: | Windows 10 |
| Extension: | MUI |
| In x64: | adamuninstall.exe Active Directory Lightweight Directory Services Uninstaller (32-bit) |
If an error occurred or the following message in English (U.S.) language and you cannot find a solution, than check answer in English. Table below helps to know how correctly this phrase sounds in English.
| id | English (U.S.) | English |
|---|---|---|
| 100 | Active Directory Lightweight Directory Services Removal Wizard | Active Directory Lightweight Directory Services Removal Wizard |
| 101 | If you continue, AD LDS instance %1 will be permanently removed from this computer. Do you want to continue? | If you continue, AD LDS instance %1 will be permanently removed from this computer. Do you want to continue? |
| 102 | The wizard did not start. | The wizard did not start. |
| 115 | If you continue, the AD LDS administration tools will be permanently removed from this computer. Do you want to continue? | If you continue, the AD LDS administration tools will be permanently removed from this computer. Do you want to continue? |
| 116 | AD LDS was successfully removed, but there were some problems during removal. Please review the warnings listed below. | AD LDS was successfully removed, but there were some problems during removal. Please review the warnings listed below. |
| 117 | AD LDS was successfully removed. | AD LDS was successfully removed. |
| 118 | Some temporary files will not be deleted until you restart Windows. | Some temporary files will not be deleted until you restart Windows. |
| 119 | The following operations succeeded: %1 |
The following operations succeeded: %1 |
| 120 | %1 |
%1 |
| 121 | AD LDS was removed successfully.
%1 Warnings: %2 |
AD LDS was removed successfully.
%1 Warnings: %2 |
| 122 | AD LDS could not be successfully removed. | AD LDS could not be successfully removed. |
| 123 | Disabling Active Directory Web Services if necessary ... | Disabling Active Directory Web Services if necessary ... |
| 124 | Failed to disable Active Directory Web Services. The error was: %1 | Failed to disable Active Directory Web Services. The error was: %1 |
| 2000 | AD LDS ADSI Edit | AD LDS ADSI Edit |
| 2001 | A low level Active Directory Services Interface editor for AD LDS. | A low level Active Directory Services Interface editor for AD LDS. |
| 2002 | AD LDS Help | AD LDS Help |
| 2006 | AD LDS Tools Command Prompt | AD LDS Tools Command Prompt |
| 2007 | Open AD LDS Command Prompt | Open AD LDS Command Prompt |
| 5100 | Deleting key %1\%2... | Deleting key %1\%2... |
| 5101 | Deleting file %1... | Deleting file %1... |
| 5102 | Removing folder %1... | Removing folder %1... |
| 5103 | Cancelling AD LDS instance %1... | Cancelling AD LDS instance %1... |
| 5105 | A required removal file did not contain any operations. | A required removal file did not contain any operations. |
| 5106 | Registry key '%1' could not be deleted.
%2 |
Registry key '%1' could not be deleted.
%2 |
| 5107 | File '%1' could not be deleted.
%2 |
File '%1' could not be deleted.
%2 |
| 5108 | Folder '%1' could not be deleted.
%2 |
Folder '%1' could not be deleted.
%2 |
| 5109 | The directory service could not be removed.
%1 |
The directory service could not be removed.
%1 |
| 5111 | Unregistering %1... | Unregistering %1... |
| 5112 | Component '%1' could not be unregistered.
%2 |
Component '%1' could not be unregistered.
%2 |
| 5113 | Gathering required information... | Gathering required information... |
| 5114 | Preparing to remove AD LDS... | Preparing to remove AD LDS... |
| 5115 | Removing AD LDS... | Removing AD LDS... |
| 5200 | The registry key '%1' could not be saved: %2 | The registry key '%1' could not be saved: %2 |
| 5201 | The registry key '%1'could not be restored: %2 | The registry key '%1'could not be restored: %2 |
| 5202 | The file '%1' could not be deleted: %2 | The file '%1' could not be deleted: %2 |
| 5203 | The file '%1' could not be moved: %2 | The file '%1' could not be moved: %2 |
| 5204 | The file '%1' could not be restored: %2 | The file '%1' could not be restored: %2 |
| 5206 | The folder '%1' could not be moved: %2 | The folder '%1' could not be moved: %2 |
| 5207 | The folder '%1' could not be restored: %2 | The folder '%1' could not be restored: %2 |
| 5208 | The folder '%1' could not be deleted: %2 | The folder '%1' could not be deleted: %2 |
| 5209 | The component '%1' could not be removed from the registry: %2 | The component '%1' could not be removed from the registry: %2 |
| 5210 | The component '%1' could not be registered: %2 | The component '%1' could not be registered: %2 |
| 5211 | The component '%1' could not be removed from the archive: %2 | The component '%1' could not be removed from the archive: %2 |
| 5212 | No backup for the current AD LDS installation was found. | No backup for the current AD LDS installation was found. |
| 5213 | The registry key '%1' could not be deleted: %2 | The registry key '%1' could not be deleted: %2 |
| 5214 | The registry value '%1:%2' could not be read: %3 | The registry value '%1:%2' could not be read: %3 |
| 5215 | The registry key '%1' could not be opened: %2 | The registry key '%1' could not be opened: %2 |
| 5300 | Inbound rule for Active Directory Lightweight Directory Services to allow remote LDAP traffic. [TCP] | Inbound rule for Active Directory Lightweight Directory Services to allow remote LDAP traffic. [TCP] |
| 5301 | Inbound rule for Active Directory Lightweight Directory Services to allow remote Secure LDAP traffic. [TCP] | Inbound rule for Active Directory Lightweight Directory Services to allow remote Secure LDAP traffic. [TCP] |
| 5302 | Inbound rule for Active Directory Lightweight Directory Services to allow remote management via RPC/TCP. | Inbound rule for Active Directory Lightweight Directory Services to allow remote management via RPC/TCP. |
| 5303 | Inbound rule for the RPCSS service to allow RPC/TCP traffic for Active Directory Lightweight Directory Services. | Inbound rule for the RPCSS service to allow RPC/TCP traffic for Active Directory Lightweight Directory Services. |
| 5304 | Outbound rule for Active Directory Lightweight Directory Services. [TCP] | Outbound rule for Active Directory Lightweight Directory Services. [TCP] |
| 5305 | Active Directory Lightweight Directory Services - %1 | Active Directory Lightweight Directory Services - %1 |
| 7001 | AD LDS Setup was unable to delete password information from the unattended installation file, %1, because of a system error. The file might still contain passwords. To minimize security vulnerability, ensure that the file was deleted after AD LDS Setup completed. The system error encountered by AD LDS Setup was: | AD LDS Setup was unable to delete password information from the unattended installation file, %1, because of a system error. The file might still contain passwords. To minimize security vulnerability, ensure that the file was deleted after AD LDS Setup completed. The system error encountered by AD LDS Setup was: |
| 7002 | You must qualify the user name with a domain or computer name.
Example: COMPUTER1\UserName Example: DOMAIN\UserName Example: [email protected] |
You must qualify the user name with a domain or computer name.
Example: COMPUTER1\UserName Example: DOMAIN\UserName Example: [email protected] |
| 8000 | Operation Skipped: %1 To Complete: %2 |
Operation Skipped: %1 To Complete: %2 |
| 8001 | The following directory partitions are associated only with this instance of AD LDS. If you remove this instance, these directory partitions will be permanently deleted. Are you sure you want to remove this instance of AD LDS? | The following directory partitions are associated only with this instance of AD LDS. If you remove this instance, these directory partitions will be permanently deleted. Are you sure you want to remove this instance of AD LDS? |
| 8002 | The AD LDS instance %1 is the last instance in this configuration set. If you remove the instance, you will also remove the configuration set. Are you sure you want to remove this instance? | The AD LDS instance %1 is the last instance in this configuration set. If you remove the instance, you will also remove the configuration set. Are you sure you want to remove this instance? |
| 8003 | Operation Skipped: %1 |
Operation Skipped: %1 |
| 9020 | Verdana | Verdana |
| 9021 | 12 | 12 |
| 9022 | 700 | 700 |
| 20001 | AD LDS Setup was cancelled. | AD LDS Setup was cancelled. |
| 20002 | You do not have the correct permissions to run AD LDS Setup. For more information, contact your system administrator. | You do not have the correct permissions to run AD LDS Setup. For more information, contact your system administrator. |
| 20003 | The value entered for ShowOrHideProgressGUI is not 'Show' or 'Hide'. The current value is set to 'Hide'. To change this value, update the unattended installation file, and run Setup again. | The value entered for ShowOrHideProgressGUI is not 'Show' or 'Hide'. The current value is set to 'Hide'. To change this value, update the unattended installation file, and run Setup again. |
| 20004 | The value entered for InstallType is not 'Unique', or 'Replica'. The current value is set to 'Unique'. To change this value, update the unattended installation file, and run Setup again. | The value entered for InstallType is not 'Unique', or 'Replica'. The current value is set to 'Unique'. To change this value, update the unattended installation file, and run Setup again. |
| 20005 | The instance name is not valid. An instance name can contain characters only in the ranges a-z, A-Z, and 0-9 or the following special character: hyphen (-). | The instance name is not valid. An instance name can contain characters only in the ranges a-z, A-Z, and 0-9 or the following special character: hyphen (-). |
| 20006 | The instance name is too long. Type a name that is fewer than %1!d! characters. | The instance name is too long. Type a name that is fewer than %1!d! characters. |
| 20007 | The name '%1' is already in use as an AD LDS instance name. Type a different instance name. | The name '%1' is already in use as an AD LDS instance name. Type a different instance name. |
| 20008 | The value entered for LocalLDAPPortToListenOn is not a number. In the unattended setup file, type either 389 or a number between 1025 and 65535 in this field, and then run Setup again. | The value entered for LocalLDAPPortToListenOn is not a number. In the unattended setup file, type either 389 or a number between 1025 and 65535 in this field, and then run Setup again. |
| 20009 | The value entered for LocalLDAPPort is not 389 or between 1025 and 65535. In the unattended setup file, type a valid port number in this field, and then run Setup again. | The value entered for LocalLDAPPort is not 389 or between 1025 and 65535. In the unattended setup file, type a valid port number in this field, and then run Setup again. |
| 20010 | The value entered for LocalLDAPPort is in use. In the unattended setup file, type a unique port number in this field, and then run Setup again. | The value entered for LocalLDAPPort is in use. In the unattended setup file, type a unique port number in this field, and then run Setup again. |
| 20011 | The value entered for LocalSSLPortToListenOn is not a number. In the unattended setup file, type a number in this field, and then run Setup again. | The value entered for LocalSSLPortToListenOn is not a number. In the unattended setup file, type a number in this field, and then run Setup again. |
| 20012 | The value entered for LocalSSLPort is not 636 or between 1025 and 65535. In the unattended setup file, type a valid port number in this field, and then run Setup again. | The value entered for LocalSSLPort is not 636 or between 1025 and 65535. In the unattended setup file, type a valid port number in this field, and then run Setup again. |
| 20013 | The value entered for LocalSSLPort is in use. In the unattended setup file, type a unique value in this field, and then run Setup again. | The value entered for LocalSSLPort is in use. In the unattended setup file, type a unique value in this field, and then run Setup again. |
| 20014 | The value entered for SourceServer is not a computer name. In the unattended setup file, type a valid computer name in this field, and then run Setup again. | The value entered for SourceServer is not a computer name. In the unattended setup file, type a valid computer name in this field, and then run Setup again. |
| 20015 | AD LDS is not running on the specified LDAP port of the source server. Enter the source server and port of a valid configuration set in these fields, and then run Setup again. | AD LDS is not running on the specified LDAP port of the source server. Enter the source server and port of a valid configuration set in these fields, and then run Setup again. |
| 20016 | The value entered for SourceLDAPPort is not a number. In the unattended setup file, type a number in this field, and then run Setup again. | The value entered for SourceLDAPPort is not a number. In the unattended setup file, type a number in this field, and then run Setup again. |
| 20017 | No value was entered in the SourceUsername field.
If you are an administrator of the selected configuration set, you can remove the SourceUsername field from the unattended setup file or type a valid account in the Sourceusername field. If you are not an administrator of the selected configuration set, you must type a valid user account in the SourceUsername field. After you have updated the unattended setup file, run Setup again. |
No value was entered in the SourceUsername field.
If you are an administrator of the selected configuration set, you can remove the SourceUsername field from the unattended setup file or type a valid account in the Sourceusername field. If you are not an administrator of the selected configuration set, you must type a valid user account in the SourceUsername field. After you have updated the unattended setup file, run Setup again. |
| 20018 | The replication credentials are not valid or are insufficient. Type the credentials of an account that has replication permissions for the specified server. | The replication credentials are not valid or are insufficient. Type the credentials of an account that has replication permissions for the specified server. |
| 20019 | The value for NewApplicationPartitionToCreate is not a distinguished name. Type a distinguished name in this field, and then run Setup again. A distinguished name consists of an ordered set of "attribute type=attribute value" pairs separated by commas. Each attribute value is limited to 256 characters. Example distinguished name: DC=Woodgrove,DC=COM | The value for NewApplicationPartitionToCreate is not a distinguished name. Type a distinguished name in this field, and then run Setup again. A distinguished name consists of an ordered set of "attribute type=attribute value" pairs separated by commas. Each attribute value is limited to 256 characters. Example distinguished name: DC=Woodgrove,DC=COM |
| 20020 | The value entered for Administrator is not a valid user account. In the unattended setup file, type a valid user account in the Administrator field, and then run Setup again. | The value entered for Administrator is not a valid user account. In the unattended setup file, type a valid user account in the Administrator field, and then run Setup again. |
| 20021 | The value entered for ApplicationPartitionsToReplicate does not have correct syntax. In the unattended setup file, type one or more valid application directory partition names, and then run Setup again. Each partition name should be enclosed in quotation marks. To replicate all application directory partitions that exist on the replica source, type “*”. | The value entered for ApplicationPartitionsToReplicate does not have correct syntax. In the unattended setup file, type one or more valid application directory partition names, and then run Setup again. Each partition name should be enclosed in quotation marks. To replicate all application directory partitions that exist on the replica source, type “*”. |
| 20022 | An internal error has occurred and AD LDS Setup must close. | An internal error has occurred and AD LDS Setup must close. |
| 20023 | The folder selected to store the AD LDS files, %1, is the same as the Windows installation folder.
Select a different folder. |
The folder selected to store the AD LDS files, %1, is the same as the Windows installation folder.
Select a different folder. |
| 20024 | The folder selected to store the AD LDS files, %1, is the same as the Windows system folder.
Select a different folder. |
The folder selected to store the AD LDS files, %1, is the same as the Windows system folder.
Select a different folder. |
| 20025 | The path to the folder %1 is not in a valid format. Specify a valid folder path, including the drive letter. Example path: C:\NTDS. | The path to the folder %1 is not in a valid format. Specify a valid folder path, including the drive letter. Example path: C:\NTDS. |
| 20026 | The folder name %1 includes the following characters that are not allowed for the data and data recovery folders:
%2 Choose another folder name. |
The folder name %1 includes the following characters that are not allowed for the data and data recovery folders:
%2 Choose another folder name. |
| 20027 | The folder %1 does not refer to a valid hard disk. Select a folder on a hard disk drive. | The folder %1 does not refer to a valid hard disk. Select a folder on a hard disk drive. |
| 20028 | The folder %1 refers to a drive that is not formatted for the NTFS file system. Because this folder can be replicated among AD LDS servers on multiple computers, NTFS is required. Select a folder on a drive formatted for NTFS. To convert drives formatted with the FAT file system to the NTFS file system, use the Convert.exe command-line tool. For more information about the Convert.exe tool, see Help and Support. |
The folder %1 refers to a drive that is not formatted for the NTFS file system. Because this folder can be replicated among AD LDS servers on multiple computers, NTFS is required. Select a folder on a drive formatted for NTFS. To convert drives formatted with the FAT file system to the NTFS file system, use the Convert.exe command-line tool. For more information about the Convert.exe tool, see Help and Support. |
| 20029 | The path %1 contains a mounted volume on the path %2. Please type a path that does not contain any mounted volumes. | The path %1 contains a mounted volume on the path %2. Please type a path that does not contain any mounted volumes. |
| 20030 | The path %1 does not refer to a folder. Select a folder. | The path %1 does not refer to a folder. Select a folder. |
| 20031 | The folder %1 is compressed. AD LDS cannot be installed in a compressed folder. Select a folder that is not compressed. | The folder %1 is compressed. AD LDS cannot be installed in a compressed folder. Select a folder that is not compressed. |
| 20032 | The folder %1 is encrypted. AD LDS cannot be installed in an encrypted folder. Select a folder that is not encrypted. | The folder %1 is encrypted. AD LDS cannot be installed in an encrypted folder. Select a folder that is not encrypted. |
| 20033 | The folder %1 is not empty. Select an empty folder to store AD LDS installation files. | The folder %1 is not empty. Select an empty folder to store AD LDS installation files. |
| 20034 | There is insufficient free disk space on volume %1. At least %2!u! MB of free disk space is required to proceed. | There is insufficient free disk space on volume %1. At least %2!u! MB of free disk space is required to proceed. |
| 20035 | You do not have the correct permissions to access the folder %1. For more information, contact your system administrator. | You do not have the correct permissions to access the folder %1. For more information, contact your system administrator. |
| 20036 | Type a valid user name and password for the selected service account. | Type a valid user name and password for the selected service account. |
| 20037 | The selected account does not have permission to run as a service. Before continuing, select an account with the appropriate permissions, or update the selected account. To update this account to run as a service, modify its settings in the Local Security Settings console. | The selected account does not have permission to run as a service. Before continuing, select an account with the appropriate permissions, or update the selected account. To update this account to run as a service, modify its settings in the Local Security Settings console. |
| 20038 | %1 | %1 |
| 20039 | There is not enough memory to complete the operation. Save your work, close other programs, and then try again. | There is not enough memory to complete the operation. Save your work, close other programs, and then try again. |
| 20040 | An Active Directory installation is already in progress. | An Active Directory installation is already in progress. |
| 20041 | The removal log could not be created because of the following error:
%1 |
The removal log could not be created because of the following error:
%1 |
| 20042 | Value for ShowInAddRemovePrograms must be 'Show' or 'Hide' | Value for ShowInAddRemovePrograms must be 'Show' or 'Hide' |
| 20043 | The install failed because a unique registry key name could not be generated for the 'Add/Remove Programs' component. | The install failed because a unique registry key name could not be generated for the 'Add/Remove Programs' component. |
| 20045 | Before using backup files to add a new instance of AD LDS to a configuration set, ensure that the following values have been set in the unattended setup file: ReplicationDataSourcePath and ReplicationLogSourcePath. | Before using backup files to add a new instance of AD LDS to a configuration set, ensure that the following values have been set in the unattended setup file: ReplicationDataSourcePath and ReplicationLogSourcePath. |
| 20046 | No value was entered for ReplicationDataSourcePath. In the unattended setup file, specify a folder that contains the restored AD LDS data in this field, and then run Setup again. | No value was entered for ReplicationDataSourcePath. In the unattended setup file, specify a folder that contains the restored AD LDS data in this field, and then run Setup again. |
| 20047 | The folder that contains the restored AD LDS data does not exist. Specify a valid path, including the drive letter. Example folder path: C:\restored\data. | The folder that contains the restored AD LDS data does not exist. Specify a valid path, including the drive letter. Example folder path: C:\restored\data. |
| 20048 | The folder that contains the restored AD LDS data is not stored on a local drive. Specify a folder on a local drive. | The folder that contains the restored AD LDS data is not stored on a local drive. Specify a folder on a local drive. |
| 20049 | The folder that contains the restored AD LDS data is missing the file Adamntds.dit. Specify the correct path to the restored .dit file. | The folder that contains the restored AD LDS data is missing the file Adamntds.dit. Specify the correct path to the restored .dit file. |
| 20050 | No value was entered for ReplicationLogSourcePath. In the unattended setup file, specify a folder that contains the restored AD LDS data recovery files in this field, and then run Setup again. | No value was entered for ReplicationLogSourcePath. In the unattended setup file, specify a folder that contains the restored AD LDS data recovery files in this field, and then run Setup again. |
| 20051 | The folder that contains the restored AD LDS data recovery folder does not exist. Specify a valid path, including the drive letter. Example folder path: C:\restored\log. | The folder that contains the restored AD LDS data recovery folder does not exist. Specify a valid path, including the drive letter. Example folder path: C:\restored\log. |
| 20052 | The folder that contains restored AD LDS data recovery files is not stored on a local drive. Specify a folder on a local drive. | The folder that contains restored AD LDS data recovery files is not stored on a local drive. Specify a folder on a local drive. |
| 20053 | The folder that contains the restored AD LDS data recovery files is missing the file Edb.log. Specify the correct path to the restored .log file or leave the path empty. | The folder that contains the restored AD LDS data recovery files is missing the file Edb.log. Specify the correct path to the restored .log file or leave the path empty. |
| 20054 | This version of AD LDS cannot run on 64-bit computers. To run AD LDS on an 64-bit computer, install the 64-bit version of AD LDS. | This version of AD LDS cannot run on 64-bit computers. To run AD LDS on an 64-bit computer, install the 64-bit version of AD LDS. |
| 20055 | Application partitions created during setup must have one of the following object classes for the root component: C, CN, DC, L, O, OU. Please enter a DN that fits this criteria. | Application partitions created during setup must have one of the following object classes for the root component: C, CN, DC, L, O, OU. Please enter a DN that fits this criteria. |
| 20056 | The user name of the replication account must be qualified by a domain or computer name.
Example: COMPUTER1\UserName Example: DOMAIN\UserName Example: [email protected] |
The user name of the replication account must be qualified by a domain or computer name.
Example: COMPUTER1\UserName Example: DOMAIN\UserName Example: [email protected] |
| 20057 | The user cancelled the uninstall. | The user cancelled the uninstall. |
| 20058 | Uninstalls AD LDS instance.
adamuninstall [/q] [/answer:filename] [/force] /i:instanceName /q Run quietly. /answer Use the unattended script file. /force Ignore warnings during uninstall. /i Remove the AD LDS instance with this name. |
Uninstalls AD LDS instance.
adamuninstall [/q] [/answer:filename] [/force] /i:instanceName /q Run quietly. /answer Use the unattended script file. /force Ignore warnings during uninstall. /i Remove the AD LDS instance with this name. |
| 20059 | The AD LDS instance you are trying to remove, %1, is not installed on this computer. | The AD LDS instance you are trying to remove, %1, is not installed on this computer. |
| 20060 | A valid undo log could not be found for AD LDS instance '%1'. Uninstall cannot complete. | A valid undo log could not be found for AD LDS instance '%1'. Uninstall cannot complete. |
| 20061 | The undo log %1 could not be opened. Uninstall cannot complete. | The undo log %1 could not be opened. Uninstall cannot complete. |
| 20066 | You do not have the correct permissions to run the AD LDS Removal Wizard. For more information, contact your system administrator. | You do not have the correct permissions to run the AD LDS Removal Wizard. For more information, contact your system administrator. |
| 20067 | The removal wizard was not able to remove all of the components. To complete removal, run "Adamuninstall.exe /i:" after resolving the following error:
%1 |
The removal wizard was not able to remove all of the components. To complete removal, run "Adamuninstall.exe /i:" after resolving the following error:
%1 |
| 20068 | An internal program error has occurred. The program must quit. | An internal program error has occurred. The program must quit. |
| 20069 | The file %1 is not in the installation folder %2. AD LDS cannot be installed without this file. Locate the file, and then copy it to the folder that contains Adaminstall.exe. | The file %1 is not in the installation folder %2. AD LDS cannot be installed without this file. Locate the file, and then copy it to the folder that contains Adaminstall.exe. |
| 20071 | AD LDS Setup cannot continue because the unattended installation file, %1, was not found. Verify that the file exists, and then try running Setup again. | AD LDS Setup cannot continue because the unattended installation file, %1, was not found. Verify that the file exists, and then try running Setup again. |
| 20072 | The path '%1' is too long. Specify a path shorter than %2!d! characters. | The path '%1' is too long. Specify a path shorter than %2!d! characters. |
| 20073 | AD LDS could not be installed on this computer because the system folder path is too long. | AD LDS could not be installed on this computer because the system folder path is too long. |
| 20074 | Installs an Active Directory Lightweight Directory Services (AD LDS) instance on this server.
Command line parameters include: /answer:filename [/quiet] /adv /strict /?[:answer] /answer is used to supply an unattend install script file. /quiet is used to specify a quiet mode for an unattended installation. /adv enables advanced user options. /strict makes the setup utility treat warnings as errors. /? displays this help. /?:answer displays help on the various options that can be specified to set up an AD LDS instance. |
Installs an Active Directory Lightweight Directory Services (AD LDS) instance on this server.
Command line parameters include: /answer:filename [/quiet] /adv /strict /?[:answer] /answer is used to supply an unattend install script file. /quiet is used to specify a quiet mode for an unattended installation. /adv enables advanced user options. /strict makes the setup utility treat warnings as errors. /? displays this help. /?:answer displays help on the various options that can be specified to set up an AD LDS instance. |
| 20075 | You have successfully removed the AD LDS instance %1 from this computer. However, some temporary files will not be deleted until you restart Windows. | You have successfully removed the AD LDS instance %1 from this computer. However, some temporary files will not be deleted until you restart Windows. |
| 20077 | The security policy of the selected computer prevents AD LDS from using a service account with a blank password. Select a different account to use as the AD LDS service account. | The security policy of the selected computer prevents AD LDS from using a service account with a blank password. Select a different account to use as the AD LDS service account. |
| 20078 | AD LDS cannot run as the selected account because the account does not have administrative permissions. Administrative permissions are required by this version of Windows to exclusively use a port. Select a different account as the AD LDS service account. | AD LDS cannot run as the selected account because the account does not have administrative permissions. Administrative permissions are required by this version of Windows to exclusively use a port. Select a different account as the AD LDS service account. |
| 20079 | The selected account does not have permission to run as a service. Before continuing, select an account with the appropriate permissions, or update the selected account. To update this account to run as a service, modify its settings in the Domain Controller Security Settings console. | The selected account does not have permission to run as a service. Before continuing, select an account with the appropriate permissions, or update the selected account. To update this account to run as a service, modify its settings in the Domain Controller Security Settings console. |
| 20080 | AD LDS Setup cannot add the Log on as service permission to the selected account. Select a different account to use as the AD LDS service account. | AD LDS Setup cannot add the Log on as service permission to the selected account. Select a different account to use as the AD LDS service account. |
| 20081 | The service account for this instance of AD LDS cannot be used with the selected configuration set. The account failed validation with the following error:
Error 0x%1!x! %2 Select a different service account, and then try again. For more information about AD LDS service accounts, see "Selecting a service account" in AD LDS Help. |
The service account for this instance of AD LDS cannot be used with the selected configuration set. The account failed validation with the following error:
Error 0x%1!x! %2 Select a different service account, and then try again. For more information about AD LDS service accounts, see "Selecting a service account" in AD LDS Help. |
| 20082 | The file %1 is not an allowed LDIF file. | The file %1 is not an allowed LDIF file. |
| 20083 | AD LDS Setup did not complete because one or more LDIF files could not be imported successfully. | AD LDS Setup did not complete because one or more LDIF files could not be imported successfully. |
| 20084 | No value was entered in the SourceUsername field.
If you are an administrator of this AD LDS instance, you can remove the SourceUsername field from the unattended setup file. If you are not an administrator of this AD LDS instance, type the credentials for an account with administrative permissions for AD LDS in the SourceUsername and SourcePassword fields. After you have updated the unattended setup file, run Setup again. |
No value was entered in the SourceUsername field.
If you are an administrator of this AD LDS instance, you can remove the SourceUsername field from the unattended setup file. If you are not an administrator of this AD LDS instance, type the credentials for an account with administrative permissions for AD LDS in the SourceUsername and SourcePassword fields. After you have updated the unattended setup file, run Setup again. |
| 20085 | You must be an administrator of this AD LDS instance to import LDIF files. In the unattended setup file, in the SourceUsername and SourcePassword fields, type the credentials of an account with administrative permissions for AD LDS.
After you have updated the unattended setup file, run Setup again. |
You must be an administrator of this AD LDS instance to import LDIF files. In the unattended setup file, in the SourceUsername and SourcePassword fields, type the credentials of an account with administrative permissions for AD LDS.
After you have updated the unattended setup file, run Setup again. |
| 20086 | The user name entered in the SourceUsername field must be qualified with a domain or computer name. In the unattended setup file, qualify the user name with a domain or computer name.
Example: COMPUTER1\UserName Example: DOMAIN\UserName Example: [email protected] After you have updated the unattended setup file, run Setup again. |
The user name entered in the SourceUsername field must be qualified with a domain or computer name. In the unattended setup file, qualify the user name with a domain or computer name.
Example: COMPUTER1\UserName Example: DOMAIN\UserName Example: [email protected] After you have updated the unattended setup file, run Setup again. |
| 20087 | AD LDS Setup could not complete because the account supplied for LDIF file importation could not be used. Either the credentials were not valid, or the account did not have administrative permissions for AD LDS. | AD LDS Setup could not complete because the account supplied for LDIF file importation could not be used. Either the credentials were not valid, or the account did not have administrative permissions for AD LDS. |
| 20088 | The path '%1' is not valid. To install AD LDS on this version of Windows, the path must be on the same volume as the data folder. Please type a path that is on the volume '%2'. | The path '%1' is not valid. To install AD LDS on this version of Windows, the path must be on the same volume as the data folder. Please type a path that is on the volume '%2'. |
| 20089 | %1
Error code: 0x%2!x! %3 |
%1
Error code: 0x%2!x! %3 |
| 20090 | Setup could not start the service '%1' because of the following error:
Error code: 0x%2!x! %3 |
Setup could not start the service '%1' because of the following error:
Error code: 0x%2!x! %3 |
| 20091 | The AD LDS Setup Wizard is older than AD LDS files that are already installed on this computer. Only a more recent version of AD LDS Setup will run on this computer. | The AD LDS Setup Wizard is older than AD LDS files that are already installed on this computer. Only a more recent version of AD LDS Setup will run on this computer. |
| 20099 | "NTDS" is not a valid instance name. Type a different name. | "NTDS" is not a valid instance name. Type a different name. |
| 20100 | The LDIF files selected for importing are not specified correctly. In the unattended setup file, specify the LDIF files using the ImportLDIFFiles field. Each file name must be in quotes and the file names must be separated by a space. | The LDIF files selected for importing are not specified correctly. In the unattended setup file, specify the LDIF files using the ImportLDIFFiles field. Each file name must be in quotes and the file names must be separated by a space. |
| 20101 | The AD LDS Setup Wizard found a pre-release version of AD LDS installed on this computer. Please remove all installed AD LDS instances and run AD LDS Setup again. | The AD LDS Setup Wizard found a pre-release version of AD LDS installed on this computer. Please remove all installed AD LDS instances and run AD LDS Setup again. |
| 20102 | The removal wizard cannot continue because the unattended removal file, %1, was not found. Verify that the file exists, and then try removing AD LDS again. | The removal wizard cannot continue because the unattended removal file, %1, was not found. Verify that the file exists, and then try removing AD LDS again. |
| 20103 | The user name entered in the Administrator field must be qualified with a domain or computer name. In the unattended removal file, qualify the user name with a domain or computer name.
Example: COMPUTER1\UserName Example: DOMAIN\UserName Example: [email protected] After you have updated the unattended removal file, try removing AD LDS again. |
The user name entered in the Administrator field must be qualified with a domain or computer name. In the unattended removal file, qualify the user name with a domain or computer name.
Example: COMPUTER1\UserName Example: DOMAIN\UserName Example: [email protected] After you have updated the unattended removal file, try removing AD LDS again. |
| 20104 | AD LDS Setup was unable to validate the selected service account.
Error code: 0x%1!x! %2 |
AD LDS Setup was unable to validate the selected service account.
Error code: 0x%1!x! %2 |
| 20105 | AD LDS Setup cannot continue because TCP/IP is not functioning. | AD LDS Setup cannot continue because TCP/IP is not functioning. |
| 20106 | AD LDS Setup requires an answer file. | AD LDS Setup requires an answer file. |
| 20107 | The following is a list of unattend parameters that can be specified to install a new AD LDS instance (default values are enclosed in ):
|
The following is a list of unattend parameters that can be specified to install a new AD LDS instance (default values are enclosed in ):
|
| 20108 | /InstallType:{ | replica}
Optional. Specifies whether a new unique AD LDS instance is created or whether a new instance is created by replicating all or part of an existing AD LDS instance, either over the network or from a restored backup medium. |
/InstallType:{ | replica}
Optional. Specifies whether a new unique AD LDS instance is created or whether a new instance is created by replicating all or part of an existing AD LDS instance, either over the network or from a restored backup medium. |
| 20109 | /ShowOrHideProgressGUI:{Show | }
Optional. Specifies whether the AD LDS setup should display progress information during installation. |
/ShowOrHideProgressGUI:{Show | }
Optional. Specifies whether the AD LDS setup should display progress information during installation. |
| 20110 | /InstanceName:"name_of_the_instance"
Optional. Specifies the name of the instance that you are creating. By default, the AD LDS instance is named “Instancen” where n is the lowest number greater than 0 such that Instancen is unique on the local computer. |
/InstanceName:"name_of_the_instance"
Optional. Specifies the name of the instance that you are creating. By default, the AD LDS instance is named “Instancen” where n is the lowest number greater than 0 such that Instancen is unique on the local computer. |
| 20111 | /InstanceDescription:"description_of_the_instance"
Optional. Specifies a description for the instance. By default, the description will be "AD LDS instance". |
/InstanceDescription:"description_of_the_instance"
Optional. Specifies a description for the instance. By default, the description will be "AD LDS instance". |
| 20112 | /ApplicationPartitionsToReplicate:{"DNs_of_partitions_to_replicate" | *}
Optional. Specifies the distinguished names of the application partitions to replicate from the source AD LDS instance. To replicate all application partitions from the source AD LDS instance, specify a wildcard character. AD LDS ignores any value that you specify here if you do not set the value of InstallType to Replica. |
/ApplicationPartitionsToReplicate:{"DNs_of_partitions_to_replicate" | *}
Optional. Specifies the distinguished names of the application partitions to replicate from the source AD LDS instance. To replicate all application partitions from the source AD LDS instance, specify a wildcard character. AD LDS ignores any value that you specify here if you do not set the value of InstallType to Replica. |
| 20113 | /ReplicationSourcePath:"path_to_data_source"
Optional. Specifies the directory path to a backup of an AD LDS instance data. When this option is specified, AD LDS setup attempts an installation from media. This parameter can only be specified in cases where InstanceType is set to Replica. |
/ReplicationSourcePath:"path_to_data_source"
Optional. Specifies the directory path to a backup of an AD LDS instance data. When this option is specified, AD LDS setup attempts an installation from media. This parameter can only be specified in cases where InstanceType is set to Replica. |
| 20114 | /ReplicationLogSourcePath:"path_to_logs_source"
Optional. Specifies the directory path to a backup of an AD LDS instance logs. This parameter can only be specified in cases where InstanceType is set to Replica and ReplicationSourcePath has a valid value. |
/ReplicationLogSourcePath:"path_to_logs_source"
Optional. Specifies the directory path to a backup of an AD LDS instance logs. This parameter can only be specified in cases where InstanceType is set to Replica and ReplicationSourcePath has a valid value. |
| 20115 | /LocalLDAPPortToListenOn:{port_number: 389 or any unused port number between 1025 and 65535, inclusive}
Required. Specifies the local LDAP port to listen on. |
/LocalLDAPPortToListenOn:{port_number: 389 or any unused port number between 1025 and 65535, inclusive}
Required. Specifies the local LDAP port to listen on. |
| 20116 | /LocalSSLPortToListenOn:{port_number: 636 or any unused port number between 1025 and 65535, inclusive}
Required. Specifies the local SSL port to listen on. |
/LocalSSLPortToListenOn:{port_number: 636 or any unused port number between 1025 and 65535, inclusive}
Required. Specifies the local SSL port to listen on. |
| 20117 | /SourceServer:"Source Server DNS or NetBIOS name"
Required for replica installations. Specifies which server to replicate data from. |
/SourceServer:"Source Server DNS or NetBIOS name"
Required for replica installations. Specifies which server to replicate data from. |
| 20118 | /SourceLDAPPort: {port_number: 389 or a number between 1025 and 65535}
Required for replica installations. Specifies the port to use on the source server. |
/SourceLDAPPort: {port_number: 389 or a number between 1025 and 65535}
Required for replica installations. Specifies the port to use on the source server. |
| 20119 | /NewApplicationPartitionToCreate:"DN of application partition to create, with the name that you specify"
Optional. By default, no new application partition is created. |
/NewApplicationPartitionToCreate:"DN of application partition to create, with the name that you specify"
Optional. By default, no new application partition is created. |
| 20120 | /DataFilesPath:"path_name"
Optional. By default, the data is stored under "Program Files\Microsoft ADAM\instance_name\data" where instance_name is the name of the AD LDS instance. |
/DataFilesPath:"path_name"
Optional. By default, the data is stored under "Program Files\Microsoft ADAM\instance_name\data" where instance_name is the name of the AD LDS instance. |
| 20121 | /LogFilesPath:"path_name"
Optional. By default, the log files are stored under "Program Files\Microsoft ADAM\instance_name\data" where instance_name is the name of the AD LDS instance. |
/LogFilesPath:"path_name"
Optional. By default, the log files are stored under "Program Files\Microsoft ADAM\instance_name\data" where instance_name is the name of the AD LDS instance. |
| 20122 | /ServiceAccount:"name of the service account"
Optional. Name of the service account used by this AD LDS instance. The name of the service account can be specified in various formats: - DNS domain name, followed by a backslash, and then the account name - NetBIOS name, followed by a backslash, and then the account name - User Principal Name (UPN) - Account name only By default, the instance of AD LDS runs under the Network Service Account. |
/ServiceAccount:"name of the service account"
Optional. Name of the service account used by this AD LDS instance. The name of the service account can be specified in various formats: - DNS domain name, followed by a backslash, and then the account name - NetBIOS name, followed by a backslash, and then the account name - User Principal Name (UPN) - Account name only By default, the instance of AD LDS runs under the Network Service Account. |
| 20123 | /AddPermissionsToServiceAccount:{Yes|}
Optional. If Yes is specified, the AD LDS setup attempts to add the logon as a service right to the account that you specify as the service account. |
/AddPermissionsToServiceAccount:{Yes|}
Optional. If Yes is specified, the AD LDS setup attempts to add the logon as a service right to the account that you specify as the service account. |
| 20124 | /ServicePassword:"password"
Required when the specified ServiceAccount is not the Network Service Account. Specifies the service account password. |
/ServicePassword:"password"
Required when the specified ServiceAccount is not the Network Service Account. Specifies the service account password. |
| 20125 | /Administrator:"administrator name"
Optional. Name of the user that will administer this AD LDS instance. The administrator name can be specified in various formats: - DNS domain name, followed by a backslash, and then the account name - NetBIOS name, followed by a backslash, and then the account name - User Principal Name (UPN) - Account name only By default, the currently logged on user will have administrator permissions on this AD LDS instance. |
/Administrator:"administrator name"
Optional. Name of the user that will administer this AD LDS instance. The administrator name can be specified in various formats: - DNS domain name, followed by a backslash, and then the account name - NetBIOS name, followed by a backslash, and then the account name - User Principal Name (UPN) - Account name only By default, the currently logged on user will have administrator permissions on this AD LDS instance. |
| 20126 | /ImportLDIFFiles:"filename.ldf"
Optional. Specifies which optional ldif files you want to import into the AD LDS instance schema, among: md-User.ldf, ms-InetOrgPerson.ldf, ms-UserProxy.ldf, and ms-adman.ldf. By default, none of these optional ldif files are imported. |
/ImportLDIFFiles:"filename.ldf"
Optional. Specifies which optional ldif files you want to import into the AD LDS instance schema, among: md-User.ldf, ms-InetOrgPerson.ldf, ms-UserProxy.ldf, and ms-adman.ldf. By default, none of these optional ldif files are imported. |
| 20127 | /SourceUserName:"user name"
/SourcePassword:"password" Optional. Specifies the username and password of an account that has administrative rights for an existing configuration set; you should use these parameters when you install a replicat that you want to join to the corresponding configuration set. By default, AD LDS joins the replica to the configuration set by using the credentials of the logged on user. |
/SourceUserName:"user name"
/SourcePassword:"password" Optional. Specifies the username and password of an account that has administrative rights for an existing configuration set; you should use these parameters when you install a replicat that you want to join to the corresponding configuration set. By default, AD LDS joins the replica to the configuration set by using the credentials of the logged on user. |
| 20128 | The Configuration set level specified in the answer file is invalid. Please specify a valid value. | The Configuration set level specified in the answer file is invalid. Please specify a valid value. |
| 20129 | /ConfigurationSetLevel:{|3|4|5}
Optional. Specifies the configuration set level for a new unique AD LDS instance; the default is Windows Server 2003 (2). The ConfigurationSetLevel cannot be set for a replica. A value of 2 specifies Windows Server 2003. A value of 3 specifies Windows Server 2008. A value of 4 specifies Windows Server 2008 R2. A value of 5 specifies %WINDOWS_SERVER_VERSION_6_2%. |
/ConfigurationSetLevel:{|3|4|5}
Optional. Specifies the configuration set level for a new unique AD LDS instance; the default is Windows Server 2003 (2). The ConfigurationSetLevel cannot be set for a replica. A value of 2 specifies Windows Server 2003. A value of 3 specifies Windows Server 2008. A value of 4 specifies Windows Server 2008 R2. A value of 5 specifies %WINDOWS_SERVER_VERSION_6_2%. |
| File Description: | Active Directory Lightweight Directory Services Uninstaller |
| File Version: | 10.0.15063.0 (WinBuild.160101.0800) |
| Company Name: | Microsoft Corporation |
| Internal Name: | ADAMUNINSTALL |
| Legal Copyright: | © Microsoft Corporation. All rights reserved. |
| Original Filename: | adamuninstall.exe.mui |
| Product Name: | Microsoft® Windows® Operating System |
| Product Version: | 10.0.15063.0 |
| Translation: | 0x409, 1200 |