Office install issues on WinXP Pro SP2

[Chad]

Hello.

We are testing an image for one of our PC's that we will
be implementing here at our Company. We have Windows XP
Professional with SP2. The SP2 comes from a SUS server
that handles our critical updates and such. Now after we
do this, we try to install Office 2000 Professional, and
it comes up asking for the Windows XP SP2 cd. Does anyone
know how to fix this as we would like to make sure that
the users getting these PC's do not see this message and
that the installer finds the files it needs without
prompting for a CD?

Any help would be nice.

Thanks,

Chad

[R. McCarty]

You'll need to change a couple of Registry Keys to resolve this.
The Office install is triggering a call to the XP source media for
files. XP has a hierarchy for getting source files.
(1.) DllCache (From Windows\System32
(2.) ServicePackFiles
(3.) i386 Folder (If installed from a disk drive or share)
(4.) Original Source point ( CD-ROM, I'm assuming)
The Registry keys are CDInstall which is likely set to 1 and the
SourcePath key is pointing to the CD-ROM Drive Letter.
You'll also find two keys related to the Service Pack location.
If it was me, I would add a System Share to the image to map to
a folder with i386 (Slipstreamed) and then change the Registry keys
to use/point to that location.
[HKLM]\Software\Microsoft\Windows\CurrentVersion\Setup]
"SourcePath"="F:\\"
"ServicePackSourcePath"="F:\\"
"CDInstall"=dword:00000000
"LogLevel"=dword:20000000
"ServicePackCachePath"="F:\\"
**F:\\ Represents my system, where the i386 is stored.

"Chad" > wrote in message
...
> Hello.
>
> We are testing an image for one of our PC's that we will
> be implementing here at our Company. We have Windows XP
> Professional with SP2. The SP2 comes from a SUS server
> that handles our critical updates and such. Now after we
> do this, we try to install Office 2000 Professional, and
> it comes up asking for the Windows XP SP2 cd. Does anyone
> know how to fix this as we would like to make sure that
> the users getting these PC's do not see this message and
> that the installer finds the files it needs without
> prompting for a CD?
>
> Any help would be nice.
>
> Thanks,
>
> Chad

[Chad]

Now how would we do this to direct the install to the
proper files. We get the SP2 through the SUS server. Now
do the files go to the same locations?

Thanks, Chad
>-----Original Message-----
>You'll need to change a couple of Registry Keys to
resolve this.
>The Office install is triggering a call to the XP source
media for
>files. XP has a hierarchy for getting source files.
>(1.) DllCache (From Windows\System32
>(2.) ServicePackFiles
>(3.) i386 Folder (If installed from a disk drive or share)
>(4.) Original Source point ( CD-ROM, I'm assuming)
>The Registry keys are CDInstall which is likely set to 1
and the
>SourcePath key is pointing to the CD-ROM Drive Letter.
>You'll also find two keys related to the Service Pack
location.
>If it was me, I would add a System Share to the image to
map to
>a folder with i386 (Slipstreamed) and then change the
Registry keys
>to use/point to that location.
>[HKLM]\Software\Microsoft\Windows\CurrentVersion\Setup]
>"SourcePath"="F:\\"
>"ServicePackSourcePath"="F:\\"
>"CDInstall"=dword:00000000
>"LogLevel"=dword:20000000
>"ServicePackCachePath"="F:\\"
>**F:\\ Represents my system, where the i386 is stored.
>
>"Chad" > wrote in message
...
>> Hello.
>>
>> We are testing an image for one of our PC's that we will
>> be implementing here at our Company. We have Windows XP
>> Professional with SP2. The SP2 comes from a SUS server
>> that handles our critical updates and such. Now after
we
>> do this, we try to install Office 2000 Professional, and
>> it comes up asking for the Windows XP SP2 cd. Does
anyone
>> know how to fix this as we would like to make sure that
>> the users getting these PC's do not see this message and
>> that the installer finds the files it needs without
>> prompting for a CD?
>>
>> Any help would be nice.
>>
>> Thanks,
>>
>> Chad
>
>
>.
>

[R. McCarty]

Not been involved in SUS, since I left Corporate work.
However, I would check your machine and see how the
SourcePath and ServicePackFiles are defined.
I suppose that SUS actually leaves the ServicePackFiles
folder resident on the client PC. But since your original
Image was created with a CD-ROM(?), it's that value &
pointer that caused your message.
If you use some type of Administrative share, you could
slipstream a CD to SP2, copy the files to the share and
then modify your image to point to it as the SourcePath.
I would contact Microsoft directly as they can answer &
guide you on this better since SUS is involved.

"Chad" > wrote in message
...
> Now how would we do this to direct the install to the
> proper files. We get the SP2 through the SUS server. Now
> do the files go to the same locations?
>
> Thanks, Chad
>>-----Original Message-----
>>You'll need to change a couple of Registry Keys to
> resolve this.
>>The Office install is triggering a call to the XP source
> media for
>>files. XP has a hierarchy for getting source files.
>>(1.) DllCache (From Windows\System32
>>(2.) ServicePackFiles
>>(3.) i386 Folder (If installed from a disk drive or share)
>>(4.) Original Source point ( CD-ROM, I'm assuming)
>>The Registry keys are CDInstall which is likely set to 1
> and the
>>SourcePath key is pointing to the CD-ROM Drive Letter.
>>You'll also find two keys related to the Service Pack
> location.
>>If it was me, I would add a System Share to the image to
> map to
>>a folder with i386 (Slipstreamed) and then change the
> Registry keys
>>to use/point to that location.
>>[HKLM]\Software\Microsoft\Windows\CurrentVersion\Setup]
>>"SourcePath"="F:\\"
>>"ServicePackSourcePath"="F:\\"
>>"CDInstall"=dword:00000000
>>"LogLevel"=dword:20000000
>>"ServicePackCachePath"="F:\\"
>>**F:\\ Represents my system, where the i386 is stored.
>>
>>"Chad" > wrote in message
...
>>> Hello.
>>>
>>> We are testing an image for one of our PC's that we will
>>> be implementing here at our Company. We have Windows XP
>>> Professional with SP2. The SP2 comes from a SUS server
>>> that handles our critical updates and such. Now after
> we
>>> do this, we try to install Office 2000 Professional, and
>>> it comes up asking for the Windows XP SP2 cd. Does
> anyone
>>> know how to fix this as we would like to make sure that
>>> the users getting these PC's do not see this message and
>>> that the installer finds the files it needs without
>>> prompting for a CD?
>>>
>>> Any help would be nice.
>>>
>>> Thanks,
>>>
>>> Chad
>>
>>
>>.
>>

[UncleFrank]

You have to Download Windows Installer Cleanup Utility on MS website.
Read instructions carefully \. I had to use it for Frontpage and Office
2000.

Solved my re-install problems.

"Chad" > wrote in message
...
> Hello.
>
> We are testing an image for one of our PC's that we will
> be implementing here at our Company. We have Windows XP
> Professional with SP2. The SP2 comes from a SUS server
> that handles our critical updates and such. Now after we
> do this, we try to install Office 2000 Professional, and
> it comes up asking for the Windows XP SP2 cd. Does anyone
> know how to fix this as we would like to make sure that
> the users getting these PC's do not see this message and
> that the installer finds the files it needs without
> prompting for a CD?
>
> Any help would be nice.
>
> Thanks,
>
> Chad

[Chad]

That stuff did not work guys. Thanks though. I talked to
one of our LAN Admins, and he said that the sysprep we run
is what makes this happen. If we run a service pack
install after a machine is imaged, the install works
fine. But if we do not install a service pack, it fails
with error 1933, windows installer could not update one or
more protected files etc.

How we do it is we build the image, run sysprep, then
ghost it upto the server to ghost down to multiple
machines. When the sysprep is run, we run into this issue.

Any more ideas???

Chad
>-----Original Message-----
>Not been involved in SUS, since I left Corporate work.
>However, I would check your machine and see how the
>SourcePath and ServicePackFiles are defined.
> I suppose that SUS actually leaves the ServicePackFiles
>folder resident on the client PC. But since your original
>Image was created with a CD-ROM(?), it's that value &
>pointer that caused your message.
> If you use some type of Administrative share, you could
>slipstream a CD to SP2, copy the files to the share and
>then modify your image to point to it as the SourcePath.
>I would contact Microsoft directly as they can answer &
>guide you on this better since SUS is involved.
>
>"Chad" > wrote in message
...
>> Now how would we do this to direct the install to the
>> proper files. We get the SP2 through the SUS server.
Now
>> do the files go to the same locations?
>>
>> Thanks, Chad
>>>-----Original Message-----
>>>You'll need to change a couple of Registry Keys to
>> resolve this.
>>>The Office install is triggering a call to the XP source
>> media for
>>>files. XP has a hierarchy for getting source files.
>>>(1.) DllCache (From Windows\System32
>>>(2.) ServicePackFiles
>>>(3.) i386 Folder (If installed from a disk drive or
share)
>>>(4.) Original Source point ( CD-ROM, I'm assuming)
>>>The Registry keys are CDInstall which is likely set to 1
>> and the
>>>SourcePath key is pointing to the CD-ROM Drive Letter.
>>>You'll also find two keys related to the Service Pack
>> location.
>>>If it was me, I would add a System Share to the image to
>> map to
>>>a folder with i386 (Slipstreamed) and then change the
>> Registry keys
>>>to use/point to that location.
>>>[HKLM]\Software\Microsoft\Windows\CurrentVersion\Setup]
>>>"SourcePath"="F:\\"
>>>"ServicePackSourcePath"="F:\\"
>>>"CDInstall"=dword:00000000
>>>"LogLevel"=dword:20000000
>>>"ServicePackCachePath"="F:\\"
>>>**F:\\ Represents my system, where the i386 is stored.
>>>
>>>"Chad" > wrote in message
...
>>>> Hello.
>>>>
>>>> We are testing an image for one of our PC's that we
will
>>>> be implementing here at our Company. We have Windows
XP
>>>> Professional with SP2. The SP2 comes from a SUS
server
>>>> that handles our critical updates and such. Now after
>> we
>>>> do this, we try to install Office 2000 Professional,
and
>>>> it comes up asking for the Windows XP SP2 cd. Does
>> anyone
>>>> know how to fix this as we would like to make sure
that
>>>> the users getting these PC's do not see this message
and
>>>> that the installer finds the files it needs without
>>>> prompting for a CD?
>>>>
>>>> Any help would be nice.
>>>>
>>>> Thanks,
>>>>
>>>> Chad
>>>
>>>
>>>.
>>>
>
>
>.
>

[Chad]

I got the issue repaired for those that want to know. If
you look up Microsoft KB article 314812 and use method 1,
that will repair the issue. I tried it this am and it
required the CD, but now that we know this we can repair
the base image and get it working without any issues.

Chad
>-----Original Message-----
>Hello.
>
>We are testing an image for one of our PC's that we will
>be implementing here at our Company. We have Windows XP
>Professional with SP2. The SP2 comes from a SUS server
>that handles our critical updates and such. Now after we
>do this, we try to install Office 2000 Professional, and
>it comes up asking for the Windows XP SP2 cd. Does
anyone
>know how to fix this as we would like to make sure that
>the users getting these PC's do not see this message and
>that the installer finds the files it needs without
>prompting for a CD?
>
>Any help would be nice.
>
>Thanks,
>
>Chad
>.
>