├── LICENSE
├── README.md
├── install.Generic.config
├── install.ExampleCD.config
├── install.ExamplePreviewCD.config
├── install.ExampleCM.config
├── install.ExampleProcessing.config
└── install.ExamplePublishing.config


/LICENSE:
--------------------------------------------------------------------------------
 1 | The MIT License (MIT)
 2 | 
 3 | Copyright (c) 2015 Patrick Perrone
 4 | 
 5 | Permission is hereby granted, free of charge, to any person obtaining a copy
 6 | of this software and associated documentation files (the "Software"), to deal
 7 | in the Software without restriction, including without limitation the rights
 8 | to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
 9 | copies of the Software, and to permit persons to whom the Software is
10 | furnished to do so, subject to the following conditions:
11 | 
12 | The above copyright notice and this permission notice shall be included in all
13 | copies or substantial portions of the Software.
14 | 
15 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
16 | IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
17 | FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
18 | AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
19 | LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
20 | OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
21 | SOFTWARE.
22 | 
23 | 


--------------------------------------------------------------------------------
/README.md:
--------------------------------------------------------------------------------
 1 | Sitecore-PowerShell-Installer
 2 | =============================
 3 | The Sitecore-PowerShell-Installer script enables you to install Production-ready Sitecore instances from the command-line. This script supports installing Sitecore 8.0, 8.1, and 8.2. I've provided some example .config files for standard Sitecore server roles to help get you started.
 4 | 
 5 | ### Features of the Project
 6 | - Install Sitecore with or without the databases.
 7 | - Supports installing a CD, CM, Processing, or Publishing server
 8 | - Script sanity checks SQL connection, input validation, and module dependencies prior to making any changes
 9 | - Write output to the screen and to a log file.
10 | - Fine-grained control of the application pool identity (built-in or domain account)
11 | - Assign recommended file system permissions on web server.
12 | - Add application pool identity to recommended local groups on web server.
13 | - Create user mappings for login in SQL and grant execute permission.
14 | - Install database files on any valid filesystem path or UNC share
15 | - SQL Login used during install doesn't have to be the same account executing the script.
16 | - Full supports MongoDB's connection string specification
17 | - May supply a Solr base address
18 | - Choose to use SQL as a session state server
19 | - Optionally encrypt connection strings
20 | - Many CD-hardening options
21 | 
22 | ### Software Dependencies
23 | - Web Server (IIS) Administration: https://technet.microsoft.com/en-us/library/ee790599.aspx
24 | - SQL Server PowerShell
25 |   - Description: https://msdn.microsoft.com/en-us/library/hh245198.aspx
26 |   - Install Instructions: http://guidestomicrosoft.com/2015/01/13/install-sql-server-powershell-module-sqlps/
27 | - ImportExcel PowerShell Module: used to process Sitecore's Config Enable/Disable [spreadsheet](https://doc.sitecore.net/sitecore_experience_platform/setting_up_and_maintaining/xdb/configuring_servers/server_configuration_resources)
28 | 	- Install-Module -Name ImportExcel
29 | - If using AzureSQL the following should also be installed on the machine running the script: 
30 | 	- [DacFx](https://www.microsoft.com/en-us/download/confirmation.aspx?id=55255)
31 | 	- The following packages from the [SQL Server Feature Pack](https://www.microsoft.com/en-us/download/details.aspx?id=52676)
32 | 		- SQLSysClrTypes.msi
33 | 		- SharedManagementObjects.msi
34 | 		- PowerShellTools.msi
35 | 	- Install-Module -Name AzureRM.sql
36 |  
37 | 
38 | ### Requirements
39 | - SQL logins must exist prior to running script
40 | - SQL login used for install must have the sysadmin role
41 |   - You may optionally turn off all database operations by disabling the <database> configuration element. Do this if database operations must be performed through some other process. Turning database operations removes this requirement.
42 | - The path used to install SQL files must exist and the targetted SQL instance must have FullControl
43 |   - As above, you may either turn off all database operations or disable installing the databases. If you only disable installing databases, the script will still try to ensure things like permisssions on the databases are set.
44 | - Must have a valid Sitecore .zip file
45 | 
46 | ### How To Use
47 | 1. Download [script](https://github.com/patrickperrone/Sitecore-PowerShell-Installer/archive/master.zip) and .zip for desired Sitecore version
48 | 2. Edit config file; watch [video](https://www.youtube.com/watch?v=xFp0cUWsLXA) for explanation of settings and sample config files.
49 | 3. Run Powershell as Administrator and invoke ```. .\install.ps1```
50 | 
51 | ### Troubleshooting
52 | - If you see an error in PowerShell complaining that "the execution of scripts is disabled on this system." then you need to invoke ```Set-ExecutionPolicy -ExecutionPolicy unrestricted -Force```
53 | - If you receive a security warning after invoking ```. .\install.ps1``` and want to make it go away permanently, then right-click on the install.ps1 file and "Unblock" it.
54 | 
55 | This script was inspired by Alex Shyba's script: https://github.com/Sitecore/PowerShell-Script-Library
56 | 


--------------------------------------------------------------------------------
/install.Generic.config:
--------------------------------------------------------------------------------
  1 | <?xml version="1.0" encoding="utf-8"?>
  2 | <InstallSettings>
  3 | 	<!-- PreReqs
  4 | 	https://docs.microsoft.com/en-us/sql/relational-databases/scripting/sql-server-powershell
  5 | 	https://www.microsoft.com/en-us/download/details.aspx?id=52676
  6 | 	Install-Module -Name ImportExcel
  7 | 	Install-Module -Name AzureRM.sql
  8 | 	-->
  9 | 	<!-- If blank, no log file will be generated. The log file location will be the
 10 | 	     SitecoreInstallFolder.
 11 | 	-->
 12 | 	<LogFileName>InstallLog.txt</LogFileName>
 13 | 
 14 | 	<!-- Path of downloaded zip file from Sitecore -->
 15 | 	<SitecoreZipPath>C:\Users\sp_farmadmin\AppData\Roaming\Sitecore\Sitecore Instance Manager\Repository\Sitecore 8.2 rev. 161221.zip</SitecoreZipPath>
 16 | 
 17 | 	<!-- Path of downloaded Sitecore configuration spreadsheet.
 18 | 		 This setting is required and used for installing Sitecore 8.2
 19 | 		 Find the spreadsheet here: https://doc.sitecore.net/sitecore_experience_platform/setting_up_and_maintaining/xdb/configuring_servers/server_configuration_resources
 20 | 	-->
 21 | 	<SitecoreConfigSpreadsheetPath>C:\temp\Config Enable-Disable Sitecore_8.2 Update2.xlsx</SitecoreConfigSpreadsheetPath>
 22 | 
 23 | 	<!-- If true then user prompts will be bypassed. For example, if the script cannot determine that SQL
 24 | 	     has FullControl over database files, then a dialog prompt will be displayed asking if the script
 25 | 	     should continue if this property is set to false.
 26 | 	-->
 27 | 	<SuppressPrompts>false</SuppressPrompts>
 28 | 
 29 | 	<WebServer>
 30 | 		<LicenseFilePath>C:\ArkeSitecoreLicense\license.xml</LicenseFilePath>
 31 | 		<SitecoreInstallRoot>C:\inetpub\wwwroot</SitecoreInstallRoot>
 32 | 		<!-- Folder will be created at the SitecoreInstallRoot if it does not already exist. -->
 33 | 		<SitecoreInstallFolder>mypsinstall</SitecoreInstallFolder>
 34 | 		<!-- Select a name for the last folder under /App_Config/Include
 35 | 		     This is the folder where all config files which must be patched last should be kept (e.g.
 36 | 		     SwitchMasterToWeb.config file.) For Sitecore 8.1, if no name is supplied then the installer
 37 | 		     will use the Z.SwitchMasterToWeb folder.
 38 | 		-->
 39 | 		<LastChildFolderOfIncludeDirectory>zzzMustBeLast</LastChildFolderOfIncludeDirectory>
 40 | 		<!-- Encrypt the contents of the ConnectionStrings.config file -->
 41 | 		<EncryptConnectionStrings>true</EncryptConnectionStrings>
 42 | 
 43 | 		<IISWebSiteName>MyPsInstall</IISWebSiteName>
 44 | 		<DefaultRuntimeVersion>v4.0</DefaultRuntimeVersion>
 45 | 		<!-- Valid values are:
 46 | 		      - NetworkService
 47 | 		      - ApplicationPoolIdentity
 48 | 		      - Any domain account in the form <domain>\<username>
 49 | 
 50 |          If you supply a domain account, you must also provide a valid password for the account
 51 | 		-->
 52 | 		<AppPoolIdentity>EVADEV\SCTest_AppPool</AppPoolIdentity>
 53 | 		<AppPoolIdentityPassword>P@ssword</AppPoolIdentityPassword>
 54 | 		<IISBindings>
 55 | 			<Binding IP="*" Port="80" HostHeader="mypsi" AddToHostsFile="true" />
 56 | 			<Binding IP="10.10.20.11" Port="80" HostHeader="mypsi2" AddToHostsFile="false" />
 57 | 			<Binding IP="10.10.20.11" Port="80" HostHeader="mypsi3" />
 58 | 		</IISBindings>
 59 | 
 60 | 		<!-- Provide a unique name for this instance of Sitecore. This value should be set any time you have mulitple CD or CM servers. -->
 61 | 		<SitecoreInstanceName></SitecoreInstanceName>
 62 | 
 63 | 		<!-- This section controls settings for Sitecore's Analytics -->
 64 | 		<Analytics>
 65 | 			<ClusterName></ClusterName>
 66 | 			<HostName></HostName>
 67 | 		</Analytics>
 68 | 
 69 | 		<!-- This value will be written to the reporting.api connection string. Only applies to Sitecore 8.2 -->
 70 | 		<ReportingApiKey>12345678901234567890123456789012</ReportingApiKey>
 71 | 		
 72 | 		<!-- Sitecore recommends changing the default password hash algorithm from SHA1 to SHA512
 73 | 		
 74 | 			For user management, Sitecore uses the Microsoft ASP.NET membership provider by default. 
 75 | 
 76 | 			*** IMPORTANT! ***
 77 | 			The Microsoft ASP.NET membership provider does not provide a facility for upgrading to a different hash algorithm after you have created 
 78 | 			user accounts. IF YOU CHANGE THE HASH ALGORITHM, EXISTING USERS CAN NO LONGER LOG INTO THE SYSTEM AND MUST CREATE A NEW PASSWORD.
 79 | 			
 80 | 			Valid values are:
 81 | 			- "" 
 82 | 			- a supported hash algorithm from the System.Security.Cryptography.CryptoConfig class : 
 83 | 			https://msdn.microsoft.com/en-us/library/system.security.cryptography.cryptoconfig(v=vs.110).aspx 
 84 | 		-->
 85 | 		<PasswordHashAlgorithm>SHA512</PasswordHashAlgorithm>
 86 | 
 87 | 		<CMServerSettings enabled="true">
 88 | 			<!-- If this value is non-empty, then admin's password will be set to this value -->
 89 | 			<DefaultSitecoreAdminPassword>foobar</DefaultSitecoreAdminPassword>
 90 | 
 91 | 			<!-- Add an Encryption Key for the Telerik controls 
 92 | 				  http://docs.telerik.com/devtools/aspnet-ajax/controls/asyncupload/security
 93 | 				 If using load-balanced CM servers, the value must match on both servers.
 94 | 			-->
 95 | 			<TelerikEncryptionKey></TelerikEncryptionKey>
 96 | 
 97 | 			<!-- Use these settings to dedicate Sitecore instance as the Publishing server. This is required
 98 | 			     when you are using load-balanced CM servers.
 99 | 			-->
100 | 			<Publishing enabled="false">
101 | 				<!-- This setting is ALWAYS applied to a CM server even if publishing is disabled. Therefore,
102 | 				     for an isolated CM you may leave this value blank or make sure it matches the CM
103 | 				     InstanceName
104 | 				-->
105 | 				<PublishingInstance></PublishingInstance>
106 |                 <!-- Use these settings to enable IIS Application Initialization on a dedicated publishing instance.
107 |                      Setting enabled to true will:
108 |                         - Enable the Application Initialization feature on the web server
109 |                         - Add preloadEnabled="true" to the application configuration
110 |                         - Add applicationInitialization node to the system.webserver
111 | 						- Set doAppInitAfterRestart to true
112 |                         - Set the AppPool startMode to "AlwaysRunning"
113 |                         - Set the AppPool IdleTimeout to 0
114 |                         - Set the AppPool Recycling regular time interval to 0
115 |                      Valid values are "true" or "false"
116 | 				-->
117 |                 <ApplicationInitializationEnabled>false</ApplicationInitializationEnabled>
118 |                 <!-- Timeout length in minutes for IIS App Pool
119 |                      If enabled, Application Intialization will override this value with 0.
120 |                  -->
121 | 				<AppPoolIdleTimeout>600</AppPoolIdleTimeout>
122 | 				<!-- If this setting is false, the keepalive task will not run and the publishing server will get cold. -->
123 | 				<DisableScheduledTaskExecution>true</DisableScheduledTaskExecution>
124 | 				<Parallel enabled="false">
125 | 					<!-- If set, the autogrowth for data and log files of the web database and any copy of the
126 | 					     web database will be based on a fixed size of MB rather than a percentage. This follow
127 | 					     recommendations from Sitecore. Recommended values range from 30 to 50.
128 | 					     Valid values range from 10 to 100.
129 | 					-->
130 | 					<WebDatabaseAutoGrowthInMB>30</WebDatabaseAutoGrowthInMB>
131 | 					<MaxDegreesOfParallelism>4</MaxDegreesOfParallelism>
132 | 				</Parallel>
133 | 			</Publishing>
134 | 			<!-- Use these settings to dedicate Sitecore instance as a Processing server. -->
135 | 			<Processing enabled="false">
136 | 				<!-- Valid values are "true" or "false"
137 | 					 Invalid values or missing elements will be treated as "false"
138 | 				-->
139 | 				<ApplyIPWhitelist>true</ApplyIPWhitelist>
140 | 				<!-- Enabling this will cause recommended connection strings to be commented out -->
141 | 				<DeactivateConnectionStrings>true</DeactivateConnectionStrings>
142 | 				<!-- Enabling this setting causes some files on the Processing server to have ".disabled" concatenated to
143 | 					 their filename. Other files necessary for configuring a Processing file will be enabled. The files changed are from the recommendations here:
144 | 					 https://doc.sitecore.net/sitecore_experience_platform/setting_up_and_maintaining/xdb/configuring_servers/configure_a_processing_server
145 | 				-->
146 | 				<ConfigureFilesForProcessing>true</ConfigureFilesForProcessing>
147 | 				<!-- Denies anonymous users from accessing certain directories per Sitecore's recommendations -->
148 | 				<PreventAnonymousAccess>true</PreventAnonymousAccess>
149 | 			</Processing>
150 | 		</CMServerSettings>
151 | 
152 | 		<CDServerSettings enabled="false">
153 | 			<!-- Valid values are "true" or "false"
154 | 			     Invalid values or missing elements will be treated as "false"
155 | 			-->
156 | 			<ApplyIPWhitelist>true</ApplyIPWhitelist>
157 | 			<!-- Enabling this will cause recommended connection strings to be commented out -->
158 | 			<DeactivateConnectionStrings>true</DeactivateConnectionStrings>
159 | 			<!-- Enabling this setting causes some files on the CD server to have ".disabled" concatenated to
160 | 			     their filename. Other files necessary for configuring a CD such as the
161 | 			     SwitchMasterToWeb.config file will be enabled. The files changed are from the recommendations here:
162 | 			     https://doc.sitecore.net/sitecore%20experience%20platform/xdb%20configuration/configure%20a%20content%20delivery%20server
163 | 			-->
164 | 			<ConfigureFilesForCD>true</ConfigureFilesForCD>
165 | 			<!-- Denies anonymous users from accessing certain directories per Sitecore's recommendations -->
166 | 			<PreventAnonymousAccess>true</PreventAnonymousAccess>
167 | 			<!-- Prevent the execution of scripts or programs in the upload and temp folders -->
168 | 			<DenyExecutePermission>true</DenyExecutePermission>
169 | 			<!-- Enabling this setting prevents uploading files outside of the Sitecore client -->
170 | 			<DisableUploadWatcher>true</DisableUploadWatcher>
171 | 			<!-- If you have implemented custom code that uses ASP.NET Web API attribute routing, to avoid errors, disable the following -->
172 | 			<DisableExperienceAnalyticsAssemblies>true</DisableExperienceAnalyticsAssemblies>
173 | 			<!-- Remove PhantomJs from CD per Sitecore's recommendations -->
174 | 			<RemovePhantomJs>true</RemovePhantomJs>
175 | 			<!-- Disables Telerik UI Handlers on CD server. -->
176 | 			<DisableTelerikControls>true</DisableTelerikControls>
177 | 		</CDServerSettings>
178 | 
179 | 		<!-- Media Request Protection - Applied to CM and CD Servers -->
180 | 		<MediaRequestProtection>
181 | 			<!-- In a multi-instance setup, use the same value for Media.RequestProtection.SharedSecret on every instance.
182 | 				 SharedSecret is required. If no value is provided, Sitecore default value will be used. -->
183 | 			<SharedSecret></SharedSecret>
184 | 			<!-- Specifies whether the media request protection feature will output detailed information to the Sitecore log file.
185 | 				 If no value is provided, Sitecore default value (true) will be used. -->
186 | 			<LoggingEnabled>true</LoggingEnabled>
187 | 		</MediaRequestProtection>
188 | 
189 | 		<!-- Hardened directories in IIS will deny all clients except the following IPs -->
190 | 		<IPWhiteList>
191 | 			<IP>127.0.0.1</IP>
192 | 			<IP>10.10.20.7</IP>
193 | 			<IP>10.10.20.11</IP>
194 | 		</IPWhiteList>
195 | 
196 | 		<SessionStateProvider>
197 | 			<!-- Valid values for Private and Shared are:
198 | 			       - InProc
199 | 			       - MSSQL (except for Shared on a CM!)
200 | 			       - Mongo (currently not supported by the installer)
201 | 			-->
202 | 			<Private>InProc</Private>
203 | 			<Shared>InProc</Shared>
204 | 		</SessionStateProvider>
205 | 
206 | 		<Solr>
207 | 			<!-- If provided, the installer will modify the
208 | 			     Sitecore.ContentSearch.Solr.DefaultIndexConfiguration.config.example file to use the given address
209 | 			-->
210 | 			<ServiceBaseAddress>http://solr5:8888/solr</ServiceBaseAddress>
211 | 		</Solr>
212 | 
213 | 		<!-- This section determines how the connection strings for for MongoDB will be formed. Any values
214 | 			 left blank will not be used. The settings below adhere to MongoDB's connection string format
215 | 			 specification: https://docs.mongodb.org/manual/reference/connection-string/
216 | 
217 | 			 If this section is not enabled, it will be ignored.
218 | 		-->
219 | 		<MongoDb enabled="true">
220 | 			<!-- Optional, won't be used if blank -->
221 | 			<Credentials>
222 | 				<Username>someuser</Username>
223 | 				<Password>somepassword</Password>
224 | 			</Credentials>
225 | 			<!-- At least one <Host> is required, each <Host> must specify a <HostName> and an optional <Port> -->
226 | 			<Hosts>
227 | 				<Host>
228 | 					<HostName>node1.company.com</HostName>
229 | 					<Port>27017</Port>
230 | 				</Host>
231 | 				<Host>
232 | 					<HostName>node2.company.com</HostName>
233 | 					<Port>9999</Port>
234 | 				</Host>
235 | 			</Hosts>
236 | 			<!-- This setting's value will be appended to the connection string's URI. The format should be as a
237 | 			     query string.
238 | 			-->
239 | 			<Options>?authMechanism=PLAIN&amp;authSource=$external&amp;replicaSet=mymongoset</Options>
240 | 		</MongoDb>
241 | 
242 | 	</WebServer>
243 | 
244 | 	<!-- If disabled the script will skip ALL database related operations.
245 | 		   - No SQL server connection tests
246 | 		   - Databases files will not be copied or attached
247 | 		   - User mappings, permissions will not be set
248 | 		   - Autogrowth will not be set on web database (relevant to parallel publishing)
249 | 
250 | 		 Regardless the information in this section will still be used to form connection string values.
251 | 		 Thus, ensure that the database names are always accurate as well as the SQL server name and data
252 | 		 access account information.
253 | 		 Type: Azure, Local
254 |  		Using Azure requires the installation of the Dacfx
255 |  		https://www.microsoft.com/en-us/download/confirmation.aspx?id=55255
256 | 	-->
257 | 	<Database type="Local" enabled="true">
258 | 		<Azure>
259 | 			<SQLPackagePath>C:\Program Files\Microsoft SQL Server\140\DAC\bin\sqlpackage.exe</SQLPackagePath>
260 | 			<SQLResourceGroup></SQLResourceGroup>
261 | 			<SQLEdition></SQLEdition>
262 | 			<SQLMaxSize></SQLMaxSize> <!-- in Bytes -->
263 | 			<SQLServiceObjective></SQLServiceObjective>
264 | 		</Azure>
265 | 		<!-- Valid values are "true" or "false" Invalid values or missing element will be treated as "false"
266 | 		     Note that even if you do not install the database, database mappings and permissions will still
267 | 		     be written.
268 | 		-->
269 | 		<InstallDatabase>true</InstallDatabase>
270 | 
271 | 		<!-- Do not edit this list unless you know what you are doing! :) This list represents the all of
272 | 		     the default databases used by Sitecore.
273 | 		-->
274 | 		<DatabaseNames>
275 | 			<name>Core</name>
276 | 			<name>Master</name>
277 | 			<name>Web</name>
278 | 			<name>Sessions</name>
279 | 			<name>Reporting</name>
280 | 		</DatabaseNames>
281 | 
282 | 		<!-- Add <copy> elements for each duplicate web database to be created -->
283 | 		<WebDatabaseCopies>
284 | 			<!-- Setting the connectionStringName attribute will assign that value to the "name" attribute
285 | 			     of the connection string for this databse. For example, if the connectionStringName is "web"
286 | 			     then the web connection string will point to the preview database. This is useful for creating
287 | 			     a preview-type CD server that serves content out of a different database than the normal, web
288 | 			     database. If the attribute is missing or does not have a value, then the name of the copy
289 | 			     database will be used to create the name of the connection string.
290 | 
291 | 			     NOTE: The "web" database is referred to in many places in Sitecore’s configuration:
292 | 				   - Database definitions
293 | 				   - Agents
294 | 				   - Index definitions
295 | 				   - Indexing strategies
296 | 				   - Site definitions
297 | 
298 | 			     Thus, you will need to think about patching the Sitecore's .config files to address this behavior.
299 | 
300 | 				 * On the preview CD server, by replacing the "web" connection string’s database with a preview
301 | 				 database, you can avoid much of this configuration work.  If you are using Lucene, you
302 | 				 shouldn't need to do anything else. If you are using Solr, I STRONGLY recommend you create
303 | 				 dedicated 'preview' versions of web indexes and indexing strategies.
304 | 
305 | 				 * On the CM server, you should consider doing the following:
306 | 				   - Configuring a <database> element similar to the web's
307 | 				   - If you want schedule periodic publishing, then create an <agent> for Sitecore.Tasks.PublishAgent
308 | 				     to publish to your preview database
309 | 				   - If you use WebDAV, consider adding your preview database to the
310 | 				     Sitecore.Tasks.CleanupFDAObsoleteMediaData <agent>
311 | 				   - Create 'preview' version of the onPublishEndAsync and onPublishEndAsyncSingleInstance index
312 | 				     update strategies
313 | 				   - Create Index definitions for the 'preview' versions of your 'web' indexes. This is especially
314 | 				     important if you use Solr!
315 | 			-->
316 | 		</WebDatabaseCopies>
317 | 
318 | 		<!-- The format is: {sqlservername[\instancename]}[,{port}]
319 | 			 Examples
320 | 			 - vmwebdev01
321 | 			 - vmwebdev01,1433
322 | 			 - vmwebdev01\myinstance
323 | 			 - vmwebdev01\myinstance,1433
324 | 			 Azure
325 |  			 - exampleDB.database.windows.net
326 | 		-->
327 | 		<SqlServerName>vmwebdev01,1433</SqlServerName>
328 | 
329 | 		<!-- This login is used to attach databases and assign roles in SQL. The login must have the sysadmin
330 | 			 server role.
331 | 		-->
332 | 		<SqlLoginForInstall>SC_InstallAccount</SqlLoginForInstall>
333 | 		<SqlLoginForInstallPassword>P@ssword</SqlLoginForInstallPassword>
334 | 
335 | 		<!-- If specified, this login will be used in connection strings. Only SQL logins are valid. -->
336 | 		<SqlLoginForDataAccess></SqlLoginForDataAccess>
337 | 		<SqlLoginForDataAccessPassword></SqlLoginForDataAccessPassword>
338 | 
339 | 		<!-- If true, then the ApplicationPoolIdentity will be used for the SQL login rather than
340 | 		     SqlLoginForDataAccess. This setting requires a domain account is specified for the
341 | 		     ApplicationPoolIdentity.
342 | 		-->
343 | 		<UseWindowsAuthenticationForSqlDataAccess>true</UseWindowsAuthenticationForSqlDataAccess>
344 | 
345 | 		<DatabaseInstallPath>
346 | 			<DataFiles>
347 | 				<!-- Must be defined, and folder must exist. The SQL instance must have FullControl over the folder.
348 | 					 This value is used to attach the databases in SQL. If the Unc value is missing, this is also the
349 | 					 path used as the destination for SQL database file copying.
350 | 				-->
351 | 				<Local>C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\installdemo data files</Local>
352 | 
353 | 				<!-- If defined this path will be used to copy database files into the file system of the
354 | 					 SQL server.
355 | 				-->
356 | 				<Unc>\\VMWEBDEV01\installdemo data files</Unc>
357 | 			</DataFiles>
358 | 
359 | 			<!-- This sectional is optional. If undefined, then log files will be installed in the same location
360 | 				 the same location as the data files defined above.
361 | 			-->
362 | 			<LogFiles>
363 | 			</LogFiles>
364 | 		</DatabaseInstallPath>
365 | 
366 | 		<DatabaseNamePrefix>InstallDemo_Sitecore_</DatabaseNamePrefix>
367 | 
368 | 	</Database>
369 | 
370 | </InstallSettings>
371 | 


--------------------------------------------------------------------------------
/install.ExampleCD.config:
--------------------------------------------------------------------------------
  1 | <?xml version="1.0" encoding="utf-8"?>
  2 | <InstallSettings>
  3 | 	<!-- PreReqs
  4 | 	https://docs.microsoft.com/en-us/sql/relational-databases/scripting/sql-server-powershell
  5 | 	https://www.microsoft.com/en-us/download/details.aspx?id=52676
  6 | 	Install-Module -Name ImportExcel
  7 | 	Install-Module -Name AzureRM.sql
  8 | 	-->
  9 | 	<!-- If blank, no log file will be generated. The log file location will be the
 10 | 	     SitecoreInstallFolder.
 11 | 	-->
 12 | 	<LogFileName>InstallLog.txt</LogFileName>
 13 | 
 14 | 	<!-- Path of downloaded zip file from Sitecore -->
 15 | 	<SitecoreZipPath>C:\Users\sp_farmadmin\AppData\Roaming\Sitecore\Sitecore Instance Manager\Repository\Sitecore 8.2 rev. 161221.zip</SitecoreZipPath>
 16 | 
 17 | 	<!-- Path of downloaded Sitecore configuration spreadsheet.
 18 | 		 This setting is required and used for installing Sitecore 8.2
 19 | 		 Find the spreadsheet here: https://doc.sitecore.net/sitecore_experience_platform/setting_up_and_maintaining/xdb/configuring_servers/server_configuration_resources
 20 | 	-->
 21 | 	<SitecoreConfigSpreadsheetPath>C:\temp\Config Enable-Disable Sitecore_8.2 Update2.xlsx</SitecoreConfigSpreadsheetPath>
 22 | 
 23 | 	<!-- If true then user prompts will be bypassed. For example, if the script cannot determine that SQL
 24 | 	     has FullControl over database files, then a dialog prompt will be displayed asking if the script
 25 | 	     should continue if this property is set to false.
 26 | 	-->
 27 | 	<SuppressPrompts>true</SuppressPrompts>
 28 | 
 29 | 	<WebServer>
 30 | 		<LicenseFilePath>C:\ArkeSitecoreLicense\license.xml</LicenseFilePath>
 31 | 		<SitecoreInstallRoot>C:\inetpub\wwwroot</SitecoreInstallRoot>
 32 | 		<!-- Folder will be created at the SitecoreInstallRoot if it does not already exist. -->
 33 | 		<SitecoreInstallFolder>ExampleCD</SitecoreInstallFolder>
 34 | 		<!-- Select a name for the last folder under /App_Config/Include
 35 | 		     This is the folder where all config files which must be patched last should be kept (e.g.
 36 | 		     SwitchMasterToWeb.config file.) For Sitecore 8.1, if no name is supplied then the installer
 37 | 		     will use the Z.SwitchMasterToWeb folder.
 38 | 		-->
 39 | 		<LastChildFolderOfIncludeDirectory>zzzMustBeLast</LastChildFolderOfIncludeDirectory>
 40 | 		<!-- Encrypt the contents of the ConnectionStrings.config file -->
 41 | 		<EncryptConnectionStrings>true</EncryptConnectionStrings>
 42 | 
 43 | 		<IISWebSiteName>ExampleCD</IISWebSiteName>
 44 | 		<DefaultRuntimeVersion>v4.0</DefaultRuntimeVersion>
 45 | 		<!-- Valid values are:
 46 | 		      - NetworkService
 47 | 		      - ApplicationPoolIdentity
 48 | 		      - Any domain account in the form <domain>\<username>
 49 | 
 50 | 		     If you supply a domain account, you must also provide a valid password for the account.
 51 | 		-->
 52 | 		<AppPoolIdentity>EVADEV\SCTest_AppPool</AppPoolIdentity>
 53 | 		<AppPoolIdentityPassword>P@ssword</AppPoolIdentityPassword>
 54 | 		<IISBindings>
 55 | 			<Binding IP="*" Port="80" HostHeader="examplecd" AddToHostsFile="true" />
 56 | 			<Binding IP="10.10.20.11" Port="80" HostHeader="excd" AddToHostsFile="false" />
 57 | 			<Binding IP="10.10.20.11" Port="80" HostHeader="ecd" />
 58 | 		</IISBindings>
 59 | 
 60 | 		<!-- Provide a unique name for this instance of Sitecore. This value should be set any time you have mulitple CD or CM servers. -->
 61 | 		<SitecoreInstanceName>ExampleCD1</SitecoreInstanceName>
 62 | 
 63 | 		<!-- This section controls settings for Sitecore's Analytics -->
 64 | 		<Analytics>
 65 | 			<ClusterName>mycluster1.company.com</ClusterName>
 66 | 			<HostName>www.company.com</HostName>
 67 | 		</Analytics>
 68 | 
 69 | 		<!-- This value will be written to the reporting.api connection string. Only applies to Sitecore 8.2 -->
 70 | 		<ReportingApiKey>12345678901234567890123456789012</ReportingApiKey>		
 71 | 		
 72 | 		<!-- Sitecore recommends changing the default password hash algorithm from SHA1 to SHA512
 73 | 		
 74 | 			For user management, Sitecore uses the Microsoft ASP.NET membership provider by default. 
 75 | 
 76 | 			*** IMPORTANT! ***
 77 | 			The Microsoft ASP.NET membership provider does not provide a facility for upgrading to a different hash algorithm after you have created 
 78 | 			user accounts. IF YOU CHANGE THE HASH ALGORITHM, EXISTING USERS CAN NO LONGER LOG INTO THE SYSTEM AND MUST CREATE A NEW PASSWORD.
 79 | 			
 80 | 			Valid values are:
 81 | 			- "" 
 82 | 			- a supported hash algorithm from the System.Security.Cryptography.CryptoConfig class : 
 83 | 			https://msdn.microsoft.com/en-us/library/system.security.cryptography.cryptoconfig(v=vs.110).aspx 
 84 | 		-->
 85 | 		<PasswordHashAlgorithm>SHA512</PasswordHashAlgorithm>
 86 | 
 87 | 		<CMServerSettings enabled="false">
 88 | 			<!-- If this value is non-empty, then admin's password will be set to this value -->
 89 | 			<DefaultSitecoreAdminPassword></DefaultSitecoreAdminPassword>
 90 | 
 91 | 			<!-- Add an Encryption Key for the Telerik controls 
 92 | 				 http://docs.telerik.com/devtools/aspnet-ajax/controls/asyncupload/security
 93 | 				 If using load-balanced CM servers, the value must match on both servers.
 94 | 			-->
 95 | 			<TelerikEncryptionKey></TelerikEncryptionKey>
 96 | 
 97 | 			<!-- Use these settings to dedicate Sitecore instance as the Publishing server. This is required
 98 | 			     when you are using load-balanced CM servers.
 99 | 			-->
100 | 			<Publishing enabled="false">
101 | 				<!-- This setting is ALWAYS applied to a CM server even if publishing is disabled. Therefore,
102 | 				     for an isolated CM you may leave this value blank or make sure it matches the CM
103 | 				     InstanceName
104 | 				-->
105 | 				<PublishingInstance></PublishingInstance>
106 |                 <!-- Use these settings to enable IIS Application Initialization on a dedicated publishing instance.
107 |                      Setting enabled to true will:
108 |                         - Enable the Application Initialization feature on the web server
109 |                         - Add preloadEnabled="true" to the application configuration
110 |                         - Add applicationInitialization node to the system.webserver
111 | 						- Set doAppInitAfterRestart to true
112 |                         - Set the AppPool startMode to "AlwaysRunning"
113 |                         - Set the AppPool IdleTimeout to 0
114 |                         - Set the AppPool Recycling regular time interval to 0
115 |                      Valid values are "true" or "false"
116 | 				-->
117 |                 <ApplicationInitializationEnabled>false</ApplicationInitializationEnabled>
118 |                 <!-- Timeout length in minutes for IIS App Pool
119 |                      If enabled, Application Intialization will override this value with 0.
120 |                  -->
121 | 				<AppPoolIdleTimeout>600</AppPoolIdleTimeout>
122 | 				<!-- If this setting is false, the keepalive task will not run and the publishing server will get cold. -->
123 | 				<DisableScheduledTaskExecution>true</DisableScheduledTaskExecution>
124 | 				<Parallel enabled="false">
125 | 					<!-- If set, the autogrowth for data and log files of the web database and any copy of the
126 | 					     web database will be based on a fixed size of MB rather than a percentage. This follow
127 | 					     recommendations from Sitecore. Recommended values range from 30 to 50.
128 | 					     Valid values range from 10 to 100.
129 | 					-->
130 | 					<WebDatabaseAutoGrowthInMB>30</WebDatabaseAutoGrowthInMB>
131 | 					<MaxDegreesOfParallelism>4</MaxDegreesOfParallelism>
132 | 				</Parallel>
133 | 			</Publishing>
134 | 			<!-- Use these settings to dedicate Sitecore instance as a Processing server. -->
135 | 			<Processing enabled="false">
136 | 				<!-- Valid values are "true" or "false"
137 | 					 Invalid values or missing elements will be treated as "false"
138 | 				-->
139 | 				<ApplyIPWhitelist>true</ApplyIPWhitelist>
140 | 				<!-- Enabling this will cause recommended connection strings to be commented out -->
141 | 				<DeactivateConnectionStrings>true</DeactivateConnectionStrings>
142 | 				<!-- Enabling this setting causes some files on the Processing server to have ".disabled" concatenated to
143 | 					 their filename. Other files necessary for configuring a Processing file will be enabled. The files changed are from the recommendations here:
144 | 					 https://doc.sitecore.net/sitecore_experience_platform/setting_up_and_maintaining/xdb/configuring_servers/configure_a_processing_server
145 | 				-->
146 | 				<ConfigureFilesForProcessing>true</ConfigureFilesForProcessing>
147 | 				<!-- Denies anonymous users from accessing certain directories per Sitecore's recommendations -->
148 | 				<PreventAnonymousAccess>true</PreventAnonymousAccess>
149 | 			</Processing>
150 | 		</CMServerSettings>
151 | 
152 | 		<CDServerSettings enabled="true">
153 | 			<!-- Valid values are "true" or "false"
154 | 			     Invalid values or missing elements will be treated as "false"
155 | 			-->
156 | 			<ApplyIPWhitelist>true</ApplyIPWhitelist>
157 | 			<!-- Enabling this will cause recommended connection strings to be commented out -->
158 | 			<DeactivateConnectionStrings>true</DeactivateConnectionStrings>
159 | 			<!-- Enabling this setting causes some files on the CD server to have ".disabled" concatenated to
160 | 			     their filename. Other files necessary for configuring a CD such as the
161 | 			     SwitchMasterToWeb.config file will be enabled. The files changed are from the recommendations here:
162 | 			     https://doc.sitecore.net/sitecore%20experience%20platform/xdb%20configuration/configure%20a%20content%20delivery%20server
163 | 			-->
164 | 			<ConfigureFilesForCD>true</ConfigureFilesForCD>
165 | 			<!-- Denies anonymous users from accessing certain directories per Sitecore's recommendations -->
166 | 			<PreventAnonymousAccess>true</PreventAnonymousAccess>
167 | 			<!-- Prevent the execution of scripts or programs in the upload and temp folders -->
168 | 			<DenyExecutePermission>true</DenyExecutePermission>
169 | 			<!-- Enabling this setting prevents uploading files outside of the Sitecore client -->
170 | 			<DisableUploadWatcher>true</DisableUploadWatcher>
171 | 			<!-- If you have implemented custom code that uses ASP.NET Web API attribute routing, to avoid errors, disable the following -->
172 | 			<DisableExperienceAnalyticsAssemblies>true</DisableExperienceAnalyticsAssemblies>
173 | 			<!-- Remove PhantomJs from CD per Sitecore's recommendations -->
174 | 			<RemovePhantomJs>true</RemovePhantomJs>
175 | 			<!-- Disables Telerik UI Handlers on CD server. -->
176 | 			<DisableTelerikControls>true</DisableTelerikControls>
177 | 		</CDServerSettings>
178 | 
179 | 		<!-- Media Request Protection - Applied to CM and CD Servers -->
180 | 		<MediaRequestProtection>
181 | 			<!-- In a multi-instance setup, use the same value for Media.RequestProtection.SharedSecret on every instance.
182 | 				 SharedSecret is required. If no value is provided, Sitecore default value will be used. -->
183 | 			<SharedSecret></SharedSecret>
184 | 			<!-- Specifies whether the media request protection feature will output detailed information to the Sitecore log file.
185 | 				 If no value is provided, Sitecore default value (true) will be used. -->
186 | 			<LoggingEnabled>true</LoggingEnabled>
187 | 		</MediaRequestProtection>
188 | 
189 | 		<!-- Hardened directories in IIS will deny all clients except the following IPs -->
190 | 		<IPWhiteList>
191 | 			<IP>127.0.0.1</IP>
192 | 			<IP>10.10.20.7</IP>
193 | 			<IP>10.10.20.11</IP>
194 | 		</IPWhiteList>
195 | 
196 | 		<SessionStateProvider>
197 | 			<!-- Valid values for Private and Shared are:
198 | 			       - InProc
199 | 			       - MSSQL (except for Shared on a CM!)
200 | 			       - Mongo (currently not supported by the installer)
201 | 			-->
202 | 			<Private>mssql</Private>
203 | 			<Shared>mssql</Shared>
204 | 		</SessionStateProvider>
205 | 
206 | 		<Solr>
207 | 			<!-- If provided, the installer will modify the
208 | 			     Sitecore.ContentSearch.Solr.DefaultIndexConfiguration.config.example file to use the given address
209 | 			-->
210 | 			<ServiceBaseAddress>http://solr5:8888/solr</ServiceBaseAddress>
211 | 		</Solr>
212 | 
213 | 		<!-- This section determines how the connection strings for for MongoDB will be formed. Any values
214 | 			 left blank will not be used. The settings below adhere to MongoDB's connection string format
215 | 			 specification: https://docs.mongodb.org/manual/reference/connection-string/
216 | 
217 | 			 If this section is not enabled, it will be ignored.
218 | 		-->
219 | 		<MongoDb enabled="true">
220 | 			<!-- Optional, won't be used if blank -->
221 | 			<Credentials>
222 | 				<Username>someuser</Username>
223 | 				<Password>somepassword</Password>
224 | 			</Credentials>
225 | 			<!-- At least one <Host> is required, each <Host> must specify a <HostName> and an optional <Port> -->
226 | 			<Hosts>
227 | 				<Host>
228 | 					<HostName>node1.company.com</HostName>
229 | 					<Port>27017</Port>
230 | 				</Host>
231 | 				<Host>
232 | 					<HostName>node2.company.com</HostName>
233 | 					<Port>9999</Port>
234 | 				</Host>
235 | 			</Hosts>
236 | 			<!-- This setting's value will be appended to the connection string's URI. The format should be as a
237 | 			     query string.
238 | 			-->
239 | 			<Options>?authMechanism=PLAIN&amp;authSource=$external&amp;replicaSet=mymongoset</Options>
240 | 		</MongoDb>
241 | 
242 | 	</WebServer>
243 | 		<!-- If disabled the script will skip ALL database related operations.
244 | 			   - No SQL server connection tests
245 | 			   - Databases files will not be copied or attached
246 | 			   - User mappings, permissions will not be set
247 | 			   - Autogrowth will not be set on web database (relevant to parallel publishing)
248 | 
249 | 			 Regardless the information in this section will still be used to form connection string values.
250 | 			 Thus, ensure that the database names are always accurate as well as the SQL server name and data
251 | 			 access account information.
252 | 			Type: Azure, Local
253 | 			Using Azure requires the installation of the Dacfx
254 | 			https://www.microsoft.com/en-us/download/confirmation.aspx?id=55255
255 | 		-->
256 | 		<Database type="Local" enabled="true">
257 | 			<Azure>
258 | 				<SQLPackagePath>C:\Program Files\Microsoft SQL Server\140\DAC\bin\sqlpackage.exe</SQLPackagePath>
259 | 				<SQLResourceGroup></SQLResourceGroup>
260 | 				<SQLEdition></SQLEdition>
261 | 				<SQLMaxSize></SQLMaxSize> <!-- in Bytes -->
262 | 				<SQLServiceObjective></SQLServiceObjective>
263 | 			</Azure>
264 | 		<!-- Valid values are "true" or "false" Invalid values or missing element will be treated as "false"
265 | 		     Note that even if you do not install the database, database mappings and permissions will still
266 | 		     be written.
267 | 		-->
268 | 		<InstallDatabase>false</InstallDatabase>
269 | 
270 | 		<!-- Do not edit this list unless you know what you are doing! :) This list represents the all of
271 | 		     the default databases used by Sitecore.
272 | 		-->
273 | 		<DatabaseNames>
274 | 			<name>Core</name>
275 | 			<name>Master</name>
276 | 			<name>Web</name>
277 | 			<name>Sessions</name>
278 | 			<name>Reporting</name>
279 | 		</DatabaseNames>
280 | 
281 | 		<!-- Add <copy> elements for each duplicate web database to be created -->
282 | 		<WebDatabaseCopies>
283 | 			<!-- Setting the connectionStringName attribute will assign that value to the "name" attribute
284 | 			     of the connection string for this databse. For example, if the connectionStringName is "web"
285 | 			     then the web connection string will point to the preview database. This is useful for creating
286 | 			     a preview-type CD server that serves content out of a different database than the normal, web
287 | 			     database. If the attribute is missing or does not have a value, then the name of the copy
288 | 			     database will be used to create the name of the connection string.
289 | 
290 | 			     NOTE: The "web" database is referred to in many places in Sitecore’s configuration:
291 | 				   - Database definitions
292 | 				   - Agents
293 | 				   - Index definitions
294 | 				   - Indexing strategies
295 | 				   - Site definitions
296 | 
297 | 			     Thus, you will need to think about patching the Sitecore's .config files to address this behavior.
298 | 
299 | 				 * On the preview CD server, by replacing the "web" connection string’s database with a preview
300 | 				 database, you can avoid much of this configuration work.  If you are using Lucene, you
301 | 				 shouldn't need to do anything else. If you are using Solr, I STRONGLY recommend you create
302 | 				 dedicated 'preview' versions of web indexes and indexing strategies.
303 | 
304 | 				 * On the CM server, you should consider doing the following:
305 | 				   - Configuring a <database> element similar to the web's
306 | 				   - If you want schedule periodic publishing, then create an <agent> for Sitecore.Tasks.PublishAgent
307 | 				     to publish to your preview database
308 | 				   - If you use WebDAV, consider adding your preview database to the
309 | 				     Sitecore.Tasks.CleanupFDAObsoleteMediaData <agent>
310 | 				   - Create 'preview' version of the onPublishEndAsync and onPublishEndAsyncSingleInstance index
311 | 				     update strategies
312 | 				   - Create Index definitions for the 'preview' versions of your 'web' indexes. This is especially
313 | 				     important if you use Solr!
314 | 			-->
315 | 		</WebDatabaseCopies>
316 | 
317 | 		<!-- The format is: {sqlservername[\instancename]}[,{port}]
318 | 			 Examples
319 | 			 - vmwebdev01
320 | 			 - vmwebdev01,1433
321 | 			 - vmwebdev01\myinstance
322 | 			 - vmwebdev01\myinstance,1433
323 | 			 Azure
324 |  			 - exampleDB.database.windows.net
325 | 		-->
326 | 		<SqlServerName>vmwebdev01,1433</SqlServerName>
327 | 
328 | 		<!-- This login is used to attach databases and assign roles in SQL. The login must have the sysadmin
329 | 			 server role.
330 | 		-->
331 | 		<SqlLoginForInstall>SC_InstallAccount</SqlLoginForInstall>
332 | 		<SqlLoginForInstallPassword>P@ssword</SqlLoginForInstallPassword>
333 | 
334 | 		<!-- If specified, this login will be used in connection strings. Only SQL logins are valid. -->
335 | 		<SqlLoginForDataAccess></SqlLoginForDataAccess>
336 | 		<SqlLoginForDataAccessPassword></SqlLoginForDataAccessPassword>
337 | 
338 | 		<!-- If true, then the ApplicationPoolIdentity will be used for the SQL login rather than
339 | 		     SqlLoginForDataAccess. This setting requires a domain account is specified for the
340 | 		     ApplicationPoolIdentity.
341 | 		-->
342 | 		<UseWindowsAuthenticationForSqlDataAccess>true</UseWindowsAuthenticationForSqlDataAccess>
343 | 
344 | 		<DatabaseInstallPath>
345 | 			<DataFiles>
346 | 				<!-- Must be defined, and folder must exist. The SQL instance must have FullControl over the folder.
347 | 					 This value is used to attach the databases in SQL. If the Unc value is missing, this is also the
348 | 					 path used as the destination for SQL database file copying.
349 | 				-->
350 | 				<Local>C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\installdemo data files</Local>
351 | 
352 | 				<!-- If defined this path will be used to copy database files into the file system of the
353 | 					 SQL server.
354 | 				-->
355 | 				<Unc>\\VMWEBDEV01\installdemo data files</Unc>
356 | 			</DataFiles>
357 | 
358 | 			<!-- This sectional is optional. If undefined, then log files will be installed in the same location
359 | 				 the same location as the data files defined above.
360 | 			-->
361 | 			<LogFiles>
362 | 				<!-- Must be defined, and folder must exist. The SQL instance must have FullControl over the folder.
363 | 					 This value is used to attach the databases in SQL. If the Unc value is missing, this is also the
364 | 					 path used as the destination for SQL database file copying.
365 | 				-->
366 | 				<Local>C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\installdemo log files</Local>
367 | 
368 | 				<!-- If defined this path will be used to copy database files into the file system of the
369 | 					 SQL server.
370 | 				-->
371 | 				<Unc>\\VMWEBDEV01\installdemo log files</Unc>
372 | 			</LogFiles>
373 | 		</DatabaseInstallPath>
374 | 
375 | 		<DatabaseNamePrefix>InstallDemo_Sitecore_</DatabaseNamePrefix>
376 | 
377 | 	</Database>
378 | 
379 | </InstallSettings>
380 | 


--------------------------------------------------------------------------------
/install.ExamplePreviewCD.config:
--------------------------------------------------------------------------------
  1 | <?xml version="1.0" encoding="utf-8"?>
  2 | <InstallSettings>
  3 | 	<!-- PreReqs
  4 | 	https://docs.microsoft.com/en-us/sql/relational-databases/scripting/sql-server-powershell
  5 | 	https://www.microsoft.com/en-us/download/details.aspx?id=52676
  6 | 	Install-Module -Name ImportExcel
  7 | 	Install-Module -Name AzureRM.sql
  8 | 	-->
  9 | 	<!-- If blank, no log file will be generated. The log file location will be the
 10 | 	     SitecoreInstallFolder.
 11 | 	-->
 12 | 	<LogFileName>InstallLog.txt</LogFileName>
 13 | 
 14 | 	<!-- Path of downloaded zip file from Sitecore -->
 15 | 	<SitecoreZipPath>C:\Users\sp_farmadmin\AppData\Roaming\Sitecore\Sitecore Instance Manager\Repository\Sitecore 8.2 rev. 161221.zip</SitecoreZipPath>
 16 | 
 17 | 	<!-- Path of downloaded Sitecore configuration spreadsheet.
 18 | 		 This setting is required and used for installing Sitecore 8.2
 19 | 		 Find the spreadsheet here: https://doc.sitecore.net/sitecore_experience_platform/setting_up_and_maintaining/xdb/configuring_servers/server_configuration_resources
 20 | 	-->
 21 | 	<SitecoreConfigSpreadsheetPath>C:\temp\Config Enable-Disable Sitecore_8.2 Update2.xlsx</SitecoreConfigSpreadsheetPath>
 22 | 
 23 | 	<!-- If true then user prompts will be bypassed. For example, if the script cannot determine that SQL
 24 | 	     has FullControl over database files, then a dialog prompt will be displayed asking if the script
 25 | 	     should continue if this property is set to false.
 26 | 	-->
 27 | 	<SuppressPrompts>true</SuppressPrompts>
 28 | 
 29 | 	<WebServer>
 30 | 		<LicenseFilePath>C:\ArkeSitecoreLicense\license.xml</LicenseFilePath>
 31 | 		<SitecoreInstallRoot>C:\inetpub\wwwroot</SitecoreInstallRoot>
 32 | 		<!-- Folder will be created at the SitecoreInstallRoot if it does not already exist. -->
 33 | 		<SitecoreInstallFolder>PreviewCD</SitecoreInstallFolder>
 34 | 		<!-- Select a name for the last folder under /App_Config/Include
 35 | 		     This is the folder where all config files which must be patched last should be kept (e.g.
 36 | 		     SwitchMasterToWeb.config file.) For Sitecore 8.1, if no name is supplied then the installer
 37 | 		     will use the Z.SwitchMasterToWeb folder.
 38 | 		-->
 39 | 		<LastChildFolderOfIncludeDirectory>zzzMustBeLast</LastChildFolderOfIncludeDirectory>
 40 | 		<!-- Encrypt the contents of the ConnectionStrings.config file -->
 41 | 		<EncryptConnectionStrings>true</EncryptConnectionStrings>
 42 | 
 43 | 		<IISWebSiteName>PreviewCD</IISWebSiteName>
 44 | 		<DefaultRuntimeVersion>v4.0</DefaultRuntimeVersion>
 45 | 		<!-- Valid values are:
 46 | 		      - NetworkService
 47 | 		      - ApplicationPoolIdentity
 48 | 		      - Any domain account in the form <domain>\<username>
 49 | 
 50 | 		     If you supply a domain account, you must also provide a valid password for the account.
 51 | 		-->
 52 | 		<AppPoolIdentity>EVADEV\SCTest_AppPool</AppPoolIdentity>
 53 | 		<AppPoolIdentityPassword>P@ssword</AppPoolIdentityPassword>
 54 | 		<IISBindings>
 55 | 			<Binding IP="*" Port="80" HostHeader="previewcd" AddToHostsFile="true" />
 56 | 			<Binding IP="10.10.20.11" Port="80" HostHeader="prevcd" AddToHostsFile="false" />
 57 | 			<Binding IP="10.10.20.11" Port="80" HostHeader="pcd" />
 58 | 		</IISBindings>
 59 | 
 60 | 		<!-- Provide a unique name for this instance of Sitecore. This value should be set any time you have mulitple CD or CM servers. -->
 61 | 		<SitecoreInstanceName>PreviewCD1</SitecoreInstanceName>
 62 | 
 63 | 		<!-- This section controls settings for Sitecore's Analytics -->
 64 | 		<Analytics>
 65 | 			<ClusterName></ClusterName>
 66 | 			<HostName></HostName>
 67 | 		</Analytics>
 68 | 
 69 | 		<!-- This value will be written to the reporting.api connection string. Only applies to Sitecore 8.2 -->
 70 | 		<ReportingApiKey>12345678901234567890123456789012</ReportingApiKey>
 71 | 		
 72 | 		<!-- Sitecore recommends changing the default password hash algorithm from SHA1 to SHA512
 73 | 		
 74 | 			For user management, Sitecore uses the Microsoft ASP.NET membership provider by default. 
 75 | 
 76 | 			*** IMPORTANT! ***
 77 | 			The Microsoft ASP.NET membership provider does not provide a facility for upgrading to a different hash algorithm after you have created 
 78 | 			user accounts. IF YOU CHANGE THE HASH ALGORITHM, EXISTING USERS CAN NO LONGER LOG INTO THE SYSTEM AND MUST CREATE A NEW PASSWORD.
 79 | 			
 80 | 			Valid values are:
 81 | 			- "" 
 82 | 			- a supported hash algorithm from the System.Security.Cryptography.CryptoConfig class : 
 83 | 			https://msdn.microsoft.com/en-us/library/system.security.cryptography.cryptoconfig(v=vs.110).aspx 
 84 | 		-->
 85 | 		<PasswordHashAlgorithm>SHA512</PasswordHashAlgorithm>
 86 | 
 87 | 		<CMServerSettings enabled="false">
 88 | 			<!-- If this value is non-empty, then admin's password will be set to this value -->
 89 | 			<DefaultSitecoreAdminPassword></DefaultSitecoreAdminPassword>
 90 | 
 91 | 			<!-- Add an Encryption Key for the Telerik controls 
 92 | 				  http://docs.telerik.com/devtools/aspnet-ajax/controls/asyncupload/security
 93 | 				 If using load-balanced CM servers, the value must match on both servers.
 94 | 			-->
 95 | 			<TelerikEncryptionKey></TelerikEncryptionKey>
 96 | 
 97 | 			<!-- Use these settings to dedicate Sitecore instance as the Publishing server. This is required
 98 | 			     when you are using load-balanced CM servers.
 99 | 			-->
100 | 			<Publishing enabled="false">
101 | 				<!-- This setting is ALWAYS applied to a CM server even if publishing is disabled. Therefore,
102 | 				     for an isolated CM you may leave this value blank or make sure it matches the CM
103 | 				     InstanceName
104 | 				-->
105 | 				<PublishingInstance></PublishingInstance>
106 |                 <!-- Use these settings to enable IIS Application Initialization on a dedicated publishing instance.
107 |                      Setting enabled to true will:
108 |                         - Enable the Application Initialization feature on the web server
109 |                         - Add preloadEnabled="true" to the application configuration
110 |                         - Add applicationInitialization node to the system.webserver
111 | 						- Set doAppInitAfterRestart to true
112 |                         - Set the AppPool startMode to "AlwaysRunning"
113 |                         - Set the AppPool IdleTimeout to 0
114 |                         - Set the AppPool Recycling regular time interval to 0
115 |                      Valid values are "true" or "false"
116 | 				-->
117 |                 <ApplicationInitializationEnabled>false</ApplicationInitializationEnabled>
118 |                 <!-- Timeout length in minutes for IIS App Pool
119 |                      If enabled, Application Intialization will override this value with 0.
120 |                  -->
121 | 				<AppPoolIdleTimeout>600</AppPoolIdleTimeout>
122 | 				<!-- If this setting is false, the keepalive task will not run and the publishing server will get cold. -->
123 | 				<DisableScheduledTaskExecution>true</DisableScheduledTaskExecution>
124 | 				<Parallel enabled="false">
125 | 					<!-- If set, the autogrowth for data and log files of the web database and any copy of the
126 | 					     web database will be based on a fixed size of MB rather than a percentage. This follow
127 | 					     recommendations from Sitecore. Recommended values range from 30 to 50.
128 | 					     Valid values range from 10 to 100.
129 | 					-->
130 | 					<WebDatabaseAutoGrowthInMB>30</WebDatabaseAutoGrowthInMB>
131 | 					<MaxDegreesOfParallelism>4</MaxDegreesOfParallelism>
132 | 				</Parallel>
133 | 			</Publishing>
134 | 			<!-- Use these settings to dedicate Sitecore instance as a Processing server. -->
135 | 			<Processing enabled="false">
136 | 				<!-- Valid values are "true" or "false"
137 | 					 Invalid values or missing elements will be treated as "false"
138 | 				-->
139 | 				<ApplyIPWhitelist>true</ApplyIPWhitelist>
140 | 				<!-- Enabling this will cause recommended connection strings to be commented out -->
141 | 				<DeactivateConnectionStrings>true</DeactivateConnectionStrings>
142 | 				<!-- Enabling this setting causes some files on the Processing server to have ".disabled" concatenated to
143 | 					 their filename. Other files necessary for configuring a Processing file will be enabled. The files changed are from the recommendations here:
144 | 					 https://doc.sitecore.net/sitecore_experience_platform/setting_up_and_maintaining/xdb/configuring_servers/configure_a_processing_server
145 | 				-->
146 | 				<ConfigureFilesForProcessing>true</ConfigureFilesForProcessing>
147 | 				<!-- Denies anonymous users from accessing certain directories per Sitecore's recommendations -->
148 | 				<PreventAnonymousAccess>true</PreventAnonymousAccess>
149 | 			</Processing>
150 | 		</CMServerSettings>
151 | 
152 | 		<CDServerSettings enabled="true">
153 | 			<!-- Valid values are "true" or "false"
154 | 			     Invalid values or missing elements will be treated as "false"
155 | 			-->
156 | 			<ApplyIPWhitelist>true</ApplyIPWhitelist>
157 | 			<!-- Enabling this will cause recommended connection strings to be commented out -->
158 | 			<DeactivateConnectionStrings>true</DeactivateConnectionStrings>
159 | 			<!-- Enabling this setting causes some files on the CD server to have ".disabled" concatenated to
160 | 			     their filename. Other files necessary for configuring a CD such as the
161 | 			     SwitchMasterToWeb.config file will be enabled. The files changed are from the recommendations here:
162 | 			     https://doc.sitecore.net/sitecore%20experience%20platform/xdb%20configuration/configure%20a%20content%20delivery%20server
163 | 			-->
164 | 			<ConfigureFilesForCD>true</ConfigureFilesForCD>
165 | 			<!-- Denies anonymous users from accessing certain directories per Sitecore's recommendations -->
166 | 			<PreventAnonymousAccess>true</PreventAnonymousAccess>
167 | 			<!-- Prevent the execution of scripts or programs in the upload and temp folders -->
168 | 			<DenyExecutePermission>true</DenyExecutePermission>
169 | 			<!-- Enabling this setting prevents uploading files outside of the Sitecore client -->
170 | 			<DisableUploadWatcher>true</DisableUploadWatcher>
171 | 			<!-- If you have implemented custom code that uses ASP.NET Web API attribute routing, to avoid errors, disable the following -->
172 | 			<DisableExperienceAnalyticsAssemblies>true</DisableExperienceAnalyticsAssemblies>
173 | 			<!-- Remove PhantomJs from CD per Sitecore's recommendations -->
174 | 			<RemovePhantomJs>true</RemovePhantomJs>
175 | 			<!-- Disables Telerik UI Handlers on CD server. -->
176 | 			<DisableTelerikControls>true</DisableTelerikControls>
177 | 		</CDServerSettings>
178 | 
179 | 		<!-- Media Request Protection - Applied to CM and CD Servers -->
180 | 		<MediaRequestProtection>
181 | 			<!-- In a multi-instance setup, use the same value for Media.RequestProtection.SharedSecret on every instance.
182 | 				 SharedSecret is required. If no value is provided, Sitecore default value will be used. -->
183 | 			<SharedSecret></SharedSecret>
184 | 			<!-- Specifies whether the media request protection feature will output detailed information to the Sitecore log file.
185 | 				 If no value is provided, Sitecore default value (true) will be used. -->
186 | 			<LoggingEnabled>true</LoggingEnabled>
187 | 		</MediaRequestProtection>
188 | 
189 | 		<!-- Hardened directories in IIS will deny all clients except the following IPs -->
190 | 		<IPWhiteList>
191 | 			<IP>127.0.0.1</IP>
192 | 			<IP>10.10.20.7</IP>
193 | 			<IP>10.10.20.11</IP>
194 | 		</IPWhiteList>
195 | 
196 | 		<SessionStateProvider>
197 | 			<!-- Valid values for Private and Shared are:
198 | 			       - InProc
199 | 			       - MSSQL (except for Shared on a CM!)
200 | 			       - Mongo (currently not supported by the installer)
201 | 			-->
202 | 			<Private>inproc</Private>
203 | 			<Shared>inproc</Shared>
204 | 		</SessionStateProvider>
205 | 
206 | 		<Solr>
207 | 			<!-- If provided, the installer will modify the
208 | 			     Sitecore.ContentSearch.Solr.DefaultIndexConfiguration.config.example file to use the given address
209 | 			-->
210 | 			<ServiceBaseAddress>http://solr5:8888/solr</ServiceBaseAddress>
211 | 		</Solr>
212 | 
213 | 		<!-- This section determines how the connection strings for for MongoDB will be formed. Any values
214 | 			 left blank will not be used. The settings below adhere to MongoDB's connection string format
215 | 			 specification: https://docs.mongodb.org/manual/reference/connection-string/
216 | 
217 | 			 If this section is not enabled, it will be ignored.
218 | 		-->
219 | 		<MongoDb enabled="true">
220 | 			<!-- Optional, won't be used if blank -->
221 | 			<Credentials>
222 | 				<Username>someuser</Username>
223 | 				<Password>somepassword</Password>
224 | 			</Credentials>
225 | 			<!-- At least one <Host> is required, each <Host> must specify a <HostName> and an optional <Port> -->
226 | 			<Hosts>
227 | 				<Host>
228 | 					<HostName>node1.company.com</HostName>
229 | 					<Port>27017</Port>
230 | 				</Host>
231 | 				<Host>
232 | 					<HostName>node2.company.com</HostName>
233 | 					<Port>9999</Port>
234 | 				</Host>
235 | 			</Hosts>
236 | 			<!-- This setting's value will be appended to the connection string's URI. The format should be as a
237 | 			     query string.
238 | 			-->
239 | 			<Options>?authMechanism=PLAIN&amp;authSource=$external&amp;replicaSet=mymongoset</Options>
240 | 		</MongoDb>
241 | 
242 | 	</WebServer>
243 | 		<!-- If disabled the script will skip ALL database related operations.
244 | 			   - No SQL server connection tests
245 | 			   - Databases files will not be copied or attached
246 | 			   - User mappings, permissions will not be set
247 | 			   - Autogrowth will not be set on web database (relevant to parallel publishing)
248 | 
249 | 			 Regardless the information in this section will still be used to form connection string values.
250 | 			 Thus, ensure that the database names are always accurate as well as the SQL server name and data
251 | 			 access account information.
252 | 			Type: Azure, Local
253 | 			Using Azure requires the installation of the Dacfx
254 | 			https://www.microsoft.com/en-us/download/confirmation.aspx?id=55255
255 | 		-->
256 | 		<Database type="Azure" enabled="true">
257 | 			<Azure>
258 | 				<SQLPackagePath>C:\Program Files\Microsoft SQL Server\140\DAC\bin\sqlpackage.exe</SQLPackagePath>
259 | 				<SQLResourceGroup></SQLResourceGroup>
260 | 				<SQLEdition></SQLEdition>
261 | 				<SQLMaxSize></SQLMaxSize> <!-- in Bytes -->
262 | 				<SQLServiceObjective></SQLServiceObjective>
263 | 			</Azure>
264 | 		<!-- Valid values are "true" or "false" Invalid values or missing element will be treated as "false"
265 | 		     Note that even if you do not install the database, database mappings and permissions will still
266 | 		     be written.
267 | 		-->
268 | 		<InstallDatabase>false</InstallDatabase>
269 | 
270 | 		<!-- Do not edit this list unless you know what you are doing! :) This list represents the all of
271 | 		     the default databases used by Sitecore.
272 | 		-->
273 | 		<DatabaseNames>
274 | 			<name>Core</name>
275 | 			<name>Master</name>
276 | 			<name>Web</name>
277 | 			<name>Sessions</name>
278 | 			<name>Reporting</name>
279 | 		</DatabaseNames>
280 | 
281 | 		<!-- Add <copy> elements for each duplicate web database to be created -->
282 | 		<WebDatabaseCopies>
283 | 			<!-- Setting the connectionStringName attribute will assign that value to the "name" attribute
284 | 			     of the connection string for this databse. For example, if the connectionStringName is "web"
285 | 			     then the web connection string will point to the preview database. This is useful for creating
286 | 			     a preview-type CD server that serves content out of a different database than the normal, web
287 | 			     database. If the attribute is missing or does not have a value, then the name of the copy
288 | 			     database will be used to create the name of the connection string.
289 | 
290 | 			     NOTE: The "web" database is referred to in many places in Sitecore’s configuration:
291 | 				   - Database definitions
292 | 				   - Agents
293 | 				   - Index definitions
294 | 				   - Indexing strategies
295 | 				   - Site definitions
296 | 
297 | 			     Thus, you will need to think about patching the Sitecore's .config files to address this behavior.
298 | 
299 | 				 * On the preview CD server, by replacing the "web" connection string’s database with a preview
300 | 				 database, you can avoid much of this configuration work.  If you are using Lucene, you
301 | 				 shouldn't need to do anything else. If you are using Solr, I STRONGLY recommend you create
302 | 				 dedicated 'preview' versions of web indexes and indexing strategies.
303 | 
304 | 				 * On the CM server, you should consider doing the following:
305 | 				   - Configuring a <database> element similar to the web's
306 | 				   - If you want schedule periodic publishing, then create an <agent> for Sitecore.Tasks.PublishAgent
307 | 				     to publish to your preview database
308 | 				   - If you use WebDAV, consider adding your preview database to the
309 | 				     Sitecore.Tasks.CleanupFDAObsoleteMediaData <agent>
310 | 				   - Create 'preview' version of the onPublishEndAsync and onPublishEndAsyncSingleInstance index
311 | 				     update strategies
312 | 				   - Create Index definitions for the 'preview' versions of your 'web' indexes. This is especially
313 | 				     important if you use Solr!
314 | 			-->
315 | 			<copy connectionStringName="web">Preview</copy>
316 | 		</WebDatabaseCopies>
317 | 
318 | 		<!-- The format is: {sqlservername[\instancename]}[,{port}]
319 | 			 Examples
320 | 			 - vmwebdev01
321 | 			 - vmwebdev01,1433
322 | 			 - vmwebdev01\myinstance
323 | 			 - vmwebdev01\myinstance,1433
324 | 			 Azure
325 |  			 - exampleDB.database.windows.net
326 | 		-->
327 | 		<SqlServerName>vmwebdev01,1433</SqlServerName>
328 | 
329 | 		<!-- This login is used to attach databases and assign roles in SQL. The login must have the sysadmin
330 | 			 server role.
331 | 		-->
332 | 		<SqlLoginForInstall>SC_InstallAccount</SqlLoginForInstall>
333 | 		<SqlLoginForInstallPassword>P@ssword</SqlLoginForInstallPassword>
334 | 
335 | 		<!-- If specified, this login will be used in connection strings. Only SQL logins are valid. -->
336 | 		<SqlLoginForDataAccess></SqlLoginForDataAccess>
337 | 		<SqlLoginForDataAccessPassword></SqlLoginForDataAccessPassword>
338 | 
339 | 		<!-- If true, then the ApplicationPoolIdentity will be used for the SQL login rather than
340 | 		     SqlLoginForDataAccess. This setting requires a domain account is specified for the
341 | 		     ApplicationPoolIdentity.
342 | 		-->
343 | 		<UseWindowsAuthenticationForSqlDataAccess>true</UseWindowsAuthenticationForSqlDataAccess>
344 | 
345 | 		<DatabaseInstallPath>
346 | 			<DataFiles>
347 | 				<!-- Must be defined, and folder must exist. The SQL instance must have FullControl over the folder.
348 | 					 This value is used to attach the databases in SQL. If the Unc value is missing, this is also the
349 | 					 path used as the destination for SQL database file copying.
350 | 				-->
351 | 				<Local>C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\installdemo data files</Local>
352 | 
353 | 				<!-- If defined this path will be used to copy database files into the file system of the
354 | 					 SQL server.
355 | 				-->
356 | 				<Unc>\\VMWEBDEV01\installdemo data files</Unc>
357 | 			</DataFiles>
358 | 
359 | 			<!-- This sectional is optional. If undefined, then log files will be installed in the same location
360 | 				 the same location as the data files defined above.
361 | 			-->
362 | 			<LogFiles>
363 | 				<!-- Must be defined, and folder must exist. The SQL instance must have FullControl over the folder.
364 | 					 This value is used to attach the databases in SQL. If the Unc value is missing, this is also the
365 | 					 path used as the destination for SQL database file copying.
366 | 				-->
367 | 				<Local>C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\installdemo log files</Local>
368 | 
369 | 				<!-- If defined this path will be used to copy database files into the file system of the
370 | 					 SQL server.
371 | 				-->
372 | 				<Unc>\\VMWEBDEV01\installdemo log files</Unc>
373 | 			</LogFiles>
374 | 		</DatabaseInstallPath>
375 | 
376 | 		<DatabaseNamePrefix>InstallDemo_Sitecore_</DatabaseNamePrefix>
377 | 
378 | 	</Database>
379 | 
380 | </InstallSettings>
381 | 


--------------------------------------------------------------------------------
/install.ExampleCM.config:
--------------------------------------------------------------------------------
  1 | <?xml version="1.0" encoding="utf-8"?>
  2 | <InstallSettings>
  3 | 	<!-- PreReqs
  4 | 	https://docs.microsoft.com/en-us/sql/relational-databases/scripting/sql-server-powershell
  5 | 	https://www.microsoft.com/en-us/download/details.aspx?id=52676
  6 | 	Install-Module -Name ImportExcel
  7 | 	Install-Module -Name AzureRM.sql
  8 | 	-->
  9 | 	<!-- If blank, no log file will be generated. The log file location will be the
 10 | 	     SitecoreInstallFolder.
 11 | 	-->
 12 | 	<LogFileName>InstallLog.txt</LogFileName>
 13 | 
 14 | 	<!-- Path of downloaded zip file from Sitecore -->
 15 | 	<SitecoreZipPath>C:\Users\sp_farmadmin\AppData\Roaming\Sitecore\Sitecore Instance Manager\Repository\Sitecore 8.2 rev. 161221.zip</SitecoreZipPath>
 16 | 
 17 | 	<!-- Path of downloaded Sitecore configuration spreadsheet.
 18 | 		 This setting is required and used for installing Sitecore 8.2
 19 | 		 Find the spreadsheet here: https://doc.sitecore.net/sitecore_experience_platform/setting_up_and_maintaining/xdb/configuring_servers/server_configuration_resources
 20 | 	-->
 21 | 	<SitecoreConfigSpreadsheetPath>C:\temp\Config Enable-Disable Sitecore_8.2 Update2.xlsx</SitecoreConfigSpreadsheetPath>
 22 | 
 23 | 	<!-- If true then user prompts will be bypassed. For example, if the script cannot determine that SQL
 24 | 	     has FullControl over database files, then a dialog prompt will be displayed asking if the script
 25 | 	     should continue if this property is set to false.
 26 | 	-->
 27 | 	<SuppressPrompts>true</SuppressPrompts>
 28 | 
 29 | 	<WebServer>
 30 | 		<LicenseFilePath>C:\ArkeSitecoreLicense\license.xml</LicenseFilePath>
 31 | 		<SitecoreInstallRoot>C:\inetpub\wwwroot</SitecoreInstallRoot>
 32 | 		<!-- Folder will be created at the SitecoreInstallRoot if it does not already exist. -->
 33 | 		<SitecoreInstallFolder>ExampleCM</SitecoreInstallFolder>
 34 | 		<!-- Select a name for the last folder under /App_Config/Include
 35 | 		     This is the folder where all config files which must be patched last should be kept (e.g.
 36 | 		     SwitchMasterToWeb.config file.) For Sitecore 8.1, if no name is supplied then the installer
 37 | 		     will use the Z.SwitchMasterToWeb folder.
 38 | 		-->
 39 | 		<LastChildFolderOfIncludeDirectory>zzzMustBeLast</LastChildFolderOfIncludeDirectory>
 40 | 		<!-- Encrypt the contents of the ConnectionStrings.config file -->
 41 | 		<EncryptConnectionStrings>true</EncryptConnectionStrings>
 42 | 
 43 | 		<IISWebSiteName>ExampleCM</IISWebSiteName>
 44 | 		<DefaultRuntimeVersion>v4.0</DefaultRuntimeVersion>
 45 | 		<!-- Valid values are:
 46 | 		      - NetworkService
 47 | 		      - ApplicationPoolIdentity
 48 | 		      - Any domain account in the form <domain>\<username>
 49 | 
 50 | 		     If you supply a domain account, you must also provide a valid password for the account.
 51 | 		-->
 52 | 		<AppPoolIdentity>EVADEV\SCTest_AppPool</AppPoolIdentity>
 53 | 		<AppPoolIdentityPassword>P@ssword</AppPoolIdentityPassword>
 54 | 		<IISBindings>
 55 | 			<Binding IP="*" Port="80" HostHeader="examplecm" AddToHostsFile="true" />
 56 | 			<Binding IP="10.10.20.11" Port="80" HostHeader="excm" AddToHostsFile="false" />
 57 | 			<Binding IP="10.10.20.11" Port="80" HostHeader="ecm" />
 58 | 		</IISBindings>
 59 | 
 60 | 		<!-- Provide a unique name for this instance of Sitecore. This value should be set any time you have mulitple CD or CM servers. -->
 61 | 		<SitecoreInstanceName>ExampleCM1</SitecoreInstanceName>
 62 | 
 63 | 		<!-- This section controls settings for Sitecore's Analytics -->
 64 | 		<Analytics>
 65 | 			<ClusterName></ClusterName>
 66 | 			<HostName></HostName>
 67 | 		</Analytics>
 68 | 
 69 | 		<!-- This value will be written to the reporting.api connection string. Only applies to Sitecore 8.2 -->
 70 | 		<ReportingApiKey>12345678901234567890123456789012</ReportingApiKey>
 71 | 		
 72 | 		<!-- Sitecore recommends changing the default password hash algorithm from SHA1 to SHA512
 73 | 		
 74 | 			For user management, Sitecore uses the Microsoft ASP.NET membership provider by default. 
 75 | 
 76 | 			*** IMPORTANT! ***
 77 | 			The Microsoft ASP.NET membership provider does not provide a facility for upgrading to a different hash algorithm after you have created 
 78 | 			user accounts. IF YOU CHANGE THE HASH ALGORITHM, EXISTING USERS CAN NO LONGER LOG INTO THE SYSTEM AND MUST CREATE A NEW PASSWORD.
 79 | 			
 80 | 			Valid values are:
 81 | 			- "" 
 82 | 			- a supported hash algorithm from the System.Security.Cryptography.CryptoConfig class : 
 83 | 			https://msdn.microsoft.com/en-us/library/system.security.cryptography.cryptoconfig(v=vs.110).aspx 
 84 | 		-->
 85 | 		<PasswordHashAlgorithm>SHA512</PasswordHashAlgorithm>
 86 | 
 87 | 		<CMServerSettings enabled="true">
 88 | 			<!-- If this value is non-empty, then admin's password will be set to this value -->
 89 | 			<DefaultSitecoreAdminPassword>foobar</DefaultSitecoreAdminPassword>
 90 | 
 91 | 			<!-- Add an Encryption Key for the Telerik controls 
 92 | 				  http://docs.telerik.com/devtools/aspnet-ajax/controls/asyncupload/security
 93 | 				 If using load-balanced CM servers, the value must match on both servers.
 94 | 			-->
 95 | 			<TelerikEncryptionKey></TelerikEncryptionKey>
 96 | 
 97 | 			<!-- Use these settings to dedicate Sitecore instance as the Publishing server. This is required
 98 | 			     when you are using load-balanced CM servers.
 99 | 			-->
100 | 			<Publishing enabled="false">
101 | 				<!-- This setting is ALWAYS applied to a CM server even if publishing is disabled. Therefore,
102 | 				     for an isolated CM you may leave this value blank or make sure it matches the CM
103 | 				     InstanceName
104 | 				-->
105 | 				<PublishingInstance></PublishingInstance>
106 |                 <!-- Use these settings to enable IIS Application Initialization on a dedicated publishing instance.
107 |                      Setting enabled to true will:
108 |                         - Enable the Application Initialization feature on the web server
109 |                         - Add preloadEnabled="true" to the application configuration
110 |                         - Add applicationInitialization node to the system.webserver
111 | 						- Set doAppInitAfterRestart to true
112 |                         - Set the AppPool startMode to "AlwaysRunning"
113 |                         - Set the AppPool IdleTimeout to 0
114 |                         - Set the AppPool Recycling regular time interval to 0
115 |                      Valid values are "true" or "false"
116 | 				-->
117 |                 <ApplicationInitializationEnabled>false</ApplicationInitializationEnabled>
118 |                 <!-- Timeout length in minutes for IIS App Pool
119 |                      If enabled, Application Intialization will override this value with 0.
120 |                  -->
121 | 				<AppPoolIdleTimeout>600</AppPoolIdleTimeout>
122 | 				<!-- If this setting is false, the keepalive task will not run and the publishing server will get cold. -->
123 | 				<DisableScheduledTaskExecution>true</DisableScheduledTaskExecution>
124 | 				<Parallel enabled="false">
125 | 					<!-- If set, the autogrowth for data and log files of the web database and any copy of the
126 | 					     web database will be based on a fixed size of MB rather than a percentage. This follow
127 | 					     recommendations from Sitecore. Recommended values range from 30 to 50.
128 | 					     Valid values range from 10 to 100.
129 | 					-->
130 | 					<WebDatabaseAutoGrowthInMB>30</WebDatabaseAutoGrowthInMB>
131 | 					<MaxDegreesOfParallelism>4</MaxDegreesOfParallelism>
132 | 				</Parallel>
133 | 			</Publishing>
134 | 			<!-- Use these settings to dedicate Sitecore instance as a Processing server. -->
135 | 			<Processing enabled="false">
136 | 				<!-- Valid values are "true" or "false"
137 | 					 Invalid values or missing elements will be treated as "false"
138 | 				-->
139 | 				<ApplyIPWhitelist>true</ApplyIPWhitelist>
140 | 				<!-- Enabling this will cause recommended connection strings to be commented out -->
141 | 				<DeactivateConnectionStrings>true</DeactivateConnectionStrings>
142 | 				<!-- Enabling this setting causes some files on the Processing server to have ".disabled" concatenated to
143 | 					 their filename. Other files necessary for configuring a Processing file will be enabled. The files changed are from the recommendations here:
144 | 					 https://doc.sitecore.net/sitecore_experience_platform/setting_up_and_maintaining/xdb/configuring_servers/configure_a_processing_server
145 | 				-->
146 | 				<ConfigureFilesForProcessing>true</ConfigureFilesForProcessing>
147 | 				<!-- Denies anonymous users from accessing certain directories per Sitecore's recommendations -->
148 | 				<PreventAnonymousAccess>true</PreventAnonymousAccess>
149 | 			</Processing>
150 | 		</CMServerSettings>
151 | 
152 | 		<CDServerSettings enabled="false">
153 | 			<!-- Valid values are "true" or "false"
154 | 			     Invalid values or missing elements will be treated as "false"
155 | 			-->
156 | 			<ApplyIPWhitelist>true</ApplyIPWhitelist>
157 | 			<!-- Enabling this will cause recommended connection strings to be commented out -->
158 | 			<DeactivateConnectionStrings>true</DeactivateConnectionStrings>
159 | 			<!-- Enabling this setting causes some files on the CD server to have ".disabled" concatenated to
160 | 			     their filename. Other files necessary for configuring a CD such as the
161 | 			     SwitchMasterToWeb.config file will be enabled. The files changed are from the recommendations here:
162 | 			     https://doc.sitecore.net/sitecore%20experience%20platform/xdb%20configuration/configure%20a%20content%20delivery%20server
163 | 			-->
164 | 			<ConfigureFilesForCD>true</ConfigureFilesForCD>
165 | 			<!-- Denies anonymous users from accessing certain directories per Sitecore's recommendations -->
166 | 			<PreventAnonymousAccess>true</PreventAnonymousAccess>
167 | 			<!-- Prevent the execution of scripts or programs in the upload and temp folders -->
168 | 			<DenyExecutePermission>true</DenyExecutePermission>
169 | 			<!-- Enabling this setting prevents uploading files outside of the Sitecore client -->
170 | 			<DisableUploadWatcher>true</DisableUploadWatcher>
171 | 			<!-- If you have implemented custom code that uses ASP.NET Web API attribute routing, to avoid errors, disable the following -->
172 | 			<DisableExperienceAnalyticsAssemblies>true</DisableExperienceAnalyticsAssemblies>
173 | 			<!-- Remove PhantomJs from CD per Sitecore's recommendations -->
174 | 			<RemovePhantomJs>true</RemovePhantomJs>
175 | 			<!-- Disables Telerik UI Handlers on CD server. -->
176 | 			<DisableTelerikControls>true</DisableTelerikControls>
177 | 		</CDServerSettings>
178 | 
179 | 		<!-- Media Request Protection - Applied to CM and CD Servers -->
180 | 		<MediaRequestProtection>
181 | 			<!-- In a multi-instance setup, use the same value for Media.RequestProtection.SharedSecret on every instance.
182 | 				 SharedSecret is required. If no value is provided, Sitecore default value will be used. -->
183 | 			<SharedSecret></SharedSecret>
184 | 			<!-- Specifies whether the media request protection feature will output detailed information to the Sitecore log file.
185 | 				 If no value is provided, Sitecore default value (true) will be used. -->
186 | 			<LoggingEnabled>true</LoggingEnabled>
187 | 		</MediaRequestProtection>
188 | 
189 | 		<!-- Hardened directories in IIS will deny all clients except the following IPs -->
190 | 		<IPWhiteList>
191 | 			<IP>127.0.0.1</IP>
192 | 			<IP>10.10.20.7</IP>
193 | 			<IP>10.10.20.11</IP>
194 | 		</IPWhiteList>
195 | 
196 | 		<SessionStateProvider>
197 | 			<!-- Valid values for Private and Shared are:
198 | 			       - InProc
199 | 			       - MSSQL (except for Shared on a CM!)
200 | 			       - Mongo (currently not supported by the installer)
201 | 			-->
202 | 			<Private>mssql</Private>
203 | 			<Shared>InProc</Shared>
204 | 		</SessionStateProvider>
205 | 
206 | 		<Solr>
207 | 			<!-- If provided, the installer will modify the
208 | 			     Sitecore.ContentSearch.Solr.DefaultIndexConfiguration.config.example file to use the given address
209 | 			-->
210 | 			<ServiceBaseAddress>http://solr5:8888/solr</ServiceBaseAddress>
211 | 		</Solr>
212 | 
213 | 		<!-- This section determines how the connection strings for for MongoDB will be formed. Any values
214 | 			 left blank will not be used. The settings below adhere to MongoDB's connection string format
215 | 			 specification: https://docs.mongodb.org/manual/reference/connection-string/
216 | 
217 | 			 If this section is not enabled, it will be ignored.
218 | 		-->
219 | 		<MongoDb enabled="true">
220 | 			<!-- Optional, won't be used if blank -->
221 | 			<Credentials>
222 | 				<Username>someuser</Username>
223 | 				<Password>somepassword</Password>
224 | 			</Credentials>
225 | 			<!-- At least one <Host> is required, each <Host> must specify a <HostName> and an optional <Port> -->
226 | 			<Hosts>
227 | 				<Host>
228 | 					<HostName>node1.company.com</HostName>
229 | 					<Port>27017</Port>
230 | 				</Host>
231 | 				<Host>
232 | 					<HostName>node2.company.com</HostName>
233 | 					<Port>9999</Port>
234 | 				</Host>
235 | 			</Hosts>
236 | 			<!-- This setting's value will be appended to the connection string's URI. The format should be as a
237 | 			     query string.
238 | 			-->
239 | 			<Options>?authMechanism=PLAIN&amp;authSource=$external&amp;replicaSet=mymongoset</Options>
240 | 		</MongoDb>
241 | 
242 | 	</WebServer>
243 | 
244 | 	<!-- If disabled the script will skip ALL database related operations.
245 | 		   - No SQL server connection tests
246 | 		   - Databases files will not be copied or attached
247 | 		   - User mappings, permissions will not be set
248 | 		   - Autogrowth will not be set on web database (relevant to parallel publishing)
249 | 
250 | 		 Regardless the information in this section will still be used to form connection string values.
251 | 		 Thus, ensure that the database names are always accurate as well as the SQL server name and data
252 | 		 access account information.
253 | 		 Type: Azure, Local
254 |  		Using Azure requires the installation of the Dacfx
255 |  		https://www.microsoft.com/en-us/download/confirmation.aspx?id=55255
256 | 	-->
257 | 	<Database type="Local" enabled="true">
258 | 		<Azure>
259 | 			<SQLPackagePath>C:\Program Files\Microsoft SQL Server\140\DAC\bin\sqlpackage.exe</SQLPackagePath>
260 | 			<SQLResourceGroup></SQLResourceGroup>
261 | 			<SQLEdition></SQLEdition>
262 | 			<SQLMaxSize></SQLMaxSize> <!-- in Bytes -->
263 | 			<SQLServiceObjective></SQLServiceObjective>
264 | 		</Azure>
265 | 		<!-- Valid values are "true" or "false" Invalid values or missing element will be treated as "false"
266 | 		     Note that even if you do not install the database, database mappings and permissions will still
267 | 		     be written.
268 | 		-->
269 | 		<InstallDatabase>true</InstallDatabase>
270 | 
271 | 		<!-- Do not edit this list unless you know what you are doing! :) This list represents the all of
272 | 		     the default databases used by Sitecore.
273 | 		-->
274 | 		<DatabaseNames>
275 | 			<name>Core</name>
276 | 			<name>Master</name>
277 | 			<name>Web</name>
278 | 			<name>Sessions</name>
279 | 			<name>Reporting</name>
280 | 		</DatabaseNames>
281 | 
282 | 		<!-- Add <copy> elements for each duplicate web database to be created -->
283 | 		<WebDatabaseCopies>
284 | 			<!-- Setting the connectionStringName attribute will assign that value to the "name" attribute
285 | 			     of the connection string for this databse. For example, if the connectionStringName is "web"
286 | 			     then the web connection string will point to the preview database. This is useful for creating
287 | 			     a preview-type CD server that serves content out of a different database than the normal, web
288 | 			     database. If the attribute is missing or does not have a value, then the name of the copy
289 | 			     database will be used to create the name of the connection string.
290 | 
291 | 			     NOTE: The "web" database is referred to in many places in Sitecore’s configuration:
292 | 				   - Database definitions
293 | 				   - Agents
294 | 				   - Index definitions
295 | 				   - Indexing strategies
296 | 				   - Site definitions
297 | 
298 | 			     Thus, you will need to think about patching the Sitecore's .config files to address this behavior.
299 | 
300 | 				 * On the preview CD server, by replacing the "web" connection string’s database with a preview
301 | 				 database, you can avoid much of this configuration work.  If you are using Lucene, you
302 | 				 shouldn't need to do anything else. If you are using Solr, I STRONGLY recommend you create
303 | 				 dedicated 'preview' versions of web indexes and indexing strategies.
304 | 
305 | 				 * On the CM server, you should consider doing the following:
306 | 				   - Configuring a <database> element similar to the web's
307 | 				   - If you want schedule periodic publishing, then create an <agent> for Sitecore.Tasks.PublishAgent
308 | 				     to publish to your preview database
309 | 				   - If you use WebDAV, consider adding your preview database to the
310 | 				     Sitecore.Tasks.CleanupFDAObsoleteMediaData <agent>
311 | 				   - Create 'preview' version of the onPublishEndAsync and onPublishEndAsyncSingleInstance index
312 | 				     update strategies
313 | 				   - Create Index definitions for the 'preview' versions of your 'web' indexes. This is especially
314 | 				     important if you use Solr!
315 | 			-->
316 | 			<copy>Preview</copy>
317 | 			<copy connectionStringName="altpreview">Preview2</copy>
318 | 		</WebDatabaseCopies>
319 | 
320 | 		<!-- The format is: {sqlservername[\instancename]}[,{port}]
321 | 			 Examples
322 | 			 - vmwebdev01
323 | 			 - vmwebdev01,1433
324 | 			 - vmwebdev01\myinstance
325 | 			 - vmwebdev01\myinstance,1433
326 | 			 Azure
327 |  			 - exampleDB.database.windows.net
328 | 		-->
329 | 		<SqlServerName>vmwebdev01,1433</SqlServerName>
330 | 
331 | 		<!-- This login is used to attach databases and assign roles in SQL. The login must have the sysadmin
332 | 			 server role.
333 | 		-->
334 | 		<SqlLoginForInstall>SC_InstallAccount</SqlLoginForInstall>
335 | 		<SqlLoginForInstallPassword>P@ssword</SqlLoginForInstallPassword>
336 | 
337 | 		<!-- If specified, this login will be used in connection strings. Only SQL logins are valid. -->
338 | 		<SqlLoginForDataAccess></SqlLoginForDataAccess>
339 | 		<SqlLoginForDataAccessPassword></SqlLoginForDataAccessPassword>
340 | 
341 | 		<!-- If true, then the ApplicationPoolIdentity will be used for the SQL login rather than
342 | 		     SqlLoginForDataAccess. This setting requires a domain account is specified for the
343 | 		     ApplicationPoolIdentity.
344 | 		-->
345 | 		<UseWindowsAuthenticationForSqlDataAccess>true</UseWindowsAuthenticationForSqlDataAccess>
346 | 
347 | 		<DatabaseInstallPath>
348 | 			<DataFiles>
349 | 				<!-- Must be defined, and folder must exist. The SQL instance must have FullControl over the folder.
350 | 					 This value is used to attach the databases in SQL. If the Unc value is missing, this is also the
351 | 					 path used as the destination for SQL database file copying.
352 | 				-->
353 | 				<Local>C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\installdemo data files</Local>
354 | 
355 | 				<!-- If defined this path will be used to copy database files into the file system of the
356 | 					 SQL server.
357 | 				-->
358 | 				<Unc>\\VMWEBDEV01\installdemo data files</Unc>
359 | 			</DataFiles>
360 | 
361 | 			<!-- This sectional is optional. If undefined, then log files will be installed in the same location
362 | 				 the same location as the data files defined above.
363 | 			-->
364 | 			<LogFiles>
365 | 				<!-- Must be defined, and folder must exist. The SQL instance must have FullControl over the folder.
366 | 					 This value is used to attach the databases in SQL. If the Unc value is missing, this is also the
367 | 					 path used as the destination for SQL database file copying.
368 | 				-->
369 | 				<Local>C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\installdemo log files</Local>
370 | 
371 | 				<!-- If defined this path will be used to copy database files into the file system of the
372 | 					 SQL server.
373 | 				-->
374 | 				<Unc>\\VMWEBDEV01\installdemo log files</Unc>
375 | 			</LogFiles>
376 | 		</DatabaseInstallPath>
377 | 
378 | 		<DatabaseNamePrefix>InstallDemo_Sitecore_</DatabaseNamePrefix>
379 | 
380 | 	</Database>
381 | 
382 | </InstallSettings>
383 | 


