The variable should have the same behavior on that step regardless of its use. You say you don’t see it retrying but that you haven’t upgraded to R2 yet?
Aaron From: [email protected] [mailto:[email protected]] On Behalf Of Craig Andrew (OIZ) Sent: Tuesday, October 22, 2013 12:29 AM To: [email protected] Subject: AW: [mssms] How fast are SSDs? Hi Aaron, Thanks for the info. Can you say that this variable works when using install applications from dynamic variables? When you install a single app from the install app step then there is a default retry which this tsvariable says it leverages, but when using variables I don’t see the app retrying, it fails straight away. Ps. Havent upgraded to r2 yet, so havent tested. I have heard of a couple of issues when upgrading, like the wds thread here and a very prominent sccm guru who told me after upgrading that he couldn’t install the r2 client agent… I need to follow up on that last one. Andrew Von: [email protected] [mailto:[email protected]] Im Auftrag von Aaron Czechowski Gesendet: Dienstag, 22. Oktober 2013 07:41 An: [email protected] Betreff: RE: [mssms] How fast are SSDs? That’s a fair assessment. We spent a lot of time looking at the issue, and it’s not a simple matter. If folks are still hitting this issue and using R2, adjust this variable to something larger than one minute. Aaron From: [email protected] [mailto:[email protected]] On Behalf Of Andre Vrankovic Sent: Monday, October 21, 2013 10:08 PM To: [email protected] Subject: RE: [mssms] How fast are SSDs? Thanks for the link. Okay. So that is setting a timeout for the application before it retries, rather than just failing like it did pre R2. If it still isn’t working for people they might need to set it to more than the default which is 1 minute. Would have been nice if they fixed the issue with locationservices rather than patch the application installation operation, seems like a workaround similar to the ping wait rather than a true fix. Unless I’ve got that wrong? Dre. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Aaron Czechowski Sent: Tuesday, 22 October 2013 2:52 PM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] How fast are SSDs? The extent of the documentation on it is what Craig pasted below (from http://technet.microsoft.com/en-us/library/hh273375.aspx). And no recommended value, you’ll need to determine what’s appropriate for your environment. Too many variables to provide a specific value for general use. Aaron From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Andre Vrankovic Sent: Monday, October 21, 2013 8:25 PM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] How fast are SSDs? Is there some documentation around the variable? Do you set it at the collection? From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Johan Arwidmark Sent: Tuesday, 22 October 2013 9:05 AM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] How fast are SSDs? What’s the recommended setting for SSD’s? / Johan From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Aaron Czechowski Sent: den 21 oktober 2013 23:42 To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] How fast are SSDs? Bob, are you using the new SMSTSMPListRequestTimeout variable? This is the “fix” in R2. Craig, this variable should apply in your scenario as well. Aaron From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Underwood, Bob Sent: Monday, October 21, 2013 11:50 AM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] How fast are SSDs? Has anyone seen evidence that this might indeed have been fixed in R2? From what we’re seeing here, it’s still an issue. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Johan Arwidmark Sent: Thursday, October 17, 2013 6:10 AM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] How fast are SSDs? That’s a known issue. I have been told it’s addressed in R2, but I haven’t tested yet. Keep the pause for now ☺ / Johan From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Craig Andrew (OIZ) Sent: den 17 oktober 2013 05:02 To: [email protected]<mailto:[email protected]> Subject: [mssms] How fast are SSDs? Hi All, Thought i would share something with you all. We are using ConfigMgr2012 to build Win7 OSD. Now we have just received machines with SSD and the download time and boot time is so fast that after the Install Updates step the OS reboots and starts up the OS and the TSEngine so quickly that the domain has not had time to react and verify the machine account. The next step, install Applications, fails because the client cannot get the site information from AD and subsequently gets nothing from location request and cannot download anything. After putting in a wait step before the applications step the build runs through without problem. You are only ever as fast as the slowest component. Looking at built in TS variables, if it was just an application install step then this might help: SMSTSMPListRequestTimeout: For System Center 2012 R2 Configuration Manager only: Use this variable to specify how much time a task sequence waits before it retries to install an application after it fails to retrieve the management point list from location services. By default, the task sequence waits one minute before it retries the step. This variable is applicable only to the Install Application task sequence step. But our step is install applications from list of variables and this appears not to retry any application, rather it fails immediately. The wait step is just a quick fix, I am looking at variables and retry settings, and possible a script that checks availability of the domain before continuing. Maybe this TS variable will work with install from variable. Andrew [CONFIDENTIALITY AND PRIVACY NOTICE] Information transmitted by this email is proprietary to Medtronic and is intended for use only by the individual or entity to which it is addressed, and may contain information that is private, privileged, confidential or exempt from disclosure under applicable law. If you are not the intended recipient or it appears that this mail has been forwarded to you without proper authority, you are notified that any use or dissemination of this information in any manner is strictly prohibited. In such cases, please delete this mail from your records. To view this notice in other languages you can either select the following link or manually copy and paste the link into the address bar of a web browser: http://emaildisclaimer.medtronic.com ________________________________ This message is for the designate recipient only and may contain confidential, proprietary or otherwise private information. If you have received it in error, please notify the sender by return e-mail immediately and delete the original. Any review, re-transmission, disclosure, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other then the intended recipient is prohibited and may result in legal proceedings against you. ________________________________ This message is for the designate recipient only and may contain confidential, proprietary or otherwise private information. If you have received it in error, please notify the sender by return e-mail immediately and delete the original. Any review, re-transmission, disclosure, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other then the intended recipient is prohibited and may result in legal proceedings against you.
