RFC: Migrating Printers from NetWare - KiXtart.org

You are not logged in. [Log In] KiXtart.org website » Forums » KiXtart » Advanced Scripting » RFC: Migrating Printers from NetWare

Page 1 of 1

Topic Options

#65685 - 2002-05-23 08:55 PM RFC: Migrating Printers from NetWare
Les Les KiX Master Registered: 2001-06-11 Posts: 12734 Loc: fortfrances.on.ca	I am about to move all my NetWare printers over to a Win2k server in an NT4 domain and am looking for some advice. There are nearly 100 printers but I don't intend to automate their migration as this gives me the opportunity do some cleanup. I don't mind putting them in manually. While I have a mix of Wintendo, NT and Win2k, I will make these new printers only available to Win2k clients. All other clients will have to upgrade to Win2k to use them. What I have a problem getting my mind around is that unlike NetWare where an installed printer is available to every user that logs on to the box (per-machine), NT printers are not. They are setup per-user. We don't use roaming profiles (and don't want to) so when a user logs on to a box for the first time there will not be any printers defined. We have always defined the printers per-machine as our offices (and printers) are spread out around the mill. I also need some way to script the removal of the NetWare printers from the Win2k clients. Any suggestions? _________________________ Give a man a fish and he will be back for more. Slap him with a fish and he will go away forever.
Top

#65686 - 2002-05-23 09:14 PM Re: RFC: Migrating Printers from NetWare
Sealeopard Sealeopard KiX Master Registered: 2001-04-25 Posts: 11165 Loc: Boston, MA, USA	Printer connections are independend of roaming profiles. So, you could just use ADDPRINTERCONNECTION() to connect each user to their respective printers during logon. Printer drivers will get installed automatically. I would say that this is the preferred method. Alternatively, you can set up a local printer port that connects to your TCP/IP printers, this would be available to all users on that computer. _________________________ There are two types of vessels, submarines and targets.
Top

#65687 - 2002-05-23 09:26 PM Re: RFC: Migrating Printers from NetWare
Les Les KiX Master Registered: 2001-06-11 Posts: 12734 Loc: fortfrances.on.ca	Thanks Jens. I understand the rudiments of AddPrinterConnection() and am aware that local IP'd printers would be available to all. I'm thinking that I should setup my logon script to read an INI file that correlates each @WKSTA to specific printers. How then to best manage the INI file? _________________________ Give a man a fish and he will be back for more. Slap him with a fish and he will go away forever.
Top

#65688 - 2002-05-23 09:38 PM Re: RFC: Migrating Printers from NetWare
Howard Bullock Howard Bullock KiX Supporter Registered: 2000-09-15 Posts: 5809 Loc: Harrisburg, PA USA	How many printers, workstations, and printers/workstation? _________________________ Home page: http://www.kixhelp.com/hb/
Top

#65689 - 2002-05-23 09:45 PM Re: RFC: Migrating Printers from NetWare
Les Les KiX Master Registered: 2001-06-11 Posts: 12734 Loc: fortfrances.on.ca	Howard, 100 printers/plotters, IP'd (JetDirect, LPD). None are locally attached/shared. All served by 2 Win2k servers. 300+ workstations spread over 2km. Most have 2 or 3 printers defined while some may have a dozen. _________________________ Give a man a fish and he will be back for more. Slap him with a fish and he will go away forever.
Top

#65690 - 2002-05-23 10:16 PM

Re: RFC: Migrating Printers from NetWare

Sealeopard Offline

KiX Master

Registered: 2001-04-25
Posts: 11165
Loc: Boston, MA, USA

Les:

Here are examples of the .INI files that I am using for drive and printer mappings:

code:

; Mandatory printer connections for users
;
; Format:
;
;[Printer name]
;Printserver  = Name of the printserver
;GroupInclude = User groups to be included in the printer connection
;Model        = Model of the printer

[BAMA]
Printserver=MYOSIN
GroupInclude=MUL Members, MUL Administrators
Model=HP DeskJet 932C

code:

; Mandatory drive shares for users
;
; Format:
;
;[Drive letter]
;UNC              = UNC name of the drive share
;GroupInclude     = User groups to be included in the drive share
;CompExclude      = Computers to be excluded from the drive share (overrides GroupInclude)
;UserInclude      = Users to be included in the drive share (overrides CompExclude)
;NetworkType      = Type of network connection allowed for this share (LOCAL, LAN, VPN, DIALUP)
;DenyGuestAccess  = True if guests are not allowed to access this share

[L]
UNC=\\NMRC2\filesharezone
GroupInclude=Domain Users, Domain Admins
CompExclude=JUKEBOX, NMRCEXCHANGE, WEBSTER
NetworkType=LOCAL, LAN, VPN, DIALUP

_________________________
There are two types of vessels, submarines and targets.

Top

