Page Comparison

...

1. Create directories, UnityTest and UnityProd. These can be created anywhere but we typically create in c:\inetpub\wwwroot

2. In IIS, create new Application Pools using all defaults

   1. UnityTest

   2. UnityProd

3. In IIS, under the website entry being used (typically Default Web Site) convert UnityTest/UnityProd to an application. Right click on UnityTest/UnityProd and select, ‘Convert to Application’.

   1. Update Application Pool to match newly created application pool

   2. Accept all other defaults

   3. If you don’t you don’t see UnityTest listed in IIS, refresh the website list or create manually by right clicking on Default Web Site (or the website name being used) and selecting ‘Add Application’

      1. Define Alias as UnityTest or UnityProd

      2. Define Application Pool as UntiyTest or UnityProd

      3. Define Physical Path as C:\inetpub\wwwroot\UnityTest or C:\inetpub\wwwroot\UnityProd

      4. Click OK

4. In File Explorer, right click on UnityTest and select Properties

   1. Give Full Control of directory to new IIS Application Pool user.

   2. Go to Properties / Security tab on directory and click Edit

      

   3. Go to Properties / Security tab on directory and click Edit

   4. Click Add

      

   5. Add new security user and define the Location to be the local machine.  Enter object name in the format, IIS AppPool\<newapppoolname> (i.e. IIS AppPool\UnityTest)

      

   6. If entered correctly, the user will be found after clicking ‘Check Names’:

      

   7. Click OK and then give Full Control

      

   8. Update the Unity app pool Advanced setting IIS App Pool Advanced Settings

      1. Update “Start Mode” to OnDemand to AlwaysRunning

      2. Update “Idle Time-out (minutes)” from 20 to 0

      3. Update “Idle Time-out Action” from Terminate to Suspend

      4. Update "Maximum Worker Processes" from 1 to equal to or greater than the number of logical processors (Minimum 4).

         1. Run this Powershell to check:

            1. (Get-CimInstance Win32_ComputerSystem).NumberOfLogicalProcessors

...

...

2. Configure Unity

Several configuration files need to be updated after the Unity install.  Typically these files are located in, C:\inetpub\wwwroot\UnityTest (or UnityProd).  Always recycle the IIS app pool after making changes.

...