![]() ![]() Log Off the desktop session (it is important to do this whilst the trace is running, as we can ensure that all processes are being finished and ended cleanly) The log file that is being written is limited to two megabytes in size, and when the content reaches this size, it will start overwriting the earliest entries. If it is appropriate to do so, make a note of the time that the unexpected behavior occurs:ĭo not stay logged on to the user session for too long, and be sure not to open applications or perform any actions that are not connected to the unexpected behavior you have seen. Perform the routine or action that contains the unexpected behavior that you would like RES Software to investigate. Now turn to the PC, Terminal Server or Hosted Virtual Desktop that is running Workspace Manager, and log in as usual: You can now go back to the Services snap-in and start the RES Workspace Manager service: You then need to create three String Values: HKEY_LOCAL_MACHINE => SOFTWARE => Wow6432Node => RES => Workspace Manager Note that, if you are on a 64-bit operating system, you will need to locate the necessary key in a different location: Scroll through HKEY_LOCAL_MACHINE => SOFTWARE => RES => Workspace Manager: Type the name or IP address of the PC, Terminal Server or Hosted Virtual Desktop running Workspace Manager that you would like to enable tracing on: In the registry editor, go to File and select Connect Network Registry… The next step is to make three minor changes to the registry in order to enable tracing.įrom the run dialogue box on your admin PC run regedit: Locate the RES Workspace Manager service, right click and select stop: In the Select Computer dialogue box, type the name or IP address of the PC, Terminal Server or Hosted Virtual Desktop running Workspace Manager that you would like to enable tracing on: Within the services console, right click Services in the left pane, and select Connect to another computer… On your admin PC, type services.msc from the run dialogue box: Under Authorized operation, make sure that both Execute and Modify options are both checked: In the Authorize file dialogue box fill out the text fields with the appropriate details:Īuthorized file (path): c:\temp\RESTrace.logĪdministrative note: (optionally) Enter a description of the exception. To create the exception, go to the RES Workspace Manager Console and navigate to Security => Global Authorized FilesĬlick Add at the bottom of the right pane: This functionality is only available in the Gold Edition of RES Workspace Manager so if you are not using the Gold Edition, or if you have not enabled this function, then please ignore this step: If you are using the Read-Only Blanketing functionality within RES Workspace Manager, you will need to create an exception in Global Authorized Files to allow the trace file to write. There are a couple of ways you can enable the detailed trace, but to keep it easy I always tend to enable tracing from an Admin PC (that way you don’t need to log on as admin, enable tracing, then log on as your test user. This helps us to better understand what is happening on a machine, and is often an essential part of pinpointing the cause of an unexpected behavior. ( Leave a comment ) Creating a Trace file/detailed Log in RES Workspace Manager 2011įrom time to time, the support team here at RES Software may ask you for a trace file or a detailed log. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |