.jpg .gif .bmp file associations gone, upgrade from Office XP to 2

F

fbartrom

Your understanding is not correct. After the upgrade, .jpg .gif .bmp file
associations gone. Since Photo Editor from Office XP is being upgraded to
Picture Manager from Office 2003, these associations should automatically be
re-associated to Picture Manager. I am deploying to over 600 users and do
not want to manually create the associations for every user.

How do you configure the upgrade install to correctly and automatically move
the file association of .jpg, .gif and .bmp from Photo Editor to Microsoft
Office Picture Manager.
 
F

fbartrom

Your understanding is not correct. After the upgrade, .jpg .gif .bmp file
associations gone. Since Photo Editor from Office XP is being upgraded to
Picture Manager from Office 2003, these associations should automatically be
re-associated to Picture Manager. I am deploying to over 600 users and do
not want to manually create the associations for every user.

How do you configure the upgrade install to correctly and automatically move
the file association of .jpg, .gif and .bmp from Photo Editor to Microsoft
Office Picture Manager.
 
F

fbartrom

Your understanding is not correct. After the upgrade, .jpg .gif .bmp file
associations gone. Since Photo Editor from Office XP is being upgraded to
Picture Manager from Office 2003, these associations should automatically be
re-associated to Picture Manager. I am deploying to over 600 users and do
not want to manually create the associations for every user.

How do you configure the upgrade install to correctly and automatically move
the file association of .jpg, .gif and .bmp from Photo Editor to Microsoft
Office Picture Manager.
 
F

fbartrom

Your understanding is not correct. After the upgrade, .jpg .gif .bmp file
associations gone. Since Photo Editor from Office XP is being upgraded to
Picture Manager from Office 2003, these associations should automatically be
re-associated to Picture Manager. I am deploying to over 600 users and do
not want to manually create the associations for every user.

How do you configure the upgrade install to correctly and automatically move
the file association of .jpg, .gif and .bmp from Photo Editor to Microsoft
Office Picture Manager.
 
F

fbartrom

Your understanding is not correct. After the upgrade, .jpg .gif .bmp file
associations gone. Since Photo Editor from Office XP is being upgraded to
Picture Manager from Office 2003, these associations should automatically be
re-associated to Picture Manager. I am deploying to over 600 users and do
not want to manually create the associations for every user.

How do you configure the upgrade install to correctly and automatically move
the file association of .jpg, .gif and .bmp from Photo Editor to Microsoft
Office Picture Manager.
 
F

fbartrom

Your understanding is not correct. After the upgrade, .jpg .gif .bmp file
associations gone. Since Photo Editor from Office XP is being upgraded to
Picture Manager from Office 2003, these associations should automatically be
re-associated to Picture Manager. I am deploying to over 600 users and do
not want to manually create the associations for every user.

How do you configure the upgrade install to correctly and automatically move
the file association of .jpg, .gif and .bmp from Photo Editor to Microsoft
Office Picture Manager.
 
F

fbartrom

Your understanding is not correct. After the upgrade, .jpg .gif .bmp file
associations gone. Since Photo Editor from Office XP is being upgraded to
Picture Manager from Office 2003, these associations should automatically be
re-associated to Picture Manager. I am deploying to over 600 users and do
not want to manually create the associations for every user.

How do you configure the upgrade install to correctly and automatically move
the file association of .jpg, .gif and .bmp from Photo Editor to Microsoft
Office Picture Manager.
 
F

fbartrom

Your understanding is not correct. After the upgrade, .jpg .gif .bmp file
associations gone. Since Photo Editor from Office XP is being upgraded to
Picture Manager from Office 2003, these associations should automatically be
re-associated to Picture Manager. I am deploying to over 600 users and do
not want to manually create the associations for every user.

How do you configure the upgrade install to correctly and automatically move
the file association of .jpg, .gif and .bmp from Photo Editor to Microsoft
Office Picture Manager.
 
D

Dana Brash [MSFT]

Hello,

Thank you for your prompt response, and I apologize for my delayed response
due to the weekend. I also apologize that I did not fully understand your
original concerns and provide a more thorough answer. I have performed
further research to more thoroughly answer your question.

When Office 2000 or Office XP is upgraded to Office System 2003, the
graphic file extensions associated with Microsoft Photo Editor are removed
even if the extensions have been re-associated with a different graphics
file handler. Although Office 2003 installs the Microsoft Office Picture
Manager, it does not automatically associate the graphics file extensions
during the installation.
Picture Manager offers the user a choice during the first run by the user.

Unfortunately, this is by design. It is a limitation in Windows installer
because it does not know the file association to keep it if it is
associated to something else.

There are several options to manage this scenario. Please choose the
option that best applies to your needs.

Option 1:
You can re-install Photo Editor on all the systems. This is essentially
rolling out an office installation through current methods and only
installing the Photo Editor component. To re-install Photo Editor please
follow the instructions in this link:
http://support.microsoft.com/?id=817095

Option 2:
You can include the necessary registry settings in your MST by adding the
keys in CIW to associate the graphics files with the appropriate
applications. I have generated a sample script for you below. You should
generate your own script following these steps:

1. On a system that is configured with appropriate file associations,
export the following registry keys to file:
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExt
s\.bmp
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExt
s\.gif
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExt
s\.jpe
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExt
s\.jpeg
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExt
s\.jpg
* you can of course add the keys for any other image files you want to
associate as well
** to export the keys, open regedit, browse to the key, right click and
choose export


2. Copy the resultant .reg file information into one .reg file, including
the "Windows Registry Editor Version 5.00" line only once at the top.

3. In CIW, on screen 12 of 24, Import the .reg file created in step #2.

