In the test controller configuration tool, you might see the following errors, when you install the test controller on a domain controller machine:
- 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”
- 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”
Emmanuel Buch, a team member is wondering how to link a unit test with a test case set from the MTM, for automated testing. Because as you can see in the picture can not be attached.
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 perforce.com 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: http://www.perforce.com/successful-continuous-delivery
If you’re interested on integrating TFS with SCOM definitely should see this Brian Keller post.
He has included a hands on lab demo that shows how to monitor an ASP.NET application and raise alerts based on SLAs.
Since we are starting the implementation of the Microsoft Operations Framework to guide us on the ITIL process a memeber team found the IT Pro QuickStart Kit at this link
It’s a great package full of helpful information, specially MOF 4.0 mindmaps.
What do you think about this?
So Rene a team member found a great blog from Ricky Gao where he shared a lot of knowledge on the installation and configuration of System Center Tools. The team recommends you to check it out!
Here is the link:
If you are interested in knowing the benefits that implementing ITIL can bring to you, check the next link:
The Information Technology Infrastructure Library framework is designed to standardize the selection, planning, delivery and support of IT services to a business. The main goal is to improve efficiency and achieve predictable service levels.
It is a best practice that is currently detailed within five publications:
- ITIL Service Strategy
- ITIL Service Design
- ITIL Service Transition
- ITIL Service Operation
- ITIL Continual Service Improvement.
In this image you can observe ITIL’s evolution.