An example of this. We assign all core apps to all systems. For the laptop
layer of core (vpn client etc) we made a global condition called
chassistype. It returns laptop or desktop.
We set the vpn client to only install on laptops.
Dim ChassisType
Set objWMIService =
GetObject("winmgmts:{impersonationLevel=impersonate}!\\.\root\cimv2")
Set colChassis = objWMIService.ExecQuery("Select * from
Win32_SystemEnclosure")
For Each objChassis in colChassis
For Each strChassisType in objChassis.ChassisTypes
SELECT CASE strChassisType
CASE 8 ChassisType = "Laptop"
CASE 9 ChassisType = "Laptop"
CASE 10 ChassisType = "Laptop"
CASE 11 ChassisType = "Laptop"
CASE 12 ChassisType = "Laptop"
CASE 14 ChassisType = "Laptop"
CASE 18 ChassisType = "Laptop"
CASE 21 ChassisType = "Laptop"
CASE 3 ChassisType = "Desktop"
CASE 4 ChassisType = "Desktop"
CASE 5 ChassisType = "Desktop"
CASE 6 ChassisType = "Desktop"
CASE 7 ChassisType = "Desktop"
CASE 15 ChassisType = "Desktop"
CASE 16 ChassisType = "Desktop"
End SELECT
Next
Next
Wscript.Echo ChassisType
On Thu, Jun 19, 2014 at 12:26 PM, Trevor Sullivan <[email protected]> wrote:
> Deployment Types are automatically evaluated by **all** clients that have
> been targeted with an Application. You need to change the way you’re
> thinking about the situation, in order to be successful.
>
>
>
> Ask yourself: *What is inherently different about the machines in
> Collection “A” vs. Collection “B?”*
>
>
>
> Once you answer that question, build a custom Global Condition for each
> deployment type, that satisfies that criteria. Assign the Global Condition
> to each Deployment Type, as appropriate, and then deploy the Application to
> the aggregate of systems from both Collections. In other words, build one
> Collection that encompasses both sets of systems, and deploy to that.
>
>
>
> Let the Global Condition(s) handle figuring out whether a particular
> Deployment Type is or isn’t applicable. Don’t try to do it yourself. That’s
> the old way of thinking.
>
>
>
> Cheers,
>
> Trevor Sullivan
>
> Microsoft PowerShell MVP
>
>
>
> *From:* [email protected] [mailto:
> [email protected]] *On Behalf Of *Jessie Twaddle
> *Sent:* Thursday, June 19, 2014 12:19 PM
> *To:* [email protected]
> *Subject:* [mssms] SCCM 2012 Application Deployment
>
>
>
> Hello all,
>
>
>
> I just have a question about Application Deployment in SCCM 2012. I setup
> and application and multiple deployment types for that application. I have
> one collection I want one deployment type to go to and another for a
> different deployment type. When I deploy the application to a collection
> or add it to a task sequence there is no option to select the deployment
> type. Similar to how I could select my program for a package. Am I
> missing something or can I just not do this with an application? It seems
> like I will need to create two separate “Applications” to be able to do
> this which is odd.
>
>
>
> Thank you for your time.
>
>
>
> Jessie Twaddle
>
>
>
>
>
>
