Hi Snatch Savings,
Your custom scripts failing after a restart indicates they are likely bound to a user session rather than the system kernel. You must configure these scripts in the Windows Task Scheduler, setting the trigger explicitly to run at startup and selecting the security context to run whether the user is logged on or not with the highest privileges. This ensures execution at the machine level before any administrator logs in.
The inconsistent load handling occurs because both websites are operating within the same shared Internet Information Services worker process, known as w3wp.exe. During peak traffic, they compete for the same memory space, leading to resource starvation. You must open the Internet Information Services Manager and create a dedicated Application Pool for each web platform. Assigning each site to its own pool forces the server to spin up independent w3wp.exe processes, completely isolating their CPU and memory consumption.
Your session timeout configurations are failing to save due to built-in security locks in the master configuration file located at %SystemRoot%\System32\inetsrv\config\applicationHost.config. By default, IIS prevents individual sites from overriding server-wide session policies. You must navigate to the server node in IIS Manager, open the Configuration Editor, and unlock the system.web/sessionState section. This configuration delegation will allow your site-level web.config files to successfully write and execute their specific timeout values.
Hope this answer has brought you some useful information. If it did, please hit “accept answer”. Should you have any questions, feel free to leave a comment.
VPHAN