Showing posts with label upgrade. Show all posts
Showing posts with label upgrade. Show all posts

Tuesday, 17 January 2017

Upgrade SQL Server on Red Hat Enterprise Linux Step by Step Totorial

Upgrade SQL Server on Red Hat Enterprise Linux Step by Step Totorial


  • In order to upgrade the mssql-server package, execute the following command:

sudo yum update mssql-server


  • These commands will download the newest package and replace the binaries located under /opt/mssql/. The user generated databases and system databases will not be affected by this operation.

Wednesday, 19 October 2016

SCOM 2016 UR1 Step by Step Upgrade Tutorial

SCOM 2016 UR1 Step by Step Upgrade Tutorial


  • Ok the long wait for SCOM 2016 is over we have SCOM 2016 Generally available now in RTM version.
  • Now Microsoft has fixed the bugs and release UR1
  • You can Download the Update from below Link
  • http://catalog.update.microsoft.com/v7/site/Search.aspx?q=3190029
  • It recommended that you install UR1 even if you are going to install new SCOM 2016 enviornment, but  do not install this update rollup package immediately after you install the System Center 2016 Operations Manager server. Otherwise, the Health Service state may not be initialized.
  • It has 3 Updates ,One for SCOM Server,SCOM Console and SCOM Web Console.

Step1: Install Update on Management Server


  • Extract the Files that you downloaded to C:\Bin\UR1 folder
  • Login using the SCOM service account or account which has local admin,SCOM admin and SA Admin on SCOM database.Usually your SCOM service account will have these acc. So i suggest to use it.
  • Now Open Command Prompt in elevated mode and Go to "C:\Bin\UR1" folder
  • Type "KB3190029-AMD64-Server.msp"
  • This will lauch Update.You will be prompted to restart your system after the update.Click yes and system will restart
  • Once its up check the Application log for Event ID 1036. Make sure it successful.
  • Also check the DLL Versions in the Operations Manager\Server folder and make sure its showing 7.2.11759.0
  • You Should upgrade your additional management server in same way.

Step2:Upgrade SCOM Webconsole and SCOM Console:


  • Now Open Command Prompt in elevated mode and Go to "C:\Bin\UR1" folder
  • Type "KB3190029-AMD64-ENU-WebConsole.msp"
  • This will update the Web console.
  • Next Type "KB3190029-AMD64-ENU-Console.msp"
  • This will update the Console.

Step3: Updating the Gateway Servers:

  • There is no update for Gateway Server in UR1.

Step4:Update the SCOM Databases:


  • First Make sure you have stopped all SCOM services on your Management server and restart the SQL Server service once
  • Now go to the upgrade Management server at below location %SystemDrive%\Program Files\System Center 2016\Operations Manager\Server\SQL Script for Update Rollups
  • Login to the SCOM DW Database Server
  • Now open a SQL management studio query window, connect it to your OperationsManagerDW database.
  • Copy the SQL Scripts "UR_Datawarehouse.sql" and execute in the Query windows. This script could fail but continue trying till it succeeds.

Step5:Manually Import the management packs:

  • The path for these is on your management server, after you have installed the “Server” update: \Program Files\Microsoft System Center 2012 R2\Operations Manager\Server\Management Packs for Update Rollups
  • Below are the important Mp's
  • Microsoft.SystemCenter.Advisor.Internal.mpb
  • Microsoft.SystemCenter.OperationsManager.Library.mp
  • Microsoft.SystemCenter.Image.Library.mp
  • Microsoft.SystemCenter.Visualization.Library.mpb
  • Microsoft.SystemCenter.Advisor.mpb
  • Microsoft.SystemCenter.AlertAttachment.mpb
  • Microsoft.SystemCenter.IntelliTraceProfiling.mpb
  • Microsoft.SystemCenter.2007.mp

Step6::Apply the nano agent update to manually installed agents, or push the installation from the Pending view in the Operations console.


  • As you are aware SCOM 2016 supports Nano Servers monitoring.
  • You have install the updates manually by copying the updates to the server and install the updates.
  • For rest of agents login to SCOM Management server
  • Open SCOM Console==>Administration Tab
  • Click on "Pending Management".Select all the agent you see and Click "Approve".
Voila You are now in SOCM 2016 UR1 enjoy :)

Saturday, 10 September 2016

Run Pre Scan to Avoid Windows 10 Upgrade Failures with SCCM 2012 R2

Avoid Windows 10 Upgrade Failures with SCCM 2012 R2

  • Windows 10 Upgrade is the most done work by SCCM today.
  • All most all organizations wants to upgrade from Window 7 to Windows 10.
  • But there comes the challenge the amount of failures with inplace upgrade is huge.
  • This is because of various reason.
  • One thing that all SCCM admin who are planning to upgrade should do is to run a Compatibility Check before doing the actual upgrade
  • What it does is SCAN the PC which is going to be upgraded and check for any conflicts or failures that are predicted during the upgrade.
  • This test helps you identify the failures before the upgrade and can avoid customer frustration.
  • The Command to Run this test is
SETUP.EXE /Auto Upgrade /Quiet /NoReboot /DynamicUpdate Disable /Compat ScanOnly

  • Happy upgrading

Windows 10 Upgrade Failed with Error code 0x80200056 while deploying from SCCM 2012 R2

Windows 10 Upgrade Failed with Error code 0x80200056 while deploying from SCCM 2012 R2


  • Windows 10 Upgrade Pushed from SCCM can fail because of various reasons.
  • You need to read the error code and understand it to further troubleshoot.
  • One of the frequest errors i see while upgrade is Error code "0x80200056"
  • This error means that there was some interuption while u upgrade the OS.
  • Reason couble be user has switched off the Laptop,Or it got restarted because of some power issues, or Network got disconnected.
  • To fix this instruct the user not to turn off or disconnect the PC from network till the upgrade is compelete.This should resolve the issue

Windows 10 Upgrade failed with error 0x80073712 while deploying from SCCM 2012 R2

Windows 10 Upgrade failed with error 0x80073712 while deploying from SCCM 2012 R2


  • Windows 10 Upgrade is giving lot of issues.
  • There are also lot of complains. One error i see while Deployement fails is with error code "0x80073712"
  • This error indicates that there is issue with the file which is needed is damaged or missing.
  • Mostly your ISO that you created is missing some files or is damaged.
  • So make a fresh copy of ISO from Install media and try again
  • This time it succeded without any errors.

Wednesday, 7 September 2016

SCOM 2012 R2 UR11 upgrade step by step


SCOM 2012 R2 UR11 upgrade step by step


  • Microsoft released Update(update Roleup) every now and then. They generally do lot of bug fixes in these update.Today Microsoft has released SCOM UR11 Upgrade. Lets go Step by Step in this upgrade.
  • First Download the UR11 from below Site.


http://catalog.update.microsoft.com/v7/site/Search.aspx?q=3183990



Step1: Upgrading the Management Server:


  • Extract the Files that you downloaded to C:\Bin\UR11 folder.
  • Login using the SCOM service account or account which has local admin,SCOM admin and SA Admin on SCOM database.Usually your SCOM service account will have these acc. So i suggest to use it.

  • Now Open Command Prompt in elevated mode and Go to "C:\Bin\UR11" folder
  • Type "KB3183990-AMD64-Server.msp"
  • This will launch Update.You will be prompted to restart your system after the update.Click yes and system will restart
  • Once its up check the Application log for Event ID 1036. Make sure it successful.
  • Also make sure File Version are 7.1.10226.1239 in your Management Server.
  • You Should upgrade your additional management server in same way before proceeding to next step.
Step2:Upgrade SCOM Webconsole and SCOM Console:

  • Now Open Command Prompt in elevated mode and Go to "C:\Bin\UR11" folder
  • Type "KB3183990-AMD64-ENU-WebConsole.msp"
  • This will update the Web console.
  • Next Type "KB3183990-AMD64-ENU-Console.msp"
  •  This will update the Console.
Step3:Updating the Gateway Servers:

  • Login to your Gateway server. Copy the Downloaded file  TO "C:\Bin\UR11" Folder
  • Now Open Command Prompt in elevated mode and Go to "C:\Bin\UR11" folder
  • Type "KB3183990-AMD64-Gateway.msp"
  • This will update the Gateway Server
