[mssms] RE: OSD vs. MDT -- Let the debate begin (again)

2013-07-25 Thread Daniel Ratliff 
Will you be having other admins in there making task sequences, driver 
packages, packages, etc? You probably need OSD for RBA.

Do you have a large network that linked deployment shares wont scale to? You 
probably need OSD.

I think the size of your environment and its complexity are the two biggest 
deciding factors on whether to go with OSD or MDT.

Daniel Ratliff

From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On 
Behalf Of Spinelli, Robert J
Sent: Thursday, July 25, 2013 12:33 PM
To: mssms@lists.myitforum.com
Subject: [mssms] OSD vs. MDT -- Let the debate begin (again)

Now that SCCM 2012 R2 is introducing some new variables and new task sequence 
steps (ex: Set Dynamic Variables) would you go with OSD over MDT?

One of the main reasons we were going to go with MDT was because of the issue 
of not being able to build a machine in an untrusted forest:

http://blog.coretech.dk/kea/multi-forest-support-in-configmgr-2012-part-iithere-can-be-only-oneor/

This has been resolved in R2 with the ability to use multiple network accounts, 
so were now leaning back toward using OSD.

I was hoping for some input as OSD/MDT has always been my weakest skill.

Thank you.

Robert Spinelli | CTS | GTI | 575 Washington Boulevard, Jersey City, NJ, 07310, 
United States| T: +1.201.595.6820 | C: +1.917.538.6192 | 
robert.j.spine...@jpmchase.com


This communication is for informational purposes only. It is not intended as an 
offer or solicitation for the purchase or sale of any financial instrument or 
as an official confirmation of any transaction. All market prices, data and 
other information are not warranted as to completeness or accuracy and are 
subject to change without notice. Any comments or statements made herein do not 
necessarily reflect those of JPMorgan Chase & Co., its subsidiaries and 
affiliates. This transmission may contain information that is privileged, 
confidential, legally privileged, and/or exempt from disclosure under 
applicable law. If you are not the intended recipient, you are hereby notified 
that any disclosure, copying, distribution, or use of the information contained 
herein (including any reliance thereon) is STRICTLY PROHIBITED. Although this 
transmission and any attachments are believed to be free of any virus or other 
defect that might affect any computer system into which it is received and 
opened, it is the responsibility of the recipient to ensure that it is virus 
free and no responsibility is accepted by JPMorgan Chase & Co., its 
subsidiaries and affiliates, as applicable, for any loss or damage arising in 
any way from its use. If you received this transmission in error, please 
immediately contact the sender and destroy the material in its entirety, 
whether in electronic or hard copy format. Thank you. Please refer to 
http://www.jpmorgan.com/pages/disclosures for disclosures relating to European 
legal entities.


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.

[mssms] RE: OSD vs. MDT -- Let the debate begin (again)

2013-07-25 Thread Jason Sandys 
Although a pain point, not having multiple NAA is not a strict show stopper - 
you can use Kent's proposed solution or use pass through authentication. Thus, 
basing this decision on this one single limitation which can be worked around, 
is probably ... well, not the best.

As for the additional features coming in R2, MDT is now owned by the ConfigMgr 
product group and they are going to slowly begin ingesting the features into 
the native task sequence engine. R2 is the first wave/round of this.

J

From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On 
Behalf Of Spinelli, Robert J
Sent: Thursday, July 25, 2013 11:33 AM
To: mssms@lists.myitforum.com
Subject: [mssms] OSD vs. MDT -- Let the debate begin (again)

Now that SCCM 2012 R2 is introducing some new variables and new task sequence 
steps (ex: Set Dynamic Variables) would you go with OSD over MDT?

One of the main reasons we were going to go with MDT was because of the issue 
of not being able to build a machine in an untrusted forest:

http://blog.coretech.dk/kea/multi-forest-support-in-configmgr-2012-part-iithere-can-be-only-oneor/

This has been resolved in R2 with the ability to use multiple network accounts, 
so were now leaning back toward using OSD.

I was hoping for some input as OSD/MDT has always been my weakest skill.

Thank you.

Robert Spinelli | CTS | GTI | 575 Washington Boulevard, Jersey City, NJ, 07310, 
United States| T: +1.201.595.6820 | C: +1.917.538.6192 | 
robert.j.spine...@jpmchase.com


This communication is for informational purposes only. It is not intended as an 
offer or solicitation for the purchase or sale of any financial instrument or 
as an official confirmation of any transaction. All market prices, data and 
other information are not warranted as to completeness or accuracy and are 
subject to change without notice. Any comments or statements made herein do not 
necessarily reflect those of JPMorgan Chase & Co., its subsidiaries and 
affiliates. This transmission may contain information that is privileged, 
confidential, legally privileged, and/or exempt from disclosure under 
applicable law. If you are not the intended recipient, you are hereby notified 
that any disclosure, copying, distribution, or use of the information contained 
herein (including any reliance thereon) is STRICTLY PROHIBITED. Although this 
transmission and any attachments are believed to be free of any virus or other 
defect that might affect any computer system into which it is received and 
opened, it is the responsibility of the recipient to ensure that it is virus 
free and no responsibility is accepted by JPMorgan Chase & Co., its 
subsidiaries and affiliates, as applicable, for any loss or damage arising in 
any way from its use. If you received this transmission in error, please 
immediately contact the sender and destroy the material in its entirety, 
whether in electronic or hard copy format. Thank you. Please refer to 
http://www.jpmorgan.com/pages/disclosures for disclosures relating to European 
legal entities.

[mssms] RE: OSD vs. MDT -- Let the debate begin (again)

2013-07-25 Thread Spinelli, Robert J 
We're super large, super complex :)

Thank you.

Robert Spinelli | CTS | GTI | 575 Washington Boulevard, Jersey City, NJ, 07310, 
United States| T: +1.201.595.6820 | C: +1.917.538.6192 | 
robert.j.spine...@jpmchase.com<mailto:robert.j.spine...@jpmchase.com>

From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On 
Behalf Of Daniel Ratliff
Sent: Thursday, July 25, 2013 12:42 PM
To: mssms@lists.myitforum.com
Subject: [mssms] RE: OSD vs. MDT -- Let the debate begin (again)

Will you be having other admins in there making task sequences, driver 
packages, packages, etc? You probably need OSD for RBA.

Do you have a large network that linked deployment shares wont scale to? You 
probably need OSD.

I think the size of your environment and its complexity are the two biggest 
deciding factors on whether to go with OSD or MDT.

Daniel Ratliff

From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Spinelli, Robert J
Sent: Thursday, July 25, 2013 12:33 PM
To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com>
Subject: [mssms] OSD vs. MDT -- Let the debate begin (again)

Now that SCCM 2012 R2 is introducing some new variables and new task sequence 
steps (ex: Set Dynamic Variables) would you go with OSD over MDT?

One of the main reasons we were going to go with MDT was because of the issue 
of not being able to build a machine in an untrusted forest:

http://blog.coretech.dk/kea/multi-forest-support-in-configmgr-2012-part-iithere-can-be-only-oneor/

This has been resolved in R2 with the ability to use multiple network accounts, 
so were now leaning back toward using OSD.

I was hoping for some input as OSD/MDT has always been my weakest skill.

Thank you.

Robert Spinelli | CTS | GTI | 575 Washington Boulevard, Jersey City, NJ, 07310, 
United States| T: +1.201.595.6820 | C: +1.917.538.6192 | 
robert.j.spine...@jpmchase.com<mailto:robert.j.spine...@jpmchase.com>


This communication is for informational purposes only. It is not intended as an 
offer or solicitation for the purchase or sale of any financial instrument or 
as an official confirmation of any transaction. All market prices, data and 
other information are not warranted as to completeness or accuracy and are 
subject to change without notice. Any comments or statements made herein do not 
necessarily reflect those of JPMorgan Chase & Co., its subsidiaries and 
affiliates. This transmission may contain information that is privileged, 
confidential, legally privileged, and/or exempt from disclosure under 
applicable law. If you are not the intended recipient, you are hereby notified 
that any disclosure, copying, distribution, or use of the information contained 
herein (including any reliance thereon) is STRICTLY PROHIBITED. Although this 
transmission and any attachments are believed to be free of any virus or other 
defect that might affect any computer system into which it is received and 
opened, it is the responsibility of the recipient to ensure that it is virus 
free and no responsibility is accepted by JPMorgan Chase & Co., its 
subsidiaries and affiliates, as applicable, for any loss or damage arising in 
any way from its use. If you received this transmission in error, please 
immediately contact the sender and destroy the material in its entirety, 
whether in electronic or hard copy format. Thank you. Please refer to 
http://www.jpmorgan.com/pages/disclosures for disclosures relating to European 
legal entities.


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.