Here is a sample file that I created from my system:
++++++//BEGIN FILE CUT BELOW LINE\\++++++++++++

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileEx
ts\.bmp]
"Application"="ois.exe"

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileEx
ts\.bmp\OpenWithList]
"a"="mspaint.exe"
"MRUList"="dcba"
"b"="iexplore.exe"
"c"="shimgvw.dll"
"d"="OIS.EXE"

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileEx
ts\.bmp\OpenWithProgids]
"Paint.Picture"=hex(0):

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileEx
ts\.jpg]

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileEx
ts\.jpg\OpenWithList]
"a"="shimgvw.dll"
"MRUList"="ebadc"
"b"="mspaint.exe"
"c"="iexplore.exe"
"d"="msnmsgr.exe"
"e"="OIS.EXE"

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileEx
ts\.jpg\OpenWithProgids]
"jpegfile"=hex(0):


[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileEx
ts\.gif]
"Application"="ois.exe"

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileEx
ts\.gif\OpenWithList]
"a"="shimgvw.dll"
"MRUList"="ebadc"
"b"="mspaint.exe"
"c"="iexplore.exe"
"d"="msnmsgr.exe"
"e"="OIS.EXE"

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileEx
ts\.gif\OpenWithProgids]
"giffile"=hex(0):

++++++++++//END FILE CUT ABOVE LINE\\++++++++++++++++

Option 3:

If you have already rolled out the installation and would rather not
re-install office, you can publish a .bat file or implement it as a login
script to call the .reg file created above. The .bat file should include a
line to call the .reg with this syntax:
REGEDIT /S "\\servername\Sharename\name.reg"

Hope this helps!

Sincerely,

Dana Brash
Microsoft Online Partner Support

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
Business-Critical Phone Support (BCPS) provides you with technical phone
support at no charge during critical LAN outages or "business down"
situations. This benefit is available 24 hours a day, 7 days a week to all
Microsoft technology partners in the United States and Canada.

This and other support options are available here:
BCPS:
https://partner.microsoft.com/US/technicalsupport/supportoverview/40010469
Others: https://partner.microsoft.com/US/technicalsupport/supportoverview/

If you are outside the United States, please visit our International
Support page:
http://support.microsoft.com/default.aspx?scid=/international.aspx.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.


--------------------
Thread-Topic: .jpg .gif .bmp file associations gone, upgrade from Office XP
thread-index: AcUQfDxfDDroTTX1QPawpgjcTHsjow==
X-WBNR-Posting-Host: 64.1.44.68
From: "=?Utf-8?B?ZmJhcnRyb20=?=" <[email protected]>
References: <[email protected]>
 
D

Dana Brash [MSFT]

Hello,

Thank you for your prompt response, and I apologize for my delayed response
due to the weekend. I also apologize that I did not fully understand your
original concerns and provide a more thorough answer. I have performed
further research to more thoroughly answer your question.

When Office 2000 or Office XP is upgraded to Office System 2003, the
graphic file extensions associated with Microsoft Photo Editor are removed
even if the extensions have been re-associated with a different graphics
file handler. Although Office 2003 installs the Microsoft Office Picture
Manager, it does not automatically associate the graphics file extensions
during the installation.
Picture Manager offers the user a choice during the first run by the user.

Unfortunately, this is by design. It is a limitation in Windows installer
because it does not know the file association to keep it if it is
associated to something else.

There are several options to manage this scenario. Please choose the
option that best applies to your needs.

Option 1:
You can re-install Photo Editor on all the systems. This is essentially
rolling out an office installation through current methods and only
installing the Photo Editor component. To re-install Photo Editor please
follow the instructions in this link:
http://support.microsoft.com/?id=817095

Option 2:
You can include the necessary registry settings in your MST by adding the
keys in CIW to associate the graphics files with the appropriate
applications. I have generated a sample script for you below. You should
generate your own script following these steps:

1. On a system that is configured with appropriate file associations,
export the following registry keys to file:
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExt
s\.bmp
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExt
s\.gif
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExt
s\.jpe
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExt
s\.jpeg
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExt
s\.jpg
* you can of course add the keys for any other image files you want to
associate as well
** to export the keys, open regedit, browse to the key, right click and
choose export


2. Copy the resultant .reg file information into one .reg file, including
the "Windows Registry Editor Version 5.00" line only once at the top.

3. In CIW, on screen 12 of 24, Import the .reg file created in step #2.

Here is a sample file that I created from my system:
++++++//BEGIN FILE CUT BELOW LINE\\++++++++++++

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileEx
ts\.bmp]
"Application"="ois.exe"

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileEx
ts\.bmp\OpenWithList]
"a"="mspaint.exe"
"MRUList"="dcba"
"b"="iexplore.exe"
"c"="shimgvw.dll"
"d"="OIS.EXE"

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileEx
ts\.bmp\OpenWithProgids]
"Paint.Picture"=hex(0):

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileEx
ts\.jpg]

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileEx
ts\.jpg\OpenWithList]
"a"="shimgvw.dll"
"MRUList"="ebadc"
"b"="mspaint.exe"
"c"="iexplore.exe"
"d"="msnmsgr.exe"
"e"="OIS.EXE"

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileEx
ts\.jpg\OpenWithProgids]
"jpegfile"=hex(0):


[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileEx
ts\.gif]
"Application"="ois.exe"

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileEx
ts\.gif\OpenWithList]
"a"="shimgvw.dll"
"MRUList"="ebadc"
"b"="mspaint.exe"
"c"="iexplore.exe"
"d"="msnmsgr.exe"
"e"="OIS.EXE"

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileEx
ts\.gif\OpenWithProgids]
"giffile"=hex(0):

++++++++++//END FILE CUT ABOVE LINE\\++++++++++++++++

Option 3:

If you have already rolled out the installation and would rather not
re-install office, you can publish a .bat file or implement it as a login
script to call the .reg file created above. The .bat file should include a
line to call the .reg with this syntax:
REGEDIT /S "\\servername\Sharename\name.reg"

Hope this helps!

Sincerely,

Dana Brash
Microsoft Online Partner Support

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
Business-Critical Phone Support (BCPS) provides you with technical phone
support at no charge during critical LAN outages or "business down"
situations. This benefit is available 24 hours a day, 7 days a week to all
Microsoft technology partners in the United States and Canada.

This and other support options are available here:
BCPS:
https://partner.microsoft.com/US/technicalsupport/supportoverview/40010469
Others: https://partner.microsoft.com/US/technicalsupport/supportoverview/

