Lot of interesting news are coming out from Microsoft Ignite 2015 and from social networking Sites(mainly from Twitter).I have been actively monitoring the tags with #msignite and #Configmgr .Some of the interesting facts about Configuration manager products are:
1. Microsoft has made configuration manager and Endpoint Protection Technical Preview (it will be next Configmgr Version 2016) available for testing http://www.microsoft.com/en-us/evalcenter/evaluate-system-center-configuration-manager-and-endpoint-protection-technical-preview ,for technical preview documentation refer https://technet.microsoft.com/library/dn965439.aspx
2. Service Pack will be released next week for Configuration Manager 2012 and 2012 R2.
3.Support for Windows 10 (No OSD support) using Configuration manager 2007
4.New service pack (Configmgr 2012) supports up to 600K devices and primary/standalone to 150K which is awesome .No more CAS until you have bigger client supports more than 150K Devices.
5.In-place upgrade available from Configmgr 2012 to Configuration manager technical preview (Configmgr Vnext ).
what is more interesting (capabilities) in Configuration Manager Vnext (SCCM 2016) Technical preview?
Requirements:
- It comes with 60 days validity and becomes inactive after that.
- It support only English Language
- Only standalone Primary site can be installed ,no CAS, Primary and secondary sites
- Support only SQL server 2012 R2 and SQL server 2014. There is no requirement or restriction for the cumulative update version of SQL
- Support max of 10 clients from Widows 7 to Windows 10 (you cannot have more than 10 client to test using Technical preview)
- There is no support for upgrade to this preview build.
- There is no support for upgrade to a later build from this preview build.
- Only the following install flags (switches) are supported:
- /silent
- /testdbupgrade
- There is no support for migration to or from this preview build.
Capabilities:
- Windows 10 in-place upgrade
- Mobile Application Management
- Data protection for mobile devices
- Preferred management points
- On-premises mobile device management (MDM)
- Support for Microsoft Azure virtual machines
- Client deployment status in console monitoring
Download Configuration manager Technical preview,install and have fun with your lab.
Direct download link (SC_Configmgr_SCEP_SCTP.exe) without registration for Configuration manager technical preview is here
Hi
We have SCCM 2012 R2 SP1 CU3 infrastructure and are planning to upgrade to SCCM 2016 vNext in next 1-2 months. Below are our SCCM detailed infrastructure.
OS Platform - Windows Server 2008 R2 SP1
1 CAS
2 Primary Site Servers for Servers (Intranet Only) and Workstation Management (Internet and Intranet)
10000+ Workstations
800+ Server
One of the main objective of the migration is to facilitate Windows 10 upgrades across the organization. Since we are on Windows 2008 R2 Sp1 platform, we are using WSUS 3.0 and as per below article there is a dependency for Windows 10 upgrade as it requires WSUS 4.0 for which we need to perform OS upgrade.
http://blogs.technet.com/b/wsus/archive/2015/12/04/important-update-for-wsus-4-0-kb-3095113.aspx
As per the supported configuration for Configuration Manager TechNet article, Configuration Manager does not support "Any version of Windows Server 2008 R2 to any version of Windows Server 2012 or later." This is a challenge.
We have 2 options-
Plan A- In Place Upgrade
Build separate Windows 2012 R2 infrastructure for Site Servers (1 CAS and 2 Primary Site Server), Install SCCM with site recovery option with proper backups. I need the complete documentation here.
Plan B- Side by Side upgrade
Build a clean SCCM infrastructure on Windows Server 2012 platform with a different Site Code in parallel with current SCCM infrastructure and migrate all clients phase by phase.
Please suggest which is the best possible options for our environment.
Thanks much.
regards
Guru