Search results for query: *

Actually, I'd recommend yet a third option. Dig up a PC somewhere - doesn't have to be much, just about a 500MHz with a couple gig of hard drive space. Load NT Server on it, set it up as a BDC in that domain. Promote it to PDC. Run the 2003 Server upgrade on it, and then dcpromo. After...

I've seen this happen a few times. It always panics our users, because I work for a school district, and we've had...um..."incidents" with the kids hacking when not properly supervised. We're heavily firewalled to the outside world, so these kinds of things nearly always come from...

Can the PDC ping the BDC by name? If so, what IP address does it return? Check WINS, and make sure there are no static or tombstoned entries for the BDC with the old address attached.

It's been almost seven years since I used 3.51, so forgive me if this is in error, but something in the hazy depths of my brain tells me that you CAN'T do a promote/demote between 3.51 and 4.0...is there any possibility of upgrading the 3.51 box? Your promotion should work then.

If you want to remove ALL the agents, you can do that by removing them from the directory and selecting the checkbox to "uninstall agent from all connected computers."

Check and see if you're getting later messages that online defrag completed successfully...if so, it was a transient error.

That's what you do in SBS, also - run setup and select the Remove option.

Whoops, sorry, missed that you had the open file agent installed. It sounds like you need to properly configure the open file option.

They're in use. When you do an online backup, the information store, MTA, etc., are running and thus in use. If you want to back them up, you either need to do an offline backup (not recommended, as it's harder to restore and usually less up-to-date), or use a backup product that permits...

It'll replicate *site* information, such as directory, server names, etc., and public folders can have replicas, but neither the single-site multiserver model, nor the multisite model will allow you to replicate mailboxes. The single-site multiserver allows you to load-balance by putting things...

Is your mailbox on that server, or one of your prior servers? If it's on another server, then you're having the same problem I am - not being able to get OWA to work unless it's on the same server as the users' mailboxes. It's irritating the hell out of me, because I've got the permissions and...

No such luck. They're not in Lost and Found, and the account(s) used to push (as well as the accounts used for the manual installs) had domain administrator rights. The agents are there. The server just refuses to "see" them. It's very frustrating.

Background: I have two Exch. 5.5SP4 servers, one running on NT4SP6a, one running on W2KSP3. Each is running OWA. Our users are in multiple NT domains (we aren't Active Directory yet). Abruptly, for no reason I could determine, OWA stopped authenticating each other's users; in other words...

There's a few things that can cause that. There's a couple of Q articles that reference slow information store performance; take a look at Q183924 and Q216076 and see if either of them help with that. The server may simply be processing more threads than it can handle, too. I have one server...

I finally found a solution to a problem that's been annoying me with ArcServe2000 for some time; phantom jobs remaining in "run" status after a server crash. The jobs can't be deleted, can't be stopped, and aren't really there. Stopping processes and engines does nothing to remove...

I've manually deployed the ePO agent on a number of machines, because my "push" deployment did not work (ePO Server 3.0 to W2K machines). There's no indication in the Server Events as to why it didn't work, and the account used has local administrator permissions on all machines in...

I'm having the same problem on a Compaq SDLT that was donated to us. Free hardware sometimes isn't worth the money you pay for it! But if anyone ever figures out a fix for this, I'd sure like to see it too. My symptoms are exactly the same as he's logged above - the media is unrecognizable...

I had precisely this problem on one of my servers, and tore my hair out for weeks before I got it to work. What I finally ended up doing was completely removing the ArcServe software - a complete uninstall and then a manual removal of all ArcServe directories - and then completely reinstalled...