Tier 1 machine LCS package deployment failing due to admin account getting locked

(1) Share

Report

Posted on by Daniyal Kashif

Hi,

We have a Tier 1 CHE which we use as our QA environment. We do package deployments through LCS on this environment. Initially, it was working flawlessly. However, recently the deployments were failing. The error we get is shown in the screenshot below

This is now a recurring problem. To mitigate this what I do is to ensure that every time user gets locked, I unlock the account. This way we are getting are deployments done however it is defeating the process of LCS deployments.

Is there a way to resolve this problem? How can I ensure the account doesn't get locked again and again?

All responses (3)

Answers (1)

Sort by

Suggested answer

Anthony Blake 3,226 Super User 2026 Season 2 on at

Like (2)

Report
Copy link

Link copied!

For a CHE I wouldn't waste much time investigating, redeploy. It's good practice to do occasionally anyway to keep software on the CHE on supported versions.
Verified answer

Jonas "Jones&q... 5,016 Most Valuable Professional on at

Like (2)

Report
Copy link

Link copied!

We had an issue at my previous job where our CHEs kept getting locked because hackers attempted to brute force the admin account passwords.
After you redeploy the environment, as Anthony suggested (since we don’t know the current state of the machine, maybe it's compromised?), I strongly recommend securing it properly.

Microsoft has a great guide on how to secure these VM's: https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/dev-tools/secure-developer-vm

But most importantly, restrict access to RDP to your own IP addresses.
Daniyal Kashif 49 on at

Like (0)

Report
Copy link

Link copied!

As Jonas suggested, restricting access to RDP to your own IP addresses has mitigated this issue.