If you are outside the United States, please visit our International
Support page:
http://support.microsoft.com/default.aspx?scid=/international.aspx.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.


--------------------
Thread-Topic: .jpg .gif .bmp file associations gone, upgrade from Office XP
thread-index: AcUQfDxfDDroTTX1QPawpgjcTHsjow==
X-WBNR-Posting-Host: 64.1.44.68
From: "=?Utf-8?B?ZmJhcnRyb20=?=" <[email protected]>
References: <[email protected]>
 
D

Dana Brash [MSFT]

Hello,

Thank you for your prompt response, and I apologize for my delayed response
due to the weekend. I also apologize that I did not fully understand your
original concerns and provide a more thorough answer. I have performed
further research to more thoroughly answer your question.

When Office 2000 or Office XP is upgraded to Office System 2003, the
graphic file extensions associated with Microsoft Photo Editor are removed
even if the extensions have been re-associated with a different graphics
file handler. Although Office 2003 installs the Microsoft Office Picture
Manager, it does not automatically associate the graphics file extensions
during the installation.
Picture Manager offers the user a choice during the first run by the user.

Unfortunately, this is by design. It is a limitation in Windows installer
because it does not know the file association to keep it if it is
associated to something else.

There are several options to manage this scenario. Please choose the
option that best applies to your needs.

Option 1:
You can re-install Photo Editor on all the systems. This is essentially
rolling out an office installation through current methods and only
installing the Photo Editor component. To re-install Photo Editor please
follow the instructions in this link:
http://support.microsoft.com/?id=817095

Option 2:
You can include the necessary registry settings in your MST by adding the
keys in CIW to associate the graphics files with the appropriate
applications. I have generated a sample script for you below. You should
generate your own script following these steps:

1. On a system that is configured with appropriate file associations,
export the following registry keys to file:
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExt
s\.bmp
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExt
s\.gif
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExt
s\.jpe
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExt
s\.jpeg
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExt
s\.jpg
* you can of course add the keys for any other image files you want to
associate as well
** to export the keys, open regedit, browse to the key, right click and
choose export


2. Copy the resultant .reg file information into one .reg file, including
the "Windows Registry Editor Version 5.00" line only once at the top.

3. In CIW, on screen 12 of 24, Import the .reg file created in step #2.

Here is a sample file that I created from my system:
++++++//BEGIN FILE CUT BELOW LINE\\++++++++++++

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileEx
ts\.bmp]
"Application"="ois.exe"

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileEx
ts\.bmp\OpenWithList]
"a"="mspaint.exe"
"MRUList"="dcba"
"b"="iexplore.exe"
"c"="shimgvw.dll"
"d"="OIS.EXE"

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileEx
ts\.bmp\OpenWithProgids]
"Paint.Picture"=hex(0):

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileEx
ts\.jpg]

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileEx
ts\.jpg\OpenWithList]
"a"="shimgvw.dll"
"MRUList"="ebadc"
"b"="mspaint.exe"
"c"="iexplore.exe"
"d"="msnmsgr.exe"
"e"="OIS.EXE"

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileEx
ts\.jpg\OpenWithProgids]
"jpegfile"=hex(0):


[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileEx
ts\.gif]
"Application"="ois.exe"

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileEx
ts\.gif\OpenWithList]
"a"="shimgvw.dll"
"MRUList"="ebadc"
"b"="mspaint.exe"
"c"="iexplore.exe"
"d"="msnmsgr.exe"
"e"="OIS.EXE"

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileEx
ts\.gif\OpenWithProgids]
"giffile"=hex(0):

++++++++++//END FILE CUT ABOVE LINE\\++++++++++++++++

Option 3:

If you have already rolled out the installation and would rather not
re-install office, you can publish a .bat file or implement it as a login
script to call the .reg file created above. The .bat file should include a
line to call the .reg with this syntax:
REGEDIT /S "\\servername\Sharename\name.reg"

Hope this helps!

Sincerely,

Dana Brash
Microsoft Online Partner Support

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
Business-Critical Phone Support (BCPS) provides you with technical phone
support at no charge during critical LAN outages or "business down"
situations. This benefit is available 24 hours a day, 7 days a week to all
Microsoft technology partners in the United States and Canada.

This and other support options are available here:
BCPS:
https://partner.microsoft.com/US/technicalsupport/supportoverview/40010469
Others: https://partner.microsoft.com/US/technicalsupport/supportoverview/

If you are outside the United States, please visit our International
Support page:
http://support.microsoft.com/default.aspx?scid=/international.aspx.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.


--------------------
Thread-Topic: .jpg .gif .bmp file associations gone, upgrade from Office XP
thread-index: AcUQfDxfDDroTTX1QPawpgjcTHsjow==
X-WBNR-Posting-Host: 64.1.44.68
From: "=?Utf-8?B?ZmJhcnRyb20=?=" <[email protected]>
References: <[email protected]>
 
D

Dana Brash [MSFT]

Hello,

Thank you for your prompt response, and I apologize for my delayed response
due to the weekend. I also apologize that I did not fully understand your
original concerns and provide a more thorough answer. I have performed
further research to more thoroughly answer your question.

When Office 2000 or Office XP is upgraded to Office System 2003, the
graphic file extensions associated with Microsoft Photo Editor are removed
even if the extensions have been re-associated with a different graphics
file handler. Although Office 2003 installs the Microsoft Office Picture
Manager, it does not automatically associate the graphics file extensions
during the installation.
Picture Manager offers the user a choice during the first run by the user.

Unfortunately, this is by design. It is a limitation in Windows installer
because it does not know the file association to keep it if it is
associated to something else.

There are several options to manage this scenario. Please choose the
option that best applies to your needs.

Option 1:
You can re-install Photo Editor on all the systems. This is essentially
rolling out an office installation through current methods and only
installing the Photo Editor component. To re-install Photo Editor please
follow the instructions in this link:
http://support.microsoft.com/?id=817095

Option 2:
You can include the necessary registry settings in your MST by adding the
keys in CIW to associate the graphics files with the appropriate
applications. I have generated a sample script for you below. You should
generate your own script following these steps:

1. On a system that is configured with appropriate file associations,
export the following registry keys to file:
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExt
s\.bmp
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExt
s\.gif
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExt
s\.jpe
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExt
s\.jpeg
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExt
s\.jpg
* you can of course add the keys for any other image files you want to
associate as well
** to export the keys, open regedit, browse to the key, right click and
choose export


2. Copy the resultant .reg file information into one .reg file, including
the "Windows Registry Editor Version 5.00" line only once at the top.

3. In CIW, on screen 12 of 24, Import the .reg file created in step #2.

Here is a sample file that I created from my system:
++++++//BEGIN FILE CUT BELOW LINE\\++++++++++++

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileEx
ts\.bmp]
"Application"="ois.exe"

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileEx
ts\.bmp\OpenWithList]
"a"="mspaint.exe"
"MRUList"="dcba"
"b"="iexplore.exe"
"c"="shimgvw.dll"
"d"="OIS.EXE"

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileEx
ts\.bmp\OpenWithProgids]
"Paint.Picture"=hex(0):

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileEx
ts\.jpg]

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileEx
ts\.jpg\OpenWithList]
"a"="shimgvw.dll"
"MRUList"="ebadc"
"b"="mspaint.exe"
"c"="iexplore.exe"
"d"="msnmsgr.exe"
"e"="OIS.EXE"

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileEx
ts\.jpg\OpenWithProgids]
"jpegfile"=hex(0):


[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileEx
ts\.gif]
"Application"="ois.exe"

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileEx
ts\.gif\OpenWithList]
"a"="shimgvw.dll"
"MRUList"="ebadc"
"b"="mspaint.exe"
"c"="iexplore.exe"
"d"="msnmsgr.exe"
"e"="OIS.EXE"

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileEx
ts\.gif\OpenWithProgids]
"giffile"=hex(0):

++++++++++//END FILE CUT ABOVE LINE\\++++++++++++++++

Option 3:

If you have already rolled out the installation and would rather not
re-install office, you can publish a .bat file or implement it as a login
script to call the .reg file created above. The .bat file should include a
line to call the .reg with this syntax:
REGEDIT /S "\\servername\Sharename\name.reg"

Hope this helps!

Sincerely,

Dana Brash
Microsoft Online Partner Support

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
Business-Critical Phone Support (BCPS) provides you with technical phone
support at no charge during critical LAN outages or "business down"
situations. This benefit is available 24 hours a day, 7 days a week to all
Microsoft technology partners in the United States and Canada.

This and other support options are available here:
BCPS:
https://partner.microsoft.com/US/technicalsupport/supportoverview/40010469
Others: https://partner.microsoft.com/US/technicalsupport/supportoverview/

If you are outside the United States, please visit our International
Support page:
http://support.microsoft.com/default.aspx?scid=/international.aspx.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.


--------------------
Thread-Topic: .jpg .gif .bmp file associations gone, upgrade from Office XP
thread-index: AcUQfDxfDDroTTX1QPawpgjcTHsjow==
X-WBNR-Posting-Host: 64.1.44.68
From: "=?Utf-8?B?ZmJhcnRyb20=?=" <[email protected]>
References: <[email protected]>
 
D

Dana Brash [MSFT]

Hello,

Thank you for your prompt response, and I apologize for my delayed response
due to the weekend. I also apologize that I did not fully understand your
original concerns and provide a more thorough answer. I have performed
further research to more thoroughly answer your question.

When Office 2000 or Office XP is upgraded to Office System 2003, the
graphic file extensions associated with Microsoft Photo Editor are removed
even if the extensions have been re-associated with a different graphics
file handler. Although Office 2003 installs the Microsoft Office Picture
Manager, it does not automatically associate the graphics file extensions
during the installation.
Picture Manager offers the user a choice during the first run by the user.

Unfortunately, this is by design. It is a limitation in Windows installer
because it does not know the file association to keep it if it is
associated to something else.

There are several options to manage this scenario. Please choose the
option that best applies to your needs.

Option 1:
You can re-install Photo Editor on all the systems. This is essentially
rolling out an office installation through current methods and only
installing the Photo Editor component. To re-install Photo Editor please
follow the instructions in this link:
http://support.microsoft.com/?id=817095

Option 2:
You can include the necessary registry settings in your MST by adding the
keys in CIW to associate the graphics files with the appropriate
applications. I have generated a sample script for you below. You should
generate your own script following these steps:

1. On a system that is configured with appropriate file associations,
export the following registry keys to file:
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExt
s\.bmp
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExt
s\.gif
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExt
s\.jpe
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExt
s\.jpeg
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExt
s\.jpg
* you can of course add the keys for any other image files you want to
associate as well
** to export the keys, open regedit, browse to the key, right click and
choose export


2. Copy the resultant .reg file information into one .reg file, including
the "Windows Registry Editor Version 5.00" line only once at the top.

3. In CIW, on screen 12 of 24, Import the .reg file created in step #2.

Here is a sample file that I created from my system:
++++++//BEGIN FILE CUT BELOW LINE\\++++++++++++

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileEx
ts\.bmp]
"Application"="ois.exe"

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileEx
ts\.bmp\OpenWithList]
"a"="mspaint.exe"
"MRUList"="dcba"
"b"="iexplore.exe"
"c"="shimgvw.dll"
"d"="OIS.EXE"

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileEx
ts\.bmp\OpenWithProgids]
"Paint.Picture"=hex(0):

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileEx
ts\.jpg]

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileEx
ts\.jpg\OpenWithList]
"a"="shimgvw.dll"
"MRUList"="ebadc"
"b"="mspaint.exe"
"c"="iexplore.exe"
"d"="msnmsgr.exe"
"e"="OIS.EXE"

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileEx
ts\.jpg\OpenWithProgids]
"jpegfile"=hex(0):


[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileEx
ts\.gif]
"Application"="ois.exe"

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileEx
ts\.gif\OpenWithList]
"a"="shimgvw.dll"
"MRUList"="ebadc"
"b"="mspaint.exe"
"c"="iexplore.exe"
"d"="msnmsgr.exe"
"e"="OIS.EXE"

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileEx
ts\.gif\OpenWithProgids]
"giffile"=hex(0):

++++++++++//END FILE CUT ABOVE LINE\\++++++++++++++++

Option 3:

If you have already rolled out the installation and would rather not
re-install office, you can publish a .bat file or implement it as a login
script to call the .reg file created above. The .bat file should include a
line to call the .reg with this syntax:
REGEDIT /S "\\servername\Sharename\name.reg"

Hope this helps!

Sincerely,

Dana Brash
Microsoft Online Partner Support

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
Business-Critical Phone Support (BCPS) provides you with technical phone
support at no charge during critical LAN outages or "business down"
situations. This benefit is available 24 hours a day, 7 days a week to all
Microsoft technology partners in the United States and Canada.

This and other support options are available here:
BCPS:
https://partner.microsoft.com/US/technicalsupport/supportoverview/40010469
Others: https://partner.microsoft.com/US/technicalsupport/supportoverview/

If you are outside the United States, please visit our International
Support page:
http://support.microsoft.com/default.aspx?scid=/international.aspx.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.


--------------------
Thread-Topic: .jpg .gif .bmp file associations gone, upgrade from Office XP
thread-index: AcUQfDxfDDroTTX1QPawpgjcTHsjow==
X-WBNR-Posting-Host: 64.1.44.68
From: "=?Utf-8?B?ZmJhcnRyb20=?=" <[email protected]>
References: <[email protected]>
 
D

Dana Brash [MSFT]

Hello,

Thank you for your prompt response, and I apologize for my delayed response
due to the weekend. I also apologize that I did not fully understand your
original concerns and provide a more thorough answer. I have performed
further research to more thoroughly answer your question.

When Office 2000 or Office XP is upgraded to Office System 2003, the
graphic file extensions associated with Microsoft Photo Editor are removed
even if the extensions have been re-associated with a different graphics
file handler. Although Office 2003 installs the Microsoft Office Picture
Manager, it does not automatically associate the graphics file extensions
during the installation.
Picture Manager offers the user a choice during the first run by the user.

Unfortunately, this is by design. It is a limitation in Windows installer
because it does not know the file association to keep it if it is
associated to something else.

There are several options to manage this scenario. Please choose the
option that best applies to your needs.

Option 1:
You can re-install Photo Editor on all the systems. This is essentially
rolling out an office installation through current methods and only
installing the Photo Editor component. To re-install Photo Editor please
follow the instructions in this link:
http://support.microsoft.com/?id=817095

Option 2:
You can include the necessary registry settings in your MST by adding the
keys in CIW to associate the graphics files with the appropriate
applications. I have generated a sample script for you below. You should
generate your own script following these steps:

1. On a system that is configured with appropriate file associations,
export the following registry keys to file:
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExt
s\.bmp
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExt
s\.gif
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExt
s\.jpe
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExt
s\.jpeg
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExt
s\.jpg
* you can of course add the keys for any other image files you want to
associate as well
** to export the keys, open regedit, browse to the key, right click and
choose export


2. Copy the resultant .reg file information into one .reg file, including
the "Windows Registry Editor Version 5.00" line only once at the top.

3. In CIW, on screen 12 of 24, Import the .reg file created in step #2.

Here is a sample file that I created from my system:
++++++//BEGIN FILE CUT BELOW LINE\\++++++++++++

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileEx
ts\.bmp]
"Application"="ois.exe"

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileEx
ts\.bmp\OpenWithList]
"a"="mspaint.exe"
"MRUList"="dcba"
"b"="iexplore.exe"
"c"="shimgvw.dll"
"d"="OIS.EXE"

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileEx
ts\.bmp\OpenWithProgids]
"Paint.Picture"=hex(0):

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileEx
ts\.jpg]

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileEx
ts\.jpg\OpenWithList]
"a"="shimgvw.dll"
"MRUList"="ebadc"
"b"="mspaint.exe"
"c"="iexplore.exe"
"d"="msnmsgr.exe"
"e"="OIS.EXE"

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileEx
ts\.jpg\OpenWithProgids]
"jpegfile"=hex(0):


[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileEx
ts\.gif]
"Application"="ois.exe"

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileEx
ts\.gif\OpenWithList]
"a"="shimgvw.dll"
"MRUList"="ebadc"
"b"="mspaint.exe"
"c"="iexplore.exe"
"d"="msnmsgr.exe"
"e"="OIS.EXE"

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileEx
ts\.gif\OpenWithProgids]
"giffile"=hex(0):

++++++++++//END FILE CUT ABOVE LINE\\++++++++++++++++

Option 3:

If you have already rolled out the installation and would rather not
re-install office, you can publish a .bat file or implement it as a login
script to call the .reg file created above. The .bat file should include a
line to call the .reg with this syntax:
REGEDIT /S "\\servername\Sharename\name.reg"

Hope this helps!

Sincerely,

Dana Brash
Microsoft Online Partner Support

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
Business-Critical Phone Support (BCPS) provides you with technical phone
support at no charge during critical LAN outages or "business down"
situations. This benefit is available 24 hours a day, 7 days a week to all
Microsoft technology partners in the United States and Canada.

This and other support options are available here:
BCPS:
https://partner.microsoft.com/US/technicalsupport/supportoverview/40010469
Others: https://partner.microsoft.com/US/technicalsupport/supportoverview/

If you are outside the United States, please visit our International
Support page:
http://support.microsoft.com/default.aspx?scid=/international.aspx.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.


--------------------
Thread-Topic: .jpg .gif .bmp file associations gone, upgrade from Office XP
thread-index: AcUQfDxfDDroTTX1QPawpgjcTHsjow==
X-WBNR-Posting-Host: 64.1.44.68
From: "=?Utf-8?B?ZmJhcnRyb20=?=" <[email protected]>
References: <[email protected]>
 
D

