David
Fri Aug 26 07:54:21 CDT 2005
Yup, unattend IIS installation works via the commandline.
According to documentation, InstallFilesPath has nothing to do with Optional
Components install (it is used far earlier in the install process), so not
certain what you were hoping for... it most likely did not happen.
http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/80455459-01b0-4961-aeab-081ce2eb03a4.mspx
I have no idea where in the registry you were trying to change, but the
registry keys that change where Windows looks for a file are:
"HKLM\Software\Microsoft\Windows\CurrentVersion\Setup\SourcePath"
"HKLM\Software\Microsoft\Windows\CurrentVersion\Setup\ServicePackSourcePath"
And you set them both to C:\I386 (best if you produced a SP slip-stream
installpoint at C:\i386)
--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Rob White" <RobWhite@discussions.microsoft.com> wrote in message
news:911618CC-D5FE-4751-920C-D3908C08D950@microsoft.com...
I am in the process of writing a configuration script for a windows 2003
server. Part of this script installs and configures an ftp server in IIS. On
the most part the script works fine, but I'm a little stuck on a detail.
Essentially I need to get the script to tell windows that the I386 folder
(required for the install) is available the local machine i.e. C:\I386\ and
I
don't want the installation to ask for the windows CD, I was hoping that I
would be able to use:
[Unattended]
InstallFilesPath="C:\i386\"
But that doesn't work, I've also tried to change the registry to point at
the c drive, but that failed just as badly. Is there a way that this can be
done?
Thanks for any help,
Rob