--------------------------------------------------------------------------------
/install.ExampleProcessing.config:
--------------------------------------------------------------------------------
  1 | <?xml version="1.0" encoding="utf-8"?>
  2 | <InstallSettings>
  3 | 	<!-- PreReqs
  4 | 	https://docs.microsoft.com/en-us/sql/relational-databases/scripting/sql-server-powershell
  5 | 	https://www.microsoft.com/en-us/download/details.aspx?id=52676
  6 | 	Install-Module -Name ImportExcel
  7 | 	Install-Module -Name AzureRM.sql
  8 | 	-->
  9 | 	<!-- If blank, no log file will be generated. The log file location will be the
 10 | 	     SitecoreInstallFolder.
 11 | 	-->
 12 | 	<LogFileName>InstallLog.txt</LogFileName>
 13 | 
 14 | 	<!-- Path of downloaded zip file from Sitecore -->
 15 | 	<SitecoreZipPath>C:\Users\sp_farmadmin\AppData\Roaming\Sitecore\Sitecore Instance Manager\Repository\Sitecore 8.2 rev. 161221.zip</SitecoreZipPath>
 16 | 
 17 | 	<!-- Path of downloaded Sitecore configuration spreadsheet.
 18 | 		 This setting is required and used for installing Sitecore 8.2
 19 | 		 Find the spreadsheet here: https://doc.sitecore.net/sitecore_experience_platform/setting_up_and_maintaining/xdb/configuring_servers/server_configuration_resources
 20 | 	-->
 21 | 	<SitecoreConfigSpreadsheetPath>C:\temp\Config Enable-Disable Sitecore_8.2 Update2.xlsx</SitecoreConfigSpreadsheetPath>
 22 | 
 23 | 	<!-- If true then user prompts will be bypassed. For example, if the script cannot determine that SQL
 24 | 	     has FullControl over database files, then a dialog prompt will be displayed asking if the script
 25 | 	     should continue if this property is set to false.
 26 | 	-->
 27 | 	<SuppressPrompts>true</SuppressPrompts>
 28 | 
 29 | 	<WebServer>
 30 | 		<LicenseFilePath>C:\ArkeSitecoreLicense\license.xml</LicenseFilePath>
 31 | 		<SitecoreInstallRoot>C:\inetpub\wwwroot</SitecoreInstallRoot>
 32 | 		<!-- Folder will be created at the SitecoreInstallRoot if it does not already exist. -->
 33 | 		<SitecoreInstallFolder>ExampleProc</SitecoreInstallFolder>
 34 | 		<!-- Select a name for the last folder under /App_Config/Include
 35 | 		     This is the folder where all config files which must be patched last should be kept (e.g.
 36 | 		     SwitchMasterToWeb.config file.) For Sitecore 8.1, if no name is supplied then the installer
 37 | 		     will use the Z.SwitchMasterToWeb folder.
 38 | 		-->
 39 | 		<LastChildFolderOfIncludeDirectory>zzzMustBeLast</LastChildFolderOfIncludeDirectory>
 40 | 		<!-- Encrypt the contents of the ConnectionStrings.config file -->
 41 | 		<EncryptConnectionStrings>true</EncryptConnectionStrings>
 42 | 
 43 | 		<IISWebSiteName>ExampleProc</IISWebSiteName>
 44 | 		<DefaultRuntimeVersion>v4.0</DefaultRuntimeVersion>
 45 | 		<!-- Valid values are:
 46 | 		      - NetworkService
 47 | 		      - ApplicationPoolIdentity
 48 | 		      - Any domain account in the form <domain>\<username>
 49 | 
 50 | 		     If you supply a domain account, you must also provide a valid password for the account.
 51 | 		-->
 52 | 		<AppPoolIdentity>EVADEV\SCTest_AppPool</AppPoolIdentity>
 53 | 		<AppPoolIdentityPassword>P@ssword</AppPoolIdentityPassword>
 54 | 		<IISBindings>
 55 | 			<Binding IP="*" Port="80" HostHeader="exampleproc" AddToHostsFile="true" />
 56 | 			<Binding IP="10.10.20.11" Port="80" HostHeader="expr" AddToHostsFile="false" />
 57 | 			<Binding IP="10.10.20.11" Port="80" HostHeader="epr" />
 58 | 		</IISBindings>
 59 | 
 60 | 		<!-- Provide a unique name for this instance of Sitecore. This value should be set any time you have mulitple CD or CM servers. -->
 61 | 		<SitecoreInstanceName>ExampleProc1</SitecoreInstanceName>
 62 | 
 63 | 		<!-- This section controls settings for Sitecore's Analytics -->
 64 | 		<Analytics>
 65 | 			<ClusterName></ClusterName>
 66 | 			<HostName></HostName>
 67 | 		</Analytics>
 68 | 
 69 | 		<!-- This value will be written to the reporting.api connection string. Only applies to Sitecore 8.2 -->
 70 | 		<ReportingApiKey>12345678901234567890123456789012</ReportingApiKey>
 71 | 		
 72 | 		<!-- Sitecore recommends changing the default password hash algorithm from SHA1 to SHA512
 73 | 		
 74 | 			For user management, Sitecore uses the Microsoft ASP.NET membership provider by default. 
 75 | 
 76 | 			*** IMPORTANT! ***
 77 | 			The Microsoft ASP.NET membership provider does not provide a facility for upgrading to a different hash algorithm after you have created 
 78 | 			user accounts. IF YOU CHANGE THE HASH ALGORITHM, EXISTING USERS CAN NO LONGER LOG INTO THE SYSTEM AND MUST CREATE A NEW PASSWORD.
 79 | 			
 80 | 			Valid values are:
 81 | 			- "" 
 82 | 			- a supported hash algorithm from the System.Security.Cryptography.CryptoConfig class : 
 83 | 			https://msdn.microsoft.com/en-us/library/system.security.cryptography.cryptoconfig(v=vs.110).aspx 
 84 | 		-->
 85 | 		<PasswordHashAlgorithm>SHA512</PasswordHashAlgorithm>
 86 | 
 87 | 		<CMServerSettings enabled="true">
 88 | 			<!-- If this value is non-empty, then admin's password will be set to this value -->
 89 | 			<DefaultSitecoreAdminPassword></DefaultSitecoreAdminPassword>
 90 | 
 91 | 			<!-- Add an Encryption Key for the Telerik controls 
 92 | 				  http://docs.telerik.com/devtools/aspnet-ajax/controls/asyncupload/security
 93 | 				 If using load-balanced CM servers, the value must match on both servers.
 94 | 			-->
 95 | 			<TelerikEncryptionKey></TelerikEncryptionKey>
 96 | 
 97 | 			<!-- Use these settings to dedicate Sitecore instance as the Publishing server. This is required
 98 | 			     when you are using load-balanced CM servers.
 99 | 			-->
