We hope our FAQ section helps with any of the questions you might have, but if they don't please contact us. We'll make sure your query is added to the list so it might help someone else in the future.

    Questions...




Is AOK a product or service?
It is a product that automates the majority of the manual work done around application packaging/management.
Back to top

Where can I buy the software?
We are setting up a partner channel to supply the product. For more information contact sales@changebase.com
Back to top

Does AOK really get applications to work on Windows 7?.
Yes it does. We have carried out work with over 100 companies and find that on average 95% plus of applications that have problems working under Windows 7 can be sorted with AOK.
Back to top

How easy it to load AOK?
Simple. About 5 minutes should do it.
Back to top

Do I need to use all the AOK modules?
No. It is possible to use each module independently of the others. For example AOK Test-It will normally fit in at the early stage of a migration project and give you invaluable information about the compatibility of your application portfolio with the proposed target platform. AOK Fix-It can be used on any packaging project and can even add significant value if adopted part way through.
Back to top

What time savings will I make by using the AOK?
Obviously, this will depend to some extent upon the processes that you adopt but the savings are considerable both in terms of cost and time. For example a portfolio of 500 applications would normally take 10-15 man months of effort to achieve using AOK Test-It this is reduced to less than a day!
Back to top

How much training will I need to have to use the tools?
The AOK Test-It and Manage-It tools require little or no training. They are extremely easy to use and you will be producing reports within minutes. AOK Fix-It is simple to use but the training you require will depend upon your level of expertise as a packaging team. We are able to tailor a one day or two day course to your specific needs if required.
Back to top

