Description: This script disables services, removes scheduled tasks and imports registry values to optimise system performance on Windows Server 2016 running in a Citrix SBC environment.
Warning: This script makes changes to the system registry and other configurational change and as such a full backup of the machine or # snapshot if running in a virtual environment is strongly recommended.
You can see here that the existing mailbox database on server EX2 is still configured with a standalone Client Access server as its Rpc Client Access Server.
Note that any existing Outlook profiles will not automatically update from the single Client Access Server to the new CAS array name.
If you use Hyper-V, you must enable these services.
Instructions: To avoid failure, run Power Shell as an administrator before running this script and make sure you are using the 64-bit version of Power Shell.
First, register a DNS record for the NLB cluster name.One final step, on each of the NLB members run the following command to allow the NLB virtual IP address to be reachable from outside of the subnet that it resides in.Replance “NLB” with the name of your NLB interface on your server.When the CAS array has been established any new mailbox databases created on servers in that Active Directory Site will be configured with the CAS array as their Rpc Client Access Server.However any existing mailbox databases need to be manually updates so that those mailbox users begin connecting to the new CAS array.Carry out full testing before introducing image to production.Note: You should review ALL optimisations this script makes and determine if they fit in to your environment. For example, this script disables key Hyper-V services for use in non-Hyper-V environments.I also use the -Restart switch to automate the restart of the servers, however you can remove this if you wish to control when the servers are restarted. In this example I'm using casarray.exchangeserverpro.local. Click Finish to complete the creation of the NLB cluster.Add-Windows Feature NET-Framework, RSAT-ADDS, Web-Server, Web-Basic-Auth, Web-Windows-Auth, Web-Metabase, Web-Net-Ext, Web-Lgcy-Mgmt-Console, WAS-Process-Model, RSAT-Web-Server, Web-ISAPI-Ext, Web-Digest-Auth, Web-Dyn-Compression, NET-HTTP-Activation, RPC-Over-HTTP-Proxy -Restart Add-Windows Feature NET-Framework, RSAT-ADDS, Web-Server, Web-Basic-Auth, Web-Windows-Auth, Web-Metabase, Web-Net-Ext, Web-Lgcy-Mgmt-Console, WAS-Process-Model, RSAT-Web-Server, Web-ISAPI-Ext, Web-Digest-Auth, Web-Dyn-Compression, NET-HTTP-Activation, RPC-Over-HTTP-Proxy -Restart After both servers have been prepared the NLB cluster can be created. Choose the interface that is to be used for the cluster, and then click Next. Click Add and enter an IPv4 address for the NLB cluster, then click OK. At this stage you should have a single host NLB cluster that is successfully converged.Also as recommended you should perform scheduled scans on all files and folders including those excluded files and folders.Consider excluding the below files from anti-virus scans and/or on-access scanning.