Upgrading the QMX Base Framework (BFW) Version

To upgrade your Quest QMX BFW if you are running QMX in standalone (i.e. not failover) mode

1. Download the Quest QMX BFW from the Quest web site Trial Downloads to the Windows computer where QMX is currently running (you will need this in step 8 below).



2. Start the QMX Configuration Tool.



3. If you are using QMX in System Center Operations Manager, on the MOM/_GlobalVariables tab, unselect the g_boolAutomaticallyStartVirtualAgents and g_boolUseOpsMgrSingleton global variables (if they are selected) and click Save.



4. Restart the Windows Management Instrumentation service by clicking in the QMX Configuration Tool Main Menu bar, select Tools->WMI->Restart. A dialog will ask you if you want to restart the WMI process where the QMX dll is running. Select yes. Note that the QMX Configuration Tool will automatically close when you click the yes button.



5. Download the script named QMXBFW519_PrepUpgrade.js and save it.



6. From a DOS command window, run the following command to backup your QMX configuration files (*.xml): cscript QMXBFW519_PrepUpgrade.js backup



7. From the Start menu, navigate to the Control Panel |Add or Remove Programs and remove the current version of the Quest QMX BFW
   
   Note: Older versions of Quest QMX Base Framework are called "eXc Software eXctender Event Provider for non-Windows..."; newer versions are called "Quest QMX base framework for Windows...".



8. Extract the file from the .zip file you downloaded in step 1.
   
   • Double-click the extracted file (.exe file) to start the Setup wizard.
   
   Note: You must install the latest QMX BFW to the same drive/directory as the previous version so that existing Extensions will still work properly.



9. From a DOS command window, run the following command to restore your QMX configuration files (*.xml): cscript QMXBFW519_PrepUpgrade.js restore



10. Restart the dependent Windows services:
    
    
    
    • Right-click the My Computer icon on your desktop and select Manage.
    
    
    
    • Navigate to Services and Applications | Services .
    
    
    
    • Right-click Windows Management Instrumentation and select Restart .
    
    
    
    • If you are using QMX in System Center Operations Manager, right-click System Center Management and select Restart .
    
    
    
    • Close the Computer Management window.
    
    
    
11. If you are using QMX in System Center Operations Manager, unload the QMX BFW Operations Manager Management Pack from Operations Manager by running the powershell script in C:\Program Files\eXc Software\WMI Providers\nonWindows\MOM\OpsMgr2007\ExportMPDependencies.ps1. If you have created any overrides for QMX and stored them in the eXcSoftware.nonWindows.Dynamic Management Pack, you will need to manually recreate the overrides again. Note that this powershell script needs to be run on the Operations Manager Root Management Server (RMS). This script will export any Management Packs that have a dependency on the QMX BFW Operations Manager Management Pack to the folder C:\temp\MPs. It also removes all the QMX Management Packs from Operations Manager. Once the script finishes running, go into the Operations Manager Console->Administration View and click on the Management Packs node. Verify that Management Packs that start with the name eXcSoftware and QMX have been removed. Note, there is a small possibility that you may still see the eXcSoftware.nonWindows.Dynamic Management Pack listed. If so, it is now safe to remove it manually from Operations Manager.



12. If you are using QMX in System Center Operations Manager, load the QMX BFW Operations Manager Management Pack that comes with QMX BFW version 4,0,0,519. The Management Pack is located on the hard drive where QMX BFW was installed (see step 8 above) in C:\Program Files\eXc Software\WMI Providers\nonWindows\MOM\OpsMgr2007\eXcSoftware.nonWindows.mp.



13. If you are using QMX in System Center Operations Manager, load all the Operations Manager Management Packs that you exported in step 11 (in C:\temp\MPs), except: NOTE: DO NOT RELOAD THE eXcSoftware.nonWindows.Dynamic Management Pack. Failure to follow this instruction will result in poor performance of QMX.


14. Start the QMX Configuration Tool.



15. If you are using QMX in System Center Operations Manager, since you unselected the g_boolAutomaticallyStartVirtualAgents and g_boolUseOpsMgrSingleton global variables on the MOM/_GlobalVariables tab in step #3, re-select only g_boolAutomaticallyStartVirtualAgents and click Save . Note , you should not be using g_boolUseOpsMgrSingleton unless instructed by a Quest support engineer in QMX BFW 519.



16. If you are using QMX in System Center Operations Manager, wait approximately 3-5 minutes for the non-Windows Proxy Discovery to complete inside the Operations Manager Console.



17. If you are using QMX in System Center Operations Manager, re-start the Extension(s) manually if you chose not to check g_boolAutomaticallyStartVirtualAgents.



18. If you are using QMX in System Center Configuration Manager, you will need to download and upgrade all of your QMX SMS/ConfigMgr extensions.



19. If you are using QMX in System Center Configuration Manager, you will need to delete all of the non-Windows objects currently inventoried in ConfigMgr and re-inventory them (once step 18 has been performed).