Please describe the process for loading legacy setups, vendor MSI, various installation files and combinations thereof.
To import applications into AOK with the following formats, there is a single-step process of simply dragging a root/source directory on to AOK and pressing the “Load-IT” button:

  1. MSI’s (and any combination of MST’s (transforms) and MSP’s (Patches) are dynamically loaded with the source MSI package
  2. WSI, WSC, WSE and Wise Setup Executables
  3. Microsoft App-V (SFT) sequenced packages
  4. Symantec Virtualization Packages (SVS)
  5. SYSDIFF INF Installation Packages
  6. Microsoft SETUP Executables

For applications that are not shipped in this format; we have two options:

  1. AOK will create a custom loader for the client specific environment
  2. Using freely available tools (UNIEXTRACT) we can extract the installation information from application packages and then load into AOK

Back to top

How can large software portfolios be structured?
We have had the benefit over the past few years of loading several tens of thousands of applications into AOK (now over 200,000 packages) . The process is generally as simple as dragging the “root” or top-level application or distribution source folder onto AOK and then pressing the “Load-IT” button. The AOK multi-threaded software handles all of the directory traversals and will gracefully handle any exceptions.
Back to top

How can distributed teams share one instance of AOK?
AOK is designed to be used across multi-user environments with support for multi-user package loading, reporting and fixing. AOK supports a number of server configurations including local servers, remote servers, WAN configurations and Internet based connections. Each team member, installs an instance of AOK and then chooses to connect to a central or shared server. If a user requires exclusive access to a package, then he or she is able to “Check-out” the package for fixing or updating. Once the update process is completed, the package is then “Checked-in” and other users can fully access the package.
Back to top

To what extent will the tool be able to reflect my local packaging standards?
One of the great benefits of the AOK Quality Assurance Plugin module is that the client packaging and distribution standards can be documented, codified and then integrated into AOK for automated analysis and remediation. In our past experience, we or our cllients have been able to automate the vast majority of the their packaging standards including requirements for transforms, Self-Healing and multi-target/purpose packages.
Back to top


Can I automatically migrate from XP to Windows 7 if I use these tools?
Obviously when moving from one operating system to another there are many considerations and it is almost certain that you will want to implement and deploy your applications conforming to a set of standards that will differ from that of your previous platform. However, under test conditions we and members of our client base have remediated and successfully deployed whole portfolios of applications after remediating them using AOK Fix-It!
Back to top

What reports and fixes does AOK have with regard to UAC?
At present the AOK workbench software analyzes the installation and configuration requirements for compatibility and maintenance issues for Windows XP, Vista, Windows 7 and server 2008. Using our existing application dependency analysis infrastructure, the ChangeBase AOK product will deliver a number of run-time checks including file level "version lie" checks and internal or compile security manifests
Back to top

How do you deal with any Win2000->Vista migrations?
The ChangeBase AOK Platform Integrity and Best Practices reports and automated fixes are ideally suited for the migration from Windows 2000 platforms (desktop and server environments) as they automatically identify and remediate compatibility issues, security issues and packaging best practice issues in a single tool-set. The AOK tool-set is designed to manage the journey from NT4 systems onward to Windows XP (and SP2, SP3) and on to Vista, Windows server 2003, 2008, Windows 7 and virtualization platforms such as App-V and Citrix XenApp. The existing collection of Windows XP plugins can easily be expanded to cover the entire Microsoft redistributable list (Merge Modules) which would then deliver an enhanced "clean-up" process for each application package in preparation for deployment to Windows Vista or Server 2008. In addition, the ChangeBase AOK product supports the main formats such as MSI, MST, WSI. It now supports the importing and subsequent reporting of legacy Sysdiff files (INF files) and Wise script packages (WSE files) in the event that a customer does not currently have a complete MSI package portfolio.
Back to top

What sort of testing do you do for middleware technologies (Java, .NET framework, MSI, etc)?
A number of our clients and service provider partners have recently requested middleware dependency reports. The ChangeBase AOK client currently supports automated dependency analysis as part of the import process. Clients are able to generate their own middleware reports by simply loading the applications into AOK and right clicking to turn them into middleware reports specific to their own environment.
Back to top

How easy is it to maintain the database?
The ChangeBase AOK databases (both local and remote) are automatically created, configured and updated through the AOK client. Creating, repairing and renaming databases is as simple as "right-clicking" on each database "Tab" presented at the bottom of the main AOK tree-view. The AOK client also supports 2-levels of security enabling administrators to enable or disable functions such as create and delete reports or delete databases. This security functionality is made available on a database by database basis. This ensures that users may have full control over their private or local databases, and administrators are able to maintain control over their central or shared databases.

What about new application updates? How are they discovered and added?
The AOK product is delivered as .NET client-server application with all reports, fixes and updates delivered as discrete Plugin modules. All of the existing reports are within 20-60 Kb in size and can be easily downloaded from the ChangeBase secure portal. In addition, all database and patch updates are made available in the CBP file format which enables easy database-by-database updating and control.
Back to top

Is this a pre sales tool to help win consultancy services?
As a technology platform, the AOK product is not intended as a pre-sales tool for later sales and consultancy services but is designed to easily integrate into a customer's existing processes and platforms and to support our service provider partners in simplifying and reducing the cost of Vista migrations and on-going application management services.
Back to top

What plans does ChangeBASE have for localisation support?
We currently have not officially tested AOK running under the localised settings of other regions supported by Vista/Windows 7. However, we have informally tried running it under different localisation settings and it appeared to work. In terms of supporting the same localisations in AOK that are supported under Vista, this is not on our roadmap but would not be seen as an insurmountable issue were it to be seen as of strategic advantage.
Back to top

What is our support model?
We will be selling our product through partners who will provide first line global support on AOK to their clients. We have an accreditation process to ensure they will have the appropriate skills in place. We will provide second line support to our partners.
Back to top

Can we create client specific rule-sets?
For simple and medium checks and minor additions to existing Plugins, yes - you can modify and create your own Plugins via the built in plugin generation wizard. For more complex business logic issues, you may need our assistance initially unless you have skilled SQL developers in which case you will be able to write your own more complex plugins.
Back to top

How would it reduce manual testing?
It is estimated to reduce manual testing by between 50-90%. The product can adapt to even the most unique environment by allowing you to create your own rule sets and add to it, increasing the effectiveness of the tool.
Back to top
How does the Core Application Scan module work?
It takes the MSI and converts into a rule format and checks it against all the other selected applications (MSI's). Customers have found that this reduces the traditional conflict analysis using Wise or InstallShield from 4 hours per applications down to minutes.
Back to top

How does the Complexity Analysis module work?
It analyses the files and custom actions of the application and categories them from Green (easy), Amber (medium) to Red (complex). It contains algorithms which you can customize to what you think will be easy, medium and complex applications. We will provide plug-ins; it takes approximately 1 day to create plug-ins.
Back to top

What about Citrix support?
The ChangeBASE WorkBench tool-set is an essential component of the Citrix (streamed and hosted) packaging and deployment process. Using the WorkBench software, each application is analyzed for compatibility and best practice compliance ensuring that each application installs and functions correctly on the Citrix and Terminal Service platform. In addition, as patches are continuously released by Microsoft, ensuring that Citrix servers are regularly updated raises the issue of change impact assessment on a complex system with hundreds or thousands of users. Using the ChangeBASE Workbench tool-set changes to Citrix delivered applications reduces risk, facilitates security compliance, and delivers faster application deployments.
Back to top

Does the Citrix Virtualization report pack report on issues with packages being installed in a multi-user environment?
There are a number of compatibility issues that applications may experience with Citrix including:

  1. Device or Kernel Drivers: Some Device or kernel drivers may not function correctly when shared through Citrix. In addition, Citrix application isolation environment will not isolate these files.
  2. Windows Services: Some applications install and rely on a Windows service (except Microsoft Installer (MSI)) to function correctly. Compatibility issues resulting from such applications may not be resolved using application isolation.
  3. Windows Class Names or Window Names: If the incompatibility is the result of Windows messages being used as inter process communication (IPC) mechanisms, Citrix presentation may not be the optimal solution.
  4. Registry or Application Objects that do not Link to USER32.DLL: An isolation environment does not resolve compatibility issues caused by applications that do not link to User32.dll.
  5. DCOM: Citrix application presentation may cause compatibility issues with DCOM applications. Unfortunately, Citrix application isolation does not resolve compatibility issues caused by applications that rely on Distributed Component Object Model (DCOM) to function correctly.
  6. IP Addresses: Application isolation cannot resolve compatibility issues that occur because all instances of an application running on Presentation Server share a common IP address.
  7. Installers that Require a Restart During Installation: If an application installer requires a restart during installation, it may not install correctly into an isolation environment. Removing or renaming files during a restart after an install or repair operation is also not supported.

These compatibility issues apply to the following versions of Citrix:

  • Presentation Server 4.0 for Microsoft Windows 2000
  • Citrix Presentation Server 4.0 for Microsoft Windows 2003
  • Citrix Presentation Server 4.0 x64 Edition
  • Citrix Presentation Server 4.5 for Windows Server 2003
  • Citrix Presentation Server 4.5 for Windows Server 2003 x64 Edition

The combined AOK Application WorkBench and Virtualization pack can identify these issues and in some cases, provide automated remediation's where applicable. With specific reference to registry issues, the AOK Core Application Scan is an integral element of the Citrix packaging and deployment process. Through the automated identification and remediation of application conflicts at the registry and file level, registry issues, conflicts and compatibility issues can be minimized. Therefore reducing the requirement for the Citrix Application Isolation process with it's associated development overhead and compatibility issues.
Back to top

Can AOK help me Virtualize my applications?
The answer to this is definitely. Whether your intended destination is AppV (formerly Softgrid) SVS or another virtualisation target, AOK can assist in testing and readying your applications.

When you wish to virtualize an application you will still need to get it working on the target host platform. For this you would run it through the AOK best practice, platform integrity, ICE and potentially Quality Assurance reports and automated fixes.

The next step would be to perform the AOK middleware checks to identify any dependant middleware that would need to be deployed in the same bubble as the application.
Having made sure that the application will work in the target environment (be that XP, Vista or Windows 7) you need to make sure that it will co-exist harmoniously with the other applications that will be virtualized with it. To ensure this you would use the AOK Core App Scan technology to identify and automatically remediate any inter-application conflicts.

Once your application has been prepared for a "clean" deployment it can then be tested using AOK's Virtualize-IT suite to identify any potential remaining issues that would prevent it from working successfully in a virtualized environment.
Back to top

Why do some Packages fail to load?
There are four main steps to follow when an application fails to load or fix:

  1. Read the log file to look for issues
  2. Check if the app loads into ORCA and/or WISE
  3. Does the app have its required files - eg external CABs
  4. Does the app install on your current version of version of windows

    FURTHER SPECIFIC CHECKS ARE AS FOLLOWS:
  1. Check the Log file first, this will give an indication as to why the package loading failed
  2. Non-supported package type: Supported package types: MSI, MSP, MST, SFT, WSI, WSE, IPF, OSI, SOE renamed as MSI, MS Executables, REFWI, INF
  3. Attempted package load with incorrect transform file: Ensure that you can open the MSI in Orca and apply the associated MST file. If you are not able to in Orca, you can suppress the Transform validation flags and errors in the Options menu within Orca. If the package loads now that the validation flags and errors are switched off, then you should be able to check the "Suppress Transform Validation Errors" within the Options menu in AOK to load the MSI with the MST. If the MSI and MST combination will still not load then try the MSI by itself
  4. Duplicate package: Any duplicate packages will be marked as such when you hover over the Red Cross icon in the issues column and this information is stored in the Log file
  5. Invalid Media table entries: Check the msi Media table entries in Orca. Invalid sequences, duplicate cab names and other invalid msi entries can all cause AOK to fail to load. (if a transform is being applied - remember to apply the transform in orca too) - invalid media table directives may cause AOK to fail during load. It is recommended that you get the correct source media to resolve this issue
  6. Licensed number of packages exceeded: you will have an error message advising you of this. In this case, contact your ChangeBASE Account Manager or Technical Contact to arrange for your license to be updated
  7. Security settings preventing package load: Verify the Security Tab within the Options menu to ensure that the Add Package option is NOT checked on.

Back to top


Why do some Packages fail to fix?

  1. Check the Log File: If the error message relates to a CAB or media file check that the media file actually exists in the specified location. See point 8 below
  2. Package in use: Check that the package is not in use or opened by a package editing tool such as Adminstudio or Wise Package Studio or open in Orca. It may be accessed by an editing tool on a Virtual Machine or RDP session, so ensure that you have confirmed this not to be the case
  3. Package or folder set as read-only: The package itself or the package folder may be set to read-only. Ensure that you have the correct permissions to write to the folder and to make changes to the MSI by creating a backup of the MSI, saving it into the same folder and then editing it and saving the changes
  4. Package is no longer accessible: The package may have been renamed or moved, or the network connection required to access the package may no longer be available, please check this
  5. Package in incorrect format: The package may be an MSM renamed as an MSI or of a format that doesn't have the minimum MSI tables required for it to run as an installation file. Check the package format in ORCA and if in doubt, try to install the package. If you cannot install it then you should not be running it through AOK. You should gather the current live instance of the package from its Deployment Source location.
  6. Plugin and hotfix versions are not up to date: Your plugin versions may not be inline with the version of AOK or the hotfix version that you are using. Ensure that you are A. On the latest version of AOK and B. That you have all of the latest versions of the plugins downloaded from the Upgrade Server. If you work in Offline mode, request your latest plugin pack from your ChangeBASE contact / Support
  7. Can you open the package in Orca and/or Wise? If not, then there is an underlying issue with the package and you can assume that it is not the current live and installable release and therefore not a suitable candidate for reporting and fixing
  8. Does the package have all of its required files? E.g external or internal CAB files and/or uncompressed source files. To verify this, try to install the application if the installation does not complete due to missing files, you need to go back to the live deployment source and copy down the complete source media
  9. Plugin not working correctly for this package: There may be a peculiarity in the package that is not allowing the fixing script to run correctly.

Back to top

Why do I sometimes get a fix failure message?
It is important that you maintain you copy of AOK Workbench with the latest published versions of the AOK Workbench it's self, the latest Hotfixes, and the latest published plugins. Hotfixes are always backwardly compatible so keeping up to date is the right thing to do. Some plugins will require the latest Hotfix to work correctly.
Back to top

How do I multi select items in the tree view?
To select a block of items...
select the first item in the list, hold down the Ctrl Shift and select the last items in the block. Still holding down the shift key, right click on the last item in the list to get the context menu..

To select any discrete set of items...
select the first item in the list, hold down the Ctrl Key and right click on each item in the set. The context menu will display for each item as you click it.
Back to top

Why does my context menu not show the actions I expect when I right click?
The context menu shows only those actions that are applicable to ALL the selected set of items. If you have a mixture of packages & transforms etc all the available options may not apply.

How do I use the Vista - Install Logic Scan?
This plugin assesses and identifies the install conditions it feels may be in error. It presents the user with a description of the condition and a "fix it" check box to allow the user to remove the condition if, on inspection, it requires removal.
Back to top

Why can I not stop AOK applying an existing transform to an msi when fixes are applied?
When applying fixes, AOK will either make the changes by generating transforms (MSTs) or by directly modifying the MSI depending on the selected settings.

If a pre-existing MST has been applied to an MSI using AOK, and the option is selected to make changes in the MSI then the MST changes will be rolled into the MSI along with the newly generated fixes.
Back to top

What can I do if the Legacy Help File plugin fix fails to work?
The majority of our customers install this hotfix: http://www.microsoft.com/downloads/details.aspx?FamilyID=258aa5ec-e3d9-4228-8844-008e02b32a2c as part of their Windows 7 build which adds in the engine so that it works in the same way as in Windows 95 to Windows XP.
 
The WinHelp engine was removed from Windows Vista for a couple of reasons; it had not been updated for many years and its appearance and functionality are very dated, it also poses security vulnerabilities (see http://aokcompat.blogspot.com/2010/03/i-often-get-asked-about-why-microsoft.html )
 
The risk involved in installing the hotfix in a corporate environment can be mitigated by blocking HLP files at the firewall and by only installing trusted software. Our plugin fixes the majority of packages and maintains the security of the environment by associating HLP files with a private copy of the help engine.  As it is not installed on a global case it is not available to internet explorer, preventing the attack vector in the link above.
 
Some programs do not support our fix because of the way that they launch the help files.  The help files, you will find, are not located in the same folder as the EXE file that is calling them.  The simplest solution to maintain the security provided by our fix without globally installing the help engine is to place a copy of the HLP file in the same folder as the EXE. This can be done in the package by using the DuplicateFiles Table.
Back to top