In this Post we will have a look at the workflow which is being used While a user request for a Software . The below diagram will be more clear to people who have Used MS Visio as the symbols / Images have specific meaning .
Clearly you can see that the SCCM Admin creates the Application in the SCCM Console . User Requests for the Software Using Software Center . User Submits the request . The request goes to SCCM Admin who then approves or rejects the request basis which a decision is taken .
In the Last Section ( Part 1 of this Series ) we Talked about What is the difference between the Traditional method of Deploying Software( i.e package) in SCCM 2007 and Application Deployment in SCCM 2012 . And I am sure that now you have a feel of what we can do with the new version of SCCM .
Let us now move to Few of the Important Components of SCCM 2012 Applications : First of them Being :
Requirements : Now try and recollect those days when you used to or for that matter you still do this ; Create a Collection and then deploy a software onto that collection ( Example : If you need to deploy a software onto machines which have 4 GB of RAM , then you create a collection first and then deploy the software onto that collection ) . Wasn’t that a pain !!
Well !! it Was .
But now with SCCm 2012 requirements , you need not do this ! All you need to do is to stabilish a Requirement and then SCCM 2012 will take care of all that . No Collections !!
To Sum up : SCCM 2007 Software distribution was Collection Driven but in SCCM 2012 it is not.
Below Screen Shots will give you an understanding of what will happen : Here we have created a requirement rule that if free space in D Drive is equal or greater than 110 MB , only then install the software