how would you run 2 diff TS's or apply a diff OS using MDT?
On Fri, Sep 13, 2013 at 3:05 PM, Marcum, John <[email protected]> wrote: > I agree. Using the MDT database sounds like the best alternative to me. > > > * > ------------------------------ > * > > *John Marcum* > *Sr. Desktop Architect* > > *Bradley Arant Boult Cummings LLP* > ------------------------------ > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Jason Sandys > *Sent:* Friday, September 13, 2013 1:43 PM > *To:* [email protected] > *Subject:* [mssms] RE: Add machines to collections - OSD Slow - CAS > > > > MDT will assign the variables based on MAC address – very similar to > directly creating the variables on the objects in ConfigMgr. You simply add > the MAC to the MDT DB and define the variables to set. Depending on what > variables you are setting, you may need to extend the MDT DB, but that’s > trivial and commonly done. Then, MDT will set the values at run-time during > the TS using a simply query of DB based upon the system’s MAC address. > > > > You’ll never have to rely on collection updates for this. This is > explicitly what MDT was designed to do (among other things). You can also > get dynamic with it instead of “statically” assigning things and set > variables based on other things besides the MAC address like the name of > the machine (substrings of the machine name also), the location of the > machine, and the model of the machine. > > > > J > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Spinelli, Robert J > *Sent:* Friday, September 13, 2013 1:28 PM > *To:* [email protected] > *Subject:* [mssms] RE: Add machines to collections - OSD Slow - CAS > > > > Jason, > > > > I think we have 2 options: > > > > 1) Import the machine using OSD (no MDT) and assign our computer > variables, but we need to wait for the CAS collections to update which > could be 5-10 mins. > > 2) Use unknown computers and there would be no wait for collections > to update, but then we can’t be as granular with our computer variables and > would need to prompt the user. > > > > How would MDT give me the ability to use computer variable AND not have to > wait for the collection to update on the CAS. > > > > 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 | > [email protected] > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Jason Sandys > *Sent:* Friday, September 13, 2013 2:06 PM > *To:* [email protected] > *Subject:* [mssms] RE: Add machines to collections - OSD Slow - CAS > > > > If you know the MAC address, which you clearly do because you’re importing > them, then you can easily do that using the MDT database. > > > > J > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Spinelli, Robert J > *Sent:* Friday, September 13, 2013 12:51 PM > *To:* [email protected] > *Subject:* [mssms] RE: Add machines to collections - OSD Slow - CAS > > > > We’re creating the computer object and assign lots of different variables > to it for the task sequence, so the user is never prompted for anything. > > > > You wouldn’t be able to get the same functionality if you used unknown > computers is my assumption. No way to assign all the different variables > per computer as unknown is really only “one computer” if that makes sense. > > > > 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 | > [email protected] > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Marcum, John > *Sent:* Friday, September 13, 2013 12:15 PM > *To:* '[email protected]' > *Subject:* [mssms] RE: Add machines to collections - OSD Slow - CAS > > > > use unknown computers. > > > * > ------------------------------ > * > > *John Marcum* > *Sr. Desktop Architect* > > *Bradley Arant Boult Cummings LLP* > ------------------------------ > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Spinelli, Robert J > *Sent:* Friday, September 13, 2013 8:55 AM > *To:* [email protected] > *Subject:* [mssms] Add machines to collections - OSD Slow - CAS > > > > I know this has been discussed before, but can’t seem to fine the thread. > > > If you want to create a computer object for OSD on your CAS it takes a few > minutes before it actually shows up in the collection. I understand it’s > because the evaluation actually occurs on the primary and then comes back > up to the CAS. What have others down to speed this up? We’re developing a > front end so techs can build machines, but we don’t want to have something > that says “Please wait 5 minutes, etc .. etc”. > > > > We have over 200k clients, so we need a CAS (this is before someone asks > why we are using a CAS). > > > > 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 | > [email protected] > > > > 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 proprietary, privileged, confidential 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. > > > ------------------------------ > > > 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. > > > ------------------------------ > > > 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. > > > > 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 proprietary, privileged, confidential 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. This transmission may contain > information that is proprietary, privileged, confidential 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. > > > > > ------------------------------ > > > 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. > > ------------------------------ > > 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. > >
