320 likes | 540 Views
Application Compatibility Toolkit. Martin Žugec. Three-phase approach. Evaluate. Inventory Lab inventory Internet Explorer Compatibility Evaluator Global inventory Collector Windows Firewall Compatibility Evaluator (WFCE) DCOM Compatibility Evaluator (DCOM) Prioritize Test
E N D
Application Compatibility Toolkit Martin Žugec
Evaluate • Inventory • Lab inventory • Internet Explorer Compatibility Evaluator • Global inventory • Collector • Windows Firewall Compatibility Evaluator (WFCE) • DCOM Compatibility Evaluator (DCOM) • Prioritize • Test • Create must-fix list
Inventory • Setup a SQL database • SQL/MSDE • Gather required data • Collector or Compatibility Evaluators • Process logs to build reports • Transform .xml to SQL database
Collector • Collector is the basic tool to retrieve compatibility related informations from desktops • You can run Collector manually, using logon scripts or SMS 2003 • Collector is creating .xml files • .cab (75-150kb = 1MB)
General overview Merger Collector Workstation SQL Server
Collector – important parameters • /q – hidden mode • /u – collect username of logged in user • /x – do not compress output. (.xml -> .cab) • /o – output directory (server) • /f – output filename • Default is Computer.GUID.cab • /t – number of days
Collector – ini file • You can use .ini file instead of passing parameters every time. • You specify the .ini file by /i • Collect.exe /i \\server\act\ini\collector.ini
Collector – general informations • Network • Domain • Machine Name • Chassis Information • Vendor • Asset Tag • Serial Number • Operating System • Operating System Name • Build Number • Version Corrected Service Diskette number (a string representing the service pack installed for the operating system) • Major • Minor • Platform ID • Product Type • Service Pack • Windows Directory • System Directory • DirectX • Major • Minor • Version • Hardware • Memory • Processor • Video • Disk
Compatibility Evaluators • Aimed at specific compatibility problems • Specially designed for troubleshooting compatibility problems with XP SP2
Compatibility Evaluators • Provide feature-focused evaluation • DCOM Compatibility Evaluator • Firewall Compatibility Evaluator • Internet Explorer Compatibility Evaluator
DCOM Compatibility Evaluation • Global evaluation tool • Parameters • /o – output path • /f – output filename • /q – silent mode • /i - .ini file • DCOM detects only launch-permission issues, not runtime issues!
Firewall Compatibility Evaluation • Global evaluation tool • It is installed as service • Parameters • /o – output path • /f – output filename • /ct – completion time in hours ( < 999) • /q – silent mode • /clr – clear log files on exit (not recommended)
Internet Explorer Evaluation • Lab evaluation tool • Security features • Automatic Download Blocking • Bad Certificate ActiveX Blocking • Binary Behaviors Restrictions • LocalMachine LockDown • MIME Handling • MK Protocol • Object Caching Protection • Pop-Up Blocking • Windows Restrictions • Zone Elevation Restrictions
Internet Explorer Evaluation • Automatic Mitigation
Mitigation • Identify problem • Create solution • Test solution
Identify problem • Identify problem • Check Issue DB in Analyzer • Check last functional OS version • Try compatibility modes for that OS • Read symptoms in ACT Documentation • Application Compatibility Toolkit 4.1 Help -> Compatibility Administrator -> Compatibility Fixes • Use Trial&Error Approach • Visit Microsoft Newsgroups
Create solution • Fixes, compatibility modes and AppHelp messages are distributed in databases
Compatibility Administrator • Add other fixes and save as .sdb file
Create redistributable • You must apply compatibility DB (%WinDir%\AppPath\Custom) • Sdbinst \\server\act\db\TestDB.sdb • SMS2003 • FixPack (create SED file) • FixPack /vtest.sdb test.exe • Content • Collect.exe • FixInst.exe • Fxpakcnf.exe • <sdb_file>