Outlook: Mark messages as read or unread

Manually mark messages as read or unread

1. Select the messages you want to change.
2.  

• To select adjacent items, click the first item, and then hold down SHIFT and click the last item.
• To select nonadjacent items, click the first item, and then hold down CTRL and click additional items.
• To select all items, on the Edit menu, click Select All.

 Note    Changing the view for items can make selecting specific items easier. For instance, if you want to select all messages that have the same subject, in the folder containing the messages, click View, point to Arrange By, and then click Conversation. Select the messages you want from the view.

On the Edit menu, do one of the following:

• To mark a message as read, click Mark as Read.
• To mark a message as unread, click Mark as Unread.
• Mark all the messages in a folder, click Mark All as Read.

 Note     If you mark a replied to or forwarded message as unread, the message symbol continues to display as an open envelope. However, it is still considered unread for sorting, grouping, or filtering.

Automatically mark messages as read in the Reading Pane

1. On the Tools menu, click Options, and then click the Other tab.
2. Click Reading Pane.
3. Select the Mark items as read when viewed in the Reading Pane check box, and then type a number in the Wait n seconds before marking item as read box.

Custom Report created using fields from Job History category shows duplicate entries.

Problem

Custom Report created using fields from Job History category shows duplicate entries.

Solution

This issue is solved in Backup Exec 2012

Please make sure to have "show distinct rows" specified

  

1) Click the "Backup Exec" button (i.e. yellow button on top left of console)

2) Select Configuration and Settings --> Backup Exec Settings

3) Click Reports section

4) Change report content from "Show all rows" to "Show distinct rows"

5) Click OK

6) Re-run report

How to specify a date range for Backup Exec Custom Reports

Problem

When creating a custom report within Backup Exec, it may appear that is there no way to specify a date range within the reports interface.

Solution

To create a report that is specific to a specific range of dates, the Filters will need to be used.

Select one or more filters that have date fields associated with them, such as the Job End Time and Job Start Time filters from the Job History Group.

You could then choose "=" as an operator and specify a date for each field, along with other information that is desired in each report.

Set pst-file as default delivery for Exchange account

Outlook 2003

To set the default delivery location for an Exchange account to a pst-file in Outlook 2003;

Tools-> E-mail Accounts…-> View or change existing e-mail accounts-> Next-> dropdown box: Deliver new e-mail to the following location: select Personal Folders.

Outlook 2007 and Outlook 2010

To set the default delivery location for an Exchange account to a pst-file in Outlook 2007 or 2010, you must also start with changing your default storage location to pst-file, just as in Outlook 2003;

• Outlook 2007
  Tools-> Account Settings…-> tab Data Files
• Outlook 2010
  File-> Account Settings-> Account Settings…-> tab Data Files

Accept the warning about changing the default Outlook Data File and restart Outlook.

You are not done yet! Once you’ve restarted Outlook, go back to your account settings but this time select the E-mail tab. Here, select your Exchange account and press the Change Folder button at the bottom. Accept the warning and select the root folder of the pst-file as the new storage location. Restart Outlook again to complete the process.

First set your default data store to a pst-file and then set your Exchange delivery to that pst-file. (click on images to enlarge)

Notes

I do not recommend storing your mails to a pst-file when you have an Exchange account as you’ll lose sharing capabilities and it makes you responsible for your backups and not the Exchange administrator. If you still want to go this route for whatever reason, keep the following in mind;

• Original Inbox items will be received automatically but a copy could also remain in the Inbox of the Exchange account. This does not apply to items that you received after making this change.
• You’ll need to move existing items other than from the Inbox folder manually to the pst-file after you have made this change.
• Make backups of your pst-file! This can of course be a network location so that they can be included in the corporate backups.
• Do not set the location of your pst-file itself to a network location. This is not supported by Microsoft as it could lead to poor performance, data corruption or even data loss.
• Exchange features such as sharing are not supported but you can still set your Out of Office Assistant.
• Modify your “move to folder” rules so that they are being moved in your pst-file and not back on the server.
• Messages could still be delivered to your Junk E-mail folder when they get filtered by the Exchange server. You cannot change this.
• You cannot remove the folder set of your (now empty) Exchange mailbox.

Offloading because Exchange mailbox is too small

If you are thinking about delivering your mail to a pst-file because of limited capacity on the Exchange server, it might be better leave your Exchange account as the default and to use AutoArchive to offload your Exchange mailbox to a pst-file. By doing so, you’ll keep the most recent messages on-line and you would still be able to share your Calendar and Contacts folder. This also makes sure that they are included in at least 1 Exchange backup.

