Ccmsetup.exe SMSCACHESIZE= help 1

[skclark]

Hey guys,
I have my first two SMS sites running and doing what they are supposed to be, I think. After much reading and tweaking of permissions I believe I am ready to start testing some software deployment. Before I do I wanted to go in and increase the cache size on all the advanced clients from the default 250 to 1 gig or more.

After doing some research i found the command line option SMSCACHESIZE however, I have no idea how to implement it. Do I need to setup the client as a package so that I can use the command line option or is this pretty much a login script install only feature.

I also read about using the SMS FAQ on Microsoft.com

There are three ways to increase the size of the cache on the client:

• Installing the Advanced Clients using the installation property SMSCACHESIZE=. If this property is not set, the cache defaults to a maximum size of 250 MB.

• Manually changing the Amount of disk space to use on the Advanced tab in the Systems Management control panel.

• Distributing a script.

So I suppose I have two questions, how do I set the default cache size to a gig so that all new clients will be set to that. And how do I deploy a script to update my existing clients?

I have sample scripts that I was able to locate but am unsure of how to deploy, unless I call them from a login script, which could prove to be quite dificult based on the various login scripts we have in our company.

Thanks for your input.

 

[tbrennans]

http://www.tek-tips.com/viewthread.cfm?qid=848610

and then go through this....

Package - Program:
General:
Command Line: Have tried diff last one nr 1.
1. "cscript scriptname.vbs"
RUN:Normal
and select "user can interact with program"
After running: No action required
Requirements: This program can run on any platform.
Environment:
Program can run: Only when a user is logged on
Run mode: Admin
Drive mode: UNC

Advanced: just "Run once for the computer"

In Advertisments prop:

Schedule: Priority: "doesnt matter"

Adv.Cli.:
DP Available "Run Program from DP"
When no DP "Do not run program"


should work... Happy trails

 

[skclark]

Thank you, I will give it a try.

Does anyone know if it's possible to change the default cache size BEFORE installing the advanced client? I have 8 more sites to deploy and would prefer to have the cache setup accordingly from the start.

 

[ncotton]

From your own post

Installing the Advanced Clients using the installation property SMSCACHESIZE=. If this property is not set, the cache defaults to a maximum size of 250 MB.

You have to do this through commandline scripted installation and not from the site servers automatic push installation.


Hope this Helps.

Neil J Cotton
njc Information Systems
Systems Consultant

 

[willir]

I ran into this issue when deploying XP sp2. Default cache set to 250 MB and SP2 needs about 326 MB.

"We" found this vb script on the net...

On Error Resume Next
 
Dim oUIResManager 
Dim oCache 
Dim CacheSize
 
CacheSize=1000
 
Set oUIResManager = createobject("UIResource.UIResourceMgr")
 
If oUIResManager Is Nothing Then
    wscript.echo "Could not create Resource Manager - quitting"
    wscript.quit
End If
 
Set oCache=oUIResManager.GetCacheInfo()
 
If oCache Is Nothing Then
    Set oUIResManager=Nothing
    wscript.echo "Could not get cache info - quitting"
    wscript.quit
End If
 
oCache.TotalSize=CacheSize

Save as ReSizeCache.vbs and push to the desktop.

A little different than previous code supplied but it worked like a charm.

 

[skclark]

Thanks for the post willir. I think I am having a permissions problem. I am new to the SMS gig and am questioning if I am packaging the script properly. I setup the package and pushed it to my own workstation and I left notifications on so I could see what was going on. When I assign the package I get the popup and then the script doesn't do anything. If I run it manually from my desktop it runs and changes the cache size. So I figure I am doing something wrong, I thing it's a permissions issue but not sure how to grant rights to the package aside from the security tab. I will get it figured out. Looking for the log file that will tell me what’s going on right now.
Thanks

 

[skclark]

The problem I had with this was a permissions issue on the defaul share. I setup a network account and granted rights to the domain account and was able to successfully deploy the script.

I also found where to set the default cache size. It is as simple as adding the SMSCACHESIZE=2000 after the SMSSITECODE= under the client push installation properties in the advanced client tab.

I also figured out that you can modify the sms_def.mof file to include the cache size. Code included below:


#pragma namespace ("<\\\\.\\root\\cimv2\\sms>")



[SMS_Report (TRUE),

SMS_Group_Name ("Client Cache"),

Namespace ("root\\\\ccm\\\\Softmgmtagent"),

SMS_Class_ID ("MICROSOFT|CLIENTCACHE|1.0") ]





class CacheConfig : SMS_Class_Template

{

[SMS_Report (TRUE),key ]

string ConfigKey;

[SMS_Report (TRUE) ]

Boolean InUse;

[SMS_Report (TRUE) ]

string Location;

[SMS_Report (TRUE) ]

Uint32 Size;

};