Does the IES Pro have an unattended install feature?
I am trying to set this up to install from SCCM 2012. I can install the Shared Content since it's an MSI, but the actual setup doesn't appear to have that feature, or I can't find the correct way to configure it.
Any ideas?
Unattended install?
-
philaitman
- VE Newbie
- Posts: 2
- Joined: Wed Sep 25, 2013 11:37 am
Re: Unattended install?
HI Llewis,
well I don't come here often as but as I'm having a pain in the ass moment with network licensing I dropped by.
It's a good job you're using Configmgr 2012 as it's dependency detection methods will save you a lot of bother with deploying IES unnattended.
Create Applications (NOT Packages and programs) for the Dependencies
.net 4.0 Client profile - Create a script Based deployment Type
Installation program "dotNetFx40_Client_x86_x64.exe" /q /norestart
Uninstallation program "dotNetFx40_Client_x86_x64.exe" /uninstall
Detection method = registry Hive=HKEY_LOCAL_MACHINE Key=SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Client Value=Install data Type=Integer
Select This registry setting must exist on the target system to indicate the presence of this application
Shared Content - This is an MSI so all the require install-Uninstall and Detection methods should be filled in Automatically
Create a new Application for IES
Create a deployment type of Script
Installation program "ve2013setup.exe" /install /passive /norestart
Uninstallation program "ve2013setup.exe" /uninstall /passive /norestart
Detection method = Registry Hive HKEY_LOCAL_MACHINE Key=SOFTWARE\IES\Versions\Installed Value=2013
Tick This registry key is associated with a 32bit application on 64 bit systems
Data Type = String
Select This registry Setting must exist on the target system to indicate the presence of this application.
Set the .net and Shared content application deployment types as dependencies for IES (if they aren't there they'll get installed if they are there they'll be skipped over)
If you want to license the app during deployment create another script to copy the key's file or keys path file to the correct location.
Regards
Phil
MCP MCTS Configuration Manager 2012
well I don't come here often as but as I'm having a pain in the ass moment with network licensing I dropped by.
It's a good job you're using Configmgr 2012 as it's dependency detection methods will save you a lot of bother with deploying IES unnattended.
Create Applications (NOT Packages and programs) for the Dependencies
.net 4.0 Client profile - Create a script Based deployment Type
Installation program "dotNetFx40_Client_x86_x64.exe" /q /norestart
Uninstallation program "dotNetFx40_Client_x86_x64.exe" /uninstall
Detection method = registry Hive=HKEY_LOCAL_MACHINE Key=SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Client Value=Install data Type=Integer
Select This registry setting must exist on the target system to indicate the presence of this application
Shared Content - This is an MSI so all the require install-Uninstall and Detection methods should be filled in Automatically
Create a new Application for IES
Create a deployment type of Script
Installation program "ve2013setup.exe" /install /passive /norestart
Uninstallation program "ve2013setup.exe" /uninstall /passive /norestart
Detection method = Registry Hive HKEY_LOCAL_MACHINE Key=SOFTWARE\IES\Versions\Installed Value=2013
Tick This registry key is associated with a 32bit application on 64 bit systems
Data Type = String
Select This registry Setting must exist on the target system to indicate the presence of this application.
Set the .net and Shared content application deployment types as dependencies for IES (if they aren't there they'll get installed if they are there they'll be skipped over)
If you want to license the app during deployment create another script to copy the key's file or keys path file to the correct location.
Regards
Phil
MCP MCTS Configuration Manager 2012