%3CLINGO-SUB%20id%3D%22lingo-sub-377273%22%20slang%3D%22en-US%22%3ENew%20Year....%20New%20Plans%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-377273%22%20slang%3D%22en-US%22%3E%0A%20%26lt%3Bmeta%20http-equiv%3D%22Content-Type%22%20content%3D%22text%2Fhtml%3B%20charset%3DUTF-8%22%20%2F%26gt%3B%3CSTRONG%3EFirst%20published%20on%20TECHNET%20on%20Dec%2020%2C%202018%20%3C%2FSTRONG%3E%20%3CBR%20%2F%3E%20As%202018%20wraps%20up%20we%20are%20starting%20to%20set%20our%20sights%20on%20what%20the%20future%20of%20our%20System%20Center%20Configuration%20Manager%20(ConfigMgr%2FSCCM)%20infrastructure%20could%20bring.%26nbsp%3B%20Our%20move%20to%20Azure%20was%20focused%20on%20learning%20and%20proving%20what%20could%20be%20done.%26nbsp%3B%20Now%20our%20thoughts%20turn%20toward%20cost%20reduction.%26nbsp%3B%20Here%20are%20a%20few%20things%20on%20our%20wish%20list%20for%20the%20coming%20year%3A%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%3CUL%3E%3CBR%20%2F%3E%3CLI%3E%3CSTRONG%3EScale%20back%20virtual%20machine%20sizes%20%3C%2FSTRONG%3E%20%E2%80%93%20We%20built%20machines%20with%20a%20bit%20of%20caution%20in%20our%20planning.%26nbsp%3B%20Now%20that%20our%20migration%20is%20complete%20and%20we%20have%20a%20few%20months%20of%20real%20running%20numbers%20we%20want%20to%20scale%20down%20our%20VM%20sizes%20in%20a%20few%20spots%20and%20save%20some%20money%E2%80%A6%2C%20A%20nice%20ability%20that%20Azure%20gives%20us.%3C%2FLI%3E%3CBR%20%2F%3E%3CLI%3E%3CSTRONG%3ECloud%20Management%20Gateway%20redeployment%20%3C%2FSTRONG%3E%20%E2%80%93%20We%20were%20early%20adopters%20of%20CMG%2C%20which%20were%20built%20on%20Azure%20Classic%20VMs.%26nbsp%3B%20We%20also%20had%20separate%20cloud%20distribution%20points%20(DP).%26nbsp%3B%20With%20the%20role%20combination%20in%20the%20new%20ARM%20based%20CMG%20we%20are%20looking%20to%20replace%20two%20web%20services%20with%20one%20and%20simplify%20the%20management%20of%20it%20all%20as%20well.%3C%2FLI%3E%3CBR%20%2F%3E%3CLI%3E%3CSTRONG%3EDynamic%20site%20systems%20%3C%2FSTRONG%3E%20%E2%80%93%20Azure%20has%20the%20nice%20ability%20to%20do%20auto%20scale-up%20and%20down%20of%20web%20services.%26nbsp%3B%20We%20want%20to%20investigate%20doing%20this%20for%20management%20points%20(MP)%2C%20DP%20and%20such%20to%20see%20if%20there%20is%20a%20way%20we%20can%20dynamically%20scale%20up%20and%20down%20our%20site%20systems%20based%20on%20load.%26nbsp%3B%20This%20is%20not%20going%20to%20be%20a%20simple%20task%20but%20we%20hope%20to%20get%20some%20help%20from%20the%20developers%20to%20make%20it%20more%20feasible%20and%20then%20flush%20out%20the%20rest%20of%20the%20scenario%20with%20some%20custom%20scripts.%3C%2FLI%3E%3CBR%20%2F%3E%3CLI%3E%3CSTRONG%3ECMG%2FMP%20re-design%20%3C%2FSTRONG%3E%20%E2%80%93%20When%20we%20stood%20up%20our%20initial%20CMG%20we%20had%20reasons%20to%20have%20them%20map%20back%20to%20specific%2C%20dedicated%2C%20MP.%26nbsp%3B%20Through%20bug%20fixes%20and%20design%20change%20requests%20we%20no%20longer%20have%20that%20need%20so%20we%20want%20to%20remove%20that%20extra%20MP%20and%20re-point%20CMG%20to%20use%20the%20existing%20MP%20architecture.%3C%2FLI%3E%3CBR%20%2F%3E%3CLI%3E%3CSTRONG%3ERemove%20internet%20load%20balancers%20(ILB)%20%3C%2FSTRONG%3E%20%E2%80%93%20Due%20to%20legacy%20design%20and%20needs%20we%20have%2Fhad%20windows%20software%20update%20servers%20(WSUS)%20behind%20an%20HLB%2FILB.%26nbsp%3B%20As%20we%20revisit%20those%20needs%20we%20hope%20to%20eliminate%20the%20need%20and%20be%20able%20to%20get%20back%20to%20the%20standard%20WSUS%20list%20functionality%20built-in%20to%20the%20ConfigMgr%20product.%3C%2FLI%3E%3CBR%20%2F%3E%3CLI%3E%3CSTRONG%3ESite%20consolidation%20%3C%2FSTRONG%3E%20%E2%80%93%20Our%20client%20support%20needs%20are%20shifting.%26nbsp%3B%20With%20more%20devices%20doing%20azure%20active%20directory%20(AAD)%20enrollment%20and%20Co-Management%20loads%20shifting%20to%20Intune%20it%20is%20worth%20investigation%20and%20discussion%20with%20the%20ConfigMgr%20development%20team%20about%20the%20scale%20numbers%20for%20a%20site%20and%20what%20we%20can%20possibly%20do%20to%20combine%20our%20primaries%20and%20reduce%20costs%20in%20that%20method%20as%20well.%3C%2FLI%3E%3CBR%20%2F%3E%3CLI%3E%3CSTRONG%3ERemove%20unnecessary%20site%20systems%20%3C%2FSTRONG%3E%20%E2%80%93%20With%20our%20peer%20cache%20success%2C%20the%20number%20of%20DPs%20can%20reduce%20(perhaps%20to%20only%201%20per%20site%2C%20with%20dynamic%20scale%20up%20when%20needed).%20New%20MP%20functionality%20lets%20us%20start%20the%20removal%20of%20app%20catalogs.%26nbsp%3B%20MP%20scale%20numbers%20can%20be%20re-assessed%20to%20possible%20drop%20one%20or%20two%20MP%20per%20site.%3C%2FLI%3E%3CBR%20%2F%3E%3CLI%3E%3CSTRONG%3ECo-Management%20workload%20transition%20%3C%2FSTRONG%3E%20-%20We%20are%20going%20to%20continue%20to%20test%20and%20transition%20more%20workloads%20to%20Intune%20including%20things%20such%20things%20as%20windows%20update%2C%20endpoint%20protection%2C%20and%20device%20configuration.%3C%2FLI%3E%3CBR%20%2F%3E%3C%2FUL%3E%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20As%20we%20know%2C%20we%20don%E2%80%99t%20always%20get%20all%20our%20presents%20under%20the%20tree.%26nbsp%3B%20Hopefully%20we%20will%20get%20most%20of%20them.%26nbsp%3B%20Happy%20holidays%20to%20you%20all!%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-377273%22%20slang%3D%22en-US%22%3EFirst%20published%20on%20TECHNET%20on%20Dec%2020%2C%202018%20As%202018%20wraps%20up%20we%20are%20starting%20to%20set%20our%20sights%20on%20what%20the%20future%20of%20our%20System%20Center%20Configuration%20Manager%20(ConfigMgr%2FSCCM)%20infrastructure%20could%20bring.%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-377273%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3Emsit%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESCCM%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Esccm%20lift%20and%20shift%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESystem%20Center%20Configuration%20Manager%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Ewindows%20intune%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Microsoft
First published on TECHNET on Dec 20, 2018
As 2018 wraps up we are starting to set our sights on what the future of our System Center Configuration Manager (ConfigMgr/SCCM) infrastructure could bring.  Our move to Azure was focused on learning and proving what could be done.  Now our thoughts turn toward cost reduction.  Here are a few things on our wish list for the coming year:



  • Scale back virtual machine sizes – We built machines with a bit of caution in our planning.  Now that our migration is complete and we have a few months of real running numbers we want to scale down our VM sizes in a few spots and save some money…, A nice ability that Azure gives us.

  • Cloud Management Gateway redeployment – We were early adopters of CMG, which were built on Azure Classic VMs.  We also had separate cloud distribution points (DP).  With the role combination in the new ARM based CMG we are looking to replace two web services with one and simplify the management of it all as well.

  • Dynamic site systems – Azure has the nice ability to do auto scale-up and down of web services.  We want to investigate doing this for management points (MP), DP and such to see if there is a way we can dynamically scale up and down our site systems based on load.  This is not going to be a simple task but we hope to get some help from the developers to make it more feasible and then flush out the rest of the scenario with some custom scripts.

  • CMG/MP re-design – When we stood up our initial CMG we had reasons to have them map back to specific, dedicated, MP.  Through bug fixes and design change requests we no longer have that need so we want to remove that extra MP and re-point CMG to use the existing MP architecture.

  • Remove internet load balancers (ILB) – Due to legacy design and needs we have/had windows software update servers (WSUS) behind an HLB/ILB.  As we revisit those needs we hope to eliminate the need and be able to get back to the standard WSUS list functionality built-in to the ConfigMgr product.

  • Site consolidation – Our client support needs are shifting.  With more devices doing azure active directory (AAD) enrollment and Co-Management loads shifting to Intune it is worth investigation and discussion with the ConfigMgr development team about the scale numbers for a site and what we can possibly do to combine our primaries and reduce costs in that method as well.

  • Remove unnecessary site systems – With our peer cache success, the number of DPs can reduce (perhaps to only 1 per site, with dynamic scale up when needed). New MP functionality lets us start the removal of app catalogs.  MP scale numbers can be re-assessed to possible drop one or two MP per site.

  • Co-Management workload transition - We are going to continue to test and transition more workloads to Intune including things such things as windows update, endpoint protection, and device configuration.




As we know, we don’t always get all our presents under the tree.  Hopefully we will get most of them.  Happy holidays to you all!