Jump to content


Search the Community

Showing results for tags 'SMSEXEC'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Cloud
    • Azure
    • Microsoft Intune
    • Office 365
    • Windows 365
  • General Stuff
    • General Chat
    • Events
    • Site News
    • Windows News
    • Suggestion box
    • Jobs
  • MDT, SMS, SCCM, Current Branch &Technical Preview
    • How do I ?
    • Microsoft Deployment Toolkit (MDT)
    • Official Forum Supporters
    • SMS 2003
    • Configuration Manager 2007
    • Configuration Manager 2012
    • System Center Configuration Manager (Current Branch)
    • Packaging
    • scripting
    • Endpoint Protection
  • Windows Client
    • how do I ?
    • Windows 10
    • Windows 8
    • Windows 7
    • Windows Vista
    • Windows XP
    • windows screenshots
  • Windows Server
    • Active Directory
    • Microsoft SQL Server
    • System Center Operations Manager
    • KMS
    • Windows Deployment Services
    • NAP
    • Failover Clustering
    • PKI
    • Windows Server 2008
    • Windows Server 2012
    • Windows Server 2016
    • Windows Server 2019
    • Hyper V
    • Exchange
    • IIS/apache/web server
    • System Center Data Protection Manager
    • System Center Service Manager
    • System Center App Controller
    • System Center Virtual Machine Manager
    • System Center Orchestrator
    • Lync
    • Application Virtualization
    • Sharepoint
    • WSUS

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 1 result

  1. 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
×
×
  • Create New...