It looks like a re-write of the scripts with some of the underlying structure within.
Couple of ideas that I am bouncing around..
(1) Use arrays or similar methodologies for Group detection.. I can envision the SELECT CASE INGROUP.. ENDSELECT getting rather large and cumbersome.
(2) One of the things that we have started to do is to use IP-Proximity checking. However, the problem is if you login from Administration or Underwriting, the printers should not be the same.
The thought process should be:
- Setup a "common" section that all users get routines to fit all machines.
- Use the IP Detection to filter out Site or Regional Operation Center.
- Based on the Group Detection, Detect the need for printers and other departmental needs.
I know that Shawn was part of a modular login script and maybe that would be the better solution?
Any other thoughts?
Thank you,
Kent