E-Bitz - SBS MVP the Official Blog of the SBS "Diva"

Installing GFI Faxmaker 10 in SBS2k3

 How to install GFI Faxmaker 10 in SBS 2003.

On a default SBS 2003 installation, the Microsoft Exchange MTA stacks
service and functionality are disabled. Faxmaker requires the interaction
with this service for its Exchange connector to function properly. In order
to get the full functionality of Faxmaker or any other product that requires
the user of a connector through the MTA, the following steps need to be
followed:


How to re-enable the MTA Stacks in SBS 2003.

Enabling the MTA is a two step process; it requires making changes to the
startup type of a service and also perform some registry editions.

Before starting, make sure you have a good working system state backup.

1-Removal of Registry Keys:

1.1-Open Regedit.exe

1.2-Go to:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\servername
\Private-guid_of_private_mdb

Remove (Delete) the following two entries:

            "Gateway In Threads"

           "Gateway Out Threads"

1.3-Go to:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\servername
\Public-guid_of_public_mdb

Remove (Delete) the following two entries:

            "Gateway In Threads"

           "Gateway Out Threads"

1.4-Close Regedit.exe.

2-Changing the startup type of the Microsoft Exchange MTA Stacks service.

2.1-Open the Services MMC (or open Run and type Services.msc and then press
OK).

2.2-Double click on top of the Microsoft Exchange MTA Stacks entry to open
its properties.

2.3-In the General tab, change the Startup type from Disabled to Automatic,
click Apply and then start the service. Close the properties.

2.4-Do not close the Services MMC yet.


3-Re-starting services


3.1-Select the Microsoft Exchange System Attendant service and perform a
re-start, this will also re-start all dependant services. (If Faxmaker was
already installed, re-start the proper services from that product). If in
doubt, re-start the system.

3.2-Close the Services MMC.


4-Install GFI Faxmaker 10 if it has not been installed yet, if it was, after
the services are re-started, faxes should start flowing through Exchange to
FaxMaker.

If you are having issues with getting to SSL based webpages, you may want to get this patch.

305217 - Page Cannot Be Displayed Error During SSL 3.0 Server Session Timeout:
http://support.microsoft.com/?kbid=305217

Call PSS and request it, it will be a free call.

 

Getting error codes 8026 and 8250 in your event viewer about LDAP bind?

 MSExchangeAL , event ID 8026 and 8250

If these are occuring right after start up and right before shut down you can safely ignore them.

Getting error codes 2102 and 2104 in your event viewer about MAD process?

 MSExchangeDSAccess, event ID  2102 and 2104

These errors are typically for SBS boxes right before start up and right before shut down.

You can safely ignore them.

Getting an error code 1000 in your Error logs about Sharepoint synchronization?

 Windows Sharepoint Services 2.0, event  ID 1000

These are timing errors and can be ignored.

 

Getting an event 537 in your Error logs?

http://www.eventid.net/display.asp?eventid=537&source=

If you are getting event errors 537 and throwing off Kerberos errors, ensure that your clients are time sync'd with the domain controller. 

http://www.smallbizserver.net/DesktopDefault.aspx?tabid=64

 

Getting an Event 8331 in your error logs?

http://www.eventid.net/display.asp?eventid=8331&source=

If you are getting a wacko error about Path: "f:\titanium\dsa\src\lra\abv_dg\lservagent.cpp", reboot your server.  While some posts have indicated that you “can” forestprep and other fixes, it's recommended to try rebooting first.  There is a reported fix in the works, and thus redoing the forestprep/domainprep is not recommended at this time.

UPDATE - THERE IS NOW A HOTFIX:

http://msmvps.com/bradley/posts/4046.aspx

UPDATE - Exchange 2003 sp1 now includes this

Getting an Event 1111 in your Event logs?

http://www.eventid.net/display.asp?eventid=1111&source=

Be sure that you have installed the printer driver used by a remote user on the host server or XP workstation. 

 

Will RMS run on SBS2k3?

From a posting in the newsgroups ... RMS can run properly on any Windows 2003 AD server which includes SBS 2K3.

The problem that the external clients cannot reach your RMS server is probably because that the Internet clients cannot find the RMS Services. Since the client machine is not in the domain, it will not automatically query the AD to find the location of the RMS services. I've discussed with our RMS support and they suggested that you add two registry values in the client machine to point to the RMS services directly:

" HKLM\Software\Microsoft\Office\11.0\Common\DRM\Corplicenseserver to point to the licensing service like: http: [wack wack] >_wmcs/licensing“

" HKLM\Software\Microsoft\Office\11.0\Common\DRM\CorpCertificationserver to point to the certification service like: http: [wack wack] wmcs/certification“

However, if the problem still occurs, can I suggest that you also post out this issue on the public newsgroup: microsoft.public.rights_mgmt_svcs? In that newsgroup, you will get the most qualified pool of respondents, and so other customers and partners who regularly read the newsgroups can either share their knowledge or learn from your interaction with us.

Getting an error during inplace upgrade that Base DAV protocol 0XC103748A can't install?

 FIRST
if Microsoft Office 10 Beta is or ever has been installed on the
computer. Office 10 Beta includes a local Web store. This local Web
store registers itself in the following registry key:

HKEY_LOCAL_MACHINE/Software/Microsoft/DataAccess/RootBinder/file