#65691 - 2002-05-23 10:19 PM Re: RFC: Migrating Printers from NetWare
Schuliebug Schuliebug Hey THIS is FUN Registered: 2002-01-18 Posts: 379 Loc: Netherlands	Do the printers have to be on the local subnet of the machine where the user is logged on? If not, maybe this is something? We generate an .ini file which has the following in it: [Printers] DomainGlobalGroupname=printerqueue, printerqueue, etc.. UserID=printerqueue, printerqueue, etc Printerqueues are represented as domain local groups. We add users or the domain global group the user is member of to that printerqueue group. Via some external tools and a dump of the SAM we generate the ini file, which is saved in a central place accessible by users. In the logon script we then read these values and connect the user/workstation to the queues. _________________________ Kind regards,
Top

#65692 - 2002-05-24 02:01 AM Re: RFC: Migrating Printers from NetWare
Les Les KiX Master Registered: 2001-06-11 Posts: 12734 Loc: fortfrances.on.ca	Schuliebug, All printers and workstations are in the same subnet. We don't use groups to control printers. Basically, anyone can print to any printer of their choosing except for one cheque printer. Every WKS is set to the closest HP LaserJet, the closest Xerox Document Centre, and the closest colour printer. Some also are set to large format printers and plotters. Bear with me as these are merely brain farts. I'm thinking of an INI file with sections for WKS name and keys for the printer shares they are to get. I'm paranoid so this would have to be read-only for the users. The down-side is that everyone has to diligently update this INI file. I have four co-workers that are too independent to follow procedure. I'm also paranoid so the INI would have to be read-only for the users so that means the users can't passively do it. I was thinking of triggering, from the logon script, an admin script which would rip the defined printers from the registry and merge them into the INI. Another thought is users could write to a temp INI that an admin script would merge into the RO one. That way manually added printers would also get added to the INI. The INI could also be centrally managed. Has anyone written a GUI (KiXForms maybe) to manage an INI file like this? _________________________ Give a man a fish and he will be back for more. Slap him with a fish and he will go away forever.
Top

#65693 - 2002-05-24 02:08 AM Re: RFC: Migrating Printers from NetWare
Sealeopard Sealeopard KiX Master Registered: 2001-04-25 Posts: 11165 Loc: Boston, MA, USA	I would definitely go for a centrally managed .INI file. How often do you move a printers/computers location? Those would be the only times the .INI file needs to be updated. _________________________ There are two types of vessels, submarines and targets.
Top

#65694 - 2002-05-24 02:20 AM Re: RFC: Migrating Printers from NetWare
Howard Bullock Howard Bullock KiX Supporter Registered: 2000-09-15 Posts: 5809 Loc: Harrisburg, PA USA	Les, I gather that printers are associated with computers and not users. Is that correct? I think that my approach would be individual *.kix file named after the computer. In each file would be an array that defines the printers that should be applied the computer. The reason I would go that direction instead of an INI file is that the entire INI is read for each ReadProfileString executed. I have that documented on the board somewhere. A simple: code: Call "%0\..\" + @wksta + ".kix" For Each $Printer IN $PrintArray ... Next This work equate to ~300 small files that can managed/generated with A Kixtart script from a master text file that is easily managed in a text editor. While READLINE write a new file for each line. _________________________ Home page: http://www.kixhelp.com/hb/
Top

#65695 - 2002-05-24 02:20 AM Re: RFC: Migrating Printers from NetWare
Les Les KiX Master Registered: 2001-06-11 Posts: 12734 Loc: fortfrances.on.ca	I'm with you on 'centrally managed' but fear it may become mismanaged when printers get manually added by users or coworkers. I've got to make the INI file management brain-dead-simple. The printers seldom move but the WKS are another matter. Well... not entirely true... my users and coworkers play a shell game with everything. _________________________ Give a man a fish and he will be back for more. Slap him with a fish and he will go away forever.
Top

#65696 - 2002-05-24 02:28 AM Re: RFC: Migrating Printers from NetWare
Howard Bullock Howard Bullock KiX Supporter Registered: 2000-09-15 Posts: 5809 Loc: Harrisburg, PA USA	Still OK. If you can't completely centrally manage this because your coworker will be adjusting the printers/workstation. Then your coworkers can still edit the individual files named after the @wksta. This would safeguard others from a screwup. You could then inverse the process if desired to make the central file for review of mass change. Then blow it all back out. If you use an editor that makes backup copies then there is also a quick recovery for those that screw up. _________________________ Home page: http://www.kixhelp.com/hb/
Top

#65697 - 2002-05-24 02:37 AM Re: RFC: Migrating Printers from NetWare
Sealeopard Sealeopard KiX Master Registered: 2001-04-25 Posts: 11165 Loc: Boston, MA, USA	Why not use WMI to collect all shared printers from all workstations though a central KiXtart script each night? This would at least notify you of changes/additions. _________________________ There are two types of vessels, submarines and targets.
Top

