Boxes and Arrows: Remote Contextual Inquiry: A Technique to Improve Enterprise Software: "Remote Contextual Inquiry captures the computer screen of a person working with their version of the software on their own computer. To get started, the usability professional contacts the end user via telephone and web conferencing."
A misleading name: it has little or nothing to do with contextual inquiry. If only the information architecture profession would get over its enchantment with cool names (just look at the name of the profession for starters!).
The article states "In addition, interactions with supporting software also can be captured", which is probably why the authors think this is "contextual inquiry". But reading a bit further, they say "you can ask directed questions throughout or at the end of the session". They totally miss the master-apprentice relationship step, which is the defining characteristic of the contextual inquiry method. Good article, bad label, which is ironic considering the (assumed) profession of the author.
Using confusing names like this just hurts interoperability with related professions and existing research and understanding.
I am currently using similar techniques for remote exploratory usability testing (this term sounds less cool but conforms more to standard definitions). It works surprisingly well, considering you are remote. We are talking to doctors in their practice - a typical example of a hard to reach group.