This key contains the following three values:
- //\\.\backofficestorage
- //\\<server_name>\backofficestorage
- //\backofficestorage

These values contain a class ID. The class ID for the Office 10 local
Web storage system is {9da0e11f-86ce-11d1-8699-00c04fb98036}, but the
class ID for the Exchange 2000 Web storage system is
{9da0e0f3-86ce-11d1-8699-00c04fb98036}. If any of these registry values
contain the class ID for the Office 10 Web store, Setup does not work
and you receive the error message in the "Symptoms" section of this
article.

SECOND:
296436 XADM: Setup Cannot Register the Exoledb.dll File
http://support.microsoft.com/?id=296436

THIRD:
How do you feel about an uninstall/reinstall of
IIS/Exchange.  That's also mentioned as a fix.

Try to make anew Default Web Site and what happens?
1. Start Internet Services Manager.
2. Right-click <YourServerName>, click New, and then click Web Site.
   This step starts the Web Site Creation Wizard.
3. Click Next.
4. Enter a description for this Web site, and then click Next.
5. Set the appropriate Internet Protocol (IP) and port setting, and
   then click Next.
6. Set the path for the Web site, and then click Next.
7. Set the appropriate Web site access permissions, and then click Next.
8. Click Finish.

This is mentioned in:
303063 XADM: An Error Message Occurs and Exchange 2000 Server Setup May
Not
http://support.microsoft.com/?id=303063

Are the entries in the Exchange Server Setup Progress.log consistent in
all these issues?

Inplace upgrade from SBS2k to 2k3 and get an error regarding driver not signed?

"The driver software you are installing has not been
properly signed with authenticode technology. Therefore,
Windows cannot tell if the software has been modified
since it was published. The publisher's identity cannot
be verified because of a problem:
The parameter is incorrect"

Resolution is to set Key:
HKEY_LOCAL_MACHINE\Software\Microsoft\Non-Driver Signing\Policy to 00.

"The driver software you are installing has not been
properly signed with authenticode technology. Therefore,
Windows cannot tell if the software has been modified
since it was published. The publisher's identity cannot
be verified because of a problem:
The parameter is incorrect"

UPDATE:  You probably need to edit this via Group Policy instead  -- this is an example of the group policy for kernel mode drivers for printers:

1. Open Group Policy Management and open the Default Domain Controllers
policy. NOT the default domain policy.
2. Double-click Administrative Templates, and then double-click Printers.
3. Right-click Disallow installation of printers using kernel mode drivers,
and then click Properties.
4. In the Setting tab, click Disabled, and then click OK.

Explanation of the 'Disallow installation of printers using kernel mode
drivers'

Determines whether printers using kernel-mode drivers may be installed on
the local computer.  Kernel-mode drivers have access to system-wide memory,
and therefore poorly-written kernel-mode drivers can cause stop errors.

 

Watch the webcast and download the Performance Agent tool

834120 - TechNet Support WebCast: Monitoring features in Microsoft Windows Small Business Server 2003:
http://support.microsoft.com/default.aspx?kbid=834120

Download details: Small Business Server 2003 Performance Agent:
http://www.microsoft.com/downloads/details.aspx?FamilyID=9a169091-44ca-4ce9-947a-af48eeef6147&DisplayLang=en

Having DNS issues with your SBS 2003?

 ******Begin User Part 1******
...[Server is] a Dell PowerEdge 600sc server with RAID 1. There is 1
NIC. SBS 2003 Standard came pre-installed by Dell. I plugged the server
onto a network that is sharing a public IP in a NAT configuration on a
Sonicwall Firewall, which is also the DHCP server for all PCs on the
network. I configured the NIC on the SBS server with a static IP
address. I configured the DNS server with forwarders to the public IP
addresses of the DNS servers of the Internet provider. And I made the IP
address of the new SBS server the primary DNS server assigned by the
DHCP server. PCs on the LAN, using the IP address of the SBS server as
their primary DNS server, were not able to get DNS resolution. But the
server was for itself.

Here is the response I received from Microsoft:
******End User Part 1******

******Begin Microsoft******
The configurations in SBS 2003 is simialar to configurations in SBS
2000.
There is no need for you to run ICW.exe on the computers.

This issue can occur because Extension Mechanisms for DNS is enabled on
Windows 2003 by default (it is disbled in the Windows/SBS 2000). (The
SBS 2003 is based on the Windows 2003)

828731 - An External DNS Query May Cause an Error Message in Windows Server 2003:
http://support.microsoft.com/default.aspx?scid=kb;en-us;828731&Product=w

Please try the following command to turn off EDNS0 support 1. Start a
command prompt.
2. Type "dnscmd /Config /EnableEDnsProbes 0" (without the quotation
marks), and then press ENTER.

Then please check the issue again. You can take a look at the following
URL for more information: 828263 DNS query responses do not travel
through a firewall in Windows Server
http://support.microsoft.com/?id=828263
******End Microsoft******

******Begin User Part 2******
The settings changed that is recommended by Microsoft disables Extension
Mechanisms for DNS that is supposedly blocking the computers using this
DNS server to get their name resolution. So disabling this thing then
allows proper resolution.

Apparently, Extension Mechanisms for DNS was disabled by default in SBS
2000, but Microsoft changed that in 2003 to make it more secure.
******End User Part 2******