OMPM Scanner Deployment

---

Ways to deploy the scanner
*Deploy via SMS across a network
*Distribute via CD - for laptops that may or may not be connected to the network
*Self-help deployment
*Run from central server
*Just point it a file shares
All environments are different and a combination of the above might be best for you.

Just scanning file shares

If you just want to scan your network shares, simply list them out in the FoldersToScan section of offscan.ini. For example, our documents are stored at \\Server\Share\Documents and \\Server2\Docs.
All we have to do is add those location in our scan list:
...
FoldersToScan
Folder=\\Server\Share\Documents
Folder=\\Server2\Docs
...
Then, run the scanner. The scanner will retry a number of times specified in offscan.ini if there are flaky network connections.

Environment variables

Maybe you won't know until runtime which locations you want to scan or where you want to save the resulting log files. Environment variables can be used in the FoldersToScan, FoldersToExclude, and DestinationPath portions of the offscan.ini configuration file.
For example, consider this sample offscan.ini section:
...
FoldersToExclude
Folder=%temp%
...
The scanner will now skip over the location specified in %temp% (which is typically c:\Documents and Settings\ user name \Local Settings\Temp). You can create your own environment variables and use them similarily.
If the scanner cannot resolve an environment variable, it will treat it literally as a folder. In the example above, if %temp% is unresolvable the folder Working Directory \%temp%\ will be excluded (which probably is not too helpful).

---

OMPM Homepage