System Center 2012 R2 is RTM..So What is New ?!!!

October 18, 2013 Leave a comment
Categories: DPM, Opalis 2012, SCCM, SCOM, VMM, VMM2012 Tags:

Microsoft® SQL Server® Backup to Microsoft Windows® Azure®Tool

October 16, 2013 Leave a comment

Microsoft SQL Server Backup to Windows Azure Tool enables backup to Windows Azure Blob Storage and encrypts and compresses SQL Server backups stored locally or in the cloud.

SQL Server 2012 and SQL Server 2014 have built in capability to back up to Windows Azure storage. The SQL Server Backup to Windows Azure tool provides the same functionality to previous versions of SQL Server. It can also be used to specify encryption and compression for your backups.

Using the 3-step wizard, you can specify a rule or set of rules that are applied to any SQL Server backup. One example of a rule could be to redirect all local backups to the specified Windows Azure storage. Another example of a rule would be to use compression or encryption for backups stored in a specific location.

Once you configure the rules, these rules are applied to SQL Server Backup files. If the rule is set to use Windows Azure storage account, the tool redirects the backups to the specified Windows Azure storage account, but leaves a stub file with metadata information to be used during restore.

Benefits:

· Support for backups to Windows Azure Storage for SQL Server versions that do not have the built-in capability. Using Windows Azure storage for your backups has several benefits off-site storage for disaster recovery, ability to access from any location, etc. For more information, see SQL Server Backup and Restore with Windows Azure.

· Encryption and Compress support for SQL Server versions that do not have the built in capability. Currently only SQL Server 2014 has encryption support, and SQL Server 2008 or later support compression during backup. SQL Server 2008 supports compression in Enterprise edition only, but for SQL Server 2008 R2 and later encryption is supported on Standard editions or higher.

 

Download from there

http://www.microsoft.com/en-us/download/details.aspx?id=40740

Categories: Azure, SQL

VMM Tricks: Upgrading from Currently installed of VMM to System Center VMM 2012 is Not Supported

October 13, 2013 6 comments

Some times when you try to Install/upgrade VMM 2012 “ or VMM 2012 with SP1” you get the error during install of SCVMM 2012.

“you cannot upgrade from the currently installed version of VMM to system center 2012 SP1 virtual machine manager. You must first uninstall VMM,  and then install SCVMM 2012 SP1. If you are running system center suite, when you uninstall VMM, you can retain the database. When you install System center 2012 SP1, use the retained database”

 

VMM error

 

to uninstall Old VMM Server from your environment please follow these steps

Action Plan 1:

1.Backup new VMM SP1 instance.
2.Uninstall new VMM SP1 instance.
3.Uninstall old VMM SP1 instance.
4.Install new VMM SP1.

Action Plan 2:

To force an uninstall via command, please follow these steps:

1.Find VMServerUninstall.ini from folder Program Files\Microsoft System Center 2012\Virtual Machine Manager\setup.

2.Replace its content with following code:

[OPTIONS]
RemoteDatabaseImpersonation=0
RetainSqlDatabase=0
ForceHAVMMUninstall=1

If this VMM server’s SQL instance located on a remote server, please change the value of RemoteDatabaseImpersonation to 1.

3.Save this ini file to c:\temp.
4.Run command to locate the folder contain VMM Server setup file under command prompt: cd VMM_Setup_File_folder.
5.Run command to force uninstall VMM server:
setup.exe /server /x /f C:\Temp\VMServerUninstall.ini /
SqlDBAdminDomain DomainName /SqlDBAdminName SQLAdmin /SqlDBAdminPassword password

Note: DomainName is your domina name “Like “Contoso or Fabrikum”
Account Domain\SQLAdmin is  an SQL Server administrator account which is used to connect to backend SQL server.

Categories: VMM, VMM2012

VMM 2012 SP1 Error 2912 when Moving VM

October 3, 2013 2 comments

One of the most common error that I saw in many environment when you try to move VM from one Server to another you get this message

