Since upgrading our 15 business network computers to Windows 10, users can no longer view outgoing faxes (while they are being sent), and failed faxes do not appear in outbox either. Even the outbox of the user that sent the fax is empty. The only way failed faxes can be seen is by logging into the fax server (running Server 2000) and viewing the fax manager. However, before all computers were upgraded, ones running Win7 could still see outbox faxes and failures.
This seems to not be affected by any permissions of any user groups since everybody has full fax control.
All other fax functions are working normally and no different from prior to upgrade.
I am at a loss as to how this can be solved and do not want a critical failed fax to be missed and not be able to troubleshoot it.
Any advice would be much appreciated!
Thanks in advance!
How about putting a shortcut on the users desktop point to the Windows 2000 fax manager? If they have permissions then they should be able to do it from their desktop.
Running Server 2000 with Windows 10 is the problem. You need to upgrade to at least Server 2012 r2 at this point. There are Linux Distros that will work in place of Windows Server and Windows Exchange. You would need to learn the differences to get used to working with a whole new server product.
Read this as to what you need to know about upgrading to Windows 10. 7 things small businesses need to know about Windows 10 | CIO
Zentyal & Nethserver are two that will work for the domain, mail and file sharing. You would need something like Centrify for GPO. All workstations have to be running the Pro or Enterprise edition of Windows 10.
Good idea play2mefish, I tried that, but I cannot create a shortcut to the specific fax server fax console, it instead defaults to the local "shared" fax consoles that still do not display the correct fax outbox.
I know I should upgrade servers, but trying to work through it for now...
Does anybody even use windows fax anymore? It has always worked for us...
Thanks.
I did use windows fax server but it was Windows 2012 server and not 2000. You might be able to find a good Linux solution for a fax server and run it from an older computer that you have retired from daily service. That would be a great way to put something old to work again and would probably do it real nice. Anyway, hope the ideal helps.
They cannot use anything older than maybe a Intel Core 2 Duo or Intel Core 2 Quad CPU for that group. For the size of the group and what they may be doing, they may want to use a i5 or i7 CPU, along with at least 16 to 24 gb RAM to properly handle that load.I did use windows fax server but it was Windows 2012 server and not 2000. You might be able to find a good Linux solution for a fax server and run it from an older computer that you have retired from daily service. That would be a great way to put something old to work again and would probably do it real nice. Anyway, hope the ideal helps.
The Linux distros I posted are a perfect replacement. I had one other that I found, but cannot remember the name, along with I may have accidentally tossed the DVD, because I had changed my mind on setting up a Domain setup for mine and my wife's laptops.
The only thing about coming from Microsoft Server to Linux Server, is the learning curve for some that may not know how to get it setup.
They can run the servers like mail and fax server under Docker, which is a very good Virtual platform that is not resource hungry like a lot of VM's.
That may not work, due to the changes that they did with Windows 10 to make older Server products of Microsoft to not be compatible.How about putting a shortcut on the users desktop point to the Windows 2000 fax manager? If they have permissions then they should be able to do it from their desktop.
I am all up to be part of a group to help reelcrazy if he wants to go this route.
