Can you describe the difference between a user and a contact in Microsoft Exchange 2000 Server?
This question is interesting because in Exchange Server 5.5, accounts and contacts are two completely different entities that Exchange stores in different places. The biggest difference is simple yet subtle: Users are security principals, and contacts aren't. In Windows 2000 parlance, a security principal is any object that has security credentials that someone can use to log on to a resource. A user object has such credentials, but a contact doesn't. In particular, user objects have four attributes that contacts don't: objectSID, SAMAccountName, userAccountControl, and userPrincipalName.
Now, let's talk about users' and contacts' similarities. Both can exist in a mail-enabled configuration. Mail-enabled objects have email addresses associated with them. The mere presence of an address doesn't do much for an object because an address is just a directory attribute. However, mail-enabled user objects might also be mailbox-enabled, which means that an associated mailbox is attached to the user. Contacts are a little different because they never have associated mailboxes; instead, you can give them target addresses, which are just external addresses.
Is a procedure available for moving Exchange Server databases from an Alpha server to an Intel server?
Fortunately, yes—otherwise, all the companies that spent big bucks on hot Alpha hardware would have no migration path to the x86 world. You can move the files without any special conversion, but you're subject to all the constraints you have when moving Exchange databases from one machine to another. You can perform a complete disaster recovery from the Alpha box to the x86 server, or you can take partial steps, such as moving mailboxes and public folders instead of moving all the data.
I want to run a virus scanner on my Exchange Server machine. Do I need to take any special precautions?
If you're going to run a virus scanner on your Exchange server, make absolutely sure that you don't scan the directories that contain your transaction logs or databases. Virus scanners generally disinfect or remove any suspicious files they encounter. If your scanner decides to disinfect or remove a transaction log or checkpoint file, you'll be very unhappy when you try to back up or recover your server because the data in those files will no longer match what the checksum files have recorded. If you're trying to protect mail data, not just the server's files, you need an Exchange-aware scanner. If you're considering migrating to Exchange 2000 Server, make sure the product you choose is, or will be, Exchange 2000compatible.
I installed the Windows 2000 Administrative Tools package on my workstation. Why can't I see the Exchange Tasks item or the Exchange-specific properties for user objects?
The adminpak.msi file included with Win2K Server and Win2K Advanced Server installs all the Microsoft Management Console (MMC) snap-ins (e.g., Active Directory Users and Computers, Sites and Services, DNS) on a Win2K Professional machine. This tool is handy because it lets you administer your servers without logging on to their consoles. Unfortunately, the tool also produces the problem you've identified.
Prev. page
[1]
2
3
next page 
