Winfax Pro 10.0 on Windows 2003 Standard Server

[Sleurhutje]

During installation the installation procedure return an errorcode stating
the printer couldn't be created. Don't know right now what the code was
exactly (tell you later)

Who's having any experiences on this? Even better, running Terminal Services
with the client on each client session.


Jeroen.

 

[Guest]

Winfax Pro is not supported on Terminal Services, per this article:

http://www.symantec.com/winfax/sys_req.html

Patrick Rouse
Microsoft MVP - Terminal Server
http://www.patrickrouse.com/ts.htm

 

[Sleurhutje]

That's something I know. But it ran on the Windows NT 4.0 Server, it ran on
the Windows 2000 Server but not on the Windows 2003 Server. I asked for
anyone who had any experiences with installing, not the fact it is supported
or not.

Sorry for this reaction but I'm getting a little tired of people who tell
what the specs are. These are on the box and in the manual as well. And yes,
I read the manual...


Jeroen

 

[Sleurhutje]

The installation has problems adding the printers. It reports:

The WinFax printer add failed.
Error code -> 1930 PrinterName=WinFax

and

The WinFax printer add failed.
Error code -> 1930 PrinterName=WinFax (Photo Quality)


Looks like there are problems in adding the printer automatically. Can I add
these manually?



Jeroen

 

[Vera Noest [MVP]]

The information in your first post was so minimal that any other
reaction was impossible. I didn't even bother to answer, because I
thought it useless. How can we know that you already are aware of
the fact that the application is not supported? Or what you have
already read and tried?

During installation the installation procedure return an
errorcode stating
the printer couldn't be created. Don't know right now what the
code was exactly (tell you later)

I am getting a little tired of people who don't provide any
details, expect others to be able to read their minds and get
irritated when they can't.

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup ---

 

[Guest]

My stance on running applications in a business environment is to run them on the OS that the manufacturer guarantees they'll work on.

My reasoning is because in a situation like yours the manufacturer will say "did you not read the box" and Microsoft will ask you what the manufacturers system requirements are. You're now stuck trying to hack a system that's intended to be as stable as possible as it supports multiple (sometimes 50+) concurrent users. For example, I know for a fact Exchange 2000 will run on Windows 2003 with a bit of tweaking, but there's no telling when a hotfix or service pack will make the service inoperable.

I choose to err on the side of safety, and advise others to do the same. You're obviously free to try whatever you like to get your system running and I wish you the best of luck. I would advise you to make sure your company understands that they're running unsupported software and that you can NOT guarantee that it will work properly, i.e. CYA.

Patrick Rouse
Microsoft MVP - Terminal Server
http://www.patrickrouse.com/ts.htm

 

[ironman]

Patrick, good to know that your all knowing and ever MS.
IMHO:
If the builtin fax service in Windows Server 2003 worked, then perhaps
we would not be looking at 3rd party solutions....

 

[online]

During installation the installation procedure return an errorcode stating
the printer couldn't be created. Don't know right now what the code was
exactly (tell you later)

Who's having any experiences on this? Even better, running Terminal Services
with the client on each client session.


Jeroen.

This might help:
http://www.computing.net/windows2003/wwwboard/forum/1678.html