How about modifying the script below to something like (and I've not tried this live, but it should work (or something like it)...) for /f %%a in (\\myserver\uncpath\appauthws.txt <file://\\myserver\uncpath\appauthws.txt> ) do if %clientname%==%%a goto authws goto notapproved :authws for /f %%a in (\\myserver\uncpath\appauthuser.txt <file://\\myserver\uncpath\appauthuser.txt> ) do if %username%==%%a goto auth goto notapproved :auth c:\program files\myprog\myprog.exe goto end :notapproved net send localhost You may not access this application :end Then, if you want to grant access, just add the workstation or user to the list. Jon Spriggs -- The presence of a "Fujitsu" address does not imply or assume that Fujitsu Services, Fujitsu or any other company containing the Fujitsu name uses or endorses this product. This email is purely a personal opinion. -----Original Message----- From: Landin, Mark [mailto:Mark.Landin@xxxxxxxxxxxxxxxx] Sent: 26 August 2004 14:56 To: thin@xxxxxxxxxxxxx Subject: [THIN] Re: Publishing applications to specific computers Application wrappers like this can be very flexible ways to add some more management capabilities for specific apps. For instance, we have a wrapper around our main application that allows us to lock out access to the application during certain processing periods. We have another published app, available only to admins, that enables or disables this lockout. Much handier than going in to CMC and disabling apps. _____ From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Robert K Coffman Jr - Info From Data Corporation Sent: Thursday, August 26, 2004 8:50 AM To: thin@xxxxxxxxxxxxx Subject: [THIN] Re: Publishing applications to specific computers I have some apps I limit to certain devices via a script such as: if %clientname%==ws1 goto auth if %clientname%==ws2 goto auth cls "E:\Program Files\Bulletin\Bulletin.exe" "E:\Program Files\Bulletin\projno.txt" logoff :auth start projstart.lnk exit where bulletin is a program that displays the contents of a text file as a message (ie. "This workstation not authorized") and projstart.lnk is a shortcut to the application. Not bulletproof but does the job. - Bob Coffman -----Original Message----- From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx]On Behalf Of Jeremy Thomas Sent: Thursday, August 26, 2004 4:12 AM To: 'thin@xxxxxxxxxxxxx' Subject: [THIN] Re: Publishing applications to specific computers No - applications are published straight to the start menu. We don't use NFuse or WI. I've tried adding a computername to a group, but that does not seem to work. My key problem is filetype associations. I need this to run on a per-device basis, not a per-user basis. I can control it per-user using groups, but not per device.