Microsoft has released the following KB article:

Default logging variables unexpectedly used during task sequence in System Center 2012 R2 Configuration Manager

Symptoms:

Consider the following scenario:

•You set logging variables in the registry on a client that’s running the Microsoft System Center 2012 R2 Configuration Manager client. For example, you set the logging variables as follows:

◦MaxHistory: 10

◦MaxSize: 5,000,000

•You run a task sequence from a full Windows operating system to prepare for the installation in a Windows PE environment.

In this scenario, default logging variables are used during the task sequence. You expect the logging values that you set in the registry to be used instead.

Note When you view the TSAgent.log file, you find that logging variables were set to their default values. These values were used during the task sequence:

Setting LogMaxSize to 1000000 TSAgent
Setting LogMaxHistory to 1 TSAgent
Setting LogLevel to 0 TSAgent
Setting LogEnabled to 1 TSAgent
Setting LogDebug to 1 TSAgent

Full details at:

http://support2.microsoft.com/kb/2940326

Login to leave your feedback!

Leave a Reply