Question about a Virtual Server -

It sounds like you are experiencing issues related to the user interface and functionality of your Virtual Server that is acting as a Domain Controller. Here are some potential reasons and solutions for the problems you're facing:

1. Missing "Logon as Other User" and "Switch User" Options: This could be due to a configuration issue or a policy setting that has been altered. You can check the Group Policy settings to ensure that these options are not disabled. You can access Group Policy by running gpedit.msc and navigating to Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options. Look for policies related to user logon options.
2. Limited Functionality After Logon: If you are logged into the Virtual Server and it appears to be in a limited state (like a stripped-down version of Windows), it could be that you are logged into Directory Services Repair Mode (DSRM) instead of the normal operating mode. This can happen if the server was not properly booted up or if there was an issue with the Active Directory services. To resolve this:
   • Restart the server and ensure it boots normally.
   • If it continues to boot into DSRM, you may need to check the boot configuration or repair the Active Directory installation.
   • You can also try logging in with the DSRM administrator account (using .\administrator as the username) and the DSRM password set during the original promotion of the domain controller.

If these steps do not resolve your issues, further investigation into the server's configuration and logs may be necessary to identify any underlying problems.

References:

• No logon servers are available error after cloning domain controller
• Virtualized Domain Controller Troubleshooting

Hi Michael Bach,

Regarding your issue, the Virtual Server is booting into Directory Services Repair Mode (DSRM) rather than normal Active Directory mode. This explains both the missing “Switch User” / “Logon as Other User” options and the stripped-down interface. DSRM disables normal shell components and Active Directory services. Verify the boot sequence in bcdedit, look for the /SAFEBOOT:DSREPAIR flag.

Remove it if present to force normal boot. Log in with the local DSRM administrator account to confirm credentials. Ensure the Active Directory Domain Services service starts and that SYSVOL and NTDS directories are intact. Once AD services are running, the Start Menu, Active Directory tools, and user logon options will return. Do not attempt to manipulate the interface while in DSRM; the environment is intentionally minimal.

I hope you find this piece of information useful to some extent. It's really appreciated of you to accept the answer as a way to share your valuable experience with the community. Thank you!

Vivian

Hello, it's me again. Did you find the answer useful? Do you need further assistance? In case everything has been fine, it's appreciated of you to accept the answer so that it could be spread further to those in need too. Thank you.

VP