Error (2912)
An internal error has occurred trying to contact an agent on the Server.Domain.Local server: NO_PARAM: NO_PARAM.
Unknown error (0x80072f0d)

Recommended Action
Ensure the agent is installed and running. Ensure the WS-Management service is installed and running, then restart the agent.

After checking SCVMM agent and services are running fine on hosts you have to check BITS related configuration, you can use these steps to adjust the BITS to remove this problem:

  1. On Server.Domain.Local , check if we have installed feature Background Intelligent Transfer Service (BITS) feature.
  2. Open Regedit and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft System Center Virtual Machine Manager Server\Settings
  3. Locate the BITSTcpPort name on the right. It’s data value should be 443
      a. Double click BITSTcpPort in order to modify the data. Make sure the Base is set to ‘Decimal’
      b. Change 443 to 765, or any other number less than 32768. Do not use a port that another protocol uses such as RDP (3389)
      c. Click ‘OK’ to save this value
  4. Restart the ‘Virtual Machine Manager’ and ‘Virtual Machine Manager Agent’ services on the SCVMM server. (On managed hosts simply restart the ‘Virtual Machine Manager Agent’ service’)
  5. Once complete on the SCVMM server and all Hosts you can continue using SCVMM

 

Categories: VMM, VMM2012 Tags:

SCSM 2012 R2 PowerShell Tasks Created with the Authoring Tool Do Not Work Properly

October 2, 2013 2 comments

Since we are getting ready for System Center R2 release we start testing different upgrade scenarios for System Center. One of the problems we faced that some custom workflows that has PowerShell scripts is not running on SCSM R2. This a well known issue with System Center 2012 R2 and you have to edit MonitoringHost.exe.config to get over it.

Description: When you use the Authoring tool in Service Manager for System Center 2012 R2 to create a workflow, then custom scripts called by the workflow fail. This is due to a problem in the Service Manager MonitoringHost.exe.config file.

Workaround: To work around this problem, update the MonitoringHost.exe.config XML file using the following steps.

  1. Navigate to %ProgramFiles%\Microsoft System Center 2012\Service Manager\ or the location where you installed Service Manager.
  2. Edit the MonitoringHost.exe.config file and add the section in italic type from the example below in the corresponding section of your file. You must insert the section before <publisherPolicy apply="yes" />.
  3. Save your changes to the file.
  4. Restart the System Center Management service on the Service Manager management server.

<?xml version="1.0"?>
<configuration>
  <configSections>
    <section name="uri" type="System.Configuration.UriSection, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" />
  </configSections>
  <uri>
    <iriParsing enabled="true" />
  </uri> 
  <runtime>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
        <assemblyIdentity name="Microsoft.Mom.Modules.DataTypes" publicKeyToken="31bf3856ad364e35" />
        <publisherPolicy apply="no" />
        <bindingRedirect oldVersion="6.0.4900.0" newVersion="7.0.5000.0" />
      </dependentAssembly>
      <dependentAssembly>
        <assemblyIdentity name="Microsoft.EnterpriseManagement.HealthService.Modules.WorkflowFoundation" publicKeyToken="31bf3856ad364e35" />
        <publisherPolicy apply="no" />
        <bindingRedirect oldVersion="6.0.4900.0" newVersion="7.0.5000.0" />
      </dependentAssembly>
  <dependentAssembly>
         <assemblyIdentity name="Microsoft.EnterpriseManagement.Modules.PowerShell" publicKeyToken="31bf3856ad364e35" />
        <bindingRedirect oldVersion="6.0.4900.0" newVersion="7.0.5000.0" />
     </dependentAssembly>
      <publisherPolicy apply="yes" />
      <probing privatePath="" />
    </assemblyBinding>
    <gcConcurrent enabled="true" />
  </runtime>
</configuration>

Categories: SCSM

#VMM 2012 R2 Integration with #SCOM 2012 R2 Error (10218)

September 28, 2013 Leave a comment

When creating the integration between Virtual Machine Manager 2012 R2 and Operations Manager 2012 R2 , the integration fails with the following error:

VMM SCOM Integration

Error (10218)
Setup could not import the System Center Virtual Machine Manager Management Pack into Operations Manager server because one or more required management packs are missing. The VMM Management Packs cannot be deployed unless the following component management packs are present in Operations Manager :
Windows Server Internet Information Services 2003,
Windows Server 2008 Internet Information Services 7,
Windows Server Internet Information Services Library,
SQL Server Core Library.

Recommended Action
To provide the missing component management packs, ensure that the following management packs have been imported into Operations Manager server:
Microsoft Windows Server 2003 Internet Information Services Management Pack for OpsMgr 2012 (version 6.0.6278.0 or later)
Microsoft SQL Server 2005 Management Pack(version 6.0.5000.0 or later)
You can download the management packs from the System Center Operations Manager Catalog at
http://go.microsoft.com/fwlink/?LinkId=86411

 

VMM with Operations Manager Integration

Prerequisites

Before you connect VMM with Operations Manager, perform the following actions:

  • Ensure that an appropriate version of Windows PowerShell is installed on all Operations Manager management servers:
    For System Center 2012: Windows PowerShell 2.0
    For System Center 2012 SP1: Windows PowerShell 3.0
    To determine which version of Windows PowerShell is on a server, run the following:
    Get-Host | Select-Object Version
  • Make sure that port 5724 is open between VMM and Operations Manager.
  • Install an Operations Manager Operations console on the VMM management server.
  • Install Operations Manager agents on the VMM management server and all hosts under management by VMM (managed hosts). For more information, see Operations Manager Agent Installation Methods.
  • Verify that the managed hosts on which you installed agents are visible in Operations Manager. To do this, in the Operations console, clickAdministration and then, in the Administration pane, under Device Management, click Agent Managed. Verify that the expected hosts are listed.
  • In Operations Manager, import the necessary management packs, as described in How to Import an Operations Manager Management Pack. Management packs, which in some cases are called “monitoring packs,” are available through the catalog at the Microsoft System Center Marketplace. The necessary management packs are as follows:
    Windows Server Internet Information Services 2003
    Management packs that are required by the management pack for Windows Server 2008 Internet Information Services 7:
    Windows Server 2008 Operating System (Discovery)
    Windows Server Operating System Library
    Windows Server 2008 Internet Information Services 7
    Windows Server Internet Information Services Library
    SQL Server Core Library
    I verified Prerequisites for integration as per Microsoft TechNet Link and make sure that I imported all needed MP

Cause
Conflict between exist old Microsoft Virtualization Core Library in Operations Manager. The cause of the problem is that SCVMM 2012 will import a newer version of the Microsoft Virtualization Core Library Management Pack and the old version cannot be present in order for integration to complete successfully

Solution

Remove the old version of the Microsoft Virtualization Core Library and try Integration again.

Reference

 

Categories: SCOM, VMM, VMM2012 Tags:

Oracle on Windows Azure

September 25, 2013 2 comments

 

Microsoft and Oracle provide end-to-end support for customers running business-critical Oracle software on Windows Azure


Oracle Database, Oracle WebLogic Server, and the Java development environment are now available, in preview, in the Windows Azure Virtual Machines Image Gallery. These images include licenses for the Oracle software that they contain.

During the preview period, there is no charge for the included Oracle licenses. You will pay only for the Windows Azure compute and storage resources that your Virtual Machine consumes. If you would prefer to use an Oracle software license that you already own, you can do that too. Just choose a Windows Server image from the Image Gallery and install the Oracle software yourself.

Whether you bring your own Oracle license or use one of the license-included images, you now have increased flexibility and choice in where to deploy your applications and the peace of mind that comes from knowing you will be fully supported by Oracle.

To get started, sign in to the

Windows Azure Management Portal and add a new Virtual Machine from the Image Gallery. For more information, visit the Oracle information page on the Windows Azure website.

Categories: Azure, IaaS Tags:
%d bloggers like this: