The Updatedeployment.log file is not storing enough information to allow us to troubleshoot problems, is there a setting somewhere that will allow that file to grow past its default maximum size?

hmm... maybe this still applies. Here's how to do that on an SMS 2.0 client. May or May not still apply. It's worth trying: http://support.microsoft.com/kb/259138Standardize. Simplify. Automate.

On all of your clients? You can try setting the CCMLOGMAXSIZE during ccmsetup as a command line switch: http://technet.microsoft.com/en-us/library/bb680980.aspxYou can also do a registry hack on existing clients - HKLM\Software\Microsoft\CCM\Logging\@GLOBAL Set the LogMaxSize value there. Test that out first, since I haven't done that to verify it works.

Setting HKLM\Software\Microsoft\CCM\Logging\@GLOBAL as Donnie suggestedshould work, but per client only. If all the clients have been deployed, and you can't use ccmlogmaxsize parameter anymore (unless you redeploy clients), youcould tryto set a group policy to set this registry key, just my 5 cent :)Thanks,Minh.Minh

Thanks Everyone!!

I know this post is old... yet I knocked up below vbscript, log files are now up to 500Kb in size… ' VBScript to change the Log File Size on a ConfigMgr client ' Change the 500000 to your required size in bytes Dim newLogMaxSize Dim sMachine newLogMaxSize = 500000 sMachine = "." set oCCMNamespace = GetObject("winmgmts://" & sMachine & "/root/ccm") Set oInstance = oCCMNamespace.Get("SMS_Client") set oParams = oInstance.Methods_("SetGlobalLoggingConfiguration").inParameters.SpawnInstance_() oParams.LogMaxSize = newLogMaxSize oCCMNamespace.ExecMethod "SMS_Client", "SetGlobalLoggingConfiguration", oParams ' End of script Do not change the registry value directly! The SDK shows the SetGlobalLoggingConfiguration Method in Class SMS_Client http://msdn.microsoft.com/en-us/library/cc146025.aspx