How To Troubleshoot Azure DevTest Lab Artifact Failures

One of the big selling points of the cloud is the ability to spin entire environments up, and tear them down again, on demand. We all understand this benefit, but how do you go about capitalizing on it? One specific challenge you may come across is needing to ensure that a specific PowerShell module, or third-party application, is available to be installed on virtual machines deployed into an Azure DevTest Lab.

But sometimes things don’t go to plan, artifacts don’t guarantee successful installation. And when this happens, you’ll need to know how to go about figuring out what went wrong.

In this snip, Josh demonstrates how to troubleshoot artifact failures in your Azure DevTest Labs.

Prerequisites include: An Azure account/subscription An Azure DevTest Lab An Azure VM in you lab… with a failed artifact deployment

In my Azure Devtest lab, I've been using artifacts a lot recently, but tonight have run into a bit of an issue with one of them on my lab artifact, virtual machine, so we can see here on my lab dashboard. Their particular VM has a status of running but if I click into it and then hidden to manage artifacts. I can see that of the four artifacts that have been applied to this virtual machine. One of them failed. That being there. Ed user to administrators group artifact, so for drill into that one, I can see a deployment message there that's not exactly. User friendly to read. But it ends by telling me to see the artifact. Results for details so in order to drill down a little bit further, and find out exactly why the artifact failed. Let's head back to my virtual machine. And I'll switch back over to its overview and let's go ahead and connect to it. So this will open up an RDP session as it's a windows VM and will connect to it like we normally would authenticating. And accepting the stuff Cup. Alright once we're all connected fire up windows Explorer and hit your C Drive. Here you find the packages directory and if we start drilling down into it through Plugins, then this custom script extension directory? Whatever the version numbers and then into status will see a number of status files. Here, one for each artifact that we have installed on the machine, so the one in question that we have interested in was the 4th one on the list. So it'll be this last status file so let's go ahead and open it. And the formatting of this isn't that much more user friendly. However, it is more complete so if we scroll along to the right and I can see here that the message that was returned from the artifact was actually attempting to add fake user to the administrators group, so I have a hunch that fake user might not actually exist and I should probably update the artifact. To actually target a real user and attempt to re apply. This particular artifact. So there was a look at how you can troubleshoot a failed artifact deployment. On Azure VM, thanks for watching.