SharePoint Cross-site Configurator

Source code checked in, #69631

Project Collection Service Accounts — Mon, 01 Oct 2012 21:13:48 GMT

Upgrade: New Version of LabDefaultTemplate.xaml. To upgrade your build definitions, please visit the following link: http://go.microsoft.com/fwlink/?LinkId=254563

Source code checked in, #69630

Project Collection Service Accounts — Mon, 01 Oct 2012 21:07:03 GMT

Checked in by server upgrade

New Post: Does this work with 2010?

jime — Sat, 14 Jan 2012 04:26:52 GMT

Does this tool work with 2010? I hope so.

Source code checked in, #48968

_TFSSERVICE — Thu, 22 Jul 2010 18:55:41 GMT

Checked in by server upgrade

Reviewed: SharePoint Cross-site Configurator Guide (Apr 13, 2009)

ash4farooq — Mon, 13 Apr 2009 11:52:00 GMT

Rated 4 Stars (out of 5) - Very helpful

New Post: Content Types

panoone — Tue, 03 Feb 2009 00:44:09 GMT

Does this only apply to the top-level site?

Is there any tool available which will allow you to deploy content types between farms and sites?

New Post: Need help?

saikodi — Fri, 14 Nov 2008 14:31:41 GMT

Hello Yeshwanth,

Exact details on how to modify the Setup.bat file and editing the App.Config file are present in the user guide: SharePoint_Cross-site_Configurator_Guide.docx. Please download the guide and read. If you have further questions, please post here.

Thanks,
Sai Kodi

New Post: Need help?

yeshwanthhv — Thu, 28 Aug 2008 11:51:13 GMT

Hi,

How can I deploy this across the farm? Can you give me more details regarding changing appconfig and Setup.bat so that I can deploy this in my farm.It woule be really great if you can provide these details.

-Yesh

New Post: Content Types

olegg — Fri, 20 Jun 2008 22:29:40 GMT

Neil,
What Configurator can do out of the box is limited to setting content type settings, not rolling them out.

From the user guide:

Adding Advanced Settings

List settings are used to set the advanced settings for all lists and libraries. The following code segment applies the setting “Allow content type Management = true” to the defined lists.

</ListSettings>

Neilww wrote:
Hi, how do I use the cross-site configurator to deploy multiple content types across multiple site collections?

Thanks,

Neil

New Post: Content Types

Neilww — Fri, 20 Jun 2008 13:18:41 GMT

Hi, how do I use the cross-site configurator to deploy multiple content types across multiple site collections?

Thanks,

Neil

New Post: Functional questions

olegg — Wed, 18 Jun 2008 17:11:02 GMT

That's correct. This is a limitation of the tool.

jmurray_mi wrote:
In the documentation the prerequisites lists "The MOSS sites that you want to deploy the solution to must be a publishing Web". Does this mean that this utility will only work on:

a) MOSS publishing site templates with or without workflow and/or
b) Any site template, including WSS, where the publishing infrastructure has been enabled as part of a MOSS farm

Or is that an inaccurate statement?

New Post: Feature not listed in Site Settings -> Site Features

olegg — Wed, 18 Jun 2008 17:09:57 GMT

Sounds like Feature was not installed or activating. Are you getting any error messages from setup.bat ?

parag24 wrote:
Hi,

I have configured settings in AppConfig.xml file and updated batch file setup.bat of "SharePoint Crosss -site Configurator".

But after running batch file on MOSS server i am not able to find this feature in site settings -> Site Features.

And even feature not activated automatically which i have mentioned in Application configure file.

Please let me now for any steps to quickly resolve it.

Thanks,
Parag Bhavsar

NEW POST: Feature not listed in Site Settings -> Site Features

parag24 — Fri, 18 Apr 2008 09:49:25 GMT

Hi,

I have configured settings in AppConfig.xml file and updated batch file setup.bat of "SharePoint Crosss -site Configurator".

But after running batch file on MOSS server i am not able to find this feature in site settings -> Site Features.

And even feature not activated automatically which i have mentioned in Application configure file.

Please let me now for any steps to quickly resolve it.

Thanks,
Parag Bhavsar

NEW POST: Functional questions

