Skip to main content

Posts

Showing posts from January, 2014

system center universe 2014

if you are in the system center space, you know about SCU from the past successful events… and most likely know about the 2014 date. it all happens 1/30/2014. for those of you in the atlanta area, ATLSMUG is hosting a viewing party if you’d like to come watch it with us. get all the details at http://systemcenteruniverse.com . while you’re there, check out the oppressive theme music for sc-uminator . Atlanta, GA Microsoft Office 1125 Sanctuary Pkwy Alpharetta, GA 30009 Register don’t worry. if you can’t make it in person, you’ll be able to watch it online. if you come out though, we’ll feed you breakfast, lunch, and snacks. here’s the agenda (CENTRAL TIME) of what you can expect to see: 7:00am - 8:00am Registration 8:00am - 8:10am Welcome - Your Emcee, Cameron Fuller, MVP 8:10am - 8:55am Become the Hero of the Day - Master ConfigMgr 2012 R2 with a Limited Budget and Free Community Tools Presented by Kent Agerlund No doubt that Configuration Manager 2012 R2 is a very powerful pro

sccm: ccmmigratepolicysettingsinit returns code 1603 during pull dp installation

as i sat down to write this, I realized a fellow mvp, alex zhuravlev, wrote about a very similar thing which is corrected by the same fix. it’s posted here if you’d like to read it: http://social.technet.microsoft.com/wiki/contents/articles/4709.configmgr-2012-beta2-site-component-manager-failed-to-install-this-component-because-the-microsoft-installer-file-for-this-component-mp-msi-could-not-install.aspx recently, we started deploying pull DPs out to our regional locations. one of my engineers indicated that we were having issues where the DPs appeared to be in a waiting for content state. we narrowed the issue down to an error that popped up in the pulldp_install.log file. the end of the installation exits in 1603, which i’m sure you know is a very vague error. going backward in the log file, we spotted an where the originating 1603 was logged. here are the log lines: 1: Getting settings from WMI and storing in <Program Files>\SMS_CCM\polmig.mof 2: CustomAction Ccm