Check Profile Management log files 编辑

Log files are useful when troubleshooting system behaviors. After checking Profile Management settings, enable Profile Management logging and reproduce the issue to check the log files.

Detailed steps are as follows:

  1. Enable Profile Management logging for all events and actions.
  2. Reproduce the issue on the machine.
  3. Check the Profile Management log file (for example, #computername#.#domainname#_pm.log) in the %SystemRoot%\system32\LogFiles\UserProfileManager folder for errors and warnings. Locate them by searching for the word ERROR or WARNINGS respectively.

    For more information about log files, see reference, later in this article.

  4. Check that the path to the user store is correct.
  5. Check that all information from Active Directory was read correctly.
  6. Check the time stamps to see whether there’s an action that takes too long.

Tip:

You can use Microsoft Excel to review Profile Management log files. For more information, see Knowledge Center article CTX200674.

Enable Profile Management logging

Enable Profile Management logging only when troubleshooting an issue in your Profile Management deployment. When you have the issue resolved, disable logging and delete the log files because they might include sensitive information.

You can enable Profile Management logging using:

  • A GPO in Active Directory

  • Citrix Studio

  • Workspace Experience Management (WEM)

To enable Profile Management logging and configure related settings using a GPO, follow these steps:

  1. Open the Group Policy Management Editor, and then create a Group Policy Object.

  2. Access Policies > Administrative Templates: Policy definitions (ADMX files) > Citrix Components > Profile Management > Log settings.

  3. Enable Profile Management logging as follows:

    1. Double-click Enable logging.
    2. Click Enabled.
    3. Click OK.
  4. Enable Profile Management to log all events and actions:

    1. Double-click Log settings.
    2. Select all events and actions. For more information about their descriptions, see Events and actions.
    3. Click OK.
  5. To change the default maximum size of the log file, follow these steps:

    1. Double-click Maximum size of the log file.
    2. Click Enable, and then enter a size in the Maximum size in bytes field.
    3. Click OK.

    Tip:

    When the maximum size is reached, Profile Management retains one backup file (for example, Logfilename.log.bak).

  6. Run the gpupdate /force command on the machine.

    These policies take effect on the machine.

For more information about log setting policies, see Profile Management policy descriptions and defaults.

Reference

This section provides the following information:

Log types

This table lists logs that you can use to troubleshoot Profile Management.

Informal NameLog File NameLocationType of Log Information
Profile Management log file#computername#.#domainname#_pm.log%SystemRoot%\system32\LogFiles\UserProfileManagerInformational messages, warnings, and errors, are written to the Profile Management log file. The domain name is the computer’s domain. If the computer name cannot be determined, this log file is called UserProfileManager.log. If the domain cannot be determined while the computer name is available, the log file is called #computername#_pm.log.
Profile Management configuration log file#computername#.#domainname#_pm_config.log%SystemRoot%\system32\LogFiles\UserProfileManagerThe configuration log file captures the GPO and .ini file settings even if logging is turned off. If the computer name cannot be determined it is called UserProfileManager_pm_config. If the domain cannot be determined while the computer name is available, the log file is called #computername#_pm_config.log.
Windows event logApplication.evtx%SystemRoot%\System32\winevt\Logs\The Windows events, which you view with the Microsoft Event Viewer, is used primarily for error reporting. Only errors are written to it.

Events and actions

This table lists events and actions that Profile Management can log.

TypeDescription
Common warningsAll common warnings.
Common informationAll common information.
File system notificationsOne log entry is created each time a processed file or folder is changed.
File system actionsFile system operations performed by Profile Management.
Registry actionsRegistry actions performed by Profile Management.
Registry differences at logoffAll registry keys in the hive HKCU that have been changed in a session. Important: This setting produces large amounts of output in the log file.
Active Directory actionsEach time Profile Management queries the Active Directory, an entry is written to the log file.
Policy valuesWhen the Profile Management service starts or a policy refresh occurs, policy values are written to the log file.
LogonThe series of actions during logon are written to the log file.
LogoffThe series of actions during logoff are written to the log file.
Personalized user informationWhere applicable, user and domain names are logged to dedicated columns of the log file.

Log file fields

Each line in the Profile Management log file has several fields, separated by semicolons. This table lists the log file fields.

FieldDescription
DateDate of the log entry
TimeTime of the log entry (including milliseconds)
SeverityEither INFORMATION, WARNING, or ERROR
DomainThe domain of the user (where applicable)
User nameThe name of the user (where applicable)
Session IDThe session ID (where applicable)
Thread IDThe ID of the thread that created this line
Function and descriptionThe name of the Profile Management function running at the time, and the log message

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。
列表为空,暂无数据

词条统计

浏览:1 次

字数:8941

最后编辑:7年前

编辑次数:0 次

    我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
    原文