100 | 			<Publishing enabled="false">
101 | 				<!-- This setting is ALWAYS applied to a CM server even if publishing is disabled. Therefore,
102 | 				     for an isolated CM you may leave this value blank or make sure it matches the CM
103 | 				     InstanceName
104 | 				-->
105 | 				<PublishingInstance></PublishingInstance>
106 |                 <!-- Use these settings to enable IIS Application Initialization on a dedicated publishing instance.
107 |                      Setting enabled to true will:
108 |                         - Enable the Application Initialization feature on the web server
109 |                         - Add preloadEnabled="true" to the application configuration
110 |                         - Add applicationInitialization node to the system.webserver
111 | 						- Set doAppInitAfterRestart to true
112 |                         - Set the AppPool startMode to "AlwaysRunning"
113 |                         - Set the AppPool IdleTimeout to 0
114 |                         - Set the AppPool Recycling regular time interval to 0
115 |                      Valid values are "true" or "false"
116 | 				-->
117 |                 <ApplicationInitializationEnabled>false</ApplicationInitializationEnabled>
118 |                 <!-- Timeout length in minutes for IIS App Pool
119 |                      If enabled, Application Intialization will override this value with 0.
120 |                  -->
121 | 				<AppPoolIdleTimeout>600</AppPoolIdleTimeout>
122 | 				<!-- If this setting is false, the keepalive task will not run and the publishing server will get cold. -->
123 | 				<DisableScheduledTaskExecution>false</DisableScheduledTaskExecution>
124 | 				<Parallel enabled="false">
125 | 					<!-- If set, the autogrowth for data and log files of the web database and any copy of the
126 | 					     web database will be based on a fixed size of MB rather than a percentage. This follow
127 | 					     recommendations from Sitecore. Recommended values range from 30 to 50.
128 | 					     Valid values range from 10 to 100.
129 | 					-->
130 | 					<WebDatabaseAutoGrowthInMB>30</WebDatabaseAutoGrowthInMB>
131 | 					<MaxDegreesOfParallelism>4</MaxDegreesOfParallelism>
132 | 				</Parallel>
133 | 			</Publishing>
134 | 			<!-- Use these settings to dedicate Sitecore instance as a Processing server. -->
135 | 			<Processing enabled="true">
136 | 				<!-- Valid values are "true" or "false"
137 | 					 Invalid values or missing elements will be treated as "false"
138 | 				-->
139 | 				<ApplyIPWhitelist>true</ApplyIPWhitelist>
140 | 				<!-- Enabling this will cause recommended connection strings to be commented out -->
141 | 				<DeactivateConnectionStrings>true</DeactivateConnectionStrings>
142 | 				<!-- Enabling this setting causes some files on the Processing server to have ".disabled" concatenated to
143 | 					 their filename. Other files necessary for configuring a Processing file will be enabled. The files changed are from the recommendations here:
144 | 					 https://doc.sitecore.net/sitecore_experience_platform/setting_up_and_maintaining/xdb/configuring_servers/configure_a_processing_server
145 | 				-->
146 | 				<ConfigureFilesForProcessing>true</ConfigureFilesForProcessing>
147 | 				<!-- Denies anonymous users from accessing certain directories per Sitecore's recommendations -->
148 | 				<PreventAnonymousAccess>true</PreventAnonymousAccess>
149 | 			</Processing>
150 | 		</CMServerSettings>
151 | 
152 | 		<CDServerSettings enabled="false">
153 | 			<!-- Valid values are "true" or "false"
154 | 			     Invalid values or missing elements will be treated as "false"
155 | 			-->
156 | 			<ApplyIPWhitelist>true</ApplyIPWhitelist>
157 | 			<!-- Enabling this will cause recommended connection strings to be commented out -->
158 | 			<DeactivateConnectionStrings>true</DeactivateConnectionStrings>
159 | 			<!-- Enabling this setting causes some files on the CD server to have ".disabled" concatenated to
160 | 			     their filename. Other files necessary for configuring a CD such as the
161 | 			     SwitchMasterToWeb.config file will be enabled. The files changed are from the recommendations here:
162 | 			     https://doc.sitecore.net/sitecore%20experience%20platform/xdb%20configuration/configure%20a%20content%20delivery%20server
163 | 			-->
164 | 			<ConfigureFilesForCD>true</ConfigureFilesForCD>
165 | 			<!-- Denies anonymous users from accessing certain directories per Sitecore's recommendations -->
166 | 			<PreventAnonymousAccess>true</PreventAnonymousAccess>
167 | 			<!-- Prevent the execution of scripts or programs in the upload and temp folders -->
168 | 			<DenyExecutePermission>true</DenyExecutePermission>
169 | 			<!-- Enabling this setting prevents uploading files outside of the Sitecore client -->
170 | 			<DisableUploadWatcher>true</DisableUploadWatcher>
171 | 			<!-- If you have implemented custom code that uses ASP.NET Web API attribute routing, to avoid errors, disable the following -->
172 | 			<DisableExperienceAnalyticsAssemblies>true</DisableExperienceAnalyticsAssemblies>
173 | 			<!-- Remove PhantomJs from CD per Sitecore's recommendations -->
174 | 			<RemovePhantomJs>true</RemovePhantomJs>
175 | 			<!-- Disables Telerik UI Handlers on CD server. -->
176 | 			<DisableTelerikControls>true</DisableTelerikControls>
177 | 		</CDServerSettings>
178 | 
179 | 		<!-- Media Request Protection - Applied to CM and CD Servers -->
180 | 		<MediaRequestProtection>
181 | 			<!-- In a multi-instance setup, use the same value for Media.RequestProtection.SharedSecret on every instance.
182 | 				 SharedSecret is required. If no value is provided, Sitecore default value will be used. -->
183 | 			<SharedSecret></SharedSecret>
184 | 			<!-- Specifies whether the media request protection feature will output detailed information to the Sitecore log file.
185 | 				 If no value is provided, Sitecore default value (true) will be used. -->
186 | 			<LoggingEnabled>true</LoggingEnabled>
187 | 		</MediaRequestProtection>
188 | 
189 | 		<!-- Hardened directories in IIS will deny all clients except the following IPs -->
190 | 		<IPWhiteList>
191 | 			<IP>127.0.0.1</IP>
192 | 			<IP>10.10.20.7</IP>
193 | 			<IP>10.10.20.11</IP>
194 | 		</IPWhiteList>
195 | 
196 | 		<SessionStateProvider>
197 | 			<!-- Valid values for Private and Shared are:
198 | 			       - InProc
199 | 			       - MSSQL (except for Shared on a CM!)
200 | 			       - Mongo (currently not supported by the installer)
201 | 			-->
202 | 			<Private>mssql</Private>
203 | 			<Shared>InProc</Shared>
204 | 		</SessionStateProvider>
205 | 
206 | 		<Solr>
207 | 			<!-- If provided, the installer will modify the
208 | 			     Sitecore.ContentSearch.Solr.DefaultIndexConfiguration.config.example file to use the given address
209 | 			-->
210 | 			<ServiceBaseAddress>http://solr5:8888/solr</ServiceBaseAddress>
211 | 		</Solr>
212 | 
213 | 		<!-- This section determines how the connection strings for for MongoDB will be formed. Any values
214 | 			 left blank will not be used. The settings below adhere to MongoDB's connection string format
215 | 			 specification: https://docs.mongodb.org/manual/reference/connection-string/
216 | 
217 | 			 If this section is not enabled, it will be ignored.
218 | 		-->
219 | 		<MongoDb enabled="true">
220 | 			<!-- Optional, won't be used if blank -->
221 | 			<Credentials>
222 | 				<Username>someuser</Username>
223 | 				<Password>somepassword</Password>
224 | 			</Credentials>
225 | 			<!-- At least one <Host> is required, each <Host> must specify a <HostName> and an optional <Port> -->
226 | 			<Hosts>
227 | 				<Host>
228 | 					<HostName>node1.company.com</HostName>
229 | 					<Port>27017</Port>
230 | 				</Host>
231 | 				<Host>
232 | 					<HostName>node2.company.com</HostName>
233 | 					<Port>9999</Port>
234 | 				</Host>
235 | 			</Hosts>
236 | 			<!-- This setting's value will be appended to the connection string's URI. The format should be as a
237 | 			     query string.
238 | 			-->
239 | 			<Options>?authMechanism=PLAIN&amp;authSource=$external&amp;replicaSet=mymongoset</Options>
240 | 		</MongoDb>
241 | 
242 | 	</WebServer>
243 | 
244 | 		<!-- If disabled the script will skip ALL database related operations.
245 | 			   - No SQL server connection tests
246 | 			   - Databases files will not be copied or attached
247 | 			   - User mappings, permissions will not be set
248 | 			   - Autogrowth will not be set on web database (relevant to parallel publishing)
249 | 
250 | 			 Regardless the information in this section will still be used to form connection string values.
251 | 			 Thus, ensure that the database names are always accurate as well as the SQL server name and data
252 | 			 access account information.
253 | 			Type: Azure, Local
254 | 			Using Azure requires the installation of the Dacfx
255 | 			https://www.microsoft.com/en-us/download/confirmation.aspx?id=55255
256 | 		-->
257 | 		<Database type="Azure" enabled="true">
258 | 			<Azure>
259 | 				<SQLPackagePath>C:\Program Files\Microsoft SQL Server\140\DAC\bin\sqlpackage.exe</SQLPackagePath>
260 | 				<SQLResourceGroup></SQLResourceGroup>
261 | 				<SQLEdition></SQLEdition>
262 | 				<SQLMaxSize></SQLMaxSize> <!-- in Bytes -->
263 | 				<SQLServiceObjective></SQLServiceObjective>
264 | 			</Azure>
265 | 
266 | 		<!-- Valid values are "true" or "false" Invalid values or missing element will be treated as "false"
267 | 		     Note that even if you do not install the database, database mappings and permissions will still
268 | 		     be written.
269 | 		-->
270 | 		<InstallDatabase>false</InstallDatabase>
271 | 
272 | 		<!-- Do not edit this list unless you know what you are doing! :) This list represents the all of
273 | 		     the default databases used by Sitecore.
274 | 		-->
275 | 		<DatabaseNames>
276 | 			<name>Core</name>
277 | 			<name>Master</name>
278 | 			<name>Web</name>
279 | 			<name>Sessions</name>
280 | 			<name>Reporting</name>
281 | 		</DatabaseNames>
282 | 
283 | 		<!-- Add <copy> elements for each duplicate web database to be created -->
284 | 		<WebDatabaseCopies>
285 | 			<!-- Setting the connectionStringName attribute will assign that value to the "name" attribute
286 | 			     of the connection string for this databse. For example, if the connectionStringName is "web"
287 | 			     then the web connection string will point to the preview database. This is useful for creating
288 | 			     a preview-type CD server that serves content out of a different database than the normal, web
289 | 			     database. If the attribute is missing or does not have a value, then the name of the copy
290 | 			     database will be used to create the name of the connection string.
291 | 
292 | 			     NOTE: The "web" database is referred to in many places in Sitecore’s configuration:
293 | 				   - Database definitions
294 | 				   - Agents
295 | 				   - Index definitions
296 | 				   - Indexing strategies
297 | 				   - Site definitions
298 | 
299 | 			     Thus, you will need to think about patching the Sitecore's .config files to address this behavior.
300 | 
301 | 				 * On the preview CD server, by replacing the "web" connection string’s database with a preview
302 | 				 database, you can avoid much of this configuration work.  If you are using Lucene, you
303 | 				 shouldn't need to do anything else. If you are using Solr, I STRONGLY recommend you create
304 | 				 dedicated 'preview' versions of web indexes and indexing strategies.
305 | 
306 | 				 * On the CM server, you should consider doing the following:
307 | 				   - Configuring a <database> element similar to the web's
308 | 				   - If you want schedule periodic publishing, then create an <agent> for Sitecore.Tasks.PublishAgent
309 | 				     to publish to your preview database
310 | 				   - If you use WebDAV, consider adding your preview database to the
311 | 				     Sitecore.Tasks.CleanupFDAObsoleteMediaData <agent>
312 | 				   - Create 'preview' version of the onPublishEndAsync and onPublishEndAsyncSingleInstance index
313 | 				     update strategies
314 | 				   - Create Index definitions for the 'preview' versions of your 'web' indexes. This is especially
315 | 				     important if you use Solr!
316 | 			-->
317 | 			<copy>Preview</copy>
318 | 			<copy connectionStringName="altpreview">Preview2</copy>
319 | 		</WebDatabaseCopies>
320 | 
321 | 		<!-- The format is: {sqlservername[\instancename]}[,{port}]
322 | 			 Examples
323 | 			 - vmwebdev01
324 | 			 - vmwebdev01,1433
325 | 			 - vmwebdev01\myinstance
326 | 			 - vmwebdev01\myinstance,1433
327 | 			 Azure
328 |  			 - exampleDB.database.windows.net
329 | 		-->
330 | 		<SqlServerName>vmwebdev01,1433</SqlServerName>
331 | 
332 | 		<!-- This login is used to attach databases and assign roles in SQL. The login must have the sysadmin
333 | 			 server role.
334 | 		-->
335 | 		<SqlLoginForInstall>SC_InstallAccount</SqlLoginForInstall>
336 | 		<SqlLoginForInstallPassword>P@ssword</SqlLoginForInstallPassword>
337 | 
338 | 		<!-- If specified, this login will be used in connection strings. Only SQL logins are valid. -->
339 | 		<SqlLoginForDataAccess></SqlLoginForDataAccess>
340 | 		<SqlLoginForDataAccessPassword></SqlLoginForDataAccessPassword>
341 | 
342 | 		<!-- If true, then the ApplicationPoolIdentity will be used for the SQL login rather than
343 | 		     SqlLoginForDataAccess. This setting requires a domain account is specified for the
344 | 		     ApplicationPoolIdentity.
345 | 		-->
346 | 		<UseWindowsAuthenticationForSqlDataAccess>true</UseWindowsAuthenticationForSqlDataAccess>
347 | 
348 | 		<DatabaseInstallPath>
349 | 			<DataFiles>
350 | 				<!-- Must be defined, and folder must exist. The SQL instance must have FullControl over the folder.
351 | 					 This value is used to attach the databases in SQL. If the Unc value is missing, this is also the
352 | 					 path used as the destination for SQL database file copying.
353 | 				-->
354 | 				<Local>C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\installdemo data files</Local>
355 | 
356 | 				<!-- If defined this path will be used to copy database files into the file system of the
357 | 					 SQL server.
358 | 				-->
359 | 				<Unc>\\VMWEBDEV01\installdemo data files</Unc>
360 | 			</DataFiles>
361 | 
362 | 			<!-- This sectional is optional. If undefined, then log files will be installed in the same location
363 | 				 the same location as the data files defined above.
364 | 			-->
365 | 			<LogFiles>
366 | 				<!-- Must be defined, and folder must exist. The SQL instance must have FullControl over the folder.
367 | 					 This value is used to attach the databases in SQL. If the Unc value is missing, this is also the
368 | 					 path used as the destination for SQL database file copying.
369 | 				-->
370 | 				<Local>C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\installdemo log files</Local>
371 | 
372 | 				<!-- If defined this path will be used to copy database files into the file system of the
373 | 					 SQL server.
374 | 				-->
375 | 				<Unc>\\VMWEBDEV01\installdemo log files</Unc>
376 | 			</LogFiles>
377 | 		</DatabaseInstallPath>
378 | 
379 | 		<DatabaseNamePrefix>InstallDemo_Sitecore_</DatabaseNamePrefix>
380 | 
381 | 	</Database>
382 | 
383 | </InstallSettings>
384 | 


