Merge branch 'MicrosoftDocs:main' into Branch-PostEdit

Author: AmandaAZ

support/azure/virtual-machines/linux/suse-public-cloud-connectivity-registration-issues.md

@@ -1,7 +1,7 @@
 ---
 title: Troubleshoot connectivity and registration for SUSE SLES VMs
 description: Troubleshoot scenarios in which an Azure VM that has a SUSE Linux Enterprise Server image can't connect to the SUSE Subscription Management Tool (SMT) repository.
-ms.date: 02/04/2025
+ms.date: 02/26/2025
 author: rnirek
 ms.author: hokamath
 ms.reviewer: adelgadohell, mahuss, esanchezvela, scotro, v-weizhu, divargas
@@ -221,29 +221,15 @@ If instances aren't regularly updated, they can become incompatible with our upd
     ```bash
     sudo zypper --pkg-cache-dir /root/packages/ download cloud-regionsrv-client cloud-regionsrv-client-plugin-azure regionServiceClientConfigAzure python3-azuremetadata SUSEConnect python3-cssselect python3-toml python3-lxml python3-M2Crypto python3-zypp-plugin libsuseconnect suseconnect-ruby-bindings docker libcontainers-common
     ```
-
-    > [!IMPORTANT]
-    > The latest `cloud-regionsrv-client-10.3.11-150300.13.19.1` introduces new dependencies (`libcontainers-common` and `docker`). This causes dependency errors. When [cloud instance repos fail because of outdated packages](https://www.suse.com/support/kb/doc/?id=000021552), the latest packages are installed:
-    >```ouput
-    >cloud-regionsrv-client 10.3.11-150300.13.19.1
-    >cloud-regionsrv-client-plugin-azure 2.0.0-150300.13.19.1
-    >```
-
-4. If there are dependency errors from the latest package, `cloud-regionsrv-client-10.3.11-150300.13.19.1`, you must downgrade `cloud-regionsrv-client` and `cloud-regionsrv-client-plugin-azure`. Otherwise, skip this step.
-
-    ```bash
-    sudo zypper --no-refresh --no-remote --non-interactive  install --old-package cloud-regionsrv-client-10.3.7-150300.13.14.1.noarch.rpm
-    sudo zypper --no-refresh --no-remote --non-interactive  install --old-package cloud-regionsrv-client-plugin-azure-2.0.0-150300.13.14.1.noarch.rpm
-    ```
-5. Run the following commands:
+4. Run the following commands:
 
     ```bash
     sudo find /root/packages/ -type f -name "*.rpm" -exec cp {} /root/packages/rpms/ \;
     sudo cd /root/packages
     sudo tar -czvf suse-public-registration.tgz rpms
     ```
 
-6. Transfer `suse-public-registration.tgz` to the broken instance:
+5. Transfer `suse-public-registration.tgz` to the broken instance:
 
     ```bash
     sudo scp /root/packages/suse-public-registration.tgz user@targetip:/tmp
@@ -252,7 +238,7 @@ If instances aren't regularly updated, they can become incompatible with our upd
     > [!NOTE]
     > Replace `user` and `targetip` as appropriate.
 
-7. Sign in to the broken instance to extract and install the packages:
+6. Sign in to the broken instance to extract and install the packages:
 
     ```bash
     sudo cd tmp
@@ -261,11 +247,12 @@ If instances aren't regularly updated, they can become incompatible with our upd
     sudo zypper --no-refresh --no-remote --non-interactive install --force *.rpm
     ```
 
-8. Register the VM again:
+7. Register the VM again:
 
     ```bash
     sudo registercloudguest --force-new
     ```
+For more information, see [Cloud instance repos fail due to outdated packages](https://www.suse.com/support/kb/doc/?id=000021552).
 
 ## Scenario 3: General registration issues
 

support/windows-server/active-directory/lds-service-startup-fails.md

@@ -1,7 +1,7 @@
 ---
 title: LDS service startup fails
 description: Introduce the solution for LDS Service startup failure after you manually change msDS-Behavior-Version attribute.
-ms.date: 01/15/2025
+ms.date: 02/26/2025
 manager: dcscontentpm
 audience: itpro
 ms.topic: troubleshooting
@@ -10,16 +10,14 @@ ms.custom:
 - sap:active directory\ldap configuration and interoperability
 - pcy:WinComm Directory Services
 ---
-# LDS service startup fails after you manually change msDS-Behavior-Version in Windows Server 2019 and 2016
+# LDS service startup fails after you manually change msDS-Behavior-Version in Windows Server
 
-This article provides a solution to an error that LDS service startup fails after you manually change msDS-Behavior-Version.
+This article provides a solution to an error that the LDS service startup fails after you manually change the **msDS-Behavior-Version** attribute.
 
-_Applies to:_   Windows Server 2019, Windows Server 2016  
+_Applies to:_   All supported versions of Windows Server and Windows Client  
 _Original KB number:_   4550446
 
-## Symptom
-
-In ADSI Edit, you change the **msDS-Behavior-Version** attribute of the Partitions container to **7** in order to raise the Active Directory (AD) Lightweight Directory Services (LDS) instance functional level to WIN2016.
+In ADSI Edit, you change the **msDS-Behavior-Version** attribute of the **Partitions** container to **7** in order to raise the Active Directory (AD) Lightweight Directory Services (LDS) instance functional level to **WIN2016**.
 
 :::image type="content" source="media/lds-service-startup-fails/attribute-editor.png" alt-text="Change the msDS-Behavior-Version attribute to 7.":::
 
@@ -51,81 +49,4 @@ Additionally, you receive the following error message:
 
 :::image type="content" source="media/lds-service-startup-fails/error-message.png" alt-text="Error 0xc0000025 Windows could not start the L D S service on Local Computer.":::
 
-## Cause
-
-Manually setting the **msDS-Behavior-Version** attribute value to **7** on LDS instances is not supported.
-
-## Resolution
-
-If the LDS instance contains only one server, you must restore the server from a backup to resolve the issue.
-
-If there are multiple replica servers in that instance (for example, LDSServer1 and LDSServer2), and if one server has not yet been restarted, follow these steps:
-
-1. If the LDS server on which the service that does not start (for example, LDSServer1) holds the LDS Roles (for example, Schema and Domain Naming FSMO), seize the roles by running ntdsutil:
-
-    > C:\Windows\system32> **ntdsutil**  
-    ntdsutil: **roles**  
-    fsmo maintenance: **connections**  
-    server connections: **connect to server LDSServer2:50000( 50000 is the port number in that example)**  
-    Binding to LDSServer2:50000 ...  
-    Connected to LDSServer2:50000 using credentials of locally logged on user.  
-    server connections: **q**  
-    fsmo maintenance: **seize schema master**
-
-    :::image type="content" source="media/lds-service-startup-fails/role-seizure-confirmation-dialog.png" alt-text="A role seizure confirmation dialog displays.":::
-
-2. Connect to the configuration partition of the server that still runs the LDS instance (for example, LDSServer2), and then roll back the functionality level version by reverting the **msDS-Behavior-Version** attribute value.
-
-3. Run a metadata cleanup of the LDS server (LDSServer1) by using **dsmgmt**:
-
-    > C:\Windows\system32> **dsmgmt**  
-    dsmgmt: **metadata cleanup**  
-    metadata cleanup: **connections**  
-    server connections: **connect to server LDSServer2:50000 ( 50000 is the port number in that example)**  
-    Binding to LDSServer2:50000 ...
-    Connected to LDSServer2:50000 using credentials of locally logged on user.
-    server connections: **q**  
-    metadata cleanup: **select operation target**  
-    select operation target: **list naming contexts**  
-    Found 3 Naming Context(s)
-    0 - CN=Configuration,CN={6B7FEBF4-017B-4366-A8B8-3E5467888DEF}
-    1 - CN=Schema,CN=Configuration,CN={6B7FEBF4-017B-4366-A8B8-3E5467888DEF}
-     2 - DC=LDS,DC=COM
-    select operation target: **select naming context2 ( 2 stands for the domain naming context )**  
-    No current site
-    No current domain
-    No current server
-    Naming Context - DC=LDS,DC=COM
-    select operation target: **list sites**  
-    Found 4 site(s)
-    0 - CN=Default-First-Site-Name,CN=Sites,CN=Configuration,CN={6B7FEBF4-017B-4366-A8B8-3E5467888DEF}
-    1 - CN=Site1,CN=Sites,CN=Configuration,CN={6B7FEBF4-017B-4366-A8B8-3E5467888DEF}
-    2 - CN=Site2,CN=Sites,CN=Configuration,CN={6B7FEBF4-017B-4366-A8B8-3E5467888DEF}
-     3 - CN=Site3,CN=Sites,CN=Configuration,CN={6B7FEBF4-017B-4366-A8B8-3E5467888DEF}
-    select operation target: **select site3 (where 3 is the number of the site in which the server is located,** **matching output from previous step)**  
-    Site - CN=Site3,CN=Sites,CN=Configuration,CN={6B7FEBF4-017B-4366-A8B8-3E5467888DEF}
-    No current domain
-    No current server
-    Naming Context - DC=LDS,DC=COM
-    select operation target: **list servers in Site**  
-    Found 1 server(s)
-     0 - CN=LDSServer1,CN=Servers,CN=Site3,CN=Sites,CN=Configuration,CN={6B7FEBF4-017B-4366-A8B8-3E5467888DEF}
-    select operation target: **select Server0 (where 0 is the number of the server you wish to remove, matching output from previous step)**  
-    Site - CN=Site3,CN=Sites,CN=Configuration,CN={6B7FEBF4-017B-4366-A8B8-3E5467888DEF}
-    No current domain
-    Server - CN=LDSServer1,CN=Servers,CN=Site3,CN=Sites,CN=Configuration,CN={6B7FEBF4-017B-4366-A8B8-3E5467888DEF}
-    DSA object - CN=NTDS Settings,CN=LDSServer1,CN=Servers,CN=Site3,CN=Sites,CN=Configuration,CN={6B7FEBF4-017B-4366-A8B8-3E5467888DEF}
-    DNS host name - LDSServer1.CONTOSO.COM
-    Naming Context - DC=LDS,DC=COM
-    select operation target: **q**  
-    metadata cleanup: **remove selected server**
-
-    :::image type="content" source="media/lds-service-startup-fails/server-remove-confirmation-dialog.png" alt-text="Select Yes to remove the server object in the Server Remove Confirmation Dialog box.":::
-
-4. Log on to LDSServer1, and uninstall the instance:
-
-    :::image type="content" source="media/lds-service-startup-fails/uninstall-program.png" alt-text="Select the instance that you want to uninstall in Programs and features window.":::
-
-    :::image type="content" source="media/lds-service-startup-fails/select-skip-all.png" alt-text="Select Skip All in the Active Directory Lightweight Directory Services Removal Wizard.":::
-
-5. Run the Active Directory Lightweight Directory Services Setup (C:\Windows\ADAM\adaminstall.exe) on LDSServer1 to install a replica of the existing instance from LDSServer2.
+For Windows servers with monthly updates before the February 2025 update rollup installed, manually setting the **msDS-Behavior-Version** attribute value of LDS instances to **7** isn't supported. To resolve the issue, install the February 2025 update rollup or a later version.