👨🏿‍✈️ 👔 ♀️ Briefly on how to teach Brother MFPs to scan in Windows Server 😀 🐶 🧀

This is not even an article, but a note on how to use the network features of the Brother MFP Scanner in a Microsoft Windows Server environment. It will be about the full installation of the device driver. An example with the Brother MFC-L2700DRN will be considered . Officially, the scan function is only supported on desktop OS, server OS can only send to print . During the search for a solution, I often came across forums with similar problems of this particular manufacturer. It all comes down to using FTP, SMB or Email.

Therefore, a universal solution will be presented below.

Part 1. Modification of the installer

A complete driver package is required to install the scanner. Since the target OS in my case is Windows Server 2016, the installer will be for Windows 10 . Download, unpack.
Next, you need to find out which driver is responsible for the scanner. The install / MFC-L2700DN_series folder contains the Brinst_Common.ini file . In it we find the line EnableServer = 0 in the [Specification] section and change the value to 1. This parameter disables the check for server systems. Save the file. Next, find the line ScannerInfName = in the [Driver] section . This driver will be modified.

The driver file is in the install \ driver \ gdi \ 32_64 folder. It is necessary to do the following in it: find the [Manufacturer] section and add NTamd64.XY to the end of the list after the decimal point, where X and Y correspond to the version of your OS. You can check here . For Server 2016 corresponds to Windows 10 and is equal to NTamd64.10.0

Whole string

[Manufacturer]
%Manufact%=MODEL,NTx86.5.1.1,NTamd64.5.2.1,NTx86.6.0.1,NTamd64.6.0.1,NTx86.5.1,NTamd64.5.2,NTamd64.10.0

Next, in the [MODEL] section, by copying or replacing, add:

MODEL.NTamd64.10.0