--------------------------------------------------------------------------------
/install.ExamplePublishing.config:
--------------------------------------------------------------------------------
  1 | <?xml version="1.0" encoding="utf-8"?>
  2 | <InstallSettings>
  3 | 	<!-- PreReqs
  4 | 	https://docs.microsoft.com/en-us/sql/relational-databases/scripting/sql-server-powershell
  5 | 	https://www.microsoft.com/en-us/download/details.aspx?id=52676
  6 | 	Install-Module -Name ImportExcel
  7 | 	Install-Module -Name AzureRM.sql
  8 | 	-->
  9 | 	<!-- If blank, no log file will be generated. The log file location will be the
 10 | 	     SitecoreInstallFolder.
 11 | 	-->
 12 | 	<LogFileName>InstallLog.txt</LogFileName>
 13 | 
 14 | 	<!-- Path of downloaded zip file from Sitecore -->
 15 | 	<SitecoreZipPath>C:\Users\sp_farmadmin\AppData\Roaming\Sitecore\Sitecore Instance Manager\Repository\Sitecore 8.2 rev. 161221.zip</SitecoreZipPath>
 16 | 
 17 | 	<!-- Path of downloaded Sitecore configuration spreadsheet.
 18 | 		 This setting is required and used for installing Sitecore 8.2
 19 | 		 Find the spreadsheet here: https://doc.sitecore.net/sitecore_experience_platform/setting_up_and_maintaining/xdb/configuring_servers/server_configuration_resources
 20 | 	-->
 21 | 	<SitecoreConfigSpreadsheetPath>C:\temp\Config Enable-Disable Sitecore_8.2 Update2.xlsx</SitecoreConfigSpreadsheetPath>
 22 | 
 23 | 	<!-- If true then user prompts will be bypassed. For example, if the script cannot determine that SQL
 24 | 	     has FullControl over database files, then a dialog prompt will be displayed asking if the script
 25 | 	     should continue if this property is set to false.
 26 | 	-->
 27 | 	<SuppressPrompts>true</SuppressPrompts>
 28 | 
 29 | 	<WebServer>
 30 | 		<LicenseFilePath>C:\ArkeSitecoreLicense\license.xml</LicenseFilePath>
 31 | 		<SitecoreInstallRoot>C:\inetpub\wwwroot</SitecoreInstallRoot>
 32 | 		<!-- Folder will be created at the SitecoreInstallRoot if it does not already exist. -->
 33 | 		<SitecoreInstallFolder>ExamplePublishing</SitecoreInstallFolder>
 34 | 		<!-- Select a name for the last folder under /App_Config/Include
 35 | 		     This is the folder where all config files which must be patched last should be kept (e.g.
 36 | 		     SwitchMasterToWeb.config file.) For Sitecore 8.1, if no name is supplied then the installer
 37 | 		     will use the Z.SwitchMasterToWeb folder.
 38 | 		-->
 39 | 		<LastChildFolderOfIncludeDirectory>zzzMustBeLast</LastChildFolderOfIncludeDirectory>
 40 | 		<!-- Encrypt the contents of the ConnectionStrings.config file -->
 41 | 		<EncryptConnectionStrings>true</EncryptConnectionStrings>
 42 | 
 43 | 		<IISWebSiteName>ExamplePublishing</IISWebSiteName>
 44 | 		<DefaultRuntimeVersion>v4.0</DefaultRuntimeVersion>
 45 | 		<!-- Valid values are:
 46 | 		      - NetworkService
 47 | 		      - ApplicationPoolIdentity
 48 | 		      - Any domain account in the form <domain>\<username>
 49 | 
 50 | 		     If you supply a domain account, you must also provide a valid password for the account.
 51 | 		-->
 52 | 		<AppPoolIdentity>EVADEV\SCTest_AppPool</AppPoolIdentity>
 53 | 		<AppPoolIdentityPassword>P@ssword</AppPoolIdentityPassword>
 54 | 		<IISBindings>
 55 | 			<Binding IP="*" Port="80" HostHeader="examplepub" AddToHostsFile="true" />
 56 | 			<Binding IP="10.10.20.11" Port="80" HostHeader="expub" AddToHostsFile="false" />
 57 | 			<Binding IP="10.10.20.11" Port="80" HostHeader="ep" />
 58 | 		</IISBindings>
 59 | 
 60 | 		<!-- Provide a unique name for this instance of Sitecore. This value should be set any time you have mulitple CD or CM servers. -->
 61 | 		<SitecoreInstanceName>ExamplePublishing</SitecoreInstanceName>
 62 | 
 63 | 		<!-- This section controls settings for Sitecore's Analytics -->
 64 | 		<Analytics>
 65 | 			<ClusterName></ClusterName>
 66 | 			<HostName></HostName>
 67 | 		</Analytics>
 68 | 
 69 | 		<!-- This value will be written to the reporting.api connection string. Only applies to Sitecore 8.2 -->
 70 | 		<ReportingApiKey>12345678901234567890123456789012</ReportingApiKey>
 71 | 		
 72 | 		<!-- Sitecore recommends changing the default password hash algorithm from SHA1 to SHA512
 73 | 		
 74 | 			For user management, Sitecore uses the Microsoft ASP.NET membership provider by default. 
 75 | 
 76 | 			*** IMPORTANT! ***
 77 | 			The Microsoft ASP.NET membership provider does not provide a facility for upgrading to a different hash algorithm after you have created 
 78 | 			user accounts. IF YOU CHANGE THE HASH ALGORITHM, EXISTING USERS CAN NO LONGER LOG INTO THE SYSTEM AND MUST CREATE A NEW PASSWORD.
 79 | 			
 80 | 			Valid values are:
 81 | 			- "" 
 82 | 			- a supported hash algorithm from the System.Security.Cryptography.CryptoConfig class : 
 83 | 			https://msdn.microsoft.com/en-us/library/system.security.cryptography.cryptoconfig(v=vs.110).aspx 
 84 | 		-->
 85 | 		<PasswordHashAlgorithm>SHA512</PasswordHashAlgorithm>
 86 | 
 87 | 		<CMServerSettings enabled="true">
 88 | 			<!-- If this value is non-empty, then admin's password will be set to this value -->
 89 | 			<DefaultSitecoreAdminPassword>foobar</DefaultSitecoreAdminPassword>
 90 | 
 91 | 			<!-- Add an Encryption Key for the Telerik controls 
 92 | 				  http://docs.telerik.com/devtools/aspnet-ajax/controls/asyncupload/security
 93 | 				 If using load-balanced CM servers, the value must match on both servers.
 94 | 			-->
 95 | 			<TelerikEncryptionKey></TelerikEncryptionKey>
 96 | 
 97 | 			<!-- Use these settings to dedicate Sitecore instance as the Publishing server. This is required
 98 | 			     when you are using load-balanced CM servers.
 99 | 			-->
