I think I misunderstood this whole concept. I was thinking that you deploy the deployment type to a device or user collection but after further examination, I see that you actually deploy the application. So my 2nd and 3rd scenarios will not work unless I separate each version with specific deployment rules. And that probably wouldn't be the right way to go about this. Am I right about that?
From: [email protected] [mailto:[email protected]] On Behalf Of Beardsley, James Sent: Monday, July 08, 2013 6:57 PM To: [email protected] Subject: [mssms] Application Model question I'm in the process of creating deployments for 8+ different versions of Quickbooks and I'm trying to understand the best way to do this. Which would be the recommended way based upon the SCCM 2012 Application Model? I'm sure all three of these would work but is there a technical reason for doing one over the other? I started creating one application for each version of Quickbooks (like below) and then within each application, I created the associated version as a new deployment type. Application: Quickbooks Premier 2013 D-Type: Quickbooks Premier 2013 (.msi) Application: Quickbooks Enterprise 2013 D-Type: Quickbooks Enterprise 2013 (.msi) Then I started thinking about the new Application Model and wondered if I should be grouping them in a different way. Should I group them by year? Application: Quickbooks 2013 D-Type: Quickbooks Premier 2013 (.msi) D-Type: Quickbooks Enterprise 2013 (.msi) Application: Quickbooks 2012 D-Type: Quickbooks Premier 2012 (.msi) D-Type: Quickbooks Premier 2012 Pro-Advisor Edition (.msi) Or should just create one application called "Quickbooks" and then within that application, have all of the versions as individual deployment types. Application: Quickbooks D-Type: Quickbooks Premier 2013 (.msi) D-Type: Quickbooks Enterprise 2013 (.msi) D-Type: Quickbooks Premier 2012 (.msi) D-Type: Quickbooks Premier 2012 Pro-Advisor Edition (.msi) Thanks, James Beardsley | Firm Technology Group Dixon Hughes Goodman LLP [Description: Description: Description: cid:[email protected]] ________________________________ 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.jpg>>
