<?xml version="1.0" encoding="iso-8859-1" ?>
<rss version="2.0">
  <channel>
    <title>SERVER</title>
    <link>http://www.iternity.co.uk/phorum/list.php?7</link>
    <description><![CDATA[Microsoft Server 2000/2003 - 
Microsoft SBS 2000/2003
XServer / MAC OS X Server - 
UNIX/Linux Servers]]></description>
    <language>EN</language>
    <pubDate>Fri, 20 Aug 2010 12:06:10 +0200</pubDate>
    <lastBuildDate>Fri, 20 Aug 2010 12:06:10 +0200</lastBuildDate>
    <category>SERVER</category>
    <generator>Phorum 5.1.22</generator>
    <ttl>600</ttl>
    <item>
      <title>Mozy does not back up exchange files</title>
      <link>http://www.iternity.co.uk/phorum/read.php?7,61,61#msg-61</link>
      <author>iternity</author>
      <description><![CDATA[Why isn't Mozy backing up exchange files?

If you are running Microsoft Small Business Server 2003, you need to perform the following steps to ensure your exchange files will be backed up.

   1. Click the Start menu, then click Run.
   2. Type regedit, and then click OK.
   3. Locate and then double-click the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\ParametersSystem
   4. Double-click the Disable Exchange Writer value.
   5. In the Value data text box, change the value from 1 to 0, and then click OK.
   6. Quit the Registry Editor.
   7. Click the Start menu, then select Control Panel.
   8. Double-click Administrative Tools, then click Services.
   9. Stop and then restart the Microsoft Exchange Information Store service.
  10. Click the Start menu, then click Run.
  11. Type regedit, and then click OK.
  12. Locate and then double-click the following registry subkey: hkey_local_machine\software\mozypro\state
  13. Right click on the vss_scan and select Modify
  14. Change the value of vss_scan to 1.
  15. Restart the MozyProBackup service. 

(taken from: marriottschool.byu.edu)]]></description>
      <category>SERVER</category>
      <guid isPermaLink="true">http://www.iternity.co.uk/phorum/read.php?7,61,61#msg-61</guid>
      <pubDate>Fri, 20 Aug 2010 12:06:10 +0200</pubDate>
    </item>
    <item>
      <title>VSS related problems with ntbackups</title>
      <link>http://www.iternity.co.uk/phorum/read.php?7,56,56#msg-56</link>
      <author>iternity</author>
      <description><![CDATA[Re-register VSS libraries, possibly restart VSS services/whole machine

&gt;1. Open a command prompt.
&gt;2. Key in the following command to stop VSS service:
&gt;
&gt;net stop vss
&gt;
&gt;3. Then register the following dlls and services by running the following
&gt;commands:
&gt;
&gt;regsvr32 ole32.dll
&gt;regsvr32 vss_ps.dll
&gt;Vssvc /Register
&gt;regsvr32 /i swprv.dll
&gt;regsvr32 /i eventcls.dll
&gt;regsvr32 es.dll
&gt;regsvr32 stdprov.dll
&gt;regsvr32 vssui.dll
&gt;regsvr32 msxml.dll
&gt;regsvr32 msxml3.dll
&gt;regsvr32 msxml4.dll&quot;
&gt;]]></description>
      <category>SERVER</category>
      <guid isPermaLink="true">http://www.iternity.co.uk/phorum/read.php?7,56,56#msg-56</guid>
      <pubDate>Fri, 12 Mar 2010 14:36:16 +0100</pubDate>
    </item>
    <item>
      <title>Exclude certain types of files/locations from ntbackup</title>
      <link>http://www.iternity.co.uk/phorum/read.php?7,55,55#msg-55</link>
      <author>iternity</author>
      <description><![CDATA[There is a way to globally exclude certain types of files in certain locations from ntbackup.

In regedit, go to:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\BackupRestore\FilesNotToBackup

and create new &quot;Multi String&quot; entry named conveniently for you (name does not matter). As a value, put path and type of the files you would like to exclude from ntbackups. 

File path entry may contain: drive:\subfolders\path\*.wildcard

Additionally /s at the end includes all subdirectories

Hope that helps,

Maciek

Here is the article from Microsoft:
-----------------------------------
Microsoft Windows operating systems maintain a list of files and folders that are excluded 

when you backup and restore files by using the Ntbackup.exe tool and other 

Windows-compatible backup programs.

Windows stores this information in the following registry keys:

Note The registry values shown in this article are a sample from one computer and may differ 

from what you might see on your computer depending on your configuration.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\BackupRestore\FilesNotToBackup
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\BackupRestore\KeysNotToRestore
The default values and value data for the 

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\BackupRestore\FilesNotToBackup registry 

key is listed in the following table.

    Value 	Value Data
    Client Side Cache 	%SystemRoot%\csc\* /s
    ComPlus 	%SystemRoot%\Registration\*.crmlog /s
    Internet Explorer 	%UserProfile%\index.dat /s
    Memory Page File 	\Pagefile.sys
    MS Distributed Transaction 	%SYSTEMROOT%\System32\DTCLog\MSDTC.LOG
    NtFrs 	%systemroot%\ntfrs\jet\* /s
    %SystemRoot%\debug\NtFrs*
    %systemroot%\sysvol\domain\DO_NOT_REMOVE_NtFrs_PreInstall_Directory\* /s
    %systemroot%\sysvol\domain\NtFrs_PreExisting___See_EventLog\* /s
    %systemroot%\sysvol\staging\domain\NTFRS_*
    Power Management 	\hiberfil.sys
    Temporary Files 	%TEMP%\* /s 



The default values and value data for the 

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\BackupRestore\KeysNotToRestore registry 

key are listed in the following table.

    Value 	Value Data
    Active Directory Restore 	CurrentControlSet\Services\NTDS\Restore In Progress\
    CurrentControlSet\Services\NTDS\Parameters\New Database GUID
    Fault Tolerance 	Disk\
    Installed Services 	CurrentControlSet\Services\*
    LDM Boot Information 	CurrentControlSet\Services\dmio\boot info\
    Mount Manager 	MountedDevices\
    Pending Rename Operations 	CurrentControlSet\Control\Session 

Manager\PendingFileRenameOperations
    Plug and Play 	CurrentControlSet\Enum\
    CurrentControlSet\Control\CriticalDeviceDatabase\
    Session Manager 	CurrentControlSet\Control\Session
    Windows Setup 	Setup\SystemPartition 

The file exclusions listed in this article also apply when you are using Volume Shadow Copy 

Service. In this scenario, the requestor, such as NTBACKUP.EXE, passes a list of files and 

folders it will backup or restore, subject to any exclusions by the registry keys listed in 

this article.]]></description>
      <category>SERVER</category>
      <guid isPermaLink="true">http://www.iternity.co.uk/phorum/read.php?7,55,55#msg-55</guid>
      <pubDate>Fri, 12 Mar 2010 14:32:11 +0100</pubDate>
    </item>
    <item>
      <title>Exchange emails are  bouncing back - BT Broadband revDNS/PTR problem</title>
      <link>http://www.iternity.co.uk/phorum/read.php?7,49,49#msg-49</link>
      <author>iternity</author>
      <description><![CDATA[Exchange emails are  bouncing back - BT Broadband revDNS/PTR problem

We had several clients complaining about email bouncing back from certain reciepients (including AOL). After examining the problem further we discovered that our SMTP servers are beeing rejected due to wrong PTR record. Rev-DNS entries were not pointing back to the name which was displayed in Exchange's SMT banner. 

Solution:

BT can set Rev DNS for you for free. Just drop them an email on:

 reverse.dns@btbroadbandoffice.com 

Except from bief description, email should contain your 81.IP.ADDR.ESS &gt; mail.domain.com, where mail.domain.com is where MX records are pointing to. They will do the changes manually within 24hours. 

Now lets double-check SMTP Banner on Exchange 2003:

   1. Open Exchange System Manager, Servers, , Protocols, SMTP.
   2. Right click on the &quot;Default SMTP Virtual Server&quot; and choose Properties.
   3. Click on the last tab &quot;Delivery&quot; and then the button &quot;Advanced&quot;.
   4. In the box labelled &quot;Fully Qualified Domain Name&quot; enter the name that your server is known as on the Internet - mail.domain.com for example.
      Do not bother with &quot;Check DNS&quot; as it will probably fail.

Make sure that the &quot;fully-qualified domain name&quot; field entry matches your PTR record. From now your emails should be delivered without any problems. 

Hope that helps.

Maciek
IT Engineer]]></description>
      <category>SERVER</category>
      <guid isPermaLink="true">http://www.iternity.co.uk/phorum/read.php?7,49,49#msg-49</guid>
      <pubDate>Mon, 15 Jun 2009 16:00:26 +0200</pubDate>
    </item>
    <item>
      <title>Active Sync mobile authentication problems - iPhone, Mail for Exchange: your account does not have permission to sync with current settings</title>
      <link>http://www.iternity.co.uk/phorum/read.php?7,48,48#msg-48</link>
      <author>iternity</author>
      <description><![CDATA[iPhone, Mail for Exchange - Active Sync mobile authentication problems

We had several iPhone users complainnig about not beeing able to connect to one of the exchange mail servers. Email settings worked up to the stage when you had to accept security certivicate (self signed in this case). Then, sudden disconnection was happening and error was given that the server's address cannot be verified. 

All usuall Exchange Manager Active settings were on and users were allowed to use OWA and active sync from their Exchange Properties tabs.

More, same users were able to connect and use emails via Outlooks and OWA. Weird...

As we did not have any iPhone handy, we tested the server with Nokia's Mail for Exchange, which was also failing, but this time we had a bit more info to work on. The log error message was giving this error:

'your account does not have permission to sync with current settings'.

It appeared that some of the IIS OWA folders were set up with wrong secutity settings. There are IIS 3 folders to check under Default Web Site:

- Exchange
- Exchweb
- Microsoft-Server-ActiveSync

Some of them were marked as available only to several local IP addresses from security options. Some of them were querying clients for client-side certificates as well. After granting access to this folders from all IPs and ignoring Client certificates all started to work. 

We used following web-based exchange testing tool to tackle down last folder: 

https://www.testexchangeconnectivity.com/

Good thing about it is that while testing ActiveSync it returns full HTML errors codes from IIS. I am not a huge fan of giving server's access details to 3rd parties (no mather how secure they claim they are), but in this case it paid off to create temporary testing account, run the web-tests through it and delete it afterwards. 

It may be a good idea to check properties of: 

- Exadmin
- Exchange-oma
- OMA

In case some of the security settings are wrong there.

Hope that description helps some of you guys to find sollution to your own problems. 

All the best

Maciek
IT Engineer
iternity.co.uk]]></description>
      <category>SERVER</category>
      <guid isPermaLink="true">http://www.iternity.co.uk/phorum/read.php?7,48,48#msg-48</guid>
      <pubDate>Mon, 08 Jun 2009 16:57:57 +0200</pubDate>
    </item>
    <item>
      <title>SBS 2003 shutting down. Event log shows “This computer must be configured as a domain controller”</title>
      <link>http://www.iternity.co.uk/phorum/read.php?7,31,31#msg-31</link>
      <author>iternity</author>
      <description><![CDATA[Have you ever wanted to use your license of Microsoft Small Business Server, just to use the base Windows Server 2003 portion? I know, I know, there are so many advantages to having a domain and using exchange, etc... etc... etc... But what if you are reinstalling your old server to re-use as a plain workstation or just test facility behind your normal domain controller? Full featured SBS installation will cause problems in your current AD environment…

Going through the SBS install, when you skip the follow-on steps after installing Windows Server 2003 all will be fine for exactly 1 week. Then for some reason, the server will begin to shut down, hourly.

Event Viewer shows this:

&quot;This computer must be configured as a domain controller. It will be shut down in 60 minutes. To prevent this computer from shutting down, run Setup on the disk that you used to install the operating system to configure the computer as a domain controller.&quot;

See: support.microsoft.com/kb/555087

Situation: According to your MS SBS licence, you have 7 days to finish off your installation. Then, you HAVE TO install Active Directory services. If you do not install them, MS will force your server to restart every hour and NET SEND &quot;this server doesn't comply with licensing requirements&quot; across the entire network. 

Cause: There is a special service running in the system which is causing your problems. Of course, this service cannot be disabled via the MMC snap-in.

Here is the solution: 

Tools you'll need: Process Explorer from www.sysInternals.com

As you probably noticed, you have a service called SBCore or &quot;SBS Core Services&quot;, which executes the following process: C:\WINDOWS\system32\sbscrexe.exe

If you kill it, it just restarts – and if you try and stop it you are told Access Denied.

If you fire up Process Explorer, you can select the process and Suspend it, now we can start to disable the thing.

Run RegEdit32.exe and expand the nodes until you reach the following key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SBCore

Right click this, hit permissions and give the &quot;Administrators&quot; group on the local machine full access (don't forget to replace permissions on child nodes ). F5 in regedit and you'll see all of the values and data under this key.

Select the &quot;Start&quot; DWORD and change it from 2 to 4 – this basically sets the service to the &quot;Disabled&quot; state as far as the MMC services snap-in (and windows for that matter) is concerned. 

It is good to also switch off any service recovery attempts by deleting “Failure Actions” key. This stop service recovery errors in Event logs.

Next, adjust the permissions on the file C:\WINDOWS\system32\sbscrexe.exe so that EVERYONE account is denied any sort of access to this file.

Then go back to process explorer, and kill the sbscrexe.exe process, if it doesn't restart – congratulations!

Load up the services MMC snap-in and you should find that &quot;SBS Core Services&quot; is stopped and marked as Disabled.

This should keep your server up all the times. Good Luck!
 

Source taken from: www.donnykemick.com]]></description>
      <category>SERVER</category>
      <guid isPermaLink="true">http://www.iternity.co.uk/phorum/read.php?7,31,31#msg-31</guid>
      <pubDate>Thu, 03 Apr 2008 13:23:25 +0200</pubDate>
    </item>
    <item>
      <title>Vista computers run slowly when accessing network drives and domain on Microsoft SBS 2003.</title>
      <link>http://www.iternity.co.uk/phorum/read.php?7,27,27#msg-27</link>
      <author>iternity</author>
      <description><![CDATA[Before taking the following steps, please ensure that  the latest network adapter driver supplied by manufacturer has been installed on the Vista machine. 

Step One 
--------------------------------- 
Turning off auto-tuning on the Vista client may help. 
Please run the following commands on Vista computer attached to SBS 2003 domain: 

1. Go to Accessories / Command Prompt 
2. Right click Command Prompt and click Run as Administrator 
3. Type the following command and press Enter: 

netsh interface tcp set global rss=disabled 
netsh interface tcp set global autotuninglevel=disabled and reboot 

Related Articles: 
934430: Network connectivity may fail when you try to use Windows Vista behind a firewall device 
http://support.microsoft.com/kb/934430/en-us 

555912: Windows 2003 service pack 2 known issues on Small Business Server 2003 
http://support.microsoft.com/kb/555912/en-us 


Step Two 
--------------------------------- 
NOTE: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall Windows. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. 

256986 Description of the Microsoft Windows Registry 
http://support.microsoft.com/?id=256986 

Manually add the following registry key: 

Registry path: HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\System 

Value name: CopyFileBufferedSynchronousIo 
Value type: REG_DWORD 
Value data: 1 


Step Three 
--------------------------------- 
If the problem persists, please test the issue in Safe Mode with Network to see if the issue still occurs in this mode. 

Start your computer in safe mode 
http://windowshelp.microsoft.com/Windows/en-US/Help/323ef48f-7b93-4079-a48a-5c58eec904a11033.mspx 




 

Tomasz Zbikowski]]></description>
      <category>SERVER</category>
      <guid isPermaLink="true">http://www.iternity.co.uk/phorum/read.php?7,27,27#msg-27</guid>
      <pubDate>Mon, 07 Jan 2008 17:45:48 +0100</pubDate>
    </item>
    <item>
      <title>DHCP pointing to .mshome.net 2003 SBS issue</title>
      <link>http://www.iternity.co.uk/phorum/read.php?7,25,25#msg-25</link>
      <author>iternity</author>
      <description><![CDATA[We have recently came across a problem with RRAS interfering with DHCP server in SBS 2003. It usually causes slower than normal access to the server. Some of the workstations may not be able to access the Internet connection as well. 

Upon inspection, it came out that the DHCP configuration was somehow corrupted. The service was running, but it was leasing out weird IP address. Apart from that authorized DHCP server was defaulting to company.mshome.net. 

You cannot reconfigure the scope because it keeps telling that the old scope exists though it does not display the scope nor its associated leased addresses. 

Resolution: 
1. Disable the RRAS and restart DHCP service,
2. Close and reopen DHCP configuration panel and chose reconcile (DHCP server gets back to normal),
3. Now run the wizard for RRAS

Done!

M.]]></description>
      <category>SERVER</category>
      <guid isPermaLink="true">http://www.iternity.co.uk/phorum/read.php?7,25,25#msg-25</guid>
      <pubDate>Tue, 20 Nov 2007 14:27:22 +0100</pubDate>
    </item>
    <item>
      <title>Script-mapping the network share</title>
      <link>http://www.iternity.co.uk/phorum/read.php?7,22,22#msg-22</link>
      <author>iternity</author>
      <description><![CDATA[Here's the command: 

net use Z: \\computername\sharename password /user:domain\username /persistent:no]]></description>
      <category>SERVER</category>
      <guid isPermaLink="true">http://www.iternity.co.uk/phorum/read.php?7,22,22#msg-22</guid>
      <pubDate>Wed, 17 Oct 2007 13:27:12 +0200</pubDate>
    </item>
    <item>
      <title>Moving the Data folders on SBS 2003</title>
      <link>http://www.iternity.co.uk/phorum/read.php?7,16,16#msg-16</link>
      <author>iternity</author>
      <description><![CDATA[This is the sollution from Microsoft:
SBS_MoveDataFolders.pdf
All copyright belong to Microsoft Corporation.]]></description>
      <category>SERVER</category>
      <guid isPermaLink="true">http://www.iternity.co.uk/phorum/read.php?7,16,16#msg-16</guid>
      <pubDate>Wed, 26 Sep 2007 12:54:04 +0200</pubDate>
    </item>
    <item>
      <title>Exchange: Mialbox access rights</title>
      <link>http://www.iternity.co.uk/phorum/read.php?7,14,14#msg-14</link>
      <author>iternity</author>
      <description><![CDATA[AD/User Properties/Exchange Advanced/Mailbox rights. Add a user which should have the access.]]></description>
      <category>SERVER</category>
      <guid isPermaLink="true">http://www.iternity.co.uk/phorum/read.php?7,14,14#msg-14</guid>
      <pubDate>Mon, 24 Sep 2007 14:04:14 +0200</pubDate>
    </item>
    <item>
      <title>Exchange: Send on behalf on SBS 2003</title>
      <link>http://www.iternity.co.uk/phorum/read.php?7,13,13#msg-13</link>
      <author>iternity</author>
      <description><![CDATA[On the accounth inAD, check EXCHANGE GENERAL&gt;&gt;DELIVERY RESTRICTIONS add users which may send on behalf.]]></description>
      <category>SERVER</category>
      <guid isPermaLink="true">http://www.iternity.co.uk/phorum/read.php?7,13,13#msg-13</guid>
      <pubDate>Mon, 24 Sep 2007 14:02:24 +0200</pubDate>
    </item>
    <item>
      <title>Implementing the Change Password feature with Outlook Web Access</title>
      <link>http://www.iternity.co.uk/phorum/read.php?7,11,11#msg-11</link>
      <author>iternity</author>
      <description><![CDATA[This article was previously published under Q297121
Important This article contains information about how to modify the registry. Make sure you back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 (http://support.microsoft.com/kb/256986/) Description of the Microsoft Windows registry
On This Page
SUMMARY
MORE INFORMATION
How to configure the IISADMPWD virtual directory
Enable and hide the Change Password button in Outlook Web Access
Usage scenarios
Exchange 2000 in front-end and back-end configurations
Troubleshooting
SUMMARY
This article discusses how to implement the Change Password feature in Microsoft Outlook Web Access (OWA) to allow OWA users to change their domain passwords. This article also describes some of the common troubleshooting scenarios in which you might use this feature.

The Change Password feature is provided by Microsoft Internet Information Services (IIS). The Change Password feature is not specific to Microsoft Exchange Server. This feature in IIS is implemented through the IISADMPWD virtual directory. In Microsoft IIS 5.0 and in Microsoft IIS 6.0, you must manually create and configure this virtual directory. In Microsoft IIS 4.0, this virtual directory is created by default, but it must be manually configured.

Back to the top
MORE INFORMATION
Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require you to reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

Back to the top
How to configure the IISADMPWD virtual directory
A Secure Sockets Layer (SSL) certificate is required to use the Change Password feature with Outlook Web Access. This is true for all versions of Exchange Server. When you use the Change Password feature with SSL, the communication is encrypted. OWA uses HTTPS requests to access the Change Password feature.

To configure SSL, you must obtain a server certificate for the Web server. You can use Microsoft Certificate Server or a third-party certificate server. You obtain a Web server certificate that IIS uses to enable SSL. For additional information about how to obtain and install an SSL certificate, view the following IIS Help topics:
• Obtain an SSL Certificate
• Configure SSL
For more information about how to use certificates with IIS and with Exchange Server, click the following article numbers to view the articles in the Microsoft Knowledge Base:
228821 (http://support.microsoft.com/kb/228821/) Generating a certificate request file using the Certificate Wizard in IIS 5.0
228836 (http://support.microsoft.com/kb/228836/) Installing a new certificate with Certificate Wizard for use in SSL/TLS
234022 (http://support.microsoft.com/kb/234022/) Configuring Exchange OWA to use SSL
320291 (http://support.microsoft.com/kb/320291/) Turning on SSL for Exchange 2000 Server Outlook Web Access
823024 (http://support.microsoft.com/kb/823024/) How to use certificates with virtual servers in Exchange Server 2003
Note If you are using Exchange front-end servers in your environment, SSL should only be enabled on these servers. In a single-server environment, SSL needs to be enabled on the Exchange server itself.

The following values are options for the PasswordChangeFlags setting:
• 0: Requires password change by SSL
• 1: Allows password change by non-secure ports
• 2: Disables password changes
If you are using an off-loaded SSL configuration, an SSL accelerator, you can change this value to &quot;1.&quot; To do so, follow these steps:
1. On the IIS/OWA server, click Start, click Run, type cmd, and then click OK.
2. At the command prompt, type the following command, and then press the Enter key.

cd \:inetpub\AdminScripts


For example: cd c:\inetpub\AdminScripts
3. The command prompt returns. Now type the following command:

adsutil.vbs set w3svc/passwordchangeflags 1


The value &quot;1,&quot; per the list that was provided earlier in this article, allows the Change Password functionality by using non-secure ports.
Before configuring the Change Password feature, make sure that the following fixes have been applied to all Exchange servers:
• For Windows 2000 (All versions of Exchange)
831047 (http://support.microsoft.com/kb/831047/) FIX: You experience various problems when you use the Password Change pages in IIS 5.0
• For Windows 2003 (All versions of Exchange)
833734 (http://support.microsoft.com/kb/833734/) FIX: You experience various problems when you use the Password Change pages in IIS 6.0


Note The files from this hotfix are included in Microsoft Windows Server 2003 Service Pack 1 (SP1).
To configure the IISADMPWD virtual directory, do the following:
1. Click Start, point to Programs, point to Administrative Tools, and then click Internet Services Manager.
2. Right-click the default website, point to New, and then click Virtual Directory.
3. In the Virtual Directory Creation wizard, type IISADMPWD in the Alias box, and then click Next.
4. In the Directory box, type :\winnt\system32\inetsrv\iisadmpwd or the location where your hard disk is your default hard disk, and then click Next.
5. Verify that only the Read and Run script check boxes are selected, such as the ASP check box, click Next, and then click Finish.
6. Verify that the IISADMPWD virtual directory has only basic authentication set and, if you use Windows 2003/IIS 6.0, verify that the application pool is set to ExchangeApplicationPool.
In Internet Information Server (IIS) 4.0 and in Internet Information Services (IIS) 5.0, the Change Password functionality is handled through an ISAPI extension, Ism.dll. This component has been removed from Internet Information Services versions 5.1 and 6.0, and the Change Password functionality has been modified to use Active Server Pages (ASP). A package that can be downloaded has been created to deliver this ASP functionality for servers that are running IIS 5.0 on Microsoft Windows 2000 Server Service Pack 3 (SP3) or for servers that are running IIS 4.0 on Microsoft Windows NT 4.0 Server Service Pack 6a (SP6a).

Note This package has been tested and it has been approved for use with Microsoft Exchange Server 5.5 and with Exchange 2000 Server Outlook Web Access. Because OWA references these files with an .htr extension, if you manually rename the files, OWA cannot use the change password functionality. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
331834 (http://support.microsoft.com/kb/331834/) Change password functionality replaced with Active Server Pages

Back to the top
Enable and hide the Change Password button in Outlook Web Access
Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

Note This registry value must be enabled on both front-end and back-end servers.

For Exchange 2000 Server and for Exchange Server 2003, you can use the registry to show or hide the Change Password button. To do this, follow these steps.
1. Start Registry Editor, and then locate the following registry key:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeWeb
2. If an OWA key is not present under MSExchangeWeb, click the Edit menu, click New, and then click Key to add a new key named OWA.
3. Locate the DisablePassword value and change the data to &quot;0.&quot; If this value is not present, click the Edit menu, click New, click DWORD_Value to add the following value to the OWA registry subkey if you want the Change Password button to appear:

Value name: DisablePassword
Value type: REG_DWORD
Data: 0

If you want to hide the Change Password button, change the DisablePassword value data to &quot;1.&quot;
4. Stop and then restart the Exchange Information Store Service and the IIS Admin Service. This stops and restarts the World Wide Web Publishing Services (W3SVC). In an Exchange 2000 Server environment, restarting the IIS Admin Service restarts the Microsoft Exchange System Attendant and the Microsoft Exchange Information Store.
5. Make sure that you all the dependent services that you require are restarted, such as IMAP4, POP3, Microsoft Exchange Routing Engine, W3SVC, MTA Stacks.
To remove the Change Password button in Outlook Web Access for Exchange Server 5.5, follow these steps :
1. Locate the Constant.INC file. This file is typically found in the Exchsrvr\Webdata\USA (or language required) directory on the Outlook Web Access server.
2. Under the Administrative Settings section, and then locate the following line:

fEnablePasswordMenu=True

3. Replace this line with the following text:

fEnablePasswordMenu=False

4. On the File menu, click Save, and then close the file.
5. To verify, start the Internet browser on the Outlook Web Access server. The Change Password button no longer appears.

Back to the top
Usage scenarios
Exchange 2000 in front-end and back-end configurations
If you use a front-end server, you must configure the IISADMPWD virtual directory and SSL on the front-end server. If there are multiple front-end servers in your environment, SSL and the IISADMPWD virtual directory must be configured on each server.

Note The only case where configuring this feature is recommended on a back-end server is in a single Exchange Server environment. In this environment, Internet users access Outlook Web Access on the back-end server directly.

However, if a front-end server is used and you want to enable this feature on the back-end Exchange Server computers, be cautious in how you implement SSL requirements on the back end. Specifically, make sure that you do not require SSL on the Exchange, Public, ExchWeb, Exadmin virtual directories, or on any Mailbox or Public Folder virtual roots on the back-end server. If this is set, the front-end server cannot communicate with a back-end server.

Microsoft requires SSL on the IISADMPWD virtual directory.

While the Change Password feature is independent of Outlook Web Access, it must be implemented on the server that the client interacts with directly. This server is typically the front-end server. However, the Change Password URL that OWA exposes on the Options page is generated on the back-end server. Therefore, the file extension that is .htr or .asp is dictated by the version of IIS on the back-end server rather than the file set that exists on the front-end server. A “Page not found” or 404 error may occur when a user attempts to change their password through OWA. This issue is described further later in this article.

The following table lists the file to be referenced. The table is based on the version of Windows on the back-end server:
Back-end Exchange 2000 Windows 2000 SP4 Back-end Exchange 2003 Windows 2000 SP4 Back-end Exchange 2003 Windows 2003
Front-end Exchange 2000 Windows 2000 SP4 Aexp2b.htr Not supported Not supported
Front-end Exchange 2003 Windows 2000 SP4 Aexp2b.htr Aexp2b.htr Aexp2b.asp (See Note later in this article) **
Front-end Exchange 2003 Windows 2003 Aexp2b.htr (See Note later in this article) * Aexp2b.htr (See Note later in this article) * Aexp2b.asp
* When the back-end server is Windows 2000 (IIS 5.0) and the front-end server is Windows 2003 (IIS 6.0), users who attempt to change their password through Outlook Web Access (OWA) will get a 404 or a “Page not found” error message in their browser. This error message appears because the URL that is generated by the back-end server points to the Aexp2b.htr file. However, this file does not exist by default on a Windows 2003 front-end server. Therefore, you must copy the appropriate set of files to the front-end server and configure the front-end server to handle these files correctly.

To do this, follow these steps:
1. At the command prompt on the front-end server, change to the %windir%\system32\inetsrv\IISADMPWD directory. Type the following:

copy Aexp2b.asp Aexp2b.htr

2. Add a Script Mapping for the .htr extension on the front-end server.
• In the ISM browse to the IISADMPWD virtual directory that you created, right-click to select the properties.
• On the Virtual Directory tab, click Configuration.
• On the Mappings tab, click Add.
• Add a Script Mapping with the following criteria:
Executable: %windir%\system32\inetsrv\asp.dll
Extension: .htr
Limit to: GET,POST
Leave “Script engine” and “Verify that file exits” checked.
This is similar to the issue that is mentioned earlier in this section. However, in this particular case, the Windows 2003 back-end server pushes a URL that ends in Aexp2b.asp that does not exist on the Windows 2000 front-end server. The solution is to copy the appropriate set of files to the front-end server as follows:
1. From a command prompt on the front-end server, change to the %windir%\system32\inetsrv\iisadmpwd directory
2. Type the following command:

copy Aexp2b.htr Aexp2b.asp



Note For this solution to work Windows 2000 SP4 must be applied to this server prior to performing the copy command that is described earlier in this section.
Note The steps are the same for clustered Exchange servers. When front-end servers are in use with an Exchange cluster, no configuration is necessary on the cluster itself.

Back to the top
Troubleshooting
This section contains some common troubleshooting scenarios for issues that can occur by using the Change Password feature of Outlook Web Access.
• We recommend that you view the following articles:
831047 (http://support.microsoft.com/kb/831047/) You experience various problems when you use the Password Change pages in IIS 5.0
833734 (http://support.microsoft.com/kb/833734/) You experience various problems when you use the Password Change pages in IIS 6.0
• When you create the IISADMPWD virtual directory, make sure that the following permissions are enabled:
Read
Run Scripts (such as ASP)
• When you type your account information in the password change page, you must type your credentials in the domain \ username format.
• In mixed Windows 2000 Server and Windows Server 2003 environments, you may receive an “HTTP 404 – File Not Found” error message when you try to change your password. The behavior occurs because Windows 2000 and IIS 5.0 use .htr files for the Change Password functionality. Make sure that you have updated your Windows system running Outlook Web Access to use ASP pages in the manner that is described in the following Microsoft Knowledge Base article
331834 (http://support.microsoft.com/kb/331834/) Change password functionality replaced with Active Server Pages
To work around this issue, do the following:
1. Copy the appropriate files from the operating system that your front-end server is not running to the IISADMPWD folder on your front-end server. The IISADMPWD folder is located in the following folder: %SystemRoot%\System32\Inetsrv\IISADMPWD To copy the files from the other operating system, use one of the following methods, depending on your situation:
• At a command prompt, locate the IISADMPWD folder (%SystemRoot%\System32\Inetsrv\IISADMPWD), type copy *.asp *.htr, and then press ENTER. This command makes copies of all the .asp files that are in the current folder and it renames the copies with an .htr extension.
• Copy the .htr files from the IISADMPWD folder on the computer that is running Windows 2000 Server to the IISADMPWD folder on the computer that is running Windows Server 2003.
2. Start Internet Services Manager on the computer that is running Windows Server 2003.
3. Expand Default Web Site, right-click IISADMPWD, and then click Properties.
4. Click Configuration, and then click Add.

Note If the Configuration button is unavailable or it appears dimmed, click Create, and then click Configuration.
5. Click Browse, and then click Asp.dll in the Windows\System32\Intesrv folder.
6. In the extension box, type htr.
7. In Administrative Tools, double-click Services, and then restart the IISAdmin service.
• You experience “Cannot find server” or “The page you are looking for is currently unavailable.” This behavior may occur when IIS is not configured to allow the Change Password feature, or when the feature is disabled in the registry.
• If the IISADMPWD virtual directory that you create is in a Web site other than the Default Web Site, you may experience “HTTP 404 – File Not Found” errors in Exchange Server environments. To resolve this issue, make sure that the correct hard disk location of the IISADMPWD files appears in the Directory box in the properties of the IISADMPWD virtual directory. For more information, see the &quot;How to configure the IISADMPWD virtual directory&quot; section.
• Make sure that the IISADMPWD virtual directory runs in the same application pool as the Web site that uses the Password Change functionality. For example, if the Password Change functionality is used in your Outlook Web Access Web site, the IISADMPWD virtual directory must run inside the Exchange application pool where the Outlook Web Access site resides.
• You receive the warning, &quot;Your current password is about to expire in 0 days. To change your password, go to the Options page after you login&quot; in Outlook Web Access. This can occur when the pwdLastSet property on the enabled Windows user account does not match the pwdLastSet property on the corresponding disabled Windows user account in the Exchange resource forest. This can occur when users are migrated from one resource forest to another resource forest. The user can either disregard the warning message in Outlook Web Access, if they have recently reset their Windows user account password, or reset their password by way of Outlook Web Access so they no longer receive the error message.]]></description>
      <category>SERVER</category>
      <guid isPermaLink="true">http://www.iternity.co.uk/phorum/read.php?7,11,11#msg-11</guid>
      <pubDate>Mon, 24 Sep 2007 13:22:33 +0200</pubDate>
    </item>
    <item>
      <title>Enabling OWA Change Password feature</title>
      <link>http://www.iternity.co.uk/phorum/read.php?7,10,10#msg-10</link>
      <author>iternity</author>
      <description><![CDATA[Today I enabled our network users to reset their passwords from Outlook Web Access(OWA). OWA is also capable of prompting users to change their passwords, but this functionality is not enabled by default in Exchange 2003, unlike in earlier versions of Exchange.

Before you even consider turning on this feature in OWA, please make sure your OWA operates over a secure encrypted link (SSL), because if deployed in a non-secure environment, it could compromise your network.

Steps to enable password change functionality;

1. Change registry key to unhide the 'change password' button in OWA as in Fig 1 at (HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\
Services\MSExchangeWEcool smiley to 0. The default value is 1. This should enable 'Password' column.

2. Then create a virtual directory on the Exchange server in IIS. The virtual directory must be part of the Outlook Web Access website. The name of the directory is 'iisadmpwd' and it must point to the %windir%\System32\Inetsrv\iisadmpwd folder. Enable script reading on the virtual directory.

Once you've successfully completed the above steps, you are now ready to test that the new functionality does indeed work, and when you click on the Change Password button (as in Fig 1) you should get a page that provides you the option of resetting your password as in Fig 2.


Well, I hope this makes your life easy as it is for me. E-mail in your comments or questions.]]></description>
      <category>SERVER</category>
      <guid isPermaLink="true">http://www.iternity.co.uk/phorum/read.php?7,10,10#msg-10</guid>
      <pubDate>Mon, 24 Sep 2007 13:20:22 +0200</pubDate>
    </item>
    <item>
      <title>Step-By-Step: The three tasks in building a tape backup</title>
      <link>http://www.iternity.co.uk/phorum/read.php?7,9,9#msg-9</link>
      <author>iternity</author>
      <description><![CDATA[Setting up your methodology
Your next step is to determine the best methodology for backing up your data. Most commercial backup software systems allow for a wide array of options. The most common are the following:

* Full: This methodology transfers a copy of all data within the scope of the backup to tape, regardless of whether the data has been changed since the last backup was performed.
* Differential: This methodology backs up all files changed since the last full backup, regardless of whether they have been changed since the last backup operation of any kind.
* Incremental: Here, only those files that have changed since the last backup operation of any kind (full, differential, or incremental) will be transferred to tape.


Essentially, the method you choose will depend on your tape capacity and your need for a very speedy recovery. For example, by running a full backup daily, you will need a very large amount of tape capacity, but will need only the last backup tape to restore all data.

Conversely, using a full backup once a week with an incremental daily lets you use much less tape space, but a recovery would require the last full backup and each incremental to be fed back onto the servers. Most organisations will utilise a combination of methodologies that allows them to conserve tape space while still allowing data to be quickly restored. Using weekly full backups with daily incremental backups is generally considered the strategic norm.

Rotating your tapes
Next you will need to develop a tape rotation scheme and decide where to store your tape media. Unfortunately, most companies store physical backup media within about three feet of the servers they protect. As recent physical disasters have shown us, this is not a prime way to protect data since the tapes stand a very good chance of being lost with the servers in a disaster. Physical media needs to be stored off-site in a secure location from which it can be retrieved quickly if needed.

To reduce costs for both media and off-site storage, a good tape-rotation scheme is essential. By reusing tapes after a predetermined period of time, tape rotation schemes ensure that a minimum number of tapes are stored off-site. Rotation schemes come in several flavours and complexities.

Perhaps the most common rotation scheme is Grandfather-Father-Son (GFS), which has been in use for quite some time and has proven to be effective. In the generic version of this scheme, full backups are done at two intervals. The first interval is monthly, and that media is immediately stored off-site (grandfather). Weekly full backups are also performed (father), and these are generally held on-site for the week of their use, then moved off-site for a predetermined number of weekly cycles (two or three cycles is generally sufficient).

Daily incremental backups are performed (son) and stored on-site for the week of their use as well, then moved off-site with the corresponding weekly backup on the same cycle schedule. At the end of a cycle for a set of tapes, those tapes can be returned to the system and reused. Each monthly tape would be held for 12 months before being reused.

Weekly tape sets are generally held for about three weeks after they leave the server room (so about four weeks total) and are then reused. The number of times a tape can be reused is determined by the type of media, so check with the manufacturer to ensure you don’t overuse a tape.

GFS rotation schemes allow for the monthly backups to be immediately stored in a secure location, while the most current weekly full backups and incrementals are housed for immediate use in restoration, then allowed to sit off-site in case of a catastrophic failure. While there is some limited liability inherent in this system (you could lose up to one week of data if you suffer a fire or some other disaster), this system offers the highest security with the lowest cost.

Of course, your organisation may require more security, in which case you can always courier tapes off-site as they are generated. While this is a great system for data protection, keep in mind you will need to get those tapes back on-site for restoration purposes, which will increase courier and other costs.]]></description>
      <category>SERVER</category>
      <guid isPermaLink="true">http://www.iternity.co.uk/phorum/read.php?7,9,9#msg-9</guid>
      <pubDate>Mon, 24 Sep 2007 13:15:01 +0200</pubDate>
    </item>
    <item>
      <title>SBS 2003 Fax Console cannot re-route faxes to email</title>
      <link>http://www.iternity.co.uk/phorum/read.php?7,5,5#msg-5</link>
      <author>iternity</author>
      <description><![CDATA[Verify that automatic routing is enabled for email and Sharepoint. There are two ways to do this (A. Run the Configure Fax wizard or B. Check it Manually). I will provide steps for both.

A. Run the Configure Fax wizard

1. Open the Server Management Console.
2. Click the To Do List.
3. Click the Configure Fax link.
4. Run the wizard.
a. Make sure the &quot;Route through E-mail&quot; method is checked and that a valid e-mail address is specified.
b. Make sure the &quot;Store in a document library&quot; method is checked and that a valid document library is specified.
5. Finish the wizard.

B. Verify Fax Routing is Enabled and Configured.

Enable E-mail Receipt

1. Click Start, point to All Programs, point to Accessories, point to Communications, point to Fax, and then click &quot;Fax Service Manager&quot;.

2. In the console tree in the left panel, right-click the &quot;Fax (Local)&quot; node, and then click Properties.

3. On the Receipts tab, verify the &quot;Enable SMTP e-mail receipts delivery&quot; check box is checked.

4. In the From e-mail address: box, type the e-mail address of the sender of the fax. For example, SBSFaxService@domain.local.

5. 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 &quot;hostname&quot; (without the quotation marks) at the command prompt, and then press ENTER.

6. In the Port: box, type &quot;25&quot; (without the quotation marks). If the SMTP port has changed, type the appropriate port.

7. Verify the &quot;Use these SMTP settings for the Route Through E-Mail incoming routing method&quot; check box is checked.

8. Click the Authentication button, verify the &quot;Anonymous access&quot; option is selected, and click OK.

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:

1. Start the Exchange System Manager.

2. If the administrative groups are displayed, expand Administrative Groups, and then expand &quot;&quot;.

3. Expand Servers, expand [your server] , expand Protocols, and then expand SMTP.

4. Right-click &quot;Default SMTP Virtual Server&quot;, click Properties, click the Access tab, and click the Authentication button.

5. Verify Anonymous access is selected.

Enable Incoming Fax Routing Methods

1. In the Fax Service Manager console, expand Devices and Providers, expand Devices, expand , and click on Incoming Methods.

2. Verify the &quot;Route through E-mail&quot; method is enabled.

3. Right-click the &quot;Route through E-mail&quot; method and click Properties. Click the E-mail tab and verify that a valid email address is specified.
Click OK.

4. Verify the &quot;Store in a document library&quot; method is enabled.

5. Right-click the &quot;Store in a document library&quot; method and click Properties. Click the Fax Routing tab and verify that a valid document library is specified. Click OK.

6. Restart the Fax service.]]></description>
      <category>SERVER</category>
      <guid isPermaLink="true">http://www.iternity.co.uk/phorum/read.php?7,5,5#msg-5</guid>
      <pubDate>Mon, 24 Sep 2007 12:52:33 +0200</pubDate>
    </item>
  </channel>
</rss>
