Merge pull request #6742 from MicrosoftDocs/main

3/18/2025 PM Publish

Author: Albertyang0

WindowsServerDocs/administration/windows-commands/robocopy.md

@@ -5,7 +5,7 @@ ms.topic: reference
 ms.assetid: d4c6e8e9-fcb3-4a4a-9d04-2d8c367b6354
 author: xelu86
 ms.author: alalve
-ms.date: 05/28/2024
+ms.date: 03/17/2025
 ---
 
 # robocopy
@@ -25,7 +25,7 @@ robocopy c:\reports "\\marketing\videos" yearly-report.mov /mt /z
 ```
 
 > [!IMPORTANT]
-> If any data is copied from the _root_ of a device, the destination directory will adopt the "hidden" attribute during the copy process.
+> If any data is copied from the _root_ of a device, the destination directory adopts the "hidden" and "system" attributes during the copy process.
 
 ### Parameters
 
@@ -113,15 +113,15 @@ These throttling options are used to specify the maximum I/O bandwidth that Robo
 | /xc | Excludes existing files with the same timestamp, but different file sizes. |
 | /xn | Source directory files newer than the destination are excluded from the copy. |
 | /xo | Source directory files older than the destination are excluded from the copy. |
-| /xx | Excludes extra files and directories present in the destination but not the source. Excluding extra files won't delete files from the destination. |
+| /xx | Excludes extra files and directories present in the destination but not the source. Excluding extra files doesn't delete files from the destination. |
 | /xl | Excludes "lonely" files and directories present in the source but not the destination. Excluding lonely files prevents any new files from being added to the destination. |
 | /im | Include modified files (differing change times). |
 | /is | Includes the same files. Same files are identical in name, size, times, and all attributes. |
 | /it | Includes "tweaked" files. Tweaked files have the same name, size, and times, but different attributes. |
 | /max:`<n>` | Specifies the maximum file size (to exclude files bigger than *n* bytes). |
 | /min:`<n>` | Specifies the minimum file size (to exclude files smaller than *n* bytes). |
-| /maxage:`<n>` | Specifies the maximum file age (to exclude files older than *n* days or date). |
-| /minage:`<n>` | Specifies the minimum file age (exclude files newer than *n* days or date). |
+| /maxage:`<n>` | Specifies the maximum file age to exclude files older than *n* days or a date based on when the files were last _modified_. |
+| /minage:`<n>` | Specifies the minimum file age to exclude files newer than *n* days or a date based on when the files were last _modified_. |
 | /maxlad:`<n>` | Specifies the maximum last access date (excludes files unused since *n*). |
 | /minlad:`<n>` | Specifies the minimum last access date (excludes files used since *n*) If *n* is less than 1900, *n* specifies the number of days. Otherwise, *n* specifies a date in the format YYYYMMDD. |
 | /xj | Excludes junction points, which are normally included by default. |
@@ -155,7 +155,7 @@ These throttling options are used to specify the maximum I/O bandwidth that Robo
 | /nc | Specifies that file classes aren't to be logged. |
 | /nfl | Specifies that file names aren't to be logged. |
 | /ndl | Specifies that directory names aren't to be logged. |
-| /np | Specifies that the progress of the copying operation (the number of files or directories copied so far) won't be displayed. |
+| /np | Specifies to not display the progress of the copying operation (the number of files or directories copied so far). |
 | /eta | Shows the estimated time of arrival (ETA) of the copied files. |
 | /log:`<logfile>` | Writes the status output to the log file (overwrites the existing log file). |
 | /log+:`<logfile>` | Writes the status output to the log file (appends the output to the existing log file). |
@@ -179,17 +179,17 @@ These throttling options are used to specify the maximum I/O bandwidth that Robo
 
 #### Remarks
 
-- Using **/PURGE** or **/MIR** on the root directory of the volume formerly caused robocopy to apply the requested operation on files inside the System Volume Information directory as well. This is no longer the case as if either is specified, robocopy will skip any files or directories with that name in the top-level source and destination directories of the copy session.
+- Using **/PURGE** or **/MIR** on the root directory of the volume formerly caused robocopy to apply the requested operation on files inside the System Volume Information directory as well. This is no longer the case as if either is specified, robocopy skips any files or directories with that name in the top-level source and destination directories of the copy session.
 
 - Modified files classification applies only when both source and destination filesystems support change timestamps, such as NTFS, and the source and destination files have different change times but are otherwise the same. These files aren't copied by default. Specify **/IM** to include them.
 
-- The **/DCOPY:E** flag requests that extended attribute copying should be attempted for directories. Robocopy will continue if a directory's EAs couldn't be copied. This flag isn't included in **/COPYALL**.
+- The **/DCOPY:E** flag requests that extended attribute copying should be attempted for directories. Robocopy continues the copy operation even if a directory's EAs couldn't be copied. This flag isn't included in **/COPYALL**.
 
-- If either **/IoMaxSize** or **/IoRate** are specified, robocopy will enable copy file throttling to reduce system load. Both can be adjusted to optimal values and copy parameters, but the system and robocopy are allowed to adjust them to allowed values as necessary.
+- If either **/IoMaxSize** or **/IoRate** are specified, robocopy enables copy file throttling to reduce system load. Both can be adjusted to optimal values and copy parameters, but the system and robocopy are allowed to adjust them to allowed values as necessary.
 
-- If **/Threshold** is used, it specifies a minimum file size for engaging throttling. Files below that size won't be throttled. Values for all three parameters can be followed by an optional suffix character such as [KMG] (kilobytes, megabytes, gigabytes).
+- If **/Threshold** is used, it specifies a minimum file size for engaging throttling. Files below that size aren't throttled. Values for all three parameters can be followed by an optional suffix character such as [KMG] (kilobytes, megabytes, gigabytes).
 
-- Using **/LFSM** requests robocopy to operate in 'low free space mode'. In this mode, robocopy will pause whenever a file copy would cause the destination volume's free space to go below a 'floor' value. This value can be explicitly specified using **/LFSM:_n_**[KMG] flag.
+- Using **/LFSM** requests robocopy to operate in 'low free space mode'. In this mode, robocopy pauses whenever a file copy would cause the destination volume's free space to go below a 'floor' value. This value can be explicitly specified using **/LFSM:_n_**[KMG] flag.
 
 - If **/LFSM** is specified with no explicit floor value, the floor is set to 10% of the destination volume's size. Low free space mode is incompatible with **/MT** and **/EFSRAW**.
 
@@ -213,42 +213,48 @@ These throttling options are used to specify the maximum I/O bandwidth that Robo
 
 It's highly recommended when running the `robocopy` command to create a log file that can be viewed once the process completes verifying its integrity. In the following examples, each one uses the `/LOG:` parameter. To append any log information to the same log file, use the `/LOG+:` parameter instead.
 
-To copy all files and subdirectories, including empty directories, from the "Records" folder to the "Backup" folder on drive "D", type the following:
+To copy all files and subdirectories, including empty directories, from the "Records" folder to the "Backup" folder on drive "D", type:
 
 ```cmd
 robocopy C:\Users\Admin\Records D:\Backup /E /ZB /LOG:C:\Logs\Backup.log
 ```
 
-To mirror the contents of the "Records" folder to the "Backup" folder on drive "D", delete any files in the destination that don't exist in the source with 2 retries and waiting 5 seconds between each retry, type the following:
+To mirror the contents of the "Records" folder to the "Backup" folder on drive "D", delete any files in the destination that don't exist in the source with 2 retries and waiting 5 seconds between each retry, type:
 
 ```cmd
 robocopy C:\Users\Admin\Records D:\Backup /MIR /R:2 /W:5 /LOG:C:\Logs\Backup.log
 ```
 
-To copy all files and subdirectories that aren't empty from the "Records" folder to the "Backup" folder on drive "D", retaining the file data, attributes, and timestamps with 16 multi-threaded copy operation, type the following:
+To copy all files and subdirectories that aren't empty from the "Records" folder to the "Backup" folder on drive "D", retaining the file data, attributes, and timestamps with 16 multi-threaded copy operation, type:
 
 ```cmd
 robocopy C:\Users\Admin\Records D:\Backup /S /E /COPY:DAT /MT:16 /LOG:C:\Logs\Backup.log
 ```
 
-To move files and subdirectories, excluding empty directories, from the "Records" folder to the "Backup" folder on drive "D", and exclude files older than 7 days, type the following:
+To move files and subdirectories, excluding empty directories, from the "Records" folder to the "Backup" folder on drive "D", and exclude files older than 7 days, type:
 
 ```cmd
 robocopy C:\Users\Admin\Records D:\Backup /S /MAXAGE:7 /MOV /LOG:C:\Logs\Backup.log
 ```
 
-To copy all files and subdirectories, including empty directories, from the "Records" folder to the "Backup" folder on drive "D" showing the estimated time for each file and delete any files and directories in the destination that don't exist from the source, type the following:
+To copy all files and subdirectories, including empty directories, from the "Records" folder to the "Backup" folder on drive "D" showing the estimated time for each file and delete any files and directories in the destination that don't exist from the source, type:
 
 ```cmd
 robocopy C:\Users\Admin\Records D:\Backup /ETA /PURGE /LOG:C:\Logs\Backup.log
 ```
 
-To copy all files and subdirectories from the folder named "Records" on the "C" drive to a folder named "Backup" on the "D" drive while limiting the I/O rate to 1 megabyte per second during the copy operation, type the following:
+To copy all files and subdirectories from the folder named "Records" on the "C" drive to a folder named "Backup" on the "D" drive while limiting the I/O rate to 1 megabyte per second during the copy operation, type:
 
 ```cmd
 robocopy C:\Records D:\Backup /iorate:1m
 ```
 
+To skip copying files from a source folder to a destination folder when the files already exist in the destination folder, regardless of whether they're newer, older, or modified, type:
+
+```cmd
+robocopy C:\Source C:\Destination /XC /XN /XO
+```
+
 ## Related links
 
 - [Command-Line Syntax Key](command-line-syntax-key.md)

WindowsServerDocs/administration/windows-commands/shutdown.md

@@ -5,7 +5,7 @@ ms.topic: reference
 ms.assetid: c432f5cf-c5aa-4665-83af-0ec52c87112e
 author: xelu86
 ms.author: alalve
-ms.date: 10/04/2023
+ms.date: 03/18/2025
 ---
 
 # shutdown
@@ -112,6 +112,12 @@ To force apps to close and to restart the local computer after a one-minute dela
 shutdown /r /t 60 /c "Reconfiguring myapp.exe" /f /d p:4:1
 ```
 
+To perform a planned shutdown of a device in 10 minutes and capture the reason in the shutdown event tracker with the comment "Scheduled maintenance", type:
+
+```
+shutdown.exe /s /t 600 /d p:0:0 /e /c "Scheduled maintenance"
+```
+
 To restart the remote computer *myremoteserver* with the same parameters as the previous example, type:
 
 ```

WindowsServerDocs/identity/ad-ds/deploy/virtual-dc/adds-on-azure-vm.md

@@ -1,10 +1,10 @@
 ---
 title: Install Active Directory Domain Services on an Azure virtual machine
 description: How to create a new Active Directory forest on a virtual machine (VM) on an Azure virtual machine.
-author: iainfoulds
+author: justinha
 ms.author: justinha
-manager: daveba
-ms.date: 6/28/2022
+manager: femila
+ms.date: 03/18/2025
 ms.topic: article
 ---
 
@@ -19,7 +19,7 @@ AD DS can run on an Azure virtual machine (VM) in the same way it runs in many o
 * An Azure virtual machine [availability set](/azure/virtual-machines/availability-set-overview) to put two Active Directory Domain Services (AD DS) domain controllers in.
 * Two Azure virtual machines to run AD DS and DNS.
 
-### Items that are not covered
+### Items that aren't covered
 
 * [Creating a site-to-site VPN connection](/azure/vpn-gateway/tutorial-site-to-site-portal) from an on-premises location
 * [Securing network traffic in Azure](/azure/security/azure-security-network-security-best-practices)
@@ -39,17 +39,17 @@ If you don't have an Azure subscription, [create a free account](https://azure.m
 
 The following script automates the process of building two Windows Server 2019 VMs, for the purpose of building domain controllers for a new Active Directory Forest in Azure. An administrator can modify the variables below to suit their needs, then complete, as one operation. The script creates the necessary resource group, network security group with a traffic rule for Remote Desktop, virtual network and subnet, and availability group. The VMs are each then built with a 20 GB data disk with caching disabled for AD DS to be installed to.
 
-The script below can be run directly from the Azure portal. If you choose to install and use the CLI locally, this quickstart requires that you are running the Azure CLI version 2.0.4 or later. Run `az --version` to find the version. If you need to install or upgrade, see [Install Azure CLI 2.0](/cli/azure/install-azure-cli).
+The script below can be run directly from the Azure portal. If you choose to install and use the CLI locally, this quickstart requires that you're running the Azure CLI version 2.0.4 or later. Run `az --version` to find the version. If you need to install or upgrade, see [Install Azure CLI 2.0](/cli/azure/install-azure-cli).
 
 | Variable Name | Purpose |
 | :---: | :--- |
 | AdminUsername | Username to be configured on each VM as the local administrator. |
 | AdminPassword | Cleartext password to be configured on each VM as the local administrator password. |
-| ResourceGroupName | Name to be used for resource group. Should not duplicate an existing name. |
+| ResourceGroupName | Name to be used for resource group. Shouldn't duplicate an existing name. |
 | Location | Azure location name that you would like to deploy to. List supported regions for the current subscription using `az account list-locations`. |
-| VNetName | Name to assign the Azure virtual network Should not duplicate an existing name. |
-| VNetAddress | IP scope to use for Azure networking. Should not duplicate an existing range. |
-| SubnetName | Name to assign the IP subnet. Should not duplicate an existing name. |
+| VNetName | Name to assign the Azure virtual network Shouldn't duplicate an existing name. |
+| VNetAddress | IP scope to use for Azure networking. Shouldn't duplicate an existing range. |
+| SubnetName | Name to assign the IP subnet. Shouldn't duplicate an existing name. |
 | SubnetAddress | Subnet address for the domain controllers. Should be a subnet inside of the VNet. |
 | AvailabilitySet | Name of the availability set the domain controller VMs will join. |
 | VMSize | Standard Azure VM Size available in the location for deployment. |
@@ -60,7 +60,7 @@ The script below can be run directly from the Azure portal. If you choose to ins
 | DC2IP | IP address for second domain controller. |
 
 ```azurecli
