PREREQS
http://www.microsoft.com/downloads/details.aspx?FamilyID=51d4a154-8e23-47d2-a033-764259cfb53b&DisplayLang=en
SQLXML 3.0 SP3
http://www.microsoft.com/downloads/details.aspx?familyid=13580cd7-a8bc-40ef-8281-dd2c325a5a81&displaylang=en
OMPM
 
http://technet.microsoft.com/en-us/library/cc178974.aspx
 
DEPLOY AND COLLECT SCANDATA FROM SCAN TOOL
[[C:\ompm\Scan]]
deploying offscan w/ sms
http://technet.microsoft.com/en-us/library/cc179228.aspx
 
[[C:\ompm\SCANDATA]]
collect logs from each client, (using offscan.exe /p /d)
 
PROVISION DATABASE
[[C:\ompm\Database]]
prepare the sql db
CreateDB.bat <ComputerName>\<SQLServerName> <DatabaseName>
// CreateDB.bat COMPUTER1\SQLEXPRESS OMPM001
 
IMPORT DATA INTO DATABASE
[[C:\ompm\Database]]
and import the client logs
this is made up of importing data files..
ImportScans.bat <ComputerName>\<SQLServerName> <DatabaseName> <PathToLogFiles>
 
And using the Import OMPM File Scanner to import action files into the database
ImportActions.bat <ComputerName>\<SQLServerName> <DatabaseName> <PathToLogFiles>
http://technet.microsoft.com/en-us/library/cc179204.aspx
 
To obtain help for this command, type the following at a command prompt: ImportScans.bat /? or ImportActions.bat /?.
 
PRODUCT REPORT
[[C:\ompm\Report]]
now analyse the data
double-click OMPM.accdr. Click Yes at the security prompt.
http://technet.microsoft.com/en-us/library/cc179165.aspx
 
 
FILTER REPORT TO CREATE MAP OF UPGRADE STORY
filter results by column "Error Description" does not equal to.. "File Type Not Supported by OMPM Deep Scanner."
look for "1307
 Linked workbooks in the file
 Linked workbooks are indentified to help identify upgrade issues. The path to the linked workbook and the number of occurrences are identified. Linked workbooks will have different extensions when converted to the Office Excel 2007 file format."
 
are examples of filtering the report.
 
USING REPORT TO MAKE CONVERSIONS
http://channel9.msdn.com/wiki/officedeployment/ompmv1/Default.aspx#Mode=Edit?wa=wsignin1.0
http://channel9.msdn.com/Wiki/OfficeDeployment/OMPMHowTo/
http://channel9.msdn.com/Wiki/OfficeDeployment/OMPMOFC/
 
 
 
\=============================\
DATABASE RECOVERY STEPS
Delete and restore the OMPM database

At a command prompt, navigate to the OMPM\Database folder and type:
DeleteDB.bat <ComputerName>\<SQLServerName> <DatabaseName>
For example, if your computer name is COMPUTER1, the database server is SQLEXPRESS, and the database name is OMPM001, type the following at the command prompt:
DeleteDB.bat COMPUTER1\SQLEXPRESS OMPM001
 
At a command prompt, navigate to the OMPM\Database folder and type:
CreateDB.bat <ComputerName>\<SQLServerName> <DatabaseName>
For example, if your computer name is COMPUTER1, the database server is SQLEXPRESS, and your new database name will be OMPM001, type the following at the command prompt:
CreateDB.bat COMPUTER1\SQLEXPRESS OMPM001
 
Move all of the CAB files that are in the OMPM\SCANDATA\OMPMImported folder up one level to the OMPM\SCANDATA folder, or to another folder if you prefer.
Move all of the folders that are in the OMPM\ACTIONLOGS\OMPMImported folder up one level to the OMPM\ACTIONLOGS folder, or to another folder if you prefer.
 
At a command prompt, navigate to the OMPM\Database folder and type:
ImportScans.bat <ComputerName>\<SQLServerName> <DatabaseName> <PathToLogFiles>
For example, if your computer name is COMPUTER1, the database server is SQLEXPRESS, the database name is OMPM001, and your log files are stored in c:\OMPM\SCANDATA, type the following at the command prompt:
ImportScans.bat COMPUTER1\SQLEXPRESS OMPM001 c:\OMPM\SCANDATA
 
At a command prompt, navigate to the OMPM\Database folder and type:
ImportActions.bat <ComputerName>\<SQLServerName> <DatabaseName> <PathToLogFiles>
For example, if your computer name is COMPUTER1, the database server is SQLEXPRESS, the database name is OMPM001, and your log files are stored in c:\OMPM\ACTIONLOGS, type the following at the command prompt:
ImportActions.bat COMPUTER1\SQLEXPRESS OMPM001 c:\OMPM\ACTIONLOGS