Wednesday, September 28, 2011

Recall or replace a message after it is sent


This feature requires you to use a Microsoft Exchange Server 2000, Exchange Server 2003, or Exchange Server 2007 account. Most home and personal accounts do not use Microsoft Exchange. For more information about Microsoft Exchange accounts and how to determine which version of Exchange your account connects to, see the links in the See Also section.
The recipient of the e-mail message that you want to recall must also be using an Exchange account. You cannot recall a message sent, for example, to someone's personal Internet service provider (ISP) POP3 e-mail account.
E-mail is a fast way to communicate with your co-workers, schedule meetings, and share documents. However, sometimes you might forget to attach a file or send certain information, only to realize after clicking Send that you need to make a change.

Recall and replace a message

You send an e-mail message, asking your co-workers to review the sales figures for this year, but you forget to attach the sales figures. After you send the message, your Inbox is flooded with messages that ask "What attachment?", "I didn't get the attachment!", or "Can you resend the attachment?"
How can you undo your error? You can recall the original message and then resend it with the missing attachment. For all of your co-workers who haven't opened the message yet, you can perform an e-mail sleight of hand and replace the original message with another one that contains the attachment.

RECALL AND REPLACE A MESSAGE

Do the following:
  1. In Mail, in the Navigation Pane, click Sent Items.
  2. Open the message that you want to recall and replace.
  3. On the Message tab, in the Actions group, click Other Actions, and then click Recall This Message.
Actions tab
  1. Click Delete unread copies and replace with a new message.
 NOTE   If you are sending the message to a large number of people, you may want to clear the Tell me if recall succeeds or fails for each recipient check box.
  1. Click OK, and then type a new message and include the attachment.
  2. Click Send.
In another scenario, you accidentally send a message announcing a party for your staff that afternoon. However, the party is actually scheduled for the next week. In this case, you want to recall the message but not replace the message at this time.

RECALL A MESSAGE

Do the following:
  1. In Mail, in the Navigation Pane, click Sent Items.
  2. Open the message that you want to recall.
  3. On the Message tab, in the Actions group, click Other Actions, and then click Recall This Message.
Actions tab
  1. Click Delete unread copies of this message.
 NOTE   If you are sending the message to a large number of people, you may want to clear the Tell me if recall succeeds or fails for each recipient check box.
Recall This Message dialog box
Callout 1 Select whether you want to only delete the message or delete and replace the message.
Callout 2 Select the check box to receive a confirmation that the recall was successful.

Will my recall be successful?

The success or failure of a recall depends on the recipients' settings in Microsoft Outlook. The following four scenarios explain what happens in various situations, and an additional scenario describes the recall of a message sent to a Microsoft Exchange public folder.
ACTIONRESULT
You send an e-mail message to someone. You recall the original message and replace it with a new one.
On the recipient's computer, underTracking Options, the Process requests and responses on arrival check box is selected.
(To view this setting, on the Toolsmenu, click Options, click E-mail Options, and then click Tracking Options.)
Both the original message and the recall message are received in the recipient's Inbox.
Assuming the original message has not been read, the original message is deleted and the recipient is informed that you, the sender, deleted the message from his or her mailbox.
 NOTE   If the original message is marked as read (viewing in the Reading Pane is not reading in this scenario) when the recall message is processed, the recipient is informed that you, the sender, want to delete the message, but the message remains in the recipient's Outlook folder.
You send an e-mail message to someone. You recall the original message and replace it with a new one.
On the recipient's computer, underTracking Options, the Process requests and responses on arrival check box is not selected.
(To view this setting, on the Toolsmenu, click Options, click E-mail Options, and then click Tracking Options.)
Both the original message and the recall message are received in the recipient's Inbox.
On the recipient's computer, one of the following occurs:
  • If the recipient opens the recall message first, the original message is deleted, and the recipient is informed that you, the sender, have deleted the message from their mailbox.
  • If the recipient opens the original message first, the recall fails, and both the original and recall messages are available.
 NOTE   If the original message is marked as read (viewing in the Reading Pane is not reading in this scenario) when the recall message is processed, the recipient is informed that you, the sender, want to delete the message, but the message remains in the recipient's Outlook folder.