#65698 - 2002-05-24 04:43 AM Re: RFC: Migrating Printers from NetWare
Les Les KiX Master Registered: 2001-06-11 Posts: 12734 Loc: fortfrances.on.ca	Howard, You are correct. Printers associated with computers not users. Yes, I caught your post about INI files read in, but don't think an INI with 300 sections would be an issue. If it becomes an issue, I could break it out so each WKSTA has its own INI. I'd rather not manage and update 300 @WKSTA.kix files plus it would be more difficult to have an admin script auto-update them. INI file(s) would be easier to manage/update with an admin script. With regard to your last post, If users add their own printers the individual files wouldl never get edited. I fear my coworkers may not follow up with a script edit either. I think a script inventorying the printers and updating the INI(s) is the way to go. Whether I just rip them from the registry or use WMI as Jens suggests makes little difference. Jens, I run a 24/7 shop so nightly inventory is not the way to go. I'd probably trigger an admin script during logon as well as a scheduled one for those that never logoff. _________________________ Give a man a fish and he will be back for more. Slap him with a fish and he will go away forever.
Top

#65699 - 2002-05-24 04:56 AM Re: RFC: Migrating Printers from NetWare
Howard Bullock Howard Bullock KiX Supporter Registered: 2000-09-15 Posts: 5809 Loc: Harrisburg, PA USA	There are several twists that can be adapted to the @wksta.ini or @wksta.kix file scenario. You could still have a central INI or KIX file that defines the attributes for each workstation. You admin script could stage (write individual files for each workstation). This substantially reduces network traffic especially if each workstation will load this file 3-12 times by executing ReadProfileString 3-12 times. The choice of generating KixTart script '$a="p1","p2","p3"' etc. or an INI file per computer is personal taste. The management of either can be scripted. There could be some issues with this suggestion, but I think they could be resolved as I learn more of your implementation and desired outcome. One black hole for me is I really have no clue what the change process is. You suggest that coworkers could add printers. But does this mean they used Windows to add a printer to the computer or modified the config file. If they do the previous then you would need a method to capture that fact if the printer addition should be permanent. But who decides that? _________________________ Home page: http://www.kixhelp.com/hb/
Top

#65700 - 2002-05-24 04:32 PM Re: RFC: Migrating Printers from NetWare
Sealeopard Sealeopard KiX Master Registered: 2001-04-25 Posts: 11165 Loc: Boston, MA, USA	LLigetfa: Even if you are running a 24/7 shop, you might be able to run a printer inventory from a central computer whithout impacting network traffic and/or local CPU consumption too much. You would basically have a central script that remotely connects to each workstation with WMI, retrieves a list of shared printers, and compares it to the master shared printer list. If there is a discrepancy, you then trigger a response on that central computer. Thus, the central computer does all the work and connect/enumerate/disconnect should be over within 1 or 2 seconds for each remote workstation and the user will not notice it at all. _________________________ There are two types of vessels, submarines and targets.
Top

#65701 - 2002-05-24 04:49 PM Re: RFC: Migrating Printers from NetWare
Schuliebug Schuliebug Hey THIS is FUN Registered: 2002-01-18 Posts: 379 Loc: Netherlands	I too would definitely go for a central .ini file. Of course, keeping the .ini up-to-date and clean is an issue, but it is better than allow everyone to add every printers they can find :-) Dont know about a .ini editor, cause we use the mothodology ive described in my early reaction _________________________ Kind regards,
Top

#65702 - 2002-05-24 05:05 PM Re: RFC: Migrating Printers from NetWare
Les Les KiX Master Registered: 2001-06-11 Posts: 12734 Loc: fortfrances.on.ca	Schuliebug, That's the catch... we let anyone install any printer they want. I'm looking to capture the config to an INI file so if anyone logs on to the same WKS, they get the same printers. Also good for when we scrub a WKS and bring down a new image. The printers will all come back. I started a tread in the COM section on how to create a GUI INI editor. Topic: Paging Shawn... Need Crash Couse in KiXForms _________________________ Give a man a fish and he will be back for more. Slap him with a fish and he will go away forever.
Top

#65703 - 2002-05-28 07:57 PM Re: RFC: Migrating Printers from NetWare
Hawkman Hawkman Lurker Registered: 2002-05-28 Posts: 1 Loc: USA	I am in the process of deploying a script (also read as: This is NOT fully tested) that does the following: 1) Checks what printers a user has installed. 2) Makes note of the default printer. 3) Reads a text file that has the old print shares and the new print shares (in the following format: OldShare\|NewShare) 4) Deletes each old printer (on the old print server) 5) Adds the new corresponding printer (on the new print server) 6) If the old printer was the default, sets the newly-created on as the default. 7) And cycles through the list of printers currently installed on the workstation. The intent is to run this at login. If interested in the code, write me at bundahawk@hotmail.com
Top

#65704 - 2002-10-18 06:57 PM Re: RFC: Migrating Printers from NetWare
Les Les KiX Master Registered: 2001-06-11 Posts: 12734 Loc: fortfrances.on.ca	Update... I kinda mothballed this project but here's some of the code I came up with. It doesn't work as posted but it might give some idea of what's involved. Topic: Deleting Netware printers _________________________ Give a man a fish and he will be back for more. Slap him with a fish and he will go away forever.
Top

Page 1 of 1

Previous Topic View All Topics

Index Next Topic

Moderator: Glenn Barnas, NTDOC, Arend_, Jochen, Radimus, Allen, ShaneEP, Ruud van Velsen, Mart

Hop to:

Shout Box

Search the board with:
superb Board Search
or try with google:

	Web kixtart.org