Hi Marina, That is exactly what was used to connect the workstations to the new server. All the other Patches, Outlook 2k3, IE6 were available, except for the fax client and ISA client. I had manually added the fax and ISA client to the Application Deployment wizard, but the error message still appears after a manual install of the fax client. I had also posted this question up on the sbs newsgroup, but have not gotten a full response. See below for a more complete description of my setup.
1. This is a new install of SBS2003 Premium onto a new server. Some client workstations came from an old SBS2000 network. Network consist of 65-70 clients, a mix of NT, Windows 2000 Professional and XP Professional. All workstations are prompting this error message upon login except the NT Boxes. 5 new Windows 2000 workstation clients were deployed today and the same error message occurs. Therefore regardless of client OS, the message still comes up. Server has been running for 2 weeks, same error window and message for 2 weeks on all 2k and xp clients.
From the old SBS2000 server, only data files and Exchange was migrated to the new server.
2. From the initial installation of SBS2003, the Fax Client was not present under the "Add Application Wizard" for the client computer deployment. The application was added manually. -- Also, the ISA Firewall Client was also not present under the client deployment wizard.
I have even manually installed the Fax Client on several workstations, but the error message still appears following login - even though the Shared Fax client is running on the workstation, both Windows 2000/XP. The Fax client works fine at the client and server level.
3. Under the Event Viewer, System Events the following was the only warning:
Event Type: Warning Event Source: Print Event Category: None Event ID: 20 Date: 5/5/2005 Time: 1:24:06 AM User: NT AUTHORITY\SYSTEM Computer: IS1 Description: Printer Driver Windows NT Fax Driver for Windows NT x86 Version-3 was added or updated. Files:- FAXDRV.DLL, FAXUI.DLL, FAXDRV.DLL.
Thanks in advance for any insight you can provide on this. Wayne |