Recent content by obriensl

This problem is fixed in the 7.1.3 release which you can download from the legato site

With Exchange 2003, you can use the Recovery Storage Group setup to recover the database where the user's mailbox resides, then use Exmerge to pull out the user's messages. Info on the recovery storage group feature is on the MS Exchange sites.

Hi all, well, Legato never told me what exactly they changed between the versions, but provided me with a new liblocal.dll that seems to work for me. If you want to try it-here are the instructions I got. I loaded the new dll on the clients that were having the problem. Please visit the...

Hello all, I also have this same issue on a few of my clients after updating to 7.1.2 release. I was able to back them up just fine on 7.1.1, and when I uninstalled 7.1.2 and reinstalled 7.1.1, again worked fine. I only have the issue on a few clients, and not on all of the directories. I have...

Hi all, we have brought up an additional Networker server in our environment. now we want to migrate 1 client that is also a storagenode and it's associated jukebox from server a to server b. I can't seem to find any instructions for migrating the current information about the client backups...

Has anyone ever see this before? I have not been able to get much info from MS KB, etc. My log is getting flooded with these since this am. Event Type: Error Event Source: MSExchangeIS Event Category: Content Engine Event ID: 12002 Date: 7/11/2003 Time: 10:43:53 AM User: N/A Computer...

Amen to that....but my hands are tied, since higher up is saying find a solution :)

Hi all, I need some help/suggestions. We have our Exchange 2000 environment set up right now to allow out of office replys to the internet. We want to disable this option, however, we have a group of users who say they can't do business without it. They do not want to use a functional mailbox...

are you having this problem with the physical nodes or the virtual nodes? We had an issue with the virtual node index info being written to the physical node index file. Legato had us put an empty file called "pathownerignore" into the nsr/bin directory on each one of our physical nodes.

We updated both of our Exchange 2000 servers to SP3 while still on Windows SP2 without any errors. One was standalone and one is clustered. We upgraded to Windows 2000 SP3 about a month later, also with no problems

I took the test when it first came out, so not sure if it changed. I had about 34 questions, alot of multiple choice, either single answer or choose all that apply. There were also a few drag and drop diagram type questions.

I took it a few months ago. I didn't find any practice questions..my only tip is really know the DOS commands inside and out. There is a section on SAN/Storage Node/Cluster setups too.

Just curious, why do you say that Win2K SP3 needs to go on first? From everything I have read, they are independant. We upgraded to Exchange SP3 without doing Win2K.

did you edit the client to use the storage node? You need to put the storage node name before the NSRSERVERHOST entry in the Storage Node definition of the client preferences

For your question 1, I'm assuming you mean that you want to check in the document that they edited. (If you don't have the edited document, just cancel their checkout as listed previously) There is no way I know of to check in a document that is checked out to someone else, even if you are the...