DAVID Systems

Portal  FAQ  Search  Usergroups  Register  Profile

Site Menu
 News (Home)
 Community Forum
 Knowledge Base & FAQ
 Product Lifecycle
 Software Download
 Desktop Searching

My DigaSystem
 TestTrack Login
 Contact Support
 Hardware return

Module Database
 All Parameters
Search Parameters

Log in


Remember Password 

I forgot my password

Don't have an account yet?
Join Us Now!

DAVID Systems - Customer Service Portal Forum Index -> General ->
Changes for Remote Desktops in Service Pack 3 for Windows XP

Post new topic   Reply to topic    Printer-friendly view
View previous topic :: View next topic  
Author Message

Joined: 23 Dec 2005
Posts: 437
Location: Berlin

PostPosted: Wed, 29. Oct 08, 19:30    Post subject: Changes for Remote Desktops in Service Pack 3 for Windows XP Reply with quote

Many administrators are using the Remote Desktop feature provided by Microsoft. The Adminpak.msi from Windows Server 2003 brings a good utility called "Remote Desktops" to manage multiple remote connections.

A big advantage of remote desktop handling is the possibility connecting to console. Normally this is done by MSTSC.exe -console which is an implemented feature of Adminpak's "Remote Desktops".

After installing Service Pack 3 of Windows XP there is a major change using command line options for MSTSC. Microsoft introduced a new option called -admin to be used instead of -console. The same situation exists in Windows Vista where the option "-admin" must be used.

Unfortunately Microsoft does not provide updates for Adminpak.msi for Windows Server 2003 operating systems to support this new feature. This lead to bad situations during normal work because the administrator does not get a warning that he won't connect to console.

As many servers have programs to be started from autostart folder this could lead to problems because connecting without console means doubled processes. In most cases the administrator will get error messages of the starting DigaSystem applications because of access violations caused by writing into log files which are owned by the processes from session 0.

A workaround is available by using a different product to Microsoft's Remote Desktops. Royal TS is a product running under DOT NET Framework 3.5 which fully supports the option "-admin" or "/admin". You can get this application for free from the developer: http://www.code4ward.net/main/

Please note that also running MSTSC from command line is affected because no error message is displayed in case of using "-console" or "/console".

A full setup of Microsoft's .NET Framework 3.5 including Service Pack 1 and all older version of .NET to be used for offline installation is available from this link:


Michael Burkhardt
DigaSystem Expert since 2001
Back to top
View user's profile Send private message Send e-mail Visit poster's website
Display posts from previous:   
Post new topic   Reply to topic    Printer-friendly view Page 1 of 1

Jump to:  

Forum Permissions
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum