How to Deploy Service Manager Webparts to an Existing SharePoint Site

re: How to Deploy Service Manager Webparts to an Existing SharePoint Site

Robert — Thu, 28 Feb 2013 14:02:24 GMT

Yeah I have to agree with Anton. Much better to just install the product and remove parts you don't want later. For most System Center professionals there is limited access to SharePoint development anyway, and all of this just seems like a pain in the neck. Cool stuff, but I for sure would not implement the Service Catalog this way.

re: How to Deploy Service Manager Webparts to an Existing SharePoint Site

Joshua — Tue, 02 Oct 2012 19:17:26 GMT

I agree with Anton, it would easier to jsut deploy the WSP, if you dont want the master page, and other webparts available, just remove them after deployment. That is a much more supportable senario.

Done the way this blog discribes, can become a disaster recovery nightmare, if the person that originally set it up is no longer available, and didnt document thier steps.

My personaly approach has always been to avoid manual web.config edits when at all possible. And in this situation it seems very possible to avoid it.

re: How to Deploy Service Manager Webparts to an Existing SharePoint Site

Josh Nylander — Mon, 06 Aug 2012 20:09:37 GMT

I would REALLY like to be able to install the web parts on our Sharepoint Online (Office365) site. I would be ok installing the whole WSP as Anton suggests however I do not think it is possible for me to set the Application property SMPortal_WebContentServer_URL in a shared environment. And, as a side note, it would be most helpful if the WSP file could be accessed without doing a local install.

re: How to Deploy Service Manager Webparts to an Existing SharePoint Site

Travis Wright MSFT — Mon, 13 Feb 2012 16:41:07 GMT

@Rob - You can use SharePoint 2010 Foundation Edition which doesnt cost anything.

re: How to Deploy Service Manager Webparts to an Existing SharePoint Site

Rob — Mon, 13 Feb 2012 01:23:01 GMT

What if you are moving from 2010 using the portal on IIS to 2012 and you don't have Sharepoint?

re: How to Deploy Service Manager Webparts to an Existing SharePoint Site

Travis Wright MSFT — Mon, 06 Feb 2012 18:17:55 GMT

@Johnny -

Yes, you can install the SCSM SPP on an existing SP server/farm. It will add a new site and shouldn't affect any other sites already on the SP server.

re: How to Deploy Service Manager Webparts to an Existing SharePoint Site

Johnny — Sun, 05 Feb 2012 12:42:06 GMT

If I alreay have a Sharepoint server in production, running other websites, can´t I just install the SCSM SSP direct on that server?

What will happen then?

Will it affect the other systems?

re: How to Deploy Service Manager Webparts to an Existing SharePoint Site

Anton Gritsenko - FreemanRU — Wed, 01 Feb 2012 17:34:37 GMT

Thanks Martha to respond. You right about additional features but I can't see any potential issues with that. Even if all that themes, styles and etc will be deployed - they just added to collections and will not be used until someone create new site based on this templates\thems. Or I miss something?

Anyway, here is step-by-step guid to deploy Microsoft.EnterpriseManagement.ServiceManager.Portal.SharePointSite.wsp. __blog.scsmsolutions.com/.../install-scsm12-web-parts-to-existing-sharepoint

re: How to Deploy Service Manager Webparts to an Existing SharePoint Site

Martha — Mon, 30 Jan 2012 20:00:00 GMT

Hi Anton, Thanks for the feedback!

The solution you mentioned is valid if you don’t mind deploying all the features shipped as part of “Microsoft.EnterpriseManagement.ServiceManager.Portal.SharePointSite.wsp” to your SharePoint site/site collection.

However this blog is focusing on a clean way of deploying a specific SM Webpart (not all) to your SharePoint site without deploying any other feature to your site. That’s the common customer request as mentioned in the first line of this blog!

To clarify: SM SharePoint Site Package “Microsoft.EnterpriseManagement.ServiceManager.Portal.SharePointSite.wsp” includes not only SM Webparts but also other features like SM SharePoint SiteTemplate, SM Sharepoint Site Master Page, SM Sharepoint Site CSS, SM Sharepoint site Theme, etc… as a result when you deploy this package to your SharePoint site, all these features will get deployed to your site! Depending on your site requirement, this could cause other issues and you may want to clean up these features from your site.

Thanks

Martha

re: How to Deploy Service Manager Webparts to an Existing SharePoint Site

Anton Gritsenko - FreemanRU — Sun, 29 Jan 2012 11:48:13 GMT

Ouh... this is hard way... Same can be done much easily:

1. Add new property in IIS (step 4 from this post), this can be done via IIS snap-in.

SMPortal_WebContentServer_URL: http://webcontentserver:port/ContentHost/ClientBin/

2. Find the "Microsoft.EnterpriseManagement.ServiceManager.Portal.SharePointSite.wsp" at existing installation and add it to target Sharepoint:

Add-SPSolution "C:\SMPortal\Microsoft.EnterpriseManagement.ServiceManager.Portal.SharePointSite.wsp"

3. Activate solution for site collection (Site Settings -> Site Collection Features)

Step 2 avoid as to manually copy files, adding to GAC and etc.

When do the step 6 from this blog post.