The user had been using the configured autologin for a long time under the domain user account on a laptop running Windows Prof operating system. However, after some unknown manipulations, the system started asking for the login password.

Due to not using the computer as part of the enterprise's local network for a long time, the sysadmins are unaware of the password set for the accounts of the local administrator and domain user.

There seems to be an issue with logging in under the domain administrator account, as the system reports that interactive login on the computer is prohibited by local policy. Additionally, when attempting to log in remotely, there are no connections available to all users.

It is possible that the disconnected LAN connection or other reasons could be preventing the computer from seeing the domain controller.

In this situation, gaining access to the account of a domain user or a local admin may require resetting the password or restoring the computer to a previous point in time. It is advisable to consult with IT support for assistance in resolving these issues.

To carry out this task, you will require a bootable live CD with Win* installed (preferably Win7 installer) and WindowsGate. To gain access to the required data, you can use methods such as LiveCD or by connecting a laptop hard drive to another computer (if SATA, it's quite simple, but if IDE, you'll need a USB adapter which costs around 300 rubles).

Once you have these tools, launch WindowsGate and select the desired OS. Choose the Utilman hack option and check the box. After booting into the OS, press Win+U and run CMD.exe. In the CMD window, run gpedit.msc and view the parameters. If necessary, make any required changes to the "Local Login" settings, making sure that it has at least Administrators and Users.

Next, run gpupdate /force in CMD and try to log in. If successful, reboot from the LiveCD again, launch WindowsGate and uncheck the Utilman hack box.

It is important to note that this process should be carried out only when absolutely necessary and with the appropriate legal permission. Unauthorised access to someone's data is a serious offence and can carry legal consequences.

To begin troubleshooting, the first step is to ensure that the domain controller is accessible. This can be done by checking the logs or using the ping command. Once the domain is confirmed to be available remotely, we can proceed to investigate the status of the local admin account through the laptop console (mmc).

In a recent incident, we encountered a similar situation and were able to resolve it. However, if you have any queries or concerns, please don't hesitate to message us.

In the event that these initial steps fail to yield results, the domain admin's next recourse could be to remotely access the registry to assess the situation. Alternatively, connecting an ip-kvm to the laptop, while expensive, remains another viable option worth considering.

In case the computer has been absent from the enterprise network for over a month, its computer account may have expired. To check for this issue, refer to KB 216393 and examine the event log on the controller. If the computer account has indeed expired, you will need to reset the administrator account using a tool like "Offline NT Password & Registry Editor" and then reset the computer account.

To avoid such problems in the future, it is recommended to create a separate Organizational Unit (OU) for the computer in the Active Directory (AD) and apply a policy that grants local access rights to domain users and adds domain administrators to the local administrators group. This policy can be implemented through the domain policy, as shown earlier. It would also be useful to implement this policy as a precautionary measure.

To regain access to the domain user or local admin accounts, you have a few options:

1. Resetting the Password: If you have physical access to the laptop, you can try resetting the password for the domain user or local admin accounts. This can typically be done using a password reset disk or through the Windows Recovery Environment.

2. System Restore: If you suspect that the issue arose due to recent changes on the system, you can try restoring the computer to a previous restore point. This should revert any system settings changes that might have caused the login problem.

3. Network Connectivity: It's possible that the laptop's disconnection from the local network is preventing it from accessing the domain controller. Ensure that the LAN connection is properly established and troubleshoot any network connectivity issues that might be causing this problem.

However, since you mentioned that this laptop is part of an enterprise network, it is advisable to reach out to your IT support team for assistance. They will have the knowledge and tools to resolve these types of issues efficiently and securely within your organization's policies.

steps you can take to troubleshoot and resolve the login issues:

1. Check Local Policy: If you are receiving a message stating that interactive login on the computer is prohibited by local policy when trying to log in with the domain administrator account, you might want to verify the local security policy settings. Use the "Local Security Policy" tool to check if any policies are preventing interactive logins.

2. Test Remote Connection: If you are unable to establish remote connections to the laptop, ensure that the necessary services (such as Remote Desktop Protocol) are running and properly configured on the laptop. Additionally, check if any firewall or network settings are blocking incoming remote connections.

3. Offline Password Reset: If you don't have access to a password reset disk or other recovery options, you can try using specialized tools designed for offline password resetting. These tools can help reset the password for the domain user or local admin account without requiring authentication.

4. Boot in Safe Mode: Try booting the laptop in Safe Mode. Sometimes, this can bypass certain login issues and allow you to access the system using either the domain user or local admin accounts. From there, you can make any necessary changes or troubleshooting steps.

5. Contact IT Support: As mentioned before, it is best to contact your IT support team for assistance. They can guide you through the specific steps required to resolve the issue based on your organization's policies and infrastructure setup.