MFCOM script to export the current users of an application

Posted on April 27th, 2009

Sometimes is is necessary to have a list of users in a text file of which other scripts can be run. In this case I wanted a list of all users currently logged into a specific Citrix application in order to perform some other task.

The following MFCOM script will export all the users currently logged into a specified application and export them to a text file.

Set objFarm = CreateObject(“MetaFrameCOM.MetaFrameFarm”)

Dim ObjFSO, Objuserlist
Set objFSO = CreateObject(“Scripting.FileSystemObject”)
Set Objuserlist = objFSO.OpenTextFile(“c:\windows\temp\userlist.log”, 8, True)

objFarm.Initialize(1)

For Each objSession In objfarm.Sessions

if objsession.appname = (“My Application Name”) then
objuserlist.WriteLine(objSession.UserName)
End IF
Next

WScript.Echo “userlist created here – c:\windows\temp\userlist.log”

Substitute “My Application name” and the log file location as appropriate.

Save this as a .vbs file and run.

Tags: Citrix, export, list, mfcom, Presentation Server, scipt, user, vb
Filed under Scripts/Reg | 1 Comment »

Troubleshooting the Windows logon process

Posted on August 19th, 2008

To troubleshoot the logon process, debug logging can be enabled. This is useful in a Citrix environment as the logon could be slow and the debug log file will show where the pauses occur during the logon.

Microsoft Technet article can be found here: Q221833

Use Registry Editor to add or to modify the following registry entry:

Subkey: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Winlogon
Entry: UserEnvDebugLevel
Type: REG_DWORD
Value data: 10002 (Hexadecimal)

UserEnvDebugLevel can have the following values:

NONE 0×00000000
NORMAL 0×00000001
VERBOSE 0×00000002
LOGFILE 0×00010000
DEBUGGER 0×00020000

The default value is NORMAL|LOGFILE (0×00010001).

Note To disable logging, select NONE (0×00000000).

You can combine these values. For example, you can combine VERBOSE 0×00000002 and LOGFILE 0×00010000 to get 0×00010002. Therefore, if UserEnvDebugLevel is given a value of 0×00010002, LOGFILE and VERBOSE are both turned on. Combining these values is the same as using an OR statement.

0×00010000 OR 0×00000002 = 0×00010002

Note If you set UserEnvDebugLevel to 0×00030002, the most verbose details are logged in the Userenv.log file.

The log file is written to the %Systemroot%\Debug\UserMode\Userenv.log file. If the Userenv.log file is larger than 300 KB, the file is renamed Userenv.bak, and a new Userenv.log file is created. This action occurs when a user logs on locally or by using Terminal Services, and the Winlogon process starts. However, because the size check only occurs when a user logs on, the Userenv.log file may grow beyond the 300 KB limit.

The 300 KB limit cannot be modified.

Summary

RegKey: HKLM\Software\Microsoft\Windows NT\CurrentVersion\Winlogon\UserEnvDebugLevel

For full debug logging set to: 30002

Log file: c:\windows\debug\UserMode\userenv.log

Tags: debug, environment, logon, user, UserEnvDebugLevel, Windows 2003
Filed under Windows 2003 | 2 Comments »