Dana Brash [MSFT]

Hello,

Thank you for your prompt response, and I apologize for my delayed response
due to the weekend. I also apologize that I did not fully understand your
original concerns and provide a more thorough answer. I have performed
further research to more thoroughly answer your question.

When Office 2000 or Office XP is upgraded to Office System 2003, the
graphic file extensions associated with Microsoft Photo Editor are removed
even if the extensions have been re-associated with a different graphics
file handler. Although Office 2003 installs the Microsoft Office Picture
Manager, it does not automatically associate the graphics file extensions
during the installation.
Picture Manager offers the user a choice during the first run by the user.

Unfortunately, this is by design. It is a limitation in Windows installer
because it does not know the file association to keep it if it is
associated to something else.

There are several options to manage this scenario. Please choose the
option that best applies to your needs.

Option 1:
You can re-install Photo Editor on all the systems. This is essentially
rolling out an office installation through current methods and only
installing the Photo Editor component. To re-install Photo Editor please
follow the instructions in this link:
http://support.microsoft.com/?id=817095

Option 2:
You can include the necessary registry settings in your MST by adding the
keys in CIW to associate the graphics files with the appropriate
applications. I have generated a sample script for you below. You should
generate your own script following these steps:

1. On a system that is configured with appropriate file associations,
export the following registry keys to file:
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExt
s\.bmp
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExt
s\.gif
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExt
s\.jpe
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExt
s\.jpeg
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExt
s\.jpg
* you can of course add the keys for any other image files you want to
associate as well
** to export the keys, open regedit, browse to the key, right click and
choose export


2. Copy the resultant .reg file information into one .reg file, including
the "Windows Registry Editor Version 5.00" line only once at the top.

3. In CIW, on screen 12 of 24, Import the .reg file created in step #2.

Here is a sample file that I created from my system:
++++++//BEGIN FILE CUT BELOW LINE\\++++++++++++

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileEx
ts\.bmp]
"Application"="ois.exe"

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileEx
ts\.bmp\OpenWithList]
"a"="mspaint.exe"
"MRUList"="dcba"
"b"="iexplore.exe"
"c"="shimgvw.dll"
"d"="OIS.EXE"

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileEx
ts\.bmp\OpenWithProgids]
"Paint.Picture"=hex(0):

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileEx
ts\.jpg]

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileEx
ts\.jpg\OpenWithList]
"a"="shimgvw.dll"
"MRUList"="ebadc"
"b"="mspaint.exe"
"c"="iexplore.exe"
"d"="msnmsgr.exe"
"e"="OIS.EXE"

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileEx
ts\.jpg\OpenWithProgids]
"jpegfile"=hex(0):


[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileEx
ts\.gif]
"Application"="ois.exe"

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileEx
ts\.gif\OpenWithList]
"a"="shimgvw.dll"
"MRUList"="ebadc"
"b"="mspaint.exe"
"c"="iexplore.exe"
"d"="msnmsgr.exe"
"e"="OIS.EXE"

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileEx
ts\.gif\OpenWithProgids]
"giffile"=hex(0):

++++++++++//END FILE CUT ABOVE LINE\\++++++++++++++++

Option 3:

If you have already rolled out the installation and would rather not
re-install office, you can publish a .bat file or implement it as a login
script to call the .reg file created above. The .bat file should include a
line to call the .reg with this syntax:
REGEDIT /S "\\servername\Sharename\name.reg"

Hope this helps!

Sincerely,

Dana Brash
Microsoft Online Partner Support

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
Business-Critical Phone Support (BCPS) provides you with technical phone
support at no charge during critical LAN outages or "business down"
situations. This benefit is available 24 hours a day, 7 days a week to all
Microsoft technology partners in the United States and Canada.

This and other support options are available here:
BCPS:
https://partner.microsoft.com/US/technicalsupport/supportoverview/40010469
Others: https://partner.microsoft.com/US/technicalsupport/supportoverview/

If you are outside the United States, please visit our International
Support page:
http://support.microsoft.com/default.aspx?scid=/international.aspx.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.


--------------------
Thread-Topic: .jpg .gif .bmp file associations gone, upgrade from Office XP
thread-index: AcUQfDxfDDroTTX1QPawpgjcTHsjow==
X-WBNR-Posting-Host: 64.1.44.68
From: "=?Utf-8?B?ZmJhcnRyb20=?=" <[email protected]>
References: <[email protected]>
 
D

Dana Brash [MSFT]

Hello,

Thank you for your prompt response, and I apologize for my delayed response
due to the weekend. I also apologize that I did not fully understand your
original concerns and provide a more thorough answer. I have performed
further research to more thoroughly answer your question.

When Office 2000 or Office XP is upgraded to Office System 2003, the
graphic file extensions associated with Microsoft Photo Editor are removed
even if the extensions have been re-associated with a different graphics
file handler. Although Office 2003 installs the Microsoft Office Picture
Manager, it does not automatically associate the graphics file extensions
during the installation.
Picture Manager offers the user a choice during the first run by the user.

Unfortunately, this is by design. It is a limitation in Windows installer
because it does not know the file association to keep it if it is
associated to something else.

There are several options to manage this scenario. Please choose the
option that best applies to your needs.

Option 1:
You can re-install Photo Editor on all the systems. This is essentially
rolling out an office installation through current methods and only
installing the Photo Editor component. To re-install Photo Editor please
follow the instructions in this link:
http://support.microsoft.com/?id=817095

Option 2:
You can include the necessary registry settings in your MST by adding the
keys in CIW to associate the graphics files with the appropriate
applications. I have generated a sample script for you below. You should
generate your own script following these steps:

1. On a system that is configured with appropriate file associations,
export the following registry keys to file:
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExt
s\.bmp
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExt
s\.gif
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExt
s\.jpe
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExt
s\.jpeg
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExt
s\.jpg
* you can of course add the keys for any other image files you want to
associate as well
** to export the keys, open regedit, browse to the key, right click and
choose export


2. Copy the resultant .reg file information into one .reg file, including
the "Windows Registry Editor Version 5.00" line only once at the top.

3. In CIW, on screen 12 of 24, Import the .reg file created in step #2.

Here is a sample file that I created from my system:
++++++//BEGIN FILE CUT BELOW LINE\\++++++++++++

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileEx
ts\.bmp]
"Application"="ois.exe"

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileEx
ts\.bmp\OpenWithList]
"a"="mspaint.exe"
"MRUList"="dcba"
"b"="iexplore.exe"
"c"="shimgvw.dll"
"d"="OIS.EXE"

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileEx
ts\.bmp\OpenWithProgids]
"Paint.Picture"=hex(0):

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileEx
ts\.jpg]

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileEx
ts\.jpg\OpenWithList]
"a"="shimgvw.dll"
"MRUList"="ebadc"
"b"="mspaint.exe"
"c"="iexplore.exe"
"d"="msnmsgr.exe"
"e"="OIS.EXE"

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileEx
ts\.jpg\OpenWithProgids]
"jpegfile"=hex(0):


[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileEx
ts\.gif]
"Application"="ois.exe"

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileEx
ts\.gif\OpenWithList]
"a"="shimgvw.dll"
"MRUList"="ebadc"
"b"="mspaint.exe"
"c"="iexplore.exe"
"d"="msnmsgr.exe"
"e"="OIS.EXE"

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileEx
ts\.gif\OpenWithProgids]
"giffile"=hex(0):

++++++++++//END FILE CUT ABOVE LINE\\++++++++++++++++

Option 3:

If you have already rolled out the installation and would rather not
re-install office, you can publish a .bat file or implement it as a login
script to call the .reg file created above. The .bat file should include a
line to call the .reg with this syntax:
REGEDIT /S "\\servername\Sharename\name.reg"

Hope this helps!

Sincerely,

Dana Brash
Microsoft Online Partner Support

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
Business-Critical Phone Support (BCPS) provides you with technical phone
support at no charge during critical LAN outages or "business down"
situations. This benefit is available 24 hours a day, 7 days a week to all
Microsoft technology partners in the United States and Canada.

This and other support options are available here:
BCPS:
https://partner.microsoft.com/US/technicalsupport/supportoverview/40010469
Others: https://partner.microsoft.com/US/technicalsupport/supportoverview/

If you are outside the United States, please visit our International
Support page:
http://support.microsoft.com/default.aspx?scid=/international.aspx.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.


--------------------
Thread-Topic: .jpg .gif .bmp file associations gone, upgrade from Office XP
thread-index: AcUQfDxfDDroTTX1QPawpgjcTHsjow==
X-WBNR-Posting-Host: 64.1.44.68
From: "=?Utf-8?B?ZmJhcnRyb20=?=" <[email protected]>
References: <[email protected]>
 
D

Dana Brash [MSFT]

Hello,

Thank you for your prompt response, and I apologize for my delayed response
due to the weekend. I also apologize that I did not fully understand your
original concerns and provide a more thorough answer. I have performed
further research to more thoroughly answer your question.

When Office 2000 or Office XP is upgraded to Office System 2003, the
graphic file extensions associated with Microsoft Photo Editor are removed
even if the extensions have been re-associated with a different graphics
file handler. Although Office 2003 installs the Microsoft Office Picture
Manager, it does not automatically associate the graphics file extensions
during the installation.
Picture Manager offers the user a choice during the first run by the user.

Unfortunately, this is by design. It is a limitation in Windows installer
because it does not know the file association to keep it if it is
associated to something else.

There are several options to manage this scenario. Please choose the
option that best applies to your needs.

Option 1:
You can re-install Photo Editor on all the systems. This is essentially
rolling out an office installation through current methods and only
installing the Photo Editor component. To re-install Photo Editor please
follow the instructions in this link:
http://support.microsoft.com/?id=817095

Option 2:
You can include the necessary registry settings in your MST by adding the
keys in CIW to associate the graphics files with the appropriate
applications. I have generated a sample script for you below. You should
generate your own script following these steps:

1. On a system that is configured with appropriate file associations,
export the following registry keys to file:
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExt
s\.bmp
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExt
s\.gif
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExt
s\.jpe
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExt
s\.jpeg
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExt
s\.jpg
* you can of course add the keys for any other image files you want to
associate as well
** to export the keys, open regedit, browse to the key, right click and
choose export


2. Copy the resultant .reg file information into one .reg file, including
the "Windows Registry Editor Version 5.00" line only once at the top.

3. In CIW, on screen 12 of 24, Import the .reg file created in step #2.

Here is a sample file that I created from my system:
++++++//BEGIN FILE CUT BELOW LINE\\++++++++++++

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileEx
ts\.bmp]
"Application"="ois.exe"

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileEx
ts\.bmp\OpenWithList]
"a"="mspaint.exe"
"MRUList"="dcba"
"b"="iexplore.exe"
"c"="shimgvw.dll"
"d"="OIS.EXE"

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileEx
ts\.bmp\OpenWithProgids]
"Paint.Picture"=hex(0):

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileEx
ts\.jpg]

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileEx
ts\.jpg\OpenWithList]
"a"="shimgvw.dll"
"MRUList"="ebadc"
"b"="mspaint.exe"
"c"="iexplore.exe"
"d"="msnmsgr.exe"
"e"="OIS.EXE"

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileEx
ts\.jpg\OpenWithProgids]
"jpegfile"=hex(0):


[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileEx
ts\.gif]
"Application"="ois.exe"

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileEx
ts\.gif\OpenWithList]
"a"="shimgvw.dll"
"MRUList"="ebadc"
"b"="mspaint.exe"
"c"="iexplore.exe"
"d"="msnmsgr.exe"
"e"="OIS.EXE"

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileEx
ts\.gif\OpenWithProgids]
"giffile"=hex(0):

++++++++++//END FILE CUT ABOVE LINE\\++++++++++++++++

Option 3:

If you have already rolled out the installation and would rather not
re-install office, you can publish a .bat file or implement it as a login
script to call the .reg file created above. The .bat file should include a
line to call the .reg with this syntax:
REGEDIT /S "\\servername\Sharename\name.reg"

