DanClark86
MIS
is it possible to automaticaly install a printer from NDS on a Windows 2000 workstation using the rundll32 printui.dll,PrintUIEntry command line interface?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Printer Installation 1
- Thread starter DanClark86
- Start date
- Status
- Thread starter
- #3
DanClark86
MIS
What is iprint , ndps and what is the syntax for creating a batch file or a script to run it so that you could automate the installation of printers on workstations, to include drivers and INF files
-
1
- #4
marvhuffaker
MIS
) Sometimes I get a good chuckle out of the questions that Windows people ask. No offense intended.With NDPS, you don't need a script. The whole point of NDPS is automated installation and centralized management.
Marvin Huffaker MCNE, CNE
Marvin Huffaker Consulting
- Thread starter
- #5
marvhuffaker
MIS
When you install the Novell Client on the workstation, you do a custom install and select "NOVELL DISTRIBUTED PRINT SERVICES". Then run through the rest.. This will put the agent that you need on your workstation.
Then, you create the Broker and Manager on the server, then create IP based print agents. Configure the printers with the drivers you need so they'll deploy. Add any drivers to the broker if they are not already there. Do this with NWADMN32.
Once you're done with that, In NWADMN32, select the container your users are in. (Or you can use groups). Go to the NDPS Remote Printer Management tab (or something like that, it's usually at the bottom). Add the printers to the list of printers to install.
viola. When the users login that are part of the context you assigned the printer to, they will automatically get the printer. Doesn't matter if there are 5 or 500 users. it's all automatic..
Marvin Huffaker MCNE, CNE
Marvin Huffaker Consulting
Then, you create the Broker and Manager on the server, then create IP based print agents. Configure the printers with the drivers you need so they'll deploy. Add any drivers to the broker if they are not already there. Do this with NWADMN32.
Once you're done with that, In NWADMN32, select the container your users are in. (Or you can use groups). Go to the NDPS Remote Printer Management tab (or something like that, it's usually at the bottom). Add the printers to the list of printers to install.
viola. When the users login that are part of the context you assigned the printer to, they will automatically get the printer. Doesn't matter if there are 5 or 500 users. it's all automatic..
Marvin Huffaker MCNE, CNE
Marvin Huffaker Consulting
fredericofonseca
IS-IT--Management
Many years ago I heard one that made me laugh.
A windows guy (that did not like Unix) wanted to know how to add hundred of users to a Windows Server.
The answer from the another guy was..
Install some unix utils on the windows machine and then use these to add the users in batch mode!
Even now some tasks on Windows systems are just HARD to do, and some of the Windows guys don´t know better.
Star from me for the good answer.
Regards
Frederico Fonseca
SysSoft Integrated Ltd
A windows guy (that did not like Unix) wanted to know how to add hundred of users to a Windows Server.
The answer from the another guy was..
Install some unix utils on the windows machine and then use these to add the users in batch mode!
Even now some tasks on Windows systems are just HARD to do, and some of the Windows guys don´t know better.
Star from me for the good answer.
Regards
Frederico Fonseca
SysSoft Integrated Ltd
- Thread starter
- #9
DanClark86
MIS
Which is why i am here asking about the rundll32 printui.dll,PrintUIEntry command In a windows enviroment it works great, and with a novel envirmoent it gets stuck at the driver.
marvhuffaker
MIS
Printer deployment the way windows does it is another fine example of Microsoft trying to change the definitions of "automatic", "Centralized," and "Deployment".
Marvin Huffaker MCNE, CNE
Marvin Huffaker Consulting
Marvin Huffaker MCNE, CNE
Marvin Huffaker Consulting
- Thread starter
- #11
DanClark86
MIS
I am not trying to debate which is better, Novel came out with the NDS tree first, yes and then MS made it better with AD. Yes MS has taken a lot of ideas from other products, but you know what, who cares!!! The software is what keeps most of us employed and you have to be able to adapt to changing technology, I am sure in the next 6 years we will all be saying crap about the newest ver. of Linux the same way most people say it about Microsoft. That aside, I am in a novel Environment with 2000 workstations. If i was in a NT Domain Environment I would be able to run rundll32 printui.dll,PrintUIEntry command in a script or I could publish the printer in AD but I am not in a Domain environment I am in a novel environment. So i will ask this again, "Using the rundll32 printui.dll,PrintUIEntry command in Novel, Can it work or not?
AD is no where near better than NDS. That's like saying that Windows Server is better than NetWare - never gonna happen!
-----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------
-----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------
ok - we're kind of flying off at a tangent
i cant see any reason that what you want to do will work - obviously i have never done it this way and i think in your situation ie netware server - 2000 stations - then its not the best way to go.
i'm assuming that all the printers in question are on jetdirects or something not shared on any pc etc - be it through windows or an nprinter.?
you say they are in nds - just now - what as?
what version of netware is it - ie 5 , 5.1 , 6 6.5
ndps is the better way to go here as it takes maybe 10 mins to setup and then about 2mins for each printer - after that if you want to add anyone or workstation or container - it's just a couple of mouse clicks
newer then you can extend the ndps to ipp - so the victims can also select the printer from web site - be it from a simple web page list or a map - still obviously secured so only people that are suppose to print can
i can try what you are wanting to do on monday but as i said i've never done it and assume it's quite unflexible - ie if you want to update the driver to all people with a few mouse clicks , or removing the printer etc
i cant see any reason that what you want to do will work - obviously i have never done it this way and i think in your situation ie netware server - 2000 stations - then its not the best way to go.
i'm assuming that all the printers in question are on jetdirects or something not shared on any pc etc - be it through windows or an nprinter.?
you say they are in nds - just now - what as?
what version of netware is it - ie 5 , 5.1 , 6 6.5
ndps is the better way to go here as it takes maybe 10 mins to setup and then about 2mins for each printer - after that if you want to add anyone or workstation or container - it's just a couple of mouse clicks
newer then you can extend the ndps to ipp - so the victims can also select the printer from web site - be it from a simple web page list or a map - still obviously secured so only people that are suppose to print can
i can try what you are wanting to do on monday but as i said i've never done it and assume it's quite unflexible - ie if you want to update the driver to all people with a few mouse clicks , or removing the printer etc
- Thread starter
- #14
DanClark86
MIS
it is Netware 5.1 But the rundll32 line i menoned earler is very flexible, put it into a batch file. and then change the switches if you need to do something special, like make a printer the default, change print drivers, save a print configuration to a file or recall a print configuration from a file.. and again in a strict NT enviroment it works like a charm but as soon as i do it from a Novel Server it only gets as far as requesting the driver. if i point to the driver, or if i am loading multiple printers, say 6 8150's then it will ask for the frist one and then smooth sailing on the next 5.
Thanks for your help
Thanks for your help
have you tried looking at ndps?
it is your best method here
i assume you rundll32 method - using the old (sorry not up on phrases ) pplug and print - ie there must be a central repository somewhere for the drivers to reside
i know there was a tid about getting netware clients to use this - it will be old - of the netware 4 era
it is your best method here
i assume you rundll32 method - using the old (sorry not up on phrases ) pplug and print - ie there must be a central repository somewhere for the drivers to reside
i know there was a tid about getting netware clients to use this - it will be old - of the netware 4 era
marvhuffaker
MIS
Dan, I'm going to try to explain this a little better but honestly, I feel like a lot of us are banging our heads on the wall here. I'm sure if you troubleshoot and search enough, you can find a way to make the rundll method work. But my point is that it in a Novell environment, it is not necessary.
In a NetWare environment, you are much better off to use the tools and methodologies that are integral to Netware. I know you are having problems letting the script thing go, but with NDPS, there are no scripts required. You can change drivers, change defaults, and lots of other stuff and there are no scripts required (Did I already say that).
Do you want to deploy a printer driver to 2000 workstations? No problem. Assign it to the container, boom, they have it. No sloppy scripts to debug, it just happens.
Do you want to update a driver on 2000 workstaitons that are already installed? No problem. Click UPDATE driver in the NDPS control page and it will be done next time they login.
Do you want to restrict users from getting to certain printers? Not a problem. Restrict printer access by group, container, or user.
What about decommissioning a Printer and removing it from 2000 workstations? No problem. Just remove it from the container or group and it's gone. No big deal.
How bout this... What if you want to prevent your users from installing printers manually? Can you do this with a script? Not even close. With NDPS you can configure it so only the assigned printers can be installed. If a user installs them manually, they will be removed automatically.
Do you follow this logic? You need to push your Microsoft way of thinking aside for a few minutes, and realize that there are easier ways to do things (than the Microsoft way). NetWare is the best example of this.
Again, no offense intended, but many microsoft people I deal with are very caught up on scripts and complex procedures that are absolutely necessary in a pure Windows environment. It's just the nature of the Windows operating system. But NetWare is so much easier to work with that I just laugh at how much time is spent on MS problems compared to how much time I spend on similar issues in a Netware environment.
This is the last comment I have on this thread. I highly encourage you to at least try an NDPS configuration, even if it's just in a test environment, so you can see how simple and easy it is. Just don't try to make it so complex. It's simple. very simple.
Marvin
Marvin Huffaker MCNE, CNE
Marvin Huffaker Consulting
In a NetWare environment, you are much better off to use the tools and methodologies that are integral to Netware. I know you are having problems letting the script thing go, but with NDPS, there are no scripts required. You can change drivers, change defaults, and lots of other stuff and there are no scripts required (Did I already say that).
Do you want to deploy a printer driver to 2000 workstations? No problem. Assign it to the container, boom, they have it. No sloppy scripts to debug, it just happens.
Do you want to update a driver on 2000 workstaitons that are already installed? No problem. Click UPDATE driver in the NDPS control page and it will be done next time they login.
Do you want to restrict users from getting to certain printers? Not a problem. Restrict printer access by group, container, or user.
What about decommissioning a Printer and removing it from 2000 workstations? No problem. Just remove it from the container or group and it's gone. No big deal.
How bout this... What if you want to prevent your users from installing printers manually? Can you do this with a script? Not even close. With NDPS you can configure it so only the assigned printers can be installed. If a user installs them manually, they will be removed automatically.
Do you follow this logic? You need to push your Microsoft way of thinking aside for a few minutes, and realize that there are easier ways to do things (than the Microsoft way). NetWare is the best example of this.
Again, no offense intended, but many microsoft people I deal with are very caught up on scripts and complex procedures that are absolutely necessary in a pure Windows environment. It's just the nature of the Windows operating system. But NetWare is so much easier to work with that I just laugh at how much time is spent on MS problems compared to how much time I spend on similar issues in a Netware environment.
This is the last comment I have on this thread. I highly encourage you to at least try an NDPS configuration, even if it's just in a test environment, so you can see how simple and easy it is. Just don't try to make it so complex. It's simple. very simple.
Marvin
Marvin Huffaker MCNE, CNE
Marvin Huffaker Consulting
- Status
Similar threads