“The product cannot be installed on this machine since it seems to be a domain

What a start to 2009!!! – the above dreaded message when trying to (in this case)
install BizTalk RFID on a DC.
For me – this happens quite a bit, as I’m building up a proof of concept, a demo,
something to show and present with.

I alwaysalways.forget to install BizTalk RFID bits before I promote to a DC (this
technique can also cause security acct issues after the machine has been promoted
to a DC – depends on how the authentication is setup etc)

NOTE: BTW – Installing BizTalk RFID on a DC is NOT SUPPORTED (had
to put that one in their – keeps both sides happy)

For love or money I’ve bounced this question around for a while and come up empty,
untiltoday!!! Niklas Engfelt a senior MS support engineer came to my rescue (he
famously provided those thoughts from left field which were on the money! Big thank
you Niklas)

He suggested grabbing Orca from the Platform SDK and having a browse
through – I’d used HEX editors, disassembled files, attached process monitors during
installs and looked through any config file with a fine tooth combbut I’d never tried
a MSI Editor.

The steps to Enlightenment: (changing the installer validation conditions)

  1. Grab a download of Orca
    from here (I didn’t have the platform SDK currently installed and wasn’t about
    to install 1.2 GB worth either) and follow default install prompts.
  2. If you haven’t done so already copy the RFID_x86 or RFID_x64 folders
    off the install media to a temp folder nearby (note: sometimes on Win2K8, the system
    prevents copied files from being accessed until an admin comes along and says ’these
    are ok’ by going into File->Properties on each file. It’s weird I know, but I get
    it every now and then)
  3. Locate the RFIDServices.msi under the RFID folder and you’re ready
    to go.
  4. Launch Orca and open RFIDServices.msi to get something
  5. Under the Tables Column select LaunchCondition and
    drop the 2nd Row as follows:
  6. Drop the Row and Save the MSI file again.
  7. Run Setup.exe as per normal.

Oh what a sweet day!

p.s. I’m sure you’d be able to employ this technique onto other MSI’s causing grief.