S
Scott
I am using an OEM CD that contains SP1 for my RIS Flat
file image. After adding in the NIC using the OEM DRIVER
KB Doc I was able to bring the image down with no
problem. After modifying the image and applying the
service packs and hotfixes the image would not load back
up using riprep. The following error occurs:
Missing CD Image on Server
The RIS server to which you are attempting to post this
installation does not contain the correct CD-based image.
The version of the CD-based image on the server must match
the version of the system you are attempting to image
[Version 5.1 Build 2600, Language English]. Please either
select a different RIS server to post this installation to
or add the corresponding CD-based image to the current RIS
server.
What I have found is that the OEM has Windows XP PRO on
the CD and is adding the SP1 during the installation phase
using the SVCPACK.INF. This causes the NTOSKRNL.EXE file
to remain at the standard version. When you apply the
811493 hotifix patch to a PC that has pulled the flat file
down it sees that SP1 is on the system and uses the latest
driver dated 04/24/03. It doesn't matter if you
slipstream the source image with SP1 then use that for RIS
to load as a flat file since the Dual Mode 811493 patch
applies either
5.1.2600.108 12/12/02 NTOSKRNL.EXE for Pre-SP1 or
5.1.2600.1151 04/24/03 NTOSKRNL.EXE With SP1. The flat
file contains 5.1.2600.1106 08/29/02. The CD has the SP1
on it but uses the SVCPACK.INF to install it during the
setup phase. I have attempted to fake out RIS by trying
to update the NTOSKRNL.EXE in the flat file image by
coping the hotfix version over the flat file version but
as expected the results were not good.
Its appears that this issue has been overlooked by
Microsoft since I have not seen another post about it. My
solution at this point is to avoid the 811493 patch like
the plague. Eventually a SP or hotfix will update the
NTOSKRNL.EXE and we will be back in this same battle. If
anyone has experienced this problem or knows about it I
would sure appreciate some assistance. I have 30 systems
to go out in 2 weeks and I would really like to have this
resolved.
Thank you,
Scott
(e-mail address removed)
file image. After adding in the NIC using the OEM DRIVER
KB Doc I was able to bring the image down with no
problem. After modifying the image and applying the
service packs and hotfixes the image would not load back
up using riprep. The following error occurs:
Missing CD Image on Server
The RIS server to which you are attempting to post this
installation does not contain the correct CD-based image.
The version of the CD-based image on the server must match
the version of the system you are attempting to image
[Version 5.1 Build 2600, Language English]. Please either
select a different RIS server to post this installation to
or add the corresponding CD-based image to the current RIS
server.
What I have found is that the OEM has Windows XP PRO on
the CD and is adding the SP1 during the installation phase
using the SVCPACK.INF. This causes the NTOSKRNL.EXE file
to remain at the standard version. When you apply the
811493 hotifix patch to a PC that has pulled the flat file
down it sees that SP1 is on the system and uses the latest
driver dated 04/24/03. It doesn't matter if you
slipstream the source image with SP1 then use that for RIS
to load as a flat file since the Dual Mode 811493 patch
applies either
5.1.2600.108 12/12/02 NTOSKRNL.EXE for Pre-SP1 or
5.1.2600.1151 04/24/03 NTOSKRNL.EXE With SP1. The flat
file contains 5.1.2600.1106 08/29/02. The CD has the SP1
on it but uses the SVCPACK.INF to install it during the
setup phase. I have attempted to fake out RIS by trying
to update the NTOSKRNL.EXE in the flat file image by
coping the hotfix version over the flat file version but
as expected the results were not good.
Its appears that this issue has been overlooked by
Microsoft since I have not seen another post about it. My
solution at this point is to avoid the 811493 patch like
the plague. Eventually a SP or hotfix will update the
NTOSKRNL.EXE and we will be back in this same battle. If
anyone has experienced this problem or knows about it I
would sure appreciate some assistance. I have 30 systems
to go out in 2 weeks and I would really like to have this
resolved.
Thank you,
Scott
(e-mail address removed)