With the complete onslaught of more and more people wanting to test/automate tasks with QTP I wanted to quickly document how to find out which version of QTP is installed on your XenApp Terminal server or Workstation. And I’d also like to add an opinion because I honestly believe QTP was a better product before Mercury Interactive was sold to HP. I just seems that anything HP purchases becomes part of their black hole and lost in never never land. Not to mention finding any support on HP’s website is completely impossible to navigate. Nevertheless – hey Mercury people out there, can you buy back QTP and run it the way it once was? Please please?

  • Now I’m done -here is how to quickly identify the version of QTP installed.
  • Version 8 was still owned by Mercury Interactive to you need to look for the QTPro.exe directory in ‘C:\Program Files\Mercury Interactive\QuickTest Professional\bin\QTPro.exe”.
  • Version 10 is branded HP and where the mess with license server and web downloads start. So does the complication of installing QTP for  multi user environments like Citrix Servers and Terminal servers.
  • For Version 10, you need to look in the following directory for QTPro.exe > ‘C:\Program Files\HP\QuickTest Professional\bin\qtpro.exe’

Very easy huh? I guess in ending – at least HP still gives props to Mercury Interactive (Israel) for the company name. And as far as I’m concerned Israel as a country has some solid developers and has advanced technology in may different sectors of information technology.

 

Its been quite some time since I’ve become upset at the quality of the Diskeeper product. Especially seeing they proclaim to do so many good things for the servers and computers on your network. And apparently they have a very good sales pitch as well because people, corporations and government entities are buying into the product. Is buying Diskkeeper a poor decision? YES! In fact, I don’t even believe disk keeper is as effective as free version of Disk Defragmenter which is part of your OS and always has been.

So in theory when you think of it – you are paying for a product that uses the same API as the free version of Disk Defragmenter but at an added cost and with our testing, Diskkeeper does not perform as well as Disk Defragmenter. Lets take a quick look at the following and we will prove to you why it is not worth it to purchase Diskkeeper based on the ability to properly move fragmented files and speed up drive access.

To preface the following information, we only stumbled on Diskepers inability to work as we originally anticipated when we ran the ‘analyze’ process located under storage/Disk Defragmenter via the computer management console and noticed the drive was completely fragmented.

Note: Diskeeper had been running on this server for roughly 3 years and we had assumed it was doing its job and managing fragmented files. Apparently we were wrong. Very wrong! And we suffered from sluggish disk performance as a result, and for quite some time.

  • The following is the results of fragmentation analysis on a Windows Server 2003 R2 with Diskeeper. You can see anything inred is fragmentation.
  • So we wanted to run a little test. Lets just click on the defrag now button via ‘disk defragmenter’ which is part of the the server OS. The results were completely interesting.
  • As you can see, there is very little fragmentation.
  • So what is the underscoring point? Based on our tests, Disk Degfragmenter outperformed Diskeeper completely. If there was any way to get your money back from Diskkeeper  or if you are considering just writing a script and defraging your assets via a scheduled task – I’d definitely go with the free version. Spend infrastructure money on something elese.

 

 

Not sure where all the issue is coming from out there. Apparently there are issues installing the latest version of VMware DiskMount on a Windows 7 x64 OS.  I guess it makes no sense if you think about it. Why would VMware botch something they have built their business around? Probably because they have expanded very well over the last several years and have very little direction with their code anymore and how to manage software updates appropriately. They probably also need to consider adding a more robust QA process with their release testing. Now that being said, here is a quick capture of how to properly install DiskMount on a Windows 7 64bit Operating System so you can finally open your much needed Windows 98 SE virtual disk file and add the needed drivers for sound and network!

  •  Start the installer by right clicking and selecting install as administrator
  • click next at the VMware DiskMount Utility installation wizard
  • At the license prompt, please make sure you fully read the entire agreement. Then print it out and file it away in the event you want to read it one evening or happen to be on the toilette and needed a good read!
  • After you click on “I accept the terms in the license agreement”, go ahead and click on next. Now note – we are not implying the fact you are going to accept the terms, but if you want to have the software installed to do your job, this is the only solution.
  • Assuming you clicked on next – you should be at a prompt allowing you to choose your destination folder. This is the important step. Your windows 7 64bit os is by default going to want to slap the code into the (x86) directory. Since this installer is dumb (thanks vmware) we are going to have to trick the installer and plop it where we would traditionally install only our 64 bit applications. So remove the ‘(x86)’ part and install VMware DiskMount to ‘c:\program files\vmware\vmware diskmount utility\’ and click on next when you are ready to continue.
  • courtesy of the install, you will be reminded that you need to click on the install button just in case you forgot to change something. make any last minute updates and click on the ‘install’ button when you are ready!
  • Once complete you will get a success message indicating everything was good. If you messed up the install path, you will get a message indicating ‘the wizard was interrupted before VMware Diskmount Utility could be completed’. To correct and properly install repeat the above steps and thoroughly read what I have typed this time!

 

© 2012 random technology [RT] technology documentation

Optimized by SEO Ultimate