A method that requires no future coding would be to utilize an INI file. If your computers use a standard name format [ \:D ] then you could take the common part of the name with the Left() function. Thus, if the first 6 characters of a computer name uniquely identified the site, you could
$Location = Left(@WKSTA, 6)
to get the Site ID.
An INI file could exist on a central file server, so it only needs to be maintained in one place. Using an INI file allows you to add or change mappings without having to modify and redistribute your code each time you update your configuration.

Using an ini file similar to this :
 Code:
[PrinterMapping]
be_105=\\server\printshare
be_106=\\server\printshare
(and so on...)

The code to support this would be
 Code:
$Location = Left(@WKSTA, 6)
; printer table is in \\fileserver\share\printertable.ini
; If this is done during a login script, table would be
; \\domain\netlogon\printertable.ini
$Table   = '\\fileserver\share\printertable.ini'
$Printer = ReadProfileString($Table, 'PrinterMapping', $Location)
; use your favorite method to map $Printer

You could do your assignments by OU as well, although that would require more coding. The login script on my web site does mapping by group or OU membership - might give you some ideas if the INI file doesn't give you what you want.

Glenn
_________________________
Actually I am a Rocket Scientist! \:D