Following error message appears and turns the script to be halted:
-------------------------------------------------------------------------------
- Script halted!
- Provisioning Managed Metadata Service Application
- Managed Account BEPIPELINE\SVC_SP2010_SERVICE BEPIPELINE\SVC_SP2010_FARM not found
At C:\install\SP\AutoSPInstaller\AutoSPInstallerFunctions.ps1:1346 char:41
+ If ($managedAccountGen -eq $null) { Throw " - Managed Account $($spservice.u ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : OperationStopped: ( - Managed Acco..._FARM not found:String) [], RuntimeException
+ FullyQualifiedErrorId : - Managed Account BEPIPELINE\SVC_SP2010_SERVICE BEPIPELINE\SVC_SP2010_FARM not found
-------------------------------------------------------------------------------
My InputFile looks as following:
<?xml version="1.0" ?>
<!-- AutoSPInstaller Sample Configuration File
General Instructions:
1. If you use the characters ' " < > & in your configuration (e.g. in passwords) you should encode them as follows:
' '
" "
< <
> >
& &
For example <Password>Fd"je&f</Password> should be written <Password>Fd"je&f</Password>
2. Configuration IS case sensitive.
3. Use a validator like http://www.w3schools.com/xml/xml_validator.asp to check the syntax of your file.
4. Any element that has a Provision="" attribute controls whether a particular component, site, or service is installed
on a particular server. It can be set to either true to provision on every server on which the script is run,
false to never provision, or to a list of computer names to provision the service only on the listed machines.
This allows you to configure an entire multi-server farm with different servers fulfilling different roles
using a single configuration file.
e.g. <ExcelServices Provision="Server1 Server2"> would provision excel services only on Server1 and Server2. -->
<Configuration Environment="Dev" Version="3.2">
<!-- The Environment attribute above appears at the top of the installation transcript. It does not affect the installation -->
<!-- The Install section controls what modifications are made to the Windows OS prior to installation and how the SharePoint installation is run -->
<Install>
<!-- ConfigFile is the name of the file containing the unattended install settings for SharePoint's setup.exe
You must put your product key in this file -->
<ConfigFile>config.xml</ConfigFile>
<!-- If true, the SharePoint prerequisite installer will install from the \SharePoint\PrerequisiteInstallerFiles folder.
If false, the prerequisites will be downloaded during install. In order to use true you must obviously download all the prerequisites in advance.
You can use a script like http://autospinstaller.codeplex.com/releases/view/44442 to quickly accomplish this -->
<OfflineInstall>true</OfflineInstall>
<!-- Set <PauseAfterInstall> to true in order to pause the script after the SharePoint binaries are installed.
Useful for running the binary install simultaneously on multiple servers but stopping short of the farm config (which can cause conflicts if running on multiple servers at once) -->
<PauseAfterInstall>false</PauseAfterInstall>
<!-- Set RemoteInstall Enable="true" to attempt a centralized, remote install & config of your entire farm -->
<RemoteInstall Enable="false">
<!-- ParallelInstall controls whether SharePoint binary file installs are triggered simultaneously on all servers in the farm during a remote install. Can speed things up considerably (unless of course all your VMs are running on the same host, sharing I/O resources etc.!) -->
<ParallelInstall>false</ParallelInstall>
</RemoteInstall>
<!-- AutoAdminLogon tells the script to place values in the registry that allow automatic logon with the install account credentials (only), should the installation proces require reboot(s).
In combination with the RunOnce entry, it gives a better unattended experience (as there can be several reboots now with SharePoint 2013).
Only the dedicated install account is supported; you can enter its password below. Note that it will be stored in PLAIN TEXT, both here and in the registry so be sure to change it afterwards (or disable the account).
Otherwise, you can leave the password blank in order to be prompted at run-time (though it will still be stored in plain text in the registry, at least until the server is rebooted once more after the install. -->
<AutoAdminLogon Enable="true" Password="PaSSwoRD" />
<Disable>
<!-- Disables network loopback checks. This prevents the OS blocking access to your server under names other than its actual host name,
which SharePoint needs to do for WebDAV requests. -->
<LoopbackCheck>true</LoopbackCheck>
<!-- Disables windows services that are running by default on Windows 2008 that are not used by SharePoint to conserve resources -->
<UnusedServices>true</UnusedServices>
<!-- Switch off IE Enhanced Security configuration, so that your sites and Central Admin render properly in a browser on the server -->
<IEEnhancedSecurity>true</IEEnhancedSecurity>
<!-- Switch off checking whether the code-signing certificates used to sign the SharePoint code have been revoked. This slows down the
start up time for SharePoint, particularly if the server cannot connect to the Internet to perform the revocation check. -->
<CertificateRevocationListCheck>true</CertificateRevocationListCheck>
</Disable>
</Install>
<!-- The Farm section contains basic farm-wide settings -->
<Farm>
<!--Enter the passphase that will be used to join additional servers to the farm. This farm passphrase will also be used for the Secure Store service app-->
<Passphrase>PaSSPHrase!</Passphrase>
<!-- The "Farm" account that will be used to run Central Administration and the timer service. If AddToLocalAdminsDuringSetup is true, it will be
added to the server's local administrators group for the duration of the execution of the script. This is required for some steps, such as
configuring the User Profile Synchronization service. If for some reason you need to leave the Farm account in the Administrators group after setup, set LeaveInLocalAdmins to true -->
<Account AddToLocalAdminsDuringSetup="true" LeaveInLocalAdmins="true">
<Username>CUSTOMER\SVC_SP2010_FARM</Username>
<Password>PaSSwoRD</Password>
<Email></Email>
</Account>
<!-- Which server(s) to provision CentralAdmin on. Specify "true" or a list of servers -->
<CentralAdmin Provision="true">
<Database>CUSTOMER_SP2013_AdminContent</Database>
<Port>7777</Port>
<UseSSL>false</UseSSL>
</CentralAdmin>
<Database>
<!-- If you are creating an alias (recommended!), <DBServer> is actually the value of the SQL alias; otherwise it's the NetBIOS name of the SQL server or instance.
If you leave <DBServer> blank or specify localhost, script will assume the local server for SQL databases -->
<DBServer>SQL_ALIAS</DBServer>
<!-- The script can create a SQL alias for you. Enter the DBInstance, and if you leave <DBPort> blank, script will assume default port value of 1433 -->
<DBAlias Create="true"
DBInstance="SERVER9005\SQL_ALIAS"
DBPort="1434" />
<!-- The DBPrefix is prepended to all database names. e.g. If you set this to TEST, your config DB will be TEST_ConfigDB.
If you set the prefix to localhost, script will prepend each database with the name of the server on which the script is run.
Leave this blank for no prefix.
NOTE: If you are installing a multi-server farm, it is recommended that you do not use localhost as services provisioned on different servers
will have different prefixes.
-->
<DBPrefix>CUSTOMER_SP2013</DBPrefix>
<!-- The name of the farm configuration database -->
<ConfigDB>Config</ConfigDB>
</Database>
<!-- The Services section configures the core service instances & components that are part of SharePoint Foundation -->
<Services>
<SandboxedCodeService Start="false" />
<ClaimsToWindowsTokenService Start="false" />
<SMTP Install="false" />
<OutgoingEmail Configure="false">
<SMTPServer></SMTPServer>
<EmailAddress></EmailAddress>
<ReplyToEmail></ReplyToEmail>
</OutgoingEmail>
</Services>
Part1
Comments: ** Comment from web user: AndreOL **
<!-- The ManagedAccounts section configures all accounts that will be added to SharePoint as managed accounts. -->
<ManagedAccounts>
<!-- The CommonName values should remain unchanged; you can add additional managed accounts, but script expects certain static values for these 4 managed accounts.
If you are creating additional web applications, use a new account for each web application with a new common name, unless you are creating a large number
of web applications, in which case the additional memory consumption this requires outweighs the security benefits. -->
<ManagedAccount CommonName="spservice">
<Username>CUSTOMER\SVC_SP2010_SERVICE</Username>
<Password>PaSSwoRD</Password>
</ManagedAccount>
<ManagedAccount CommonName="spservice">
<Username>CUSTOMER\SVC_SP2010_FARM</Username>
<Password>PaSSwoRD</Password>
</ManagedAccount>
<ManagedAccount CommonName="portalapppool">
<Username>CUSTOMER\SVC_SP2010_APP</Username>
<Password>PaSSwoRD</Password>
</ManagedAccount>
<ManagedAccount CommonName="mysiteapppool">
<Username>CUSTOMER\SVC_SP2010_MYAPP</Username>
<Password>PaSSwoRD</Password>
</ManagedAccount>
<ManagedAccount CommonName="searchservice">
<Username>CUSTOMER\SVC_SP2010_SEARCH</Username>
<Password>PaSSwoRD</Password>
</ManagedAccount>
</ManagedAccounts>
<!-- The object cache accounts are user accounts that are given FullControl and FullRead privileges on WebApplications so items can be cached by ASP.Net to improve performance.
These accounts should not have any special Active Directory privileges other than Domain User membership -->
<ObjectCacheAccounts>
<SuperUser>CUSTOMER\SVC_SP2010_PSUA</SuperUser>
<SuperReader>CUSTOMER\SVC_SP2010_PSRA</SuperReader>
</ObjectCacheAccounts>
<!-- The <Logging> section allows you to move various log files to another location / volume, per best practices and to control disk space usage on the (default) C: drive.
It also allows you to specify some logging options, such as using NTFS compression for additional disk space savings.
The <Path> for all log types will be created if it doesn't yet exist. However, the root (drive, e.g. D:) must obviously pre-exist - and on ALL servers in your farm. -->
<Logging>
<IISLogs Compress="true">
<!-- The default <Path> is $Env:SystemDrive\Inetpub\logs\LogFiles - enter another path (e.g. D:\IISLogs) or leave <Path> empty to use the default. -->
<Path>D:\IIS_LOGS</Path>
</IISLogs>
<ULSLogs Compress="true">
<!-- The default <LogLocation> is $Env:CommonProgramFiles\Microsoft Shared\Web Server Extensions\LOGS - enter another path (e.g. D:\Logs) or leave <LogLocation> empty to use the default. -->
<LogLocation>D:\ULS_LOGS</LogLocation>
<!-- <LogDiskSpaceUsageGB> specifies the maximum amount of disk space (GB) to use. If you specify a value here, LogMaxDiskSpaceUsageEnabled will automatically be set to True.
Leave empty to use the default values (1000 GB, but with LogMaxDiskSpaceUsageEnabled set to False - so effectively NO restriction on disk space) -->
<LogDiskSpaceUsageGB>10</LogDiskSpaceUsageGB>
<!-- <DaysToKeepLogs> specifies the time, in days, to retain diagnostic log files. Leave empty to use the default (14 days). -->
<DaysToKeepLogs>30</DaysToKeepLogs>
<!-- <LogCutInterval> specifies the time, in minutes, before a new log file is generated. Leave empty to use the default (30 minutes). -->
<LogCutInterval>30</LogCutInterval>
</ULSLogs>
<UsageLogs Compress="true">
<!-- The default <UsageLogDir> is $Env:CommonProgramFiles\Microsoft Shared\Web Server Extensions\LOGS - enter another path (e.g. D:\Logs) or leave <UsageLogDir> empty to use the default. -->
<UsageLogDir>D:\ULS_LOGS</UsageLogDir>
<!-- <UsageLogMaxSpaceGB> must be between 1 and 20 GB. Leave empty to use the default (5 GB) -->
<UsageLogMaxSpaceGB>10</UsageLogMaxSpaceGB>
<!-- <UsageLogCutTime> specifies the time, in minutes, of usage data collected per usage log file (acceptable values are between 1 and 1440, default 5). Leave empty to use the default. -->
<UsageLogCutTime>5</UsageLogCutTime>
</UsageLogs>
</Logging>
</Farm>
<!-- The WebApplications section configures the applications and sites that will be created. You can add additional <WebApplication> child tags to create extra web applications.
The AddURLsToHOSTS flag will add all Alternate Access Mappings to the local server's HOSTS file and is useful if you are (for example):
creating web apps whose URLs are not defined in DNS yet, a test farm, or if you are creating a DR farm, etc. -->
<WebApplications AddURLsToHOSTS="true">
<!-- Web application attributes are as follows:
type:
"Portal" is the primary site. Exactly one WebApplication should have this type. It is setup as a trusted file location
for Excel services, and as the portal site connection for other site collections. The script also uses it internally
when it requires the URL of an arbitrary site.
"MySiteHost" is the host web application for mysites.
Any additional web applications that you create should have a type of your own choice such as "Other"
name: Name of the web application
applicationPool: Application pool name
applicationPoolAccount: CUSTOMER\SVC_SP2010_APP of the account under which the application pool runs. This should be a managed account.
url: URL of the root site collection in the application pool. Do not include the port number, but do set http/https correctly.
port: Port on which the web application runs.
databaseName: Name of the first content database.
useClaims: false = disable claims based authentication. true = enable claims based authentication.
useBasicAuthentication: false = only accept Kerberos/NTLM claims. true = also accept Basic authentication claims. Has no effect if useClaims is false.
useOnlineWebPartCatalog: false = disable use of the online webpart gallery on the web application. true (default) enable it. -->
<WebApplication type="Portal"
name="Portal"
applicationPool="Portal"
applicationPoolAccount="CUSTOMER\SVC_SP2010_APP"
url="http://sharepoint"
port="80"
AddURLToLocalIntranetZone="true"
databaseName="SharepointContent"
useClaims="true"
useBasicAuthentication="false"
useOnlineWebPartCatalog="false">
<!-- You can now specify a different DB server/instance or alias per web application and service application. The behavior is slightly different than with the farm DB server though, see below. -->
<Database>
<!-- If you are creating an alias (recommended!), <DBServer> is actually the value of the SQL alias; otherwise it's the NetBIOS name of the SQL server or instance.
If you leave <DBServer> blank, the default DBServer value for the farm is used -->
<DBServer>SQL_ALIAS</DBServer>
<!-- The script can create a SQL alias for you. Enter the DBInstance, and if you leave <DBPort> blank, script will assume default port value of 1433 -->
<DBAlias Create="false"
DBInstance="SERVER\INSTANCE"
DBPort="" />
</Database>
<ManagedPaths>
<ManagedPath relativeUrl="help" explicit="true" />
</ManagedPaths>
Part2