Exchange 2007 Out of Office Administrators Assistant

Transcription

1 Exchange 2007 Out of Office Administrators Assistant Installation Guide Version: 2.0

2 Jun. 27 Table of Contents System Requirements... 3 Definition of Configuration Options... 3 Pre Requisites:... 4 Installation:... 5 Active Directory Configuration:... 5 Exchange Permissions Configuration:... 9 Download and Install the OOOAA Tool to your Management Server: Downloading and Installing Microsoft SQL 2005 (Express Edition) on your Client Access OR Dedicated Management Server Installing SQL 2005 (Express Edition) on your Client Access or Dedicated Management Server: Installing SQL 2005 Management Studio Express Installing and configuring the OOOAA on your CAS / Management Server Creating the SQL Database and relevant SQL User Configuring IIS: Configuring the ASP Application to Connect the Database: Configuring the PS Processor: Configuring Powershell to Remote Signed Script Execution: Configuring the OOOService Account within the Database: Summary:

3 Jun. 27 System Requirements Windows 2003 x64 or Windows 2008 x64 based operating system IIS 6 or IIS 7 Exchange 2007 Service Pack 1 Management Tools Microsoft SQL 2005 (Express Edition) or Microsoft SQL 2005 Instance on your Network Exchange 2007 installed and configured organisation Definition of Configuration Options The Out of Office Admin Assistant is supported under the following configurations; Installed on a Dedicated Management Server (this would be a server that is not an Exchange Server, but has the Exchange Management Tools installed as well as SQL 2005 Express Edition along with the ASP pages and Powershell script which make up the program) this is a recommended configuration for larger enterprises Installed on an Exchange Client Access Server where the SQL 2005 Database is on a separate SQL server in your network (the Client Access Server essentially contains the ASP files and the Powershell scripts which connect to the remote database) this is a recommended configuration for medium enterprises Installed on an Exchange Client Access Server with the SQL 2005 Express Edition installed on the same server (the Client Access Server essentially contains the ASP files the Database and the Powershell scripts) this is not a recommended configuration but might suite some smaller companies Installed on an Exchange Server with all Roles and the SQL 2005 Express Edition installed on the same server (the Exchange Server contains the ASP files the Database and the Powershell scripts) this is not a recommended configuration but might suite some smaller companies There are some variations of the above configurations however in order to successfully configure the tool your install will need to meet the prerequisites detailed in the next section and be similar to a configuration example given above. 3

4 Jun. 27 Pre Requisites: You must be using Exchange 2007 RTM or SP1 this version of the tool will not work with Exchange This program requires Microsoft SQL 2005 (Express Edition) or a SQL 2005 instance on your network to function This guide assumes that Exchange (or indeed the management tools) have been installed to their Default locations To ensure proper and reliable functionality your Client Access Servers MUST pass all of the test when running the following Exchange cmdlet from the Exchange Management Console: Test-OutlookWebServices fl If your installation is functioning normally you should see an output which resembles the following: >> Test-OutlookWebServices fl Id : 1003 Type : Information Message : About to test AutoDiscover with the address Administrator@justice.lab.com. Id : 1007 Type : Information Message : Testing server lab-ex27-01.justice.lab.com with the published name & Id : 1019 Type : Information Message : Found a valid AutoDiscover service connection point. The AutoDiscoverURL on this object is Id : 1006 Type : Information Message : The Autodiscover service was contacted at Id : 1016 Type : Success Message : [EXCH]-Successfully contacted the AS service at The elapsed time was 453 milliseconds. Id : 1015 Type : Success Message : [EXCH]-Successfully contacted the OAB service at justice.lab.com/ews/exchange.asmx. The elapsed time was 0 milliseconds. 4

5 Id Type : 1014 : Success Message : [EXCH]-Successfully contacted the UM service at The elapsed time was 593 milliseconds. Id Type Message : 1006 : Success : The Autodiscover service was tested successfully. Installation: Active Directory Configuration: For this part of the installation you will need access to Active Directory Users and Computers I would recommend that perform the following steps on a domain controller in your environment. Open ADUC and then right click on the FQDN of your Domain, from the context menu that appears choose [ NEW -> Organizational Unit ] From the dialog box that appears give the new OU a descriptive name such as OOO and then click on the OK button see below; 5

6 Right click on the new OU that you have created and from the context menu that appears choose [ NEW - > Group ] see below 6

7 Within the Create Group dialog box give the new group a name of OOO_ADMINGROUP ensure that the Group Scope is set to Global and the Group Type is Set to Security when you are happy with this click on the OK button: Returning to the New OU that you have created in Active Directory right click on the OU and from the context menu that appears choose [NEW->User] 7

8 When the New User wizard appears ensure thatt you create your new user with the following account details: o First Name: OOOO o Last Name: Service o User Logon Name: OOOService Then Click on the Next Button Give the OOOService account an appropriate password that is in line with your domain complexity rules but ensure that you tick the User Cannot Change Password and Password Never Expires options then complete the remaining steps of the wizard to create your user. 8

9 You should now add the OOOServicee account (that you have just created) into the following groups within Active Directory: o o Account Operators [located in the Built in container] OOO_AdminGroup [That you created in a previous step] Exchange Permissions Configuration: In order for the OOOServices account to function properly it needs to be assigned Exchange Organization Admin rights in order to complete this step it is recommended that you logon to the Exchange Client Access Server where you intend to install the OOOAA then and use the Exchange Management Shell. The following steps assume the following: You have logged onto your Client Access Server You have the correct permissions to manipulate your Exchange Organizations Administrators. Open the Exchange Management Shell [Start -> Programs -> Microsoft Exchange > Exchange Management Shell] when the Shell opens type in the following command: Add-ExchangeAdministrator Identity ooo_admingroup Role OrgAdmin The output of this command can be seen on the next page. 9

10 10

11 Jun. 27 Download and Install the OOOAA Tool to your Management Server: Before we install the application itself it is important to understand some of the requirements of the OOO and the impact they might have on your installation: The OOOAA requires an installation of SQL Server 2005 Express or a SQL 2005 server located on your network The OOOAA requires access to the Exchange 2007 Management Tools in order to function Considering the above requirements the following options are open to you: You can install the OOOAA Databases on a dedicated SQL 2005 server within your network if you choose this scenario then you will need to install the OOOAA ASP and Powershell scripts on a Client Access Server within your environment (Preferred Scenario) You can install Microsoft SQL 2005 Express Edition on your Client Access Server, you can also install the ASP and Powershell files on the same CAS this option is not recommended as any version of SQL server should not run on the same server as Exchange (unless it is a SBS installation) You can install a copy of Microsoft SQL 2005 (Express Edition) and the Exchange 2007 Management Tools onto a dedicated Management Server and run the OOOAA from that server (Ideal Scenario) The following Instructions are based around an installation of the OOOAA and SQL Server 2005 (express Edition) on a Client Access Server however if you choose to separate out the Databases from the Client Access Server (which is a preferred option) there are pointers within the Installation which will information you of where you should work from. Downloading and Installing Microsoft SQL 2005 (Express Edition) on your Client Access OR Dedicated Management Server DO NOT PERFORM THE FOLLOWING STEPS IF YOU ARE GOING TO USE A SEPERATE SQL SERVER): If you plan to make use of a separate dedicated SQL server (recommended) then please skip these steps and go directly to the Creating the SQL Database and relevant SQL User later on in this section. Logon to you Exchange 2007 Client Access Server and download Microsoft SQL Server 2005 (Express Edition) from the following location: When you have downloaded SQL 2005 again on your Client Access Server - download the SQL Server Express Management Studio from the following location: 11

12 Installing SQL 2005 (Express Edition) on your Client Access or Dedicated Management Server: Double click on the SQLEXPR32.exe to launch Setup you will be presented with the End user license Agreement screen. Tick the box I accept the licensing terms and conditions and then click on the Next button. The installation wizard will then scan your Servers installation and advise you of any components that it needs to install before setup can continue see below: 12

13 Click on the Install button to continue when setup has completed installing the required software will be presented with the following screen: Client on the Next button to continue: You will then be presented with the SQL Server installationn wizard introduction screen click on the Next button to proceed see below: 13

14 The installation wizard will now perform the SCC (Systemss Configuration Check) to ensure that the CAS or indeedd management server is capable of running SQL 2005 Express you will be presented with the following screen (after a brief scan): You will clear to should review the results of the above scan and correct any errors or warnings when you are proceed click on the Next button. You will then be presented with the Registration information screen enter in the detail which are relevant to you or your company ensure that you have UNTICKED the Hide Advanced Configuration Options tick box see below: When you are happy with your settings click on the Next button 14

15 You will now be presented with the Feature Selection screen ensure that you have selected the following features to install: Database Services o o Dataa Files Shared Tools Client Components o o Connectivity Components Software Development Kit An example of how you screen should look is given below: When you are happy with your selection click on the Next button You will then be presented with the Instance Name screen here it is very important that you ensure that the Default Instance radio box is selected (this guide assumes that the OOO Database will be installed on the default instance of SQL Server) example provided on next page. 15

16 Ensure that you screen matches the above and then click on the Next button. The SQL installation wizard will now ask you to configure the Service account to which it will run under considering the purposes that this is being used for we do not necessarily need to follow SQL best practices (unless you really want to) however I suggest that for the purposes of the OOOAA tool you can use the following settings for simplicity of setup: When done click on the Next button You will now be asked to specify an Authentication Mode for SQL the OOOAA requires your SQL server to be install in Mixed Mode - therefore you will need to provide a SA password. 16

17 SQL 2005 requires you to provide a complex password for the SA account therefore it is advisable that your password is around 8 characters, contains numbers and a special character. When you are happy that you settings match that of the above click on the Next button. You will then be presented with the Collation Settings section of SQL setup here you can accept the defaults and click on the Next button. You will then be presented with the Configuration Options Screen ensure that you tick the add user to the SQL server administrator role tick box and then click on the Next button see below: You will then be presented with the Error Reporting screen here you can accept the defaults (or indeed customise them to you own preference) and then click on the Next button. 17

18 Setup should now be ready to install SQL 2005 on your server see below: Click on the Install button. Setup will now begin to install the components that you have selected see below: When setup has finished you will be presented with the following screen: 18

19 19

20 Click on the Next button which will present you with the Completing SQL setup Screen click on the Finish button. When SQL Setup has completed navigate to the following [ START -> Programs -> Microsoft SQL Server > Configuration Tools -> SQL Server Configurationn Manager ] When the configuration manager has loaded, from the left hand navigation tree expand the following: [ SQL Server Configuration Manager (Local) -> SQL Server 2005 Network Configuration -> Protocols for MSSQLSERVER ] The Window will change to look like the following: Ensure that you enabled TCP/IP when you have done this you will need to restart the MSSQLSERVER service. 20

21 Installing SQL 2005 Management Studio Express SQL 2005 Management Studio (Express Edition) is an integral part of the installation for the OOOAA tool essentially it is required to run a number of SQL scripts that will create the OOO database, create the database user and then assign the correct permissions to the database. As indicated above SQL 2005 Management Studio from the following location: fwlink/?linkid=65110 When you have downloaded the application double click on the SQLServer2005_SSMSEE.msi file You will then be presented with the setup welcome screen (see below) click on the Next button to continue. You will then be presented with the License agreement screen accept the agreement and then click on the Next button, this will take you to the license registration screen enter you details and then again click on the Next button. You will then be taken the Featuree Selection Screen (below) accept the defaults (Management Studio Express) and then click on the Next button, you will then be presented with the Ready to install screen click on the Install button where setup will then go away an install SQL 2005 Management Studio Express. When setup has completed you will be presented with the Setup complete dialog click on the Finish button (see below) to complete setup. 21

