MSFN Forum: The First Of Many...Logon Script Problems - MSFN Forum

Jump to content



Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

The First Of Many...Logon Script Problems Rate Topic: -----

#1 User is offline   InTheWayBoy 

  • Friend of MSFN
  • PipPipPipPipPip
  • Group: Members
  • Posts: 709
  • Joined: 16-August 04

Posted 18 August 2005 - 03:59 AM

So I've recently moved into an IT position from my previous technican position...I'm pretty exhausted scrambling around learning most as I go, but that's how I work/learn best anyway.

So I've got a few questions, and I'm sure I'll have more...

On to the topic...logon scripts...specifically printers. I've got a small domain (20 computers) and two Canon network laser multifunction devices. Now before the roll over to the domain they all connected using a TCP port printer setup. I found that was more of a pain for me, so I decided to look into using the Canon's built-in servers and such. I've got them configured to list in the domain, but it's as their own computer, with the printer inside...\\canon\printer

Now what I want to do is install these via the logon script. At the moment I have the drivers laying on the domain controller and mapped to all the computers...I have many other sub-printers, and that share contains all the drivers. I'd like to keep it that way, but all the syntax I find on the web doesn't seem to take that into account.

Most assume the drivers are already loaded onto the client computer, which I haven't done. I can manually install it fine by just pointing the wizard to the mapped drive and it finds the .inf, but I can't find a way to do that in a script! I found one method, using some .dll (Don't have the page up anymore) that looked like it had a function to install the driver first, and then install the printer...but it never worked right.

I really like AutoIT, but I don't even know how to run that as a logon script properly...I have autoit.exe in the sys32 of every client, but I don't know if the file association is set. I have a VBS script that takes care of my drive mapping very nicely, so that's something to consider as well.

I was looking at this program called Policy Maker that supposedly does this via GPO, which would rule...I downloaded a mini free version, but it only allows custom registry GPO's. Of course, that didn't work either...but that was for a different problem.

I know the driver name, inf location, printer name, and share info for the printers...I just don't know how to line it all up...thanx!


Share this topic:


Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

1 User(s) are reading this topic
0 members, 1 guests, 0 anonymous users



All trademarks mentioned on this page are the property of their respective owners
Copyright © 2001 - 2011 msfn.org
Privacy Policy