Data Protection Manager 2012 R2 Update Rollup 11 Çıktı

System Center ailesinin içerisinde yedekleme ürünü olarak yer alan Data Protection Manager 2012 R2 için Update Rollup 11 KB3162908 güncelleme paketi yayınlandı.

Güncellemeyi indirmek için : http://catalog.update.microsoft.com/v7/site/search.aspx?q=3162908

Güncellemenin en büyük özelliği artık DPM ile VmWare üzerinde çalışan sanal sunucularda yedeklenebilecek.


Devamını Oku…

System Center Ağustos 2016 Bülten

Configuration Manager (SCCM)

Intune / Enterprise Mobility

Operations Manager (SCOM)

Operations Management Suite (OMS)

System Center Service Manager

Virtualization

Automation

Data Protection Manager – DPM Port Number

Protocol

Details

TCP – 135 DCOM is used by the DPM server and the DPM protection agent to issue commands and responses. DPM issues commands to the protection agent by invoking DCOM calls on the agent. The protection agent responds by invoking DCOM calls on the DPM server.

TCP port 135 is the DCE endpoint resolution point that is used by DCOM. By default, DCOM assigns ports dynamically from the TCP port range of 1024 through 65535.

TCP – 5718 – 5719 The DPM data channel is based on TCP. Both DPM and the protected computer initiate connections to enable DPM operations such as synchronization and recovery. DPM communicates with the agent coordinator on port 5718 and with the protection agent on port 5719.
TCP – 6075 Enabled when you create a protection group to help protect client computers. Required for end-user recovery.

An exception in Windows Firewall (DPMAM_WCF_Service) is created for the program Amscvhost.exe when you enable Central Console for DPM in Operations Manager.

UDP – 53 Used for host name resolution between DPM and the domain controller, and between the protected computer and the domain controller.
TCP ve UDP 88 Used for authentication of the connection endpoint between DPM and the domain controller, and between the protected computer and the domain controller.
TCP ve UDP 389 Used for queries between DPM and the domain controller.
TCP – 139 – 445

UDP – 137 – 138

Used for miscellaneous operations between DPM and the protected computer, between DPM and the domain controller, and between the protected computer and the domain controller. Used for DPM functions for Server Message Block (SMB) when it is directly hosted on TCP/IP.

Kaynak : https://technet.microsoft.com/en-us/library/hh757794(v=sc.12).aspx

System Center Data Protection Manager – DPM Build Numbers

System Center Data Protection Manager 2016

Build Number Description
4.3.1012.0 SCDPM 2016 Technical Preview
4.3.1071.0 SCDPM 2016 Technical Preview 2
4.3.1043.0 SCDPM 2016 Technical Preview 3
5.0.46.0 SCDPM 2016 Technical Preview 4
5.0.58.0 SCDPM 2016 Technical Preview 5

System Center Data Protection Manager 2012 R2

Build Number KB Release Date Description
4.2.1205.0 SCDPM 2012 R2 RTM
4.2.1217.0 KB2904687 SCDPM 2012 R2 Rollup Update 1
4.2.1226.0 KB2958100 SCDPM 2012 R2 Rollup Update 2
4.2.1235.0 KB2963543 SCDPM 2012 R2 Rollup Update 2 (re-released)
4.2.1254.0 KB2966014 SCDPM 2012 R2 Rollup Update 3
4.2.1273.0 KB3009516 2014 October 28 SCDPM 2012 R2 Rollup Update 4
4.2.1292.0 KB3021791 2015 February 10 SCDPM 2012 R2 Rollup Update 5
4.2.1297.0 KB3040326 2015 March 5 SCDPM 2012 R2 HOTFIX for Rollup Update 5
4.2.1312.0 KB3030574 2015 April 28 SCDPM 2012 R2 Rollup Update 6
4.2.1338.0 KB3065246 2015 July 28 SCDPM 2012 R2 Rollup Update 7
4.2.1373.0 KB3086084 2015 October 27 SCDPM 2012 R2 Rollup Update 8
4.2.1417.0 KB3112306 2016 January 26 SCDPM 2012 R2 Rollup Update 9
4.2.1473.0 KB3143871 2016 May 24 SCDPM 2012 R2 Rollup Update 10
4.2.1553.0 KB3162908  2016 August 29 SCDPM 2012 R2 Rollup Update 11

System Center Data Protection Manager 2012 SP1

Build Number KB Description
4.1.3313.0 SCDPM 2012 SP1
4.1.3322.0 KB2785682 SCDPM 2012 SP1 Rollup Update 1
4.1.3333.0 KB2785682 SCDPM 2012 SP1 Rollup Update 1 v2
4.1.3408.0 KB2802159 SCDPM 2012 SP1 Rollup Update 2
4.1.3415.0 KB2836751 SCDPM 2012 SP1 Rollup Update 3
4.1.3417.0 KB2836751 SCDPM 2012 SP1 Rollup Update 3 v2
4.1.3419.0 KB2886362 SCDPM 2012 SP1 Rollup Update 3.6 (Fix)
4.1.3426.0 KB2904723 SCDPM 2012 SP1 Rollup Update 5
4.1.3441.0 KB2958098 SCDPM 2012 SP1 Rollup Update 6
4.1.3453.0 KB2966012 SCDPM 2012 SP1 Rollup Update 7
4.1.3465.0 KB2991995 SCDPM 2012 SP1 Rollup Update 8

