It sounds a little funny, but this is actually an issue in the new millennium.  The Engyro Remedy connector leverages the COM / .Net API's from BMC and they are only executable in 32bit windows.

If your attending the Microsoft Management Summit this year, you'll hear our latest updates on the new MSFT branded versions being developed but in the meantime here is a workaround that I figured out to keep your Ops Mgr infrastructure running 64 bit with Remedy integration.

Given that this is a COM / .Net API issue we have to get those pieces of the connector to run in a 32bit context.  The API's are leveraged by the connector service itself for normal operations and the Web Config for setting up the relationship between Ops Mgr alerts and Remedy tickets.

You would think that the solution is to move the Web Config off the server, but Kerberos delegation issues aside (there's a work around!) it is actually the Engyro service that needs to run on a separate 32bit server.  In my test architecture I leveraged a SQL Reporting Services Server for this; you'll see why shortly.

This server should be running 32 bit OS, IIS and SSRS.  Install the Engyro connector here according to the instructions for running the connector on a server that is not the RMS.  I also recommend running the Ops Mgr Web Console here for sanity's sake, unless you run it on one of the other Management Servers to leverage 64bit IIS.  I don't recommend running it on the RMS because we haven't tested the web console running in a 32bit IIS instance on 64 bit OS.

Now, in order to get the Web Config to work, you first have to set IIS to run ASP 1.1 and 2.0 in 32bit mode.  This KB article will explain how to do this:  http://support.microsoft.com/kb/894435

Now that you've effectively set up IIS to run as a 32bit server, you can follow the Engyro install for separate Web Config and connector systems.

Once everything is installed, you will get to deal with all of the permission issues connecting to Remedy.  I'll have to blog this later, but the errors you will see are fairly clear that you are connected to Remedy, but it doesn't like your permission levels.  One carrot that I'll give you that isn't documented, is that you actually need two remedy accounts.

The Engyro connector service with Sub-Admin rights, along with field-level "change" permissions on the status form AND a second account (can be your test user) that has app-admin rights.  This second account is used as the credentials for the Web Config.

Send me questions if you need more info.