Kevin Remde's IT Pro Weblog
IT Pro Resources
TechNet EventsMicrosoft Security Response CenterMicrosoft Virtual AcademyKevin’s Evaluation Download Center
IT Pro Evangelist Blogs
Blain Barton Blain Barton's Blog@BlainBar
Brian LewisMy Thoughts on IT...@BrianLewis_
Dan Stolts IT Pro Guru Blog@ITProGuru
Jennelle Crothers TechBunny@jkc137
Kevin RemdeFull of I.T.@KevinRemde
Tommy PattersonVirtually Cloud 9@Tommy_Patterson
Yung Chou Yung Chou on Hybrid Cloud@YungChou
If you’ve been to one of our live TechNet Briefings this quarter, you probably learned about the Application Compatibility Toolkit. Well… they just released a new version 4.0 of the tool.
Download it here.
“The Microsoft Application Compatibility Toolkit (ACT) version 4.0 for Windows XP, including Service Pack 2, and Windows Server 2003 contains the tools and documentation you need to evaluate and mitigate application compatibility issues before deploying on these platforms. Tools include the latest versions of the Microsoft Application Analyzer that simplifies application inventory and compatibility reporting, the Internet Explorer Compatibility Evaluator that assists testers in locating compatibility issues with Internet Explorer on Windows XP Service Pack 2, and the Compatibility Administrator that provides access to the necessary compatibility fixes to support legacy applications in Windows.”
The tool is great especially if you want to fix LUA problems. The problem is, much of how you can use the other fixes in the Compatibility Administrator is so undocumented that they are usless. For exmaple, here is the documentation for the MoveINIToRegistry fix
"Applications may still be storing data in INI files instead of using the registry. This is a generic compatibility fix to move INI data into the registry. The compatibility fix is command line driven." OK, I understand its command line driven, I could have guessed that. But why does the doc not tell me what to put in the command line to tell Windows what INI I need remapped into the registry. Where do I tell it to map it to in the registry. The problem is, most of the tool is documented, or if you will, undocumented in this manner which makes most of the fixes impossible to use.