You send an e-mail message to someone. You recall the original message and replace it with a new one.
On the recipient's computer, either by rule or by action of the recipient, the original message is moved to another folder and the recall message remains in the Inbox (or it is moved to another folder as well).
As long as the recall message and the original message exist in separate folders, the recipient receives a message indicating that a recall attempt failed. This occurs regardless of the Outlook configurations and the read status of the message.
The original message and the new message are both available to the recipient.
 NOTE   If the recipient read the original message and then marks it as unread, Outlook treats it as if it had never been read and recalls it successfully.
You send an e-mail message to someone. You recall the original message and replace it with a new one.
On the recipient's computer, either by rule or by action of the recipient, both messages are moved to the same folder. This results in behavior similar to that which occurs when Outlook is not configured to automatically process messages.
On the recipient's computer, one of the following occurs:
  • If the recipient opens the recall message first, the original message is deleted, and the recipient is informed that you, the sender, deleted the message from his or her mailbox.
  • If the recipient opens the original message first, the recall fails, and both the old and new messages are available.
 NOTE   If the recipient read the original message and then marked it as unread, Outlook treats it as if it had never been read and recalls it successfully.
You send an e-mail message to a public folder. You recall the original message and replace it with a new one.
One of the following occurs:
  • If the recipient who reads the recall message has read access to all the items in the public folder but did not read the original message, the recall succeeds, and only the new message remains. You, the sender, receive a message indicating that the recall succeeded.
  • If the recipient has already marked the original message as read, he or she is informed that the recall failed, and only the recall message is deleted.
If a user with any other public folder rights opens the recall message, the recall fails, and the user receives a message indicating that the recall failed. Both the old and new messages remain in the public folder.
 NOTES 
  • If the recipient reads the original message and then marks it as unread, Outlook treats it as if it had never been read and recalls it successfully.
  • In the public folder, it is the reader's rights, not the sender's, that determine the success or failure of the recall.

Adding or removing icons in Windows Control Panel.


Issue

Adding or removing icons in Windows Control Panel.

Cause

Missing Control Panel icons can be caused by any of the below possibilities.
  1. Control Panel icon was deleted or has become corrupt.
  2. Related software program or hardware device has been uninstalled or is no longer being detected by Windows.

Solution

Note: Before following any of the below steps if you're running Windows ME / XP or later we suggest that Control Panel be setup to show icons in Classic View.
Enabling and removing Control Panel icons easily with TweakUI
Microsoft Windows XP and later revisions of Windows users can easily enable and remove Control Panel icons with the TweakUI program.
After TweakUI has been installed, check and uncheck the the icons you wish or do not wish to display in the Windows Control Panel under the Control Panel section.
Adding Windows Control Panel icons
Users can add a Windows Control Panel icon by installing the software program or hardware device related to the icon. If doing this does not install an icon into the Windows Control Panel that is either listed in the below chart or has been present in the past, follow the below steps.
  1. Reinstall the software program or hardware device associated with the program. This should copy the the necessary .CPL file back onto the computer.
  2. Manually copy, expand, and extract the .cpl file back into the Windows System or System 32 directory.
Note: Unless your software program or hardware device has a .cpl file associated with it, the program will not create an icon in your Control Panel. 
Manually testing or running a Windows Control Panel .cpl file
If you are unfamiliar with what each .CPL file does,
  1. Manually execute many of the .CPL files by typing "control <name of .cpl file>.cpl." See thecontrol command page for additional information and help with this command.
  2. Users can also use the rundll32 file to open the Control Panel icons. Below is an example of how a user would open the Date/Time Properties window using the rundll32 file. If you wish to run an alternate .cpl file, replace the TimeDate.cpl with a different .cpl.
rundll32.exe shell32.dll,Control_RunDLL TimeDate.cpl
Hiding Windows Control Panel icons
If you wish to hide an icon from being displayed in the Control Panel you can delete or move the icon as explained in the below steps or hide the icon by editing the control.ini file.
Removing Windows Control Panel icons
Using the Microsoft Find utility, users can locate all .cpl files on their computer.
Once all the .cpl files have been found, locate the file associated with your icon and delete the file or move it to an alternate location.
Windows Control Panel icons and their associated files
Below is a small chart of the available files and their associated Control Panel icons. Keep in mind that not all of the below files or icons are available in all versions of Microsoft Windows and may be missing because the associated hardware device, software program, or other setting is not installed. Icons that have an asterisks in the availability section indicate that a third-party software program not available through the Microsoft Windows CD must be installed before the icon is displayed.
Control Panel IconAssociated file95/98/MENT2000/XP
Accessibility OptionsAccess.cplYesYesYes
Add/Remove HardwareHdwwiz.cplYesYesYes
Add/Remove ProgramsAppwiz.cplYesYesYes
Adobe Gammaadobe gamma.cpl***
MS-DOS ConsoleConsole.cplYes
Date/TimeTimeDate.cplYesYesYes
DirectXdirectx.cpl***
DisplayDesk.cplYesYesYes
FaxFax.cplYesYes
Find FastFindfast.cplYesYes
FontsMain.cplYesYesYes
GSNWNwc.cplYes
Intel Pro SetProset.cplYes
InternetIntelcpl.cplYesYesYes
Infrared Settings propertiesIrprops.cplYes
Java Plug-in x.x.x - This icon and its associated
file changes by version.
plugincplx_x.cpl***
Joystick Properties or Game ControllersJoy.cplYesYesYes
KeyboardMain.cplYesYesYes
LicensingLiccpa.cplYes
MacfileSfmmgr.cplYes
Mail and FaxMlcfg32.cplYes
Microsoft Mail Post OfficeWgpocpl.cplYes
ModemsModem.cplYesYes
MouseMain.cplYesYesYes
MultimediaMmsys.cplYesYesYes
Network Connections propertiesNcpa.cplYesYes
Network PropertiesNetcpl.cplYes
ODBC32Odbc32.cplYesYesYes
Passwordspassword.cplYes
PCCardDevapps.cplYes
PortsPorts.cplYes
Power Options propertiesPowercfg.cplYes
PrintersMain.cplYesYesYes
QuickTimeQuicktime.cpl***
Regional SettingsIntl.cplYesYesYes
Services and DevicesSrvmgr.cplYes
SCSI AdaptersDevapps.cplYes
ServerSrvmgr.cplYes
SoundsMmsys.cplYesYesYes
Speech PropertiesSapi.cplYes
SystemSysdm.cplYesYes
Tape DevicesDevapps.cplYes
Telephony or Phone and Modem Options PropertiesTelephon.cplYesYes
TweakUITweakui.cpl***
UPSUps.cplYes
User Accounts propertiesNusrmgr.cplYes
VirusScanAvsmcpa.cpl***

Additional information

Microsoft Windows stores information about each of the icons that are shown in the Control Panel in files with the extension .CPL. If these files are present and not corrupted, Microsoft Windows will display these icons, otherwise, these icons will not be visible. The Control Panel files are often found in the C:\Windows\System, C:\Windows\System32, or C:\Winnt\system32 directories once the hardware device or software program related to the icon has been installed.
  • Additional information about the Microsoft Windows Control Panel as well as related dictionary definitions can be found on our Control Panel definition.

Friday, September 23, 2011

This three part article series takes a step by step look at how to prepare for, create and configure an Exchange 2007 Cluster Continuous Replication based mailbox server.

Introduction

Exchange Server 2007 introduces several new high availability features, one of them is the Cluster Continuous Replication (CCR) feature. This feature takes the new Exchange Server 2007 Log file shipping and replay features and combines them with the features that are available in a more traditional 2 node Windows 2003 active/passive cluster setup. A traditional 2 node active/passive cluster certainly has its benefits, but it also has one major drawback and that is you still have a single point of failure when it comes to Exchange databases.

Prerequisites

In order to follow the steps throughout this article series, you need the following:
  • A Windows 2003 Active Directory forest with at least one Domain Controller (raised to 2000 or 2003 forest functional level).
  • Two Windows 2003 Server R2 Enterprise Editions or Windows 2003 Server SP1 Enterprise Editions.
  • One Windows File share Witness (MS recommends this to be an Exchange 2007 Hub Transport Server in the existing Exchange 2007 organization)
NoteRemember to apply the update mentioned in MS KB article 921181 to both servers that will act as nodes in the Exchange Server 2007 Clustered Mailbox setup. The update adds a new file share witness feature to the current Majority Node Set (MNS) quorum model. The file share witness feature lets you use a file share that is external to the cluster as an additional "vote" to determine the status of the cluster in a two-node MNS quorum cluster deployment, which is a requirement in order to make use of the cluster continuous replication (or CCR in short) functionality in Exchange Server 2007.

In addition to the above prerequisites you should be aware of the following general requirements as well:
  • When dealing with CCR environments you must use/can only use one database per storage group.
  • You cannot create a public folder database in a CCR environment if you already have more than one public folder database in your organization.
  • You can create up to 50 storage groups and 50 databases on a CCR cluster. Bear in mind though, that you should create only one database per storage group.
  • The cluster in which Exchange 2007 is installed cannot contain Exchange Server 200x, or any version of Microsoft SQL Server. Running Exchange 2007 in a cluster with any of these other applications is not supported.
WarningSince Exchange Server 2007 Beta 2 isn’t supported in a production environment, unless you’re participating in the Rapid Deployment Program (RDP) or Technology Adopter Program (TAP), you should install the mailbox cluster in a test domain.

Configuring the Network Settings for the Cluster nodes

When you start the servers that are to be the nodes in the cluster, start by naming the machines E2K7Node1 andE2K7Node2 or whatever naming scheme you want to use (these names have nothing to do with the Exchange server name which your clients will be configured to connect to later on). Now name the two network connections Publicand Private for the external and the internal network respectively (remember to do this on both nodes).

Figure 1: Network Connections
Click Advanced > Advanced Settings, if it’s not already the case, make sure Public is listed first on the binding order list, then Private and lastly Remote Access Connections.

Figure 2: Binding order
Before Exchange 2007 SP1 released, it was also recommended to disable File and Printer Sharing for Microsoft Networks for the private network as shown in Figure 3. However, when SP1 released this guidance changed, since Exchange 2007 SP1 introduced a new cmdlet named Enable-ContinuousReplicationHostName. This cmdlet makes it possible to specify over which network log files should be ship and seeded. So no matter whether you deploy CCR on Windows 2003 or Windows 2008 based servers, please don’t disable File and Printer Sharing for Microsoft Networks for the private network.

Figure 3: Disabling File and Printer Sharing for Microsoft Networks
Configure the Public network with the respective network settings you use in your test environment.

Figure 4: Configuring the Public network
Configure the Private network with an IP address and a subnet mask. Nothing else is required since this network is only used for communication (heartbeats) between the nodes in the cluster.

Figure 5: Configuring the Private network
Now click Advanced then select the DNS tab. Here you should untick both Register this connection's addresses in DNS and Use this connection's DNS suffix.

Figure 6: Configuring DNS settings for the Private network
Click the WINS tab. Untick Enable LMHOSTS lookup and select Disable NetBIOS over TCP/IP.

Figure 7: Configuring WINS settings for the Private network
Click OK three times and close the network connections window.
Now add both Windows 2003 Servers as member servers in your Active Directory test domain.

Creating and Configuring the Windows 2003 Server Cluster

advertisement

Now that the two servers are ready to act as nodes in a Windows 2003 cluster, it’s time to create the actual Windows 2003 Server Cluster. In order to do so logon to E2K7Node1 with a Domain admin account, then click Start >Administrative Tools > Cluster Administrator, and select Create new cluster in the drop-down box. Now clickOK.

Figure 8: Creating a new cluster
Note
You can also open a command prompt and type Cluster.exe /create /wizard in order to start the cluster wizard.
Click Next.

Figure 9: Cluster Wizard
Specify the domain name as well as the cluster name (name for the Windows 2003 cluster NOT the Exchange cluster name which the clients will connect to), then click Next.

Figure 10: Cluster Name and Domain
Type the name of the Windows 2003 server that is to be the first node in the cluster, in this case E2K7Node1, then click Next.

Figure 11: Adding the First Cluster Node
Let the cluster wizard determine the cluster configuration and click Next.
NoteYou can ignore the two warnings in Figure 12, since the nodes in a cluster continuous replication based mailbox server setup aren’t going to share the same disk subsystem.

Figure 12: Analyzing Cluster Configuration
Now enter the IP address that the cluster management tools should use to connect to the cluster, in this case10.10.1.216, then click Next.

Figure 13: Specifying the IP address the Cluster Management Tools should connect to
Enter the credentials of the cluster service account (When speaking test environments I’m often too lazy to create a specific cluster service account and instead tend to use the Administrator account which will have the appropriate permissions) and click Next.

Figure 14: Entering the credentials of the Cluster Service Account
Now click Quorum and select Majority Node Set as the resource type, then click Ok and Next.

Figure 15: Proposed Cluster Configuration

Figure 16: Setting Majority Node Set as the Resource Type
Now wait for the cluster to be configured, then click Next.

Figure 17: Creating the Cluster
When the cluster has been completed successfully you can click Finish.

Figure 18: Cluster Wizard Successfully Completed
We now have a full working Windows 2003 cluster running, but since there’s only one node it’s not very fault tolerant. So let’s add the second Windows 2003 server too. We can do this by right-clicking E2K7Node1 in the left pane of the Cluster Administrator, then selecting New > Node as shown in Figure 19 below.

Figure 19: Adding a second node to the Cluster
The Add Nodes Wizard will launch and you can click Next.

Figure 20: Add Nodes Wizard
Enter the name of the server that is going to be the second node (in this case E2K7Node2), then click Next.

Figure 21: Entering the name of the second node
Again let the Add Notes Wizard determine the cluster configuration, then click Next.

Figure 22: Analyzing Cluster Configuration
Enter the password for the cluster service account (in this case the Administrator account), then click Next.

Figure 23: Entering the password for the Cluster Service Account
When you are verified, you want to add the second node to the cluster with the configuration shown in Figure 24, click Next.

Figure 24: Proposed Cluster Configuration for node 2
When the cluster has been configured properly without any errors or warnings, click Next.

Figure 25: Cluster is configured for the second node
When the Add Notes Wizard has completed successfully, click Finish.

Figure 26: Completing the Add Nodes Wizard
The second Windows server is now part of the cluster as can be seen in Figure 27 below.

Figure 27: Cluster Administrator with two nodes
Alright we have reached the end of part one, but you can look forward to part two of this article series in the near future. Until then have a nice one!
If you would like to read the other 

How to block inbound and outbound external mail flow for internal users.

Introduction

For the sake of this article, I created a fictitious organization which I will name MSExchange.org, and a user-name which I will name Anderson.Patricio. Through this article we are going to manage the users ability to send or receive internet messages. These are some of the topics that we are going to cover in this article:
  • Block any incoming mail to that user
  • Block that user from sending outbound messages
  • Allow that user to send messages to a specific user outside
  • Allow the user to receive external messages from a specific domain
  • Allow that user to send messages to a specific domain only
The main idea here is to provide some possible ways to accomplish this kind of task, for your personal environment or for the entire network. You can also combine more than one of the possible scenarios above to accomplish your requirements.

Managing the inbound traffic to a specific user

There are several ways to manage the incoming traffic to a specific user. We can create Transport Rules, configure Recipient Filtering, change at mailbox level and so on.
The first option is to use Transport Rules. This feature allows us to create a rule to return a NDR to the sender, for example, saying that this specific user does not have permission to receive Internet mail. This can be done as follows:
  1. Open Exchange Management Console
  2. Expand Organization Configuration
  3. Click on Hub Transport
  4. Click on Transport rules tab
  5. On Toolbox Actions, click on New Transport Rule…
  6. In the Introduction page, define a name for the rule and click Next
  7. In the Conditions page. Select the from users inside or outside the organization item and sent to people item as well. In the step 2 box, you can define the previous items’ value. To do this, make sure that the Outside value is selected for the first one and for the second one you added the user mailbox that will not be able to receive Internet mail. When done, click on Next
  8. In the Actions page, select the option send bounce message to sender with enhanced status code, you can go to Step 2 box, and change the text of the message and status code as well. (Figure 1)

Figure 1
  1. In the Exceptions page. Let’s just click on Next, New and Finish.
A second option is using Recipient Filtering anti-spam agent, it is enabled by default in an Edge Transport Server. However, if you are using the Hub Transport role to receive internet mail you need to enable the Anti-Spam Transport Agents, you can find how to do that in this following MSExchange.org article.
Either way, the process to configure the Recipient Filtering is very similar to the previous one. We are going to cover those changes in a Hub Transport, which are as follows;
  1. Open Exchange Management Console
  2. Expand Organization Configuration
  3. Click on Hub Transport
  4. Click on Anti-spam tab
  5. Double click on Recipient filtering
  6. Click on Blocked Recipients tab
  7. Check the Block the following recipients option and type in the internal users that you want blocking Internet mail (Figure 2)

Figure 2
The result, as you may expect, is that any message sent from the Internet to anderson@msexchange.org will return a NDR saying that the user does not exist in our organization.
Well, sometimes blocking external incoming traffic to a user is not enough and you want to make the restriction a little tighter. Restricting a user to only receive messages from his boss and no other email client is one such example.
Note:You can also accomplish this requirement by using Transport Rules, however the objective of this article is to give extra options and so, I opted to configure it at mailbox level.
The configuration process is as follows:
  1. Open Exchange Management Console
  2. Expand Recipient Configuration
  3. Click on Mailbox
  4. Double click on the mailbox that you want to restrict
  5. Click on Mail flow settings tab
  6. Click on Message Delivery Restriction and click on Properties
  7. On this page, we are able to restrict the user to accept or reject message from specific users. This user can only accept messages from authenticated users (Figure 3)
Note:
Any message coming from the Internet is not authenticated.

Figure 3

Managing outbound traffic

So far we have seen several ways to block inbound traffic directed towards specific internal users, now it is time to block their ability to send internal/external messages. When we speak about restriction, we are speaking about the Hub transport architecture combined with Transport Rules, which when combined do a great job in this sort of management. Therefore, a simple and easy way to mange outbound traffic is by using Transport rules, and this is how you set it up:
  1. Open Exchange Management Console
  2. Expand Organization Configuration
  3. Click on Hub Transport
  4. Click on Transport rules tab
  5. On Toolbox Actions, click on New Transport Rule
  6. In the Introduction page. define a name for the rule and click on Next
  7. In the Conditions page, select the from people item and from people inside or outside the organization item. In the Step 2 box you can define the previous items values, make sure that on the first one (from people link) you selected all users that are not allowed to send messages out, and on the second one the value Outside is selected
  8. In the Actions page, select the option send bounce message to sender with enhanced status code, you can go to Step 2 box and change the text of the message and status code as well. In this case we are going to change the text to “You are not allowed to send external messages". (Figure 4)

Figure 4
The result will be that any message sent by our test user will generate an NDR on his mailbox and the end-user will be able to see the information about the internal policy that we have just added in our Transport rule (Figure 5).

Figure 5

Dealing with exceptions…

Deploying rules in your organization is really nice but we already know that there is always something and/or some exception which must be created down the road. Technically speaking it is not a big deal and it is included during the transport rule creation process.
However, if you look closely at all the transport rules that we have created so far, there is no built-in rule to allow an internal user to send messages to a specific external domain. You do have the option to create a contact and specify that contact in the exception but it is not possible to do that when the requirement is an entire domain. Let us say that the requirement is that an internal user is able to send messages to any recipient at either Microsoft.com or live.com, well that is a big deal because if the users has a lot of contacts on those domains the contact creation will be painful and unmanageable.
Let us edit the transport rule that we created to block external messages from our organization, and instead select the item except when the text patterns appears in a message header in the Exceptions page. Click on the message header link; type in TO and click on the text patterns link and finally, type in @domain.com$ (where @domain.com can be substituted by any domain that you have in your requirements).
We are going to use a RegEx expression to match the domain(s) that we want to be accepted from our current transport rule. When you see the expression “@domain.com$”, any text that contains that string will be matched, for example: user1@domain.com, userXX@domain.com. However if the user tries user1@domain.com.fr it would not work.
The exception that we added to the transport rule in order to allow internal users to send messages to a specific domain can be seen in the Figure 6.

Figure 6
Now, using the concept we have just seen, we can create an exception for the Inbound Internet mail by editing the existent transport rule and adding the item except when the text patterns appears in a message header item in the Exceptions page. Then, you need to add the text “FROM” on the message header link, and in the list of the domains accepted using the same pattern that we used before (@domain.com$). A summary of this change can be seen in the Figure 7.

Figure 7
These exceptions were created using Transport Rules. If you have in place Sender Filtering or mailbox settings they would not be applied. Keep that in mind when you create your plan to deploy this kind of restriction in your environment.

Explaining DNS Concepts - DNS Servers-DNS Queries-DNS Records

3 types of DNS queries— recursive, iterative, and non-recursive 3 types of DNS servers— DNS Resolver, DNS Root Server and Authoritative Name...