Office 2007 breaks TIFF files extensions
On our test machine we had Office 2003 SP3 and TIFF files associated with:
C:\Program files\Common files\Microsoft Shared\MODI\11.0\MSPView
On installing Office 2007 SP1, the file association was gone; on opening the TIFF files, it prompted for an application to open the file with; I could associate it with Microsoft fax and image viewer but not mspview, as mspview gets removed in Office 2007 installation.
Does anyone know a way to fix this file assoiation issue post Office 2007 Install?
I tried copying these reg entries but this still does not open the files in mspview.
We have huge population using faxes and I just want to make sure users do not lose the ability to open faxes using mspview, and the TIFF file association does not break on installing Office 2007.
C:\Program files\Common files\Microsoft Shared\MODI\11.0\MSPView
On installing Office 2007 SP1, the file association was gone; on opening the TIFF files, it prompted for an application to open the file with; I could associate it with Microsoft fax and image viewer but not mspview, as mspview gets removed in Office 2007 installation.
Does anyone know a way to fix this file assoiation issue post Office 2007 Install?
I tried copying these reg entries but this still does not open the files in mspview.
We have huge population using faxes and I just want to make sure users do not lose the ability to open faxes using mspview, and the TIFF file association does not break on installing Office 2007.
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
sk
15 years ago
If you are able to restore the settings (with Open With) you should also be able to capture the settings. It could be that the other application restores the settings but that is something you have to check out.
Posted by:
anonymous_9363
15 years ago
As 'sk' says, it would be simple to capture the requisite registry data. Once you have all the relevant entries, you can add them to a custom MSP. You would then drop that MSP into the Office 2007 'Updates' folder, along with your other customisation patch files.
If you didn't want to go the patch route, you could take the registry data and add it via a script of some sort. How you handle that would obviously depend on your distribution method.
If you didn't want to go the patch route, you could take the registry data and add it via a script of some sort. How you handle that would obviously depend on your distribution method.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
