MX-M503N and Server 2016

[JLSam]

Issue is resolved. For future techs.

We deliver an MX-M503N, end user says their IT (Cybersecurity Networking Professional) will do all installation for print and scan. Get a call, that they are not able to deploy drivers from their Server 16.

I said what the hell, and I stopped by to see if I can help the guy. Should be easy right? So he does things correctly, he set up the driving under printing policy, set up the driver, and deployed it. Uploaded additional drivers for 32bit. On the end user side, we would click on new printer, and it would say Driver Unavailable. I checked the ports in the main driver to make sure the port is not a hostname or WSD, but no... it's standard IP.

After wasting an hour I noticed that the driver from our website, says support for up to server 2012. I didn't think it would make sense, but we brought a MX-3640 where on the driver it says "Active Directory" and "Server 16" is supported. We did the same thing and it deployed beautifully without any drama. They upgraded to the 3640.

I feel like I'm missing something here though. And I kind of wish I would have resolved the issue on the 503. I don't think it should of made a difference. But if anyone has seen this, or have a MXM503N working on Server 16. Let me know.

[oeshuron]

I believe the universal Windows OS Driver package is compatible with Server 16.

http://siica.sharpusa.com/Portals/0/...PCL6_1510a.zip

[daileyrobn714]

Issue is resolved. For future techs.

We deliver an MX-M503N, end user says their IT (Cybersecurity Networking Professional) will do all installation for print and scan. Get a call, that they are not able to deploy drivers from their Server 16.

I said what the hell, and I stopped by to see if I can help the guy. Should be easy right? So he does things correctly, he set up the driving under printing policy, set up the driver, and deployed it. Uploaded additional drivers for 32bit. On the end user side, we would click on new printer, and it would say Driver Unavailable. I checked the ports in the main driver to make sure the port is not a hostname or WSD, but no... it's standard IP.

After wasting an hour I noticed that the driver from our website, says support for up to server 2012. I didn't think it would make sense, but we brought a MX-3640 where on the driver it says "Active Directory" and "Server 16" is supported. We did the same thing and it deployed beautifully without any drama. They upgraded to the 3640.

I feel like I'm missing something here though. And I kind of wish I would have resolved the issue on the 503. I don't think it should of made a difference. But if anyone has seen this, or have a MXM503N working on Server 16. Let me know.

Wow, that's a big jump from a 503 to a 3640. Just saying.

Sent from my SM-G930V using Tapatalk