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]] On 
Behalf Of Underwood, Bob
Sent: Monday, October 21, 2013 11:50 AM
To: [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




Reply via email to