Click on the button marked Launch Personalization Server Configuration
Click on Next and the configuration tool will check for any variances from the recommended configuration, and report them to you
Click on View to review the variances that the configuration tool has found
Most of the variances in this case are centred around missing IIS7 modules. If, as in this case, the server is not yet in production use, you can install these modules without worrying about the potential impact on IIS performance. If there are other web sites hosted here that are in use, then the possible performance lag must be considered before continuing with the configuration. We have no such worries, so we can click the Repair All button to continue.
Once the variances have been corrected, you should see a screen something like this
As advised on the screen, click Refresh to re-check the variances
If all the variances have been successfully repaired, you should see a screen like this
Click on Close, and then click Next on the initial Pre-requisites screen
The config tool will now check the IIS settings. Select the web site you wish to use from the following screen
We will simply use the Default Web Site. If you have a dedicated site for the Management Server, select it here, then click Next
Now we need to select authentication types, the account used for authentication to the database, and the database itself. I’d always recommend using Windows Authentication wherever possible, although in some environments you may need to use SQL authentication.
Once you’ve made all the necessary selections, click Next to continue. Enter the credentials at the next screen to match the service account you have selected to communicate with the database, and then you will be presented with a summary screen as shown below
Click Accept, and the settings will be configured
When this finishes, check the box for Launch the server configuration utility on exit, and click Finish
This will launch the configuration utility without the wizard, and will allow you to perform a last check for variances from the configuration. Hopefully they should all check out – if they don’t, repair them as per the instructions in the program. Then close the utility.
Next we need to click on the button on the installer’s final screen (the one captioned Launch Management Server configuration). This will launch the second part of the AppSense configuration
Click on Next and you will be presented with the pre-requisites screen in much the same manner as we did for Personalization Server earlier
Click View to see the variances. In our case, BITS is missing, which cannot be repaired by the configuration tool. We will have to go into Server Manager | Features | Add Features and install it through the wizard. Once it is installed, click Refresh, verify that the variances are gone, and then click Close followed by Next.
Next we need to select the web site to use
Again, we will use the Default Web Site, unless our enterprise configuration dictates that it should be different. Click Next.
Next we will select the Authentication Method for clients
Again, we will use the recommended method of Windows Authentication, then click Next.
Next you will need to provide the credentials of an account that can create and configure the database on the server you have selected.
Once you have filled in these details, click on Next again
Then you will need to provide the credentials for impersonation. Once you have entered the username and password and they have been verified, you will be taken to the summary screen
Click on Accept to commit the configuration options you have chosen
The changes will then be deployed
Once this has completed (hopefully successfully), you can also launch the non-wizard configuration utility by checking the box at the end and verifying that there are no other variances to be repaired. If there are any variances (like there were in my example, as I had made a spelling mistake in the configuration) clicking Repair All should allow them to be fixed without much trouble.
Share
