Synchronization, profiles, printers and scripting

  • Thread starter Thread starter weirdo.kid
  • Start date Start date
W

weirdo.kid

I am running a windows 2003 server domain. My users have redirected
folders ( "\\servername\share$\%username%\my
documents" ) and they all share the same desktop ( "\\servername
\desktop$" ). I have 1300 users and only 300 workstations, so a
workstation gets used by multiple users. Also there are 25 printer
around the network. Some plugged directly into the network, some to
workstations via usb cables and shared. Users have vbs logon script
that runs when they logon, and a vbs script that runs from group
policy that deletes all shared printers and mapped drives at logoff.
Here are my questions:

1. When a user logs off, it synchronizes the users files to "\
\servername\share$\%username%\my documents". Is there a way to hide
the "synchronization" windows that pops up at logoff?

2. Workstations get used by different users, so I never know where
which users is going to use which workstation. The problem comes in
with the vbs script. The script has the following line:
objNetwork.AddWindowsPrinterConnection "\\hod-1\printer" If now user
X logs onto workstation hod-1 he will get a scripting error saying
that he cannot connect to printer \\hod-1\printer. This being the
printer connected to the local machine. Is there a way to tell the
script to make provision for this?

3. because the users never stick to the same workstations, I cant
tell GP to deleted their profiles when they logoff, because it means
the next time they log onto the same machine, office will pop up with
"please wait will office is busy configuring". Is there a way around
then?

4. sometimes users switch workstations / printer off. This of cause
means, if there is anyone else that has a script pointing to that
printer... will get a error from the vbs scriot that runs. It also
means that the script does not run beyond that point. So if the
script error is then on line 2, none of the other printer will get
loaded. Is there a way to let the vbs script that skip that line,
not give an error, and load the rest of the printers?

weirdo.kid
 
weirdo.kid said:
2. Workstations get used by different users, so I never know where
which users is going to use which workstation. The problem comes in
with the vbs script. The script has the following line:
objNetwork.AddWindowsPrinterConnection "\\hod-1\printer" If now user
X logs onto workstation hod-1 he will get a scripting error saying
that he cannot connect to printer \\hod-1\printer. This being the
printer connected to the local machine. Is there a way to tell the
script to make provision for this?


You have to check if the script is running on the same computer as it is
connecting to, e.g.:

If Not objNetwork.ComputerName = "hod-1" Then
objNetwork.AddWindowsPrinterConnection "\\hod-1\printer"
End If
4. sometimes users switch workstations / printer off. This of cause
means, if there is anyone else that has a script pointing to that
printer... will get a error from the vbs scriot that runs. It also
means that the script does not run beyond that point. So if the
script error is then on line 2, none of the other printer will get
loaded. Is there a way to let the vbs script that skip that line,
not give an error, and load the rest of the printers?


Add "On Error Resume Next" (no quotes) statement as the first line of
the vbs script.
 
Back
Top