Step4:Update the SCOM Databases:

  • First Make sure you have stopped all SCOM services on your Management server and restart the SQL Server service once
  • Login to the SCOM Database Server
  • Open a SQL management studio query window, connect it to your Operations Manager database.
  • Now go to the upgrade Management server at below location %SystemDrive%\Program Files\Microsoft System Center 2012 R2\Operations Manager\Server\SQL Script for Update Rollups
  • Copy the SQL Scripts "update_rollup_mom_db.sql" and execute in the Query windows. This script could faill but continue trying till it succeeds
  • Try re-running the script several times until it completes without errors.  In a production environment, you have to shut down the services (sdk, config, and healthservice) on your management servers, to break their connection to the databases, to get a successful run. 
  • Once OperationsManager DB is update close the Query window.
  • Now open a SQL management studio query window, connect it to your OperationsManagerDW database.
  • Copy the SQL Scripts "UR_Datawarehouse.sql" and execute in the Query windows. This script could fail but continue trying till it succeeds.
Note: Dont Proceed to Next step till it succeeds

Step5:Import the management packs:
  • The path for these is on your management server, after you have installed the “Server” update: \Program Files\Microsoft System Center 2012 R2\Operations Manager\Server\Management Packs for Update Rollups
  • You can install the MP.
Step5:Updating the Agents:

  • Login to SCOM Management server
  • Open SCOM Console==>Administration Tab
  • Click on "Pending Management".Select all the agent you see and Click "Approve".

SCCM 1608 Technical Preview released

SCCM 1608 Technical Preview released


You can Download it here



Some Key Features added are


Software Center Changes – There has been some great improvements in Software Center. When an user requests for an application, the application request history can be now seen in Application Details view in Software Center. If the user clicks on request button, it would not redirect to the Application Catalog.

Asset Intelligence Changes– In this preview, you can find a new field added to the properties for inventoried software. This will lets you set a parent and child relationship with other software. You can now view the parent of any software and also hide all child software. Once you define parent to child relationships, you can filter your view to only show software that is a parent or that has no defined relationship.

Remote Control Keyboard Translation Issues Resolved – When an admin takes a remote control of user’s computer, there would be problem if the keyboard configurations were different at each end. This issue has been resolved now. What ever key the viewer types in, the same key arrives at sharer end.

Changes in Prepare ConfigMgr Client for Capture task sequence step – starting with this preview, instead of removing key information, the configuration manager client will be removed. So when you deploy a captured OS, the configuration manager client is installed freshly.

Thursday, 7 July 2016

Dell Client Management Pack Version 5.1 for SCOM 2012 R2

Dell Client Management Pack Version 5.1 for SCOM 2012 R2




The Client Management Pack enables the following operations to manage Dell client systems:


  • Discover and monitor Dell Latitude, Dell Precision, and Dell OptipPlex computers running supported OMCI and client Windows operating systems.
  • Group Dell Clients without instrumentation and client systems running without OMCI service under the Dell UnManaged Clients group.NOTE: Dell Vostro systems are displayed under the Dell UnManaged Clients group.
  • Monitor the health status for client hardware components by polling at periodic intervals, and update the state of each component in the diagram view. A health status is a standardized description of the functional performance of a component, system, or service. For more information, see Tasks
  • Perform client shutdown and reboot tasks.
  • Launch remote desktop for Dell client systems.
  • Generate reports on Dell Windows


Thursday, 2 June 2016

SCCM Interview Questions

SCCM Interview Questions


Does the Configuration Manager console support a 64-bit operation system?
Yes. The Configuration Manager console is a 32-bit program that can run on a 32-bit version of Windows and on a 64-bit version of Windows.

Are there new Active Directory schema extensions for System Center 2012 Configuration Manager?
No. The Active Directory schema extensions for System Center 2012 Configuration Manager are unchanged from those used by Configuration Manager 2007. If you extended the schema for Configuration Manager 2007, you do not need to extend the schema again for System Center 2012 Configuration Manager.

Have the site types changed from Configuration Manager 2007?
System Center 2012 Configuration Manager introduces changes to both primary and secondary sites while the central administration site is new site type. The central administration site replaces the primary site referred to as a central site as the top-level site of a multi-primary site hierarchy. This site does not directly manage clients but does coordinate a shared database across your hierarchy, and it is designed to provide centralized reporting and configurations for your entire hierarchy.
Can I join a pre-existing site to another site in System Center 2012 Configuration Manager?
No. In System Center 2012 Configuration Manager you cannot change the parent relationship of an active site. You can only add a site as a child of another site at the time you install the new site. Because the database is shared between all sites, joining a site that has already created default objects or that has custom configurations can result in conflicts with similar objects that already exist in the hierarchy.

Why can’t I install a primary site as a child of another primary site like I could in Configuration Manager 2007?
With System Center 2012 Configuration Manager, primary sites have changed to support only secondary sites as child sites, and the new central administration site as a parent site. Unlike Configuration Manager 2007, primary sites no longer provide a security or configuration boundary. Because of this, you should only need to install additional primary sites to increase the maximum number of clients your hierarchy can support, or to provide a local point of contact for administration.



Why do I need SQL Server for my secondary site?
In System Center 2012 Configuration Manager, secondary sites require either SQL Server, or SQL Server Express to support database replication with their parent primary site.



Sunday, 24 April 2016

SCOM 2012 R2 Windows Server 2012 R2 Storage Direct Management Pack

SCOM 2012 R2 Windows Server 2012 R2 Storage Direct  Management Pack


  • Microsoft has released a new Storage Management Pack for Window Server 2012 R2.
  • This management pack supports up to:
    16 Storage Nodes
    12 Storage Pools
    120 File Shares.
  • This Management Pack contains rules to monitor physical disk and enclosure state in storage spaces.
  • Health is calculated by the storage service and is passed to Virtual Machine Manager (VMM) using the Storage Management API (SM-API), and is in turn passed to Operations Manager (OM) through the OM connector for VMM.

  • There are no state or alert visualizations as part of this MP. 
  • All alerts for physical disks and enclosures must be manually closed and any health state impact manually reset.
  • You can see file share and storage pool health on the VMM Fabric Dashboard or you can build your own views in a custom MP. 
  • If OM agent proxy setting is not enabled for file server nodes and VMM server, it needs to be turned on. This can be done from Administration space in OM console.
You can see the Rollup Model below for the MP


You can Download the Management pack from here -->Click here to download

Monday, 8 February 2016

Citrix Aquires Comtrade Managemet pack

Citrix Aquires Comtrade Managemet pack

  • Citrix Product is one of the most important product that is monitored via SCOM
  • Almost 50 % of desktops and app are Citrix Apps in any environment.
  • Comtrade was the only reliable MP for Citrix across the world for SCOM.
  • Citrix has now aquired Comtrade MP which means we will get it lke HP mp's free of cost .

Read More:-->

Wednesday, 3 February 2016

SCOM 2012 R2 UR9 Upgrade Step by Step

SCOM 2012 R2 UR9 Upgrade Step by Step

  • Microsoft released UP(update Roleup) every now and then. They generally do lot of bug fixes in these update.Today Microsoft has released SCOM UR9 Upgrade. Lets go Step by Step in this upgrade.
