If you have been using eDirectory or Identity Manager on Windows servers, then you have probably noticed that some options, like NDSTrace for eDirectory, and driver tracing for IDM (remote loader for example) will not work when you click on the buttons, if you connect via RDP.


This is according to TID 10098906, because you need to be running in the console session. With Windows 2003 Server, you can try an “mstsc /console” command to launch the RDP client, which will do the trick.

The extra point to bring out is this:

If you do not want to disconnect and reconnect your RDP session, you can just do a Start:Run and execute the command “shadow 0” and you will be able to get at the console session.

0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this post.

Disclaimer: As with everything else at NetIQ Cool Solutions, this content is definitely not supported by NetIQ, so Customer Support will not be able to help you if it has any adverse effect on your environment.  It just worked for at least one person, and perhaps it will be useful for you too.  Be sure to test in a non-production environment.

Leave a Reply

No Comments
By: geoffc
Aug 8, 2007
3:17 am
Active Directory Authentication Automation Cloud Computing Cloud Security Configuration Customizing Data Breach DirXML Drivers End User Management Identity Manager Importing-Exporting / ICE/ LDIF Intelligent Workload Management IT Security Knowledge Depot LDAP Monitoring Open Enterprise Server Passwords Reporting Secure Access Supported Troubleshooting Workflow