System Writer Missing/Failing – Quick Fix

Dear all,

I was exploring something and found a quick fix to reset and bring back the System Writer which cause many backups to fail.

This fix won’t let you and ask you for any downtime. Please save this as a .BAT file and run it on your system on which are receiving issues when you the System Writer is spoofed from your VSSADMIN LIST WRITERS output.

@Echo “Correcting the Permissions – Making it to Default”

cd /d %windir%\system32

takeown /f %windir%\winsxs\filemaps /a
icacls %windir%\winsxs\filemaps /grant “NT AUTHORITY\SYSTEM:(RX)”
icacls %windir%\winsxs\filemaps /grant “NT Service\trustedinstaller:(F)”
icacls %windir%\winsxs\filemaps /grant “BUILTIN\Users:(RX)”
icacls %windir%\winsxs\filemaps /grant “Administratoren:(RX)”
takeown /f %windir%\winsxs\filemaps\* /a
icacls %windir%\winsxs\filemaps\*.* /grant “NT AUTHORITY\SYSTEM:(RX)”
icacls %windir%\winsxs\filemaps\*.* /grant “NT Service\trustedinstaller:(F)”
icacls %windir%\winsxs\filemaps\*.* /grant “BUILTIN\Users:(RX)”
icacls %windir%\winsxs\filemaps\*.* /grant “Administrators:(RX)”
takeown /f %windir%\winsxs\temp\PendingRenames /a
icacls %windir%\winsxs\temp\PendingRenames /grant “Administrators:(RX)”
icacls %windir%\winsxs\temp\PendingRenames /grant “NT AUTHORITY\SYSTEM:(RX)”
icacls %windir%\winsxs\temp\PendingRenames /grant “NT Service\trustedinstaller:(F)”
icacls %windir%\winsxs\temp\PendingRenames /grant “BUILTIN\Users:(RX)”
takeown /f %windir%\winsxs\temp\PendingRenames\*.* /a
icacls %windir%\winsxs\temp\PendingRenames\*.* /grant “Administrators:(RX)”
icacls %windir%\winsxs\temp\PendingRenames\*.* /grant “NT AUTHORITY\SYSTEM:(RX)”
icacls %windir%\winsxs\temp\PendingRenames\*.* /grant “NT Service\trustedinstaller:(F)”
icacls %windir%\winsxs\temp\PendingRenames\*.* /grant “BUILTIN\Users:(RX)”

@Echo “Look for any Failures above – If any than Note Down and Share it Here”
@PAUSE

net stop “Cryptography Service”
net start “Cryptography Service”

@Echo “—-END OF SCRIPT—-“

Install MSDE Instance for Blackberry Enterprise Server

The BlackBerry Enterprise Server installation program does not provide the option
to install a named MSDE instance for the BlackBerry Enterprise Server, however the
BlackBerry Configuration Database must be installed with its own MSDE instance.

Well.. All those who were wondering how to achieve this feat, here are the steps :-

1.Install an MSDE instance for the BlackBerry Software Professional
2. Download MSDE 2000 SP4
3. The installation will be in C:SQL2KSP4MSDE.
4. Go this Directory and in order to install a named instance of MSDE with mixed mode authentication (required for MDSS), type the following:
setup SAPWD=”password1!” INSTANCENAME=”BlackBerry” SECURITYMODE=SQL
6. This will create an instance with the directory in C:Program FilesMicrosoft
SQL ServerMSSQL$BlackBerry
7. If we want to change the directory use the following command
setup SAPWD=”password1!” INSTANCENAME=”BlackBerry” SECURITYMODE=SQL DataDir=”Path”
TargetDir=”Path”
8. Once we have done this we will have a service in the services console by the
name MSSQL$Blackberry which will be stopped. Start the service
9. Continue with the installation by creating the database for BlackBerry Software
Professional.

SBS 2003–CEICW Fails while Configuring Firewall/Networking/Email “Error 0x80070003 returned from call to Resetting client dns query timeouts in config.dat()” CEICW

Problem Description:-

While running CEICW after installing Server Tools and intranet component
CEICW Logs
Error 0x80070003 returned from call to Resetting client dns query timeouts in
config.dat().
Error 0x80070003 returned from call to CNetCommit::Common().
Error 0x80070003 returned from call to CNetCommit::Commit(). calling
CRFireCommit::CommitEx (0x3ef48).

Cause
================
Happens in the following Scenarios
The IIS has been installed manually and not from the integrated setup
The Exchange was installed  manually
When we try to browse default website we get errors to check dns
We dont get the IIS log files created in C:WindowsSystem32LogfilesW3SVC1
Event Type: Error
Event Source: W3SVC-WP
Event Category: None
Event ID: 2268
Date: 7/16/2008
Time: 1:57:55 PM
User: N/A
Computer: XXXX-SBS
Description:
Could not load all ISAPI filters for site/service. Therefore startup aborted.

Resolution:-

1>Check the ISAPI Filters for Default Website
2>Check if we have a folder in C:Inetpubsbsftl
3>If we have the folder we need to have sbsflt.dll and stsfltr.dll present
4>In the event we don’t have these files please copy the files from Disk3SBSSBSFLT
folder
5>Register the dlls and reset IIS.
6>We should be able to browse the default website and all VDIRs under default
website

Outlook clients getting error “Task ‘Microsoft Exchange Server’ reported error (0x80040119) : ‘Unknown Error 0x80040119′” while Send/Receive

Problem Description:-
Outlook Clients getting error "Task ‘Microsoft Exchange Server’ reported error
(0x80040119) : ‘Unknown Error 0x80040119’" when click on Send/Receive

 

Resolution:-

Open Exchange System Manager
Servername>>First Storage Group>>Mailbox Store>>Properties
On the General Tab –Offline Address List
Click On Browse>>Type in "Default Offline Address List"
Click on "Check Names" it will resolve to the Default Offline Address List
Click OK

VSS Admin List writers command does not return anything

Problem Description:-
You are not able to list any writers when running "VSSAdmin list writers"
you try registering es.dll and it will fail with the following error message:
————————————-
Regsvr32 es.dll
————————————-
The Module "es.dll" was loaded but the entry-point DllRegisterServer was not
found.
Make sure that "es.dll" is a valid DLL or OCX file and then try again.
I tried registering this DLL on my test box and found that it is normal for
register action to come up with this error message.
You may have checked the registry entries under
HKEY_LOCAL_MACHINESOFTWAREMicrosoftEventSystem{26c409cc-ae86-11d1-b616-00805fc79
216}EventClasses, and they may appear to be correct with no inconsistencies.

Resolution:-
In my case it turned out that we had installed and uninstalled a third
party backup software on the server.
Ever since we did that, we were not able to list writers or take backups on the
server.
Listing shadow copy providers did not list any third party providers.
We found that the TypeLib entry for
HKEY_LOCAL_MACHINESOFTWAREMicrosoftEventSystem{26c409cc-ae86-11d1-b616-00805fc79216}EventClasses{FAF53CC4-BD73-4E36-83F1-2B23F46E513E}-{00000000-0000-0000-0000-000000000000}-{00000000-0000-0000-0000-000000000000} —> was set as a "REG_SZ" and was pointing to %systemroot%system32EVENTCLS.DLL
We tried changing the path to C:WindowsSystem32Eventcls.dll, will let us list
all the writers.
We deleted the key and created a "REG_EXPAND_SZ" regkey and made it point to its
default value of %systemroot%system32EVENTCLS.DLL
Backups started working fine now.

A quick way to migrate Public Folders from Exchange 2003 to Exchange 2007

Sometimes the Public Folders creates the folders under public folders from the old
server however there are no contents in it. For all these situations we have to
migrate the public folder all over again. The quickest way to get them migrated is
mentioned below.

Assuming that the Old server [Small Business Server 2003 with Exchange 2003] is no
longer there however we have good backup of the Exchange Stores.

PART 1: Export
1 Mount the stores from the backup on any working SBS 2003server with Exchange on
it. [ we also can use a test or a virtual machine with Exchange 2003 running on it
where we can mount the stores from the backup ]
2 Now create a test use account or use one of the existing user account and connect
to Exchange using Outlook. In other words we want to access the mailbox for the
user where we can see the Actual Public Folders [ as we are mounting the old
Exchange stores we will see the Public Folder information as it was on the old
server ]
3 Now in Outlook go to “File Menu” and select “Import and Export” click “Next”
4 “Export To A File” click “Next’
5 “Personal Folder File (.pst)” click “Next”
6 We need to highlight “Public Folders” from the list also check the box for
“Include Subfolders” and click “Next”
7 Now specify the path where you want to save the PST file and click “Next”
8 It may ask you to specify a password for accessing the PST file later. You can
choose any random password here.
9 Click “Finish” and we are done

PART 2: Import
1 In this new server [SBS 2008] we need to create a new user account with the
mailbox
2 This temporary user will not have any emails in the mailbox, if he does then
delete them all so that the Inbox for the user is empty. Use Outlook for this.
3 Open Outlook for this user and then go to “File Menu” and select “Import and
Export” The option that is highlighted by default should be “Import from another
program or a file”, if it is not highlighted then choose that option from the list
and click “Next”
4 On this next screen highlight “Personal Folder File (.pst)” and click “Next”
5 Now choose the location where you have the PST file stored/copied now click
“Next”
6 If asked for the password use the one we gave earlier while Exporting to PST [it
may or may not ask for the password as it depends on setting of Outlook on the
customer’s machine]
7 Next screen asks you for the location where you want to import it to. Here DO NOT
HIGHLIGHT PUBLIC FOLDERS instead highlight Inbox and from below this choose the
option to “Import in the Current Location” [** Make sure that you have highlighted
the Inbox before proceeding**]
8 Do not change any other options and proceed to complete the Wizard
9 Now you will see a “+” sign next to the “Inbox” Expand the Inbox and you should
see all the Public Folders there
10 Check to see if the Public Folders have all the information, if it has the
information as it should do the following
11 Drag and drop Public Folders, from the Inbox one at a time, in the actual Public
Folder location
Hit “Send/Receive” on the Outlook to replicate on the Exchange Database on the new
server [SBS 2008 with Exchange 2007 on it]
12 Log on to the Outlook for other user(s) to check if they have the Public Folder
information.
Note:-This is a fastest way to get the Public Folder Migrated. These steps are similar to Exchange Data “Fork-Lifting”.

SBS 2003 Sharepoint Unable to install WMSDE instance of Sharepoint

Problem Description:-
This is created while creating a manual instance of WMSDE using the
following command :
c:program filesmicrosoft sql server sp4wmsdesetupsqlrun16.msi
DISABLENETWORKPROTOCOLS=1 DISABLEAGENTSTARTUP=1 DISABLETHROTTLE=1 SAPWD=2194032892
INSTANCENAME=SharePoint DATADIR="C:Program FilesMicrosoft SQL Server" /l*v
C:wsmde.log
When we try to create a instance of MSDE manually , we may get the following error:-
Setup failed to configure the server. Refer to the server error logs and setup
error logs for more information.
If we check the error log created during the same command ( i,e c:wmsde.log ) we
see the following errors :-
MSI (c) (FC:54) [13:07:13:328]: Font created. Charset: Req=0, Ret=0, Font: Req=MS
Shell Dlg, Ret=MS Shell Dlg
Setup failed to configure the server. Refer to the server error logs and setup
error logs for more information.
MSI (s) (BC!E8) [13:08:06:171]: Product: Microsoft SQL Server Desktop Engine —
Setup failed to configure the server. Refer to the server error logs and setup
error logs for more information.
Error the following data files were found in data directory:
C:Program FilesMicrosoft SQL ServerMSSQL$SHAREPOINTDatamsdbdata.mdf
C:Program FilesMicrosoft SQL ServerMSSQL$SHAREPOINTDatamsdblog.ldf
C:Program FilesMicrosoft SQL ServerMSSQL$SHAREPOINTDatamaster.mdf
C:Program FilesMicrosoft SQL ServerMSSQL$SHAREPOINTDatamastlog.ldf
C:Program FilesMicrosoft SQL ServerMSSQL$SHAREPOINTDatamodel.mdf
C:Program FilesMicrosoft SQL ServerMSSQL$SHAREPOINTDatamodellog.ldf
Setup has detected existing data/log files. Please make sure to delete/move the
files before re-running setup
Ending custom action DetectExistingData
Action ended 13:08:06: DetectExistingData.2D02443E_7002_4C0B_ABC9_EAB2C064397B.
Return value 3.
Action ended 13:08:06: INSTALL. Return value 3.

