Search the Community

Hi All I have now built 2 labs over Christmas period, both labs were 4 box solutions which work perfectly on 1606 from baseline media. Got them all working. deployments of software, osd patches everything I needed. Initial lab was on server 2012 r2 and sql 2012 - all service packed and patched up. Worked fine on 1606 - upgraded to 1610 and I get high CPU on smsexec on the box which functions as a DP (role) 2012 r2 lab Domain controller (test.local) DNS DHCP AD PRI - ADK 10.1.14393.0 DP (dp,pxe,fsp,scp,sup) MP (mp,appcatalogue,reporting services) SQL 2012 Didn't take snapshots so couldn't go back. The funny thing is I have high CPU but it still works fine on 1610 - all functionality is still working... Have recently (today) applied the hotfix for 1610 from servicing, and this has not cured the high cpu on the dp. So - I read the fantastic guide on building with server 2016, sql 2016 guide and built a second lab using all 2016 products. 2016 lab Domain controller (lab.local) dns, DHCP, AD PRI - ADK 10.1.14393.0 DP (dp,pxe,fsp,scp,sup) MP (mp,appcatalogue,reporting services) SQL 2016 Again this worked fine on 1606, everything doing what it should, osd, patching, deploy software. Then took this 2016 lab from 1606 to 1610 and again getting high cpu on my DP. I have 2 labs, both on 1610, both working, but the high cpu on my dp is present on both... Is this a known issue, or part of the 1610 additional functionality that I will admit I am unaware of ? If I add another CPU to the DP, then 1 cpu goes 50% usage - this is consistent on both labs. Any information or thoughts on where to look appreciated. Regards, Wazzie