Search results for query: *

You have to buy 2 copies of Exchange to do FE/BE and that would definately be overkill for 50 users. As for popping IIS on the Exchange server, you are stuck with that no matter what. Exchange 2000 requires the installation of IIS. You can restrict access, but you cannot have Exchange 2000...

Yes, two licenses are required. If you only have 2 Exchange servers in your entire Exchange infrastructure, I'd advise against FE/BE structure. In the FE/BE, no mailboxes actually reside on the FE server and it is just used to access BE servers, usually through a firewall. This means if the FE...

Had this one not so long ago and found the answer at www.eventid.net Source MSExchangeES Type Error Description An unexpected MAPI error occurred. Error returned was [<error code>]. ---------------- Error: 0x80004005 = &quot;Unspecified error&quot; - This error may occur if you starting...

The most obvious advantage to moving to Exchange 2000 (or 2003) is it's integration with Windows Active Directory. Exchange no longer has to store it's own directory information, as that is maintained on the AD controllers and in the global catalog. This allows all directory information to be...

Have you tried putting in the server name when you configure outlook, rather than letting it look up the server name automatically? If it is just one or two users, you might consider using exmerge to drop their mailbox to a PST, and then push the PST up to the new mailbox on the E2K box. Once...

As this is the sole AD/Exchange server, I'd probably cut my losses, restore from the backup, and use this as an excuse to get a second server. You use the second box as an extra DC for AD and Exchange server. Gives you a place to queue mail till you bring your &quot;downed&quot; system back...

ONLY TRUE FOR INITIAL PURCHASE OF A DATABASE AGENT! If you are upgrading from 8.5 or 8.6 database agent (Exchange or SQL) to 9.0 agent, it does not come with remote agent.

If this is an Exchange server, and you are doing a brick-level backup, this may be your problem. Most backup vendors use the MAPI client to perform a brick-level backup, and it usually drops the performance significantly.

Additional warning for Exchange administrators. Any systems which were upgraded from Exchange 5.5 to Exchange 2000 may experience backup failures. Further information to be found at: http://seer.support.veritas.com/docs/255233.htm No fix noted yet.

If you purchase BE9 database agents, they come with a remote agent included. The idea being that you will be backing up an Exchange or SQL database on different server than your backup server. I was told by a veritas rep, that if you purchase an agent upgrade, Exchange agent 8.5 to Exchange...

Need a little bit more information on the problem than &quot;the whole network went down&quot;. What precisely went down? Servers, desktops, a hub/switch? Sounds to me like a network/bandwidth issue rather than a &quot;veritas&quot; issue.

The remote agent service runs on the remote server with the LOCAL SYSTEM account if not installed at the same time as BE. I changed the Remote Agent Service logon account to the same account the rest of my backup services run under, and it worked fine. Backup account must have rights for the...