100 | 			<Publishing enabled="true">
101 | 				<!-- This setting is ALWAYS applied to a CM server even if publishing is disabled. Therefore,
102 | 				     for an isolated CM you may leave this value blank or make sure it matches the CM
103 | 				     InstanceName
104 | 				-->
105 | 				<PublishingInstance>ExamplePublishing</PublishingInstance>
106 |                 <!-- Use these settings to enable IIS Application Initialization on a dedicated publishing instance.
107 |                      Setting enabled to true will:
108 |                         - Enable the Application Initialization feature on the web server
109 |                         - Add preloadEnabled="true" to the application configuration
110 |                         - Add applicationInitialization node to the system.webserver
111 | 						- Set doAppInitAfterRestart to true
112 |                         - Set the AppPool startMode to "AlwaysRunning"
113 |                         - Set the AppPool IdleTimeout to 0
114 |                         - Set the AppPool Recycling regular time interval to 0
115 |                      Valid values are "true" or "false"
116 | 				-->
117 |                 <ApplicationInitializationEnabled>true</ApplicationInitializationEnabled>
118 |                 <!-- Timeout length in minutes for IIS App Pool
119 |                      If enabled, Application Intialization will override this value with 0.
120 |                  -->
121 | 				<AppPoolIdleTimeout>0</AppPoolIdleTimeout>
122 | 				<!-- If this setting is false, the keepalive task will not run and the publishing server will get cold. -->
123 | 				<DisableScheduledTaskExecution>true</DisableScheduledTaskExecution>
124 | 				<Parallel enabled="true">
125 | 					<!-- If set, the autogrowth for data and log files of the web database and any copy of the
126 | 					     web database will be based on a fixed size of MB rather than a percentage. This follow
127 | 					     recommendations from Sitecore. Recommended values range from 30 to 50.
128 | 					     Valid values range from 10 to 100.
129 | 					-->
130 | 					<WebDatabaseAutoGrowthInMB>30</WebDatabaseAutoGrowthInMB>
131 | 					<MaxDegreesOfParallelism>4</MaxDegreesOfParallelism>
132 | 				</Parallel>
133 | 			</Publishing>
134 | 			<!-- Use these settings to dedicate Sitecore instance as a Processing server. -->
135 | 			<Processing enabled="false">
136 | 				<!-- Valid values are "true" or "false"
137 | 					 Invalid values or missing elements will be treated as "false"
138 | 				-->
139 | 				<ApplyIPWhitelist>true</ApplyIPWhitelist>
140 | 				<!-- Enabling this will cause recommended connection strings to be commented out -->
141 | 				<DeactivateConnectionStrings>true</DeactivateConnectionStrings>
142 | 				<!-- Enabling this setting causes some files on the Processing server to have ".disabled" concatenated to
143 | 					 their filename. Other files necessary for configuring a Processing file will be enabled. The files changed are from the recommendations here:
144 | 					 https://doc.sitecore.net/sitecore_experience_platform/setting_up_and_maintaining/xdb/configuring_servers/configure_a_processing_server
145 | 				-->
146 | 				<ConfigureFilesForProcessing>true</ConfigureFilesForProcessing>
147 | 				<!-- Denies anonymous users from accessing certain directories per Sitecore's recommendations -->
148 | 				<PreventAnonymousAccess>true</PreventAnonymousAccess>
149 | 			</Processing>
150 | 		</CMServerSettings>
151 | 
152 | 		<CDServerSettings enabled="false">
153 | 			<!-- Valid values are "true" or "false"
154 | 			     Invalid values or missing elements will be treated as "false"
155 | 			-->
156 | 			<ApplyIPWhitelist>true</ApplyIPWhitelist>
157 | 			<!-- Enabling this will cause recommended connection strings to be commented out -->
158 | 			<DeactivateConnectionStrings>true</DeactivateConnectionStrings>
159 | 			<!-- Enabling this setting causes some files on the CD server to have ".disabled" concatenated to
160 | 			     their filename. Other files necessary for configuring a CD such as the
161 | 			     SwitchMasterToWeb.config file will be enabled. The files changed are from the recommendations here:
162 | 			     https://doc.sitecore.net/sitecore%20experience%20platform/xdb%20configuration/configure%20a%20content%20delivery%20server
163 | 			-->
164 | 			<ConfigureFilesForCD>true</ConfigureFilesForCD>
165 | 			<!-- Denies anonymous users from accessing certain directories per Sitecore's recommendations -->
166 | 			<PreventAnonymousAccess>true</PreventAnonymousAccess>
167 | 			<!-- Prevent the execution of scripts or programs in the upload and temp folders -->
168 | 			<DenyExecutePermission>true</DenyExecutePermission>
169 | 			<!-- Enabling this setting prevents uploading files outside of the Sitecore client -->
170 | 			<DisableUploadWatcher>true</DisableUploadWatcher>
171 | 			<!-- If you have implemented custom code that uses ASP.NET Web API attribute routing, to avoid errors, disable the following -->
172 | 			<DisableExperienceAnalyticsAssemblies>true</DisableExperienceAnalyticsAssemblies>
173 | 			<!-- Remove PhantomJs from CD per Sitecore's recommendations -->
174 | 			<RemovePhantomJs>true</RemovePhantomJs>
175 | 			<!-- Disables Telerik UI Handlers on CD server. -->
176 | 			<DisableTelerikControls>true</DisableTelerikControls>
177 | 		</CDServerSettings>
178 | 
179 | 		<!-- Media Request Protection - Applied to CM and CD Servers -->
180 | 		<MediaRequestProtection>
181 | 			<!-- In a multi-instance setup, use the same value for Media.RequestProtection.SharedSecret on every instance.
182 | 				 SharedSecret is required. If no value is provided, Sitecore default value will be used. -->
183 | 			<SharedSecret></SharedSecret>
184 | 			<!-- Specifies whether the media request protection feature will output detailed information to the Sitecore log file.
185 | 				 If no value is provided, Sitecore default value (true) will be used. -->
186 | 			<LoggingEnabled>true</LoggingEnabled>
187 | 		</MediaRequestProtection>
188 | 
189 | 		<!-- Hardened directories in IIS will deny all clients except the following IPs -->
190 | 		<IPWhiteList>
191 | 			<IP>127.0.0.1</IP>
192 | 			<IP>10.10.20.7</IP>
193 | 			<IP>10.10.20.11</IP>
194 | 		</IPWhiteList>
195 | 
196 | 		<SessionStateProvider>
197 | 			<!-- Valid values for Private and Shared are:
198 | 			       - InProc
199 | 			       - MSSQL (except for Shared on a CM!)
200 | 			       - Mongo (currently not supported by the installer)
201 | 			-->
202 | 			<Private>mssql</Private>
203 | 			<Shared>InProc</Shared>
204 | 		</SessionStateProvider>
205 | 
206 | 		<Solr>
207 | 			<!-- If provided, the installer will modify the
208 | 			     Sitecore.ContentSearch.Solr.DefaultIndexConfiguration.config.example file to use the given address
209 | 			-->
210 | 			<ServiceBaseAddress>http://solr5:8888/solr</ServiceBaseAddress>
211 | 		</Solr>
212 | 
213 | 		<!-- This section determines how the connection strings for for MongoDB will be formed. Any values
214 | 			 left blank will not be used. The settings below adhere to MongoDB's connection string format
215 | 			 specification: https://docs.mongodb.org/manual/reference/connection-string/
216 | 
217 | 			 If this section is not enabled, it will be ignored.
218 | 		-->
219 | 		<MongoDb enabled="true">
220 | 			<!-- Optional, won't be used if blank -->
221 | 			<Credentials>
222 | 				<Username>someuser</Username>
223 | 				<Password>somepassword</Password>
224 | 			</Credentials>
225 | 			<!-- At least one <Host> is required, each <Host> must specify a <HostName> and an optional <Port> -->
226 | 			<Hosts>
227 | 				<Host>
228 | 					<HostName>node1.company.com</HostName>
229 | 					<Port>27017</Port>
230 | 				</Host>
231 | 				<Host>
232 | 					<HostName>node2.company.com</HostName>
233 | 					<Port>9999</Port>
234 | 				</Host>
235 | 			</Hosts>
236 | 			<!-- This setting's value will be appended to the connection string's URI. The format should be as a
237 | 			     query string.
238 | 			-->
239 | 			<Options>?authMechanism=PLAIN&amp;authSource=$external&amp;replicaSet=mymongoset</Options>
240 | 		</MongoDb>
241 | 
242 | 	</WebServer>
243 | 
244 | 		<!-- If disabled the script will skip ALL database related operations.
245 | 			   - No SQL server connection tests
246 | 			   - Databases files will not be copied or attached
247 | 			   - User mappings, permissions will not be set
248 | 			   - Autogrowth will not be set on web database (relevant to parallel publishing)
249 | 
250 | 			 Regardless the information in this section will still be used to form connection string values.
251 | 			 Thus, ensure that the database names are always accurate as well as the SQL server name and data
252 | 			 access account information.
253 | 			Type: Azure, Local
254 | 			Using Azure requires the installation of the Dacfx
255 | 			https://www.microsoft.com/en-us/download/confirmation.aspx?id=55255
256 | 		-->
257 | 		<Database type="Azure" enabled="true">
258 | 			<Azure>
259 | 				<SQLPackagePath>C:\Program Files\Microsoft SQL Server\140\DAC\bin\sqlpackage.exe</SQLPackagePath>
260 | 				<SQLResourceGroup></SQLResourceGroup>
261 | 				<SQLEdition></SQLEdition>
262 | 				<SQLMaxSize></SQLMaxSize> <!-- in Bytes -->
263 | 				<SQLServiceObjective></SQLServiceObjective>
264 | 			</Azure>
265 | 
266 | 		<!-- Valid values are "true" or "false" Invalid values or missing element will be treated as "false"
267 | 		     Note that even if you do not install the database, database mappings and permissions will still
268 | 		     be written.
269 | 		-->
270 | 		<InstallDatabase>false</InstallDatabase>
271 | 
272 | 		<!-- Do not edit this list unless you know what you are doing! :) This list represents the all of
273 | 		     the default databases used by Sitecore.
274 | 		-->
275 | 		<DatabaseNames>
276 | 			<name>Core</name>
277 | 			<name>Master</name>
278 | 			<name>Web</name>
279 | 			<name>Sessions</name>
280 | 			<name>Reporting</name>
281 | 		</DatabaseNames>
282 | 
283 | 		<!-- Add <copy> elements for each duplicate web database to be created -->
284 | 		<WebDatabaseCopies>
285 | 			<!-- Setting the connectionStringName attribute will assign that value to the "name" attribute
286 | 			     of the connection string for this databse. For example, if the connectionStringName is "web"
287 | 			     then the web connection string will point to the preview database. This is useful for creating
288 | 			     a preview-type CD server that serves content out of a different database than the normal, web
289 | 			     database. If the attribute is missing or does not have a value, then the name of the copy
290 | 			     database will be used to create the name of the connection string.
291 | 
292 | 			     NOTE: The "web" database is referred to in many places in Sitecore’s configuration:
293 | 				   - Database definitions
294 | 				   - Agents
295 | 				   - Index definitions
296 | 				   - Indexing strategies
297 | 				   - Site definitions
298 | 
299 | 			     Thus, you will need to think about patching the Sitecore's .config files to address this behavior.
300 | 
301 | 				 * On the preview CD server, by replacing the "web" connection string’s database with a preview
302 | 				 database, you can avoid much of this configuration work.  If you are using Lucene, you
303 | 				 shouldn't need to do anything else. If you are using Solr, I STRONGLY recommend you create
304 | 				 dedicated 'preview' versions of web indexes and indexing strategies.
305 | 
306 | 				 * On the CM server, you should consider doing the following:
307 | 				   - Configuring a <database> element similar to the web's
308 | 				   - If you want schedule periodic publishing, then create an <agent> for Sitecore.Tasks.PublishAgent
309 | 				     to publish to your preview database
310 | 				   - If you use WebDAV, consider adding your preview database to the
311 | 				     Sitecore.Tasks.CleanupFDAObsoleteMediaData <agent>
312 | 				   - Create 'preview' version of the onPublishEndAsync and onPublishEndAsyncSingleInstance index
313 | 				     update strategies
314 | 				   - Create Index definitions for the 'preview' versions of your 'web' indexes. This is especially
315 | 				     important if you use Solr!
316 | 			-->
317 | 			<copy>Preview</copy>
318 | 			<copy connectionStringName="altpreview">Preview2</copy>
319 | 		</WebDatabaseCopies>
320 | 
321 | 		<!-- The format is: {sqlservername[\instancename]}[,{port}]
322 | 			 Examples
323 | 			 - vmwebdev01
324 | 			 - vmwebdev01,1433
325 | 			 - vmwebdev01\myinstance
326 | 			 - vmwebdev01\myinstance,1433
327 | 			 Azure
328 |  			 - exampleDB.database.windows.net
329 | 		-->
330 | 		<SqlServerName>vmwebdev01,1433</SqlServerName>
331 | 
332 | 		<!-- This login is used to attach databases and assign roles in SQL. The login must have the sysadmin
333 | 			 server role.
334 | 		-->
335 | 		<SqlLoginForInstall>SC_InstallAccount</SqlLoginForInstall>
336 | 		<SqlLoginForInstallPassword>P@ssword</SqlLoginForInstallPassword>
337 | 
338 | 		<!-- If specified, this login will be used in connection strings. Only SQL logins are valid. -->
339 | 		<SqlLoginForDataAccess></SqlLoginForDataAccess>
340 | 		<SqlLoginForDataAccessPassword></SqlLoginForDataAccessPassword>
341 | 
342 | 		<!-- If true, then the ApplicationPoolIdentity will be used for the SQL login rather than
343 | 		     SqlLoginForDataAccess. This setting requires a domain account is specified for the
344 | 		     ApplicationPoolIdentity.
345 | 		-->
346 | 		<UseWindowsAuthenticationForSqlDataAccess>true</UseWindowsAuthenticationForSqlDataAccess>
347 | 
348 | 		<DatabaseInstallPath>
349 | 			<DataFiles>
350 | 				<!-- Must be defined, and folder must exist. The SQL instance must have FullControl over the folder.
351 | 					 This value is used to attach the databases in SQL. If the Unc value is missing, this is also the
352 | 					 path used as the destination for SQL database file copying.
353 | 				-->
354 | 				<Local>C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\installdemo data files</Local>
355 | 
356 | 				<!-- If defined this path will be used to copy database files into the file system of the
357 | 					 SQL server.
358 | 				-->
359 | 				<Unc>\\VMWEBDEV01\installdemo data files</Unc>
360 | 			</DataFiles>
361 | 
362 | 			<!-- This sectional is optional. If undefined, then log files will be installed in the same location
363 | 				 the same location as the data files defined above.
364 | 			-->
365 | 			<LogFiles>
366 | 				<!-- Must be defined, and folder must exist. The SQL instance must have FullControl over the folder.
367 | 					 This value is used to attach the databases in SQL. If the Unc value is missing, this is also the
368 | 					 path used as the destination for SQL database file copying.
369 | 				-->
370 | 				<Local>C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\installdemo log files</Local>
371 | 
372 | 				<!-- If defined this path will be used to copy database files into the file system of the
373 | 					 SQL server.
374 | 				-->
375 | 				<Unc>\\VMWEBDEV01\installdemo log files</Unc>
376 | 			</LogFiles>
377 | 		</DatabaseInstallPath>
378 | 
379 | 		<DatabaseNamePrefix>InstallDemo_Sitecore_</DatabaseNamePrefix>
380 | 
381 | 	</Database>
382 | 
383 | </InstallSettings>
384 | 


--------------------------------------------------------------------------------