>From memory: the original source installation files (the Win2k3 with SP1 
>integrated) aren't cached anywhere. So the required SP2 files are there, but 
>not the other files you need. So you need to keep switching between the two 
>source folders during the installation.

Cheers
Ken


From: Brian Desmond [mailto:[email protected]]
Sent: Friday, 27 February 2009 1:03 PM
To: NT System Admin Issues
Subject: RE: Compare i386 directories?

There is functionality in Windows to get around this - there's a patch/service 
pack file cache (one of the hidden folders in System32) that should mitigate 
this.

Thanks,
Brian Desmond
[email protected]

c - 312.731.3132

From: Bryan Garmon [mailto:[email protected]]
Sent: Thursday, February 26, 2009 10:54 AM
To: NT System Admin Issues
Subject: Compare i386 directories?

I'm troubleshooting a scenario where I think a Server was built using Server 
2003 SP1, then had SP2 installed, then had IIS installed, but pointed IIS to 
the SP1 i386 directory for the source files. Anyone have any ideas for a quick 
way to figure out if this is the case?











~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

Reply via email to