Hi All :
Forefront endpoint protection 2010 is released on December , Now , FEP 2010 is integration with SCCM 2007 R2 or above version, this document is introduction how to deployment FEP 2010 RTM on SCCM 2007 environment .
Enjoy !
Justin Gao
Microsoft (China)
System Center 2012 RC is coming , i will successively publish System Center 2012 products family relate document . Today , i will provide System Center 2012 Configuration Manager RC2 advanced security deploy document .
I am look forward you can smoothly testing ConfigMgr 2012 .
Endpoint Protection in System Center 2012 Configuration Manager (SCEP 2012) lets you manage antimalware policies and Windows Firewall security for client computers in your Configuration Manager hierarchy.
When you use Endpoint Protection with Configuration Manager, you benefit from the following:
Endpoint Protection installs its own client in addition to the Configuration Manager client. The Endpoint Protection client has the following capabilities:
In this document , I will to show how to enable Endpoint Protection Point and configure EP agent to client .
Please use Adobe Reader X or above version to open.
Configuration Manager provides several methods that you can use to deploy an operating system. However, regardless of the deployment method that you use, there are several actions that you must take. These actions include:
This document will to show how to capture a reference computer , and made a OS package , and then implement Bare Metal computer to install OS.
Enjoy!
The attachment file is System Center Configuration Manager 2012 Beta2 deployment document update version , not including advanced security part. You can reference this document to rapid deploy ConfigMgr 2012 environment.
Hi All:
SCCM 2012 provider a new application software distribution function , you can use this document to implement this feature .
1. Exchange 2007可以支持升级到Exchange 2010，但需要提前将Exchange 2007所有服务器环境升级至 SP2或以上版本。
2. Exchange 2007如果更新至SP2或以上版本，则建议按照以下顺序进行各角色的更新： CAS、UM、HUB、Edge、Mailbox。
3. 不支持从Exchange 2007本地升级至Exchange 2010的操作，因此需要在Exchange 2007环境中，全新部署Exchange 2010环境后进行数据迁移。在数据迁移后可以实现Exchange 2010和Exchange 2007环境的共存，或再将Exchange 2007环境卸载等操作。
4. 如果企业环境中已经包含多台Exchange 2007服务器角色，而迁移后的Exchange 2010环境也包含多台服务器角色，则升级相应角色时应遵循以下升级顺序：CAS、HUB、UM、Mailbox、Edge。
5. 当开始将你的组织升级至Exchange 2010时，你必须首先升级面对Internet（Internet-facing）的AD站点中的服务器，随后再升级非面对Internet的AD站点中的服务器。如果你的企业具有多个面对Internet的AD站点，则首先要升级的是启用了外部发现记录（External Autodiscover Record ）的AD站点中的服务器，随后是其余面对Internet的AD站点中的服务器。
6. 如果你在全新的环境中部署了Exchange 2010，随后你将无法再添加Exchange 2007角色的服务器到该环境。如果你希望在Exchange 2010环境中添加Exchange 2007服务器，则首先你需要在Exchange 2007环境中部署Exchange 2010服务器，然后实现共存，至少保留一台Exchange 2007服务器，才能再随后添加Exchange 2007服务器角色。
7. 当你的环境处于Exchange 2007与Exchange 2010共存时，在同一个AD站点你需要每个Mailbox角色都有与之版本相对应的HUB角色存在。由于Exchange 2010 Exchange Server Object (XSO)模型的改变，Exchange 2010的HUB角色将不能传输从Exchange 2007 Mailbox服务器传递的数据。同样，Exchange 2007的HUB角色也不能与Exchange 2010的Mailbox服务器进行沟通。因此你需要一直保留Exchange 2007的HUB角色，除非在该AD站点中完全没有Exchange 2007的Mailbox角色。
8. Exchange 2010 管理控制台（EMC）没有32位版本，仅能部署在64位环境下的以下OS上：
l Windows Vista with SP2 for Management tools only installation
l 64-bit of Windows Server 2008 Standard or Enterprise with SP2
l 64-bit of Windows Server 2008 R2 Standard or Enterprise
l Windows 7
9. 在Exchange 2007和Exchange 2010共存环境下，两个版本的EMC均可以使用，但创建对象的操作，如新建邮箱或新建脱机通讯簿（OAB），只能在目标对象相同版本的EMC上执行。Exchange 2010的EMC���以查看Exchange 2007邮箱数据库，但无法管理。Exchange 2010的EMC无法启用或禁用Exchange 2007统一消息邮箱。Exchange 2010的EMC无法管理Exchange 2007的移动设备。
10. 在Exchange 2007和Exchange 2010共存环境下，要求查看对象的操作可以从任意版本的EMC执行到任意版本的Exchange对象，但以下情况例外：
l Exchange 2010 和 Exchange 2007 传输规则对象只能从其对应版本的 EMC 查看。
l Exchange 2010 和 Exchange 2007 服务器只能从其对应版本的 EMC 查看。
l Exchange 2010 EMC 中的队列查看器工具无法连接到 Exchange 2007 服务器以查看队列或邮件。
11. 不能在 Exchange 2010 和 Exchange 2007 之间使用邮件跟踪配置任务。必须在 Exchange 2007 服务器中使用 Exchange 2007 邮件跟踪工具，在 Exchange 2010 服务器中使用 Exchange 2010 邮件跟踪工具。
12. 在Exchange 2007和Exchange 2010共存环境下，只能在Exchange 2007下呈现而不能在Exchange 2010环境下呈现的对象如下：
l Storage Groups
l Exchange Administrators
l WebDAV
仅能在Exchange 2010环境下呈现而不能在Exchange 2007环境下呈现的对象如下：
l DAG
l Certificate creation
l Database copies
l Federation Trust
l Sharing Relationships
l Sharing Policies
l OWA Mailbox Policies
l Customer Experience Program properties
13. 在将用户邮箱从Exchange 2007版本迁移至Exchange 2010版本的过程中，该用户的邮箱仍处于在线状态，即终端用户在邮箱被迁移过程中仍可以正常使用邮箱。但从Exchange 2003至Exchange 2010、Exchange 2010 至Exchange 2003、Exchange 2010至Exchange 2007的邮箱迁移过程中，邮箱均处于离线状态，即终端用户在邮箱被迁移过程中不可使用邮箱，直到该邮箱被完全迁移完成才能使用。
Many people told me Exchange Server 2007 install on Windows Server 2008 not stability and occur many error .
Today , i will share my little case of troubleshooting with you.
I setup Exchange 2007 with sp1 (x86 or x64) on Windows Server 2008 , when install Hub transport role phase, display Service "MSExchangeTransport" on server not reach state "Running" . in Eventlog application logs , i find Event ID 2114 , Level is Error . Description: Process MSEXCHANGEADTOPOLOGYSERVICE.EXE(PID=2776). Topology discovery failed,error 0x80040a02(DSC_E_NO_SUITABLE_CDC).
The same way to install on Windows Server 2003 you can't encounter this error . I find Windows Server 2008 TCP/IP protocol including IPv4 and IPv6 , because i haven't IPv6 topology , so i unselected TCP/IPv6 , result in this fails.
when i selected TCP/IPv6 and reinstall Exchange Server 2007 , setup successful! J
Microsoft(China)
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:
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!
Hi all :
When you finished System Center 2012 cloud services process pack deployment , you need to create VMM , OM and Orchestrator connector , create and configure cost center and so on .
More details , please reference this document .
Compliance settings in System Center 2012 Configuration Manager provides a unified interface and user experience that lets you manage the configuration and compliance of servers, laptops, desktop computers, and mobile devices in your organization. Compliance settings contains tools to help you to assess the compliance of users and client devices with regard to a number of configurations, such as whether the correct Windows operating system versions are installed and configured appropriately, whether all required applications are installed and configured correctly, whether optional applications are configured appropriately, and whether prohibited applications are installed. Additionally, you can check for compliance with software updates, security settings, and mobile devices. Configuration item settings of the type WMI, registry, script, and all mobile device settings in Configuration Manager let you automatically remediate noncompliant settings when they are found.
In this document , I will to show you how to implement a secure and standardization desktop configuration .
Software updates in System Center 2012 Configuration Manager provides a set of tools and resources that can help manage the complex task of tracking and applying software updates to client computers in the enterprise. An effective software update management process is necessary to maintain operational efficiency, overcome security issues, and maintain the stability of the network infrastructure. However, because of the changing nature of technology and the continual appearance of new security threats, the task of effective software update management requires consistent and continual attention.
This document will display how to enable software update point and configure software synchronization , create automatic deployment rule and so on .
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.
Here’s a hotfix for ConfigMgr 2007 that we recently published. This is an update that adds support for Windows 8-based client computers in System Center Configuration Manager 2007 SP2.
An update is available that adds support for Windows 8-based client computers in Microsoft System Center Configuration Manager 2007 Service Pack 2 (SP2).
Additionally, this update adds Windows 8 and Windows Server 2012 to the supported platform list in the following features:
This update also fixes the following issues:
For the latest version of this article as well as a link to the hotfix, please see the following:
2750782 - Update adds support for Windows 8-based client computers in System Center Configuration Manager 2007 SP2 (http://support.microsoft.com/kb/2750782)
Windows 8 and Windows Server 2012 released , I believe more and more company will begin to deployment. I think you will start to consider how to planning activation method. MAK ? KMS ? or ...
Windows Server 2012 have a new feature call Active Directory-Based Activation :
Active Directory-based Activation is a role service that allows you to use Active Directory Domain Services (AD DS) to store activation objects, which can further simplify the task of maintaining volume activation services for a network. With Active Directory-based Activation, no additional host server is needed, and activation requests are processed during computer startup. Any computers running Windows 8 or Windows Server 2012 with a Generic Volume License Key (GVLK) that are connected to the domain will activate automatically and transparently. They will stay activated as long as they remain members of the domain and maintain periodic contact with a domain controller. Activation takes place after the licensing service starts. When this service starts, the computer running Windows 8 or Windows Server 2012 contacts AD DS automatically, receives the activation object, and activates without user intervention.
This document is introduce how to installing and implementing ADBA.
Enjoy！
The System Center Configuration Manager Company Portal app allows users of Windows 8 and Windows 8.1 machines to view and install applications made available to the user by their administrators. The machine must be managed by Microsoft System Center 2012 R2 Configuration Manager, or later, with the agent installed. The app communicates directly with the Configuration Manager on-premise server infrastructure. Note that this contrasts with the Windows Intune Company Portal app (available through the Windows Store and the Download Center) which communicates directly with the Windows Intune service.
You can download System Center Configuration Manager Company Portal app from : http://www.microsoft.com/en-us/download/details.aspx?id=40795
The enclosed document will to show how to install Company Portal app and how to deploy applications throw Company Portal.
More information, please refer the TechNet library : http://technet.microsoft.com/en-us/library/jj822984.aspx
This post will to introduce how to deploy Lync Server 2013 Standard Edition, the whole processes is easy.
More information, you can refer TechNet website:http://technet.microsoft.com/en-us/library/gg398616.aspx
Virtual Machine Manager (VMM) is a management solution for the virtualized datacenter, enabling you to configure and manage your virtualization host, networking, and storage resources in order to create and deploy virtual machines and services to private clouds that you have created. The VMM Self-Service Portal is no longer supported in System Center 2012 SP1. Instead, we recommend that you use System Center 2012 SP1 - App Controller as the self-service portal solution.
This document will to show you how to deploy System Center 2012 SP1 VMM.
This blog post will to show you how to deploy System Center 2012 SP1 Service Manager on Windows Server 2012 environment , including Service Manager , Data Warehouse and Self-service portal .
More details information , please access TechNet website : http://technet.microsoft.com/en-us/library/hh495575.aspx
Please use Adobe reader X or above version to open.
March 6th MSFT released System Center 2012 SP1 Cloud Services Process Pack. System Center Cloud Services Process Pack (CSPP) is Microsoft’s Infrastructure as a Service solution built on the System Center platform. With the System Center Cloud Services Process Pack, enterprises can realize the benefits of Infrastructure as a Service while simultaneously leveraging their existing investments in the Service Manager, Orchestrator, Virtual Machine Manager, and Operations Manager platforms.CSPP is an extension pack built on top of System Center. This release is compatible only with System Center 2012 and 2012 SP1. This release does not contain a new feature set from prior releases.
You can download it from this link : http://www.microsoft.com/en-us/download/details.aspx?id=36497
More details technology information , you can access TechNet library : http://technet.microsoft.com/en-us/library/hh562067.aspx
This document will introduction how to deploy System Center 2012 SP1 CSPP on System Center 2012 SP1 environment.
FIM 2010 is a new version Identity and certificate lifecycle management solution , deployment step is too much .
This document intro how to deploy FIM 2010 core services .
This document is introduction how to deploy System Center Configuration Manager 2012 Beta2 advanced security mode , including how to configure Web certificate and Client certificate steps , like SCCM 2007 Native Mode .
Hope useful to you !
Note : Please use Adobe Reader X or above version to reading.
System Center 2012 Service Manager is very powerful . The fully installation phase is very long and time-consuming .
There are six major parts of a System Center 2012 – Service Manager installation, as described in the following table.
Service Manager management server
Contains the main software part of a Service Manager installation. You can use the Service Manager management server to manage incidents, changes, users, and tasks.
Service Manager database
The database that contains Service Manager configuration items (CI) from the IT Enterprise; work items, such as incidents, change requests, and the configuration for the product itself. This is the Service Manager implementation of a Configuration Management Database (CMDB).
Data warehouse management server
The computer that hosts the server piece of the data warehouse.
Data warehouse databases
Databases that provide long-term storage of the business data that Service Manager generates. These databases are also used for reporting.
Service Manager console
The user interface (UI) piece that is used by both the help desk analyst and the help desk administrator to perform Service Manager functions, such as incidents, changes, and tasks. This part is installed automatically when you deploy a Service Manager management server. In addition, you can manually install the Service Manager console as a stand-alone part on a computer.
Self-Service Portal
A web-based interface into Service Manager.
This document will discription install Service Manager MS \ Data Warehouse \ Self-Service Portal . But have not how to deploying the System Center Cloud Services Process Pack part in this document .
System Center 2012 Orchestrator provides a workflow management solution for the data center. Orchestrator lets you automate the creation, monitoring, and deployment of resources in your environment.
Today , i will share System Center 2012 Orchestrator RC deployment document for you reference .
System Center 2012 will successively release , Now System Center 2012 Virtual Machine Manager is internal released . The RTM Version is 3.0.6005.0
The VMs and Services workspcae :
The Fabric Workspace :
The Self-Service Portal :
More documents you can access TechNet library : http://technet.microsoft.com/en-us/library/gg610610.aspx