Outlook 2003

How to Turn On the Out of Office Assistant

1. On the Tools menu, click Out of Office Assistant.

2. In the Out of Office Assistant dialog box, click I am currently Out of the Office.

3. In the Auto Reply only once to each sender with the following text box, type the message that you want to send while you are out of the office.

How to Create a Rule

1. On the Tools menu, click Out of Office Assistant.

2. In the Out of Office Assistant dialog box, click Add Rule.

3. In the When a message arrives that meets the following conditions box, specify the conditions that you want the message to meet.

4. Click to select the Do not process subsequent rules check box to specify that this rule must be the last one applied.

5. To specify more conditions, click Advanced; select the options that you want, and then click OK.

6. In the Perform these actions box, select the options that you want.

How to Delete a Rule

1. On the Tools menu, click Out of Office Assistant.

2. In the These rules will be applied to incoming messages while you are out of the office box, click the rule that you want to delete.

3. Click Delete Rule, and then click Yes.

How to Edit a Rule

1. On the Tools menu, click Out of Office Assistant.

2. In the These rules will be applied to incoming messages while you are out of the office box, click the rule that you want to edit, and then click Edit Rule.

3. Make changes to the conditions and actions for the rule.

How to Change the Order in Which Rules are Applied

1. On the Tools menu, click Out of Office Assistant.

2. In the These rules will be applied to incoming messages while you are out of the office box, click the rule that you want to move up or down in the list.

3. Click Move Up or Move Down.

How to Turn a Rule On or Off

1. On the Tools menu, click Out of Office Assistant.

2. In the These rules will be applied to incoming messages while you are out of the office box, click to select or click to clear the check box next to the rule that you want to turn on or off.

How Rules Are Applied

Rules are applied in the order in which they appear, going from top to bottom, in the list of rules in the Out of Office Assistant box.

If you select more than one condition in the Edit Rule box, only messages that meet all of the conditions have the rule applied to them. For example, if you specify "Bob Green" as the sender (condition), and "Marketing Meeting" (condition) in the Subject box, the rule only applies to messages that meet both conditions.

If you set multiple conditions in one rule, messages that meet any of the conditions in the rule are found. For example, if you specify "Bob Green; Jeffrey Weems," in the From box, the rule applies to messages from either Bob Green or Jeffrey Weems. To specify that a rule must be the last one applied, click to select the Do not process subsequent rules check box (in the Add Rule or Edit Rule dialog box).

When you specify an action for a rule and the action cannot be performed, an error message appears with an "X" next to the rule. To fix the error, click Edit Rule, and then make any necessary changes

Remote Blob Storage(RBS) Configuration

First of all we have to activate FILESTREAM on the SQL instance that you want to put to the BLOB. 

Connect to SQL Server

Start –> All Programs –> Microsoft SQL Server 2008 R2 –> Configuration Tools –> SQL Server Configurations Manager

In the Services list, click “SQL Server Services”

Choose your SQL instance (here “SQL Server (MSSQLSERVER)”) and right click Properties.

Switch to the FILESTREAM tab and check all the available checkboxes

Click Apply –> OK 

Now start SQL Server Management Studio

Start –> All Programs –> Microsoft SQL Server 2008 R2 –>SQL Server Management Studio

Open a query windows and start the following SQL statement

 

For easier reference, just copy the text below

---

EXEC sp_configure filestream_access_level, 2 

RECONFIGURE 

---

Connect to a Front End Server Start –> Microsoft SharePoint 2010 Products –> SharePoint 2010 Management Shell Create a Content Database

 

For easier reference, just copy the text below

---

New-SPContentDatabase –name WSS_Content_Blob_001 –WebApplication http://sp2010 –MaxSiteCount 1 –WarningSiteCount 0

---

Connect to your SQL Server

Start –> All Programs –> Microsoft SQL Server 2008 R2 –>SQL Server Management Studio

---

if not exists (select * from sys.symmetric_keys where name = N'##MS_DatabaseMasterKey##')create master key encryption by password = N'Admin Key Password !2#4'

---

if not exists (select groupname from sysfilegroups where groupname=N'RBSFilestreamProvider')alter database [WSS_Content_Blob_001]  add filegroup RBSFilestreamProvider contains filestream

---

alter database [WSS_Content_Blob_001] add file (name = RBSFilestreamFile, filename = 'c:\Blob_001') to filegroup RBSFilestreamProvider

---

Connect to the Web Front End hosting the Central Admin Console

Open a Command Prompt (IMPORTANT -> run with elevated permissions) 

Change to the directory containing the previously downloaded RBS.exe

Delete or rename a already existing „rbs_install_log.txt“ if applicable.

Run the follwoing command, replace DBNAME with your content database and DBINSTANCE with your SQL instance. Mind that this command only works once, if you want to configure a second database, chose the option “Configure additional database” (see below).

---

msiexec /qn /lvx* rbs_install_log.txt /i RBS.msi TRUSTSERVERCERTIFICATE=true FILEGROUP=PRIMARY DBNAME="WSS_Content_Blob_001" DBINSTANCE="DC" FILESTREAMFILEGROUP=RBSFilestreamProvider FILESTREAMSTORENAME=FilestreamProvider_1

---

After this process has completed (it may take a minute or two, the log reads “Verbose Logging stopped”), check the “rbs_install_log.txt” if it contains the following line of text (it should be approximately 21 lines before the end of the file: 

---

"Product: SQL Remote Blob Storage -- Configuration completed successfully" 

---

If that is not the case you have an issue. Check the following:

- Are you in the right directory

- Did you make a typo

- Did you run the prompt with elevated privileges

If you have more than one WFE in your farm, you now have to change to the other servers and run the following command: 

For easier reference, just copy the text below 

---

msiexec /qn /lvx* rbs_install_log.txt /i RBS.msi DBNAME="WSS_Content_Blob_001" DBINSTANCE="DC" ADDLOCAL="Client,Docs,Maintainer,FilestreamClient,FilestreamServer" 

---

Check the “rbs_install_log.txt” if it contains the following line of text (it should be approximately 21 lines before the end of the file: 

---

"Product: SQL Remote Blob Storage -- Configuration completed successfully" 

---

Execute all steps from step 7 on every additional WFE. This is mandatory, otherwise problems might occur.

Connect to SQL Server

Start –> All Programs –> Microsoft SQL Server 2008 R2 –>SQL Server Management Studio

Execute the following query

 

For easier reference, just copy the text below 

---

use WSS_Content_Blob_001 

select * from dbo.sysobjects 

where name like ‘rbs%’ 

---

Connect to WFE

Start –> Microsoft SharePoint 2010 Products –> SharePoint 2010 Management Shell

Execute the following commands in sequence:

 

For easier reference, just copy the text below 

---

$cdb = Get-SPContentDatabase WSS_Content_Blob_001 

---

$rbss = $cdb.RemoteBlobStorageSettings

---

$rbss.Installed()

---

$rbss.Enable() 

---

$rbss.SetActiveProviderName($rbss.GetProviderNames()[0]) 

---

$rbss 

---

Connect to WFE

Start –> Microsoft SharePoint 2010 Products –> SharePoint 2010 Central Administration

Application Management – Manage Content Databases

Choose the applicable Web Application

Configure the Content Database to put the next site collection to “WSS_Content_Blob_001”

– If you have multiple databases, set “Maximum Number of Site Collections” to the current value

– “WSS_Content_Blob_001” should not contain any site collections

Go back to the main site of  Central Administration

Application Management – Create Site Collection

- Enter all the required data

- OK

As soon as the site collection creation is finished, all newly uploaded documents should be created in the filesystem.

Notice:

---

$cbd.RemoteBlobStorageSettings.MinimumBlobStorageSize=1048576$cbd.Update()

---

This was the first step, FILESTREAM is now successfully activated.All further steps requires SharePoint to be installed properly and that a WebApplication has already been created. The Content Database in this case I created by Powershell: Now the new content database (in this case “WSS_Content_Blob_001”) has to be prepared for use with FILESTREAM. Open a query and execute the statement below. Replace “C:\Blobstore“ by your storage-path. The directory must not exist when executing the statement, otherwise an error will be given.  For easier reference, just copy the text below
use [WSS_Content_Blob_001]
use [WSS_Content_Blob_001]
use [WSS_Content_Blob_001]
Now the direcory for the Blobstore has been created in “C:\Blob_001”Next you have to download the EXE for RBS, and it has to be copied to each Web Frontend Server (please, do not rename the file). During all the following steps mind checking the log files for errors. The script has created a few tables in the database, check if they are existing: The result should show the RBS tables. This may take a while.As one last step you have to tell Sharepoint that the content database uses RBS. To do that you have to execute the following command: Since all has been prepared we can check the functionality. Just create a site collection and make sure the content database used is “WSS_Content_Blob_001”. (or whatever you chose during install). Documents below 100 kB will not be put to the file system but will be stored in the database.If you like to change this value, you can use this command (to set the value to 1MB):

$cbd = Get-SPContentDatabase “WSS_Content”Configure additional content databases:If you want to configure more than one content database for RBS, all the steps above have to be executed. The only difference is the command in step 5. This one dies not work, and no RBS tables are created. Therefore use the command below:

 msiexec /qn /i rbs.msi REMOTEBLOBENABLE=1 FILESTREAMPROVIDERENABLE=1 DBNAME=WSS_Content_Blob_002 FILESTREAMSTORENAME=FilestreamProvider_1 ADDLOCAL=EnableRBS,FilestreamRunScript DBINSTANCE=CD 

Grant Active Directory Domain Services permissions for profile synchronization

Grant Active Directory Domain Services permissions for profile synchronization (SharePoint Server 2010)

Grant Replicate Directory Changes permission on a domain

Use this procedure to grant Replicate Directory Changes permission on a domain to an account.
The Replicate Directory Changes permission enables the synchronization account to read AD DS objects and to discover AD DS objects that have been changed in the domain. The Grant Replicate Directory Changes permission does not enable an account to create, modify or delete AD DS objects.

To grant Replicate Directory Changes permission on a domain

1. On the domain controller, click Start, click Administrative Tools, and then click Active Directory Users and Computers.
2. In Active Directory Users and Computers, right-click the domain, and then click Delegate Control.
3. On the first page of the Delegation of Control Wizard, click Next.
4. On the Users or Groups page, click Add.
5. Type the name of the synchronization account, and then click OK.
6. Click Next.
7. On the Tasks to Delegate page, select Create a custom task to delegate, and then click Next.
8. On the Active Directory Object Type page, select This folder, existing objects in this folder, and creation of new objects in this folder, and then click Next.
9. On the Permissions page, in the Permissions box, select Replicating Directory Changes (select Replicate Directory Changes on Windows Server 2003), and then click Next.
10. Click Finish.

Add an account to the Pre-Windows 2000 Compatible Access group

Use this procedure to add an account to the Pre-Windows 2000 Compatible Access group.

To add an account to the Pre-Windows 2000 Compatible Access group

1. On the domain controller, click Start, click Administrative Tools, and then click Active Directory Users and Computers.
2. In Active Directory Users and Computers, expand the domain, expand Builtin, right-click Pre-Windows 2000 Compatible Access, and then click Properties.
3. In the Properties dialog box, click the Members tab, and then click Add.
4. Type the name of the synchronization account, and then click OK.
5. Click OK.

Grant Replicate Directory Changes permission on the cn=configuration container

Use this procedure to grant Replicate Directory Changes permission on the cn=configuration container to an account.

To grant Replicate Directory Changes permission on the cn=configuration container

1. On the domain controller, click Start, click Run, type adsiedit.msc, and then click OK.
2. If the Configuration node is not already present, do the following:
   
   1. In the navigation pane, click ADSI Edit.
   2. On the Action menu, click Connect to.
   3. In the Connection Point area of the Connection Settings dialog box, click Select a well know Naming Context, select Configuration from the drop-down list, and then click OK.
3. Expand the Configuration node, right-click the CN=Configuration... node, and then click Properties.
4. In the Properties dialog box, click the Security tab.
5. In the Group or user names section, click Add.
6. Type the name of the synchronization account, and then click OK.
7. In the Group or user names section, select the synchronization account.
8. In the Permissions section, select the Allow check box next to the Replicating Directory Changes (Replicate Directory Changes on Windows Server 2003) permission, and then click OK.

Grant Create Child Objects and Write permission

Use this procedure to grant Create Child Objects and Write permission to an account.

To grant Create Child Objects and Write permission

1. On the domain controller, click Start, click Run, type adsiedit.msc, and then click OK.
2. If the Default naming context node is not already present, do the following:
   
   1. In the navigation pane, click ADSI Edit.
   2. On the Action menu, click Connect to.
   3. In the Connection Point area of the Connection Settings dialog box, click Select a well know Naming Context, select Default naming context from the drop-down list, and then click OK.
3. In the navigation pane of the ADSI Edit window, expand the domain, expand the DC=... node, right-click the OU to which you want to grant permission, and then click Properties.
4. On the Security tab of the Properties dialog box, click Advanced.
5. In the Advanced Security Settings dialog box, select the row whose value in the Name column is the synchronization account and whose value in the Inherited From column is <not inherited>, and then click Edit. If this row is not present, click Add, click Locations, select Entire Directory, click OK, type the synchronization account, and then click OK. This adds the appropriate row, which you can now select.
   

   Note:
   Do not select the row for the synchronization account that is inherited from another location. Doing so would only enable you to apply the permissions to the OU and not to the contents of the OU.

6. In the Permission Entry dialog box, select This object and all descendant objects from the Apply to box, (select This object and all child objects on Windows Server 2003), select the Allow check box in the rows for the Write all properties and Create all child objects properties, and then click OK.
7. Click OK to close the Advanced Security Settings dialog box.
8. Click OK to close the Properties dialog box.
9. Repeat steps 3 through 8 to grant permissions on any additional OUs.