Search results for query: *

An IBM blade server is just a form factor of the physical hardware, it doesn't encompass the software or operating system. You've got three typical types of server form factors: Tower Rack Blade Each is useful in different ways, but generally Blade servers are used when you need a lot of...

Hi guys, We've got a 3848 that we've misplaced the mounting kit for. 3Com and a bunch of their distributors can't source a mount kit for it as it's now discontinued. I'm wondering if the 4500/4200's are the same mount kit but different colour as they are probably much easier to find. Anyone...

There's some good documentation available on the Microsoft site now. For the Exchange Management Pack Guide for Operations Manager 2007 check out: http://download.microsoft.com/download/7/4/d/74deff5e-449f-4a6b-91dd-ffbc117869a2/OM2007_MP_ExSrvr2003.doc

It's now in Tools/Email Accounts. You need to define the Exchange Server account, and then change the Deliver New E-Mail to the Following Location to the Exchange Mailbox as opposed to the PST file. PST's are bad, m'kay... S.

Yeah, there's a patch from MS to trick the Exchange setup routine in to accepting the 2003 Admin Tools if you have them handy. XADM: You Receive an Error Message When You Try to Install Exchange System Manager on a Windows XP-Based Computer...

Nope you can't. Microsoft Consulting Services can, but you'd need to pay them money to come up with the DLL's or whatever they change. Only other thing you can do is fiddle round with SMTP EventSync's to trap outgoing NDR's and change them for an alternative email. Very difficult, don't fancy...

Don't put it on servers, put it on your workstation. Just run the Exchange 2000 setup from your CD, select a 'Custom install' and select to install only the Microsoft Exchange System Management Tools. Don't forget to service pack the install when you've finished!

XADM: How to Exclude a Single Mailbox, Multiple Mailboxes, or a Group When You Use Mailbox Manager http://support.microsoft.com/?kbid=288115

I had the same problem. Jump in to Active Directory Users and Computers MMC snapin and do a 'Find Objects In Active Directory' (book and magnifying glass icon). Pick the Exchange tab, and hit Show only Exchange recipients and Users with Exchange mailbox. Then do a Find Now. On that list should...

If you're running everything on Exchange 2000, you want to create some Routing Groups for your sites, and then join them together using either Routing Group Connectors (which actually use SMTP to talk) or SMTP Connectors. Routing Group Connectors are very simple to set up, and since you're all...

Ah, Exchange 2000 has a built in dynamic memory allocation system, which means it will pinch every bit of ram it can get it hands on, and as other processes require memory, will give it back to them. It's not unusual to see Store.exe using most of the servers memory, a 1Gb equipped server might...

Yes, the new one should be capable of taking over should the other fail, but you should make sure you have all the relevant services such as DNS and DHCP set up on it. Also you would need to delegate the 'operation masters' over to the new box...

Firstly, there is no such thing as a Win2000 PDC. PDC is a NT4 term, with Win2000 all domain controllers are considered equal. All you need to do is get the new server online, make sure you install all the services the old one has (such as DHCP, DNS), promote it to a Domain Controller and it...

Yeah definitely the biggest problem I've found with Multihomed servers is that two default gateways are specified. Only the one should be specified, the other left blank.

I'll add to ADSC's point on documentation by saying you probably should have a folder prepared for each machine, with all the documentation on its config, plus a copy of all the software installed on it. If things really kick off then the last thing you want is to have to search round for who...

Adminpak.msi is also in Service Pack 3. You might need to extract all the files to find it.

Yup! As above, but in the disk management console, you right click the volume set you wish to expand and choose Extend Volume from the short cut menu. This'll fire up the Extend Volume Wizard. There are a few catches though: - You can only extend NTFS volumes - You can't extend volumes that...

When they install the new Windows 2000 server, it won't be a BACKUP domain controller, it will be a domain controller, of equal status as the existing w2k domain controller. Windows 2000 Active Directory setups do away with the idea of primary and backup domain controllers that NT4 used to use...

It's a terminology programmers use to describe the first 16 bits and the last 16 bits of a 32 bit value. A 'word' is 16 bits (or two bytes) in size. Slap a High Word and a Low Word together (16 bits + 16 bits) and you get a 32 bit value which Windows reaaaaally likes since it's a 32 bit...

Yeah I would just try to delete it rather then build yourself a new server etc... Try deleting in the Domain Controllers section of the Active Directory Computers and Users MMC if its listed, or if not, use the adsiedit/ntdsutil to kill off the entry in the active directory...