So trying to figure out how others do this:
Application called App1 The App can be installed using 2 command lines: Command line1: install.exe /test1 Command line2: install.exe /test2 You want to use App1 and target it to a collection based of a user group called: Contoso\App1 with 100 machines in it. 50 of the machines need command line: install.exe /test1 50 of the machines need command line: install.exe /test2 I can create 2 DT': DT1: install.exe /test1 DT2: install.exe /test2 In order to do requirements for both DT's its best to bounce of something local on the machine (ex: OS), but what if there really isn't anything different about the 100 machines 50 of them need to do a specific thing (ex: /test1) and the other 50 need to do some other specific thing (ex: /test2). I was thinking of doing a requirement based off of AD group, but from everything I read requirements shouldn't use AD groups since that could cause high load at evaluation time. Do others just create 2 apps even though it's the same app just with a different command line and then create 2 collections and target those 2 collections? Rob
