Hey Julia,
Here are some semi-random thoughts:
#1. OCI 6.4.0 and higher are all 64 bit only, so they must be installed on a 64bit Windows. However, it may be that 3rd party 32bit software will work fine on OCI (FYI, my experience is that a lot of HP CommandView EVA versions will not install on 64bit windows).
#2. I don't think that you should need to worry about 32 vs 64bit for Solutions Enabler. SE is cross platform, and I am not aware of any known issues using 64bit vs 32bit in client/server mode.
#3. I don't see the idea of an OCI Remote Acquisition Unit (RAU) in your options - this .msi will install a "SANscreen Acq" on the Windows server of your choosing - it simply needs to be able to *initiate* HTTPS connections to your OCI server. The RAU is a tool to make working around firewalls possible, as well as a way to reduce latency issues by pushing OCI acquisition closer to distributed devices
So, my thinking is:
Do you own Perform?
Do you want to collect Symmetrix performance?
If yes to both, you may want to stand up a new 2vcpu / 8 GB Windows 64bit VM - map gatekeepers to it as RDMs, and install the SMI-S enabled version of Solutions Enabler, and the OCI RAU software. Then, you can create an OCI datasource, living on the RAU where the connection type is "local".
The upside of this topology is it gets you out of Solutions Enabler version matching, as the OCI datasource has direct access to the Symms.
I have a global insurer that is doing a lot of their Symmetrix discovery this way, as they were having trouble managing Solutions Enabler versions, as well as not having the SMI-S enabled version of Solutions Enabler deployed.
Solutions Enabler is somewhat picky with regard to latency - if the ping time from the OCI server to the remote SolEnabler server is >= 15ms, you may see very slow OCI inventory acquisition times. Deploying a RAU into the remote site can eliminate this.
Matt