FSLogix Unable to access logging directory

Андрей Михалевский 2,581 Reputation points
2021-05-29T17:49:45.293+00:00

Hi.

I installed the folder(LogDir): \DATTUM-FS-03\FSLogix\Logs\%computername%

After restarting the server, the folder is created, but the logs do not appear

100684-1.png

I gave full rights to everyone
also gave full rights to domain computers, domain users

If change the directory to \DATTUM-FS-03\FSLogix\Logs\DATTUM-RDP-12

All logs appear.

What the problem?

Update:

I am testing further.

I replaced the computername with the username

Folders began to be created and logs were written.

I also have a policy enabled: Access network as computer

Maybe this is the problem?

But I still don't understand why the variable works with the %username%, but not with the %computername%.

FSLogix
FSLogix
A set of solutions that enhance, enable, and simplify non-persistent Windows computing environments and may also be used to create more portable computing sessions when using physical devices.
463 questions
0 comments No comments
{count} votes

11 answers

Sort by: Most helpful
  1. Leila Kong 3,691 Reputation points
    2021-05-31T03:42:10.697+00:00

    Hello @Андрей Михалевский ,

    \computername\share\%computername% is recommended.
    important note: FSLogix will not append numerous computers logs to the same file, therefore the directory for each computer needs to be different.
    The %computername% directory in this example will be created if it does not exist. Note: If there are spaces in the path (directories or folders) use quote marks as appropriate.

    The UNC locations are usable as long as access is allowed to the location. The logs are written by the FSLogix service and this runs in the context of the computer. So the share must allow access to the computer account/object. The access must be granted at both the share and the NTFS permissions level.

    For your reference:
    Change the logging output location and permissions: https://social.msdn.microsoft.com/Forums/windowsserver/en-US/b9d37ab2-f754-434c-b487-afef7886f31c/change-the-logging-output-location-and-permissions?forum=FSLogix
    Logging and diagnostics: https://learn.microsoft.com/en-us/fslogix/logging-diagnostics-reference
    Using the FSLogix support tool to troubleshoot FSLogix Issues: https://social.msdn.microsoft.com/Forums/windows/en-US/0935e903-95d6-497a-9d9a-ae6ba5ece937/using-the-fslogix-support-tool-to-troubleshoot-fslogix-issues?forum=FSLogix

    Best regards,
    Leila


    If the Answer is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments No comments

  2. Андрей Михалевский 2,581 Reputation points
    2021-05-31T09:07:12.293+00:00

    I read it all. Why do you tell me this when I have a problem with the %computername%?

    0 comments No comments

  3. Leila Kong 3,691 Reputation points
    2021-06-01T01:52:21.467+00:00

    Hello @Андрей Михалевский ,

    Thanks for your response.

    What's your registry settings of FSLogix Logging and profile container?

    0 comments No comments

  4. Андрей Михалевский 2,581 Reputation points
    2021-06-01T05:26:36.67+00:00

    101258-1.png

    101147-2.png

    0 comments No comments

  5. Leila Kong 3,691 Reputation points
    2021-06-01T09:51:34.987+00:00

    Hello @Андрей Михалевский ,

    Thanks for your information.

    1.What's the advantage to set the value as %computername%?

    2.Can you provide complete process of reproducing the issue?

    3.If ComputerName is not specified, a random computer name is generated. This may be one possible cause.
    https://learn.microsoft.com/en-us/windows-hardware/customize/desktop/unattend/microsoft-windows-shell-setup-computername

    0 comments No comments