Vmware auto-starts on boot (Vmware17) (virtual machine auto-start, virtual machine auto-start, and host auto-start) (Failed to exclusively lock this configuration file. Another running VMware process may be using the configuration file)

Reference article 1: VMware workstation16 sets up the virtual machine to start up

Reference article 2: VMware pro 17 sets the virtual machine to start automatically when the host is turned on.

Setup steps

The steps to set up the virtual machine to start automatically in VMware Workstation 17 are as follows:

1. Open VMware Workstation 17.

2. Click Configure to automatically start the virtual machine in the left navigation bar. Then select the virtual machine to be started automatically and configure the startup sequence, and click OK.

3. Set up the automatic startup service.

Open the Task Manager, click on Services, find VmwareAutostartService, right-click and click Start.

Right-click the service and click Open Service.

Find the VMware Automatic Start Service, right-click and click Properties. Then change the startup type to Automatic in General and click Apply.

Then click Login. The default is to log in with the local system account. If you need to log in with another account, click this account setting.

The difference between the "Local System Account" and "This Account" options in the "Login" settings

Windows服务的"登录"设置决定了服务在系统中运行时所使用的安全上下文。
这有两个主要选项："本地系统账户"和"此账户"。

1. 本地系统账户：如果选择这个选项，那么服务将以本地系统账户的身份运行。
这是一个特殊的账户，具有广泛的权限，包括在本地计算机上访问所有文件和注册表项。
不过，当需要通过网络进行交互时，本地系统账户通常被视为匿名账户。

2. 此账户：如果选择这个选项，你需要提供一个特定的用户账户的详细信息（用户名、密码等）。
服务将以该用户的身份运行，并拥有该用户的权限。
这对于需要在网络上进行身份验证或需要特定权限的服务来说非常有用。

总的来说，选择哪种登录类型取决于服务需要执行什么样的任务以及服务需要多少权限。
但是，请注意，如果给服务提供过多的权限可能会带来安全风险。
因此，在配置服务时，应尽量遵循最小权限原则。

We require that our Vmware virtual machine must be very domineering, so I set it to log in with the local system account by default.

The meaning of the "Allow service to interact with the desktop" option under the local system account login option

Under the local system account login option, there is an option to allow services to interact with the desktop. Regarding this option, the explanation is as follows:

"允许服务与桌面交互"这个选项，如果被选中，
将允许运行在本地系统账户下的服务在用户桌面上创建窗口或对话框，从而与用户进行交互。

例如，一些服务可能需要显示错误消息、警告或其他类型的通知，或者需要用户输入一些信息。
在这种情况下，就需要选择"允许服务与桌面交互"。

然而，需要注意的是，该选项可能会带来安全风险。
如果一个恶意的或者被破坏的服务被允许与桌面交互，
那么它可能会利用这个权限做出一些不适当的操作，比如展示误导性的信息或者收集用户的输入。
此外，由于服务和用户桌面在不同的会话中运行，所以有时候即使选中了这个选项，
服务也可能无法正确地在用户桌面上显示窗口或对话框。

因此，一般建议只有在确实需要并且了解相关风险的情况下，才应选择"允许服务与桌面交互"。

It's a bit risky, so we won't check it.

4. Test auto-start (successful) (exclusively locking this profile failed. Another running VMware process may be using the profile)

We restarted the computer directly. After starting, we opened Vmware and found that the virtual machine did not start?

When we click to start the virtual machine, an error message will appear:以独占方式锁定此配置文件失败。另一个正在运行的 VMware 进程可能正在使用配置文件。

Click OK, and "Failed to open xxx" pops up:

But in fact, our virtual machine has been started successfully. I can ping the fixed IP of the virtual machine using the local console and it can be pinged successfully. This is the best proof. Testing various services in the virtual machine is also normal (skip here):

‌‍ᅟᅠ ‌‍ᅟᅠ ‌‍ᅟᅠ ‌‍ᅟᅠ ‌‍ᅟᅠ ‌‍ᅟᅠ ‌‍ᅟᅠ ‌‍ᅟᅠ