[MODEL.NTamd64.10.0]
%DCL2500D.USB.SCN%  = DCL2500D.USB.SCN, USB\VID_04F9&PID_0321&MI_01
%DCL2520DW.USB.SCN% = DCL2520DW.USB.SCN,USB\VID_04F9&PID_0322&MI_01
%DCL2520D.USB.SCN%  = DCL2520D.USB.SCN, USB\VID_04F9&PID_0324&MI_01
%DCL2540DN.USB.SCN% = DCL2540DN.USB.SCN,USB\VID_04F9&PID_0326&MI_01
%DCL2540DW.USB.SCN% = DCL2540DW.USB.SCN,USB\VID_04F9&PID_0328&MI_01
%HLL2380DW.USB.SCN% = HLL2380DW.USB.SCN,USB\VID_04F9&PID_0330&MI_01
%DCL2560DW.USB.SCN% = DCL2560DW.USB.SCN,USB\VID_04F9&PID_0329&MI_01
%FAL2700DN.USB.SCN% = FAL2700DN.USB.SCN,USB\VID_04F9&PID_0335&MI_01
%MFL2700DW.USB.SCN% = MFL2700DW.USB.SCN,USB\VID_04F9&PID_0331&MI_01
%MFL2720DW.USB.SCN% = MFL2720DW.USB.SCN,USB\VID_04F9&PID_0337&MI_01
%MFL2720DN.USB.SCN% = MFL2720DN.USB.SCN,USB\VID_04F9&PID_0338&MI_01
%MFL2740DW.USB.SCN% = MFL2740DW.USB.SCN,USB\VID_04F9&PID_0320&MI_01
%MFL2700D.USB.SCN%  = MFL2700D.USB.SCN, USB\VID_04F9&PID_0373&MI_01
%DC7080.USB.SCN%    = DC7080.USB.SCN,   USB\VID_04F9&PID_0368&MI_01
%DC7080D.USB.SCN%   = DC7080D.USB.SCN,  USB\VID_04F9&PID_0367&MI_01
%DC7180DN.USB.SCN%  = DC7180DN.USB.SCN, USB\VID_04F9&PID_0369&MI_01
%DC7189DW.USB.SCN%  = DC7189DW.USB.SCN, USB\VID_04F9&PID_036A&MI_01
%MF7380.USB.SCN%    = MF7380.USB.SCN,   USB\VID_04F9&PID_036B&MI_01
%MF7480D.USB.SCN%   = MF7480D.USB.SCN,  USB\VID_04F9&PID_036C&MI_01
%MF7880DN.USB.SCN%  = MF7880DN.USB.SCN, USB\VID_04F9&PID_036D&MI_01
%MF7889DW.USB.SCN%  = MF7889DW.USB.SCN, USB\VID_04F9&PID_036E&MI_01
%MFL2705DW.USB.SCN% = MFL2705DW.USB.SCN,USB\VID_04F9&PID_0392&MI_01
%MFL2680W.USB.SCN%  = MFL2680W.USB.SCN, USB\VID_04F9&PID_03BB&MI_01
%MFL2700DN.USB.SCN% = MFL2700DN.USB.SCN,USB\VID_04F9&PID_03BC&MI_01
%DCL2520DW.NET.SCN% = DCL2520DW.NET.SCN,VID_04F9&PID_0322&NETSCN
%DCL2540DN.NET.SCN% = DCL2540DN.NET.SCN,VID_04F9&PID_0326&NETSCN
%DCL2540DW.NET.SCN% = DCL2540DW.NET.SCN,VID_04F9&PID_0328&NETSCN
%HLL2380DW.NET.SCN% = HLL2380DW.NET.SCN,VID_04F9&PID_0330&NETSCN
%DCL2560DW.NET.SCN% = DCL2560DW.NET.SCN,VID_04F9&PID_0329&NETSCN
%FAL2700DN.NET.SCN% = FAL2700DN.NET.SCN,VID_04F9&PID_0335&NETSCN
%MFL2700DW.NET.SCN% = MFL2700DW.NET.SCN,VID_04F9&PID_0331&NETSCN
%MFL2720DW.NET.SCN% = MFL2720DW.NET.SCN,VID_04F9&PID_0337&NETSCN
%MFL2720DN.NET.SCN% = MFL2720DN.NET.SCN,VID_04F9&PID_0338&NETSCN
%MFL2740DW.NET.SCN% = MFL2740DW.NET.SCN,VID_04F9&PID_0320&NETSCN
%DC7180DN.NET.SCN%  = DC7180DN.NET.SCN, VID_04F9&PID_0369&NETSCN
%DC7189DW.NET.SCN%  = DC7189DW.NET.SCN, VID_04F9&PID_036A&NETSCN
%MF7880DN.NET.SCN%  = MF7880DN.NET.SCN, VID_04F9&PID_036D&NETSCN
%MF7889DW.NET.SCN%  = MF7889DW.NET.SCN, VID_04F9&PID_036E&NETSCN
%MFL2705DW.NET.SCN% = MFL2705DW.NET.SCN,VID_04F9&PID_0392&NETSCN
%MFL2680W.NET.SCN%  = MFL2680W.NET.SCN, VID_04F9&PID_03BB&NETSCN
%MFL2700DN.NET.SCN% = MFL2700DN.NET.SCN,VID_04F9&PID_03BC&NETSCN

Part 2. Server and installation

A small feature of the installation is the need for two reboots. This is due to it, that the server needs to be put into "test mode" to disable the digital signature verification of drivers. After installation, turn everything back on and it will work.

Open the command line or PS (as you like) and enter bcdedit -set TESTSIGNING ON , after which we reboot the system.

In the standard way, run the Brother installer at install \ MFC-L2700DN_series \ setup.exe BUT! do not install the network printer driver, otherwise the installer will throw out an error and you will have to manually remove the unknown device (it is installed by adding a printer). The remaining items to taste.

After the installation is complete, open the command line or PS and enterbcdedit -set TESTSIGNING OFF , then reboot the system. Checking the scanner.

PS: thanks to the Charles Wastell blog anonymous for pushing in the right direction.

Briefly on how to teach Brother MFPs to scan in Windows Server

Part 1. Modification of the installer

Part 2. Server and installation

More articles: