Search results for query: *

Our server is server 2000, it also has Exchange Server 2000 and all the mailboxes. I am not talking Disaster Recovery that would go to the identical nmachne, but if my server physically burned - and all I had was the tapes, a new machine -- server 2000 and Veritas 9.0 to install -- how much...

HP Omnibook 900 a formerly win98 PC trying to install win2k on it -- gets to the stage "installing Devices...screen may flicker momentarily..." well - half-way thru the bar on that -- the screen goes BLANK and just never comes back hard drive keeps working away - I can even see...

wit's end -- all I can do is take off Open File Option altogether off the Job parameters and then it will run I have recently installed OFO on some machines and could not reboot them immediately after the remote agent/OFO install to those PC"s but like I thot "use OFO 'IF...

This is different, but similar to, messages I have seen related to Microsoft KB article Q189692 -- but it is different so anyone who has experience above and beyond that old office 97 problem with powerpoint orgchart please H_E_L_P !!! I have all win2k pc's -- NONE had either win2k or...

I am considering doing this -- as opposed to a clean install of win 2000 Pro after fdisk and formatting -- does anyone have any experience (or "horror stories") of how the "install win 2000 on top of MIllennium" has in fact worked?

I gotta find some rhyme or reason why a backup job ends in a failed status -- all I can tell is -- that from time to time-- an .mmp file on the exchsrvr/WebTemp folder on the 5.5 exchange server machine is denied access to at time of backup of the HARD DRIVES THEMSELVES of this NT 4.0 (sp6)...

Is creating this BEDIAGS.FAX file of any use in tracking down Backup Exec Service Account usernames/passwords??

wits end again Re-installing OPtion for OFO on a handful of machines that have remote agent on 'em OFO Option goes OK on all but one -- screens requiring an admin name and password have come up for each machine -- I use the same one -- but this one big File Server (not the one the tape drive...

Exchange 5.5 sp3 running on NT 4.0 sp6 -- we are using Veritas backup Exec 8.6 & this might be related to its OPEN FILE OPTION -- INTERMITTENTLY this "Otman4" stuff kills the Exchange server during the night I come in and Email is down until the exchange 5.5 server is rebooted...

Exchange 5.5 running on NT 4.0 sp6 -- we are using Veritas backup Exec 8.6 & this might be related to its OPEN FILE OPTION -- INTERMITTENTLY this "Otman4" stuff kills the Exchange server during the night I come in and Email is down until the exchange server is rebooted same...

some unused directories in Program Files /Backup Exec / NT ??? bent.old = a folder I think was formed when I upgraded from 8.5 to 8.6 under AGENTS -- the folders for MAC, UNIX and Win95 The C: drive of the NT 4.0 Server that BE 8.6 resides on needs every bit of hard drive real estate it...

to have users "access email from the web". Whatever IIS functions were exploited by Nimda also allowed that very useful feature of checking corporate email through a web address. Anyone know how to remain protected from Nimda and still turn that feature back on?

We have BE 8.6 on one NT 4.0 Server and it backs up that one and 2 other NT 4.0 Servers on the domain. Now the Disaster Recovery Diskettes have "hardware-specific" machine info on them -- so using them for that kind of Restore would mean you "had the same boxes; just corrupt...

after downloading a 130 meg self-extracting executable & trying to upgrade -- the setup process shows the existing serial numbers -- how convenient!! Only when I try to enter the one for the main product; it says "serial number already in use". Official Veritas Tech Support emailed me...