Technology Tips and News
Hi all,
I just install SCCM 2012 R2 and want to deploy our Voice applications to our new SOE.
Currently install via GPO.
msiexec /i "\\server\softwareshare\1.ICUserApps_SU10.msi" PATCH="\\server\softwareshare\2.ICUserApps_SU18.msp" /l "\\server\softwareshare\logfile.log" ICSERVERNAME=cic3-prod.domain.com /qn
so how do i do it in SCCM
You could put the files in a folder, create a package or application using the new folder.
command line could be something like:
msiexec /i "%~dp01.ICUserApps_SU10.msi" PATCH="%~dp02.ICUserApps_SU18.msp" /l "\\server\softwareshare\logfile.log" ICSERVERNAME=cic3-prod.domain.com /qn
Grant domain computers account access to the share that contains the log file so the log can be created as configuration manager uses the local system account of the client device to carry out the installation.
The folder will be cached down to the device and ran locally on each workstation.
If you run an install where you do not need to specify the full path of a patch file then you could simply have
msiexec /i "msi name.msi" /qn
Better yet, put both the MSP and MSI in a folder set as the source location for the deployment type -- not doing this really makes no sense in ConfigMgr. Then place the following in a batch file (in the same folder as the MSP and MSI) and run the batch in your deployment type.
msiexec /I "%~dp01.ICUserApps.msi" PATCH="%~dp02.ICUserApps_SU18.msp" ICSERVERNAME=cic3-prod.domain.com /l %windir%\temp\logfile.log /qnYou could put the files in a folder, create a package or application using the new folder.
command line could be something like:
msiexec /i "%~dp01.ICUserApps_SU10.msi" PATCH="%~dp02.ICUserApps_SU18.msp" /l "\\server\softwareshare\logfile.log" ICSERVERNAME=cic3-prod.domain.com /qn
Grant domain computers account access to the share that contains the log file so the log can be created as configuration manager uses the local system account of the client device to carry out the installation.
The folder will be cached down to the device and ran locally on each workstation.
If you run an install where you do not need to specify the full path of a patch file then you could simply have
msiexec /i "msi name.msi" /qn
You could put the files in a folder, create a package or application using the new folder.
command line could be something like:
msiexec /i "%~dp01.ICUserApps_SU10.msi" PATCH="%~dp02.ICUserApps_SU18.msp" /l "\\server\softwareshare\logfile.log" ICSERVERNAME=cic3-prod.domain.com /qn
Grant domain computers account access to the share that contains the log file so the log can be created as configuration manager uses the local system account of the client device to carry out the installation.
The folder will be cached down to the device and ran locally on each workstation.
If you run an install where you do not need to specify the full path of a patch file then you could simply have
msiexec /i "msi name.msi" /qn
HI All,
Thanks, I don't required the log file. But this application got lot of msp to install.
So what is the best way to go with that?
Ex:
App.msi
update1.msp...................update9.msp
They will release something in few weeks?
As
You could also slipstream the MSP files to the MSI file.
HI,
I'm not sure its good idea to do it but i thought test.
Microsoft Windows [Version 6.1.7601]But this Open the App and not asking to select the Folder?
Thought of follow this procedure.
First, run
Then apply the patches:
You can simply use the PATCH parameter, as mentioned by Jason, and use the ; -sign to create a list of patches. For example: PATCH=patch1.msp;patch2.msp;patch3.msp.
For more information please refer to: https://msdn.microsoft.com/en-us/library/windows/desktop/aa370576%28v=vs.85%29.aspx?f=255&MSPPError=-2147217396
HI,
I'm not sure its good idea to do it but i thought test.
Microsoft Windows [Version 6.1.7601]But this Open the App and not asking to select the Folder?
Thought of follow this procedure.
First, run
Then apply the patches:
HI,
I'm not sure its good idea to do it but i thought test.
Microsoft Windows [Version 6.1.7601]But this Open the App and not asking to select the Folder?
Thought of follow this procedure.
First, run
Then apply the patches:
HI,
I'm not sure its good idea to do it but i thought test.
Microsoft Windows [Version 6.1.7601]But this Open the App and not asking to select the Folder?
Thought of follow this procedure.
First, run
Then apply the patches:
Hi Peter,
Thanks, thats how i did it with GPO. But if i get patch10 after this month then what should i do?
again i'm new to SCCM and thought of easily patch the base MSI...
As
You can also use SCUP to deploy the patches.
You have two different challenges here though you didn't discuss in your original post:
- Installation
- Maintenance
Your installation package will *not* handle on-going maintenance of existing application installations. That has nothing to do with ConfigMgr though, that's simply how the msiexec command lines work. Thus, you'll need two separate "things"; one for installation and one for maintenance. One valid approach is the one outlined by Peter and the other is using an installation as I've outlined and then use SCUP to perform the maintenance to inject the MSPs into Software Updates and treat them like all other updates. With either method, updating the original installation package/application in ConfigMgr is optional as the maintenance package/application or injected updates will update any new or existing installations of the application on client systems.
Hi Jason,
1. Put all the files into my \\software\CIC\ share
2. Create install.cmd
msiexec /I "%~dp01.ICUserApps_64bit.msi" PATCH="%~dp02.ICUserApps_64bit_SU6.msp";"%~dp03.ICUserApps_64bit_SU6-120779.msp";"%~dp04.ICUserApps_64bit_SU6-125141.msp";"%~dp05.ICUserApps_64bit_SU6-125793.msp";"%~dp06.ICUserApps_64bit_SU6-126000.msp";"%~dp07.ICUserApps_64bit_SU6-126015-125972-125513.msp";"%~dp08.ICUserApps_64bit_SU6-126048.msp";"%~dp09.ICUserApps_64bit_SU6-130628.msp"; ICSERVERNAME=cic4-prod.domain.com /l %windir%\temp\logfile.log /qn
3. create the software package
4. Select this install.cmd
5. Distribute the content and deploy to the collection
6. Update memebership /reboot client few times
But nothing happening? How do i check or monitor?
do i have to put like this "%~dp01.ICUserApps.msi%" also try to run manually but Windows Installer Screen pops.
As
Hi Jason,
1. Put all the files into my \\software\CIC\ share
2. Create install.cmd
msiexec /I "%~dp01.ICUserApps_64bit.msi" PATCH="%~dp02.ICUserApps_64bit_SU6.msp";"%~dp03.ICUserApps_64bit_SU6-120779.msp";"%~dp04.ICUserApps_64bit_SU6-125141.msp";"%~dp05.ICUserApps_64bit_SU6-125793.msp";"%~dp06.ICUserApps_64bit_SU6-126000.msp";"%~dp07.ICUserApps_64bit_SU6-126015-125972-125513.msp";"%~dp08.ICUserApps_64bit_SU6-126048.msp";"%~dp09.ICUserApps_64bit_SU6-130628.msp"; ICSERVERNAME=cic4-prod.domain.com /l %windir%\temp\logfile.log /qn
3. create the software package
4. Select this install.cmd
5. Distribute the content and deploy to the collection
6. Update memebership /reboot client few times
But nothing happening? How do i check or monitor?
do i have to put like this "%~dp01.ICUserApps.msi%" also try to run manually but Windows Installer Screen pops.
As
Hi Jason,
1. Put all the files into my \\software\CIC\ share
2. Create install.cmd
msiexec /I "%~dp01.ICUserApps_64bit.msi" PATCH="%~dp02.ICUserApps_64bit_SU6.msp";"%~dp03.ICUserApps_64bit_SU6-120779.msp";"%~dp04.ICUserApps_64bit_SU6-125141.msp";"%~dp05.ICUserApps_64bit_SU6-125793.msp";"%~dp06.ICUserApps_64bit_SU6-126000.msp";"%~dp07.ICUserApps_64bit_SU6-126015-125972-125513.msp";"%~dp08.ICUserApps_64bit_SU6-126048.msp";"%~dp09.ICUserApps_64bit_SU6-130628.msp"; ICSERVERNAME=cic4-prod.domain.com /l %windir%\temp\logfile.log /qn
3. create the software package
4. Select this install.cmd
5. Distribute the content and deploy to the collection
6. Update memebership /reboot client few times
But nothing happening? How do i check or monitor?
do i have to put like this "%~dp01.ICUserApps.msi%" also try to run manually but Windows Installer Screen pops.
As
There's no need to reboot systems, they simply need to retrieve the latest machine policy which can be done from the ConfigMgr Control Panel applet on the Actions tab.
To monitor a program's execution, you need to check execmgr.log on the client.
Have you manually tested the above batch file? I see at least one syntax error: the semi-colon after the final patch.
Hi Jason,
I cannot find this "ConfigMgr Control Panel applet on the Actions tab" from client control panel ?
I just tested manually copy evry thing to Temp folder but its popup this
To me it looks OK.. Did you try with less of the MSP-files? You might also try changing the uppercase /I to lowercase /i and renaming your files to start without 1_ instead of 1. just in case.
HI Torsten,
You mean like this?
msiexec /I "%~dp01.ICUserApps_64bit.msi" PATCH="2.ICUserApps_64bit_SU6.msp;p3.ICUserApps_64bit_SU6-120779.msp;4.ICUserApps_64bit_SU6-125141.msp "ICSERVERNAME=cic4-prod.domain.com /l %windir%\temp\logfile.log /qn
after make changes to install.cmd do i have to update anything in Configmgr?
As
msiexec /I "%~dp01.ICUserApps_64bit.msi" PATCH="2.ICUserApps_64bit_SU6.msp;p3.ICUserApps_64bit_SU6-120779.msp;4.ICUserApps_64bit_SU6-125141.msp "ICSERVERNAME=cic4-prod.domain.com /l %windir%\temp\logfile.log /qn
after make changes to install.cmd do i have to update anything in Configmgr?
Close ... msiexec /I "%~dp01.ICUserApps_64bit.msi" PATCH="2.ICUserApps_64bit_SU6.msp;p3.ICUserApps_64bit_SU6-120779.msp;4.ICUserApps_64bit_SU6-125141.msp" ICSERVERNAME=cic4-prod.domain.com /l*v %windir%\temp\logfile.log
You have to update content then.
This topic is archived. No further replies will be accepted.
Other recent topics
Click here to get your free copy of Network Administrator. Over 25 plugins to make your life easier