Client Cache size in a .wim dilemma

myITforum.com Community Forum

Home Forums Blogs Live Support chat Search Articles Wiki FAQ Email Lists Register Login My Profile Inbox Address Book My Subscription My Forums

Photo Gallery Member List Search Calendars FAQ Ticket List Log Out

All Forums RSS Feed Subscription:

Client Cache size in a .wim dilemma

View related threads: (in this forum | in all forums)

Logged in as: Guest

Printable Version

All Forums >> [Management Products] >> System Center Products >> System Center Configuration Manager >> Client Cache size in a .wim dilemma

Page: [1]

Message

<< Older Topic Newer Topic >>

Client Cache size in a .wim dilemma - 8/28/2008 8:43:17 AM

jbenoit

Posts: 22
Score: 0
Joined: 4/4/2008
Status: offline

How can I correct a CCM Client cache size within a .wim file?

I'm deploying PCs from a .wim where the client is the default (5012?) and my software installs later in the Task Sequence are stalling because they've run out. I've found scripts to both clear the cache and also expand it so it eventually does a retry of the installs and completes. However, this bandaid is a pretty lengthy delay in the process...

How can I go back and correct the issue so that the fix isn't needed? I've tried adding SMSCACHE=10000 to the Command Line of the Package that's called from the Setup Windows and ConfigMgr step in the TS, but that doesn't take. The Clients all keep the setting from the original client install in the .wim.

Post #: 1

RE: Client Cache size in a .wim dilemma - 8/28/2008 9:59:04 AM

jsandys

Posts: 530
Score: 17
Joined: 3/24/2005
From: San Antonio, TX
Status: offline

The cache size is stored in WMI and I don't see any way of modifying a WMI value in a WIM.

How did you capture the WIM? If you didn't use a build & capture TS, you should start, it makes fixing minor issues like this trivial. Building images by hand is so last century.

_____________________________

Jason
________________________________________
http://myitforum.com/cs2/blogs/jsandys/default.aspx

(in reply to jbenoit)

Post #: 2

RE: Client Cache size in a .wim dilemma - 8/28/2008 10:03:27 AM

jbenoit

Posts: 22
Score: 0
Joined: 4/4/2008
Status: offline

Ok. I'll continue using my post install "fix" then.

I don't have the experience or knowledge to use Build and Capture yet and get the result I need. School starts next Tuesday and I've got just about enough time to image and deploy these things without starting over. Thanks for the advice though.

(in reply to jsandys)

Post #: 3

RE: Client Cache size in a .wim dilemma - 8/28/2008 3:02:06 PM

rbennett806

Posts: 825
Score: 13
Joined: 6/14/2006
Status: offline

Well why not capture a new .WIM image, this time leaving out the SCCM client? The client shouldn't be incorporated into the image, but should be installed as part of the Task Sequence. I haven't had any cache issues with just the default settings, but if you want to modify things (in case you aren't already aware of them), the switches can be found here: http://technet.microsoft.com/en-us/library/bb680980.aspx

And I have to say, in my opinion I think building the image by hand is a lot smoother and easier than using the Build and Capture method - I do too much customization to make that worth my time. And your .WIM image (again, in my opinion) should really only contain the OS and the OS updates - everything else should be layered on during the OSD process.

Just my two cents...

(in reply to jbenoit)

Post #: 4