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.

     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)

   Hi All :

   Beginning with Configuration Manager SP1, you can configure a distribution point that is not on a site server to be a pull-distribution point. When you deploy content to a large number of distribution points at a site, pull-distribution points can help reduce the processing load on the site server and can help to speed the transfer of the content to each distribution point. This efficiency is achieved by offloading the process of transferring the content to each distribution point from the distribution manager process on the site server. Instead, each pull-distribution point individually manages the transfer of content by downloading content from another distribution point that already has a copy of the content. A pull-distribution point can only obtain content from a distribution point that is specified as a source distribution point.

   Pull-distribution points support the same configurations and functionality as typical Configuration Manager distribution points. For example, a distribution point that is configured as a pull-distribution point supports the use of multicast and PXE configurations, content validation, and on-demand content distribution. A pull-distribution point supports HTTP or HTTPS communications from clients, supports the same certificates options as other distribution points, and can be managed individually or as a member of a distribution point group. However, the following configurations are exceptions to support for the pull-distribution point:

• A cloud-based distribution point cannot be configured as a pull-distribution point. Similarly, a cloud-based distribution point cannot be used as a source distribution point.
• A distribution point on a site server cannot be configured as a pull-distribution point.
• The prestage content configuration for a distribution point overrides the pull-distribution point configuration. A pull-distribution point that is configured for prestaged content waits for the content. It does not pull content from source distribution point, and, like a standard distribution point that has the prestage content configuration, does not receive content from the site server.
• A distribution point that is configured as a pull-distribution point does not use configurations for rate limits when it transfers content. If you configure a previously installed distribution point to be a pull-distribution point, configurations for rate limits are saved, but not used. If, at a later time, you remove the pull-distribution point configuration, the rate limit configurations are implemented as previously configured. 
• A distribution point that is configured as a pull-distribution point does not use the Retry settings for content distribution. Retry Settings can be configured as part of the Software Distribution Component Properties for each site. To view or configure these properties, in the Administration workspace of the Configuration Manager console, expand Site Configuration, and then select Sites. Next, in the results pane, select a site, and then on the Home tab, select Configure Site Components, and then select Software Distribution. The following sequence of events occurs when you distribute software to a pull-distribution point:
  • As soon as content is distributed to a pull-distribution point, the Package Transfer Manager on the site server checks the site database to confirm if the content is available on a source distribution point. If it cannot confirm that the content is on a source distribution point for the pull-distribution point, it repeats the check every 20 minutes until the content is available.
  • When the Package Transfer Manager confirms that the content is available, it notifies the pull-distribution point to download the content. When the pull-distribution point receives this notification, it attempts to download the content from its source distribution points.
  • After the pull-distribution point completes the download of content, it submits this status to a management point. However, if after 60 minutes, this status is not received, the Package Transfer Manager wakes up and checks with the pull-distribution point to confirm if the pull-distribution point has downloaded the content. If the content download is in progress, the Package Transfer Manager sleeps for 60 minutes before it checks with the pull-distribution point again. This cycle continues until the pull-distribution point completes the content transfer.
• To transfer content from a source distribution point in a remote forest, the computer that hosts the pull-distribution point must have a Configuration Manager client installed. A Network Access Account that can access the source distribution point must be configured for use.

    The attached document will to show you how to installing and configure a DP being a Pull-DP.

    Please use Adobe Reader X or above version to open!

    Enjoy!

    Justin Gao

    Microsoft (China)

       Hi All :

       When you installing Exchange Server 2013 Mailbox High-available on Windows Server 2012 environment , you may encounter this error : An Active Manager operation failed with a transient error: Please retry the operation. Error: The fully qualified domain name for node 'XXXX' could not be found.

        Now , you need to assign the machine account of the first node added to the DAG with full control of the pre-staged object.

      1. Select the appropriate container in Active Directory Users and Computers snap-in console where you wish the account to be created.  Right click, select New –> Computer :

      2. In the Computer name box, type the name that was assigned to the database availability group :

        3. Click OK , the computer account created . Right-click this account and click Properties :

       4. Then click Security tab , and click Add... , add the first DAG member server computer account and assign the machine account Full control Allow permission :

   6. When presented with the disable dialog, select Yes :

     7. After the object has been successfully disabled,  press the OK button on the success confirmation :

    8. And now , you can start to creating DAG successfully !

     Enjoy!

     Justin Gao

     Microsoft (China)

   Hi All :

   This document will to show you how to implementing Application Virtualization 5.0 deployment, and how to sequence application and so on .

   More information you can reference TechNet library :  http://technet.microsoft.com/en-us/library/jj713487.aspx

   Please use Adobe Reader X or above version to open.

   Enjoy!

   Justin Gao

   Microsoft (China)

      Hi All :

      Lync Server 2013 CU (KB 2809243)  has been released at Jan.8 2014.  You can download this CU from this link : http://www.microsoft.com/en-us/download/details.aspx?id=36820

      The update process is very simple. For the best practice, you can refer this flowchart :  

     Now I will to show this process.

     Logon to the Lync Server Frontend server for enterprise edition or standard edition. Open the Powershell cmdlet , run Get-CsPoolUpgradeReadinessState , If the State value of the pool is Busy, wait for 10 minutes, and then try to run the Get-CsPoolUpgradeReadinessState cmdlet again. If you see Busy for at least three consecutive times after you wait 10 minutes in between each attempt, or if you see any result of InsufficientActiveFrontEnds for the State value of the pool, there is an issue with the pool.

     Stop new connections to the frontend server by using the Stop-CsWindowsServers cmdlet and run Get-CsPoolUpgradeReadinessState again

     Make sure the State is Ready, go to the update phase. Open the Lync Server 2013 Cumulative Update Installer,  you will to see the updates list :

    Click Install Updates will start automatic installing process

       Wait some minutes, the updates install completed

    Then use Start CsWindowsServices cmdlet to starting all services. Logon to the Lync Server 2013 Control Panel, you can see the version is 5.0.8308.556:

   Now the update is completed. For more information, please check the KB 2809243 : http://support.microsoft.com/kb/2809243/en-us

   Enjoy!

   Justin Gao

   Microsoft (China)