Upgrading the Management Server:

  • Extract the Files that you downloaded to C:\Bin\UR9 folder


  • Login using the SCOM service account or account which has local admin,SCOM admin and SA Admin on SCOM database.Usually your SCOM service account will have these acc. So i suggest to use it.
  • Now Open Command Prompt in elevated mode and Go to "C:\Bin\UR9" folder
  • Type "KB3129774-AMD64-Server.msp"


      •  This will lauch Update.You will be prompted to restart your system after the update.Click yes and system will restart
      • Once its up check the Application log for Event ID 1036. Make sure it successful.


        •  Also check the DLL Versions in the Operations Manager\Server folder and make sure its showing 7.1.10226.1177


            •  You Should upgrade your additional management server in same way.

            Upgrade SCOM Webconsole and SCOM Console:


            • Now Open Command Prompt in elevated mode and Go to "C:\Bin\UR9" folder
            • Type "KB3129774-AMD64-ENU-WebConsole.msp"




            •  This will update the Web console.
            • Next Type "KB3129774-AMD64-ENU-Console.msp"


            •  This will update the Console.


            Updating the Gateway Servers:

            • Login to your Gateway server. Copy the Downloaded file  TO "C:\Bin\UR9" Folder
            • Now Open Command Prompt in elevated mode and Go to "C:\Bin\UR9" folder
            • Type "KB3129774-AMD64-Gateway.msp"

            • This will update the Gateway Server



             Update the SCOM Databases:


            • First Make sure you have stopped all SCOM services on your Management server and restart the SQL Server service once
            • Login to the SCOM Database Server
            • Open a SQL management studio query window, connect it to your Operations Manager database.
            • Now go to the upgrade Management server at below location %SystemDrive%\Program Files\Microsoft System Center 2012 R2\Operations Manager\Server\SQL Script for Update Rollups
            • Copy the SQL Scripts "update_rollup_mom_db.sql" and execute in the Query windows. This script could faill but continue trying till it succeeds




            • Try re-running the script several times until it completes without errors.  In a production environment, you have to shut down the services (sdk, config, and healthservice) on your management servers, to break their connection to the databases, to get a successful run. 
            • Once OperationsManager DB is update close the Query window.
            • Now open a SQL management studio query window, connect it to your OperationsManagerDW database.
            • Copy the SQL Scripts "UR_Datawarehouse.sql" and execute in the Query windows. This script could faill but continue trying till it succeeds.



            Import the management packs:
            • There are 55 management packs in this update!.Most of these we don’t need 
            • The path for these is on your management server, after you have installed the “Server” update: \Program Files\Microsoft System Center 2012 R2\Operations Manager\Server\Management Packs for Update Rollups
            • You can install the MP Shown below and ignore the rest.Total 19 MP's will come.



              Updating the Agents:

              • Login to SCOM Management server
              • Open SCOM Console==>Administration Tab
              • Click on "Pending Management".Select all the agent you see and Click "Approve".

              Monday, 29 June 2015

              Lync 2013 MP Install Step by Step SCOM 2012 R2

              Lync 2013 MP Install Step by Step:


              • Lync has taken over the entire communication channel.
              • Gone are the VOIP IP Cisco Phones which use to sit on your Desk.
              • Today everything is going to Mobile and Lync is the best and cheapest option from Micrososft.
              • So almost all enterprise have decided to migrate to Lync. So much is the Lync affects today that, we need a realtime monitoring more critical then outlook.
              • So Microsoft has worked on it very hard and have brought the realtime Monitoring using SCOM for Lync 2013.
              Microsoft Lync Server 2013 includes two SCOM management packs:

              • The Component and User Management Pack (Microsoft.LS.2013.Monitoring.ComponentAndUser.mp):
              • This MP Monitors Lync Server issues recorded in event logs, registered by performance counters, or logged in the call detail records (CDR) or the Quality of Experience (QoE) databases.

              Active Monitoring Pack (Microsoft.LS.2013.Monitoring.ActiveMonitoring.mp):

              • This MP proactively tests key Lync Server components such as logging on to the system, exchanging instant messages, or making calls to a phone located on the public switched telephone network (PSTN). These tests are conducted using the Lync Server synthetic transaction cmdlets. 

              Example:

              Test-CsIM: cmdlet is used to simulate an instant messaging conversation between a pair of test users. If this simulated messaging conversation fails an alert will be generated.

              Steps to Install MP:

              • Download the files Microsoft.LS.2013.Monitoring.ActiveMonitoring.mp and Microsoft.LS.2013.Monitoring.ComponentAndUser.mp.
              • In System Center Operations Manager, click Administration.In the Administration pane, right-click Management Packs, and then click Import Management Packs.
              • In the Select Management Packs dialog box, click Add, and then click Add from disk.
              • In the Online Catalog Connection dialog box, click Cancel to prevent Operations Manager from going online to see if any dependencies exist for the Lync Server management packs. If you are using System Center Operations Manager 2012, click No.
              • In the Select Management Packs to import dialog box, locate and select the files Microsoft.LS.2013.Monitoring.ActiveMonitoring.mp and Microsoft.LS.2013.Monitoring.ComponentAndUser.mp and then click Open. To select multiple files in the dialog box, click the first file, hold down the Ctrl key and then click the second file.
              • In the Select Management Packs dialog box, click Install. If you get an error message and installation fails, that typically means that the management pack files are in a folder protected by the Windows User Account Control. If this occurs, copy the files to a different folder and then restart the import and installation process.
              • In the Select Management Packs dialog box, click Close. Note that the import and installation process might require several minutes to complete.

              Wednesday, 17 June 2015

              Audiocodes Management pack for Lync 2013

              Audiocodes Management pack for Lync 2013


              • Audio codes Management pack for Lync 2013 is SNMP based MP which is used to monitor the Audio codes devices.
              • Audio codes are the back end device which acts like a epbax box for lync.
              • Lync telephony is fast replacing the traditional cisco voip phones which we see in most organizations.
              • The cost saving benefit is huge and lot of organizations are migrating to it.
              • So it become vital to monitor these devices and Audicodes have replased a Management for all there devices be it M1K,M2K,M3K.
              • The Configuration of this MP is straight forward..First you discover it as netowrk device in SCOM. Then you install the MP and the devices will start getting monitored.
              • To download the MP go click here

              Tuesday, 19 May 2015

              What is a Management Pack an What does it contain

              What is a Management Pack an What does it contain


              Management packs contain monitoring settings for applications and services. Once you import the management pack in SCOM 2012 R2 management group, it immediately begins monitoring objects based on configurations and thresholds that are set by the management pack.

              Each management pack can contain any or all of the following:

              • Monitors:It tells an agent to track the state of various parts of a managed component.
              • Rules: It tells an agent to collect performance and discovery data, send alerts and events etc.
              • Tasks: The activities that can be executed by either the agent or the console.
              • Views: It offer customized user interfaces for monitoring and managing this component.
              • Reports: It define specialized ways to report on information about this managed component.
              • Object discoveries: which identify objects to be monitored.
              • Knowledge Base: It provides Knowledge to help operators diagnose and fix problems.

              Wednesday, 13 May 2015

              Upgrade SCOM 2012 R2 agent using SCCM for latest UR upgrade



              Upgrade SCOM 2012 R2 agent using SCCM for latest UR upgrade



              • Follow the below command to upgrade SCOM agents using SCCM



              msiexec /i path\Directory\MOMAgent.msi /qn /l*v %temp%\MOMAgentUpgrade.log
              
              
              • This will upgrade the agent using the latest UR4 or UR5 upgrade

              Sunday, 10 May 2015

              New Features added in SCOM 2016

              New Features added in SCOM 2016


              • SCOM 2016 is the next version of SCOM after SCOM 2012.
              • There architecture remains the same, but the support for dasboard has been improved vastly.
              • If you have see the SQL mp then you could see cool charts being displayed.
              • The same has been extended to all the MP's and given as a template which you can extend it to your MP as well.
              • The support for Azure is also improved,earlier you have connect through certificates to establish connection, but now you connect through Azure AD,so you just have to enter the username and password and it will connect you to the Azure platform from scom.This is a huge welcome move.
              • Also it will support Windows 2016,and SQL 2014.

              Tuesday, 13 August 2013

              SCOM 2012 SP1 upgrade fails with error "Failed to set DW upgrade scenario"

              Reason:

              This can occur if there is an invalid Data Warehouse server name or SRS database instance name in the registry on the Management Server.

              Resolution:

              To resolve this, verify that the correct Data Warehouse server name and SRS database instance name exist in the registry on the Management Server:

              Data Warehouse server name Reg key:

              HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Operations Manager\3.0\Setup\DatawarehouseDBServerName

              SRS database instance name REG KEY:

              HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Operations Manager\3.0\Reporting\SRSInstance

              Once its done, you can do the upgrade and should work fine

              Sunday, 3 February 2013

              SCOM 2007 to SCOM 2012 Upgrade conceptual steps

              These are the step that you have to do before upgrade



              • http://technet.microsoft.com/en-us/video/prepare-yourself-to-move-to-scom-2012