Migrating to Windows Server 2003 from Windows Server 2000 and using Remote Desktop Client

Migrating to Windows Server 2003 from Windows Server 2000 and using Remote Desktop Client

Post by Navodi » Fri, 15 Sep 2006 03:27:17


I am migrating an application from Windows 2000 server to Windows 2003
server.

The process followed on Windows 2000 server was as follows:
1. Open Client Connection manager.
2. create a new connection named say foo.
3. Set automatic logon option.
4. In the Program Tab for properties of foo, check "Start the following
program" and give path to a batch file which launches autocad (for example)
5. save connection
6. when i connect to "foo", a terminal window comes up with autocad launched
in it. In the terminal window only the autocad application is seen and the
task bar is not seen.

Now I am trying to replicate the same process in Windows 2003 server. The
steps I followed was:
1. Open Remote Desktop Connection.
2. Create a new connection say foo with ipaddress, username, passwd and
domain of that machine and check "save password".
3. In the Programs Tab, I check "Start the following program on connection"
and give path to a batch file which launches autocad.
4. save connection.
5. Now when I connect to "foo", a terminal window shows up showing the logon
process followed by the "Manage Your Server" dialog which shows up whenever
I log into that machine. Somehow the autocad application does not get
launched ! If i click on the batch file separately then the autocad
application shows up,
6. Also in the terminal window the task bar also shows up.

I resolved these issues by changing startup settings: getting autocad to be
launched and autohiding the taskbar whenever someone logs on. However is
there an alternate workaround to this kind of thing ? I mean why does the
"foo" connection not automatically start the AutoCAD file when it is
configured to do so ? Any help/hints would be appreciated. Thanks.