This communication is for informational purposes only. It is not intended as an 
offer or solicitation for the purchase or sale of any financial instrument or 
as an official confirmation of any transaction. All market prices, data and 
other information are not warranted as to completeness or accuracy and are 
subject to change without notice. Any comments or statements made herein do not 
necessarily reflect those of JPMorgan Chase & Co., its subsidiaries and 
affiliates.

[mssms] RE: OSD vs. MDT -- Let the debate begin (again)

2013-07-25 Thread Spinelli, Robert J 
I didn't say I was basing it off of one factor; I said it was one of the main 
reasons, there are few others also.  We could never do a pass thru 
authentication; the security guys would have our heads.

It does seem like there slowly getting MDT into SCCM; maybe R3 will have all 
the good features of MDT.

Thank you.

Robert Spinelli | CTS | GTI | 575 Washington Boulevard, Jersey City, NJ, 07310, 
United States| T: +1.201.595.6820 | C: +1.917.538.6192 | 
robert.j.spine...@jpmchase.com<mailto:robert.j.spine...@jpmchase.com>

From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On 
Behalf Of Jason Sandys
Sent: Thursday, July 25, 2013 12:46 PM
To: mssms@lists.myitforum.com
Subject: [mssms] RE: OSD vs. MDT -- Let the debate begin (again)

Although a pain point, not having multiple NAA is not a strict show stopper - 
you can use Kent's proposed solution or use pass through authentication. Thus, 
basing this decision on this one single limitation which can be worked around, 
is probably ... well, not the best.

As for the additional features coming in R2, MDT is now owned by the ConfigMgr 
product group and they are going to slowly begin ingesting the features into 
the native task sequence engine. R2 is the first wave/round of this.

J

From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Spinelli, Robert J
Sent: Thursday, July 25, 2013 11:33 AM
To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com>
Subject: [mssms] OSD vs. MDT -- Let the debate begin (again)

Now that SCCM 2012 R2 is introducing some new variables and new task sequence 
steps (ex: Set Dynamic Variables) would you go with OSD over MDT?

One of the main reasons we were going to go with MDT was because of the issue 
of not being able to build a machine in an untrusted forest:

http://blog.coretech.dk/kea/multi-forest-support-in-configmgr-2012-part-iithere-can-be-only-oneor/

This has been resolved in R2 with the ability to use multiple network accounts, 
so were now leaning back toward using OSD.

I was hoping for some input as OSD/MDT has always been my weakest skill.

Thank you.

Robert Spinelli | CTS | GTI | 575 Washington Boulevard, Jersey City, NJ, 07310, 
United States| T: +1.201.595.6820 | C: +1.917.538.6192 | 
robert.j.spine...@jpmchase.com<mailto:robert.j.spine...@jpmchase.com>


This communication is for informational purposes only. It is not intended as an 
offer or solicitation for the purchase or sale of any financial instrument or 
as an official confirmation of any transaction. All market prices, data and 
other information are not warranted as to completeness or accuracy and are 
subject to change without notice. Any comments or statements made herein do not 
necessarily reflect those of JPMorgan Chase & Co., its subsidiaries and 
affiliates. This transmission may contain information that is privileged, 
confidential, legally privileged, and/or exempt from disclosure under 
applicable law. If you are not the intended recipient, you are hereby notified 
that any disclosure, copying, distribution, or use of the information contained 
herein (including any reliance thereon) is STRICTLY PROHIBITED. Although this 
transmission and any attachments are believed to be free of any virus or other 
defect that might affect any computer system into which it is received and 
opened, it is the responsibility of the recipient to ensure that it is virus 
free and no responsibility is accepted by JPMorgan Chase & Co., its 
subsidiaries and affiliates, as applicable, for any loss or damage arising in 
any way from its use. If you received this transmission in error, please 
immediately contact the sender and destroy the material in its entirety, 
whether in electronic or hard copy format. Thank you. Please refer to 
http://www.jpmorgan.com/pages/disclosures for disclosures relating to European 
legal entities.



This communication is for informational purposes only. It is not intended as an 
offer or solicitation for the purchase or sale of any financial instrument or 
as an official confirmation of any transaction. All market prices, data and 
other information are not warranted as to completeness or accuracy and are 
subject to change without notice. Any comments or statements made herein do not 
necessarily reflect those of JPMorgan Chase & Co., its subsidiaries and 
affiliates.