-#Update based on your organizational requirements
+#Add lines for AdminUsername and AdminPassword, and update based on your organizational requirements
 Location=westus2
 ResourceGroupName=ADonAzureVMs
 NetworkSecurityGroup=NSG-DomainControllers
@@ -71,8 +71,6 @@ SubnetAddress=10.10.10.0/24
 AvailabilitySet=DomainControllers
 VMSize=Standard_DS1_v2
 DataDiskSize=20
-AdminUsername=azureuser
-AdminPassword=ChangeMe123456
 DomainController1=AZDC01
 DC1IP=10.10.10.11
 DomainController2=AZDC02
@@ -149,7 +147,7 @@ az vm create \
 
 If the Azure virtual machines created as part of this process will be an extension of an existing on-premises Active Directory infrastructure, the DNS settings on the virtual network must be changed to include your on-premises DNS servers before deployment. This step is important to allow the newly created Domain Controllers in Azure to resolve on-premises resources and allow for replication to occur. More information about DNS, Azure, and how to configure settings can be found in the section [Name resolution that uses your own DNS server](/azure/virtual-network/virtual-networks-name-resolution-for-vms-and-role-instances#name-resolution-that-uses-your-own-dns-server).
 
-After promoting the new domain controllers in Azure, they will need to be set to the primary and secondary DNS Servers for the virtual network, and any on-premises DNS Servers would be demoted to tertiary and beyond. VMs continue to use their current DNS settings until they are restarted. More information on changing DNS Servers can be found in the article [Create, change, or delete a virtual network](/azure/virtual-network/manage-virtual-network#change-dns-servers).
+After promoting the new domain controllers in Azure, they'll need to be set to the primary and secondary DNS Servers for the virtual network, and any on-premises DNS Servers would be demoted to tertiary and beyond. VMs continue to use their current DNS settings until they're restarted. More information on changing DNS Servers can be found in the article [Create, change, or delete a virtual network](/azure/virtual-network/manage-virtual-network#change-dns-servers).
 
 Information about extending an on-premises network to Azure can be found in the article [Creating a site-to-site VPN connection](/azure/vpn-gateway/vpn-gateway-howto-site-to-site-resource-manager-portal).
 
@@ -174,7 +172,7 @@ Connect to AZDC01 using the credentials you provided in the script.
    * Review the selections made in the wizard and choose **Next**
 
 > [!NOTE]
-> The Prerequisites Check will warn you that the physical network adapter does not have static IP address(es) assigned, you can safely ignore this as static IPs are assigned in the Azure virtual network.
+> The Prerequisites Check will warn you that the physical network adapter doesn't have static IP address(es) assigned, you can safely ignore this as static IPs are assigned in the Azure virtual network.
 
 * Choose **Install**
 
@@ -210,7 +208,7 @@ Connect to AZDC02 using the credentials you provided in the script.
    * Review the selections made in the wizard and choose **Next**
 
 > [!NOTE]
-> The Prerequisites Check will warn you that the physical network adapter does not have static IP address(es) assigned. You can safely ignore this, as static IPs are assigned in the Azure virtual network.
+> The Prerequisites Check will warn you that the physical network adapter doesn't have static IP address(es) assigned. You can safely ignore this, as static IPs are assigned in the Azure virtual network.
 
 * Choose **Install**
 

WindowsServerDocs/identity/ad-ds/manage/group-managed-service-accounts/group-managed-service-accounts/group-managed-service-accounts-overview.md

@@ -5,7 +5,7 @@ ms.topic: article
 ms.assetid: cef0693c-f861-48a7-a1c0-8d1bc06143ce
 ms.author: roharwoo
 author: robinharwood
-ms.date: 09/17/2024
+ms.date: 03/18/2025
 ---
 # Group Managed Service Accounts Overview
 
@@ -49,7 +49,6 @@ Here are some other resources you can read to learn more about Managed Service A
 
 - [Managed Service Accounts Documentation for Windows 7 and Windows Server 2008 R2](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/ff641731(v=ws.10))
 - [Service Accounts Step-by-Step Guide](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/dd548356(v=ws.10))
-- [Managed Service Accounts in Active Directory](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/dd378925(v=ws.10))
 - [Getting Started with Group Managed Service Accounts](getting-started-with-group-managed-service-accounts.md)
 - [Managed Service Accounts in Active Directory Domain Services](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/dd378925(v=ws.10))
 - [Managed Service Accounts: Understanding, Implementing, Best Practices, and Troubleshooting](/archive/blogs/askds/managed-service-accounts-understanding-implementing-best-practices-and-troubleshooting)