SharePoint 2010 and System Center Service Manager (SCSM) 2010
I ran into a challenge recently on making the SCSM web parts work with SharePoint 2010. This document describes how to make it work. A good chunk of this comes from the Deployment Document, but because it does not specifically address SharePoint 2010, the process has been adjusted.
After you have SharePoint 2010 installed, you will need to install the SCSM web portal.
Important : The account you use to run Self-Service Portal Setup must be a member of the Service Manager Administrator user role.
You have to install the Self-Service Portal on the computer hosting SharePoint 2010:
1. You need to install the hotfix from KB975332 first!
2. On the System Center Service Manager 2010 installation media, double-click the Setup.exe file.
3. On the Microsoft System Center Service Manager 2010 page, click Install the Service Manager Web portals.
4. On the Product registration page, type information in the boxes. In the Product key boxes, type the product key you received with Service Manager, or alternatively, select Install as an evaluation edition (180 day trial)?. Read the Microsoft Software License Terms, and, if applicable, click I have read, understood, and agree with the terms of the license agreement, and then click Next.
5. On the Installation location page, verify that sufficient free disk space is available, and then click Next. If necessary, click Browse to change the installation location of the Service Manager management server.
Note: It is recommended that you install the Self-Service Portal in the default location. Installing the Self-Service Portal in another location requires you to change configuration settings in Internet Information Services (IIS).
6. On the System check results page, make sure that the prerequisite check passed or at least passed with warnings, and then click Next.
7. On the Configure the Service Manager self-service portal name and port page, follow these steps:
a. In the Web site name box, accept the default name, or type a new name.
b. In the Port box, type 443.
c. In the SSL certificate list, select the Secure Sockets Layer (SSL) certificate you want to use with the Self-Service Portal, and then click Next.
Note: SSL is a requirement of the Self-Service Portal.
8. On the Select the Service Manager database page, follow these steps:
a. In the Database server box, type the name of the computer that hosts the existing Service Manager database.
b. In the SQL Server instance list, select the instance name for the Service Manager database.
c. In the Database list, select the database that hosts the Service Manager database. (ServiceManager is the default database name.)
d. Click Next.
9. On the Configure account for the Service Manager self-service portal page, click Domain account.
10. Specify the user name, password, and domain for the Service Manager services account that you specified during installation of Service Manager. For example, enter the account information for the SM_Acct domain user.
11. Click Test Credentials. After you verify that you receive a The credentials were accepted message, click Next.
12. On the Help improve System Center Service Manager page, indicate your preference for participation in the Customer Experience Improvement Program and in Error Reporting. Optionally, click Tell me more about the program, and then click Next.
13. On the Use Microsoft Update to help keep your computer secure and up-to-date page, indicate your preference for using Microsoft Update to check for Service Manager updates, and then click Next.
14. On the Installation summary page, click Install.
15. On the Setup completed successfully page, click Close.
16. On the Setup completed successfully page, it is recommended that you leave Open the Encryption Backup or Restore Wizard selected, and then click Close.
You have to convert the Windows SharePoint Services 3.0 wsp file to SharePoint 2010:
1. Download the file ServiceManager.EnduserWebparts.wsp (http://blogs.technet.com/cfs-file.ashx/__key/CommunityServer-Components-PostAttachments/00-03-32-83-96/ServiceManager.EnduserWebparts.wsp) to your developer computer.
2. On the Windows desktop, click Start, point to Programs, move over Visual Studio 2010, Open Visual Studio 2010 (you can download the trial if you don't currently have it).
3. On the left panel click New Project.
4. Under Installed Templates expand SharePoint and click 2010.
5. In the middle pane, select Import SharePoint Solution Package make the name ServiceManager.EnduserWebparts and use the default location. Click OK.
6. Choose your local site to debug and choose between sandboxed and farm solution. Click Next.
7. Browse to where you saved the wsp download in step 1. Click Next.
8. Make sure all items import and click Finish.
9. After the project imports, From the menu select Build, then Package. Assuming you use the default settings, your package should be located at c:\users\%username%\documents\visual studio 2010\Projects\ServiceManager.EnduserWebparts\ServiceManager.EnduserWebparts\bin\Release\ServiceManager.EnduserWebpart.wsp
10. Copy the wsp file to the SharePoint server.
You have to add the solution Package to the SharePoint Site Collection:
1. Save your converted web part to the c:\wsp folder on your SharePoint server. If the folder doesn't exist, create it...it will reduce your typing.
2. Open a command prompt and change directories to c:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\bin.
3. Type the command stsadm -o addsolution –filename c:\wsp\ServiceManager.EnduserWebparts.wsp.
4. When Operation completed successfully is displayed, type exit to close the command window.
5. On the Windows desktop, click Start, point to Programs, point to Microsoft SharePoint 2010 Products, and then click SharePoint 2010 Central Administration.
6. In the Central Administration pane, click System Settings.
7. In the Systems Settings pane, in the Farm Management area, click Manage Farm Solutions.
8. Observe that servicemanager.enduserwebparts.wsp is listed. Click servicemanager.enduserwebparts.wsp.
9. In the Solution Properties pane, click Deploy Solution and then click OK. This will deploy the solution globally.
Edit the Web.Config file
1. Using an XML editor, open the file \inetpub\wwwroot\wss\VirtualDirectories\\web.config where is the port number used by SharePoint 2010. You will need admin acces to perform the next step so open as administrator.
Note: Make sure that you are editing the web.config file of the correct site where you are planning to deploy Self-Service Portal.
2. Locate the following line and delete it. There is only one occurrence of this line. When deleted, close your editor and save the web.config file.
Configure IIS
These procedures are performed in the Internet Information Services Manager.
To set application pool identity
1. On the Windows desktop, click Start, point to Programs, point to Administrative Tools, and then click Internet Information Services (IIS) Manager.
2. In the Connection pane, expand the computer name, expand Sites, and then click the site for your SharePoint installation.
3. In the Actions pane, click Advanced Settings.
4. In the Advanced Settings dialog box, in the General area, note the setting for Application Pool, and then click Cancel.
5. In the Connections pane, expand the computer name, and then click Application Pools.
6. In the Application Pools pane, click the application pool you identified in step 4.
7. In the Actions pane, click Advanced Settings.
8. In the Advanced Settings dialog box, in the Process Model area, click Identity, and then click the ellipsis button (…).
9. In the Application Pool Identity dialog box, click Custom account, and then click Set.
10. In the Set Credentials dialog box, type the username and password for the credentials you provided for the Service Manager Services account, and then click OK three times.
To set Windows Authentication and Session State profile
1. In the Connections pane, expand the computer name, expand Sites, and then click the site for your SharePoint installation.
2. In the center pane, under IIS, double-click Authentication.
3. In the Authentication page, make sure that Windows Authentication is set to Enabled and that all other settings are set to Disabled.
4. In the Connections pane, click the site for your SharePoint installation.
5. In the center pane, in the ASP.NET area, double-click Session State.
6. In the Cookie Settings area, in the Mode list, click Use Device Profile.
7. In the Actions pane, select Apply.
8. Close Internet Information Services (IIS) Manager.
Configure the Site Collection
The following procedure must be performed on the SharePoint Web site that you will use for your Self-Service Portal. Make sure that you are not working with the SharePoint 2010 Central Administration page.
1. On the Web site where you want to deploy the web parts, in the upper left part of the page, click Site Actions, and then click Site Settings.
2. In the Site Collection Administration area, click Site collection features.
3. For the entry titled Service Manager Web Parts, click Activate. The web parts should show in the list of web parts under the miscellaneous section.
Adding Application Settings
I suggest creating SharePoint pages for the corresponding web part taking note of the URL (in non-design mode). For example, create a web part page called RequestDetails.aspx in SharePoint for request details and add a RequestDetails web part to it from the SharePoint web part gallery. Then exit the design mode of this page and note the URL– http://webserver:portnumber/RequestDetailspage.aspx. Set this URL as the value of RequestDetailsPage application settings.
To configure application settings
1. On the Windows desktop, click Start, point to Programs, point to Administrative Tools, and then click Internet Information Services (IIS) Manager.
2. In the Connections pane, expand the computer name, expand Sites, and then click the site for your SharePoint installation.
3. In the center pane, under ASP.NET, double-click Application Settings.
4. In the Actions pane, click Add.
5. In the Add Application Setting dialog box, perform the following:
a. In the Name box, type SM_ConnectionTimeout
b. In the Value box, type a number representing the number of seconds. For example, type 60, and then click OK.
6. Repeat steps 4 and 5 for the name-value pairs in the following fields. For the Default404ErrorPage, you will need to create a default error page and enter the name of your page for the value. For example, create a default error page named Default404.aspx and type a value of ~/Default404.aspx.
Name, [Value]
• Default404ErrorPage, [Default error page]
• DisplayClosedRequestsForDays, [Number of days]
• DefaultMaximumFileAttachments, [Number of attachments]
• HomePage, [Home page of SharePoint site]
• NumberOfTopAnnouncements, [Number of announcements]
To configure end user portal application settings
1. For each of the settings you first need to create the pages in SharePoint with the corresponding web part, and then make a note of this URL (in non-design mode). For example, to create a request page, start by creating a web part page called CreateRequestPage.aspx in SharePoint, and then add a CreateRequest web part to it from the SharePoint web part gallery. Exit the design mode of this page and note the URL, for example, http://webserver:portnumber/CreateRequestPage.aspx Set this URL as the value of the CreateRequestPage application setting.
Name, [Value]
• CreateRequestPage, [Page_Address]
• KnowledgeArticleDetailsPage, [Page_Address]
• MaximumKnowledgeArticles, [Page_Address]
• RequestDetailsPage, [Page_Address]
• RequestDetailsPage, [Page_Address]
• ViewAllAnnouncementsPage, [Page_Address]
• ViewAllKnowledgeArticlesPage, [Page_Address]
• ViewAllRequestsPage, [Page_Address]
To configure analyst portal application settings
1. For each of the settings you first need to create the pages in SharePoint with the corresponding web part, and then make a note of this URL (in non-design mode). For example, to create a page for viewing the change requests that have been submitted, start by creating a web part page called ChangeRequestSubmittedPage.aspx in SharePoint, and then add a ChangeRequestSubmitted web part to it from the SharePoint web part gallery. Exit the design mode of this page and note the URL, for example, http://webserver:portnumber/ChangeRequestSubmittedPage.aspx Set this URL as the value of the ChangeRequestSubmittedPage application setting
Name, [Value]
• ChangeRequestsSubmittedPage, [Page_Address]
• ChangeRequestsAssignedToMePage, [Page_Address]
• ChangeRequestsINeedToManualPage, [Page_Address]
• ChangeRequestsINeedToReviewPage, [Page_Address]
• ManualActivityDetailsPage, [Page_Address]
• ReviewActivityDetailsPage, [Page_Address]
• ChangeRequestDetailsPage, [Page_Address]
• ManualActivitiesPage, [Page_Address]
• ReviewActivitiesPage, [Page_Address
Create Request Page Workaround
The create request web part errors out when trying to move to the summary page using the web part. The create Request SharePoint page works so these steps are the work-around for the error.
There are two pages that need to be edited to give the proper look and feel:
• /EndUser/CreateRequest.aspx
• /EndUser/MasterPages/ServiceManagerPortal.aspx
/EndUser/CreateRequest.aspx
Browse to %root\inetpub\wwwroot\System Center Service Manager Portal\EndUser\. Make a copy of the CreateRequest.aspx file as CreateRequestOld.aspx.
Using an XML editor, open the file CreateRequest.aspx
Replace all of the text with the following:
Save the file as CreateRequest.aspx.
EndUser/MasterPages/ServiceManagerPortal.aspx
Browse to %root\inetpub\wwwroot\System Center Service Manager Portal\EndUser\MasterPages\. Make a copy of the ServiceManagerPortal.aspx file as ServiceManagerPortalOld.aspx.
Using an XML editor, open the file ServiceManagerPortal.aspx
To make this easier, replace the text in the file with the following:
Save the file as ServiceManagerPortal.aspx
Add the Page to SharePoint
On the SitePage Create Request (made in the End User Portal Applications section of this document) select Site Action>Edit page. Select the Insert Tab on the editing tools and click Web Part.
In the categories window, choose Media and Content.
In the Web Parts select Page Viewer and Click Add. The page viewer Web part will appear.
Select the open the tool pane link.
In the Page View Link section put in the URL for the Service Manager Portal Create Ticket page. The Default for this should be https://servername/EndUser/CreateRequest.aspx
Under the Appearance section increase the height to a fixed height of 720 pixels. Also, change Chrome Type to None.
Click OK.
Remove Recent Changes menu from Site Pages
Open a command line with Administrative rights
Change Directory to %Drive%\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\Document Templates\
Type notepad.exe wkpstd.aspx and hit enter
Find SharePoint:RecentChangesMenu control and add visible=”false” to the line. This will hide the Recent Change menu.
Save and close.
Workaround for required web application pool Service account
Log into the SharePoint server with administrative rights.
Open Internet Information Services Manager
Expand the server under the connections pane and then expand sites.
Select the site associated site you need to perform the workaround.
Choose Basic Settings from the Actions pane and note the Application Pool.
Click cancel and select Application Pools from the connections pane.
Select the Application Pool you just noted and choose Advanced Settings from the Action pane.
Under the Process Model section, note the identity account.
Log into the SQL server with administrative rights.
Open the SQL Server Management Studio
The following databases need to have User account for the account stated above created. Note: DEV\%SP_Service_Account% is the account used to set up the SharePoint environment originally.
Log into the SharePoint front in using a Site Collection Administrator account.
Select Site Actions> Site Settings.
Under the Users and Permissions section select Site collection administrators
Add the name of the application service account used by the web application and Click OK.
Addendum:
Since the release of SP1, The create page web part and my recent requests web part no longer work. I am checking into a solution.
After you have SharePoint 2010 installed, you will need to install the SCSM web portal.
Important : The account you use to run Self-Service Portal Setup must be a member of the Service Manager Administrator user role.
You have to install the Self-Service Portal on the computer hosting SharePoint 2010:
1. You need to install the hotfix from KB975332 first!
2. On the System Center Service Manager 2010 installation media, double-click the Setup.exe file.
3. On the Microsoft System Center Service Manager 2010 page, click Install the Service Manager Web portals.
4. On the Product registration page, type information in the boxes. In the Product key boxes, type the product key you received with Service Manager, or alternatively, select Install as an evaluation edition (180 day trial)?. Read the Microsoft Software License Terms, and, if applicable, click I have read, understood, and agree with the terms of the license agreement, and then click Next.
5. On the Installation location page, verify that sufficient free disk space is available, and then click Next. If necessary, click Browse to change the installation location of the Service Manager management server.
Note: It is recommended that you install the Self-Service Portal in the default location. Installing the Self-Service Portal in another location requires you to change configuration settings in Internet Information Services (IIS).
6. On the System check results page, make sure that the prerequisite check passed or at least passed with warnings, and then click Next.
7. On the Configure the Service Manager self-service portal name and port page, follow these steps:
a. In the Web site name box, accept the default name, or type a new name.
b. In the Port box, type 443.
c. In the SSL certificate list, select the Secure Sockets Layer (SSL) certificate you want to use with the Self-Service Portal, and then click Next.
Note: SSL is a requirement of the Self-Service Portal.
8. On the Select the Service Manager database page, follow these steps:
a. In the Database server box, type the name of the computer that hosts the existing Service Manager database.
b. In the SQL Server instance list, select the instance name for the Service Manager database.
c. In the Database list, select the database that hosts the Service Manager database. (ServiceManager is the default database name.)
d. Click Next.
9. On the Configure account for the Service Manager self-service portal page, click Domain account.
10. Specify the user name, password, and domain for the Service Manager services account that you specified during installation of Service Manager. For example, enter the account information for the SM_Acct domain user.
11. Click Test Credentials. After you verify that you receive a The credentials were accepted message, click Next.
12. On the Help improve System Center Service Manager page, indicate your preference for participation in the Customer Experience Improvement Program and in Error Reporting. Optionally, click Tell me more about the program, and then click Next.
13. On the Use Microsoft Update to help keep your computer secure and up-to-date page, indicate your preference for using Microsoft Update to check for Service Manager updates, and then click Next.
14. On the Installation summary page, click Install.
15. On the Setup completed successfully page, click Close.
16. On the Setup completed successfully page, it is recommended that you leave Open the Encryption Backup or Restore Wizard selected, and then click Close.
You have to convert the Windows SharePoint Services 3.0 wsp file to SharePoint 2010:
1. Download the file ServiceManager.EnduserWebparts.wsp (http://blogs.technet.com/cfs-file.ashx/__key/CommunityServer-Components-PostAttachments/00-03-32-83-96/ServiceManager.EnduserWebparts.wsp) to your developer computer.
2. On the Windows desktop, click Start, point to Programs, move over Visual Studio 2010, Open Visual Studio 2010 (you can download the trial if you don't currently have it).
3. On the left panel click New Project.
4. Under Installed Templates expand SharePoint and click 2010.
5. In the middle pane, select Import SharePoint Solution Package make the name ServiceManager.EnduserWebparts and use the default location. Click OK.
6. Choose your local site to debug and choose between sandboxed and farm solution. Click Next.
7. Browse to where you saved the wsp download in step 1. Click Next.
8. Make sure all items import and click Finish.
9. After the project imports, From the menu select Build, then Package. Assuming you use the default settings, your package should be located at c:\users\%username%\documents\visual studio 2010\Projects\ServiceManager.EnduserWebparts\ServiceManager.EnduserWebparts\bin\Release\ServiceManager.EnduserWebpart.wsp
10. Copy the wsp file to the SharePoint server.
You have to add the solution Package to the SharePoint Site Collection:
1. Save your converted web part to the c:\wsp folder on your SharePoint server. If the folder doesn't exist, create it...it will reduce your typing.
2. Open a command prompt and change directories to c:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\bin.
3. Type the command stsadm -o addsolution –filename c:\wsp\ServiceManager.EnduserWebparts.wsp.
4. When Operation completed successfully is displayed, type exit to close the command window.
5. On the Windows desktop, click Start, point to Programs, point to Microsoft SharePoint 2010 Products, and then click SharePoint 2010 Central Administration.
6. In the Central Administration pane, click System Settings.
7. In the Systems Settings pane, in the Farm Management area, click Manage Farm Solutions.
8. Observe that servicemanager.enduserwebparts.wsp is listed. Click servicemanager.enduserwebparts.wsp.
9. In the Solution Properties pane, click Deploy Solution and then click OK. This will deploy the solution globally.
Edit the Web.Config file
1. Using an XML editor, open the file \inetpub\wwwroot\wss\VirtualDirectories\
Note: Make sure that you are editing the web.config file of the correct site where you are planning to deploy Self-Service Portal.
2. Locate the following line and delete it. There is only one occurrence of this line. When deleted, close your editor and save the web.config file.
Configure IIS
These procedures are performed in the Internet Information Services Manager.
To set application pool identity
1. On the Windows desktop, click Start, point to Programs, point to Administrative Tools, and then click Internet Information Services (IIS) Manager.
2. In the Connection pane, expand the computer name, expand Sites, and then click the site for your SharePoint installation.
3. In the Actions pane, click Advanced Settings.
4. In the Advanced Settings dialog box, in the General area, note the setting for Application Pool, and then click Cancel.
5. In the Connections pane, expand the computer name, and then click Application Pools.
6. In the Application Pools pane, click the application pool you identified in step 4.
7. In the Actions pane, click Advanced Settings.
8. In the Advanced Settings dialog box, in the Process Model area, click Identity, and then click the ellipsis button (…).
9. In the Application Pool Identity dialog box, click Custom account, and then click Set.
10. In the Set Credentials dialog box, type the username and password for the credentials you provided for the Service Manager Services account, and then click OK three times.
To set Windows Authentication and Session State profile
1. In the Connections pane, expand the computer name, expand Sites, and then click the site for your SharePoint installation.
2. In the center pane, under IIS, double-click Authentication.
3. In the Authentication page, make sure that Windows Authentication is set to Enabled and that all other settings are set to Disabled.
4. In the Connections pane, click the site for your SharePoint installation.
5. In the center pane, in the ASP.NET area, double-click Session State.
6. In the Cookie Settings area, in the Mode list, click Use Device Profile.
7. In the Actions pane, select Apply.
8. Close Internet Information Services (IIS) Manager.
Configure the Site Collection
The following procedure must be performed on the SharePoint Web site that you will use for your Self-Service Portal. Make sure that you are not working with the SharePoint 2010 Central Administration page.
1. On the Web site where you want to deploy the web parts, in the upper left part of the page, click Site Actions, and then click Site Settings.
2. In the Site Collection Administration area, click Site collection features.
3. For the entry titled Service Manager Web Parts, click Activate. The web parts should show in the list of web parts under the miscellaneous section.
Adding Application Settings
I suggest creating SharePoint pages for the corresponding web part taking note of the URL (in non-design mode). For example, create a web part page called RequestDetails.aspx in SharePoint for request details and add a RequestDetails web part to it from the SharePoint web part gallery. Then exit the design mode of this page and note the URL– http://webserver:portnumber/RequestDetailspage.aspx. Set this URL as the value of RequestDetailsPage application settings.
To configure application settings
1. On the Windows desktop, click Start, point to Programs, point to Administrative Tools, and then click Internet Information Services (IIS) Manager.
2. In the Connections pane, expand the computer name, expand Sites, and then click the site for your SharePoint installation.
3. In the center pane, under ASP.NET, double-click Application Settings.
4. In the Actions pane, click Add.
5. In the Add Application Setting dialog box, perform the following:
a. In the Name box, type SM_ConnectionTimeout
b. In the Value box, type a number representing the number of seconds. For example, type 60, and then click OK.
6. Repeat steps 4 and 5 for the name-value pairs in the following fields. For the Default404ErrorPage, you will need to create a default error page and enter the name of your page for the value. For example, create a default error page named Default404.aspx and type a value of ~/Default404.aspx.
Name, [Value]
• Default404ErrorPage, [Default error page]
• DisplayClosedRequestsForDays, [Number of days]
• DefaultMaximumFileAttachments, [Number of attachments]
• HomePage, [Home page of SharePoint site]
• NumberOfTopAnnouncements, [Number of announcements]
To configure end user portal application settings
1. For each of the settings you first need to create the pages in SharePoint with the corresponding web part, and then make a note of this URL (in non-design mode). For example, to create a request page, start by creating a web part page called CreateRequestPage.aspx in SharePoint, and then add a CreateRequest web part to it from the SharePoint web part gallery. Exit the design mode of this page and note the URL, for example, http://webserver:portnumber/CreateRequestPage.aspx Set this URL as the value of the CreateRequestPage application setting.
Name, [Value]
• CreateRequestPage, [Page_Address]
• KnowledgeArticleDetailsPage, [Page_Address]
• MaximumKnowledgeArticles, [Page_Address]
• RequestDetailsPage, [Page_Address]
• RequestDetailsPage, [Page_Address]
• ViewAllAnnouncementsPage, [Page_Address]
• ViewAllKnowledgeArticlesPage, [Page_Address]
• ViewAllRequestsPage, [Page_Address]
To configure analyst portal application settings
1. For each of the settings you first need to create the pages in SharePoint with the corresponding web part, and then make a note of this URL (in non-design mode). For example, to create a page for viewing the change requests that have been submitted, start by creating a web part page called ChangeRequestSubmittedPage.aspx in SharePoint, and then add a ChangeRequestSubmitted web part to it from the SharePoint web part gallery. Exit the design mode of this page and note the URL, for example, http://webserver:portnumber/ChangeRequestSubmittedPage.aspx Set this URL as the value of the ChangeRequestSubmittedPage application setting
Name, [Value]
• ChangeRequestsSubmittedPage, [Page_Address]
• ChangeRequestsAssignedToMePage, [Page_Address]
• ChangeRequestsINeedToManualPage, [Page_Address]
• ChangeRequestsINeedToReviewPage, [Page_Address]
• ManualActivityDetailsPage, [Page_Address]
• ReviewActivityDetailsPage, [Page_Address]
• ChangeRequestDetailsPage, [Page_Address]
• ManualActivitiesPage, [Page_Address]
• ReviewActivitiesPage, [Page_Address
Create Request Page Workaround
The create request web part errors out when trying to move to the summary page using the web part. The create Request SharePoint page works so these steps are the work-around for the error.
There are two pages that need to be edited to give the proper look and feel:
• /EndUser/CreateRequest.aspx
• /EndUser/MasterPages/ServiceManagerPortal.aspx
/EndUser/CreateRequest.aspx
Browse to %root\inetpub\wwwroot\System Center Service Manager Portal\EndUser\. Make a copy of the CreateRequest.aspx file as CreateRequestOld.aspx.
Using an XML editor, open the file CreateRequest.aspx
Replace all of the text with the following:
Save the file as CreateRequest.aspx.
EndUser/MasterPages/ServiceManagerPortal.aspx
Browse to %root\inetpub\wwwroot\System Center Service Manager Portal\EndUser\MasterPages\. Make a copy of the ServiceManagerPortal.aspx file as ServiceManagerPortalOld.aspx.
Using an XML editor, open the file ServiceManagerPortal.aspx
To make this easier, replace the text in the file with the following:
Save the file as ServiceManagerPortal.aspx
Add the Page to SharePoint
On the SitePage Create Request (made in the End User Portal Applications section of this document) select Site Action>Edit page. Select the Insert Tab on the editing tools and click Web Part.
In the categories window, choose Media and Content.
In the Web Parts select Page Viewer and Click Add. The page viewer Web part will appear.
Select the open the tool pane link.
In the Page View Link section put in the URL for the Service Manager Portal Create Ticket page. The Default for this should be https://servername/EndUser/CreateRequest.aspx
Under the Appearance section increase the height to a fixed height of 720 pixels. Also, change Chrome Type to None.
Click OK.
Remove Recent Changes menu from Site Pages
Open a command line with Administrative rights
Change Directory to %Drive%\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\Document Templates\
Type notepad.exe wkpstd.aspx and hit enter
Find SharePoint:RecentChangesMenu control and add visible=”false” to the line. This will hide the Recent Change menu.
Save and close.
Workaround for required web application pool Service account
Log into the SharePoint server with administrative rights.
Open Internet Information Services Manager
Expand the server under the connections pane and then expand sites.
Select the site associated site you need to perform the workaround.
Choose Basic Settings from the Actions pane and note the Application Pool.
Click cancel and select Application Pools from the connections pane.
Select the Application Pool you just noted and choose Advanced Settings from the Action pane.
Under the Process Model section, note the identity account.
Log into the SQL server with administrative rights.
Open the SQL Server Management Studio
The following databases need to have User account for the account stated above created. Note: DEV\%SP_Service_Account% is the account used to set up the SharePoint environment originally.
Log into the SharePoint front in using a Site Collection Administrator account.
Select Site Actions> Site Settings.
Under the Users and Permissions section select Site collection administrators
Add the name of the application service account used by the web application and Click OK.
Addendum:
Since the release of SP1, The create page web part and my recent requests web part no longer work. I am checking into a solution.
Comments
Thank you for putting this guide together, When I try to add in the webpart I get this message:
"Cannot import this Webpart. Contact SM Support for help."
I noticed you posted on another forum you were running into this same error message, do you know what causes this?
Regards,
David
Thanks!
CB
Unfortunately, I just moved halfway across the country and I haven't had a chance to rebuild my lab. As soon as I have my lab back, i will be glad to post a link to download the 2010 wsp file.
John