22 Installing and configuring the OOOAA on your CAS / Management Server Creating the SQL Database and relevant SQL User Download the following file to your Exchange 2007 CAS Server: when the download has completed double click on the ooo-v2.exe file which will present you with the following screen: 22

23 NOTE : If you are using a separate SQL Server Choose a location on your CAS server where you would like the programs binary files to be installed (the default is c:\ooo) then click on the Install button. When the installation has finished copying files to your CAS server you are ready to begin the configuration of IIS. Navigate to the location where you have extracted the files (default is C:\OOO) open the folder inside you should see a folder entitled CreationSQLServer open this folder, inside you will see four scripts: 19/07/ :12 19/07/ :13 19/07/ :14 19/07/ :15 4,924 CreateOOODB.sql 1,348 CreateOOOSetupTable.sql 1,882 CreateOOOUserTable.sql 1,498 CreateSA-Account.sql Copy these scripts to a location on your SQL server. Open SQL Server Management Studio Expresss (this is common weather you have installed SQL on your CAS / Management Server or indeed on a independent SQL installation) [ START -> Programs -> Microsoft SQL Server > SQL Serverr Management Studio Express ] and connect to your default SQL instance. When you have connected to the SQL instance go to the file menu and choose [ OPEN-> File ] 23

24 Using the Open Dialog box navigate to the location where the SQL scripts discussedd above (if you copied them to a separate SQL server you will need to find this location) if you are using a dedicated Management Server or indeed have installed everything on your CAS server they will be located in <OOOAA Install Directory>\CreationSQLServer\ - this is typically C:\ooo\CreationSQLServer Open the CreateOOODB.sql file This script will createe the physical Database files and attach them to the Database engine you will need to modify the paths for both the Database and the Log files to suit your server configuration. Firstly find the following line in the SQL code: NAME = N'ooo', FILENAME UNLIMITED, FILEGROWTH = = N'B:\ooo\DB\ooo. mdf', SIZE = 3072KB, MAXSIZE = 1024KB ) You will need to change the B:\ooo\DB\ to match a path on your server where you would like to place the Database (do not change the name of the database). Then locate the following line within code: NAME = N'ooo_log', FILENAME = N'B:\ooo\DB\ \ooo_log.ldf', SIZE = 1024KB, MAXSIZE = 2048GB, FILEGROWTH = 10%) Again modfiy the path to reflect a sutible path on your server. When you are happy with the changes that you have mode to the script click on the Execute button within the SQL Management Studio: After execution you should receive the following Message within the Management Studio: 24

25 After the database has been created correctly you should now see it appear within the Object Explorer see below; Return to the file menu and open the CreateOOOSetupTable.sql file, then click on the Execute button the Management Studio should return Command(s) completed successfully Now open the CreateOOOUserTable.sql file then click Execute, again the Management Studio should report Command(s) completed successfully Open the CreateSA-Account.sql file you might be tempted to change the user name and the password contained within the file please do not do this at this stage. When you have opened the file Execute it and ensure that you get the Command(s) successfully completed Configuring IIS: Open IIS on your CAS (or Management) Server [ Start -> Programs -> Administrative Tools -> Internet Information Services (IIS) Manager ]. When the IIS Manager has opened expand the [ Internet Information Services -> Web Sites -> Web Service Extensions ] In the right hand pane of the screen you should now see the configured and enabled web service extensions ensure that Active Server Pages is set to Allowed see the example on the next page. When you ha ave enabled ASP move back up the IIS tree and expand [ Internet Information Services -> Web Sites -> Your Server -> Default Web Site ] 25

26 Right click on n the entry for Default Web Site and from the context menu that appears choose [ New -> Virtual Directory ] see below This will then open the Virtual Directory Creation Wizard click on the Next button on the welcomee page which will present you with the Virtual Directory Alias page here you can give the OOO VDIR a custom name I suggest for simplicity you choose OOO and then click on the Next button there is an example of this on the next page: When you have clicked on the Next button you will be presented with the Web Site Content Directory here you need to browse to the path where you installed the OOOAA source files 26

