Jump to content




    Admin Console not loading and WMI Errors

    LemonEistee
    By LemonEistee,
    Hello,   I have the problem with my SCCM that I cannot open the Administration Console anymore. The last think I have do bevor it don't works anymore was to fix my 0% downloading from Software Center Problem. I have tried these steps from Arthur_Li (because the fix with the .mof files don't work for me): https://social.technet.microsoft.com/Forums/windows/en-US/df00b2e4-3bab-4b46-ad5a-95e82617a039/wmi-errors?forum=winserverNIS Here are the SMSAdmin Logs: [19, PID:1928][10/11/2018 08:50:07] :Transport error; failed to connect, message: 'The SMS Provider reported an error.'\r\nMicrosoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryException\r\nThe SMS Provider reported an error.\r\n   at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryResultsObject.<GetEnumerator>d__74.MoveNext() [19, PID:1928][10/11/2018 08:50:07] :Transport error; failed to connect, message: 'The SMS Provider reported an error.'\r\nMicrosoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryException\r\nThe SMS Provider reported an error.\r\n   at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryResultsObject.<GetEnumerator>d__74.MoveNext()    at Microsoft.ConfigurationManagement.AdminConsole.SmsSiteConnectionNode.GetConnectionManagerInstance(String connectionManagerInstance)\r\nConfigMgr Error Object: instance of __ExtendedStatus
    {
    Operation = "ExecQuery";
    ParameterInfo = "SELECT * FROM SMS_Site WHERE SiteCode = 'PS0'";
    ProviderName = "WinMgmt"; } Error Code: ProviderLoadFailure [19, PID:1928][10/11/2018 08:50:07] :Transport error; failed to connect, message: 'The SMS Provider reported an error.'\r\nMicrosoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryException\r\nThe SMS Provider reported an error.\r\n   at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryResultsObject.<GetEnumerator>d__74.MoveNext()   I have tried to reinstall the console with the AdminConsole.msi but this don't work. Also I have tried to connect with my IP, but also no success. The complete D drive where SCCM is installed, the SMSAdmins Group has "Full control" permissions. At this group are all user where can connected to the server and the server itself.
    All sms services are running.   One think I found out is that my wmi maybe don't work right. At another Topic (https://www.windows-noob.com/forums/topic/10298-applications-suddenly-wont-deploy-hung-stuck-at-0-downloading/) they tried "Run the query select * from sms_sci_component where componentname=SMS_DISTRIBUTION_MANAGER" to fix the wmi problem, but if I try this query I get the following error: Number: 0x80041017
    Facility: WMI
    Description: Invalid query   Could it be that this query is only for 2012? At the wmiprov.log I get this error by trying to open the Console from SCCM: (Wed Oct 10 10:16:42 2018.780762406) : WDM call returned error: 5   The WMIDIAG Log is attach below     WMIDIAG-V2.2_2K12R2.SRV.RTM.64_SRV-SCCM_2018.10.12_09.52.41-REPORT.TXT

    Surface Pro 4 PXE

    Ranighte
    By Ranighte,
    Hello Guys,   We have the Problem that our Surface wont boot from Network. The last Message we get is "nbp file downloaded successfully" When i use the same TS an USB-Stick it works fine.. a normal HP Workstation over Legacy installation works fine..   Any ideas? best Regards

    ** Solved ** OS Task fails at applying driver pack

    nhottinger
    By nhottinger,
    We just upgraded SCCM to 1806 including the hotfix.  Everything seemed to be ok.  I updated the ADK as well so I could install the new version of Windows 10.  I'm currently having trouble with that as well, but that's a different post.  Any idea why my windows 7 images fail at the driver package now that I upgraded SCCM?  Nothing else has changed.  Logs don't show anything of use that I can find. ** Update ** For all my windows 7 driver packages, I had to check "Install driver package via running DISM with recurse option".  Wish that was in some kind of documentation I had read ahead of time.

    ** Solved ** Windows 10 1809 Task Sequence Fails

    nhottinger
    By nhottinger,
    We just downloaded Win 10 1809 and started to attempt to roll it out (testing) but every time the task sequence fails with unknown errors (0x80004005) at the Apply Operating System Step.  I did some searching and it sounded like the version of SCCM we were on was not compatible so yesterday I upgraded to Config Mgr 1806 and also the 1806 hotfix.  Thought that would resolve the issue but it doesn't.  I copied the original task sequence for 1803 that was working and replaced the OS thinking that would be the easiest way to do it.  Any ideas what might we wrong with the 1809 version?   *Edit, my Network Admin downloaded the ARM version which will not work on our pc's.  Now that 1809 is paused, I'm not going to worry about it anymore.  Until the next version...

    Peer Caching, unable to download from peer

    Siroj
    By Siroj,
    Our Setup:
    - SCCM 1806 on Server 2016
    - Clients are running Windows 10 1709 (about 25000 clients)
    - Clients running corresponding SCCM client v5.00.8692.1008 We are trying to utilize Peer Caching but are unsuccessful in getting it to work. After a number of tries to connect to a peer, it uses the DP as last resort and successfully downloads the data (but not from a peer cache source). We verified that firewall ports (8003, 8004) are opened at the source peer. We re-entered the NAA account info and successfully verified. For testing purposes we also granted full access rights to CCMCACHE folder to the NAA account In SMSTS.log we see that the client has located a peer, tried to connect but failed. Some possible relevant LOG entries: Does anyone have any idea where to look next?

    Windows 10 Enterprise, version 1809 (updated Sept ’18) is released, and Windows Server 2019 is Generally Available !

    anyweb
    By anyweb,
    It’s finally released, the long awaited Windows 10 Enterprise, version 1809 (otherwise known as The Windows 10 October 2018 Update) is available for download on Microsoft’s MSDN site, also to note, the Windows 10 Enterprise LTSC 2019 version is released. There is a corresponding download for Windows 10 Enterprise version 1809 also on VLSC however it’s for ARM Architecture only (64bit), so probably not of much use to you and me… This release is packed with lots of interesting new features detailed here. Also released is the Windows ADK version 1809 here. And if that wasn’t enough, Windows Server 2019 is finally Generally Available (on MSDN), time to start downloading ! For more info about the new release, please read this: https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/What-s-new-for-IT-pros-in-Windows-10-version-1809/ba-p/263909 cheers niall

    Capture Failing - Initialising Configuration Manager Client - Smstslog = Class Not Registered 0x80040154

    Robbie Wallis
    By Robbie Wallis,
    Hello, We have an issue that has introduced itself into what was a working system so I'm guessing it is update related We are running the latest version with latest updates of SCCM with the latest ADK and capture media After the build process a machine will capture. If you make a single change i.e. installing software the capture will fail at initialising configuration manager client - 0x80040154. SMSTS.log shows the same error code against "Class not registered" This is a process that was working fine. We make the same changes every time but this time round nothing wants to capture Just noticed prior to this there is "GetMPInformation() failed 0x80040154" Any ideas? Robbie

    IPv6

    sysadmin101
    By sysadmin101,
    Hi Folks, Hope all is well! I'm trying to enable IPv6 PXE boot on my DP, but the checkbox simply isn't there. I'm on 1806, and I've already selected 'enable PXE responder without WDS'. My DP does not have an IPV6 address assigned at the moment (although IPv6 is certainly enabled at the NIC/OS) - does that need to be configured first?   p.s. my clients will be PXE booting from a different subnet. Currently I use IP helpers to point the clients to the PXE server. The IP helpers are IPv4; I assume I will need to create IPv6 helpers as well?
    Thanks!

Portal by DevFuse · Based on IP.Board Portal by IPS
×