specify application on Mac to open Windows file by extension in VMware Fusion

Hi all

I've got an unusual predicament in that I need to be able to open .msg files from a Windows VMware Fusion instance within the Mac (host) environment.

On a proper Windows system, MS Outlook can open .msg (from Outlook on Windows) and .eml (from Outlook for Mac) perfectly; but on a Mac system, Outlook for Mac can ONLY open .eml files.  To open .msg files using Outlook for Mac, you need 3rd party software or it cannot be done.  Period.  For this I'm using OutlookMsgViewer.

The Fusion instance running Windows 7 has a Document Management System which stores all types of files - some of which are .msg files created by MS Outlook (on Windows).
If the .msg file is located on the Mac or in a location shared by the Mac (host) and Windows 7 (Fusion instance) and I open it by double-clicking it (on the Mac side), it opens using the 3rd party conversion program OutlookMsgViewer and then in Outlook for Mac perfectly.
Double-click the file while in the Document Management System (Windows application) or from the same shared location as mentioned above within Windows 7 on the Fusion instance and the file tries to open with MS Outlook (the Windows version) on the Mac side (which doesn't exist and is impossible).

Other files stored in the Document Management System on the Windows 7 Fusion instance or in the shared location (.jpg, .docx, .pdf etc.) all open perfectly on the Mac side because the VMTools program (in Windows) tells the Mac which application to open the files with.

Back on the Mac, OutlookMsgViewer is already set as the default application to open files with the .msg extension, so I believe the problem lies with VMware Fusion...  
While it can tell the Mac to open the Windows files, it cannot seem to do this based on file extension...   I want the .msg files to open with OutlookMsgViewer (a Mac application) and NOT MS Outlook.

I hope this makes sense.  I can add screenshots if needed.

Any suggestions?
Reece DoddsAsked:
Who is Participating?
Reece DoddsAuthor Commented:
An update on this...

I ran the command
/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/Support/lsregister -kill -r -domain local -domain system -domain user

Open in new window

and now the Microsoft Office Outlook -- Practice Evolve.app entry (in the above screenshot) has disappeared and I can now select OutlookMSG Viewer and it stays.

All .msg files opened from the Mac side are now opening correctly (first with OutlookMSG Viewer for conversion) then with Outlook For Mac, but if I try to open a .msg file from the Windows instance, I get the error
The document /file-path/location/file-name.msg could not be opened

fusion error
From the Mac OS X desktop, find a MSG file and hit Command+i to “Get Info” on the file
Click on the arrow next to “Open with:” to expand and access the default application list
Click the pull-down menu and choose “OutlookMsgViewer” from the list, or if it’s not visible, navigate to it by choosing “Other” and point to the OutlookMsgVIewer.app found in
With OutlookMsgViewer.app selected, click on the “Change All” button

Altered from: http://osxdaily.com/2011/10/31/set-default-pdf-viewer-mac-os-x/
Reece DoddsAuthor Commented:
I have done this, but the moment I click the change all button and continue, it changes back to Microsoft Office Outlook (the Windows version which doesn't exist)

I've even used RubiCode RCDefaultApp (http://www.rubicode.com/Software/RCDefaultApp/) to change it at a system preferences level and it doesn't help.
Reece DoddsAuthor Commented:
Due to a limitation of VMware Fusion, I don't think it is possible to do exactly what I'm trying to get done.  But the work around was to at least make the OutlookMSG Viewer application on the Mac the default program for .msg files (after a cleanup of the erroneous open with entries).
Now at least if the file is exported to the shared location from the Windows app (rather than double-clicked) and then double-clicked from that shared location on the Mac side, the file opens as expected.
Tedious - but better than nothing.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.