Friday, August 20, 2010
Adjust time Setting by changing time zone using GPOs
We will walk through three main steps to complete this setting:-
1. Disable Automatic adjust clock for Daylight Saving Time using administrative template.
2. Change local time zone using batch file.
3. Deploy all above setting using created GPO linked to all computers OU.
• Disable Automatic adjust clock for Daylight Saving Time using administrative template
1- Create new Notepad file
2- Copy the following code to it:
CLASS MACHINE
CATEGORY "Windows Time settings"
POLICY "Disable automatic set of daylight savings time"
KEYNAME "System\CurrentControlSet\Control\TimeZoneInformation"
VALUENAME "DisableAutoDaylightTimeSet"
END POLICY
END CATEGORY
3- Save it as DST.adm
• Change local time zone using batch file
1- Create new Notepad file
2- Copy the following code to it:
TZChange.exe /C "Time Zone Nam"
3- Save it as DST.bat
• Deploy all above setting using created GPO linked to all computers OU
1- Create a new GPO, name it DST Change then link it to all computers OU
2- Edit it by adding DST.adm to administrative templates under computer configuration
3- Enable Disable automatic set of daylight saving time setting under Computer Configuration>>>Administrative Templates>>>Windows Time settings
4- Add DST.bat as a startup script under Computer Configuration>>>Windows Settings>>>Scripts (Startup/Shutdown)>>>Startup
And now we complete all necessary steps in order to change the time using GPO and you can modify it any time according to your need.
1. Disable Automatic adjust clock for Daylight Saving Time using administrative template.
2. Change local time zone using batch file.
3. Deploy all above setting using created GPO linked to all computers OU.
• Disable Automatic adjust clock for Daylight Saving Time using administrative template
1- Create new Notepad file
2- Copy the following code to it:
CLASS MACHINE
CATEGORY "Windows Time settings"
POLICY "Disable automatic set of daylight savings time"
KEYNAME "System\CurrentControlSet\Control\TimeZoneInformation"
VALUENAME "DisableAutoDaylightTimeSet"
END POLICY
END CATEGORY
3- Save it as DST.adm
• Change local time zone using batch file
1- Create new Notepad file
2- Copy the following code to it:
TZChange.exe /C "Time Zone Nam"
3- Save it as DST.bat
• Deploy all above setting using created GPO linked to all computers OU
1- Create a new GPO, name it DST Change then link it to all computers OU
2- Edit it by adding DST.adm to administrative templates under computer configuration
3- Enable Disable automatic set of daylight saving time setting under Computer Configuration>>>Administrative Templates>>>Windows Time settings
4- Add DST.bat as a startup script under Computer Configuration>>>Windows Settings>>>Scripts (Startup/Shutdown)>>>Startup
And now we complete all necessary steps in order to change the time using GPO and you can modify it any time according to your need.
Configure MOC 2007 R2 Clients using GPOs
We will walk through three main steps in order to complete creating and deploying these configurations:-
• Download required administrative templates
• Create Group Policy and add the administrative templates to it
• Create a security group and filter the GPO to it
Download required administrative templates
One way to provide the appropriate registry settings for each user when you are deploying Office Communicator 2007 R2 or Microsoft office Live Meeting 2007 is to define Group Policies by using an administrative template (.adm) file.
Create Group Policy and add the administrative templates to it
In order to automatically configure and manage the Office Communicator components (MOC 2007 R2 and Live Meeting 2007) the creation and configuration of a dedicated Group Policy Object is required.
The new GPO should be linked to the OU that directly or indirectly contains all the user accounts under your administration, even if the Office Communicator components are not to be distributed over all of them: a security group must be configured and set as target of the GPO object.
In this way only the user accounts set as member of this group will be involved into the automated configuration procedures.
After creating GPO you must add the administrative Template, after adding adm files you can configure GPO settings.
The following figure describes the custom GPO containers containing setting for Communicator and Live Meeting clients.
If you don’t see settings disable filtering view.
Then configure the settings accordingly to the following figure, and you can modify it according to your requirements.
Create a security group and filter the GPO to it
In order to filter GPO scope it’s necessary to create a security group, for example MOC2007 Users security group.
Then configure a GPO containing the above settings as following:
• Scope: OU where the GPO has been linked (top level domain OU is preferred)
• Security filtering: add the previously created group and delete any other account listed in the Security Filtering panel
• Download required administrative templates
• Create Group Policy and add the administrative templates to it
• Create a security group and filter the GPO to it
Download required administrative templates
One way to provide the appropriate registry settings for each user when you are deploying Office Communicator 2007 R2 or Microsoft office Live Meeting 2007 is to define Group Policies by using an administrative template (.adm) file.
Create Group Policy and add the administrative templates to it
In order to automatically configure and manage the Office Communicator components (MOC 2007 R2 and Live Meeting 2007) the creation and configuration of a dedicated Group Policy Object is required.
The new GPO should be linked to the OU that directly or indirectly contains all the user accounts under your administration, even if the Office Communicator components are not to be distributed over all of them: a security group must be configured and set as target of the GPO object.
In this way only the user accounts set as member of this group will be involved into the automated configuration procedures.
After creating GPO you must add the administrative Template, after adding adm files you can configure GPO settings.
The following figure describes the custom GPO containers containing setting for Communicator and Live Meeting clients.
If you don’t see settings disable filtering view.
Then configure the settings accordingly to the following figure, and you can modify it according to your requirements.
Create a security group and filter the GPO to it
In order to filter GPO scope it’s necessary to create a security group, for example MOC2007 Users security group.
Then configure a GPO containing the above settings as following:
• Scope: OU where the GPO has been linked (top level domain OU is preferred)
• Security filtering: add the previously created group and delete any other account listed in the Security Filtering panel
Display a business data from SQL 2005 sever into a SharePoint site
You can add and connect business data Web Parts on a Microsoft Office SharePoint Server 2007 site to display business data from an external database such as Microsoft SQL Server, SAP, or Siebel. The procedures in this article refer to specific data from two AdventureWorks sample databases that are available from the Codeplex Center as following:-
• Running Setup to Install AdventureWorks Sample Databases and Samples
• Creating a Database Connection by Using the Business Data Catalog Editor
• Display a summary of business data in a list
Running Setup to Install AdventureWorks Sample Databases and Samples
The AdventureWorks (OLTP), AdventureWorksDW (data warehouse), and Adventure Works DW (analysis services) sample databases, as well as the companion samples, are not installed by default in SQL Server 2005. You can download these from http://sqlserversamples.codeplex.com at Codeplex Center, or you can use the following procedures to install the sample databases and samples during or after setup. Additional instructions for deploying the Adventure Works DW analysis services project are also provided.
Installation during Setup
To install the sample databases and companion samples during setup, use the following instructions.
1. On the Components to Install page, select Workstation components, Books Online and development tools.
2. Click Advanced and then expand Documentation, Samples, and Sample Databases.
3. Select Sample Code and Applications.
4. Expand Sample Databases and then select the sample databases to install.
5. To complete the installation of the samples, after setup, perform one of the following steps:
1. From the Start menu, click All Programs, click Microsoft SQL Server 2005, click Documentation and Tutorials, click Samples, and then click Microsoft SQL Server 2005 Samples.
2. Alternatively, using Windows Explorer, navigate to:\Program Files\Microsoft SQL Server\90\Tools\Samples\ and double-click SqlServerSamples.msi to launch the installer.
Installation after Setup
If you did not install the sample databases or samples during the initial setup of SQL Server 2005, you can install them later.
1. From Add or Remove Programs, select Microsoft SQL Server 2005 and click Change. Follow the steps in the Microsoft SQL Server 2005 Maintenance wizard.
2. From Component Selection, select Workstation Components and then click Next.
3. From Welcome to the SQL Server Installation Wizard, click Next.
4. From System Configuration Check, click Next.
5. From Change or Remove Instance, click Change Installed Components.
6. From Feature Selection, expand the Documentation, Samples, and Sample Databases node.
7. Select Sample Code and Applications.
8. Expand Sample Databases and then select the sample databases to be installed. Click Next.
9. To install and attach the sample databases, from Sample Databases Setup, select Install and attach sample databases, and then click Next.
The database files are created and stored in the folder:\Program Files\Microsoft SQL Server\MSSQL.n\MSSQL\Data. The database is attached and ready for use.
10. To install the sample database files without attaching, from Sample Databases Setup, select Install sample databases without attaching, and then click Next.
The AdventureWorks database files are created in the folder:\Program Files\Microsoft SQL Server\90\Tools\Samples\AdventureWorks OLTP. AdventureWorksDW files are created in the :\Program Files\Microsoft SQL Server\90\Tools\Samples\AdventureWorks Data Warehouse folder. You must attach the database before you can use it.
11. Select the instance of SQL Server on which to install the sample databases and samples.
12. Complete the steps in the wizard.
13. To complete the installation of the samples, after setup, perform one of the following steps:
1. From the Start menu, click All Programs, click Microsoft SQL Server 2005, click Documentation and Tutorials, click Samples, and then click Microsoft SQL Server 2005 Samples.
2. Alternatively, using Windows Explorer, navigate to:\Program Files\Microsoft SQL Server\90\Tools\Samples\ and double-click SqlServerSamples.msi to launch the installer.
Deploying the Adventure Works DW Analysis Services project
1. Make sure that the AdventureWorksDW and Adventure Works DW databases have been installed.
2. Make sure Analysis Services has been installed.
3. From the SQL Server Business Intelligence Development Studio toolbar, click File, point to Open, and then click Project/Solution.
4. Browse to:\Program Files\Microsoft SQL Server\90\Tools\Samples\AdventureWorks Analysis Services Project, select the file Adventure Works.sln, and then click Open.
5. From Solution Explorer, right-click Adventure Works DW and select Deploy or Process.
Creating a Database Connection by Using the Business Data Catalog Definition Editor
The Business Data Catalog in Microsoft Office SharePoint Server 2007 exposes and incorporates line-of-business (LOB) data into other baseline portal functionality, such as lists and Enterprise Search. To incorporate this data into your portal site, and make it available to the Enterprise Search crawler, you must build an application definition file, which is an XML file that identifies where the data is stored (either in a database, or as a Web service) and what format the data is stored in (for example, what the data types and primary keys are).
The Microsoft Business Data Catalog Definition Editor helps you to author application definition files for the Business Data Catalog. This tool automatically generates the XML for the definition file, so you do not need to manually create the file in an XML editor.
This how-to topic shows you how to create an application definition file for the Business Data Catalog and how to create a database connection by using the new Business Data Catalog Definition Editor. This example uses the AdventureWorksDW sample database for Microsoft SQL Server 2005.
System Requirements
Before you begin, you must install the following:
• Microsoft Office SharePoint Server 2007, Enterprise Edition.
• Microsoft SQL Server 2005 with the AdventureWorksDW database installed.
• Microsoft Business Data Catalog Definition Editor.
Adding an LOB System
Begin by adding a LOB system for the AdventureWorksDW sample database for Microsoft SQL Server 2005.
To add an LOB system
1. On the Start menu, click Microsoft Business Data Application Definition Editor.
2. In the tool, click Add LOB System.
3. In the Add LOB System window, click Connect to Database.
4. Select SqlServer for Connection Type.
5. For Connection String, enter the following text.
Server={DATABASE_SERVER_NAME}\{INSTANCE_NAME};Database=AdventureWorksDW;Integrated Security=SSPI;
Replace {DATABASE_SERVER_NAME}\{INSTANCE_NAME} with the name of your database server.
6. Click Add Table.
7. Drag the following tables to the Design Surface:
o Product
o ProductCategory
o ProductSubcategory
o Reseller
8. In the Foreign Keys section of the DimProduct window, select FK_DimProduct_DimProductSubcategory.
9. Click OK.
10. In the LOB System Name dialog box that opens, click OK to create the AdventureWorksDW connection.
Testing the AdventureWorksDW LOB System Connection
Next, test the connection to the AdventureWorksDW LOB system.
To test the connection to the LOB system
1. In the Metadata Objects pane, expand the AdventureWorksDW node, and then expand the Entities node.
2. Expand the DimProduct node.
3. Expand the Methods node
4. Expand the FindAll_DimProducts node, and then expand the Instances node.
5. Right-click FindAll_DimProduct_Instance, and then click Execute.
6. In the Execute FindAll_DimProduct_Instance window, click Next, and verify that the values from the ProductKey field of the DimProducts table are displayed in the Results window. Click Next to page through the results.
7. Make note of one of the ProductKey values for the next step. For this walkthrough, we use the ProductKey value 212.
8. In the Methods node, expand the Find_DimProduct node, and then expand the Instances node.
9. Right-click Find_DimProduct_Instance, and then click Execute.
10. In the Value field, enter the 212, and then click Execute.
11. If the DimProduct table contains any fields that will not display correctly, you might receive a message, Click OK to close the message and continue.
12. If the Find method is working correctly, the record with the ProductKey field matching 212 appears in the Results window.
Testing the Entity Associations
Now you will test the entity associations for the LOB system.
To test the entity associations
1. In the DimProducts node, expand the Methods node, and then expand the FK_DimProduct_DimProductSubcategory node.
2. Expand the Instances node.
3. Right-click FK_DimProduct_DimProductSubcategory_Instance, and then click Execute to open the Execute FK_DimProduct_DimProductSubcategory_Instance window.
4. Click the Search button or click anywhere in the Value field to open the Select Entity Instance window.
5. Select FindAll_DimProductSubcategory_Instance, and then click Next to display the first page of results.
6. Select the row for the record from the DimProductSubcategory table you want to retrieve the associations for, and then click OK. If the record is not displayed in the first set of results, click Next to page through the results. For this example, select the record with the ProductSubcategoryKey 31.
7. In the Execute FK_DimProduct_DimProductSubcategory_Instance window, click Execute to display all the records from the DimProduct table where the ProductSubcategoryKey field matches 31.
If results are returned, the associations are configured correctly.
Exporting the LOB System Instance Metadata
After you confirm that the connection for the LOB system and with the entities, associations, and methods, are configured correctly within the Business Data Catalog Definition Editor, you are ready to export the LOB system instance metadata to an application definition file.
To export the metadata
1. Select the AdventureWorksDW node in the Metadata Objects window, and then click Export.
2. Save the file as AdventureWorks2005.xml.
Importing the Application Definition File into the Shared Services Provider
Next, you import the application definition file into the Shared Services Provider (SSP).
To import the application definition file into the SSP
1. To start the SharePoint 3.0 Central Administration Web page, click Start, and then point to All Programs. Point to Microsoft Office Server, and then click SharePoint 3.0 Central Administration.
2. In the left navigation pane, click the name of your SSP.
3. In the Business Data Catalog section, click Import application definition.
4. In the Import Application Definition page that opens, browse to AdventureWorks2005.xml, select the file, and then click Open.
5. Click Import.
6. Click Browse, locate the file, and double-click it.
7. Leave all other application definition settings with their default values, and then click Import.
Modifying an Existing Application Definition by using the Business Data Catalog Definition Editor
You can also modify the metadata in an existing application definition file by importing it into the Business Data Catalog Definition Editor. If you are modifying the application definition for an existing application in the Business Data Catalog, you must export the metadata file for the application definition from the SSP first.
To export the application definition file from the SSP
1. To start the SharePoint 3.0 Central Administration Web page, click Start, and then point to All Programs. Point to Microsoft Office Server, and then click SharePoint 3.0 Central Administration.
2. In the left navigation pane, click the name of your SSP.
3. In the Business Data Catalog section, click View applications.
4. In the Applications list, click the application name.
5. Click Export Application Definition to open the Export Application Definition page.
6. Click Export, and then click Save.
To import an application definition file into the Business Data Catalog Definition Editor and modify the metadata
1. On the Start menu, click Microsoft Business Data Catalog Application Definition Editor.
2. Click Import.
3. Browse to the location of the application definition file, select it, and then click Open.
After the LOB system is loaded into the Business Data Catalog Definition Editor, you can make several changes to the LOB system instance, such as:
o Connection string
o Authentication mode
o Add or remove entities
Display a summary of business data in a list
You can display business data from an external database in a simple list form by using the Business Data List Web Part. For example, you can display a list of products and their list prices.
After the data appears, you can edit the view properties of a Business Data List Web Part, just as you can edit the view of any SharePoint list. You can also filter by property or limit the number of items shown in the Web Part.
1. Go to the page on the SharePoint site where you want to display a list of business data.
2. On the Site Actions menu, click Edit Page.
3. In the Web Part zone where you want to add the Web Part, click Add a Web Part.
4. In the Add Web Parts dialog box, select the Business Data List check box, and then click Add.
5. From the business data Web Part that you just created, click the Web Part menu, and then click Modify Shared Web Part to open the tool pane.
6. In the tool pane, next to the Type box, click Browse.
7. In the Business Data Type dialog box, select a business data type for the business application that you are working with, and then click OK.
For example, select Product. In this example, the Application is AdventureWorksDWInstance.
8. In the tool pane, expand the Appearance section.
9. In the Title box, replace Business Data List with your own title for the Web Part, and then click OK.
For example, type Product List in the Title box.
10. From the newly added Web Part, click Edit View, and then do the following:
• In the Items to Retrieve section, select Retrieve all items.
• In the Columns section, select the names of the columns that you want to display in the Web Part.
11. Click OK.
The new Business Data List Web Part now displays a list of products from your business application database.
Display details about a single item of business data
You can display the details about a business item from an external database by using the Business Data Item Web Part. For example, you can display the details about a particular product from the business application database.
1. Go to the page on the SharePoint site where you want to display the details about a particular business item.
2. On the Site Actions menu, click Edit Page.
3. In the Web Part zone where you want to add the Web Part, click Add a Web Part.
4. In the Add Web Parts dialog box, select the Business Data Item check box, and then click Add.
5. From the business data Web Part that you just created, click the Web Part menu, and then click Modify Shared Web Part to open the tool pane.
6. In the tool pane, next to the Type box, click Browse.
7. In the Business Data Type dialog box, select a business data type for the business application that you are working with, and then click OK.
For example, select Product for the Business Data Type. In this example, the Application is AdventureWorksDWInstance.
8. Next to the Item box, click Browse to choose the product that you want to display.
9. In the dialog box that appears, the first drop-down list displays the filters that are defined for this entity in the BDC. Click the Name filter. In the adjacent field, type a product category, such as Bike, that you want to find. Click Search to search for product names that contain the category that you entered.
10. Select one item from the list of products that appears, and then click OK. The ID of the item that you selected is now displayed in the Item box in the tool pane.
11. Under Fields, click the Choose button.
12. In the Select Fields dialog box, select the item information that you want to display, and then click OK.
13. In the tool pane, expand the Appearance section.
14. In the Title box, replace Business Data Item with your own title for the Web Part, and then click OK.
For example, type Featured Product in the Title box.
The new Business Data Item Web Part displays the product details from your business application database.
Connect Web Parts to configure business application actions
By using a Business Data Actions Web Part on your SharePoint site, you can add an action to a product profile that enables you to perform a search for that item on MSN without leaving Office SharePoint Server 2007. The Business Data Actions Web Part displays a list of actions, in the form of links or on a toolbar, that are associated with a business item in the BDC.
Step 1: Add and connect a Business Data Actions Web Part
In this procedure, you add an action to a Business Data Actions Web Part and connect the Web Part to the Product List Web Part that you created earlier in Display a summary of business data in a list.
Before you begin, your administrator must download the AdventureWorksDW SQL Server 2005 Sample database and register it with the BDC. Additionally, your administrator must define the Search on MSN business data action and add it to Office SharePoint Server 2007. Find more information about the AdventureWorksDW SQL Server 2005 Sample database in the See Also section.
You must first have the Full Control or Design permission level before you can modify the Web Parts on your SharePoint site. Find links to more information about permission levels and permissions in the See Also section.
1. Go to the page on the SharePoint site where you created the Product List Web Part.
2. On the Site Actions menu, click Edit Page.
3. In the Web Part zone where you want to add the Web Part, click Add a Web Part.
4. In the Add Web Parts dialog box, select the Business Data Actions check box, and then click Add.
5. From the business data Web Part that you just created, click the Web Part menu, and then click Modify Shared Web Part to open the tool pane.
6. In the tool pane, next to the Type box, click Browse.
7. In the Business Data Type dialog box, select a business data type for the business application that you are working with, and then click OK.
For example, select Product for the Business Data Type. In this example, the Application is AdventureWorksDWInstance.
8. Under Actions, click Choose.
9. In the Select Actions dialog box, select the Display check box for the Search on MSN action, and then click OK.
The View Profile check box should be selected by default. The View Profile action is automatically created for each entity (or business item) that is defined in the BDC. This action enables you to view details about the entity. Because actions are associated with entities, the actions appear wherever the entity is displayed on a SharePoint site.
10. In the tool pane, configure the Web Part as needed in the Appearance, Layout, and Advanced sections, and then click OK to close the tool pane.
11. For the Business Data Actions Web Part that you just created, click the Web Part menu , point to Connections, point to Get Item From, and then click Product List.
If a message appears under the Product Actions Web Part that notifies you of a conflict in connecting the Product Actions Web Part to the Product List Web Part, verify that the Web Parts are both using the AdventureWorksDWInstance sample database.
Step 2: Verify that the Web Parts are properly connected and configured
1. If no data appears in the Product List Web Part, click Retrieve Data.
2. Select an item from the list by clicking the option button next to the product key.
3. In the Product Actions section of the site, click Search on MSN. A new window appears displaying search results for the item selected.
Connect Web Parts to display related business items
You can use the Business Data Related List Web Part along with a Business Data List Web Part to display two lists of related business items from a business application. For example, you can connect the two Web Parts to display all the sales orders for a specific customer.
• Business Data List Web Part
• Business Data Related List Web Part
The following procedure uses fictitious customer data from the AdventureWorks SQL Server 2000 Sample database, which must first be downloaded and registered with the BDC. Find more information about the AdventureWorks SQL Server 2000 Sample database in the See Also section.
Step 1: Create a Web Part to display a summary list
The first step in displaying related data from an external database is to create a Business Data List Web Part to display a summary list of customers.
1. Go to the page on the SharePoint site where you want to display orders for a specific customer in the database.
2. On the Site Actions menu, click Edit Page.
3. In the Web Part zone where you want to add the Web Part, click Add a Web Part.
4. In the Add Web Parts dialog box, select the Business Data List check box, and then click Add.
5. From the business data Web Part that you just created, click the Web Part menu, and then click Modify Shared Web Part to open the tool pane.
6. In the tool pane, next to the Type box, click Browse.
7. In the Business Data Type dialog box, select a business data type for the business application that you are working with, and then click OK.
For example, select Customer for the Business Data Type. In this example, the Application is AdventureWorksDWInstance.
8. In the tool pane, expand the Appearance section.
9. In Title box, replace Business Data List with Customers from AdventureWorks, and then click OK.
Step 2: Create and connect a Web Part to display related items
After you create a Business Data List Web Part that can display customers from the AdventureWorks SQL Server 2000 Sample database, you can create a Business Data Related List Web Part that connects to the first list. The end result will allow you to select an item from the customer list and view a list of sales orders for that customer in the Business Data Related List Web Part.
1. On the same page where you created the Business Data List Web Part, click Add a Web Part to create a new Web Part on the page.
2. In the Add Web Parts dialog box, select the Business Data Related List check box, and then click Add.
3. From the business data Web Part that you just created, click the Web Part menu, and then click Modify Shared Web Part to open the tool pane.
4. In the tool pane, next to the Type box, click Browse.
5. In the Business Data Type dialog box, select a business data type for the business application that you are working with, and then click OK.
For example, select SalesOrder for the Business Data Type. In this example, the Application is AdventureWorksDWInstance.
6. From the Relationship drop-down list, select CustomerToSalesOrder.
7. In the tool pane, expand the Appearance section.
8. In Title box, replace Business Data Related List with Sales Orders for Customer, and then click OK.
9. For the Web Part that you just created, click the Web Part menu , point to Connections, point to Get Related Item From, and then click Customers from AdventureWorks.
Step 3: Verify that the Web Parts are properly connected and configured
1. On the same page that contains the List Web Part and the Related List Web Part that you just created, if no data appears in the Customers from AdventureWorks Related List Web Part, click Retrieve Data.
2. Select a customer from the list by clicking the option button next to the customer name. All sales orders related to the selected customer appear in the Sales Orders for Customer Web Part.
• Running Setup to Install AdventureWorks Sample Databases and Samples
• Creating a Database Connection by Using the Business Data Catalog Editor
• Display a summary of business data in a list
Running Setup to Install AdventureWorks Sample Databases and Samples
The AdventureWorks (OLTP), AdventureWorksDW (data warehouse), and Adventure Works DW (analysis services) sample databases, as well as the companion samples, are not installed by default in SQL Server 2005. You can download these from http://sqlserversamples.codeplex.com at Codeplex Center, or you can use the following procedures to install the sample databases and samples during or after setup. Additional instructions for deploying the Adventure Works DW analysis services project are also provided.
Installation during Setup
To install the sample databases and companion samples during setup, use the following instructions.
1. On the Components to Install page, select Workstation components, Books Online and development tools.
2. Click Advanced and then expand Documentation, Samples, and Sample Databases.
3. Select Sample Code and Applications.
4. Expand Sample Databases and then select the sample databases to install.
5. To complete the installation of the samples, after setup, perform one of the following steps:
1. From the Start menu, click All Programs, click Microsoft SQL Server 2005, click Documentation and Tutorials, click Samples, and then click Microsoft SQL Server 2005 Samples.
2. Alternatively, using Windows Explorer, navigate to
Installation after Setup
If you did not install the sample databases or samples during the initial setup of SQL Server 2005, you can install them later.
1. From Add or Remove Programs, select Microsoft SQL Server 2005 and click Change. Follow the steps in the Microsoft SQL Server 2005 Maintenance wizard.
2. From Component Selection, select Workstation Components and then click Next.
3. From Welcome to the SQL Server Installation Wizard, click Next.
4. From System Configuration Check, click Next.
5. From Change or Remove Instance, click Change Installed Components.
6. From Feature Selection, expand the Documentation, Samples, and Sample Databases node.
7. Select Sample Code and Applications.
8. Expand Sample Databases and then select the sample databases to be installed. Click Next.
9. To install and attach the sample databases, from Sample Databases Setup, select Install and attach sample databases, and then click Next.
The database files are created and stored in the folder
10. To install the sample database files without attaching, from Sample Databases Setup, select Install sample databases without attaching, and then click Next.
The AdventureWorks database files are created in the folder
11. Select the instance of SQL Server on which to install the sample databases and samples.
12. Complete the steps in the wizard.
13. To complete the installation of the samples, after setup, perform one of the following steps:
1. From the Start menu, click All Programs, click Microsoft SQL Server 2005, click Documentation and Tutorials, click Samples, and then click Microsoft SQL Server 2005 Samples.
2. Alternatively, using Windows Explorer, navigate to
Deploying the Adventure Works DW Analysis Services project
1. Make sure that the AdventureWorksDW and Adventure Works DW databases have been installed.
2. Make sure Analysis Services has been installed.
3. From the SQL Server Business Intelligence Development Studio toolbar, click File, point to Open, and then click Project/Solution.
4. Browse to
5. From Solution Explorer, right-click Adventure Works DW and select Deploy or Process.
Creating a Database Connection by Using the Business Data Catalog Definition Editor
The Business Data Catalog in Microsoft Office SharePoint Server 2007 exposes and incorporates line-of-business (LOB) data into other baseline portal functionality, such as lists and Enterprise Search. To incorporate this data into your portal site, and make it available to the Enterprise Search crawler, you must build an application definition file, which is an XML file that identifies where the data is stored (either in a database, or as a Web service) and what format the data is stored in (for example, what the data types and primary keys are).
The Microsoft Business Data Catalog Definition Editor helps you to author application definition files for the Business Data Catalog. This tool automatically generates the XML for the definition file, so you do not need to manually create the file in an XML editor.
This how-to topic shows you how to create an application definition file for the Business Data Catalog and how to create a database connection by using the new Business Data Catalog Definition Editor. This example uses the AdventureWorksDW sample database for Microsoft SQL Server 2005.
System Requirements
Before you begin, you must install the following:
• Microsoft Office SharePoint Server 2007, Enterprise Edition.
• Microsoft SQL Server 2005 with the AdventureWorksDW database installed.
• Microsoft Business Data Catalog Definition Editor.
Adding an LOB System
Begin by adding a LOB system for the AdventureWorksDW sample database for Microsoft SQL Server 2005.
To add an LOB system
1. On the Start menu, click Microsoft Business Data Application Definition Editor.
2. In the tool, click Add LOB System.
3. In the Add LOB System window, click Connect to Database.
4. Select SqlServer for Connection Type.
5. For Connection String, enter the following text.
Server={DATABASE_SERVER_NAME}\{INSTANCE_NAME};Database=AdventureWorksDW;Integrated Security=SSPI;
Replace {DATABASE_SERVER_NAME}\{INSTANCE_NAME} with the name of your database server.
6. Click Add Table.
7. Drag the following tables to the Design Surface:
o Product
o ProductCategory
o ProductSubcategory
o Reseller
8. In the Foreign Keys section of the DimProduct window, select FK_DimProduct_DimProductSubcategory.
9. Click OK.
10. In the LOB System Name dialog box that opens, click OK to create the AdventureWorksDW connection.
Testing the AdventureWorksDW LOB System Connection
Next, test the connection to the AdventureWorksDW LOB system.
To test the connection to the LOB system
1. In the Metadata Objects pane, expand the AdventureWorksDW node, and then expand the Entities node.
2. Expand the DimProduct node.
3. Expand the Methods node
4. Expand the FindAll_DimProducts node, and then expand the Instances node.
5. Right-click FindAll_DimProduct_Instance, and then click Execute.
6. In the Execute FindAll_DimProduct_Instance window, click Next, and verify that the values from the ProductKey field of the DimProducts table are displayed in the Results window. Click Next to page through the results.
7. Make note of one of the ProductKey values for the next step. For this walkthrough, we use the ProductKey value 212.
8. In the Methods node, expand the Find_DimProduct node, and then expand the Instances node.
9. Right-click Find_DimProduct_Instance, and then click Execute.
10. In the Value field, enter the 212, and then click Execute.
11. If the DimProduct table contains any fields that will not display correctly, you might receive a message, Click OK to close the message and continue.
12. If the Find method is working correctly, the record with the ProductKey field matching 212 appears in the Results window.
Testing the Entity Associations
Now you will test the entity associations for the LOB system.
To test the entity associations
1. In the DimProducts node, expand the Methods node, and then expand the FK_DimProduct_DimProductSubcategory node.
2. Expand the Instances node.
3. Right-click FK_DimProduct_DimProductSubcategory_Instance, and then click Execute to open the Execute FK_DimProduct_DimProductSubcategory_Instance window.
4. Click the Search button or click anywhere in the Value field to open the Select Entity Instance window.
5. Select FindAll_DimProductSubcategory_Instance, and then click Next to display the first page of results.
6. Select the row for the record from the DimProductSubcategory table you want to retrieve the associations for, and then click OK. If the record is not displayed in the first set of results, click Next to page through the results. For this example, select the record with the ProductSubcategoryKey 31.
7. In the Execute FK_DimProduct_DimProductSubcategory_Instance window, click Execute to display all the records from the DimProduct table where the ProductSubcategoryKey field matches 31.
If results are returned, the associations are configured correctly.
Exporting the LOB System Instance Metadata
After you confirm that the connection for the LOB system and with the entities, associations, and methods, are configured correctly within the Business Data Catalog Definition Editor, you are ready to export the LOB system instance metadata to an application definition file.
To export the metadata
1. Select the AdventureWorksDW node in the Metadata Objects window, and then click Export.
2. Save the file as AdventureWorks2005.xml.
Importing the Application Definition File into the Shared Services Provider
Next, you import the application definition file into the Shared Services Provider (SSP).
To import the application definition file into the SSP
1. To start the SharePoint 3.0 Central Administration Web page, click Start, and then point to All Programs. Point to Microsoft Office Server, and then click SharePoint 3.0 Central Administration.
2. In the left navigation pane, click the name of your SSP.
3. In the Business Data Catalog section, click Import application definition.
4. In the Import Application Definition page that opens, browse to AdventureWorks2005.xml, select the file, and then click Open.
5. Click Import.
6. Click Browse, locate the file, and double-click it.
7. Leave all other application definition settings with their default values, and then click Import.
Modifying an Existing Application Definition by using the Business Data Catalog Definition Editor
You can also modify the metadata in an existing application definition file by importing it into the Business Data Catalog Definition Editor. If you are modifying the application definition for an existing application in the Business Data Catalog, you must export the metadata file for the application definition from the SSP first.
To export the application definition file from the SSP
1. To start the SharePoint 3.0 Central Administration Web page, click Start, and then point to All Programs. Point to Microsoft Office Server, and then click SharePoint 3.0 Central Administration.
2. In the left navigation pane, click the name of your SSP.
3. In the Business Data Catalog section, click View applications.
4. In the Applications list, click the application name.
5. Click Export Application Definition to open the Export Application Definition page.
6. Click Export, and then click Save.
To import an application definition file into the Business Data Catalog Definition Editor and modify the metadata
1. On the Start menu, click Microsoft Business Data Catalog Application Definition Editor.
2. Click Import.
3. Browse to the location of the application definition file, select it, and then click Open.
After the LOB system is loaded into the Business Data Catalog Definition Editor, you can make several changes to the LOB system instance, such as:
o Connection string
o Authentication mode
o Add or remove entities
Display a summary of business data in a list
You can display business data from an external database in a simple list form by using the Business Data List Web Part. For example, you can display a list of products and their list prices.
After the data appears, you can edit the view properties of a Business Data List Web Part, just as you can edit the view of any SharePoint list. You can also filter by property or limit the number of items shown in the Web Part.
1. Go to the page on the SharePoint site where you want to display a list of business data.
2. On the Site Actions menu, click Edit Page.
3. In the Web Part zone where you want to add the Web Part, click Add a Web Part.
4. In the Add Web Parts dialog box, select the Business Data List check box, and then click Add.
5. From the business data Web Part that you just created, click the Web Part menu, and then click Modify Shared Web Part to open the tool pane.
6. In the tool pane, next to the Type box, click Browse.
7. In the Business Data Type dialog box, select a business data type for the business application that you are working with, and then click OK.
For example, select Product. In this example, the Application is AdventureWorksDWInstance.
8. In the tool pane, expand the Appearance section.
9. In the Title box, replace Business Data List with your own title for the Web Part, and then click OK.
For example, type Product List in the Title box.
10. From the newly added Web Part, click Edit View, and then do the following:
• In the Items to Retrieve section, select Retrieve all items.
• In the Columns section, select the names of the columns that you want to display in the Web Part.
11. Click OK.
The new Business Data List Web Part now displays a list of products from your business application database.
Display details about a single item of business data
You can display the details about a business item from an external database by using the Business Data Item Web Part. For example, you can display the details about a particular product from the business application database.
1. Go to the page on the SharePoint site where you want to display the details about a particular business item.
2. On the Site Actions menu, click Edit Page.
3. In the Web Part zone where you want to add the Web Part, click Add a Web Part.
4. In the Add Web Parts dialog box, select the Business Data Item check box, and then click Add.
5. From the business data Web Part that you just created, click the Web Part menu, and then click Modify Shared Web Part to open the tool pane.
6. In the tool pane, next to the Type box, click Browse.
7. In the Business Data Type dialog box, select a business data type for the business application that you are working with, and then click OK.
For example, select Product for the Business Data Type. In this example, the Application is AdventureWorksDWInstance.
8. Next to the Item box, click Browse to choose the product that you want to display.
9. In the dialog box that appears, the first drop-down list displays the filters that are defined for this entity in the BDC. Click the Name filter. In the adjacent field, type a product category, such as Bike, that you want to find. Click Search to search for product names that contain the category that you entered.
10. Select one item from the list of products that appears, and then click OK. The ID of the item that you selected is now displayed in the Item box in the tool pane.
11. Under Fields, click the Choose button.
12. In the Select Fields dialog box, select the item information that you want to display, and then click OK.
13. In the tool pane, expand the Appearance section.
14. In the Title box, replace Business Data Item with your own title for the Web Part, and then click OK.
For example, type Featured Product in the Title box.
The new Business Data Item Web Part displays the product details from your business application database.
Connect Web Parts to configure business application actions
By using a Business Data Actions Web Part on your SharePoint site, you can add an action to a product profile that enables you to perform a search for that item on MSN without leaving Office SharePoint Server 2007. The Business Data Actions Web Part displays a list of actions, in the form of links or on a toolbar, that are associated with a business item in the BDC.
Step 1: Add and connect a Business Data Actions Web Part
In this procedure, you add an action to a Business Data Actions Web Part and connect the Web Part to the Product List Web Part that you created earlier in Display a summary of business data in a list.
Before you begin, your administrator must download the AdventureWorksDW SQL Server 2005 Sample database and register it with the BDC. Additionally, your administrator must define the Search on MSN business data action and add it to Office SharePoint Server 2007. Find more information about the AdventureWorksDW SQL Server 2005 Sample database in the See Also section.
You must first have the Full Control or Design permission level before you can modify the Web Parts on your SharePoint site. Find links to more information about permission levels and permissions in the See Also section.
1. Go to the page on the SharePoint site where you created the Product List Web Part.
2. On the Site Actions menu, click Edit Page.
3. In the Web Part zone where you want to add the Web Part, click Add a Web Part.
4. In the Add Web Parts dialog box, select the Business Data Actions check box, and then click Add.
5. From the business data Web Part that you just created, click the Web Part menu, and then click Modify Shared Web Part to open the tool pane.
6. In the tool pane, next to the Type box, click Browse.
7. In the Business Data Type dialog box, select a business data type for the business application that you are working with, and then click OK.
For example, select Product for the Business Data Type. In this example, the Application is AdventureWorksDWInstance.
8. Under Actions, click Choose.
9. In the Select Actions dialog box, select the Display check box for the Search on MSN action, and then click OK.
The View Profile check box should be selected by default. The View Profile action is automatically created for each entity (or business item) that is defined in the BDC. This action enables you to view details about the entity. Because actions are associated with entities, the actions appear wherever the entity is displayed on a SharePoint site.
10. In the tool pane, configure the Web Part as needed in the Appearance, Layout, and Advanced sections, and then click OK to close the tool pane.
11. For the Business Data Actions Web Part that you just created, click the Web Part menu , point to Connections, point to Get Item From, and then click Product List.
If a message appears under the Product Actions Web Part that notifies you of a conflict in connecting the Product Actions Web Part to the Product List Web Part, verify that the Web Parts are both using the AdventureWorksDWInstance sample database.
Step 2: Verify that the Web Parts are properly connected and configured
1. If no data appears in the Product List Web Part, click Retrieve Data.
2. Select an item from the list by clicking the option button next to the product key.
3. In the Product Actions section of the site, click Search on MSN. A new window appears displaying search results for the item selected.
Connect Web Parts to display related business items
You can use the Business Data Related List Web Part along with a Business Data List Web Part to display two lists of related business items from a business application. For example, you can connect the two Web Parts to display all the sales orders for a specific customer.
• Business Data List Web Part
• Business Data Related List Web Part
The following procedure uses fictitious customer data from the AdventureWorks SQL Server 2000 Sample database, which must first be downloaded and registered with the BDC. Find more information about the AdventureWorks SQL Server 2000 Sample database in the See Also section.
Step 1: Create a Web Part to display a summary list
The first step in displaying related data from an external database is to create a Business Data List Web Part to display a summary list of customers.
1. Go to the page on the SharePoint site where you want to display orders for a specific customer in the database.
2. On the Site Actions menu, click Edit Page.
3. In the Web Part zone where you want to add the Web Part, click Add a Web Part.
4. In the Add Web Parts dialog box, select the Business Data List check box, and then click Add.
5. From the business data Web Part that you just created, click the Web Part menu, and then click Modify Shared Web Part to open the tool pane.
6. In the tool pane, next to the Type box, click Browse.
7. In the Business Data Type dialog box, select a business data type for the business application that you are working with, and then click OK.
For example, select Customer for the Business Data Type. In this example, the Application is AdventureWorksDWInstance.
8. In the tool pane, expand the Appearance section.
9. In Title box, replace Business Data List with Customers from AdventureWorks, and then click OK.
Step 2: Create and connect a Web Part to display related items
After you create a Business Data List Web Part that can display customers from the AdventureWorks SQL Server 2000 Sample database, you can create a Business Data Related List Web Part that connects to the first list. The end result will allow you to select an item from the customer list and view a list of sales orders for that customer in the Business Data Related List Web Part.
1. On the same page where you created the Business Data List Web Part, click Add a Web Part to create a new Web Part on the page.
2. In the Add Web Parts dialog box, select the Business Data Related List check box, and then click Add.
3. From the business data Web Part that you just created, click the Web Part menu, and then click Modify Shared Web Part to open the tool pane.
4. In the tool pane, next to the Type box, click Browse.
5. In the Business Data Type dialog box, select a business data type for the business application that you are working with, and then click OK.
For example, select SalesOrder for the Business Data Type. In this example, the Application is AdventureWorksDWInstance.
6. From the Relationship drop-down list, select CustomerToSalesOrder.
7. In the tool pane, expand the Appearance section.
8. In Title box, replace Business Data Related List with Sales Orders for Customer, and then click OK.
9. For the Web Part that you just created, click the Web Part menu , point to Connections, point to Get Related Item From, and then click Customers from AdventureWorks.
Step 3: Verify that the Web Parts are properly connected and configured
1. On the same page that contains the List Web Part and the Related List Web Part that you just created, if no data appears in the Customers from AdventureWorks Related List Web Part, click Retrieve Data.
2. Select a customer from the list by clicking the option button next to the customer name. All sales orders related to the selected customer appear in the Sales Orders for Customer Web Part.
Friday, August 6, 2010
How to create Auto-numbering InfoPath form with custom approval workflow in SharePoint 2007 environment Lab
We will walk through three main steps in order to complete this Lab:-
Create Auto-numbering InfoPath form
You can accomplish this functionality as follows:
1. In SharePoint, create a form library to submit your forms to.
Content Approval Workflow Scenario
The approval process is initiated when a user or author creates a new document and saves the document to a SharePoint document library (or uploads a new document). Individuals responsible for approving the content are notified by e-mail that there is new content pending approval, and confirmation is also sent automatically to the author. At this point in the process, a delay is introduced into the workflow due to the time it takes for an approver to review the material and decide whether to accept or reject. The approver downloads and reviews the content. After review, the content is either accepted or rejected. Based on the reviewer's response, the workflow can follow two different parallel paths:
• If approved, then the document is moved from its current location to a different document library for published content. An e-mail is sent to the author and approvers notifying them that the document has been approved.
• If the content is rejected, then the document is moved to another document library and the author and approvers are notified electronically.
Regardless of the path, the workflow terminates once notification has completed.
Creating the Content Approval Workflow
The following is a step-by-step walkthrough for creating a custom workflow that models the business process outlined in above Figure.
This walkthrough introduces you to the concept of creating a custom workflow using SharePoint Designer. You are encouraged to walk through this exercise on your own:
1. Create two new document libraries and name them Published, and Rejected. For the Submitted document library we created it before and add the InfoPath form to it, enable "Require content approval for submitted items" (from the Versioning Settings page).
2. Open SharePoint Designer. Close any site that may be open using the File ➪ Close Site command.
3. Open your Developers Team Site by choosing File ➪ Open Site. Inside of the Open Site dialog, enter the URL of your team site for the Site Name and click Open.
4. Open the Workflow Designer dialog by selecting File ➪ New ➪ Workflow. Assign the name Publishing to the workflow. Attach the workflow to the Submitted list. Enable "Automatically start this workflow when a new item is created" and disable all other start options. The result, with the Workflow Designer dialog showing the initial configuration for the Publishing workflow, Click Next.
5. Assign the name Launch and Wait to the Step Name.
6. From Conditions, select Compare Submitted Field. Assign Field to Approval Status and Value to Pending. From the Actions menu, choose Send an email. Click this message hyperlink to open the Define Email Message dialog. Click the address book icon at the end of the To: line to open the Select Users dialog. Select the Approvers group and add it to Selected Users. Add the user who created the current item to the CC: line using a similar process. Fill out the e-mail appropriately or leave it blank and then click OK.
7. From Actions, select More Actions and then select "Wait for field change in current item" and click Add. Assign Field to Approval Status. Change the "to equal" phrase to "not equal" and assign Value to Pending. This completes the Launch and Wait step.
8. Under Workflow Steps, click the Add Workflow Step hyperlink. Assign the name Review and Routing for step 2.
9. From the Conditions option, choose Compare Submitted Field. Click the Field hyperlink and select Approval Status. Click the Value hyperlink and select Approved.
10. From Actions, select Copy list item. Click the "first this list" hyperlink and select Current Item. Click the "second this list" hyperlink and choose Published.
11. From Actions, select Delete Item. You may need to choose More Items in order to see this option. Click the "this list" hyperlink, select "current item," and click OK.
12. From Actions, select Send an email. Click the "this message" hyperlink and fill out the e-mail. Send an e-mail to the user who created the current item and CC: the Approvers group.
13. Click the Add 'Else If' Conditional Branch hyperlink.
14. Add the Compare Submitted Field condition for the second condition. Assign Field to Approval Status, and Value to Rejected.
15. From Actions, select Copy list item. Assign the first "this list" to Current Item and the second to Rejected.
16. Add an action to delete the current item.
17. Add an action to Send an e-mail to the item creator stating that their document has been rejected and CC: the Approvers group. This completes the Review and Routing step.
18. Click Finish. As described previously, workflows authored using SharePoint Designer are automatically deployed and bound to the specific list during creation. The dialog will confirm that the Publishing workflow has been deployed and associated with the Submitted document library and that no instances have been created.
If you are going to utilize the e-mail capability from SharePoint Designer workflow, make sure that you have configured an e-mail server as part of your SharePoint deployment. If not, the workflow may have problems and not function as intended.
19. Navigate to the Submitted documents library. Create a new document and save it with the name First Document to the Submitted document library. Add some example text if you wish, such as this is a test of a new workflow. Close Word.
20. View the newly created document item in the Submitted library. Notice that the Approval Status of First Document is pending because you enabled content approval (back in step 2). Also notice that the Publishing column contains In Progress, indicating that an instance of the Publishing workflow has been created. Navigate to the Workflow Settings page of the Submitted document library to confirm that one instance has been created and is currently running.
21. Approve First Document by hovering the mouse over the item inside of the Submitted document library, clicking the drop-down arrow to reveal the context menu, choosing Approve/Reject, and then approving the content in the subsequent pages.
22. Once the document has been approved, confirm that the document is moved to the Published document library.
23. Repeat the process with a second document but this time reject the content to demonstrate that the created document is moved to the Rejected document library.
24. As an exercise, view the e-mails sent to the author after the document is submitted and approved or rejected. In addition, you can add users to the Approvers group and review the corresponding e-mail communication.
- Create Auto-numbering InfoPath form
- Publish InfoPath form to SharePoint Library as Content Type
- Creating Custom Workflows for Office SharePoint 2007
Create Auto-numbering InfoPath form
You can accomplish this functionality as follows:
1. In SharePoint, create a form library to submit your forms to.
2. In InfoPath, create a new (browser-compatible) InfoPath form template.
3. Add a Text Box control to the form template and name it autonumber.
4. On the Tools menu, click Data Connections.
5. On the Data Connections dialog box, click Add, and create a Receive data connection to the SharePoint library that you created in step 1. In step 5 of the data connection wizard, uncheck all fields and then check the ID field. In the last step of the data connection wizard, uncheck Automatically retrieve data when form is opened, name the data connection RetrieveIDs, and click Finish.
6. On the Data Connections dialog box, click Add, and create a Submit data connection to the SharePoint library that you created in step 1. In step 3 of the data connection wizard, click the formula button behind the File name field.
7. On the Insert Formula dialog box, type max( and then click Insert Field or Group.
8. On the Select a Field or Group dialog box, select RetrieveIDs from the Data source drop-down list box, expand all the nodes, click ID, and then click OK.
9. On the Insert Formula dialog box, type ) + 1 and click OK.
10. On the Data Connection Wizard dialog box, the expression in the File name field should resemble: max(@ID) + 1
11. On the Data Connection Wizard dialog box, click Next, name the data connection Main submit, and then click Finish.
12. On the Data Connections dialog box, click Close.
13. On the Tools menu, click Submit Options.
14. On the Submit Options dialog box, check the Allow users to submit this form checkbox, select the Perform custom actions using rules option, click Advanced, select Close the form from the After submit drop-down list box, and then click Rules.
15. On the Rules dialog box, click Add.
16. On the Rule dialog box, add an Action that says: Query using data connection: RetrieveIDs
17. On the Rule dialog box, add a second Action that says: Set a field's value: autonumber = max(@ID) + 1 Note: @ID is selected from the RetrieveIDs secondary data source in the same way you selected it in step 8.
18. On the Rule dialog box, add a third Action that says: Submit using data connection: Main submit
19. Click OK when closing all dialog boxes that are currently open.
20. Publish the form template to the library you created in step 1.You should now be able to fill out a form and submit it. The next available number in the form library will be automatically saved in the autonumber field of the form when the form is submitted and this number will also be used for the Name of the form. This solution works for both forms that are filled out through the InfoPath client application as well as those that are filled out through the browser.
Publish InfoPath form to SharePoint Library as Content Type
1- From the file menu, select Publish, you will be prompted to save the form template locally if you have not done so. You are required to do this to be able to publish the form template to SharePoint.
2- Select "To a SharePoint server With or Without InfoPath Form Services" when asked where to publish the form template.
3- Enter the URL of your SharePoint Server, Example "http://SharePointServer/"
4- Select the publish method: "Site Content Type"
5- Select "Create a new Content Type"
6- Enter a name for the content type
7- When asked to specify a location for the form template, enter the URL of the library created in the first step, press Next.
8- Press "Add..", and select the " autonumber " field from the list
9- Repeat for the second field
10- Press "Next"
11- Press "Ok" to close
Now Add and Set the Content Type as the Form Library's Default
1- Using the browser, navigate to the SharePoint Form library created in the second step.
2- From the "Settings" dropdown menu for the library, select "Forms Library Settings"
3- Under the General Setting heading, click "Advanced Settings"
4- Select "Yes" to Allow management of content types
5- Press OK
6- Under the Content Types section of the Library Settings page, select "Add from existing site content types"
7- Add the newly created content type from the form library, press OK
8- You can either remove the default "Document" content type from the library or set the new content type as the default to allow a blank form to be opened in a browser or InfoPath when the "New" button is pressed on the form library.
When a new form is submitted, it will be submitted to the specified SharePoint form library, with data from the fields in the InfoPath form being mapped to Columns in the library.
Creating Custom Workflows for Office SharePoint Server 2007
One of the most common human workflow scenarios is related to content approval. Below figure shows a flowchart describing an approval and routing business process. This scenario can be represented by a custom workflow. Before we walk through creating the workflow, we'll discuss the overall process.
Content Approval Workflow Scenario
The approval process is initiated when a user or author creates a new document and saves the document to a SharePoint document library (or uploads a new document). Individuals responsible for approving the content are notified by e-mail that there is new content pending approval, and confirmation is also sent automatically to the author. At this point in the process, a delay is introduced into the workflow due to the time it takes for an approver to review the material and decide whether to accept or reject. The approver downloads and reviews the content. After review, the content is either accepted or rejected. Based on the reviewer's response, the workflow can follow two different parallel paths:
• If approved, then the document is moved from its current location to a different document library for published content. An e-mail is sent to the author and approvers notifying them that the document has been approved.
• If the content is rejected, then the document is moved to another document library and the author and approvers are notified electronically.
Regardless of the path, the workflow terminates once notification has completed.
Creating the Content Approval Workflow
The following is a step-by-step walkthrough for creating a custom workflow that models the business process outlined in above Figure.
This walkthrough introduces you to the concept of creating a custom workflow using SharePoint Designer. You are encouraged to walk through this exercise on your own:
1. Create two new document libraries and name them Published, and Rejected. For the Submitted document library we created it before and add the InfoPath form to it, enable "Require content approval for submitted items" (from the Versioning Settings page).
2. Open SharePoint Designer. Close any site that may be open using the File ➪ Close Site command.
3. Open your Developers Team Site by choosing File ➪ Open Site. Inside of the Open Site dialog, enter the URL of your team site for the Site Name and click Open.
4. Open the Workflow Designer dialog by selecting File ➪ New ➪ Workflow. Assign the name Publishing to the workflow. Attach the workflow to the Submitted list. Enable "Automatically start this workflow when a new item is created" and disable all other start options. The result, with the Workflow Designer dialog showing the initial configuration for the Publishing workflow, Click Next.
5. Assign the name Launch and Wait to the Step Name.
6. From Conditions, select Compare Submitted Field. Assign Field to Approval Status and Value to Pending. From the Actions menu, choose Send an email. Click this message hyperlink to open the Define Email Message dialog. Click the address book icon at the end of the To: line to open the Select Users dialog. Select the Approvers group and add it to Selected Users. Add the user who created the current item to the CC: line using a similar process. Fill out the e-mail appropriately or leave it blank and then click OK.
7. From Actions, select More Actions and then select "Wait for field change in current item" and click Add. Assign Field to Approval Status. Change the "to equal" phrase to "not equal" and assign Value to Pending. This completes the Launch and Wait step.
8. Under Workflow Steps, click the Add Workflow Step hyperlink. Assign the name Review and Routing for step 2.
9. From the Conditions option, choose Compare Submitted Field. Click the Field hyperlink and select Approval Status. Click the Value hyperlink and select Approved.
10. From Actions, select Copy list item. Click the "first this list" hyperlink and select Current Item. Click the "second this list" hyperlink and choose Published.
11. From Actions, select Delete Item. You may need to choose More Items in order to see this option. Click the "this list" hyperlink, select "current item," and click OK.
12. From Actions, select Send an email. Click the "this message" hyperlink and fill out the e-mail. Send an e-mail to the user who created the current item and CC: the Approvers group.
13. Click the Add 'Else If' Conditional Branch hyperlink.
14. Add the Compare Submitted Field condition for the second condition. Assign Field to Approval Status, and Value to Rejected.
15. From Actions, select Copy list item. Assign the first "this list" to Current Item and the second to Rejected.
16. Add an action to delete the current item.
17. Add an action to Send an e-mail to the item creator stating that their document has been rejected and CC: the Approvers group. This completes the Review and Routing step.
18. Click Finish. As described previously, workflows authored using SharePoint Designer are automatically deployed and bound to the specific list during creation. The dialog will confirm that the Publishing workflow has been deployed and associated with the Submitted document library and that no instances have been created.
If you are going to utilize the e-mail capability from SharePoint Designer workflow, make sure that you have configured an e-mail server as part of your SharePoint deployment. If not, the workflow may have problems and not function as intended.
19. Navigate to the Submitted documents library. Create a new document and save it with the name First Document to the Submitted document library. Add some example text if you wish, such as this is a test of a new workflow. Close Word.
20. View the newly created document item in the Submitted library. Notice that the Approval Status of First Document is pending because you enabled content approval (back in step 2). Also notice that the Publishing column contains In Progress, indicating that an instance of the Publishing workflow has been created. Navigate to the Workflow Settings page of the Submitted document library to confirm that one instance has been created and is currently running.
21. Approve First Document by hovering the mouse over the item inside of the Submitted document library, clicking the drop-down arrow to reveal the context menu, choosing Approve/Reject, and then approving the content in the subsequent pages.
22. Once the document has been approved, confirm that the document is moved to the Published document library.
23. Repeat the process with a second document but this time reject the content to demonstrate that the created document is moved to the Rejected document library.
24. As an exercise, view the e-mails sent to the author after the document is submitted and approved or rejected. In addition, you can add users to the Approvers group and review the corresponding e-mail communication.
Overview and configuring Unified Messaging 2007 in Office Communications Server 2007 environment
Introducing Unified Messaging in Office Communications Server 2007 environment
The Unified Messaging component of Exchange 2007 SP1 is the designed to be the voice mail solution for Office Communications Server 2007 (OCS). What it means is that anyone can dial an Office Communications Server user and leave a voice mail which will then be delivered to that user's Outlook inbox. The integration of Office Communication Server 2007 and Exchange 2007 Unified Messaging will take users closer to the vision Microsoft has for Unified Communications.
http://www.microsoft.com/presspass/exec/jeff/06-26-06UnifiedCommunications.mspx
For an enterprise with Office Communications Server 2007, the integration of Unified Messaging (hence Exchange 2007) will give enterprise users the added benefit of having e-mail, voice mail, and fax messages consolidated in their inbox. Moreover, certain voice mail features can now be accessed using Office Communicator clients. The Unified Messaging role must be deployed with Exchange 2007 service pack 1 to support this integration.
In an integrated environment when a call to a person is not answered (busy, ring no answer, or diverted to voice mail) it gets routed to the Unified Messaging server (UM). The front end server role of OCS (or the Director) is responsible for processing and routing the call to the UM server.
Clients for OCS can be one of the following:
• Office Communicator (OC)
• OC qualified IP phone device
These clients are also known as Unified Communications Clients or UC Clients. Any user in Active Directory (AD) will have to be enabled and configured for voice capability to talk to the OCS server. The same client will also have to be enabled for Unified Messaging to divert their missed call to the UM server.
Common Scenarios
Following are some of the common scenarios where a call will route through OCS as well as UM. In each of these scenarios the users are enabled for Office Communications as well as Unified Messaging.
Divert to Voice Mail
User A calls User B, who does not answer. The call is then diverted to the UM server by OCS. Exchange UM plays a greeting previously recorded by User B, after which User A records a message. User B receives the voice mail message in their e-mail inbox with contextual information (additional contact information, phone numbers, title) provided in the body of the voice mail message. Callers can are identified through Active Directory or from User B's personal address book in Outlook. Finally, Outlook and Outlook Web Access both display this message along with an embedded player to play the voice message.
Subscriber Access
User A logs on using Office Communicator and selects the option to call voice mail. Since the user is already authenticated through Office Communicator, UM will not require the user to enter their PIN. Exchange UM will play the prompts for voice mail, e-mail, and calendar in Outlook Voice Access, all of which is pulled from User A's mailbox. User A selects to listen to their voice mail.
Auto-Attendant
User A does not know User B's direct line or extension, so User A calls the public access number for User B's organization. User B is connected to the Exchange UM Automated Attendant, which offers various options, including a corporate directory. User A says User B's name verbally, which is recognized by the Automated Attendant and User A's call is transferred to User B's extension in the organization.
Better Together
Integration of OCS and UM gives users a seamless experience to communicate across their entire organization. A UC client has the option to do instant messaging, audio-video conversations, conferencing, and access to all UM functionality from their UC client.
The following are some of the key features of this experience:
• Provides a single authentication method – A user who has logged into Office Communicator does not need to enter their PIN when they check their voice mail from the Office Communicator interface.
• Maintain subject name and priority - An OC user can add subject and priority when making a call. If the call gets diverted to UM, the subject is added to the subject line of the message containing the voice mail or the missed call notification. Additionally, the priority of the original call is maintained by UM in the auto-generated notification for missed calls or new voice mails.
• Integrated missed call notifications - When a call is missed by the receiving party, UM will generate an e-mail notification for the missed call and place it in the inbox for the receiving party.
• Both missed calls and voice mails show the name and contact information for the calling party user. This information is retrieved through Active Directory or from the called party user's personal contact list.
• Traversing the firewall - Media streams can be traversed through the corporate firewall securely without complicated configurations.
• High fidelity voice quality - UM now supports high fidelity codecs for voice mail recording and play back.
E.164 Number Format
The format of the telephone number associated with the UC-enabled user is E.164 (example: +19805551234). Therefore, if a user enters a number that is in different format (example: extension 1234) it has to be manipulated into the E.164 format. OCS will take this number and search the corporate directory to find the user who has a matching number and then voice mail will be routed to the correct user. OCS uses normalization rules to translate these number formats and uses an internal translation service to perform canonicalization transformation. Stay tuned for future blog post on this topic.
A Simple Scenario
In this scenario User A makes a call to user B using Office Communicator. User B does not answer and the call is forwarded to voice mail. User A hears the mailbox greeting and leaves a voice mail for User B.
Call Flow
The following is the call flow for the above scenario:
1. When User A makes a call to User B, the request is first sent to the OCS front end server as a SIP INVITE. OCS will first try to find the target user (User B) in AD and determine whether User B is OC-enabled. If the user is OC-enabled, the call will be forwarded to the registered SIP endpoint for User B. OCS will send the request as a SIP INVITE.
2. If User B does not answer the call, a response message will be sent back to OCS server indicating that User B did not answer the call.
3. OCS will query AD to find out if User B is UM-enabled, and if so, will extract out information such as their proxy address, dial plan name, and the UM server(s) assigned to the dial plan. OCS will use its routing logic to determine the appropriate UM server to route the call to.
4. A new INVITE request will be sent to the UM server by the OCS server. In this new INVTIE request, User B's SIP address will be added as a diversion header indicating that this is a voice mail call for User B.
5. A new session will be created between OCS and UM. OCS will exchange media information with UM and indicate that the RTP end point is the IP address of User A. After media negotiation is done, UM will establish a RTP session with User A and play prompts for leaving a voice mail. User A will directly communicate with UM and leave a voice mail for User B.
6. The remainder of the communication remains the same for any Exchange 2007 environment. After the voice mail is received by UM, it will be handed it off to a hub-transport server which will in turn route the voice mail to the user's mailbox on the appropriate mailbox server.
Configuring Unified Messaging and Office Communications Server 2007
Microsoft Exchange Server 2007 Unified Messaging and Microsoft Office Communications Server 2007 can be deployed together to provide voice messaging, Instant Messaging (IM), enhanced user presence, audio-video conferencing, and an integrated e-mail and messaging experience for users in your organization. This topic discusses how to configure Exchange 2007 Unified Messaging and Communications Server 2007 to support these features.
Deploying Exchange Unified Messaging and Communications Server 2007
Exchange 2007 Unified Messaging combines voice messaging and e-mail messaging into a single messaging infrastructure. Communications Server 2007 Enterprise Voice takes advantage of the Unified Messaging infrastructure to provide voice mail, subscriber access, call notification, and auto attendant services.
Before you can implement these services or features, you must do the following:
• Install Communications Server 2007 in the same Active Directory directory service topology as the Unified Messaging servers.
• Deploy the following Exchange 2007 server roles:
• Unified Messaging server role The Unified Messaging server connects Exchange 2007 with Communications Server 2007.
• Hub Transport server role The Hub Transport server routes e-mail messages from the Unified Messaging server to user mailboxes.
• Client Access server role The Client Access server hosts client protocols, such as Post Office Protocol 3 (POP3), Internet Message Access Protocol 4 (IMAP4), Secure Hypertext Transfer Protocol (HTTPS), Outlook Anywhere (formerly known as RPC over HTTP), the Availability service, and the Autodiscover service. The Client Access server also hosts Exchange Web services.
• Mailbox server role The Mailbox server hosts user mailboxes.
• Install Exchange 2007 Service Pack 1 (SP1) on the computers that have the Unified Messaging server role installed.
• Install and configure Communications Server 2007 in your organization, as follows:
1. Install Communications Server 2007 on servers in your organization.
2. Install a valid certificate that is valid and signed by a certification authority on the Communications Server 2007 servers.
3. Make sure that the certificate that you installed on the Communications Server 2007 servers is trusted by the Unified Messaging servers.
4. Confirm that at least one Communications Server 2007 pool object is created during installation.
Certificate Configuration Recommendations
You must have a certificate that is trusted by both the computers that are running Microsoft Exchange and Office Communications Server 2007. In an environment that has Office Communications Server 2007 and Exchange 2007 Unified Messaging, use the following guidelines for deploying a trusted certificate:
• Import a certificate that is valid and signed by a certification authority (CA). This should be a trusted third-party commercial certificate or a public key infrastructure (PKI) certificate and should be imported on the Communications Server 2007 computers and the Exchange servers that have the Unified Messaging and Client Access server roles installed.
• The most simple certificate deployment scenario is to import the same third-party commercial or PKI certificate to each Exchange 2007 server that has the following server roles installed: Unified Messaging, Client Access, and Hub Transport. Also install this trusted certificate on each computer that is running Office Communications Server 2007. This will help simplify your certificate deployment and reduce the administrative overhead associated with deploying certificates. However, you must obtain a trusted certificate that supports Subject Alternative Names (SANs).
• Although you can install the Unified Messaging server role and other Exchange 2007 server roles on the same computer, when you are deploying Communications Server 2007 we recommend that you install the Unified Messaging server role on a computer that will not be running other Exchange 2007 server roles. If another server role is installed on the same computer as the Unified Messaging server role, the Microsoft Exchange Unified Messaging service may select the incorrect certificate and be unable to use mutual TLS to encrypt traffic. This occurs because of limitations with subject alternative names found in certificates.
For example, if you install the Unified Messaging server role first, and then later install the Client Access server role on the same server, the Microsoft Exchange Unified Messaging service will use the certificate that is created by the Client Access server role instead of the certificate that was created when the Unified Messaging server role was installed. This is because the Microsoft Exchange Unified Messaging service looks for the certificate in the Trusted Root Store that has the most time left before it will expire.
• Because the trusted certificate uses mutual TLS to establish an encrypted channel with Communications Server 2007, Client Access, Hub Transport, and Unified Messaging servers, the name on the certificate that is used during mutual TLS negotiation must match the fully qualified domain name (FQDN) of the server that presents the certificate.
Deployment Path
After you have installed the required server roles in your Exchange 2007 organization, there is a recommended sequence of steps that you must perform on the Exchange UM environment and in your Communications Server 2007 environment to correctly deploy Enterprise Voice and Exchange 2007 Unified Messaging. Exchange 2007 Unified Messaging is used to provide call answering, Outlook Voice Access, and auto attendant services. Communications Server 2007 enables more advanced features that are found in Enterprise Voice services. The following figure illustrates the recommended deployment path for implementing Enterprise Voice services found with Exchange 2007 Unified Messaging and Communications Server 2007.
Deploying Exchange 2007 Unified Messaging and Office Communications Server 2007
There are several steps that you must complete to configure Exchange 2007 Unified Messaging to work with Enterprise Voice in Communications Server 2007. You must do the following:
1. Create one or more Exchange 2007 Unified Messaging Session Initiation Protocol (SIP) URI dial plans that each map to a corresponding Communications Server 2007 location profile. An Enterprise Voice location profile must be created for each Exchange UM dial plan. The location profile name has to match the fully qualified domain name (FQDN) of the UM dial plans. The Unified Messaging dial plan FQDN is used as the name of its corresponding location profile. Use the Get-UMDialPlan cmdlet to obtain the FQDN of a SIP URI dial plan, and then create its corresponding location profile.
2. Install a certificate on the Unified Messaging servers that is valid and signed by a certification authority, and then restart the Microsoft Exchange Unified Messaging service on each Unified Messaging server.
3. To encrypt the VoIP traffic, configure the SIP URI dial plan as SIP secured or Secured.
Although a Unified Messaging dial plan can be configured as SIP Secured or Secured, we recommend that you configure the dial plan as Secured to enable Microsoft Office Communicator Phone Edition devices to work correctly. This is recommended because of the default encryption level settings that are configured in Communications Server 2007. An Office Communicator Phone Edition device will only work if the encryption settings are configured as they are in the following table. This table shows the relationship between the encryption settings for both Communications Server 2007 and Unified Messaging dial plans.
Encryption settings for Office Communicator Phone Edition
4. Add the servers that are running the Unified Messaging server role to the SIP dial plan. To enable the server to answer incoming calls, you must add the Unified Messaging server to a dial plan.
5. Create a SIP address for the users who will be using Enterprise Voice.
6. Open the Exchange Management Shell and run the exchucutil.ps1 script that is located in the Exchange Installation folder\Exchange Server\Script folder. The exchucutil.ps1 script does the following:
• Grants Office Communications Server permission to read Exchange UM Active Directory objects, specifically, the SIP URI dial plan objects that were created in the previous task.
• Creates a UM IP gateway object in Active Directory for each Communications Server pool or for each server that is running Communications Server 2007 Standard Edition that hosts users who are enabled for Enterprise Voice.
• Creates an Exchange UM hunt group for each gateway. The hunt group pilot identifier will be the name of the dial plan that is associated with the corresponding gateway. The hunt group must specify the Exchange 2007 Unified Messaging SIP dial plan that is used with the UM IP gateway.
You must also complete the following tasks to configure Communications Server 2007 to work with Exchange 2007 Unified Messaging:
• Create location profiles. The location profile name has to match the FQDN of the corresponding UM dial plans.
• Assign location profiles to Communications Server 2007 pools.
• Deploy and configure media gateways and Mediation Servers.
• Define telephone usages, voice policies, and outbound call routes.
• Configure the users for Enterprise Voice services.
• Run the ocsumutil.exe command that creates the contact objects for subscriber access and for the auto attendant. It also validates that there is a location profile name whose name matches the FQDN of the Exchange UM dial plan.
After you have configured the Communications Server 2007 and the Unified Messaging servers, you must enable the user to use Communications Server 2007 and install Office Communicator 2007 on the user's client computer.
Configuring Exchange unified messaging with OCS 2007
Exchange 2007 Unified Messaging combines email, voicemail and fax into a single unified message store. Office Communications Server 2007 integrates into the UM infrastructure to provide call answering, subscriber access, call notification and auto-attendant services. But what's the best way to integrate both products? Configuring Exchange for OCS isn't that different from configuring UM with other IP-based private branch exchanges (PBX).
An Exchange UM dial plan supports three different security levels: unsecured, SIP secured, and secured, the below table shows the differences in terms of Mutual TLS and SRTP for each security level.
You'll want to create a UM dial plan for each Enterprise Voice location profile.
When integrating Exchange UM with OCS 2007 and selecting the appropriate dial-plan security level, consider the following criteria:
• Mutual TLS is required between Exchange UM and OCS. Unsecured level is not an option.
• Office Communicator 2007 clients support secure real-time transport protocol (SRTP); therefore, both secured and SIP secured levels can be used. The encryption level that Communicator uses can be set by means of Group Policy or by changing the PC2PCAVEncryption registry key.
• If Communicator Phone Edition is deployed, the security level should be set to secured.
If you choose to use the Exchange Management Console, create a new dial plan with the security setting SIP secured.
If you use the Exchange Management Shell, type the following command:
New-UMDialPlan -name {dial plan name} -URIType "SipName" -VoIPSecurity {SIPSecured
Secured} -NumberOfDigitsInExtension {number of digits} -AccessTelephoneNumbers "{access number in E.164 format}"
Example:
New-UMDialPlan -Name 'OCS' -NumberOfDigitsInExtension '4' -URIType 'SipName' -VoIPSecurity 'SIPSecured' --AccessTelephoneNumbers '+44020071000'
The dial plan must be enabled on the UM server. Open the Exchange Management Console, expand Server Configuration and select Unified Messaging. On the right pane, right click the UM server and select Properties.
On the UM Settings tab, add the dial plan and click OK.
A box will appear to show you how to create a new UM auto attendant.
Although it's not required, you can use the Exchange Management Console to create a new UM auto attendant for the dial plan that you just configured. You can also use a PowerShell cmdlet to create a new UM auto attendant for the previously configured dial plan.
New-UMAutoAttendant -Name {auto attendant name} -UMDialPlan {name of dial plan} -PilotIdentifierList {auto attendant phone number in E.164 format} -SpeechEnabled $true -Status Enabled
Example:
New-UMAutoAttendant -Name 'OCS Auto Attendant' -UMDialPlan 'OCS' -PilotIdentifierList '+44020071099' -Status 'Enabled' -SpeechEnabled $true
Run ExchUCUtil.ps1
The ExchUCUtil.ps1 script performs the following:
• Creates a UM IP gateway object in Active Directory for each Communications Server pool that hosts Enterprise Voice-enabled users.
• Creates an Exchange UM hunt group for each gateway. The hunt group pilot identifier will be the name of the dial plan associated with the corresponding gateway.
• Grants Communications Server permission to read Exchange UM Active Directory objects, specifically, SIP dial plans that were created in the previous task.
To run this script, open the Exchange Management Shell and navigate to the Scripts folder, which can be found under the Exchange installation directory, and type ExchUCUtil.ps1.
Verify that there are no errors in the output and check the UM IP Gateways tab in the Exchange Management Console. There you'll see the newly created gateway and hunt group.
Now, obtain a certificate for Exchange UM server from a trusted root certificate authority (CA).
Exchange and OCS will communicate using mutual TLS, so they both need a certificate from a trusted CA.
The Exchange setup installs a self-signed certificate that cannot be used with OCS, so you must obtain a new certificate. You can do so using a series of PowerShell cmdlets.
Note: To view the certificate, type Get-ExchangeCertificate in the Exchange Management Shell.
Use this command to generate the request:
New-ExchangeCertificate -GenerateRequest -Path c:\certreq.txt -SubjectName "c=UK, o=MI6, cn=e2k7.mydomain.local" -DomainName autodiscover.webmail.com, webmail.mydomain.local -PrivateKeyExportable $true
The generated text file contains the encoded certificate request that can be used on the online certificate request form.
After the certificate has been issued and saved locally, the following cmdlet will enable it for use with the Exchange UM service and HTTPS:
Enable-ExchangeCertificate -Thumbprint A9594D9632BAB0A136B2372442656CD99C13121B -Services "UM, IIS"
TIP: Open the Exchange server default web site with Internet Explorer to check there are no certificate errors.
Next, restart the Exchange unified Messaging service. Although there are two certificates (self-signed and the new one) installed, the UM service will pick the one that is not self-signed. You can search for event ID 1112 on the Exchange server application log to check which certificate Exchange is using.
You can also double check the certificate by inspecting the serial number.
Enable users for unified messaging
Before enabling users for unified messaging, I recommend filling in the telephone number information in AD. Although Microsoft recommends using E.164 normalized numbers, you can safely use a four-digit (or more) extension on the telephone number field. But I strongly recommend using E.1645 numbers on the Telephones tab (mobile number, home number, etc.).
TIP: If you use non-E.164 telephone numbers, make sure there is a rule on the Company_Phone_Number_Normalization_Rules.txt file (OCS Address Book server) to normalize the numbers.
Once the telephones are added to AD, open the Exchange Management Console to enable users for unified messaging. Then navigate to Recipient Configuration and select Mailbox.
Right-click on the user and select Enable Unified Messaging.
On the Enable Unified Messaging window, click Browse and select the UM Mailbox Policy.
Click Next -- notice that Exchange uses the extension number from AD --, then click Next again.
Finally, click Enable and then Finish.
TIP: In order to make the Call Voice Mail option available in Office Communicator, make sure the SIP URI, for example xyz@mydomain.local, is the default EUM address. The address should be in bold.
Auto-Attendant and Dial Plan Configuration
After installing the Unified Messaging server role, we need to set up a dial plan and auto-attendant on the Exchange 2007 UM server. To create a dial plan and auto-attendant follow these steps:
1. Open the Exchange Management Console.
2. Locate and click on the Unified Messaging tree node in the left pane of the console.
3. In the Action Pane, click the New UM Dial Plan link. This will launch the New UM Dial Plan Wizard.
4. In the first step of the New UM Dial Plan wizard, type a name for the dial plan. In the Number of digits in extension numbers text box enter the number of digits to use for the dial plan.
5. Now click the New button.
Now that we’ve set up the dial plan, let’s configure an auto-attendant:
1. In the Exchange Management Console, locate and click on the Unified
Messaging node in the tree in the left pane of the console.
2. From within the work pane, click UM Auto Attendants. Then click New UM Auto Attendant in the Action pane. The New UM Auto Attendant Wizard will launch.
3. From the New UM Auto Attendant Wizard screen, enter a name for the new attendant into the Name text box.
4. Click the Browse button located next to Select Associated Dial Plan. Locate the dial plan you created earlier in this section, and then click OK.
5. Back in the New UM Auto Attendant Wizard enter an extension number to use for the auto-attendant in the Extension Numbers text box.
6. Select the options to Create the auto-attendant enabled and Create the
auto-attendant as speech enabled. Then click the New button.
7. Now click the Finish button to complete the wizard.
You have now successfully created a dial plan and auto-attendant for use with Exchange 2007 UM.
Mailbox Configuration: Combining OCS and Exchange 2007 Unified Messaging
We set up and configured Exchange 2007 UM with a dial plan and auto-attendant. You now need to configure user mailboxes for UM and OCS 2007–Exchange 2007 connectivity.
Now let’s finish configuring OCS to Exchange 2007 integration. First you need to enable users for UM.
Perform the following steps:
1. Open the Exchange Management Console.
2. Locate the Recipient Configuration section in the tree and expand it.
3. In the middle pane, click to select the user you want to enable for UM.
4. In the Action pane, click Enable Unified Messaging. The Enable Unified Messaging Wizard will launch.
5. Click the Browse button to select a UM policy. Then click OK.
6. To configure a pin choose to Automatically Generate Pin to Access Outlook Voice Access. Then click the Next button.
7. In the Extension configuration section, select Automatically generated SIP resource identifier. Then click the Next button.
8. On the next page, click Enable and then click the Finish button.
You have now configured a user for unified communications. Now let’s set up the connection between OCS 2007 and Exchange 2007. This process involves several different configurations, and it can get complicated. Luckily, Microsoft has provided us with a powershell script and OCSUMUTIL to configure and link the two systems. The OCSUMUTIL creates contacts for Exchange auto-attendants and the phone number for subscriber access to Exchange unified messaging. The OCSUMUTIL also ensures that Enterprise Voice location profiles in OCS match up to an Exchange UM dial plan.
To integrate Exchange 2007 and OCS 2007 do the following:
1. From your Exchange UM server open the Exchange Management Shell.
2. From the Exchange Management Shell run the script exchucutil.ps1 which is located in the Exchange installation folder. This script performs several configuration steps, including providing OCS 2007 access to Exchange 2007 objects.
3. After running the Exchange configuration script, note the UMIPGateway.
4. From the Exchange Management Shell type Set-umipgateway –identity
name from step 3 –port 5061 and press Enter.
5. Now let’s link OCS to the Exchange environment. Log on to the Exchange UM server.
6. From a command prompt, run ocsumutil /domain:yourdomainname and press Enter.
7. Finally, restart the Unified Messaging service on your Exchange 2007 UM server and restart the Office Communications Server Front-End Service on your OCS 2007 server(s).
You have now completed the process of setting up and configuring connectivity between Exchange 2007 UM and OCS 2007.
Tools automate an Exchange UM and OCS 2007 integration
The integration of Exchange UM and OCS 2007 poses some challenges and requires detailed configuration of different utilities and contacts. Performing these tasks manually can be difficult, but certain tools, such as the Exchange UM Integration Utility (OcsUMUtil.exe), can automate the process.
RUN OcsUMUtil.exe
The final step to integrating Exchange UM and OCS 2007 is to run the Exchange UM Integration Utility (OcsUMUtil.exe). The default path on the OCS front-end server should be C:\Program Files\Microsoft Office Communications Server 2007\Server\Support.
The Exchange UM Integration Utility performs the following tasks:
• Creates contact objects for each auto attendant and subscriber access number that Enterprise voice users will need.
• Verifies that the name of each Enterprise Voice location profile matches its corresponding UM dial plan phone context.
Double-click on OcsUMUtil.exe and then onto Load Data to get started. Select a UM SIP dial plan on the left-hand side and click Add.
In the Organizational Unit (OU) check box, select an OU and click OK. In the Name box, accept the default dial plan name or type a new user-friendly name for the contact object that you are creating. In the SIP Address box, accept the default SIP address or type a new SIP address. In the Server or Pool drop-down box, select the OCS Pool where the contact object will be enabled.
In the Phone Number box, leave the default option of Use this pilot number from Exchange UM selected. This number should have been configured when the dial plan and the auto attendant were created.
In the Contact Type list, select the contact type that you want to create -- Subscriber Access or Auto Attendant -- and click OK.
You should create at least one contact for each auto attendant. The utility will display a warning if there an auto attendant object does not have a corresponding contact.
Create at least one contact for each auto attendant. Depicts the two contacts that were created -- Auto Attendant and Subscriber Access.
To verify that the contact objects have been created, open Active Directory Users and Computers and select the OU where the objects were created. Contact objects should appear in the details pane.
Verifying the results
If everything was configured correctly, the Office Communicator client will now display the Call Voice Mail option.
The Call Voice Mail option can be used to call Exchange UM with a simple click.
Other features include missed call notifications, allowing Directory Search calls to outside telephone numbers.
A cool feature of Exchange UM is Directory Search, which lets you browse the Global Address List to find a contact. If the only UM dial plan that's set up is for OCS, you'll have to configure Dialing Rule Groups to be able to make calls to telephone numbers outside of your company.
An easy way to do this is to edit the dial plan properties. Select the Dialing Group Rules tab, then add two rule groups: countrywide and worldwide. Include "*" as Number Mask and Dialed Number.
These two rule groups must also be added to the Dialing Restrictions of the UM mailbox default policy.
Reverse number lookup (RNL)
Both OCS and Exchange Server will try to connect a telephone number to a name every time a call is received or when the system sends a missed call notification.
Both Exchange Server and OCS will search Active Directory and personal Outlook contacts using reverse number lookup (RNL). Although they search the same places, the methods they use are somehow different.
OCS (Communicator) normalizes dialed numbers according to defined rules and performs RNL against the generated address book, which, in turn gets its Primary Phone Numbers from the msRTCSIP-line AD attribute and Outlook contacts. It's also important you ensure that personal contacts are normalized.
Exchange 2007 SP1 will perform RNL against other UM-enabled mailboxes in the same UM dial plan, against personal Outlook contacts and finally against the msRTCSIP-line AD attribute. The normalization logic (InternationalNumberFormat) is only applied if the calling number has the same number of digits of the user's dial plan. Otherwise, Exchange will only add a "tel:+" to the number.
What are some OCS limitations?
OCS behaves like a regular IP PBX, so the UM experience is very similar to the same type of PBX or a SIP gateway. The only limitation is fax capabilities. Users who are associated with a SIP URI dial plan cannot receive incoming faxes because incoming voice and fax calls are routed through a Mediation Server computer and the T.38 protocol is not supported.
The Unified Messaging component of Exchange 2007 SP1 is the designed to be the voice mail solution for Office Communications Server 2007 (OCS). What it means is that anyone can dial an Office Communications Server user and leave a voice mail which will then be delivered to that user's Outlook inbox. The integration of Office Communication Server 2007 and Exchange 2007 Unified Messaging will take users closer to the vision Microsoft has for Unified Communications.
http://www.microsoft.com/presspass/exec/jeff/06-26-06UnifiedCommunications.mspx
For an enterprise with Office Communications Server 2007, the integration of Unified Messaging (hence Exchange 2007) will give enterprise users the added benefit of having e-mail, voice mail, and fax messages consolidated in their inbox. Moreover, certain voice mail features can now be accessed using Office Communicator clients. The Unified Messaging role must be deployed with Exchange 2007 service pack 1 to support this integration.
In an integrated environment when a call to a person is not answered (busy, ring no answer, or diverted to voice mail) it gets routed to the Unified Messaging server (UM). The front end server role of OCS (or the Director) is responsible for processing and routing the call to the UM server.
Clients for OCS can be one of the following:
• Office Communicator (OC)
• OC qualified IP phone device
These clients are also known as Unified Communications Clients or UC Clients. Any user in Active Directory (AD) will have to be enabled and configured for voice capability to talk to the OCS server. The same client will also have to be enabled for Unified Messaging to divert their missed call to the UM server.
Common Scenarios
Following are some of the common scenarios where a call will route through OCS as well as UM. In each of these scenarios the users are enabled for Office Communications as well as Unified Messaging.
Divert to Voice Mail
User A calls User B, who does not answer. The call is then diverted to the UM server by OCS. Exchange UM plays a greeting previously recorded by User B, after which User A records a message. User B receives the voice mail message in their e-mail inbox with contextual information (additional contact information, phone numbers, title) provided in the body of the voice mail message. Callers can are identified through Active Directory or from User B's personal address book in Outlook. Finally, Outlook and Outlook Web Access both display this message along with an embedded player to play the voice message.
Subscriber Access
User A logs on using Office Communicator and selects the option to call voice mail. Since the user is already authenticated through Office Communicator, UM will not require the user to enter their PIN. Exchange UM will play the prompts for voice mail, e-mail, and calendar in Outlook Voice Access, all of which is pulled from User A's mailbox. User A selects to listen to their voice mail.
Auto-Attendant
User A does not know User B's direct line or extension, so User A calls the public access number for User B's organization. User B is connected to the Exchange UM Automated Attendant, which offers various options, including a corporate directory. User A says User B's name verbally, which is recognized by the Automated Attendant and User A's call is transferred to User B's extension in the organization.
Better Together
Integration of OCS and UM gives users a seamless experience to communicate across their entire organization. A UC client has the option to do instant messaging, audio-video conversations, conferencing, and access to all UM functionality from their UC client.
The following are some of the key features of this experience:
• Provides a single authentication method – A user who has logged into Office Communicator does not need to enter their PIN when they check their voice mail from the Office Communicator interface.
• Maintain subject name and priority - An OC user can add subject and priority when making a call. If the call gets diverted to UM, the subject is added to the subject line of the message containing the voice mail or the missed call notification. Additionally, the priority of the original call is maintained by UM in the auto-generated notification for missed calls or new voice mails.
• Integrated missed call notifications - When a call is missed by the receiving party, UM will generate an e-mail notification for the missed call and place it in the inbox for the receiving party.
• Both missed calls and voice mails show the name and contact information for the calling party user. This information is retrieved through Active Directory or from the called party user's personal contact list.
• Traversing the firewall - Media streams can be traversed through the corporate firewall securely without complicated configurations.
• High fidelity voice quality - UM now supports high fidelity codecs for voice mail recording and play back.
E.164 Number Format
The format of the telephone number associated with the UC-enabled user is E.164 (example: +19805551234). Therefore, if a user enters a number that is in different format (example: extension 1234) it has to be manipulated into the E.164 format. OCS will take this number and search the corporate directory to find the user who has a matching number and then voice mail will be routed to the correct user. OCS uses normalization rules to translate these number formats and uses an internal translation service to perform canonicalization transformation. Stay tuned for future blog post on this topic.
A Simple Scenario
In this scenario User A makes a call to user B using Office Communicator. User B does not answer and the call is forwarded to voice mail. User A hears the mailbox greeting and leaves a voice mail for User B.
Call Flow
The following is the call flow for the above scenario:
1. When User A makes a call to User B, the request is first sent to the OCS front end server as a SIP INVITE. OCS will first try to find the target user (User B) in AD and determine whether User B is OC-enabled. If the user is OC-enabled, the call will be forwarded to the registered SIP endpoint for User B. OCS will send the request as a SIP INVITE.
2. If User B does not answer the call, a response message will be sent back to OCS server indicating that User B did not answer the call.
3. OCS will query AD to find out if User B is UM-enabled, and if so, will extract out information such as their proxy address, dial plan name, and the UM server(s) assigned to the dial plan. OCS will use its routing logic to determine the appropriate UM server to route the call to.
4. A new INVITE request will be sent to the UM server by the OCS server. In this new INVTIE request, User B's SIP address will be added as a diversion header indicating that this is a voice mail call for User B.
5. A new session will be created between OCS and UM. OCS will exchange media information with UM and indicate that the RTP end point is the IP address of User A. After media negotiation is done, UM will establish a RTP session with User A and play prompts for leaving a voice mail. User A will directly communicate with UM and leave a voice mail for User B.
6. The remainder of the communication remains the same for any Exchange 2007 environment. After the voice mail is received by UM, it will be handed it off to a hub-transport server which will in turn route the voice mail to the user's mailbox on the appropriate mailbox server.
Configuring Unified Messaging and Office Communications Server 2007
Microsoft Exchange Server 2007 Unified Messaging and Microsoft Office Communications Server 2007 can be deployed together to provide voice messaging, Instant Messaging (IM), enhanced user presence, audio-video conferencing, and an integrated e-mail and messaging experience for users in your organization. This topic discusses how to configure Exchange 2007 Unified Messaging and Communications Server 2007 to support these features.
Deploying Exchange Unified Messaging and Communications Server 2007
Exchange 2007 Unified Messaging combines voice messaging and e-mail messaging into a single messaging infrastructure. Communications Server 2007 Enterprise Voice takes advantage of the Unified Messaging infrastructure to provide voice mail, subscriber access, call notification, and auto attendant services.
Before you can implement these services or features, you must do the following:
• Install Communications Server 2007 in the same Active Directory directory service topology as the Unified Messaging servers.
• Deploy the following Exchange 2007 server roles:
• Unified Messaging server role The Unified Messaging server connects Exchange 2007 with Communications Server 2007.
• Hub Transport server role The Hub Transport server routes e-mail messages from the Unified Messaging server to user mailboxes.
• Client Access server role The Client Access server hosts client protocols, such as Post Office Protocol 3 (POP3), Internet Message Access Protocol 4 (IMAP4), Secure Hypertext Transfer Protocol (HTTPS), Outlook Anywhere (formerly known as RPC over HTTP), the Availability service, and the Autodiscover service. The Client Access server also hosts Exchange Web services.
• Mailbox server role The Mailbox server hosts user mailboxes.
• Install Exchange 2007 Service Pack 1 (SP1) on the computers that have the Unified Messaging server role installed.
• Install and configure Communications Server 2007 in your organization, as follows:
1. Install Communications Server 2007 on servers in your organization.
2. Install a valid certificate that is valid and signed by a certification authority on the Communications Server 2007 servers.
3. Make sure that the certificate that you installed on the Communications Server 2007 servers is trusted by the Unified Messaging servers.
4. Confirm that at least one Communications Server 2007 pool object is created during installation.
Certificate Configuration Recommendations
You must have a certificate that is trusted by both the computers that are running Microsoft Exchange and Office Communications Server 2007. In an environment that has Office Communications Server 2007 and Exchange 2007 Unified Messaging, use the following guidelines for deploying a trusted certificate:
• Import a certificate that is valid and signed by a certification authority (CA). This should be a trusted third-party commercial certificate or a public key infrastructure (PKI) certificate and should be imported on the Communications Server 2007 computers and the Exchange servers that have the Unified Messaging and Client Access server roles installed.
• The most simple certificate deployment scenario is to import the same third-party commercial or PKI certificate to each Exchange 2007 server that has the following server roles installed: Unified Messaging, Client Access, and Hub Transport. Also install this trusted certificate on each computer that is running Office Communications Server 2007. This will help simplify your certificate deployment and reduce the administrative overhead associated with deploying certificates. However, you must obtain a trusted certificate that supports Subject Alternative Names (SANs).
• Although you can install the Unified Messaging server role and other Exchange 2007 server roles on the same computer, when you are deploying Communications Server 2007 we recommend that you install the Unified Messaging server role on a computer that will not be running other Exchange 2007 server roles. If another server role is installed on the same computer as the Unified Messaging server role, the Microsoft Exchange Unified Messaging service may select the incorrect certificate and be unable to use mutual TLS to encrypt traffic. This occurs because of limitations with subject alternative names found in certificates.
For example, if you install the Unified Messaging server role first, and then later install the Client Access server role on the same server, the Microsoft Exchange Unified Messaging service will use the certificate that is created by the Client Access server role instead of the certificate that was created when the Unified Messaging server role was installed. This is because the Microsoft Exchange Unified Messaging service looks for the certificate in the Trusted Root Store that has the most time left before it will expire.
• Because the trusted certificate uses mutual TLS to establish an encrypted channel with Communications Server 2007, Client Access, Hub Transport, and Unified Messaging servers, the name on the certificate that is used during mutual TLS negotiation must match the fully qualified domain name (FQDN) of the server that presents the certificate.
Deployment Path
After you have installed the required server roles in your Exchange 2007 organization, there is a recommended sequence of steps that you must perform on the Exchange UM environment and in your Communications Server 2007 environment to correctly deploy Enterprise Voice and Exchange 2007 Unified Messaging. Exchange 2007 Unified Messaging is used to provide call answering, Outlook Voice Access, and auto attendant services. Communications Server 2007 enables more advanced features that are found in Enterprise Voice services. The following figure illustrates the recommended deployment path for implementing Enterprise Voice services found with Exchange 2007 Unified Messaging and Communications Server 2007.
Deploying Exchange 2007 Unified Messaging and Office Communications Server 2007
There are several steps that you must complete to configure Exchange 2007 Unified Messaging to work with Enterprise Voice in Communications Server 2007. You must do the following:
1. Create one or more Exchange 2007 Unified Messaging Session Initiation Protocol (SIP) URI dial plans that each map to a corresponding Communications Server 2007 location profile. An Enterprise Voice location profile must be created for each Exchange UM dial plan. The location profile name has to match the fully qualified domain name (FQDN) of the UM dial plans. The Unified Messaging dial plan FQDN is used as the name of its corresponding location profile. Use the Get-UMDialPlan cmdlet to obtain the FQDN of a SIP URI dial plan, and then create its corresponding location profile.
2. Install a certificate on the Unified Messaging servers that is valid and signed by a certification authority, and then restart the Microsoft Exchange Unified Messaging service on each Unified Messaging server.
3. To encrypt the VoIP traffic, configure the SIP URI dial plan as SIP secured or Secured.
Although a Unified Messaging dial plan can be configured as SIP Secured or Secured, we recommend that you configure the dial plan as Secured to enable Microsoft Office Communicator Phone Edition devices to work correctly. This is recommended because of the default encryption level settings that are configured in Communications Server 2007. An Office Communicator Phone Edition device will only work if the encryption settings are configured as they are in the following table. This table shows the relationship between the encryption settings for both Communications Server 2007 and Unified Messaging dial plans.
Encryption settings for Office Communicator Phone Edition
4. Add the servers that are running the Unified Messaging server role to the SIP dial plan. To enable the server to answer incoming calls, you must add the Unified Messaging server to a dial plan.
5. Create a SIP address for the users who will be using Enterprise Voice.
6. Open the Exchange Management Shell and run the exchucutil.ps1 script that is located in the Exchange Installation folder\Exchange Server\Script folder. The exchucutil.ps1 script does the following:
• Grants Office Communications Server permission to read Exchange UM Active Directory objects, specifically, the SIP URI dial plan objects that were created in the previous task.
• Creates a UM IP gateway object in Active Directory for each Communications Server pool or for each server that is running Communications Server 2007 Standard Edition that hosts users who are enabled for Enterprise Voice.
• Creates an Exchange UM hunt group for each gateway. The hunt group pilot identifier will be the name of the dial plan that is associated with the corresponding gateway. The hunt group must specify the Exchange 2007 Unified Messaging SIP dial plan that is used with the UM IP gateway.
You must also complete the following tasks to configure Communications Server 2007 to work with Exchange 2007 Unified Messaging:
• Create location profiles. The location profile name has to match the FQDN of the corresponding UM dial plans.
• Assign location profiles to Communications Server 2007 pools.
• Deploy and configure media gateways and Mediation Servers.
• Define telephone usages, voice policies, and outbound call routes.
• Configure the users for Enterprise Voice services.
• Run the ocsumutil.exe command that creates the contact objects for subscriber access and for the auto attendant. It also validates that there is a location profile name whose name matches the FQDN of the Exchange UM dial plan.
After you have configured the Communications Server 2007 and the Unified Messaging servers, you must enable the user to use Communications Server 2007 and install Office Communicator 2007 on the user's client computer.
Configuring Exchange unified messaging with OCS 2007
Exchange 2007 Unified Messaging combines email, voicemail and fax into a single unified message store. Office Communications Server 2007 integrates into the UM infrastructure to provide call answering, subscriber access, call notification and auto-attendant services. But what's the best way to integrate both products? Configuring Exchange for OCS isn't that different from configuring UM with other IP-based private branch exchanges (PBX).
An Exchange UM dial plan supports three different security levels: unsecured, SIP secured, and secured, the below table shows the differences in terms of Mutual TLS and SRTP for each security level.
You'll want to create a UM dial plan for each Enterprise Voice location profile.
When integrating Exchange UM with OCS 2007 and selecting the appropriate dial-plan security level, consider the following criteria:
• Mutual TLS is required between Exchange UM and OCS. Unsecured level is not an option.
• Office Communicator 2007 clients support secure real-time transport protocol (SRTP); therefore, both secured and SIP secured levels can be used. The encryption level that Communicator uses can be set by means of Group Policy or by changing the PC2PCAVEncryption registry key.
• If Communicator Phone Edition is deployed, the security level should be set to secured.
If you choose to use the Exchange Management Console, create a new dial plan with the security setting SIP secured.
If you use the Exchange Management Shell, type the following command:
New-UMDialPlan -name {dial plan name} -URIType "SipName" -VoIPSecurity {SIPSecured
Secured} -NumberOfDigitsInExtension {number of digits} -AccessTelephoneNumbers "{access number in E.164 format}"
Example:
New-UMDialPlan -Name 'OCS' -NumberOfDigitsInExtension '4' -URIType 'SipName' -VoIPSecurity 'SIPSecured' --AccessTelephoneNumbers '+44020071000'
The dial plan must be enabled on the UM server. Open the Exchange Management Console, expand Server Configuration and select Unified Messaging. On the right pane, right click the UM server and select Properties.
On the UM Settings tab, add the dial plan and click OK.
A box will appear to show you how to create a new UM auto attendant.
Although it's not required, you can use the Exchange Management Console to create a new UM auto attendant for the dial plan that you just configured. You can also use a PowerShell cmdlet to create a new UM auto attendant for the previously configured dial plan.
New-UMAutoAttendant -Name {auto attendant name} -UMDialPlan {name of dial plan} -PilotIdentifierList {auto attendant phone number in E.164 format} -SpeechEnabled $true -Status Enabled
Example:
New-UMAutoAttendant -Name 'OCS Auto Attendant' -UMDialPlan 'OCS' -PilotIdentifierList '+44020071099' -Status 'Enabled' -SpeechEnabled $true
Run ExchUCUtil.ps1
The ExchUCUtil.ps1 script performs the following:
• Creates a UM IP gateway object in Active Directory for each Communications Server pool that hosts Enterprise Voice-enabled users.
• Creates an Exchange UM hunt group for each gateway. The hunt group pilot identifier will be the name of the dial plan associated with the corresponding gateway.
• Grants Communications Server permission to read Exchange UM Active Directory objects, specifically, SIP dial plans that were created in the previous task.
To run this script, open the Exchange Management Shell and navigate to the Scripts folder, which can be found under the Exchange installation directory, and type ExchUCUtil.ps1.
Verify that there are no errors in the output and check the UM IP Gateways tab in the Exchange Management Console. There you'll see the newly created gateway and hunt group.
Now, obtain a certificate for Exchange UM server from a trusted root certificate authority (CA).
Exchange and OCS will communicate using mutual TLS, so they both need a certificate from a trusted CA.
The Exchange setup installs a self-signed certificate that cannot be used with OCS, so you must obtain a new certificate. You can do so using a series of PowerShell cmdlets.
Note: To view the certificate, type Get-ExchangeCertificate in the Exchange Management Shell.
Use this command to generate the request:
New-ExchangeCertificate -GenerateRequest -Path c:\certreq.txt -SubjectName "c=UK, o=MI6, cn=e2k7.mydomain.local" -DomainName autodiscover.webmail.com, webmail.mydomain.local -PrivateKeyExportable $true
The generated text file contains the encoded certificate request that can be used on the online certificate request form.
After the certificate has been issued and saved locally, the following cmdlet will enable it for use with the Exchange UM service and HTTPS:
Enable-ExchangeCertificate -Thumbprint A9594D9632BAB0A136B2372442656CD99C13121B -Services "UM, IIS"
TIP: Open the Exchange server default web site with Internet Explorer to check there are no certificate errors.
Next, restart the Exchange unified Messaging service. Although there are two certificates (self-signed and the new one) installed, the UM service will pick the one that is not self-signed. You can search for event ID 1112 on the Exchange server application log to check which certificate Exchange is using.
You can also double check the certificate by inspecting the serial number.
Enable users for unified messaging
Before enabling users for unified messaging, I recommend filling in the telephone number information in AD. Although Microsoft recommends using E.164 normalized numbers, you can safely use a four-digit (or more) extension on the telephone number field. But I strongly recommend using E.1645 numbers on the Telephones tab (mobile number, home number, etc.).
TIP: If you use non-E.164 telephone numbers, make sure there is a rule on the Company_Phone_Number_Normalization_Rules.txt file (OCS Address Book server) to normalize the numbers.
Once the telephones are added to AD, open the Exchange Management Console to enable users for unified messaging. Then navigate to Recipient Configuration and select Mailbox.
Right-click on the user and select Enable Unified Messaging.
On the Enable Unified Messaging window, click Browse and select the UM Mailbox Policy.
Click Next -- notice that Exchange uses the extension number from AD --, then click Next again.
Finally, click Enable and then Finish.
TIP: In order to make the Call Voice Mail option available in Office Communicator, make sure the SIP URI, for example xyz@mydomain.local, is the default EUM address. The address should be in bold.
Auto-Attendant and Dial Plan Configuration
After installing the Unified Messaging server role, we need to set up a dial plan and auto-attendant on the Exchange 2007 UM server. To create a dial plan and auto-attendant follow these steps:
1. Open the Exchange Management Console.
2. Locate and click on the Unified Messaging tree node in the left pane of the console.
3. In the Action Pane, click the New UM Dial Plan link. This will launch the New UM Dial Plan Wizard.
4. In the first step of the New UM Dial Plan wizard, type a name for the dial plan. In the Number of digits in extension numbers text box enter the number of digits to use for the dial plan.
5. Now click the New button.
Now that we’ve set up the dial plan, let’s configure an auto-attendant:
1. In the Exchange Management Console, locate and click on the Unified
Messaging node in the tree in the left pane of the console.
2. From within the work pane, click UM Auto Attendants. Then click New UM Auto Attendant in the Action pane. The New UM Auto Attendant Wizard will launch.
3. From the New UM Auto Attendant Wizard screen, enter a name for the new attendant into the Name text box.
4. Click the Browse button located next to Select Associated Dial Plan. Locate the dial plan you created earlier in this section, and then click OK.
5. Back in the New UM Auto Attendant Wizard enter an extension number to use for the auto-attendant in the Extension Numbers text box.
6. Select the options to Create the auto-attendant enabled and Create the
auto-attendant as speech enabled. Then click the New button.
7. Now click the Finish button to complete the wizard.
You have now successfully created a dial plan and auto-attendant for use with Exchange 2007 UM.
Mailbox Configuration: Combining OCS and Exchange 2007 Unified Messaging
We set up and configured Exchange 2007 UM with a dial plan and auto-attendant. You now need to configure user mailboxes for UM and OCS 2007–Exchange 2007 connectivity.
Now let’s finish configuring OCS to Exchange 2007 integration. First you need to enable users for UM.
Perform the following steps:
1. Open the Exchange Management Console.
2. Locate the Recipient Configuration section in the tree and expand it.
3. In the middle pane, click to select the user you want to enable for UM.
4. In the Action pane, click Enable Unified Messaging. The Enable Unified Messaging Wizard will launch.
5. Click the Browse button to select a UM policy. Then click OK.
6. To configure a pin choose to Automatically Generate Pin to Access Outlook Voice Access. Then click the Next button.
7. In the Extension configuration section, select Automatically generated SIP resource identifier. Then click the Next button.
8. On the next page, click Enable and then click the Finish button.
You have now configured a user for unified communications. Now let’s set up the connection between OCS 2007 and Exchange 2007. This process involves several different configurations, and it can get complicated. Luckily, Microsoft has provided us with a powershell script and OCSUMUTIL to configure and link the two systems. The OCSUMUTIL creates contacts for Exchange auto-attendants and the phone number for subscriber access to Exchange unified messaging. The OCSUMUTIL also ensures that Enterprise Voice location profiles in OCS match up to an Exchange UM dial plan.
To integrate Exchange 2007 and OCS 2007 do the following:
1. From your Exchange UM server open the Exchange Management Shell.
2. From the Exchange Management Shell run the script exchucutil.ps1 which is located in the Exchange installation folder. This script performs several configuration steps, including providing OCS 2007 access to Exchange 2007 objects.
3. After running the Exchange configuration script, note the UMIPGateway.
4. From the Exchange Management Shell type Set-umipgateway –identity
name from step 3 –port 5061 and press Enter.
5. Now let’s link OCS to the Exchange environment. Log on to the Exchange UM server.
6. From a command prompt, run ocsumutil /domain:yourdomainname and press Enter.
7. Finally, restart the Unified Messaging service on your Exchange 2007 UM server and restart the Office Communications Server Front-End Service on your OCS 2007 server(s).
You have now completed the process of setting up and configuring connectivity between Exchange 2007 UM and OCS 2007.
Tools automate an Exchange UM and OCS 2007 integration
The integration of Exchange UM and OCS 2007 poses some challenges and requires detailed configuration of different utilities and contacts. Performing these tasks manually can be difficult, but certain tools, such as the Exchange UM Integration Utility (OcsUMUtil.exe), can automate the process.
RUN OcsUMUtil.exe
The final step to integrating Exchange UM and OCS 2007 is to run the Exchange UM Integration Utility (OcsUMUtil.exe). The default path on the OCS front-end server should be C:\Program Files\Microsoft Office Communications Server 2007\Server\Support.
The Exchange UM Integration Utility performs the following tasks:
• Creates contact objects for each auto attendant and subscriber access number that Enterprise voice users will need.
• Verifies that the name of each Enterprise Voice location profile matches its corresponding UM dial plan phone context.
Double-click on OcsUMUtil.exe and then onto Load Data to get started. Select a UM SIP dial plan on the left-hand side and click Add.
In the Organizational Unit (OU) check box, select an OU and click OK. In the Name box, accept the default dial plan name or type a new user-friendly name for the contact object that you are creating. In the SIP Address box, accept the default SIP address or type a new SIP address. In the Server or Pool drop-down box, select the OCS Pool where the contact object will be enabled.
In the Phone Number box, leave the default option of Use this pilot number from Exchange UM selected. This number should have been configured when the dial plan and the auto attendant were created.
In the Contact Type list, select the contact type that you want to create -- Subscriber Access or Auto Attendant -- and click OK.
You should create at least one contact for each auto attendant. The utility will display a warning if there an auto attendant object does not have a corresponding contact.
Create at least one contact for each auto attendant. Depicts the two contacts that were created -- Auto Attendant and Subscriber Access.
To verify that the contact objects have been created, open Active Directory Users and Computers and select the OU where the objects were created. Contact objects should appear in the details pane.
Verifying the results
If everything was configured correctly, the Office Communicator client will now display the Call Voice Mail option.
The Call Voice Mail option can be used to call Exchange UM with a simple click.
Other features include missed call notifications, allowing Directory Search calls to outside telephone numbers.
A cool feature of Exchange UM is Directory Search, which lets you browse the Global Address List to find a contact. If the only UM dial plan that's set up is for OCS, you'll have to configure Dialing Rule Groups to be able to make calls to telephone numbers outside of your company.
An easy way to do this is to edit the dial plan properties. Select the Dialing Group Rules tab, then add two rule groups: countrywide and worldwide. Include "*" as Number Mask and Dialed Number.
These two rule groups must also be added to the Dialing Restrictions of the UM mailbox default policy.
Reverse number lookup (RNL)
Both OCS and Exchange Server will try to connect a telephone number to a name every time a call is received or when the system sends a missed call notification.
Both Exchange Server and OCS will search Active Directory and personal Outlook contacts using reverse number lookup (RNL). Although they search the same places, the methods they use are somehow different.
OCS (Communicator) normalizes dialed numbers according to defined rules and performs RNL against the generated address book, which, in turn gets its Primary Phone Numbers from the msRTCSIP-line AD attribute and Outlook contacts. It's also important you ensure that personal contacts are normalized.
Exchange 2007 SP1 will perform RNL against other UM-enabled mailboxes in the same UM dial plan, against personal Outlook contacts and finally against the msRTCSIP-line AD attribute. The normalization logic (InternationalNumberFormat) is only applied if the calling number has the same number of digits of the user's dial plan. Otherwise, Exchange will only add a "tel:+" to the number.
What are some OCS limitations?
OCS behaves like a regular IP PBX, so the UM experience is very similar to the same type of PBX or a SIP gateway. The only limitation is fax capabilities. Users who are associated with a SIP URI dial plan cannot receive incoming faxes because incoming voice and fax calls are routed through a Mediation Server computer and the T.38 protocol is not supported.
Subscribe to:
Posts (Atom)