[DUG] Terminal server/Win2003

[mike at webdata.co.nz]

Hello John.
How are you?

I found some info about this on the following website:
http://www.microsoft.com/technet/technetmag/issues/2006/05/WindowsConfidential/?topics=y

To summarize this it looks like you have to add your application name to
your trusted sites list in Windows 2003 Server.

>If you have a logon script that runs scripts from a network location,
that >network location needs to be listed in your intranet sites list.
Otherwise, >the ShellExecute function will display a warning that the
program you’re >about to run is from an untrusted source. Alternatively,
you can prefix the >script location with the script engine you want to
use. For example, if you >have a logon script that runs the script
\\atl-dc01\public\monitor.vbs, you >can either add \\atl-dc01 to your
trusted sites list, or you can change the >line in the script to wscript
\\atl-dc01\public\monitor.vbs, running the >wscript script engine
explicitly. (If you prefer it to be run as a console >script, then use
cscript instead of wscript.)


All the best,
Mike

> I have a related question - I have a client with a Windows 2003 server and
> TS, and I can log in using RDP.  I have  a backup and monitoring program I
> would like to offer them to run on the server, that from time to time does
> a
> shellexecute.   Windows 2003 server pops up a dialogue box with every such
> shellexecute asking if I want to run this.  Is there a way around this, or
> is there a Windows 2003 setting I need to change, as this program is most
> useful running unattended.
>
> I can run it on a workstation no problem with no  dialogues, so its not a
> biggie, but it is slower as it is accessing large files over the network.
>
>
>
> John
>
> _______________________________________________
> Delphi mailing list
> Delphi at ns3.123.co.nz
> http://ns3.123.co.nz/mailman/listinfo/delphi
>