Resolution:-
This would generally happen if a previously installed version of the similar
instance is present either in files or in registry.the log file will tell us where to look for.
Open the log file and scroll to the bottom.Then search for "failed" upwards.
the first occurrence of this error will generally be followed by the reason of
failure.This can either be instances of the instance in the registry , or files on the NTFS
partition.The above log was a failure on the NTFS partition.
Renaming the MSSQL$Sharepoint folder under C:Program FilesMicrosoft SQL Server
might resolve the issue.
In another case there are instances of the GUID in registry that indicate a
previously installed instance.
TO make sure we dont have old instances in registry , look for those GUIDs :
1] Make sure the instance is removed from this location :
HKLM software microsoft microsoft sql server Installed Instances
2] Make sure you do not have any failed attempts under :
HKLM software microsoft microsoft sql server Component Set
3] The same GUID that you see above will be seen as an incomplete GUID under this
key :-
HKLM software microsoft microsoft sql server setup { …GUID…}
Removing the faulty registry GUIDs after a backup should enable us to install a
clean instance of WMSDE.

OneCare For Server “Network Location” option for backup feature is no longer visible

Problem Description:-
1>Unable to choose backup location when backing up with Onecare Backup.
2>Unable to do a Centralized backup from the SBS Server.

 

It appears that, by design, when a OneCare standalone client is joined to a
domain with the SBS2008 server hosting "OneCare for Server", the "OneCare for
Server" code changes settings on the client machines to render them no longer a
"standalone" OneCare install, but rather a member client of the "OneCare for
Server". Additionally, the subscription ID may contribute to causing the actual
changes from a OneCare "standalone installation" with centralized backup
capabilities, to then a member client of the "OneCare for Server" server, which
does not support centralized backup from a member client, whether or not configured
as a "hub".
While various Microsoft web site documentation states that centralized backup "from
the OneCare for Server" server is possible, that documentation may have been
written and posted during the Beta period. The final release version, including all
internal training materials state that the backup feature is disabled when "OneCare
for Server" is installed onto SBS 2008 server.
RESOLUTION:
============
There is a detection routine that occurs on install that will determine if the
retail or SBS client version of OneCare gets installed. It really doesn’t matter
where you install from, as the detection is what differentiates the installations.
The change of the "client" status from "standalone" to "member client" happens when
a client machine is joined to the domain hosting "OneCare for Server". While it
was possible to trick the client installation into seeing itself as a "standalone"
installation with SBS 2003 server, that option is no longer possible with SBS 2008
server.
FOR SBS 2003 SERVER WITH ONECARE FOR SERVER ONLY:
There is a registry hack that you can use to “trick” the OneCare installer into
installing the Retail Client instead of the Server Client, which hopefully will
allow us to configure the backup. Please perform the step below on the Hub PC (not
the server).
1. Rename the reg key “HKEY_LOCAL_MACHINESOFTWAREMicrosoftsmallbusinessserver”
to something else
2. Uninstall/Re-install OneCare
3. Then activate
Please note this will only work if the SBS server is SBS 2003 (does not work on the
most recent version of SBS).

How to Install Fax in SBS 2003, Configure Fax for sending and recieving Faxes with Outlook, Print Item to Fax Printer

                                                                                                      Installing Fax on the SBS 2003 Server

 How to Install Fax on SBS 2003

 Insert SBS 2003 CD 1. Let it autoplay and then click Set Up Windows Small Business Server on the Microsoft Windows Small Business Server Setup screen.

On the Welcome to Microsoft Windows Small Business Server Setup screen, click Next.

On the Windows Configuration screen, click Next.

On the Component Selection screen, select Install in the Action column next to Fax Services, and then click Next.

On the Data Folders screen, specify the folder to save sent faxes to and click Next.

On the Component Summary screen, click Next.

On the Finishing Your Installation screen, click Finish.

In SBS 2003, you can install the fax client software on the client computers using the Add Software to Computer wizard or you can install it manually. The Add Software to Computer wizard deploys the fax client via a user logon script called SBS_LOGIN_SCRIPT.bat which runs \servernameclientssetupsetup.exe /s servername. If the user is not configured to run SBS_LOGIN_SCRIPT.bat or the setup command is not present in the logon script, the fax client will not be installed by the wizard and you may have to install it manually.

 

Install fax on the SBS client (using the Add Software to Computer wizard)

On the SBS server, click Start, point to Administrative Tools and then click Server Management.

On the left, click Client Computers, and then click Assign Applications to Client Computers on the right.

On the Welcome to the Assign Applications Wizard, click Next.

On the Client Computers screen, select the client computer(s) to install the fax client on and click Add. Then click Next.

On the Client Applications screen, ensure the Shared Fax Client is checked and then click Next.

On the Mobile Client and Offline Use screen click Next.

On the Completing the Assign Applications Wizard screen, click Finish.