jmurray_mi — Mon, 03 Mar 2008 17:49:39 GMT

In the documentation the prerequisites lists "The MOSS sites that you want to deploy the solution to must be a publishing Web". Does this mean that this utility will only work on:

a) MOSS publishing site templates with or without workflow and/or
b) Any site template, including WSS, where the publishing infrastructure has been enabled as part of a MOSS farm

Or is that an inaccurate statement?

NEW POST: Rolling back customizations

rdcpro — Fri, 29 Feb 2008 17:17:41 GMT

joelo wrote:
Can you give the flow for the master page one? Like what happens? It pushes it and yanks it or sets it back to the previous?

It appears to me that it runs through each masterPage in the AppSettings file, and resets the custom and default masters it to the default master page.

foreach (ApplyMasterPage masterPage in AppSettings.ApplyMasterPages)
{
switch (masterPage.MasterPageType)
{
case MasterPageType.SystemMasterPage:

web.CustomMasterUrl = "/_catalogs/masterpage/default.master";
break;

case MasterPageType.RegularMasterPage:
web.MasterUrl = "/_catalogs/masterpage/default.master";
break;
}
}

I would have thought it would reset to the one that was saved in the backup settings file:

foreach (ApplyMasterPage masterPage in AppSettings.ApplyMasterPages)
{
ApplyMasterPage masterPageForRetract = new ApplyMasterPage();
switch (masterPage.MasterPageType)
{
case MasterPageType.RegularMasterPage:
masterPageForRetract.Name = web.MasterUrl;
masterPageForRetract.MasterPageType = MasterPageType.RegularMasterPage;
break;

case MasterPageType.SystemMasterPage:
masterPageForRetract.Name = web.CustomMasterUrl;
masterPageForRetract.MasterPageType = MasterPageType.SystemMasterPage;
break;
}
ApplyMasterPages.Add(masterPageForRetract);
}

Maybe I'm missing something here?

Regards,
Mike Sharp

NEW POST: Rolling back customizations

joelo — Thu, 28 Feb 2008 22:20:44 GMT

Can you give the flow for the master page one? Like what happens? It pushes it and yanks it or sets it back to the previous?

NEW POST: Rolling back customizations

olegg — Fri, 15 Feb 2008 22:07:52 GMT

The only thing tool will actually "pull out" is the master page. Other settings are left in place, and can be turned off using a "false" parameter. For example you can deploy audit setting (turn checkbox to "checked") and then pull the feature out. The checkbox will stay turned on. To set it to "off" position you would have to deploy solution again with that parameter explicitly identified as "false".

NEW POST: Rolling back customizations

rdcpro — Wed, 13 Feb 2008 19:47:06 GMT

I like this tool, but I'm concerned that customizations made after the tool is activated would be lost on deactivation. I think it would be better if instead of reapplying the configurations that were in place before the tool was activated, you iterate through the current AppSettingsContainer from LoadExistingAppSettingsFromSPSite and check each setting against the original deployed configuration on this tool.

If the current node in AppSettingsContainer is configured the same as the node in the AppSettingsModifier.XMLCONFIGFILE then apply the configuration from the corresponding node in AppSettingsModifier.XMLRETRACTCONFIGFILE.
Else, it would seem that the setting has changed from when you first activated this solution. This case should be examined to see if the configuration change is a result of a lack of change management process, and needs to be added into this solution as a standard configuration, or it's extraneous and can be removed.

I bet if you deactived this feature a long time after it was first deployed, because it applies the original configuration on SharePoint, you'd find yourself restoring from the most recent backup. ;^)

Regards,
Mike Sharp

NEW POST: Can I get a sample already compiled?

slauterhaus — Fri, 08 Feb 2008 01:01:09 GMT

The installation instructions don't seem to coincide with the installation files provided. It talks about using spadmin to install the solution whereas the zip contains a setup.bat. And the instructions don't give much directions regarding when/how/where to edit the appconfig.xml file or how to activate the features for MOSS. Could we get a more complete administrator guilde?

NEW POST: Expiration Policies

olegg — Fri, 08 Feb 2008 00:32:28 GMT

As it stands the code does not support this feature.