If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
GPO Office 2003
Hello, here is the problem. Office 2003 pushed out via
GPO works great. Calling a CIW MST...works great. Except that when Office tries to uninstall the pervious version of office 2000. It asks for the CD in the background which you never see of course. All features seem to get installed except that whichever profile in windows was previously there will not beable to start Outlook. The windows installer comes up and then rolls back. And says to reinstall Outlook. If i log in as a different user everything works great?? Anyone know how to specify the CD location of the old version?? Or if there are any switches i can use? Thanks for your help \ Tony Holland |
#2
|
|||
|
|||
GPO Office 2003
Hello, here is the problem. Office 2003 pushed out via GPO works great. Calling a CIW MST...works great. Except that when Office tries to uninstall the pervious version of office 2000. It asks for the CD in the background which you never see of course. All features seem to get installed except that whichever profile in windows was previously there will not beable to start Outlook. The windows installer comes up and then rolls back. And says to reinstall Outlook. If i log in as a different user everything works great?? Anyone know how to specify the CD location of the old version?? Or if there are any switches i can use? Thanks for your help \ Tony Holland Hello Tony, You can look at for all the setup switches 826530 Setup Command-Line Switches for Office 2003 http://kb/article.asp?id=Q826530 or Method 1: Provide the Office source files ----------------------------------------- When you install an update to an Office program, you must provide the Office source files (CD-ROM or administrative installation point) from where you originally installed Microsoft Office to make sure that all Office files are complete. Note For Microsoft Office 2000, the update that is described in the following article in the Microsoft Knowledge Base will help reduce the need to provide source files during an Office update: KBLink:835220.KB.[LN]: Office 2000 Update: February 10, 2004 Method 2: Manually change the modified dates of certain Office files -------------------------------------------------------------------- Sometimes you may be able to manually change the modified date of the file that the Windows Installer program has identified as changed. After you update the modified date of the file, the Windows Installer program will consider the file as 'user data'. A file that is considered 'user data' will not cause the Windows Installer program to request the Office source files. A partial list of the shared files that may be considered 'user data' during typical use of an Office program include the following files: - Access9.mdb - Ctryinfo.txt - Excel9.xls - Outlook.hol - Pwrpnt9.pot - Pwrpnt10.pot - XL8Galry.xls - Winword8.doc - Readme.txt To determine the Office file that the Windows Installer has determined must be changed, you must review the verbose log of the update installation. There are two ways to turn on verbose logging before you start the update process for your Office programs. - Use Regedit. To use Regedit, follow these steps: 1. Click "Start", and then click "Run". 2. In the "Open" (without the quotation marks) box, type "regedit" (without the quotation marks), and then click "OK" (without the quotation marks). 3. In Registry Editor, locate, and then click the following key: " HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Win dows\Installer" 4. With Installer selected, point to "New" on the "Edit" menu, and then click "String Value". 5. Type "Logging", and then press ENTER. 6. With "Logging" selected, click "Modify" on the "Edit" menu. 7. In the "Value data" box, type "voicewarmup" (without the quotation marks), and then click "OK". 8. With "Installer" selected, point to "New" on the "Edit" menu, and then click "DWORD Value". 9. Type "Debug" (without the quotation marks), and then press ENTER. 10. With "Debug" selected, click "Modify" on the "Edit" menu. 11. In the "Value data" box, type "7" (without the quotation marks), click "Hexadecimal", and then click "OK". 12. On the "File" menu, click "Exit" to quit Registry Editor. - Use the Group Policy editor (Local Machine). To use the Group Policy editor, follow these steps: 1. Click "Start", and then click "Run". 2. In the "Open" box, type "gpedit.msc" (without the quotation marks), and then click "OK". 3. In the Group Policy editor, under "Local Computer Policy", expand "Computer Configuration". 4. Expand "Administrative Templates". 5. Expand "Windows Components". 6. Select "Windows Installer". 7. In "Windows Installer", select "Logging". 8. On the "Action" menu, click "Properties". 9. On the "Settings" tab of the "Logging Properties" dialog box, click "Enabled". 10. In the "Logging" box, type "voicewarmup" (without the quotation marks), and then click "OK". 11. On the "File" menu, click "Exit" to close the "Group Policy" editor dialog box. After you turn on verbose logging and you install an Office update, a log file may be created that identifies the Office files that have changed. To locate and to change the modified date of the files that the Windows Installer program has determined to have changed, follow these steps: 1. Find the Office update verbose log file that is located in the user's Temp folder. To find the user's Temp folder, follow these steps: a. Click "Start", and then click "Run". b. In the "Open" box, type "%temp%" (without the quotation marks), and then click "OK".The path of the user's Temp folder should be similar to the following: C:\Documents and Settings\username\Local Settings\TempThe Office update verbose logs will have file names that are similar to "Msi#####.log", where the "#" (number sign) represents any alpha/numeric character. For example, a verbose log file could have the following file name: Msi7b3d5.logNote If the OHotfix.exe bootstrapping application utility is used for updates, the log files are stored in the following folder: C:\Documents and Settings\username\Local Settings\Temp\OhotfixThe update log files are created in two set pairs with a naming convention of "OHotfix(00001).log" and "OHotfix(00001)_Msi.log". For more information about the OHotfix.exe utility, visit the following Microsoft Web site: http://www.microsoft.com/office/ork/...rn/Ohotfix.htm 2. Check the timestamp of the log file to make sure that you have found the correct log file that was created for the latest update attempt because there may be many log files in the folder. To check the timestamp of the log file, right-click the log file, and then click "Properties". 3. Double-click the log file to open the file in your default text editor (such as Notepad). 4. On the "Edit" menu, click "Find". 5. In the "Find what" box, type "Resolving source" (without the quotation marks), and then click "Find Next". 6. The line in the log file immediately above the words "Resolving source" will show the Office file that the Windows Installer program has determined was changed. Note The following example shows that the file Readme.txt has changed and will cause the Windows Installer program to prompt you for the Office source files: MSI (s) (B0:2C): File: C:\Program Files\Common Files\Microsoft Shared\Snapshot Viewer\README.TXT; Overwrite; No patch; Existing file is unversioned and unmodified - hash doesn't match source file MSI (s) (B0:2C): Resolving source. 7. To change the modified date of the files listed in the log file, follow these steps: a. Click "Start", and then click "Search". b. Click "All files and folders". c. In the "All or part of the file name" box, type the file name of the file that you found in the log file. d. In the "Look in" box, click your local hard disk drive. e. Click "Search". f. Double-click the found file. g. After the file has opened, close the file without making any changes to the file. h. You may have to repeat steps 7a to 7g several times. After each files modified date is changed, the Windows Installer program will not prompt you for the source Office files because each file will be considered 'user data' by the Windows Installer program. -- Kindest regards, Vincent Schouten - Technical Support Specialist - Microsoft Services This posting is provided "AS IS" with no warranties, and confers no rights. Go to http://www.microsoft.com/protect and follow instructions today! |
Thread Tools | |
Display Modes | |
|
|