System Center Data Protection Manager 2012

Build Number KB Description
4.0.1908.0 SCDPM 2012 RTM
4.0.1915.0 KB2706783 SCDPM 2012 Rollup Update 2
4.0.1920.0 KB2756127 SCDPM 2012 Rollup Update 3

System Center Data Protection Manager 2010

Build Number KB Description
3.0.7336.0 SCDPM 2010 Beta
3.0.7475.0 SCDPM 2010 CTP3
3.0.7558.0 SCDPM 2010 RC
3.0.7696.0 SCDPM 2010 RTM
3.0.7706.0 KB2250444 SCDPM 2010 QFE1
3.0.7707.0 KB2465832 SCDPM 2010 QFE2
3.0.8158.0 KB2581742 SCDPM 2010 QFE3
3.0.8180.0 KB2615782 SCDPM 2010 QFE4
3.0.8185.0 N/A SCDPM 2010 QFE5
3.0.8193.0 KB2718797 SCDPM 2010 QFE6
3.0.8195.0 KB2751231 SCDPM 2010 QFE7

System Center Data Protection Manager 2007

Build Number KB Description
2.0.5820.0 SCDPM 2007 RTM
2.0.8107.0 KB949779 SCDPM 2007 Feature Pack
2.0.8793.0 KB959605 SCDPM 2007 SP1

One of the update processes returned error code 14101

Hyper-V integration servis 6.3.9600.18339 güncellemesini yapmak istediğinizde aşağıdaki hatayı alabilirsiniz.

Çözüm 1
Hyper-V Host üzerine aşağıdaki güncellemeyi yükleyin, sunucuyu reboot edin daha sonra integration servis cd’sini sanal sunucuya takarak güncellemeyi yapın.
https://support.microsoft.com/en-us/kb/3172614

Çözüm 2
Aşağıdaki path’de bulunan dosyası silin ve integration servis güncellemesini yüklemeyi tekrar deneyin.
C:\Windows\Winsxs\Manifests\amd64_wnetvsc.inf_31bf3856ad364e35_6.3.9600.18339_none_48176f52a345f953.manifest

Dosyayı silmek için Owner’lığı alarak dosya üzerinde full control iznine sahip olmanı gerekli. Bu işlemi manual olarak yapabilirsiniz. CMD’den hızlıca yapmak için aşağıdaki komutları kullanabilirsiniz.

  • takeown /F “C:\Windows\Winsxs\Manifests\amd64_wnetvsc.inf_31bf3856ad364e35_6.3.9600.18339_none_48176f52a345f953.manifest”
  • cacls “C:\Windows\Winsxs\Manifests\amd64_wnetvsc.inf_31bf3856ad364e35_6.3.9600.18339_none_48176f52a345f953.manifest” /e /p Everyone:f
  • icacls “C:\Windows\Winsxs\Manifests\amd64_wnetvsc.inf_31bf3856ad364e35_6.3.9600.18339_none_48176f52a345f953.manifest” /setowner “Everyone” /T /C
  • del /F /Q C:\Windows\Winsxs\Manifests\amd64_wnetvsc.inf_31bf3856ad364e35_6.3.9600.18339_none_48176f52a345f953.manifest

Çözüm 3
Sanal sunucu üzerinden KB3161606 güncellemesini kaldırın, sistemi reboot edin ve integration servis güncellemesini yüklemeyi tekrar deneyin.

System Center Temmuz 2016 Bülten

Headlines

System Center 2016 to launch in September

We are pleased to announce that Microsoft System Center 2016 will be launched at the Microsoft Ignite conference in late September. Highlights of System Center 2016 include:

  • Support for new Windows Server 2016 technologies, including lifecycle management for Nano server-based hosts and virtual machines, Storage Spaces Direct, and shielded virtual machines
  • Performance and usability improvements, including all the update rollups since System Center 2012 R2, improved UNIX and Linux monitoring, and ability to tune management packs and alerts
  • Native integrations with Microsoft Operations Management Suite to give you expanded analytics, data correlation, orchestration, archival, and hybrid management capabilities

The Windows Server 2016 Application Platform – Nano Server, Containers and DevOps

There has been a lot of press on Nano Server and Containers as new technologies coming in Windows Server 2016. In this blog post we’ll discuss how these two technologies are core pieces of the Windows Server 2016 developer/DevOps solution, discuss the full inbox stack, and provide links to additional resources to get you started. In addition to this post, at Build 2016, Taylor Brown and Andrew Mason presented a session with demos on this topic. The recording is available on Channel9.

Gartner names Microsoft as a leader in DRaaS

With Operations Management Suite and Azure Site Recovery, organizations can achieve low recovery point objective (RPO) and recovery time objective (RTO) targets for every major IT system, without the hassle or the cost of a secondary data center. With this disaster recovery as a service (DRaaS) offering designed for the needs of enterprises, customers can tap into effectively unlimited capacity at a moment’s notice. Devamını Oku…