Understanding How to Read a Userenv Log – Part 1

Understanding How to Read a Userenv Log – Part 2

Ask the Directory Services Team — Tue, 11 Nov 2008 22:43:48 GMT

As promised here is the second part of Understanding How to Read a Userenv Log (see Part 1 if you missed

re: Understanding How to Read a Userenv Log – Part 1

Mkline — Wed, 12 Nov 2008 22:59:03 GMT

Good article, SysPro software puts out a really great free utility that helps with reading userenv log files

I first heard about them from Group Policy MVP Darren MarElia's mailing list. I've liked the tool ever since.

http://www.sysprosoft.com/policyreporter.shtml

Policy Reporter V4

re: Understanding How to Read a Userenv Log – Part 1

Juoaquin — Wed, 07 Jan 2009 21:27:59 GMT

I have a problem that I think is quite unique. I get the regular Event 1521 userenv error but when debugging I notice how it mapped drive f:\ to the central profile location. Usually one of the consoles of our TS servers has the F:\ mapped to a different share on the network.

I just happened to notice that a bunch of profiles had populated that drive. WHen I disconnect the F:\ drive from the console I continue to get the profile loading error.

Somehow this all started when I chose the 'Enforce' option on the Group Policy Management - Default Domain Policy.

I have never see that happen where an actual drive has to be mapped on the Console in order for the roaming profiles to load.

Right now, as a workaround, I have to make sure the F:\ or E:\ [depending...] is mapped on the Console to the central location for users to logon successfully.

How do I fix this???

re: Understanding How to Read a Userenv Log – Part 1

Mark R. — Wed, 14 Jan 2009 03:04:43 GMT

By default when using roaming profiles the system will map a drive to the share where the user profile resides. Example would be \\server\share then change to the mapped drive such as the E drive. Once this is done it will change the directory to the users folder such as E:\user1. It will use this path to copy down the profile to the Terminal Server.

All logged on sessions should not overlap another one in anyway so it seems you have a very unique issue. From what you are saying the only thing I can think of is that the user that is logged on to the console with a mapped drive to the server that has the profiles creates a session to that server where otherwise the user is not able to without it.

Check the "Access this computer from the network" on the server that stores the profiles and verify that Administrators, Authenticated Users and Everyone has that user right.

re: Understanding How to Read a Userenv Log – Part 1

betech — Wed, 28 Jan 2009 19:28:16 GMT

I tried to open the file userenv.log with notepad++ ulraedit32 or woordpad. Only with notepad,I van see the file in plain text. Why ?

thanks

re: Understanding How to Read a Userenv Log – Part 1

NedPyle — Wed, 28 Jan 2009 19:33:55 GMT

If I recall, that file is stored in UNICODE format. Notepad knows to open those directly, your applications may need to be told to do so.

re: Understanding How to Read a Userenv Log – Part 1

NedPyle — Wed, 28 Jan 2009 19:34:57 GMT

Or maybe it was UTF-8, I don't recall, and don't have one handly. Look at what format notepad says it is in the Save As dialog.

Temporary User Profiles and the Citrix ICA Client

Ask the Directory Services Team — Thu, 21 May 2009 17:45:05 GMT

Howdy folks, Scott Goad again to talk about an issue that I thought you might find useful. I recently