RE: Exchange 5.5 SP4 Patch KB829418 - STORE.EXE GPF

2003-11-18 Thread David, Andy
Does the dev server have McAfee installed on it as well? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 18, 2003 9:22 AM To: Exchange Discussions Subject: Exchange 5.5 SP4 Patch KB829418 - STORE.EXE GPF I have applied recent MS Patch

RE: Exchange 5.5 SP4 Patch KB829418 - STORE.EXE GPF

2003-11-18 Thread Dave Parker
Yes, identical version of McAfee GroupShield. Only difference seems to be loading - dev server has very little traffic - production is busy. Thanks Dave Does the dev server have McAfee installed on it as well? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]

Re: Exchange 5.5 SP4 update to OWA box wont install :(

2003-09-15 Thread Tony Hlabse
Kinda sounds like a service is not shutting down properly. Try manually shutting down all services for Exchange then try. From: Jose Manzano [EMAIL PROTECTED] Reply-To: Exchange Discussions [EMAIL PROTECTED] To: Exchange Discussions [EMAIL PROTECTED] Subject: Exchange 5.5 SP4 update to OWA box

RE: Exchange 5.5 SP4 update to OWA box wont install :(

2003-09-15 Thread Jose Manzano
I tried manually stopping the IIS services but, it didn't help. Outlook Web Access is the only exchange app installed on this box :( -Original Message- From: Tony Hlabse [mailto:[EMAIL PROTECTED] Sent: Monday, September 15, 2003 7:22 PM To: Exchange Discussions Subject: Re: Exchange 5.5

RE: Exchange 5.5 SP4 update to OWA box wont install :(

2003-09-15 Thread Tony Hlabse
Not sure maybe shutdown any antivirus programs running From: Jose Manzano [EMAIL PROTECTED] Reply-To: Exchange Discussions [EMAIL PROTECTED] To: Exchange Discussions [EMAIL PROTECTED] Subject: RE: Exchange 5.5 SP4 update to OWA box wont install :( Date: Mon, 15 Sep 2003 19:44:37 -0400 I tried

RE: Exchange 5.5 SP4 DIR.EDB troubles

2002-08-27 Thread Tim Ault
You've introduced an add'l Site into the Org, am I correct? It takes a bit of time for a cross-site replication of directories to complete. Sometimes they never do. Shame you went right for KCC and essential as prospective remedies. A no-cost and much more prudent t-shooting step would have

RE: Exchange 5.5 (sp4) to E2K upgrade

2002-07-17 Thread William Lefkovics
With only 12 users, you really have lots of options, I think. Even exporting the clients mailboxes to .pst (and using Outlook to export the public folders to .pst) and doing a clean installation instead of an upgrade. But, more formally:

RE: Exchange 5.5 (sp4) to E2K upgrade

2002-07-17 Thread Ken Cornetet
I think this is the general route I'd take... 1. Buy new server 2. Install NT4 as a BDC of your current domain 3. Promote new server to PDC (which will simultaneously demote the old PDC). 4. Install win2k server on new server, converting domain to mixed mode AD 5. Install ADC, do forestprep and

RE: Exchange 5.5 (sp4) to E2K upgrade

2002-07-17 Thread Chris Scharff
Subject: RE: Exchange 5.5 (sp4) to E2K upgrade With only 12 users, you really have lots of options, I think. Even exporting the clients mailboxes to .pst (and using Outlook to export the public folders to .pst) and doing a clean installation instead of an upgrade. But, more formally: http

RE: Exchange 5.5 SP4

2002-02-13 Thread Huot, Denyse
. Thanks for your response Ed. Denyse -Original Message- From: Ed Crowley [mailto:[EMAIL PROTECTED]] Sent: Tuesday, February 12, 2002 5:20 PM To: Exchange Discussions Subject: RE: Exchange 5.5 SP4 That message might be bad. Can you find the message in the IMCDATA\IN directory? Try

RE: Exchange 5.5 SP4

2002-02-12 Thread Ed Crowley
That message might be bad. Can you find the message in the IMCDATA\IN directory? Try moving it to another directory if so. Ed Crowley MCSE+Internet MVP kcCC+I Tech Consultant Compaq Computer Corporation Protecting the world from PSTs and Bricked Backups! -Original Message- From:

RE: Exchange 5.5 sp4 Windows NT sp6 BDC ---- migrate W2k Server DC?

2002-01-17 Thread Ed Crowley
My advice to you would be to find some additional equipment and use the leapfrog method of upgrading. The Exchange part is explained in the FAQ Appendix A. Ed Crowley MCSE+I MVP Tech Consultant Compaq Computer There are seldom good technological solutions to behavioral problems. -Original

RE: Exchange 5.5 sp4 Windows NT sp6 BDC ---- migrate W2k Server D C?

2002-01-10 Thread Chris Scharff
You only need to change the LDAP port of Exchange servers running on a DC. The servers don't talk to each other via LDAP, so they don't care what port any other server is listening on.. Or if it is listening at all. Chris -- Chris Scharff Senior Sales Engineer MessageOne If you can't measure,

RE: Exchange 5.5 sp4 Windows NT sp6 BDC ---- migrate W2k Server DC?

2002-01-10 Thread Ed Crowley
I want to tell you, Yes it will work. But I can't say that because all the detail you've provided about your strategy is the word migrate. Ed Crowley MCSE+I MVP Tech Consultant Compaq Computer There are seldom good technological solutions to behavioral problems. -Original Message-

RE: Exchange 5.5 SP4 and W2K SP2

2002-01-08 Thread Soysal, Serdar
Gah! No need to check the archives! Just today there were 10 messages in a different thread that discussed this. For your convenience the thread's subject line was: Exchange 5.5 on NT4 and W2K?! You can probably find them in your Deleted Items. S. -Original Message- From: Huot,

RE: Exchange 5.5 SP4

2002-01-07 Thread Lefkovics, William
You might consider just installing the Exchange admin on the remote workstation. Or perhaps ADSI can return the data required. William Lefkovics -Original Message- From: Huot, Denyse [mailto:[EMAIL PROTECTED]] Sent: Monday, January 07, 2002 8:48 AM To: Exchange Discussions Subject:

RE: Exchange 5.5 SP4

2002-01-07 Thread Chris Scharff
I believe Sherpa Software has a tool which will do this. http://www.sherpasoftware.com/ Chris -- Chris Scharff Senior Sales Engineer MessageOne If you can't measure, you can't manage! -Original Message- From: Huot, Denyse [mailto:[EMAIL PROTECTED]] Sent: Monday, January 07, 2002

RE: Exchange 5.5 sp4 Locks up

2001-12-14 Thread Hunter, Lori
You installed CA This was your first mistake there Now go uninstall. -Original Message- From: smugg [mailto:[EMAIL PROTECTED]] Sent: Thursday, December 13, 2001 4:00 PM To: Exchange Discussions Subject: Exchange 5.5 sp4 Locks up I recently moved my mailsite to an NT4 sp6a Server with

RE: Exchange 5.5 sp4 Locks up

2001-12-13 Thread Drewski
Uninstall any CA products at all. What does it give you that you can't get by loading the Exchange Admin app on your workstation? -- Drew Visit http://www.drewncapris.net! Go! Go there now! It is far more impressive when others discover your good qualities

Re: Exchange 5.5 sp4 Locks up

2001-12-13 Thread Phil Labonte
I had the same problem and setup. With mine I had to set the Scan attachments in store in the background or the server would freeze up. Once that was set everything has been running smoothly. Give that a try. - Original Message - From: smugg [EMAIL PROTECTED] To: Exchange Discussions

RE: Exchange 5.5 sp4

2001-09-25 Thread Herrick, Michael
Harriet - Upgraded to Sp4, applied all subsequent hotfixes and the Security Rollup Patch on many servers. Took exactly 1 hour on servers with approx 25GB priv.edb. If you have teamed NICs on Compaq servers, be sure to break the teaming before applying the Security Rollup Patch and then re-team

Re: Exchange 5.5 SP4, Event ID:3038 -IMC Warning in Event Log

2001-09-13 Thread Daniel Chenault
Disable your AV and contact the AV company. - Original Message - From: RSangha [EMAIL PROTECTED] To: Exchange Discussions [EMAIL PROTECTED] Sent: Thursday, September 13, 2001 5:34 PM Subject: Exchange 5.5 SP4, Event ID:3038 -IMC Warning in Event Log Here's the entire error message:

RE: Exchange 5.5 sp4

2001-09-10 Thread Peña, Botp
in my case 1. 30 mins is the average. Sp4 is fastest to install (fr my experience). 2. apply first on a test lab/server. then restore to previous state. simulate update and restore. 3. remember: backup before applying on prodn. 4. in case..., restore as mentioned by ms's whitepaper. I've always