Our System Center Memo

Remove Change Request Link from SCSM Portal

In some environments, the customer only wants the end users to log Incident tickets via Self Service Portal. So how do we remove the Change Request Link from the portal so users won’t click on it? I’ll show you a step by step guide here.

Before we begin, download the new source code here.

Also make sure that your Service Manager and Portal has been installed with Service Pack 1. You will also need to have a machine that has Microsoft Visual Studio installed. I’m using version 2010.

Note!: You do not need to install Visual Studio on the server and do your modifications there, you can do it on any machine.

After downloading the source code you’ll get this folder. SCSM2010SP1PORTALSOURCERELEASE. Next go to SourceCode, then New, you’ll then find a zip file called Unzip this to any location you desire, remember this does not need to be on the server. Next open up the folder that you’ve unzipped, you’ll find 5 folders and a file called Portal.sln. Open this Portal.sln with your Visual Studio and we can begin work.

Note!: Before doing anything, please backup your original portal by copying System Center Service Manager Portal under %systemDrive%\inetpub\wwwroot\ to another place.

Note!: Before going to step 1 below, also do the following.

Go into your SCSM Server, under %systemDrive%\inetpub\wwwroot\System Center Service Manager Portal\EndUser\bin, copy the following files into the common folder under PortalSource-New which you’ve just unzipped.

· Microsoft.EnterpriseManagement.Config.dll

· Microsoft.EnterpriseManagement.UI.Foundation.dll

· Microsoft.EnterpriseManagement.UI.SdkDataAccess.dll

· Microsoft.Mom.BuildConstants.dll

· Microsoft.EnterpriseManagement.DataAccessService.Core.dll

· Microsoft.EnterpriseManagement.ServiceManager.dll

· Microsoft.EnterpriseManagement.ServiceManager.Portal.Common.dll


1. Ok after opening up Portal.sln with Virtual Studio, find the Solutions Explorer panel, for me it’s on the right hand side. You’ll notice under AnalystWebParts, there’s something called References. Expand it. 



2. Look for all the entries that has a yellow exclamation mark. You’ll need to remove them and add it back, every single one of them. Do it 1 by 1. Right click on the first one you see with the exclamation mark, then click Remove.



3. Next right click on References and click Add Reference.



4. Go to the Browse tab, and follow this step by step if you’re unclear or else you’ll not be able to find the files.

4.1 Under Look in:, the default will be AnalystWebparts. Go up 1 level, then browse into Common. This is the folder that you’ve just copied the 7 files too earlier before step 1.


4.2 Under Common, noticed that the file Microsoft.EnterpriseManagement.Core.dll was the file that you removed earlier from the reference? Highlight it and click Ok.



4.3 Notice now that Microsoft.EnterpriseManagement.Core is back, but without the exclamation mark. Repeat this on ALL references that has the exclamation mark. Don’t forget you’ll need to do for references that are under Common, End user portal and WebParts as well.



5. Now after all the references has been updated, in the Solutions Explorer pane, go to WebParts, expand Request and you’ll see CreateRequest.cs, PortalRequest.cs and RequestDetails.cs. What we’re interested here is PortalRequest.cs so go ahead and double click it.



6. After clicking the PortalRequest.cs you’ll see a bunch of codes on the main panel. Look for the code highlighted as below. You can easily find it using CTRL+F and paste this into the search box.

DisplayName = WebPartsResources.NewChangeOrResourceDisplayName




7. Next, add /* in front of RequestsTypes.Add(new RequestType() and then */ after {);

Just follow the screenshot and you wont miss it.



8. Now on top of the Visual Studio, notice the button Build? Click it, and click on Build Solution.



9. See the output log, you should have 0 failed and 0 skipped. If you do, make sure you’ve completely replaced all the references in step 1 to 4.



10. Next go to the PortalSource-New folder again, then End User Portal\bin. Sort by modified date and copy the files that has just been modified, then paste it into %systemDrive%\inetpub\wwwroot\System Center Service Manager Portal\EndUser\bin in the Server. Overwrite all the files.



11. Now launch the end user portal, you’ll notice that under Request Type, only Need help with a problem is left, so users won’t be able to raise a change request from the portal anymore.



April 12, 2011 - Posted by | System Center Service Manager (SCSM)


  1. When I copy the necessary .dll files and open the portal.sln, I dont see the yellow exclamation marks under related reference folders. They look all fine!!

    Am I doing something wrong?

    Comment by Ozge | June 22, 2011 | Reply

    • Hey Ozge,

      Sorry for the late response, was away on a long leave. You should see the yellow exclamation though, did you open the file from PortalSource-New?


      Comment by James | June 29, 2011 | Reply

    • I download the folders onto my personal PC, copy the .dll files from the server into the corresponding folder on my PC and open the portal.sln. No yellow exclamation mark!

      Comment by Ozge | June 30, 2011 | Reply

      • Well, as long as it doesn’t have the yellow exclamation mark you should be fine. If you have, you’ll get a lot of errors when you build the solution. Did you manage to do what you wanted to do?


        Comment by James | July 4, 2011

  2. Hi again,

    Is it possible to remove the Create Request links as well. Because my customer dont want the end users to open ticket via the portal.


    Comment by Ozge Ozkaya | October 3, 2011 | Reply

    • Hi Ozge,

      My apologies, I’ve not been visiting my blog for awhile due to some reasons. I’m back now, do you still require help for this? In short, yes this is doable. I am however a little busy to provide the solution, however if you need it, I will make time to blog about it. (This is also a very rare requirement) Let me know!

      James Yeoh

      Comment by James | October 24, 2011 | Reply

      • Hi James,

        I found the solution. Thanks for getting back to me.


        Comment by atmayoniozge | October 24, 2011

  3. Great post. Worked perfectly!

    Comment by Andrew | November 11, 2011 | Reply

    • Thanks! Glad it helped 🙂

      Comment by James | November 13, 2011 | Reply

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: