[mssms] Maximum number of steps in an SCCM Task Sequence?
There's actually is a maximum number of steps, which is associated with the amount of memory in WMI to store the task sequence (which I think is what that TechNet article is referencing). Typical sequences could get around 300-400 steps before errors would start to appear (e.g., when trying to save the TS). A more complex sequence could max out much lower (e.g., 100). I've been told that a 64bit OS has no effect on the amount of memory available to WMI. Also, any potential tweaks/hacks to increase the WMI memory limits is not tested, thus not supported. J
Aaron
From: admin@lists.myITforum.com [mailto:admin@lists.myITforum.com] On Behalf Of Benjamin Derr
Sent: Wednesday, October 07, 2009 9:26 PM
To: mssms@lists.myitforum.com
Subject: Re: [mssms] Maximum number of steps in an SCCM Task Sequence?
Thanks Jason:
I don't think we're at the 4MB limit, but it is good to know.
On Wed, Oct 7, 2009 at 9:09 PM, Jason Sandys <Jason@sandys.us> wrote:
There is no limit on the actual number of tasks in the TS, but there is a cap on the size of TS: 4MB. Check this link for more details: http://technet.microsoft.com/en-us/library/bb932192.aspx.
Jason Sandys
You cannot build character and courage by taking away a man's initiative and independence.
-Abraham Lincoln
From: admin@lists.myITforum.com [mailto:admin@lists.myITforum.com] On Behalf Of Benjamin Derr
Sent: Wednesday, October 07, 2009 7:55 PM
To: mssms
Subject: [mssms] Maximum number of steps in an SCCM Task Sequence?
I haven't seen too much literature on this, but is there an upper limit to the number of steps in a TS? I am doing a server deployment for a customer, and we have approximately 40-50 steps. I was having issues with not all the package policies coming down - i.e., a review of the SMSTS.log showed that two package policies (OS Images, in this case), we not being downloaded/applied to the boot media TS process. I have deleted and re-imported the OS image packages in question, and will re-attempt the process tomorrow.
The odd thing is that the process was working well this morning, but not this afternoon, and may or may not be tied to adding a new set of images to the process. The overall number of steps did not change, just the packages.
Any thoughts?
==============
Missed an email? Check out the list archive:
http://myitforum.com/cs2/blogs/smslist/
==============
Missed an email? Check out the list archive:
http://myitforum.com/cs2/blogs/smslist/
==============
Missed an email? Check out the list archive:
http://myitforum.com/cs2/blogs/smslist/
Published with BlogMailr
Trackbacks
No Trackbacks
Comments
No Comments
