Been lurking for weeks and figured I should post this as i've not seen it posted anywhere.
Many of you may know or read here that you can perform a silent install by running:
Well you may not know that you really can run this: \%isaserver%\MSPCLNT\SETUP.EXE /v"/passive"
Basically the /v"variable" means it passes whatever is in the quotes to the msi. By passing the /passive command you get unattended mode - progress bar only. No need to click "okay". There are other switches you may prefer depending on your setup. Let me know if anyone wants them and I'll post.
Sorry if this is already well know, I looked forever and only found the first commands but they were less than ideal.
I'm surprised it hadn't been posted because I did see alot of people requesting it.
Anyway here are the other parameters I know about, I have not tested them all.
Display Options /quiet Quiet mode, no user interaction /passive Unattended mode - progress bar only /q[n|b|r|f] Sets user interface level n - No UI b - Basic UI r - Reduced UI f - Full UI (default) /help Help information
Restart Options /norestart Do not restart after the installation is complete /promptrestart Prompts the user for restart if necessary /forcerestart Always restart the computer after installation
Logging Options /l[i|w|e|a|r|u|c|m|o|p|v|x|+|!|*] <LogFile> i - Status messages w - Nonfatal warnings e - All error messages a - Start up of actions r - Action-specific records u - User requests c - Initial UI parameters m - Out-of-memory or fatal exit information o - Out-of-disk-space messages p - Terminal properties v - Verbose output x - Extra debugging information + - Append to existing log file ! - Flush each line to the log * - Log all information, except for v and x options /log <LogFile> Equivalent of /l* <LogFile>
There are also some update options which include repair info but they require the .msi file and since the setup.exe client is already passing that info over I don't know how it would handle it.
I hope everyone finds at least some of this usefull and maybe the info in the article about silent installs can be updated.
I'm looking for fuly automated, and unattended client deployment. Above method is known and quite good, but it needs Administrator rights on client computer Installing via GPO is better, but has popup from FCManagement Tool, wich is also user confusing. I was trying copy FWC config (common.ini and managemet.ini) to allusers profile before install via GPO. It was done by machine startup script, but after starting install the settings were overwriten by MSI installer(I'd like to turn off proxy setting). I was also trying to install with transform file generated by me with ORCA. No luck - popup from Management Tool still appears. Firewall settings are correct and not overwriten. User still needs click OK button. I'd like to install Management Tool, but without popup on first run.
Have you any ideas how can it be done without user intervention and admin rights - I cannot find such method? My goal is to install client with automatic proxy configuration and automatic ISA searching - required by mobile clients. THX.
< Message edited by test541 -- 24.Nov.2005 11:31:39 PM >
Did you get an answer to this? I have the same problem. Although the install actually performs silently, once the user is logged in the first thing that happens is the ISA client pops up, pretty much inviting the user to change the settings. The user must at least press OK to get rid of the window.
How can we stop it popping up for the user on first login or deny the user the ability to modify the settings?
As to your silent install line, I found the following gives you the most control \mspclnt\setup.exe">\\<ClientServername>\mspclnt\setup.exe /v" SERVER_NAME_OR_IP=<ISAServerName> ENABLE_AUTO_DETECT=0 REFRESH_WEB_PROXY=0 /qn"
This fixes the server name and doesn't auto-configure the web proxy. Note there is no space after the /v but there is one after the /v" !!
I rolled out the ISA 2004 SP2 fwclient today, to around 75 users via a gpo. First time I've used a gpo install for the ISA fwclient and was pleasantlly pleased..:))I never had any popups or needed reboots on any of the clients, just the initial reboot for clients that were already signed in.Completely silent install.Steve
I think I have this figured out. It is as simple as forcing a reboot after the installation. I have been able to install the ISA 2004 client (SP1 or SP2 version), using a GPO, with a forced reboot, and there is no more configuration box popping up after logging on. It is consistent, so far, with the testing that I have done. I have not yet done a widespread deployment, but I will be now that I have this worked out.
To force a reboot, you will need to edit the MS_FWC.MSI file with an editor such as Orca or WinINSTALL, or anything that understands the MSI format. In the InstallExecuteSequence table, look for the row that is for ScheduleReboot. Its sequence number is 1010. The condition is set to ISSCHEDULEREBOOT. Remove the condition. That's all there is to it. It's a bit easier in WinINSTALL, since the option to require a reboot is in the interface, but then WI will add quite a few other things to the MSI database that I prefer not to have if it is not necessary.
my main problem that when i install it i get message " client firewall is not instlalled correctly" and i enabled auto detect. when i set enable all settings are passed to internet explorere settings and then when i click disable settings are still there!!! so if i instruct user to disable it when he is out of office he still can't access internet and that's not logical. i enabled cache drive will that cause problems?
thnx tarek for yor answer. as i searched for an answer for my situation the only thing i think it could be the problem that i have Vodafone Mobile Connect software installed to laptops to be used with PCMCIA connect cards for internet access out of office so i think that would be the reason that i get notification that firewall client is not installed proberly. any recommendations?