On the Finishing Your Installation screen, click OK.

Go to the client computer and log on. If the client computer is already logged on, log off and then log on to the domain again.

Follow the client setup wizard prompts to install the Fax client.

Install fax on SBS client manually. To install the Fax client on Windows XP-based clients, follow these steps:

Log on to the Windows XP-based computer as a user with local administrator rights.

Click Start, click Control Panel, and then click Add or Remove Programs.

Click Add/Remove Windows Components.

Click to select the Fax Services check box, and then click Next. If you are prompted to do so, insert the Windows XP CD-ROM.

Click Finish.

To connect the Fax printer to Windows XP-based client computers:

Click Start, and then click Run.

Type \<servername> and then click OK.

Right-click the Fax printer, and then click Connect.

Install fax on SBS client manually. To install the Shared Fax Client on computers that are not running Windows XP, follow these steps:

Run setup.exe from the fax client share on the server. \servernamefaxclientsetup.exe

Sending Faxes

Using the Send Fax Wizard

Click Start, point to All Programs, point to Accessories, point to Communications, point to Fax, and then click Send a Fax.

In the Welcome to the Send Fax Wizard dialog box, click Next.

In the Recipient Information dialog box, type the recipient name in the To box, type the recipient fax number in the Fax number box, or use the Address Book to click the recipient name, and then click Next.

Note: If you want to send the fax to more than one recipient, type the recipient information in the appropriate boxes, and then click Add. The recipient appears in the box and the boxes are cleared so that you can type additional recipient information. When you finish adding recipients, click Next.

 In the Preparing the Cover Page dialog box, click the template that you want to use in the Cover page template box. If you want to edit the information that appears on the cover page, click Sender Information. Type the subject that you want to appear on the cover page of the fax in the Subject line box, and then type a cover page note in the Note box if you want to include a note.

 Click Next.

 In the Schedule dialog box, click the time that you want to send the fax, for example, click Now.

 In the What is the fax priority box, click the priority that you want (a higher priority allows this fax item to be sent before another similarly scheduled and lower priority item), and then click Next.

 In the Delivery Notification dialog box, select how you would like to be notified of a successful or failed fax delivery and click Next.

 In the Completing the Send Fax Wizard dialog box, confirm the options that you selected, and then click Finish.

 From Outlook

 Open Outlook, click Tools, and then click E-mail Accounts.

 On the E-mail Accounts screen, select View or change existing e-mail accounts and click Next.

 The Fax Mail Transport should be present in the list.

 If the Fax Mail Transport is not present in the Accounts list in Outlook 2003.

 Click Add.

 Select Additional Server Types and click Next.

 Select the Fax Mail Transport and click Next.

 If you receive the following pop-up message, click OK.

 The E-mail Account you have just added will not start until you choose Exit from the File menu, and then restart Microsoft Office Outlook.

 To access and configure the Fax Mail Transport options, perform the following steps:

 In the Accounts list in Outlook 2003, select the Fax Mail Transport and click Change. The following options are configurable.

Include a cover page with faxes

 This specifies that all faxes sent from Outlook should include a cover page.

Single delivery receipt for multiple recipients

This checkbox specified that you want a single receipt to confirm delivery of a fax sent from Outlook to multiple recipients. This feature is not available if you use a locally installed fax device to send faxes from Outlook.

Attach a copy of a sent fax to its delivery notification receipt

This checkbox specifies that you want a copy of the fax to be attached to the delivery receipt notification. If you select this option, and you send a fax with a cover page to multiple recipients, the cover page will not be included with the copy of the sent fax. This is because the cover page information will be different for each recipient. In addition, if a multi-recipient fax consists only of a cover page then you cannot attach a copy of the fax to a delivery receipt. This feature is not available if you use a locally installed fax device to send faxes from Outlook.

Default Message Font

This defines the message font used for the Subject line in Outgoing Faxes when a cover page is not used. It does not affect the font of the message body typed in the email message. It also does not affect the font of any attachments. If ‘Include a cover page with faxes’ is checked, the Subject will be printed on the cover page and the font will not be affected by the Default Message Font setting.

Click OK and click Finish.

To send a fax from Outlook:

Open Outlook 2003.

Click File, point to New, and then click Mail Message.

In the To.. field, specify the fax recipient. To do so, click the To.. button, or type the fax number in the format [FAX:n,nnnnnnnnnnn]. For example, type [FAX:9,13215551234] where 9 is the number to dial an outside line, 1 is the number to dial long distance, and (321) 555-1234 is the area code and the phone number.