27 (remember that the default was c:\ooo) when you have the correct path click on the Next button seee below When you have clicked on the Next button you will be presented with the Virtual Directory Access Permissions box here you need to ensure that the following options are ticked: o Read o Run scripts (such as ASP) When you are happy with you choices and your options reflect that of the example below click on the Next button. You will then be presented with the Successful screen click on the Finish button to complete the creation of your OOO directory. 27

28 If you now review tree under Default Web Site in IIS you should now see your new OOO directory right click on the entry for OOO and from the context menu that appears choose Permissions see below You will be presented with the Standard Windows permissions dialog box (see below) click on the Add button You will then be presented with the Select users, computers, or groups dialog box you need to enter in the name of the OOO_ADMINGROUP and then click on the OK button 28

29 When you have clicked on the OK button you will then be returned to the Windows permissions group dialog box you should now see the OOO_ADMINGROUP contained within the list of account and groups that have permissions on the OOO folder you need to Grant the OOO_ADMINGROUP Full Control and then click OK seee below Again under the Defaultt Web Site in IIS right click on the OOO directory and from the context menu that appears choose the Properties option this will bring up the configuration of the Virtual Directory choose the Directory Security tab see below 29

30 Under the Authentication and Access control section click on the Edit button whichh will open the following Dialog box: 30

31 Jun. 27 Configure the Authentication Methods to look like those that are configured on the previous page, essentially you need to ensure that the Directory only accepts Basic Authentication it would also be beneficial if you also configure the Default domain to reflect that of your own. Configuring the ASP Application to Connect the Database: If you have gone for either a dedicated Management Server configuration (which combines the SQL Server, ASP pages and the Exchange Management tools on a dedicated non Exchange server) or indeed you have installed SQL 2005 and the ASP files on your Client Access Server then you can skip this step. If however you have chosen to use a separate SQL instance located elsewhere on your Network and install only the ASP pages on your Client Access Server then you will need to configure the ASP DSN file. If you are using a separate SQL use the following steps to configure the DSN: On your server navigate to the installation directory of the OOOAA (if you accepted the installation defaults this will be C:\OOO\) Within this directory you will find a file called odbc.inc open it within Microsoft Notepad which will display the following string: cn="provider=sqloledb;" & "Data Source=localhost;" & "Initial Catalog=ooo;" & "Network=DBMSSOCN;" & "User Id=ooosa;" & "Password=bg194022!" You will need to change the section entitled Datasource=localhost to the IP address or the name of your SQL Server. When you have made the changes save the file and exit Notepad. Configuring the PS Processor: The heart of the OOOAA is called the PS-Processor. Essentially the PS-Processor is a Powershell script that contacts the OOO database (which is populated by the ASP pages) examines the entries and then sets the OOO Internal or External message accordingly. In order for the PS-Processor to work properly on your Client Access server (or Management Server) the following tasks must be completed: Powershell on your Client Access Server must have its Execution Policy set to RemoteSigned The OOOSA tool makes use of a third part reference assembly the location of this assembly is always within the Reflection folder under the Application Directory Powershell needs a fully qualified path to the assembly this is handled by $RefAssemb variable within the script The PS-Processor must have the OOOService account configured within the database The PS-Processor must be configured to run at spaced intervals using the Windows Task Scheduler 31

