SCCM - Adobe Push
Hey Guys,
I have SCCM 07 configured in a VM environment with ten machines. I just started using SCCM a day ago so i'm still have a lot to learn. I have successfully installed SCCM on all the client VM machines. I have created a custom install program that installs adobe reader X. My custom install is called install.exe this program calls the reader .msi file and performs a silient install of that file. It works fine when a manually run install.exe. I was wondering if anyone could explain how I could push this through SCCM.
Thanks,
Justin
I have SCCM 07 configured in a VM environment with ten machines. I just started using SCCM a day ago so i'm still have a lot to learn. I have successfully installed SCCM on all the client VM machines. I have created a custom install program that installs adobe reader X. My custom install is called install.exe this program calls the reader .msi file and performs a silient install of that file. It works fine when a manually run install.exe. I was wondering if anyone could explain how I could push this through SCCM.
Thanks,
Justin
0 Comments
[ + ] Show comments
Answers (9)
Please log in to answer
Posted by:
pjgeutjens
14 years ago
in broad lines
1) create a package in SCCM, pointing it to the installation sources, and in the package create an install program (you may have already done this?)
2) assign Distribution Points to your package so the contents get synched.
3) create a Collection containing the objects (users/computers) that are allowed to receive the package.
4) create an Advertisement for the distribution, linking the package you created to the collection, decide whether the Adverisement is mandatory (installation enforced) or not (users have to go to the "Run Advertised Programs" dialog in Windows and select to install the program)
Undoubtedly more detailed info can be found on Microsoft's Technet or MSDN
Rgds,
PJ
1) create a package in SCCM, pointing it to the installation sources, and in the package create an install program (you may have already done this?)
2) assign Distribution Points to your package so the contents get synched.
3) create a Collection containing the objects (users/computers) that are allowed to receive the package.
4) create an Advertisement for the distribution, linking the package you created to the collection, decide whether the Adverisement is mandatory (installation enforced) or not (users have to go to the "Run Advertised Programs" dialog in Windows and select to install the program)
Undoubtedly more detailed info can be found on Microsoft's Technet or MSDN
Rgds,
PJ
Posted by:
moshbmxer4130
14 years ago
Posted by:
moshbmxer4130
14 years ago
Posted by:
pjgeutjens
13 years ago
Posted by:
moshbmxer4130
13 years ago
Posted by:
Lucid
13 years ago
Posted by:
rodtrent
13 years ago
You might also want to check the work done on the Adobe deployments by the Queen of SCUP...
http://www.queenofscup.com/
http://www.queenofscup.com/
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.