Some points to improve the shutdown times

Start Registry Editor and navigate to the following key:

[HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management]

Set ClearPageFileAtShutdown value to 0

Or, using Group Policy Editor [for Windows XP Professional]

Click Start, Run and type Secpol.msc
Click Local Policies | Security Options
In the right-pane, set Shutdown: Clear virtual memory pagefile to Disabled

How to create acronis bootable on flash drive

1. format flash drive follow the screen.




2. copy menu.lstand grldr to flash drive




3. create folder and copy acronis.iso


=========menu.lst code=========
title Acronis True Image Home 2009 (9,615)
map (hd0,0)/acronis/AcronisMedia.iso (hd32)
map --hook
chainloader (hd32)
boot
=========



For more details refer to http://www.themudcrab.com/acronis_grub4dos.php

Exchange version

Version Number Service Pack Release Date
4.0.837.10 Microsoft Exchange Server 4.0 RTM April 1996
4.0.838.15 Microsoft Exchange Server 4.0 SP1 May 1996
4.0.993.40 Microsoft Exchange Server 4.0 SP2 (4.0a) August 1996
4.0.994.64 Microsoft Exchange Server 4.0 SP3 November 1996
4.0.995.54 Microsoft Exchange Server 4.0 SP4 April 1997
4.0.996.00 Microsoft Exchange Server 4.0 SP5 May 1998

5.0.1457.10 Microsoft Exchange Server 5.0 RTM March 1997
5.0.1458.50 Microsoft Exchange Server 5.0 SP1 June 1997
5.0.1460.13 Microsoft Exchange Server 5.0 SP2 February 1998

5.5.1960 Microsoft Exchange Server 5.5 RTM February 1998
5.5.2232 Microsoft Exchange Server 5.5 SP1 July 1998
5.5.2448 Microsoft Exchange Server 5.5 SP2 December 1998
5.5.2650 Microsoft Exchange Server 5.5 SP3 September 1999
5.5.2653 Microsoft Exchange Server 5.5 SP4 November 7, 2000

6.0.4417 Microsoft Exchange Server 2000 RTM October 2000
6.0.4712 Microsoft Exchange Server 2000 SP1 July 2001
6.0.5762 Microsoft Exchange Server 2000 SP2 December 2001
6.0.6249 Microsoft Exchange Server 2000 SP3 July 18, 2002
6.0.6396.1 Microsoft Exchange Server 2000 post-SP3 March 2003
6.0.6487 Microsoft Exchange Server 2000 post-SP3 August 27, 2003
6.0.6556 Microsoft Exchange Server 2000 post-SP3 April 2004
6.0.6603.1 Microsoft Exchange Server 2000 post-SP3 August 16, 2004
6.0.6617.52 Microsoft Exchange Server 2000 post-SP3
with Security Update MS05-021 April 12, 2005

6.5.6944 Microsoft Exchange Server 2003 RTM October 2003
6.5.7226 Microsoft Exchange Server 2003 SP1 May 2004
6.5.7638 Microsoft Exchange Server 2003 SP2 October 19, 2005

Service - Browser

The browser has forced an election on network \Device\NetBT_Tcpip_{E5F369B3-DDBB-4D59-8BEF-DBC518B76FCE} because a master browser was stopped.

Try to fix by changing registry. Refer to http://support.microsoft.com/kb/135404

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Browser\Parameters]
"IsDomainMaster"="FALSE"
"MaintainServerList"="FALSE"

Firewall HTTP Proxy in non-transparent mode

http://kb.endian.com/entry/22/





You can let the browsers get the proxy configuration automatically. Only precondition is, that you roll out the browsers with "Auto-detect proxy settings" enabled, which is default for both Firefox and Internet Explorer.

If you use the DHCP server or DNS proxy (or both) of Endian Firewall, there is no more to do. Otherwise you have two possibilities to make your clients find the proxy configuration on Endian Firewall:
1. Add a hostname to your local DNS called "wpad" and make it point to the Endian Firewall. You then should be able to reach Endian Firewall by accessing http://wpad/, otherwise it will not work.
2. Add a custom option to your DHCP server in order to make it push the wpad url with the other DHCP information.
Example for ISC DHCP server:

Global option:

option wpad code 252 = text;

Option for each subnet configuration:

option wpad "http://YOUR_EFW_IP_ADDRESS/proxy.pac";

Replace YOUR_EFW_IP_ADDRESS with the zones respective IP address of your Endian Firewall.
Note: If you like to force your users to use the proxy, you need to block HTTP ports within the outgoing Proxy. Otherwise a user may disable the Proxy within his/her browser and simply go directly without being blocked.

Granular Recovery Technology (GRT)

An Exchange backup to disk/tape with the Granular Recovery Technology (GRT) enabled completes successfully but with an exception "The Backup Exec Remote Agent on the resource does not support the option to enable the restore of individual items"

 

Problem

 

An Exchange backup to disk/tape with the Granular Recovery Technology (GRT) enabled completes successfully but with an exception "The Backup Exec Remote Agent on the resource does not support the option to enable the restore of individual items"

Error

 

The Backup Exec Remote Agent on the resource does not support the option to enable the restore of individual items. A backup was run, but you will not be able to restore individual items from this backup set

Solution

 

In Backup Exec 11.x/12.x Exchange GRT backups to disk/tape may complete successfully but the job log reports an exception as shown above. The backup job does not collect or display any GRT information.

If Backup Exec debugging is enabled while running the Exchange GRT backup, then the following messages are logged in the debug logs. Please refer the Related Documents section below for more information on how to enable the debugging.


The Backup Exec Job Engine debug log on the Backup Exec server reports the following error:
------------------------------------------------------------------------------------------------------------------------------
[2944] 09/08/08 09:48:59 Application server(Exchange.domain.local) supports PDI
[2944] 09/08/08 09:48:59 Querying PDI data store server(BEXEC) for PDI support.
[2944] 09/08/08 09:48:59 NDMPAgentConnector:SetupConnection(): Data Server = BEXEC
[2944] 09/08/08 09:48:59 Could not resolve the 'ndmp' service, error: 10109, using port 10000
[2944] 09/08/08 09:48:59 ndmpConnectEx: 'BEXEC' resolves to the local machine itself. So, we will try and connect to a loopback address ...
[2944] 09/08/08 09:48:59 ndmpConnectEx : Control Connection information: A connection was established between end-points 127.0.0.1:19585 and 127.0.0.1:10000.
[2944] 09/08/08 09:48:59 NDMP version 3 connection CONNECTED
[2944] 09/08/08 09:48:59 NDMPAgentConnector::AuthenticateClient(): Using SSPI authentication with SLA/DLA as a fallback
[2944] 09/08/08 09:48:59 NDMPAgentConnector::ConnectAuthUseSSPIasDefault(): Attempting SSPI authentication...
[2944] 09/08/08 09:48:59 NDMP_SSPI: InitializeSecurityContext status 0x00090312 in 0 out 53
[2944] 09/08/08 09:48:59 NDMP_SSPI: InitializeSecurityContext status 0x00000000 in 190 out 72
[2944] 09/08/08 09:48:59 NDMP_SSPI: client authenticated with server
[2944] 09/08/08 09:48:59 NDMPAgentConnector::ConnectAuthUseSSPIasDefault(): SSPI authentication success.
[2944] 09/08/08 09:48:59 Enabling Shared Buffers Connection type
[2944] 09/08/08 09:48:59 PDI data store server(BEXEC) does not support PDI
[2944] 09/08/08 09:48:59 @@@@@@@MyCloseSocket called with sockfd = 1576(0x628) retval = 0
-------------------------------------------------------------------------------------------------------------------------------------

the Backup Exec Remote Agent debug log on the Backup Exec server reports an error while loading Exchange related Backup Exec dll's (bedsxese.dll and bedsmbox.dll etc.)
------------------------------------------------------------------------------------------------------------------------------------
[0904] 07/31/08 20:16:23   loaded bedsxchg.dll
[0904] 07/31/08 20:16:23   bedsxese.dll could not be loaded: The specified module could not be found.
[0904] 07/31/08 20:16:23   bedsmbox.dll could not be loaded: The specified module could not be found.
[0904] 07/31/08 20:16:23   bedspush.dll could not be loaded: The specified module could not be found.
--------------------------------------------------------------------------------------------------------------------------------------

SOLUTION:

1. On the Backup Exec server download the "Dependency Walker" tool from the following link
http://www.dependencywalker.com/ 

2. Launch the "depends.exe" tool and click on "Open" under the File Menu as shown below:


3. Browse to the installation directory of Backup Exec and attempt to load the "BEDSXESE.DLL". The default installation directory for Backup Exec is "C:\Program Files\Symantec\Backup Exec".

4. The Dependency Walker console will log an exact error in red in the lower half of the console that will report why the "bedsxese.dll" could not be loaded.  The most common errors that may get reported are related to the MAPI32.dll being absent on the Backup Exec server or if present than an incorrect version may be available.
 

5. Attempt to resolve the error reported in the Dependency Walker, restart the Backup Exec services and then reattempt the backup.

Error message: "The redirector failed to determine the connection type"

http://support.microsoft.com/kb/315244

Often see the error on window xp.