32 Jun. 27 Configuring Powershell to Remote Signed Script Execution: On your Exchange Server(or Management Server) open the Exchange Management Shell [ Start -> Programs -> Microsoft Exchange Server > Exchange Management Shell ] When the Exchange Management Shell has opened type in the following command: Set-ExecutionPolicy RemoteSigned Then press enter this will then allow the PS-Processor to execute via a batch file Configuring the location of the Reflection Assembly within the PS Processor: On your Client Access Server navigate to the following directory: <OOO Tool Install Path>\PS-Processor\ - so for example if you installed the tool to the default location the path would be c:\ooo\ps-processor\ Inside this folder you will see a script entitled OOO-PSProcessor.ps1 open this file using a text Editor such as Notepad or if you have installed PowerGUI ( you can use the PowerGUI Editor. When you have opened the script file, there is variable which needs to be configured which is named: $RefAssemb $RefAssemb is located towards the top of the script (line 19) and has a default value of B:\ooo- SQL\Reflection see below Between the Quotes you need to replace the default value with the correct value which is the path to the OOOAA Reflection assembly so if you installed the files to c:\ooo the correct location would be: c:\ooo\reflection Configuring the CAS FQDN within the PS Processor: Within the PS-Processor script on line 27 you will see the following entry: $FQDN = $CompStat.Name + "." + $CompStat.Domain This section of the script assumes that the local computer is the Client Access Server (by automatically detecting the local computer name and the domain that the local computer is a member of and then concatenating the two) this is the default setting. However, if you are running the PS Processor script on a dedicated management server (e.g. the server where the script is to run is NOT a Client Access Server) you will need to comment out the above line (using a #) and then uncomment the line below it: #$FQDN = "<Provide the FULL FQDN to your CAS Server>" You need to change the value BETWEEN the quotes. Where you will need to change the <Provide the FULL FQDN to your CAS Server> to the FQDN of your Client Access Server. 32

33 Configuring the OOOService Account within the Database: On your Client Access Server (or dedicated management server) using Internet Explorer navigate to the following URL: On the Client Access or Management Server: /ooo You will be prompted for a Username and Password enter in the credentials of the OOOService account then click OK you should then be presented with a screen that looks like the following: From the menu bar at the top of the screen click on the Setup option. 33

34 When you have clicked on the Setup option you will be presented with a screen that looks like the following screen: On this screen you need to enter in the details to the OOOService account (that you created in Active Directory and indeed used to login to the site) when you have providedd that information click on the Save button if you make a mistake you will need to return to this screen and choose the Clear Setup option (top left of the screen). It is important that you get the account information correct otherwisee the PS-Processor script will not function correctly. 34

35 When you have clicked on the Save button the screen will change to look like the following: Configuring the PS Processor to RUN via a Scheduled Task under Windows: In order to configure the PS-Processor scheduled task use the following steps: Go to [ Startt -> Run ] and the type Control Panel this will open the Windows Control Panel From the Control Panel double click on Scheduled Tasks this will open the Scheduled tasks window choose the Add Scheduled Task option - this in turn will start the Scheduled Tasks wizard on the welcome page click Next You will be presented with an option box which asks you what task you would like to run click on the Browse button see next page 35

36 This will open the familiar find program window you need to navigate to the following path: <OOO Install Dir>\PS-Processor\Execute.bat therefore if you choose the default installation directory the path to the file would be C:\ooo\ps-processor\execute.bat see below When you are happy with your choice click on the Open button which will return you to the Scheduled Task Wizard: 36

37 On the Scheduling properties give the Task a meaningful name (such as the one above) and ensure that the Performm this task setting is Daily then click on the Next button You will then be presented with a screen which looks like the following ensure that all setting match the example below then click Next : You will then be asked to provide a set of credentials that this task should run under here you will need to provide the information for the OOOService account (that you created in Active Directory) when you have entered in the correct details click on the Next button 37

38 You will then be presented with the Completion Dialog ensure that you choose the Open advanced properties for this task when I click Finish see below When your screen matches above click on the Finish button. You will then be presented with the Advanced task settings choose the Schedule tab see below Click on the Advanced button. After clicking on the Advanced button you will be presented with the Advancedd Schedule Options here we need to configure the task to run every 10 minutes or so (this means that any users that are 38

39 placed in the database will have their OOO processed within 10 minutes (or sooner) from being added) however you can configure these options to suit your organisations needs below is an examplee When you are happy click on the OK button twice. Summary: Congratulations! You should now have correctly installed the OOOAA tool on to your Client Access Server you should be able to access to tool from any location on your network via the URL of your CAS remember that this will typically be 39