the answer is to del the data and havce something check to see when conditions are correct THEN begin imaging. the tech will not need to wait. It will of course add a bit of time, but they will not have to be in attendance
On Fri, Sep 13, 2013 at 2:24 PM, Daniel Ratliff <[email protected]> wrote: > That is the exact issues we are having. Given we have a CAS, I am not > sure there is a way around it. We are deploying to unknown computers, so > our PowerShell script deletes the record from the CAS and what we have > found is that the CAS then tells the primaries to delete the record. They > have to delete the record then replicate back up to the CAS before the > record is truly gone. This takes 5-10 minutes as well. **** > > ** ** > > I am testing a script currently to delete the record automatically from > the CAS and both our primaries. Just started on it yesterday and so far no > luck. :\**** > > ** ** > > *Daniel Ratliff* **** > > ** ** > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Spinelli, Robert J > *Sent:* Friday, September 13, 2013 3:02 PM > *To:* [email protected] > *Subject:* RE: [mssms] RE: Add machines to collections - OSD Slow - CAS*** > * > > ** ** > > We are trying to make it so the user has to enter in the minimum amount of > information to build a machine and the build starts quickly.**** > > ** ** > > Tech starts the image process up; we query some backend databases and pull > all the variables we need. Power shell script would create the computer > object in the imaging collection and set the variables on the computer. > What we’re seeing is the computer doesn’t show up in the imaging collection > for 5 minutes, sometimes longer. In a perfect world, we would like no > more than a 30 – 60 second wait for the build process to start. We have a > custom build we currently use, and there is no waiting, it just starts the > build. It will be hard to go into production with something that now adds > another 5 minutes, when they don’t have that wait currently.**** > > ** ** > > I appreciate any input you can provide.**** > > ** ** > > 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]] *On Behalf Of *Todd Hemsell > *Sent:* Friday, September 13, 2013 2:39 PM > *To:* [email protected] > *Subject:* Re: [mssms] RE: Add machines to collections - OSD Slow - CAS*** > * > > ** ** > > I can help with this but I need more info.**** > > **** > > What exactly are you trying to do? number of collections etc.**** > > ** ** > > On Fri, Sep 13, 2013 at 1:27 PM, Spinelli, Robert J < > [email protected]> wrote:**** > > 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]] *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. **** > > ** ** > > ** ** > > ** ** > > 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. **** > > ** ** > > 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. > >