Hope this helps!

Sincerely,

Dana Brash
Microsoft Online Partner Support

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
Business-Critical Phone Support (BCPS) provides you with technical phone
support at no charge during critical LAN outages or "business down"
situations. This benefit is available 24 hours a day, 7 days a week to all
Microsoft technology partners in the United States and Canada.

This and other support options are available here:
BCPS:
https://partner.microsoft.com/US/technicalsupport/supportoverview/40010469
Others: https://partner.microsoft.com/US/technicalsupport/supportoverview/

If you are outside the United States, please visit our International
Support page:
http://support.microsoft.com/default.aspx?scid=/international.aspx.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.


--------------------
Thread-Topic: .jpg .gif .bmp file associations gone, upgrade from Office XP
thread-index: AcUQfDxfDDroTTX1QPawpgjcTHsjow==
X-WBNR-Posting-Host: 64.1.44.68
From: "=?Utf-8?B?ZmJhcnRyb20=?=" <[email protected]>
References: <[email protected]>
 
B

Bob Buckland ?:-\)

Hi F.,

Did you get the same result if you do a test machine
with a manual install?

Graphics programs have a reputation for being 'grabby'
(taking over the associations on install).

There isn't a built in provision in the Custom Installation
Wizard screens for Office 2003 if the 'open with'
settings aren't migrating that I recall. There also
wasn't one for MS Office PhotoEditor. Photo Editor
tended to takeover the associations, where MS Office Picture Manager
tends to leave them off by default.

As you mentioned in your original post you can add the
registry entries, and you could probably use the
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts
list and set the MRU value to OIS (the Office Picture Manager)
or to Photoshop as the first entry for each file type
and use either different MST files or different OPS files
based on the user having or not having Photoshop, or
save the previous reg key and replace the entries in
the 'openwithlist' (edit replace in the reg file)
that read 'photoed.exe' with 'ois.exe' although
you may also have to update the HKEY_Classes_Root
associations reg entries, or you may want to consider
having a .reg key that Photoshop folks can use to
'reset' their graphics associations after the install.


========
Your understanding is not correct. After the upgrade, .jpg .gif .bmp file
associations gone. Since Photo Editor from Office XP is being upgraded to
Picture Manager from Office 2003, these associations should automatically be
re-associated to Picture Manager. I am deploying to over 600 users and do
not want to manually create the associations for every user.

How do you configure the upgrade install to correctly and automatically move
the file association of .jpg, .gif and .bmp from Photo Editor to Microsoft
Office Picture Manager.>>
--
Let us know if this helped you,

Bob Buckland ?:)
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

Office 2003 Editions explained
http://www.microsoft.com/uk/office/editions.mspx
 
B

Bob Buckland ?:-\)

Hi F.,

Did you get the same result if you do a test machine
with a manual install?

Graphics programs have a reputation for being 'grabby'
(taking over the associations on install).

There isn't a built in provision in the Custom Installation
Wizard screens for Office 2003 if the 'open with'
settings aren't migrating that I recall. There also
wasn't one for MS Office PhotoEditor. Photo Editor
tended to takeover the associations, where MS Office Picture Manager
tends to leave them off by default.

As you mentioned in your original post you can add the
registry entries, and you could probably use the
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts
list and set the MRU value to OIS (the Office Picture Manager)
or to Photoshop as the first entry for each file type
and use either different MST files or different OPS files
based on the user having or not having Photoshop, or
save the previous reg key and replace the entries in
the 'openwithlist' (edit replace in the reg file)
that read 'photoed.exe' with 'ois.exe' although
you may also have to update the HKEY_Classes_Root
associations reg entries, or you may want to consider
having a .reg key that Photoshop folks can use to
'reset' their graphics associations after the install.


========
Your understanding is not correct. After the upgrade, .jpg .gif .bmp file
associations gone. Since Photo Editor from Office XP is being upgraded to
Picture Manager from Office 2003, these associations should automatically be
re-associated to Picture Manager. I am deploying to over 600 users and do
not want to manually create the associations for every user.

How do you configure the upgrade install to correctly and automatically move
the file association of .jpg, .gif and .bmp from Photo Editor to Microsoft
Office Picture Manager.>>
--
Let us know if this helped you,

Bob Buckland ?:)
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

Office 2003 Editions explained
http://www.microsoft.com/uk/office/editions.mspx
 
B

Bob Buckland ?:-\)

Hi F.,

Did you get the same result if you do a test machine
with a manual install?

Graphics programs have a reputation for being 'grabby'
(taking over the associations on install).

There isn't a built in provision in the Custom Installation
Wizard screens for Office 2003 if the 'open with'
settings aren't migrating that I recall. There also
wasn't one for MS Office PhotoEditor. Photo Editor
tended to takeover the associations, where MS Office Picture Manager
tends to leave them off by default.

As you mentioned in your original post you can add the
registry entries, and you could probably use the
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts
list and set the MRU value to OIS (the Office Picture Manager)
or to Photoshop as the first entry for each file type
and use either different MST files or different OPS files
based on the user having or not having Photoshop, or
save the previous reg key and replace the entries in
the 'openwithlist' (edit replace in the reg file)
that read 'photoed.exe' with 'ois.exe' although
you may also have to update the HKEY_Classes_Root
associations reg entries, or you may want to consider
having a .reg key that Photoshop folks can use to
'reset' their graphics associations after the install.


========
Your understanding is not correct. After the upgrade, .jpg .gif .bmp file
associations gone. Since Photo Editor from Office XP is being upgraded to
Picture Manager from Office 2003, these associations should automatically be
re-associated to Picture Manager. I am deploying to over 600 users and do
not want to manually create the associations for every user.

How do you configure the upgrade install to correctly and automatically move
the file association of .jpg, .gif and .bmp from Photo Editor to Microsoft
Office Picture Manager.>>
--
Let us know if this helped you,

Bob Buckland ?:)
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

Office 2003 Editions explained
http://www.microsoft.com/uk/office/editions.mspx
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top