Analyzing an installation log or finding out what have been done...

Welcome back Automation lovers,

last time the wizard showed you, how to find the DSM log files on a client. Probably you have opened up one of these logs. And, especially when you set the overall log level for your environment to "debug", you might thought: "Jesus, there is so much stuff written in there, i have really NO idea where to find some kind of useful information".
Or, if you're a real smart guy and used the find function of your preferred editor, you might found already something related to the package you have searched for.

This time, the wizard of os will show you how to quickly find the information you're looking for, the next time. This is quite easy, because every installer log file follows the same convention. So, no matter if you look for installations, performed by the service installer (service log file; NISRV_xxx) or by the auto installer (auto installer log; NIAI_xxx), the log file is almost the same. And therefore also the method how to find informations in there.

Auto Install Job List

First, we open the log file and search for the expression " run #" (there is a space before run!).

The result should look like this:

The entry "Job:Policyinstance.XXXX <Package Name>" indicates the client has received the command to install that package. if the searched package is NOT in this list, then it either is already installed, or not assigned to the target computer.

SW Set Job List (Optional)

It can happen, that the searched package is a part of an SW Set. In this case, only the SW Set itself will be displayed in the Autoinstall Job list. To check, which packages the SW Set contains, search for the expression "SWSetJobList".

If there are SW Sets assigned, it could happen that you have to click "Find Next" until you see the correct Job list. If there is a SW Set, the result should look like this:

Starting Installation

Whe it has been confirmed that the searched package should be installed on the target computer, now the package execution section needs to be searched. Open the find window and search for the expression "---->" (It is important to use exactly those characters; 4 Dashes and 1 Right Arrow)

Usually there is more than one package to be installed. Skip forward using the "Find Next" button. After the "Starting Installatiaon" section always follows the "Installation complete" section. Then the "Starting Installation" section of the next package comes and so on...
Below the "Starting Installation" entry, all commands of the package script are listed. If there is any kind of error, it will be listed here.

If you follow this guide, your friendly wizard of OS will be very happy, because now you can tell him where exactly the problem is, instead of just telling him, you have a problem...

3 ways to the log files...

Probably you know the following situation: You have assigned a package to a client and this bloody package gets red in the compliance view. And you really have no clue why it fails. So what you're doing? Right. You call your friendly FrontRange Consultant...

<You>: "Hey Wizard of OS, i have a problem with one of my packages. Can you help me?"

<Wizard of OS>: "Hi Dude, what's written in the log file regarding?"

<You>: "Errr, don't know...I...just thought there's an error and i better should call you..."

<Wizard of OS>: "Call me again, if you have parsed the log file...."

And you think: Damn, i totally have no idea where these Logfiles he's talking about, can be found...

the good news is, they are all together in a single place. You just have to know, how to get there. Currently i know 3 ways to open the log file location on a managed client. There are a few more possibilities, yes i know, but for this post, i assume you're logged on to physical or virtual client and then these 3 are enough.

• Oldschool - Drilling down the file system
• Expert - Let the DSM Agent do the work
• Comfort - Use the NetInstall Monitor

Oldschool - Drilling down the file system

This is the "classic" way, just drilling down the file system folders until you have reached your target. The problem with this method is, that it only works, if nobody has changed the log file location in the DSM config. If somebody has relocated the log file folder to somewhere else and you're not aware of it, you might need some time until you found the folder. If all is default, you'll find the log files here:

C:\Program Files (x86)\Common Files\enteo\NiLogs

Expert - Let the DSM Agent do the work
on my consulting jobs i see quite a lot of different environments. And i also often experience that the NiLogs folder has been relocated for whatever (hopefully valid) reason. Since i'm a lazy guy, i don't want to have a look for myself where this folder is, i can order the NetInstall Agent to do it for me... Sounds strange? No it isn't. All you have to do is to execute a file with some parameters and that's it!
Sounds easy? It is! Just open the "Run" box and enter the following command:

niagnt32 /start:logs

then it takes a few seconds and TADA a Windows Explorer window comes up showing you the content of the NiLogs directory.

Isn't that magic?

Well, there are a few more things you can do with this command. But this will be topics for future posts

Comfort - Use the NetInstall Monitor
the most comfortable method is to start up the NetInstall Monitor. It's a small tool for showing up detailed informations about the local client. These information can be very useful for troubleshooting. And one of the functions is it, to offer you a button that opens up the log file directory when you click it. No matter where it is located.

Hello Automation Lovers !

I'd like to welcome the crowd out there, desperately looking for some kind of (useful) information regarding to FrontRange DSM. My name is Markus Zierer and i'm CEO and Senior Consultant at MoveIT Solutions. We are focused on Client & Server Automation, mainly using FrontRange technology (enteo Netinstall, enteo v6, DSM 7 and Heat DSM). Usually i try to earn my coins as an DSM 7 certified Engineer offering Consulting services and from time to time, i do some trainings.

And this is mainly the motivation behind this blog. In all the trainings i did over the last years, i always got asked the same question: "Very good training, but i did some googling last night and i found almost NO information regarding the products. Can you give me some tipps where to look at?"
Well, unfortunately there aren't much places. There is the official FrontRange Connect forum, which is in English language and contains only few entries regarding DSM and all that stuff, and there is the  "old" enteo Forum, which is mostly in German language. beside of this there is almost nothing...

My plan is to change this situation, at least a little bit. The idea is to start releasing a regular series of posts, containing basic guides, tips & tricks, how to's and maybe some kind of whitepapers enabling the interested audience to extend their skills when working with FrontRange technology. Also i'd like to show the rest of the world the real power of "our" Software Management tool. And hopefully a few people will be interested to learn more about it.

Greets
Mac