What about the existing Printer Location Tracking features in AD, and
simply use the app to map printers based on their location ? Even if you
don't autmatically map printers, the PLT features automatically filter
printers for users based on their current location.
The main point in the article
.NET might be a little overkill depending on what the workstations can
handle (I've found .NET to be slow to start up on first run). Script or
batch file should be able to handle it just fine and it wouldn't be that
much code to write I would imagine. What logon script language are they
using
VB.Net app? No. VBscript - yes. Assuming all your clients are 2k/XP you don't have any
worries with a VBScript running. You have no confirmation taht every one of them has
.net loaded, and do you really wanna be screwing around with p/invoke anyway?
The way I did this was via some schema
