Setting up a small office print server
Setting up a print server in a small office.
As promised , I decided to clean up the mess with the printers. In total, I have 5 of them, and they all have MFPs with web access and network cards.
Initially, I did not like the fact that they were published in AD as horrible.
This happens when the system administrator publishes a printer in AD right on the user's work machine in order not to go far. The print servers were confused, some of them were local users' machines, which is not correct, as network printers must be connected to a constantly working print server. Accordingly, the task was to attach all the printers to one print server, which at the same time is an almost idle backup server. It is spinning on WS2003 R2.
After going through several ways, among which was the MS printer migrator utility, which seems to be suitable for ws2003 and having tried importing / exporting the database from remote machines, I saw that it did not bring any results.
And the print service on the server hung up and I had to restart it with my hands so that the printers appeared again.
In the end, I came across the fact that the printmanagement.msc snap-in from WS2008 for print management is also present in Windows7.
Through it, we can already connect remotely to local print servers, through which network printers are shared and installed.
What does this give us? We can install all the required printers on our server. They are all perfectly located through the built-in search.
Redistribute the shared access to the network MFP. Copy the required and missing drivers from one machine to another (they didn’t want to be at once, but they demanded to copy them to the local machine snap-in), assign access to users and at the same time attach automatic adding of printers to new users and new computers through the default domain policies.
It is also a plus that you can access the device web interfaces directly through the snap-in.
Migration works well with both the old OS (meaning XP) and the new.
From what did not work : automatic migration of all printers from one machine to another through import / export. It may be due to the fact that he did not begin to understand the correct location of the drivers (all the drivers of the printers in the branch should be installed in the same folder, preferably on all the operating system branches). This can be a problem in a large park of printers.
ps Sorry for photo hosting, but it is impossible to use Habrastorash.
As promised , I decided to clean up the mess with the printers. In total, I have 5 of them, and they all have MFPs with web access and network cards.
Initially, I did not like the fact that they were published in AD as horrible.
This happens when the system administrator publishes a printer in AD right on the user's work machine in order not to go far. The print servers were confused, some of them were local users' machines, which is not correct, as network printers must be connected to a constantly working print server. Accordingly, the task was to attach all the printers to one print server, which at the same time is an almost idle backup server. It is spinning on WS2003 R2.
After going through several ways, among which was the MS printer migrator utility, which seems to be suitable for ws2003 and having tried importing / exporting the database from remote machines, I saw that it did not bring any results.
And the print service on the server hung up and I had to restart it with my hands so that the printers appeared again.
In the end, I came across the fact that the printmanagement.msc snap-in from WS2008 for print management is also present in Windows7.
Through it, we can already connect remotely to local print servers, through which network printers are shared and installed.
What does this give us? We can install all the required printers on our server. They are all perfectly located through the built-in search.
Redistribute the shared access to the network MFP. Copy the required and missing drivers from one machine to another (they didn’t want to be at once, but they demanded to copy them to the local machine snap-in), assign access to users and at the same time attach automatic adding of printers to new users and new computers through the default domain policies.
It is also a plus that you can access the device web interfaces directly through the snap-in.
Migration works well with both the old OS (meaning XP) and the new.
From what did not work : automatic migration of all printers from one machine to another through import / export. It may be due to the fact that he did not begin to understand the correct location of the drivers (all the drivers of the printers in the branch should be installed in the same folder, preferably on all the operating system branches). This can be a problem in a large park of printers.
ps Sorry for photo hosting, but it is impossible to use Habrastorash.
')
Source: https://habr.com/ru/post/159721/
All Articles