Search results for query: *

adding to the above... Cov 'y' or 'n' is not an offering in our vector. Could be that we have an older version of the code.

Yes it does have a coverage path.

where would I check to set the coverage? There is nothing in the vector itself for that. We are using a VDN to access the split.

stated as follows: route to number 555 if unconditionally

In the System-parameter features, Trunk-to-Trunk transfer is set to yes. Looking at all COS, “Restrict-Call-Forward-Off-Net” is set to N (No) for all except COS 2. My Voicemail system is tied to port 585, which has a COS set to 1 (and a COR set to 1). I do not see where COS would be...

We have an Avaya Definity System 75 (G3i v1.1-286), software system level is g3v2g.07.0.0.106. Our voicemail system is a Digital Speech and uses a voice bridge with 16 analog lines to access it. Last June we had a full system crash and had to restore from tape to a configuration dated 2001...

When we set up the BE Agent for Exchange 2003 we installed it as the Exchange service account. We did not run into an access problem then.

It can be done with Crystal 9.0

At one point during our growing pains, we had a problem with the Exchange server in that we had to rebuild server with operating system and Exchange 2003. We contacted Microsoft and their suggestion was to copy the .edb files and save them. Rebuild with the exact same OS and Exchange version...

I found no other way than multiple Internet email accounts and the drop down on the send button. Asking users to change profiles just to send mail is way too much of a hassle

I think what he is saying there is to set up a new profile with a different mailbox. Then when you log into Outlook you choose the profile you would like to use, log into that mailbox and send the emails you would need. This is a pain in the butt.

I just recently went through this and after a load of research, this seems to be a feature of Outlook in Corporate mode. The only way I could get it to work was to set everyone up using Internet Email and then when they wanted to send using a different domain, they used the drop down list to...

Ok. We currently run a corporate network of similar size to yours. All of our users have a mailbox on Exchange Server 2003. We configure their Outlook 2000/2002/2003 in Corporate mode to connect directly to the Exchange server. No need for PST files. We back up the Exchange server...

It is Outlook that controls the location of PST files. Whether they are local or stored on a Network Share. Network Share is our preferred method as they will be backed up as part of our backup strategy. A question for you. When you move to Exchange, what requirement do you see for PST's...

Yes, we have removed the Active Directory connector from the Exchange server.

Under the AD Users and Computers MMC/Microsoft Exchange System Objects we have 4 SystemMailbox objects that are disabled. I have noticed that one of the objects is causing an Event ID 1022 to occur at for about 30 seconds that causes about 200 error events to be generated. We have recently...

In March of this year we upgraded from Exchange 5.5 to 2000 then to 2003. We finally had everything up on 2003 by May. Since then we have found that every Monday morning a popup will occur for certain users asking if they want to keep client or server side rules. We have them choose Client...

This was quite a prevalent issue with clients on Outlook 2002 prior to our upgrade from Exchange 5.5 to 2003. We did pin it down to VAPI/MAPI in our case with Norton Antivirus Corporate Edition. The Outlook client will request data from the server to ensure an attachment is virus free. Once...

You cannot do this. The Exchange 5.5 mailboxes have to be migrated. Go to Microsoft Support website and there are many articles on the migration path from 5.5 to 2003. A good article is 327928 which compares migration methods.

From Memory.... If your information store shut down gracefully then your logs should be committed. You can take a copy of your pub.edb and priv.edb and put them in a safe place. Perform an exchange server rebuild using the /disasterrecovery switch and then turn off the services. Drop the pub...