-
UPDATE: I am now using SYSOCMGR.exe to add the component. But I'm still getting prompted for the setup files. Here's the command I'm using: sysocmgr /i:%windir%\inf\sysoc.inf /u:c:\answerfile.txt Any suggestions? Thanks.
-
Hey now... Right now, for all my Windows Server 2003 installs, I need to manually install the WMI Windows Provider Installer. I do this by opening the Control Panel, going to Add/Remove Windows Components, opening Management and Monitoring Tools, and then selecting WMI Windows Installer Provider. Well, I would like to eliminate this manual step to server deployments and want to add it to an unattended installation. But for the life of me, I can't figure out how to do so on the command line. I came across this: rundll32 setupapi,InstallHinfSection WBEMMSI 128 %SystemRoot%\inf\wbemmsi.inf That starts the installation procedure but I am prompted for the Windows CD everytime and have to manually point it to the installation files. That is depsite the fact that the following two registry keys are pointed to the correct path to the i386 folder: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\SourcePath HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\Installation Sources Any suggestions? Thanks, elegault
-
I actually figured it out over the weekend... Bascially, I had to redirect where the logfile would be written because by default, setup.exe was trying to write back to the SMSPKGC$ share, which it can't because of security. So I just used the following line in my SMS program and it worked fine: setup.exe /s /f2c:\logfile.log thanks for all your help!
-
I'm trying to distribute a couple InstallShield EXE with the silent switch via SMS. The problem is, though the app appears to install according to SMS, nothing happens. No files or folders are created on the client. Even stranger is if I push the same EXE without the switches (basically, so I can run in manually), the installation initializes properly. Here's my commandline in SMS: Setup.exe /s The setup.iss file is in the same folder as setup.exe. If I run setup.exe /s manually, it installs properly. It's only when it is installed via SMS that I experience the problem. Any suggestions? Thanks, eric