Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. Default logging variables unexpectedly used during task sequence in System Center 2012 R2 Configuration Manager

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

View products that this article applies to.

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

↑ Back to the top

Resolution

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website:
http://support.microsoft.com/contactus/?ws=support
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must have Cumulative Update 3 for System Center 2012 R2 Configuration Manager installed.

Restart information

You do not have to restart the computer after you apply this hotfix.

Note We recommend that you close Configuration Manager Administration Console before you install this hotfix package.

Hotfix replacement information

This hotfix does not replace any previously released hotfix.

File information
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

File nameFile versionFile sizeDateTimePlatform
Configmgr2012ac-r2-kb2940326-x64.mspNot Applicable7,241,72825-Aug-201401:10Not Applicable
Tsagent.dll5.0.7958.1402258,72825-Aug-201401:10x64
Tscore.dll5.0.7958.14022,495,14425-Aug-201401:10x64
Configmgr2012ac-r2-kb2940326-i386.mspNot Applicable5,832,70425-Aug-201401:10Not Applicable
Tsagent.dll5.0.7958.1402208,04025-Aug-201401:10x86
Tscore.dll5.0.7958.14021,843,37625-Aug-201401:10x86

↑ Back to the top

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top

References

Learn about the terminology that Microsoft uses to describe software updates.

↑ Back to the top

Keywords: kbqfe, kbautohotfix, kbfix, kbhotfixserver, kbsurveynew, kbexpertiseinter, kb, SCCM

↑ Back to the top

Article Info
Article ID : 2940326
Revision : 2
Created on : 4/26/2017
Published on : 4/26/2017
Exists online : False
Views : 372