Note: If you click the To button to select a contact, you must select the contact that includes Business Fax in the display name.

 Note: You can also create a distribution list made up of Business Fax contacts.

 Type the subject and body of the fax.

 Click Send.

 Print item to Fax printer

 Start the program that you want. For example, start Microsoft Word and open a saved document.

 On the File menu, click Print.

 In the Print dialog box, click Fax in the Name box, and then click OK.

 This will invoke the Send Fax Wizard.

 Mail Merge (using Contacts in Outlook or a public folder)

 Open a contact with a Business or Home fax number.

 Click the All Fields tab.

 In the Select from box, click Miscellaneous Fields.

 In User Field 1 (or one of the other 3 User Fields if this field is already being used), type the fax number exactly as it should be dialed, by using one of the following canonical format examples:

 7-digit dialing – [fax:555-1212]

 10-digit dialing – [fax:999-555-1212]

 Long-distance number (United States) – [fax:1,999-555-1212]

 You may also specify the display name for the Business Fax field of an existing contact such as:

 FirstName LastName (Business Fax)

 Joe Smith (Business Fax)

 Click Save and Close.

 B. Initiate the Mail Merge from Outlook:

 While in Contacts, click Mail Merge from the Tools menu.

 Select whether to merge using all or selected contacts.

 Select whether to merge using all of the fields or only those in the view. (If you select to merge by using only those in the view, the User Field that you selected to store the canonical fax numbers must appear in the view.)

 Configure your Document and Contact data file settings.

 In the Merge to option, click E-mail.

 Set the Message subject line option, and then click OK.

 Word opens. Click the merge to email button.

 In the To line, select User_Field_1 and click OK.

 In the Mail Format drop down list, the options are HTML, Attachment, and Plain text. The default is HTML.

 In the Send Records section, select All and click OK.

 Important: After clicking the merge to email button, the properties dialog appears. There is a Mail Format drop down list with the options: plain text, attachment, and HTML. Selecting plain text or attachment will result in the Outlook Security popup. Selecting HTML will not. If you need to use the plain text or attachment format and do not want to have to click Yes for each of the Outlook Security prompts, you will need to customize the Outlook Security settings using the Outlook E-mail Security Administrator Package. See KB article 290499 for more information.

 Note: You can also initiate the mail merge from Word, using the User Field 1 to merge on.

 Caution: 

In step 8 above, if you select the Business_Fax field, you will receive a Check Names box when you initiate the merge in step 10 which says something like. Microsoft Office Outlook does not recognize “(999) 555-1212” Select the address to use:

 

 

Enable email receipts

Enable email receipts (Fax arrival/sent notifications)

Click Start, point to All Programs, point to Accessories, point to Communications, point to Fax, and then click Fax Service Manager.

In the console tree in the left panel, right-click Fax (Local) node, and then click Properties.

On the Receipts tab, click to select the Enable SMTP e-mail receipts delivery check box.

In the From e-mail address: box, type the e-mail address of the sender of the delivery notification receipt. For example, SBSFaxService@domain.com.

In the Server address: box, type the SBS server’s NetBIOS computer name. Do not type the server’s fully qualified domain name (FQDN). To determine the SBS server’s NetBIOS computer name, type hostname (without the quotation marks) at the command prompt, and then press ENTER.

In the Port: box, type 25. If the SMTP port has changed, type the appropriate port.

Click the Authentication button, click the Anonymous access option, click OK, and then click OK again.

Check the box Use these SMTP settings for the Route Through E-Mail incoming routing method if you wish to have incoming faxes routed to a user’s mailbox via email.

The check box labeled Enable message boxes as receipts specifies whether delivery notification requests are configured as pop-up messages to keep fax senders informed of the successful delivery of their sent faxes. This option requires the Messenger service to be running on the sender’s computer.

 

Note:

The authentication method you selected must match the authentication method defined in the Exchange 2003 SMTP server. By default, it is set to Anonymous access.

To verify this:

Start the Exchange System Manager.

If the administrative groups are displayed, expand Administrative Groups, and then expand <first administrative group>.

Expand Servers, expand <servername>, expand Protocols, and then expand SMTP.

Right-click Default SMTP Virtual Server, click Properties, and on the Access tab, click the Authentication button.

Verify that Anonymous access is enabled.