I am migrating an application from Windows 2000 server to Windows 2003\nserver.\n\nThe process followed on Windows 2000 server was as follows:\n1. Open Client Connection manager.\n2. create a new connection named say foo.\n3. Set automatic logon option.\n4. In the Program Tab for properties of foo, check "Start the following\nprogram" and give path to a batch file which launches autocad (for example)\n5. save connection\n6. when i connect to "foo", a terminal window comes up with autocad launched\nin it. In the terminal window only the autocad application is seen and the\ntask bar is not seen.\n\nNow I am trying to replicate the same process in Windows 2003 server. The\nsteps I followed was:\n1. Open Remote Desktop Connection.\n2. Create a new connection say foo with ipaddress, username, passwd and\ndomain of that machine and check "save password".\n3. In the Programs Tab, I check "Start the following program on connection"\nand give path to a batch file which launches autocad.\n4. save connection.\n5. Now when I connect to "foo", a terminal window shows up showing the logon\nprocess followed by the "Manage Your Server" dialog which shows up whenever\nI log into that machine. Somehow the autocad application does not get\nlaunched ! If i click on the batch file separately then the autocad\napplication shows up,\n6. Also in the terminal window the task bar also shows up.\n\nI resolved these issues by changing startup settings: getting autocad to be\nlaunched and autohiding the taskbar whenever someone logs on. However is\nthere an alternate workaround to this kind of thing ? I mean why does the\n"foo" connection not automatically start the AutoCAD file when it is\nconfigured to do so ? Any help/hints would be appreciated. Thanks.