Microsoft Outlook 2003: Configuring multiple accounts?

In Outlook (this is for Outlook XP, but 2003 is basically the same):

1. Choose Rules Wizard from the Tools menu.

2. Click on New. In the dialog that comes up, choose the "Start from a blank rule" option. "Check messages when they arrive" should be preselected.

3. Click Next. In this step, choose the option "with specific words in the recipient's address". Click on the underlined "specific words", type (e.g.) address1@mycompany.com, click Add and then OK.

4. Click Next. In this step ("What do you want to do with this
message"), select "move to specified folder". Click the underlined word "specified" and specify the folder.

5. Click Next. In this step, add any exceptions if desired.

6. Click Next. Name the rule and click Finish.

7. In the preceding dialog (still showing, click OK).

Or Three Accounts...

The other solution you can use if you don't want to use three folders but would rather be able to file email in a set of folders, with different sets per account, is to actually create three different accounts in Outlook.

Instead of creating 3 separate accounts you could try creating three separate profiles that will give you three separate data files;

First, get rid of two of the accounts from the Outlook profile you already have.

Then go to your Mail Settings, then START --> CONTROL PANEL --> MAIL

Select SHOW PROFILES, then ADD.

Follow through the instructions to set up a profile making sure you have the necessary info from your ISP or POP account ... (account names, passwords, addresses, etc.)

Then create further profiles for the remaining accounts, giving each profile a separate and distinguishing name.

Once you have your three profiles (each with a different email address) click the radio button next to "Prompt for a Profile to be Used". Then click OK.

When you start Outlook, it should ask you which profile to use. Choose the appropriate one and you're all set. That should also give you three data files.

4ever Photo Studio

YGN WEDDIN DINNER

Case Scenario

I already have a domain controller running fine but had added a second Windows 2003 server as a backup. I had initiated the promotion of this second server as a "new domain on an existing forest". but due to corrupt files and OS, I plan to rebuild. But before I do so, how do I gracefully demote this server so that I can rebuild the server with different host name and then join the domain.

My mistake:

That error of DNS loading before AD was event ID 4004 and 4015 events. This is caused because the DNS service started before AD upon boot, not installation.

http://www.experts-exchange.com/Networking/Protocols/DNS/Q_22901131.html

After promoting it, you may run into not being able to communicate between servers and replicate between them. If this happens, you might need to register your DNS address with Server B after promoting it. Then force replicate that Host A record to the other Server. What causes this is the servers don't have a Host A record registered in DNS. So, they don't communicate between eachother because DNS does not make the name translation. A DCdiag report on Server B after promoting it will be a dead give away on this problem. You should see something like DCgetDCname error within the DCdiag test. If you see this, stop netlogon, type ipconfig /register DNS, start netlogon then force replicate as shown below. Or you can type dcdiag /fix:DNS and replicate that DNS record to the Server A.

I think you are ready to promote this machine back into the domain and replicate the AD database
FROM server A TO server B.

After all is said and done, you should be able to communicate and replicate with two clean DCdiag reports.

How to force replicate:
http://www.windowsitpro.com/Articles/ArticleID/13396/13396.html?Ad=1plicate:

How to Demote Domain Controller ?

Check that it does not hold any FSMO roles (it probably dos'nt but best to check) http://www.petri.co.il/determining_fsmo_role_holders.htm

Should it have any FSMO roles transfer them - http://www.petri.co.il/transferring_fsmo_roles.htm

If it is hosting any services such as DHCP then you might want to move these and any data.

Try and demote it from being a DC gracefully by running DCPROMO

If DCPROMO fails - try DCPROMO /forceremoval

if DCPROMO /forceremoval does no work then just zap it.

Remove the computer from the domain and delete the computer account. If you were not able to remove the DC gracefully then cleanup AD and emove all traces of the old DC from Active Directory - http://www.petri.co.il/delete_failed_dcs_from_ad.htm

To re-install

(re)install Windows 2003 on the new machine

Assign the new computer an IP address and subnet mask on the existing network
Make sure that the preferred DNS server on new machine points to the existing DNS Server on the Domain (normally the existing domain controller)

Join the new machine to the existing domain as a member server

From the command line promote the new machine to a domain controller with the DCPROMO command from the command line Select "Additional Domain Controller in an existing Domain"

Once Active Directory is installed then to make the new machine a global catalog server, go to Administrative Tools, Active Directory Sites and Services, Expand ,Sites, Default first site and Servers. Right click on the new server and select properties and tick the "Global Catalog" checkbox. (Global catalog is essential for logon as it needs to be queried to establish Universal Group Membership)

Assuming that you were using Active Directory Integrated DNS on the first Domain Controller, DNS will have replicated to the new domain controller along with Active Directory.

If you are using DHCP you should spread this across the domain controllers, In a simple single domain this is easiest done by Setting up DHCP on the second Domain controller and using a scope on the same network that does not overlap with the existing scope on the other Domain Controller. Don t forget to set the default gateway (router) and DNS Servers. Talking of which all the clients (and the domain controllers themselves) need to have their Preferred DNS server set to one domain controller, and the Alternate DNS to the other, that way if one of the DNS Servers fails, the clients will automatically use the other,

Both Domain Controllers by this point will have Active Directory, Global Catalog, DNS and DHCP. and the domain could function for a while at least should any one of them fail. However for a fully robust system you need to be aware that the first domain controller that existed will by default hold what are called FSMO Roles. There are five of these roles that are held on a single server and are essential for the functioning of the network. If the second Domain Controller fails, then no problem as the FSMO roles are on the first Domain Controller. However if you intent to function with the second Domain Controller only, then the roles need to be moved to the Second Domain Controller. Ideally if this is a planned event you should cleanly transfer the FSMO roles, if it is an unplanned "emergency" the FSMO roles can be seized (see http://support.microsoft.com/kb/255504)

Determining FSMO Roles Holders

http://www.petri.co.il/determining_fsmo_role_holders.htm