Tuesday, 21 July 2015

System Center 2012 Designs

  • Follow all of the links and thoroughly understand what you will be doing and make all required system changes up front! Documentation is available here.

Microsoft System Center Private Cloud Component Diagram (without Configuration manager)

    6012.System%20Center%20Component%20Diagram

 

System Center 2012 SP1 Integration Map with Configuration manager

clip_image002[17]

System Center 2012 Integration Guide – TechNet

Component Guides

Each of the following sections provides an overview of each System Center component, its different options for automating processes, and the methods for integrating with it from other application and other System Center components.  You can link to each of these sections below.

  • Before getting started with the installation be sure to validate firewall settings are configured as required.  Refer to the firewall configuration section of the documentation for details.  Also, during my install I found the installer would sometimes hang, seemingly without error.  I resolved this problem by increasing the maximmum concurrent policy instances on the Installer system which is running the Orchestrator management server.  Details on how to do that are found here.

Thanks to Steve Rachi’s Blog for providing the information of system Center 2012

image

Friday, 3 July 2015

ERROR in component SMS_MP_CONTROL_MANAGER

Issues :

1) Component: SMS_MP_CONTROL_MANAGER
Message ID: 5436
Description: MP Control Manager detected management point is not responding to HTTP requests. The HTTP status code and text is 500. Internal Server Error.
2214) Component: SMS_MP_CONTROL_MANAGER
Message ID: 5420
Description: SMS management point encountered an error when connecting to the database XXX on SQL Server YYY. The OLEDB error code was 0x80004005.

Resolution :

1.. Run  http://<MP name>/sms_mp/.sms_aut?mplist
  1.. This returns a blank screen.
2.. Run  http://<MP name>/sms_mp/.sms_aut?mpcert
  1.. This returns a long list of numbers and letters.
3.. Verify that the DTS Service is enabled.
4.. Verify that the Task Scheduler is enabled.
5.. Verify that the Windows Management Instrumentation service is running.
6.. Verify that the SMS Agent Host service is running.
7.. Verify that the World Wide Web Publishing Service is running.
8.. Verify that the MP machine account has been added to the
SMS_SiteSystemToSQLConnection_<site_code> group.
9.. Verify that the SQL Server has named pipes enabled.
10.. Update MDAC on the server.
  1.. Review Q820910 for details.
  2.. http://support.microsoft.com/default.aspx?scid=kb;en-us;820910
11.. SQL boxes that are running under a user account, instead of system,
need the SPN updated in AD.
  1.. Review Q829868 for additional details.
  2.. http://support.microsoft.com/default.aspx?scid=kb;en-us;829868
12.. Crossing domain boundaries between MP and SQL may also need the SPN
updated in AD.
  1.. Review Q829868 for additional details.
  2.. http://support.microsoft.com/default.aspx?scid=kb;en-us;829868
13.. IIS Lockdown Tool
  1.. If you are using the IIS lockdown tool on your IIS 5 servers be sure
to apply the SMS server template from the SMS 2003 toolkit.
  2.. http://www.microsoft.com/smserver/downloads/2003/tools/toolkit.asp
14.. Deinstall the MP and IIS, then reinstall IIS and the MP.
  1.. Remove the MP role on the server.
  2.. Disable IIS. Remove completely. Reboot the server.
  3.. Verify that the DTS Service is enabled.
  4.. Verify that the Task Scheduler is enabled.
  5.. Verify that the Windows Management Instrumentation service is
running.
  6.. Enable BITS, enable WEBDEV and install IIS.
  7.. Verify that the World Wide Web Publishing Service is running.
  8.. Verify that the MP machine account has been added to the
SMS_SiteSystemToSQLConnection_<site_code> group.
  9.. Enable MP role on the server.
This will fix most MP errors. I personally would start with step 11. But please check all

 

Thanks to Eric Zhang CHN Source : Link

Wednesday, 1 July 2015

Install/enable .Net 3.5 SP1 on Windows Server 2008 R2

Using PowerShell

  1. Click the Start button in the lower left hand corner of the display.
  2. Highlight All Programs and select Accessories
  3. Expand Windows PowerShell and right click Windows PowerShell and select Run as administrator. Click Yes on the User Account Control box.
  4. At the PowerShell command prompt, type the following commands, and then press ENTER after each command:
    • Import-Module ServerManager
    • Add-WindowsFeature as-net-framework

Note: A screenshot is shown below: