You need to add the smsts.ini file referenced in the article to the boot images.
From: [email protected] [mailto:[email protected]] On Behalf Of Jeff Poling Sent: Thursday, July 31, 2014 14:28 PM To: [email protected] Subject: Re: [mssms] CCMLOGMAXSIZE Yeah, I guess I thought that the client install properties would take effect because the client install is before all the apps being installed in the TS. We are imaging from PXE, so I guess I need to look into modifying the boot image. On that note, it sounds like there is an XML file that needs modified? Is that still true? Thanks, Jeff On Thu, Jul 31, 2014 at 2:10 PM, Nash Pherson <[email protected]<mailto:[email protected]>> wrote: Yeah, unfortunately those Client Installation properties do not apply to the SMSTSlog because it is generated before the client is installed. You’ll have to add a smsts.ini file to your boot image if you are starting the task sequence from PXE or Boot Media: I don’t think things have really changed in CM12 from what is described in this CM07 article: http://blogs.technet.com/b/system_center_configuration_manager_operating_system_deployment_support_blog/archive/2011/10/12/how-to-change-logging-options-for-smsts-log-in-system-center-configuration-manager.aspx I hope that helps, Nash Nash Pherson Microsoft MVP, Enterprise Client Managment Senior Systems Consultant Now Micro [email protected]<mailto:[email protected]> Desk: 651-796-1168<tel:651-796-1168> Cell: 507-304-0946<tel:507-304-0946> [Description: Description: Description: Description: Description: Description: cid:[email protected]]<http://www.nowmicro.com/> [Speaker Signature]<http://www.devconnections.com/> IT/Dev Connections<http://www.devconnections.com/> September 15-19, 2014<http://www.devconnections.com/> [mms-reg]<http://mms.mnscug.org> Midwest Management Summit<http://mms.mnscug.org/> November 10-12, 2014<http://mms.mnscug.org/> From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Jeff Poling Sent: Thursday, July 31, 2014 1:56 PM To: [email protected]<mailto:[email protected]> Subject: [mssms] CCMLOGMAXSIZE My task sequence logs seem to be quite large and are rolling/overwriting. This prevents me from seeing the entire scope of the task sequence in the logs. So, I changed the client installation properties to include CCMLOGMAXSIZE = 5242880 and CCMLOGMAXHISTORY = 2. The history is now correct, but the logs are rolling over at 1 MB still. Has anyone seen this before? How do I get the 5MB log size to "stick." Also, I did confirm that the registry shows the correct settings once the task sequence is complete. Thanks, Jeff
