Category Archives: DevOps Project

Errors in Configuring Test Controller on a Domain Controller Machine

In the test controller configuration tool, you might see the following errors, when you install the test controller on a domain controller machine:

  1. Failed to add Administrators group to TestTeamControllerAdmins group. The configuration log file contains an exception “Could not add WinNT://BUILTIN/Administrators to group. Exception: System.Runtime.InteropServices.COMException (0x8007056C): A new member could not be added to a local group because the member has the wrong account type”  test1
  2. Aditionally, if your service account is Network Service, you might see an error: “Failed to Configure ACL”  The configuration log file contains an exception “Systems.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. —> System.Runtime.InteropServices.COMException: A new member could not be added to a local group because the memeber has the wrong account type”

Continue reading

Good habits for continuous value delivery.


One of the best practices in Software Engineering is to perform short iterations to give to the clients functional software that can be released at any time so they can give us adequate feedback about the tasks and requirements that had been completed, in this agile development environment we create a continuous improvement cycle. Nothing is prescript because it depends on the business but I found this brief article at about good habits to reach a continuous value delivery state I recommend you to read it as can be useful to get another perspective. These five habits are:

Think beyond the code: The service to the client is not restricted to code, to create a good user experience we need to think a little more (Configuration, architecture, documentation, designs, and interfaces)

Automate: Vital part to continuous value delivery, giving testing, build and deploy faster, also giving the developers fast feedback about their changes. It let us fix the problem before it get to the customer.

Make everything visible as your team needs it: “Improved visibility leads to increase quality as well”. If we can see the full process is easier to reduce any potential issue.

Track every change: As we told in last point, if we can trace every change we have control of the software. Its one of the best practices.

Put all in one place: Work in one repository, “A “Single source of truth” should be your truth.”

You can found the complete article here: