The differentiating factor is membership of an AD group. So I'll try out conditions like you mentioned. Thanks for the tip.
From: [email protected] [mailto:[email protected]] On Behalf Of Trevor Sullivan Sent: Wednesday, January 15, 2014 12:07 PM To: [email protected] Subject: RE: [mssms] Question about Deployment Types James, What exactly is the differentiating factor that determines which edition a user gets? This seems like a good opportunity to use global conditions under the Requirements tab for two Deployment Types on a single Application. You can use a PowerShell script to detect a user's group membership, and deploy the appropriate Deployment Type. You'll want to create two global conditions, one for each software "edition." This should allow you to consolidate everything to a single Application object. Cheers, Trevor Sullivan [cid:[email protected]] From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Beardsley, James Sent: Wednesday, January 15, 2014 10:57 AM To: [email protected]<mailto:[email protected]> Subject: [mssms] Question about Deployment Types I am creating an application in CM12 for "QuickBooks Premier" and "QuickBooks Premier Pro-Advisor". They are both the exact same content source, just depending on what serial number I supply it, it'll either be the regular version or the Pro-Advisor version. In this case, would I need to create two separate applications? I was thinking I could just create the "QuickBooks 2012" application and then have the Premier and Pro-Advisor be two different deployment types but I'm not seeing a way to deploy then separately. What's the recommended way to do that? Thanks, James ________________________________ IRS Compliance: Any tax advice contained in this communication (including any attachments) is not intended or written to be used, and cannot be used, for the purpose of (i) avoiding penalties imposed under the Internal Revenue Code or applicable state or local tax law or (ii) promoting, marketing, or recommending to another party any transaction or matter addressed herein. ________________________________ Confidentiality Notice: This e-mail is intended only for the addressee named above. It contains information that is privileged, confidential or otherwise protected from use and disclosure. If you are not the intended recipient, you are hereby notified that any review, disclosure, copying, or dissemination of this transmission, or taking of any action in reliance on its contents, or other use is strictly prohibited. If you have received this transmission in error, please reply to the sender listed above immediately and permanently delete this message from your inbox. Thank you for your cooperation. ________________________________ IRS Compliance: Any tax advice contained in this communication (including any attachments) is not intended or written to be used, and cannot be used, for the purpose of (i) avoiding penalties imposed under the Internal Revenue Code or applicable state or local tax law or (ii) promoting, marketing, or recommending to another party any transaction or matter addressed herein. ________________________________ Confidentiality Notice: This e-mail is intended only for the addressee named above. It contains information that is privileged, confidential or otherwise protected from use and disclosure. If you are not the intended recipient, you are hereby notified that any review, disclosure, copying, or dissemination of this transmission, or taking of any action in reliance on its contents, or other use is strictly prohibited. If you have received this transmission in error, please reply to the sender listed above immediately and permanently delete this message from your inbox. Thank you for your cooperation.
<<inline: image001.png>>
