Results 1 to 3 of 3
  1. #1
    4 Star Lounger
    Join Date
    Apr 2001
    Location
    Tunbridge Wells, United Kingdom
    Posts
    405
    Thanks
    0
    Thanked 0 Times in 0 Posts
    I have users that work at two different sites (on the same LAN), who all have roaming profiles. I use group policy (2003 Domain) to deploy the printers at each site to the computers (XP) according to their location. A logon script (vbs) then sets the default printer to be the one closest to the computer the user has logged on to.

    I have set the script to list the installed printers as one of the first tasks and then set the default. This sometime fails, with the list of printers being empty - though all the printers are there, if you look in Printers and Faxes after the script has run. If the script is then run again manually, it works as intended.

    Is there a way to ensure that the user's printer list has been populated before the script tries to set the default? Does anyone know what process copies the per machine settings to the user?
    We never really grow up, we only learn how to act in public.

  2. #2
    Administrator
    Join Date
    Mar 2001
    Location
    St Louis, Missouri, USA
    Posts
    23,593
    Thanks
    5
    Thanked 1,059 Times in 928 Posts
    [quote name='SparkyPatrick' post='762264' date='27-Feb-09 10:32'][/quote]

    Seems as though you might have a slight timing issue with some networking component not initializing quickly enough all the time. Can you put a Sleep - fixed delay in the script and adjust the delay until you find something that works consistently?

    Joe
    Joe

  3. #3
    4 Star Lounger
    Join Date
    Apr 2001
    Location
    Tunbridge Wells, United Kingdom
    Posts
    405
    Thanks
    0
    Thanked 0 Times in 0 Posts
    Joe,

    Thanks for the response. I could put in a delay, but users are already complaining at how long the logon scripts take to run! I would like to avoid that if I can. If I knew what the process or component was that is missing, I could have a routine to check it and then wait or kick it off.

    The only other thing I can think of is to install a dummy printer to all PCs and check for it before going on to set the default, but it's not a very elegant solution.

    Cheers,
    We never really grow up, we only learn how to act in public.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •