If you are doing a fresh install of Exchange 2003 server and using the outlook 2003 OWA “Outlook Web Access” and you get a gray box in the new email message box you will need to apply a Microsoft update to fix this problem.
You can download the update from
http://www.pineway.co.uk/downloads/Exchange2003-KB911829-v3-x86-ENU.exe
Today has seen the release of my first web blog; I will be posting any developments to my skills, completed projects and upcoming events under this section.
Small Business Server 2008 (Disable Password Complexity Requirements)
You will notice that the option to disable the Password Complexity Requirements feature is greyed out, which prevents you from disabling the Complexity Requirements when using the Local Security Console.
Solution
1. Open Active Directory Users & Computers
1.1 From the menu select View and select Advanced.
2. Right click on the Active Directory Domain Name Root folder and select properties
3. Attribute Editor and locate the attribute “PWDPROPERTIES” the default value for enable is 1.
4. Change the Value from 1 to 2 and this will disable the Password Complexity Requirements feature.
Hope this helps
|
Exchange POP3 E-Mail Fetch
Sometimes you may wish to setup exchange in such a way that you use an external provider to host your email as pop3 and then you have your local exchange server download the pop3 email from the provider to the local exchange server. one of the common reasons for doing this is if your internet provider does not provide you with a static ip address and therefore cant have the email routed via SMTP directly. I have found a good solution for this and its a programmed called PopGrabber they do a free product which supports 3 pop3 email accounts or a paid version which offers more features etc. PopGrabber Free Version: http://www.pineway.co.uk/downloads/SetupPopGrabberFree109.exe
|
||||
|
|
||||
Exchange 2003 SP2 Install Fails because of MSXML
While building a new Exchange 2003 server I was installing Service Pack 2 and came across an interesting issue:
Setup failed while installing sub-component Exchange ActiveSync with error code 0xC0070643 (please consult the installatoin logs for a detailed description). You may cancel the installation or try the failed setup again.
Digging into the installation logs I see it’s trying to install MSXML:
[18:52:22] Calling MSXML installer with command line: “msiexec /i msxml3.msi /q reboot=”ReallySuppress”"
[18:52:22] Process created … waiting (-1)
[18:52:23] Process has exited with 0×000643
[18:52:23] The command
msiexec /i msxml3.msi /q reboot=”ReallySuppress”
failed, returning error code 1603 (Fatal error during installation.). — ID:31136 — ScCreateProcess (f:\tisp2\admin\src\libs\exsetup\hiddenw1.cxx:1821)
Error code 0XC0070643 (1603): Fatal error during installation.
The event logs subsequently tell me:
Event Type: Error
Event Source: MsiInstaller
Event ID: 1013
Description:
Product: Microsoft XML Parser — Your system has newer version of MSXML3 SP5 than the version you are attempting to install. Setup will quit.
Well, duh! I have MSXML3 SP7 installed. It appears that someone didn’t quite figure out that yes in fact new versions of dependent component do in fact come out and that it’s nothing to error out over. I wish all the product groups would expose a service like the MSDN Product Feedback center. I can’t be bothered to open up a PSS case just to report this. So here’s my workaround for anyone else that comes across this:
1. Get a copy of the Windows Installer package for the version of MSXML 3 you have installed.
2. Place a copy inside Exchsrvr\bin
3. Rename the existing msxml3.msi to msxml3.msi.backup
4. Make a copy of the latest version MSXML Windows Installer file and rename it to msxml3.msi. This will leave you with msxml3.msi and msxml3sp?.msi (in my case msxml3sp7.msi).
5.Click Retry on the error and it should continue as planned.
