• Migration from Configuration Manager 2007 to SC2012 Configuration Manager RTM

    Posted over 2 years ago
    by Justin Gao}

       Hi All :

       Because of the design changes that were introduced in Microsoft System Center 2012 Configuration Manager, you cannot upgrade an existing Microsoft System Center Configuration Manager 2007 infrastructure to System Center 2012 Configuration Manager. However, you can maintain your existing investment when you migrate to System Center 2012 Configuration Manager and use the built-in functionally within System Center 2012 Configuration Manager.

       When you migrate from Configuration Manager 2007 to System Center 2012 Configuration Manager, you can access data from the site databases that you identify in the Configuration Manager 2007 infrastructure and then transfer this data to the System Center 2012 Configuration Manager hierarchy. Migration does not modify the data in the Configuration Manager 2007 hierarchy, but instead discovers the data and stores a copy of it in the System Center 2012 Configuration Manager database. You can migrate some or all of the supported data from a Configuration Manager 2007 site to a System Center 2012 Configuration Manager site. You can also migrate the data from a single Configuration Manager 2007 site to several different System Center 2012 Configuration Manager sites, or you can move data from multiple Configuration Manager 2007 sites to a single System Center 2012 Configuration Manager site.

    Benefits of Migrating to System Center 2012 Configuration Manager :

    When you migrate your Configuration Manager 2007 site infrastructure, you retain your existing management information and gain the following benefits from System Center 2012 Configuration Manager.

     

    BenefitMore information

    Native 64-bit code

    System Center 2012 Configuration Manager is a native 64-bit application.

    Site database improvements

    The System Center 2012 Configuration Manager database supports full Unicode.

    Database replication between sites

    Replication in System Center 2012 Configuration Manager is based on Microsoft SQL Server, which improves the performance of site-to-site data transfer.

    User-centric management

    Users are the focus of management tasks in System Center 2012 Configuration Manager. For example, you can distribute software to a user even if you do not know the device name for that user. Additionally, System Center 2012 Configuration Manager gives users much more control over what software is installed on their devices and when it is installed.

    Hierarchy simplification

    The new central administration site type in System Center 2012 Configuration Manager, as well as changes to the behavior of primary and secondary sites let you build a simpler site hierarchy that uses less network bandwidth and requires fewer servers.

    Role-based administration

    This central security model in System Center 2012 Configuration Manager offers hierarchy-wide security and management that corresponds to your administrative and business requirements.


       

         About how to migration from Configuration Manager 2007 to System Center 2012 Configuration Manager RTM , you can reference this document .

         Please use Adobe Reader X or above version to open .

     

        Enjoy !

        Justin Gao

        Microsoft (China)

  • System Center 2012 Data Protection Manager RTM managing system protection

    Posted over 2 years ago
    by Justin Gao}

       Hi All :

        System protection aims to protect you against two scenarios – one where your computer starts, but you have lost system files and registry; and the other where the computer does not start and you have to recover everything. System Center 2012 – Data Protection Manager (DPM) enables you to protect your computer against both these scenarios.

        In the past, disaster recovery entailed rebuilding a computer from scratch. This meant installing the operating system, applying updates, installing applications, and then finally recovering data. This was a laborious and error-prone method. DPM saves you the time and trouble of rebuilding your system.

        In DPM, System State protection consists of protecting the operating system files, and bare metal recovery (BMR) protection consists of protecting the operating system files and all data except user data on critical volumes.

        DPM uses Windows Server Backup (WSB) to perform System State backup and BMR backup. For recovery, DPM will retrieve the backups and you will use the backup data to perform recovery by using WSB.

    Prerequisites

    • Windows Server Backup installed on the protected computer for BMR.
    • Windows Recovery Environment (WinRE) for BMR.

    Unsupported Scenarios

    The following scenarios are not supported for BMR:

    • Computers running Windows Server 2003.
    • Computers running client operating systems like Windows XP or Windows Vista or Windows 7.
    • A DPM server cannot protect itself for BMR.
    • Disk-Tape protection is not supported for BMR. However, long-term to tape with short-term to disk (D-D-T) is supported.

     

        Now , i will to show how to protection system status and implementing bare metal recovery .

        Create a protection group for a server that protected target , and select Bare Metal Recovery under System Protection node , the System State will be selected at the same time :

       on the Select Data Protection Method step , enter a protection group name , and select your protection method , Disk or Tape :

      and finish this wizard , the recovery point will start creating :

       Waiting some minutes , backup finished :

       Now , i will recovering BMR (Bare Metal Recovery) , on the Recovery workspace , select any System Protection recovery point , and then click Recover on the Ribbon :

       The Recovery Wizard Review Recovery Selection dialog box appears :

      On the Specify Destination dialog box , assign a path that store recovered files :

     

       And finish recovery :

      

        Now , i will to recovery this BMR to bare metal server . start up a bare metal server throw the Windows Server OS image :

     

       On the install windows step , click Repair your computer , and will into Re-image your computer step , assign BMR files path (this path should be a network path):

     

       and will start to recover this Windows Server OS :

      Waiting about 15-40 minutes , recovery finished . Restart and logon this OS , you can see recovery successfully :

     

        More detail steps , you can reference the attachment document !

     

        Please use Adobe Reader X or above version to open .

     

        Enjoy!

        Justin Gao

        Microsoft (China)

  • FreeBSD Support on Windows Server Hyper-V

    Posted over 2 years ago
    by Justin Gao}

       Hi All :

       With Windows Server our goal is to provide the best platform for cloud and you can see that in spades in Windows Server 2012. We’ve quietly engaging on this strategy for years. For example, Linux support on Hyper-V. Microsoft has been contributing GPL to the Linux kernel for years now and we’ve long supported Red Hat, SUSE, CentOS and the latest release of Ubuntu 12.04 (released with the last couple of weeks) even includes the Hyper-V drivers built in by default. Now, we’re taking this to the next level:

     FreeBSD support on Hyper-V.

     

    We’ve listened to our valued customers who have told us that they’ve been successful virtualizing Windows and Linux and now want to take a look at their pockets of FreeBSD Unix and want to consolidate them on Hyper-V and better manage them via System Center. So, today, we’re announcing that we are working with our partners NetApp and Citrix to develop and extend support for FreeBSD on Hyper-V. This means that we’re developing FreeBSD drivers to enable FreeBSD to run as a first-class guest on Windows Server Hyper-V. The drivers will be fully released early this summer, including the source code for the drivers under the BSD license, and will initially work with FreeBSD 8.2 and 8.3 on Windows Server 2008 R2 and eventually on Windows Server 2012.

     

       Enjoy!

       Justin Gao

       Microsoft (China)

  • System Center 2012 App Controller RTM deployment document

    Posted over 2 years ago
    by Justin Gao}

       Hi All :

       System Center 2012 App Controller is a unified management public cloud and private cloud tool , and App Controller is simple and straightforward to install and use.

       Now , i will to show you how to deploy SC2012 App Controller RTM , you can reference this document.

       Please use Adobe Reader X or above version to open !

       Enjoy !

       Justin Gao

       Microsoft (China)

  • System Center 2012 Orchestrator RTM Deployment Document

    Posted over 2 years ago
    by Justin Gao}

       Hi All :

    IT administrators perform many tasks and procedures to keep the health of their computing environment up-to-date and their business running. Tasks might include the following diverse activities, for example, new employees require that accounts and resources are configured, a business acquisition requires integrating a system from another vendor, and new hardware requires provisioning. Individual tasks and subtasks are automated, but typically, not the whole process. In addition, the administrators must maintain quality standards and system efficiency. System Center 2012 - Orchestrator can tie disparate tasks and procedures together by using the graphical user-interface Runbook Designer to create reliable, flexible, and efficient end-to-end solutions in the IT environment.

    By using Orchestrator, you can carry out the following tasks:

    • Automate processes in your data center, regardless of hardware or platform.

    • Automate your IT operations and standardize best practices to improve operational efficiency.

    • Connect different systems from different vendors without having to know how to use scripting and programming languages.

    Custom automation

    Orchestrator provides tools to build, test, debug, deploy, and manage automation in your environment. These automated procedures, called runbooks, can function independently or start other runbooks. The standard activities defined in every installation of Orchestrator provide a variety of monitors, tasks, and runbook controls with which you can integrate a wide range of system processes. Each activity in a runbook publishes data that is available to any subsequent activity in that runbook. You use this Published Data to provide dynamic, decision-making capabilities, which can include creating emails, alerts, log files, accounts, and more.

    Your IT organization can use Orchestrator to improve efficiency and reduce operational costs to support cross-departmental objectives. Orchestrator provides an environment with shared access to common data. By using Orchestrator, you can evolve and automate key processes between groups and consolidate repetitive manual tasks. You can automate cross-functional team processes and enforce best practices for incident, change, and service management by creating runbooks that are customized for your requirements. Through automation, regularly recurring tasks reduce the number of manual and error-prone activities in your environment. Orchestrator helps you improve the reliability and predictability of your IT procedures.

    Cross-platform integration

    Orchestrator integrates with System Center, other Microsoft products, and non-Microsoft products to enable interoperability across the data center. Orchestrator improves efficiency across multiple tools, systems, and departments by eliminating or crossing technology and organizational process structures. You can extend the capabilities of Orchestrator with integration packs that include additional functionality for both Microsoft and non-Microsoft products and technologies. Orchestrator activities and integration packs reduce unanticipated errors and shorten service delivery time by automating the common tasks associated with enterprise tools and products.

    End-to-end orchestration

    Orchestration is the collective name for the automated arrangement, coordination, and management of systems, software, and practices. It enables the management of complex cross-domain processes. Orchestrator provides the tools for orchestration to combine software, hardware, and manual processes into a seamless system. These tools let you connect and automate workflows.

    Just as manufacturing companies have automated common and repeatable tasks from their production processes, you can adopt this same efficiency in the IT environment by using Orchestrator to seamlessly perform and monitor your IT processes. Orchestrator can handle routine tasks, process enforcement, and reliably meet the demands of the largest enterprises. Orchestrator integrates seamlessly with other System Center products to integrate IT administrative tasks from start to finish.

    Extensible structure

    If you have a custom in-house solution, Orchestrator provides extensible integration to any system through the Orchestrator Integration Toolkit. You can create custom integrations that allow Orchestrator to connect to any environment.

    Orchestrator uses a Representational State Transfer (REST)-based web service that can perform processes like start and stop runbook jobs and get reporting information in Open Data protocol (OData) format. The web service lets you develop applications that can use live data from Orchestrator.

     

      This post , i will to show you how to deployment System Center 2012 Orchestrator RTM.

      Please use Adobe Reader X or above version to open .

     

       Enjoy !

       Justin Gao

       Microsoft (China)