Contact your manager or mail administrator for additional information about how long you should store your mail archive, where it should be stored, what it should contain and what can be deleted. They should provide you with sufficient space for this.

Unable to login to Symantec Endpoint Protection Manager

Unable to logon to SEPM, hangs at login Stopped the Symantec Endpoint Protection Manager service.

Set the following two registry values:

HKLM\System\CurrentControlSet\Services\semsrv\Parameters\

JVM Option Number 0=-Xms1024m

JVM Option Number 1=-Xmx1024m

JVM Option Number 2=-XX:MinHeapFreeRatio=40 JVM Option Number 3=-XX:MaxHeapFreeRatio=70

Started the Symantec Endpoint Protection Manager service.

<

<

"dbsrv9 -f "C:\Program Files\Symantec\Symantec Endpoint Protection Manager\db\sem5.db

<

<

<

<

Managing SQL Server Permissions (p2) - Using SSMS to Manage Permissions at the Database Level

The same type of hierarchy exists with permissions at the database level as at the server level. You can apply permissions at a high level to affect many objects of a particular type, or you can apply them on a specific object. You can also manage the permissions at the database level on a specific database user, or you can manage them on the database across many users.

To demonstrate the differences between object types available at the database level, let’s first look at managing permissions for a specific database user. As with logins, you can right-click a database user and select Properties. On the Properties window that appears, you select the Securables page, and you get a screen to assign permissions that is very similar to the login permissions screen. The difference at the database level is in the object types available for selection. Figure 6 shows the object types available when you choose the All Objects of Types choice during the addition of securables for a database user.

Figure 6. Database-level object types.

When a low-level object type such as a table or stored procedure is selected, you are able to apply explicit permissions to a specific object instance. Figure 7 Table object type is selected. shows an example of low-level securables available when the

Figure 7. Low-level database securables.

To apply permissions at a higher level in the database, you choose the object type Databases. With this securable added to the permissions grid, you can apply permissions to a group of objects by selecting a single permission. Figure 8 shows the AdventureWorks2008 database selected as the securable and the related permissions available. In this example, the login Chris has been granted INSERT, SELECT, and UPDATEpermissions to all the tables in the AdventureWorks2008 database.

Figure 8. High-level database securables.

Active Directory Domain Services 2008 : Transfer the RID Master Role

Scenario/Problem: Each Active Directory Domain Services domain has a single domain controller that is authoritative for processing RID Pool requests from all DCs within a given domain. This domain controller is called the RID master. Each domain in a forest has a domain controller configured as the RID master for that given domain. By default, this role is enabled on the first domain controller you add to a domain.

Solution: The RID master operations master role can be transferred by using the Windows interface or the command line.

Transfer the RID Master Role by Using the Windows Interface

To transfer the RID master role by using the Windows interface, perform the following steps:

1.	Log on to a domain controller or a member computer that has Windows Server 2008 RSAT installed.
2.	Click Start, click Administrative Tools, and click Active Directory Users and Computers.
3.	Right-click the domain node in the console tree and select Change Domain Controller, as shown in Figure 1. Figure 1. Active Directory Users and Computers console.
4.	On the Change Directory Server page, shown in Figure 2, select the domain controller to which you want to transfer the RID master role; then click OK. Figure 2. Change Directory Server page.
5.	Right-click the domain node in the console tree and select Operations Masters.
6.	On the Operations Masters page, select the RID tab, shown in Figure 3. Figure 3. Operations Masters RID tab.
7.	Ensure the domain controller you selected in Step 4 is listed as the targeted server and click Change.
8.	On the confirmation page, click Yes.
9.	A message displays that indicates the operation completed successfully.

Transfer the RID Master Role by Using the Command Line

1.	Log on to a domain controller.
2.	Click Start, and click Command Prompt.
3.	In the Command Prompt window, type ntdsutil and press Enter.
4.	At the ntdsutil command prompt, type roles and press Enter.
5.	At the fsmo maintenance command prompt, type connections and press Enter.
6.	At the fsmo maintenance command prompt, type connect to server DomainController, whereDomainController is the domain controller to which you want to transfer the role, and press Enter.
7.	At the server connections command prompt, type quit and press Enter.
8.	At the fsmo maintenance command prompt, type transfer RID master and press Enter.
9.	On the Role Transfer Confirmation page, click Yes to confirm the transfer.