You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Indicates that the cmdlet forces the removal of a domain controller.
130
-
Use this parameter to force the uninstall of AD DS if you need to remove the domain controller and do not have connectivity to other domain controllers within the domain topology.
144
+
145
+
Indicates that the cmdlet forces the removal of a domain controller. Use this parameter to force the
146
+
uninstall of AD DS if you need to remove the domain controller and do not have connectivity to other
Indicates that Windows PowerShell ignores any inconsistency that it detects with the value that you specify for the *LastDomainControllerInDomain* parameter.
146
-
For instance, if you specify *LastDomainControllerInDomain* but Windows PowerShell detects that there is actually another active domain controller in the domain, you can specify the *IgnoreLastDCInDomainMismatch* parameter to have Windows PowerShell continue the removal of AD DS from the domain controller despite the inconsistency that it has detected.
147
-
Similarly, if you do not specify *LastDomainControllerInDomain* but Windows PowerShell cannot detect that another domain controller is in the domain, you can specify *IgnoreLastDCInDomainMismatch* to have Windows PowerShell continue to remove AD DS from the domain controller.
162
+
163
+
Indicates that Windows PowerShell ignores any inconsistency that it detects with the value that you
164
+
specify for the **LastDomainControllerInDomain** parameter. For instance, if you specify
165
+
**LastDomainControllerInDomain** but Windows PowerShell detects that there is actually another
166
+
active domain controller in the domain, you can specify the **IgnoreLastDCInDomainMismatch**
167
+
parameter to have Windows PowerShell continue the removal of AD DS from the domain controller
168
+
despite the inconsistency that it has detected. Similarly, if you do not specify
169
+
**LastDomainControllerInDomain** but Windows PowerShell cannot detect that another domain
170
+
controller is in the domain, you can specify **IgnoreLastDCInDomainMismatch** to have Windows
171
+
PowerShell continue to remove AD DS from the domain controller.
Indicates that the cmdlet continues the removal of AD DS despite the fact that the domain controller is the last DNS server for one or more of the Active Directory-integrated DNS zones that it hosts.
186
+
187
+
Indicates that the cmdlet continues the removal of AD DS despite the fact that the domain controller
188
+
is the last DNS server for one or more of the Active Directory-integrated DNS zones that it hosts.
Specifies a local administrator account password when AD DS is removed from a domain controller.
193
-
In earlier releases, where uninstall of AD DS was done using Dcpromo.exe for demotion, the default was to allow an empty password for this setting.
194
-
In Windows PowerShell, the ADDS Deployment module requires that a non-empty password string value be assigned.
195
-
If a value is not provided for this parameter, you are prompted to enter a value for the password at the Windows PowerShell prompt.
196
-
The password value must be a secure string.
220
+
221
+
Specifies a local administrator account password when AD DS is removed from a domain controller. In
222
+
earlier releases, where uninstall of AD DS was done using `Dcpromo.exe` for demotion, the default
223
+
was to allow an empty password for this setting. In Windows PowerShell, the ADDS Deployment module
224
+
requires that a non-empty password string value be assigned. If a value is not provided for this
225
+
parameter, you are prompted to enter a value for the password at the Windows PowerShell prompt. The
226
+
password value must be a secure string.
197
227
198
228
If this parameter is not specified, the cmdlet prompts you to enter and confirm a masked password.
199
-
This is the preferred usage when running the cmdlet interactively.
200
-
If additionally there are no other arguments specified with the cmdlet, you are prompted to enter a masked password for this parameter but no confirmation of the password entered is made.
201
-
This is not recommended as it could allow a mistyped password to be configured.
202
-
Another available advanced option is to use the **ConvertTo-SecureString** cmdlet and specify the password string inline as unmasked console input, which is also not a recommended security best practice in production deployments.
229
+
This is the preferred usage when running the cmdlet interactively. If additionally there are no
230
+
other arguments specified with the cmdlet, you are prompted to enter a masked password for this
231
+
parameter but no confirmation of the password entered is made. This is not recommended as it could
232
+
allow a mistyped password to be configured. Another available advanced option is to use the
233
+
`ConvertTo-SecureString`cmdlet and specify the password string inline as unmasked console input,
234
+
which is also not a recommended security best practice in production deployments.
Indicates that the cmdlet restarts the computer upon completion, regardless of success.
218
-
By default, reboot upon completion occurs when this cmdlet is used and this parameter is omitted.
219
-
As a general rule, Microsoft support recommends that you not use this parameter except for testing or troubleshooting purposes because once configuration has completed the server will not function correctly as either a member server or a DC until it is rebooted.
249
+
250
+
Indicates that the cmdlet restarts the computer upon completion, regardless of success. By default,
251
+
reboot upon completion occurs when this cmdlet is used and this parameter is omitted. As a general
252
+
rule, Microsoft support recommends that you not use this parameter except for testing or
253
+
troubleshooting purposes because once configuration has completed the server will not function
254
+
correctly as either a member server or a DC until it is rebooted.
Specifies whether to preserve DNS delegation that point to this DNS server from the parent DNS Zone. If you use this parameter, DNS delegations that point to this server from the parent DNS zone will not be retained after uninstallation of the domain controller.
251
-
This setting corresponds to the earlier Dcpromo.exe parameter default of /RemoveDNSDelegation:Yes.
287
+
Specifies whether to preserve DNS delegation that point to this DNS server from the parent DNS Zone.
288
+
If you use this parameter, DNS delegations that point to this server from the parent DNS zone will
289
+
not be retained after uninstallation of the domain controller. This setting corresponds to the
290
+
earlier `Dcpromo.exe` parameter default of `/RemoveDNSDelegation:Yes`.
Indicates that only a base set of validations is performed.
282
-
This behavior is equivalent to the validations that were performed when using Dcpromo.exe in earlier versions of Windows Server to add a new domain controller.
283
-
When this switch parameter is set, it specifies that additional preliminary checks should be bypassed.
284
-
For more information on the scope of these additional preliminary checks that the ADDSDeployment module performs by default when using Windows Server 2012, refer to the table in the section ADPrep and Prerequisite Checking Architecture in [AD DS Simplified Administration](https://go.microsoft.com/fwlink/?LinkID=237244).
322
+
323
+
Indicates that only a base set of validations is performed. This behavior is equivalent to the
324
+
validations that were performed when using `Dcpromo.exe` in earlier versions of Windows Server to
325
+
add a new domain controller. When this switch parameter is set, it specifies that additional
326
+
preliminary checks should be bypassed. For more information on the scope of these additional
327
+
preliminary checks that the **ADDSDeployment** module performs by default when using Windows Server
328
+
2012, refer to the table in the section ADPrep and Prerequisite Checking Architecture in
This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see [about_CommonParameters](https://go.microsoft.com/fwlink/?LinkID=113216).
360
+
361
+
This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable,
0 commit comments