This project has moved. For the latest updates, please go here.

Clarification on the new Provision synax

Topics: Feedback, General Questions, Support
Nov 26, 2013 at 2:57 PM
Edited Nov 26, 2013 at 3:03 PM
I am just migrating an old 3.93 based script to the latest 3.96 standard and to add to the complications from SP2010 to SP2013

The new provision syntax used to require either "true" or "false"; whereas, the new syntax means can specify the SharePoint server we want provision the service app on (see code below) . So is the following valid settings for provision

"localhost" - the current server
"true" - similar to localhost so current server
"false" - don't provision anywhere
"servername" - provision the service on the named server.
 <ManagedMetadataServiceApp Provision="localhost"
                                   Name="Managed Metadata Service"
                                   ProxyName="Managed Metadata Service">
Nov 26, 2013 at 8:11 PM
also sever,server1,server2 is supported.
Nov 26, 2013 at 11:48 PM
Correct - in a single-server farm, "localhost" is essentially equivalent to "true". Although the ability to specify single or multiple servername values has been around for a while so it's not really new.

And thanks for the further clarification Ivan!

Marked as answer by brianlala on 12/13/2013 at 1:04 PM
Nov 27, 2013 at 8:06 AM
Thanks Brian and Ivan
Marked as answer by brianlala on 12/13/2013 at 1:04 PM