I would like to set up a file baseline for a specific folder. How do I accomplish this?
File baselines consists of three different components, each dealing with a different stage of the baseline process. The first component is the baseline configuration. The configuration (.bls) file specifies the directory and the file extensions the scan will target. The second component is compiling the .bls. The baseline contains file property information for each file extension specified in the configuration. The final component is comparison scanning. After the scan is complete, Application Management reports are used to view the results of the scan.
Creating a custom Baseline Configuration
A baseline requires a target directory and files to scan. Multiple directories and files can be set in the configuration. The following steps walk you through setting up a sample file baseline for '\Windows\system32'.
- On the Notification Server, browse to Start > Programs > Altiris > Solutions > Application Management > Files > Configuration Editor.
- In the file menu, select File > Open.
- Select default.bls, located in \NSCap\Bin\Win32\X86\Application Mgmt Solution\Programs.
- Edit the "Baseline" name and "Comments" sections to identify the baseline, that is "Windows XP System32 Baseline".
- Click the Extension tab and type the file extensions the scan will examine (without using the period) By default EXE, DLL and OCX are included.
- In the Directories tab under the Include these directories, remove all the directories removing the %windir% directory as the last one.
- In the Scan only these directories section type %windir%\system32.
- Click Add.
- Review the default file properties, these will be contained in the baseline.
- Save the baseline file with the new name, system32.bls.
- Save a copy of the baseline within \NSCap\Bin\Win32\X86\Application Mgmt Solution\FileBaselinePackage.
The baseline configuration now contains the directory, the file types and their respective file properties to examine.
Compiling a Baseline SnapshotAfter the baseline configuration has been created, the snapshot needs to be complied from a clean machine. The baseline snapshot contains the expected files and file properties.
- Browse to Configuration > Software Management > Application Management > Windows > Baseline Agents > File baseline client
- Select the Programs tab and click New.
- Configure the program as follows:
- Type in a name and description, for example, "Windows XP System32 baseline".
- Type in the following command line: baseline.exe /hidden /baseline system32.bls /output xml /generatebaseline /nserver /collect.
- Set Estimated disk space to 1200 KB.
- Set Estimated run time to 10 minutes.
- Set Terminate after 90 minutes.
- In the Starting window pull-down, select Hidden.
- In the Run with rights pull-down, select System Account.
- In the Program can run pull down, select Whether or not a user is logged in.
- Click Apply to save.
- Right-click Create local file baseline.
- Select Clone.
- Type in a new task name such as "Create Windows XP System32 baseline".
- In the program pull-down, select the baseline created in step 3.
- In the collections, choose the appropriate computer the snapshot should be compiled from.
- Disable the Schedule check box.
- Click Apply.
When the computer checks in, this task will compile the snapshot. A compiled snapshot contains the directory, the file types, and the respective file properties to compare against on other computers or the client computer it was taken from (over time comparison). This file is saved in C:\Program Files\Altiris\eXpress\Baseline and contain the same name as the baseline that is sent to the client. Save this file on the Notification Server in order for the next step to deploy the baseline. For example, save it in \NSCap\Bin\Win32\X86\Application Mgmt Solution\Custom baseline snapshots.
Setting up a Comparison scanThe last part of gathering data is to execute the scan on a single computer or collections.
- Browse to Tasks > Software Management > Application Management > Baseline Compliance Scan Wizard.
- Launch the wizard by clicking Run Baseline Compliance Scan Wizard.
- Browse to the baseline snapshot from Creating a custom baseline configuration, step 11, then click Next.
- Set the collection that the comparison scan will execute on.
- Set the schedule you want this task to run on, and then click Next.
- Review the task and then click Finish.
- Click close to return to the console. If you marked the check box to view the new task then the console will open the task. However the navigation pane will need to be manually refreshed.
When the clients check in with Notification Server they will pick up this task. The baseline client will then scan the target directory, Windows\System32, and compare the files and their properties to the ones gathered in the snapshot.
The application management reports are used to view the results of the baseline comparison results. The report will show if files are missing, different, or added. The most useful ones are Summary of all File Baselines, Different Version Files by Product, and Missing Files by Product.