It works well for us. Just keep up to date on patches and drivers. Also, check out article 31103 from the technical document index (http://esupport.ca.com/premium/antivirus/infodocs/nt/31103.asp). That issue can cause some problems.
Joe
Not sure, but it could have something to do with the OL2002 blocking attachments issue mentioned in this KB article:
http://support.microsoft.com/default.aspx?scid=kb;en-us;290497
Joe
The thread mentioned in by Strator (thread616-437790) worked for me and is well marked with stars, so it must have worked for others. Did you give it a try?
There are a couple of threads on this. Try uninstalling hotfixes Q329170 and Q328310. You might want to search the forum using these for more complete answers.
We have XP boxes on our NT server working just fine. Printers were the biggest problem, but used this KB article to clean those problems up:
http://support.microsoft.com/default.aspx?scid=kb;en-us;314073
Joe
>>Trying to stop the Information Store process- after 17 minutes, the system couldn't shut it down.
I had a similar problem, but with 5.5, maybe it will help. Turned out the fix was 2 parts: 1) had to pay MS for a hotfix to Ex 5.5 for documented but unavailable patch to store; and 2) a...
We use CA Inoculateit, but I think the processes monitored would be the same:
EMSDATA.EXE
ESEUTIL.EXE
EXMGMT.EXE
MSACHECK.EXE
STORE.EXE
ISINTEG.EXE
MSACHECK.EXE
MTACHECK.EXE
SRSMAIN.EXE
I got this list from a KB article, but can't find it. I did find these 2 that also address this problem...
There are a few threads on this is various forums. Search around or check this KB article out and see if it helps:
http://support.microsoft.com/default.aspx?scid=kb;en-us;290497
Joe
Hi euston,
Sounds like you in a heap o'trouble. Acknowledging that this has nothing to do with computers, to answer your last question for an explanation of the term "craw" go to:
http://phrases.shu.ac.uk/bulletin_board/11/messages/738.html
In case you were really talking about...
Junk sender list is stored in c:\Documents and Settings\username.domainname\Application Data\Microsoft\Outlook as Junk Senders.txt. I process the list through Excel to strip off what I dont want and generate a text file (there are easier ways I'm sure), then import it to Exchange using Regedt32...
Don't know how "right" this is, I know it isn't elegant, but I had a similar problem. Resolved it by installing printers under the admin account. Then users were able to add the network printers to their own profiles.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.