The conversion wizard is still a pain as in most instances you still have to state a detection method as this info isn't available for the package you are converting.
> On 14 May 2015, at 20:07, Daniel Ratliff <[email protected]> wrote: > > Yeah, we have a project to migrate over, would love to do a quick turn of > everything. > > Daniel Ratliff > > From: [email protected] [mailto:[email protected]] > On Behalf Of Ryan > Sent: Thursday, May 14, 2015 2:30 PM > To: [email protected] > Subject: Re: [mssms] RE: Question from the Ignite Conference > > Only packages?? Want me to write something to convert them to applications > with the detection method? > > On Thu, May 14, 2015 at 1:17 PM, Daniel Ratliff <[email protected]> wrote: > Still packages here, 1500+ and counting. > > Daniel Ratliff > > From: [email protected] [mailto:[email protected]] > On Behalf Of Ryan > Sent: Thursday, May 14, 2015 2:13 PM > > To: [email protected] > Subject: Re: [mssms] RE: Question from the Ignite Conference > > Someone asked me to write the opposite of that (App->Package) as a right > click tool or something like that... I should get on that before applications > work 100% in task sequences! :-) > > Package -> App seems easy enough also. The detection method would be blank > (ok, it would be a script detection that didn't do anything) but otherwise > it'd be a fully functional application. > > John, you only write packages, no applications? I've seen most places write > everything as an application and then just convert the stuff they need in OSD > to packages. > > On Thu, May 14, 2015 at 12:54 PM, Daniel Ratliff <[email protected]> wrote: > Never used it but there is a Package Conversion Manager, not sure if it would > eliminate much of the pain though. > > https://www.microsoft.com/en-us/download/details.aspx?id=34605 > > Although its for SP1 only, and is out of support as of March 2014, it does > still work: > > http://gerryhampsoncm.blogspot.com/2014/03/configmgr-2012-sccm-2012-migration.html > > Daniel Ratliff > > From: [email protected] [mailto:[email protected]] > On Behalf Of Marcum, John > Sent: Thursday, May 14, 2015 1:50 PM > To: [email protected] > Subject: RE: [mssms] RE: Question from the Ignite Conference > > Good point… I was too heavily invested in packages before CU4 to have to go > back and change to applications would not be fun so I stick with packages. > > From: [email protected] [mailto:[email protected]] > On Behalf Of Ryan > Sent: Thursday, May 14, 2015 10:37 AM > To: [email protected] > Subject: Re: [mssms] RE: Question from the Ignite Conference > > They are much better since CU4. I use applications almost exclusively and > have not had problems. > > On Thu, May 14, 2015 at 10:02 AM, Marcum, John <[email protected]> wrote: > From what I’ve seen task sequences don’t like applications in general. I use > packages for OSD. > > > > From: [email protected] [mailto:[email protected]] > On Behalf Of [email protected] > Sent: Wednesday, May 13, 2015 12:47 PM > To: [email protected] > Subject: [mssms] Question from the Ignite Conference > > Hello > I vaguely remember hearing that CM2012 will have difficulty > installing/provisioning “Applications” (in task sequences) in Windows 10 as > well as Office 365 indicating Task Sequences have issues reading the rules > associated with those Applications. As I remember they indicated this will > NOT be fixed until ConfigMgr 2016 is released. > > Can anyone corroborate or provide additional information about this? > Thanks > > > > > > Confidentiality Notice: This e-mail is from a law firm and may be protected > by the attorney-client or work product privileges. If you have received this > message in error, please notify the sender by replying to this e-mail and > then delete it from your computer. > > > > > > The information transmitted is intended only for the person or entity to > which it is addressed > and may contain CONFIDENTIAL material. If you receive this > material/information in error, > please contact the sender and delete or destroy the material/information. > > > > > The information transmitted is intended only for the person or entity to > which it is addressed > and may contain CONFIDENTIAL material. If you receive this > material/information in error, > please contact the sender and delete or destroy the material/information. > > > > > The information transmitted is intended only for the person or entity to > which it is addressed > and may contain CONFIDENTIAL material. If you receive this > material/information in error, > please contact the sender and delete or destroy the material/information. >
