Leaderboard

Okay, I think you may be onto something. I ran psexec -i -s Powershell.exe , then executed the script manually. All it did was write the txt file and the apps are still there.

Do you have software inventory set to inventory .dll files and to not exclude c:\windows? If so, then the collection would look like this: select SMS_R_System.ResourceId, SMS_R_System.ResourceType, SMS_R_System.Name, SMS_R_System.SMSUniqueIdentifier, SMS_R_System.ResourceDomainORWorkgroup, SMS_R_System.Client from SMS_R_System inner join SMS_G_System_SoftwareFile on SMS_G_System_SoftwareFile.ResourceID = SMS_R_System.ResourceId where SMS_G_System_SoftwareFile.FilePath = "C:\\Windows\\System\\" and SMS_G_System_SoftwareFile.FileName = "nlwnsck.dll" If inventory is set correctly and the collection still doesn't populate, try this instead: select SMS_R_System.ResourceId, SMS_R_System.ResourceType, SMS_R_System.Name, SMS_R_System.SMSUniqueIdentifier, SMS_R_System.ResourceDomainORWorkgroup, SMS_R_System.Client from SMS_R_System inner join SMS_G_System_SoftwareFile on SMS_G_System_SoftwareFile.ResourceID = SMS_R_System.ResourceId where SMS_G_System_SoftwareFile.FilePath like "%C:\\Windows\\System\\%" and SMS_G_System_SoftwareFile.FileName = "nlwnsck.dll"

Mate you rule. Thanks for all the help

I found the issue - minimal rights in C:\scripts. I gave appropriate rights and everything ran fine. Not really sure why rights were so limited in the first place but glad it's now working.

Hi Experts, I am currently designing a Current Branch implementation for a customer who continues to ask for a Microsoft best practice evidence/ documentation. From whatever I have gathered over my past years of experience, i have never really come across a single "best practice rulebook" as one size can never fit all. In any case, could you guys direct me to any such guide which has design decisions/ used cases documented? other than these https://docs.microsoft.com/en-us/sccm/core/plan-design/configs/supported-configurations https://docs.microsoft.com/en-us/sccm/core/plan-design/hierarchy/design-a-hierarchy-of-sites Meanwhile, just to get an idea i am planning an implementation for ~ 7K clients and below is what I have proposed - Single Primary at one of the Datacentre ( 8 Core, 48GB RAM) - Management server holding client facing roles in another Datacentre (4 Core, 32GB RAM) - Dedicated server for SQL (I was all for co-hosting the SQL on the same server as the primary but due to reasons more political in nature had to go with a dedicated SQL server) (4 Core, 16GB RAM) - 2x Secondary sites at remote sites (4 Core, 16GB RAM) - Distribution points (across various sites spread across the globe) - No CAS ( Future expansion possible) Let me know what you think, thanks in advance

+1 host SQL on the primary, you're in for a load of headaches hosting it remotely, stick to the idea that you need to reduce points of failure. as if you need a +1 when anyweb comments (you shouldn't!)

Well that was it! Wow i have been battling this for weeks, Not sure how i missed that! Thank you TrialandError so much for your wisdom! Once again Windows-Noob.com saves the day!!!!! Thanks again guys! I am curious though, what does the NAA have to do with f8 working to get the command prompt working as well?

Have you defined the network access account? I've seen that error at applying the OS phase because my NAC didn't have the correct privileges. You have multiple issues going on so can you give some more info about your environment? You said it's a new 1702 install but what OS are you deploying? Is MDT integrated? Are you pxe booting or using media? Will F8 bring up the cmd window in winpe before you start the task sequence?

First off, whomever created the script to install SQL... THANK YOU! THANK YOU! THANK YOU! Second, is there any way to modify that script to separate the SQL Data, SQL Logs, SQL backup, and SQL temp to a different drive? C-OSDrive D-ProgramFiles E-SQLData F-SQLLogs G-SQLBackups T-SQLTemp Thank you in advance for any help!

Hi Grudd, I found the solution to my problem over on my post on the SCCM Subreddit page!: The logs didn't show any issues anyway :-( Thanks to Padgo I found one entry in the x64 area that was the culprit! So I deleted it and now everything works! What is strange about this is we have the most current 1702 Hotfix Rollup (KB4019926) applied which is supposed to fixed this issue... I'm doing some more investigation and testing to see if the issue reoccurs. To fix it, I had to run a couple of SQL queries to find a stuck record in the ConfigMrg database and then delete it. In the meantime, here are the screenshots and steps I followed: Disclaimer: Cation should always be exercised when editing the SCCM/ConfigMrg database directly and you should always have a working backup regardless of these steps. I am not responsible for any damage that may caused when doing these steps! Finding the ID's of the Unknown Computers (x86 & x64): (You need to copy value from the SMS_Unique_Identifier0 field for each record and run it for each Unknown computer type (x86 & x64) This is the entry (the culprit) that I found (this will be different/unique in every environment ) Copy the value as mentioned about and run it against each value and see if you get a result. If you get a result, it means that you have a stuck record. if not than it might be a more common problem/gotcha as i mentioned in my original post above. In my case I did have a returned vaule so I went about deleting it. This is how I deleted the entry: Note: its worth running the select unknown machines (built in) query as shown here at the top of this image to confirm that everything is still in order. I will continue to test by imaging a handful of machines and try deleting them afterwards to see if the issue still occurs. As for why it happened, I'm not exactly sure but when I checked with the other guys in my department, apparently that machine went flat during imaging (laptop). This has been an excellent learning curve and I will document this one in length in case it happens again in the future.

Insider builds and any builds not known to your site will show up as Other. I have several computers running Win10 1703 (build 15063.332) that are showing as Other in my dashboard as well. Once I read this article from Jason Sandy's I gave up on the Servicing Dashboard and used Upgrade Task Sequences instead. Either way it would be nice to get accurate data and to be able to click on the rings to see which systems are being inventoried.

Sorry folks, I think i got this one on my own. Below is what I have found: **The IIS Worker service was using high amounts of CPU. After further investigation we found the issue to be with the WsusPool Worker Process on the server. It would climb up and service a few clients and then recycle on a regular basis. We noticed the same IP addresses were in the "current requests" for the worker service each time before it crashed. It was the Windows Server 2016 servers, which were coincidentally the Advanced Threat Analytics servers (not related). ** After many searches and digging on this topic it would appear it is an IIS configuration change issue, which is reflected in the following articles: http://serverfault.com/questions/522832/problems-with-sup-on-sccm-2012-sp1 http://blog.coretech.dk/kea/house-of-cardsthe-configmgr-software-update-point-and-wsus/ https://social.technet.microsoft.com/Forums/en-US/a629c131-1c12-4803-a479-e5c6ca784b10/sccm-wsus-failed?forum=configmanagergeneral http://stackoverflow.com/questions/16162524/how-to-increase-memory-and-cache-size-for-application-pool-in-iis-7-efficiently https://blogs.msdn.microsoft.com/the_secure_infrastructure_guy/2015/09/02/windows-server-2012-r2-wsus-issue-clients-cause-the-wsus-app-pool-to-become-unresponsive-with-http-503/ So here are the settings that I changed within IIS on Private Memory Usage Increase (for Recycling Conditions) - Private Memory Usage increase to 8388608 KB Output Cache Increase (for response file size): - Output Cache Settings increase to 1048576 (in bytes) Maximum Worker Processes: -Maximum Worker Processes from 1 to 0 (System must be NUMA aware for this and will essentially trigger as many worker processes as there are NUMA nodes). Thanks /Gus

Hi all, Looking for some tips on this one as its not the most straightforward of activities. Scenario: We are planning to outsource our imaging to Dell, essentially this means we will create a image, and Dell will preload it onto newly purchased hardware. Therefore when the end-user gets their new laptop delivered, they simply connect the network cable, switch it on and follow the very basic on screen instructions (choose country etc), and away they go. Based on the country the users choose, lang packs are installed, time zone set, locale, and even the computer name is prefixed with the country code. We're familiar with this part. I'm curious as to whether anyone has been able to implement a recovery partition using SCCM task sequences. A scenario where this would be required is when the end-user has issues on their machine but no local IT support is available to rebuild it. We could instruct the end-user to restart the computer press a "F" key and recover the machine back to its original state. Thus totally eliminate the need for local IT which can be VERY costly in remote areas/countries. I know both pre-staging and recovery can be achieve as separate functions. Its combining them into a single, automated, deployable solution that is my task. So curious as to whether anyone has done this before and has any tips that could speed things up on my end.

hi can you try enabling/starting the Remote Registry Service, does it work then ?

One thing i can't stand about forums is no one responding back to how they fixed their issue. I hope this helps someone down the road. I just got off the phone with support and this was their fix as well. They said it's a client side issue with certificates being corrupt. ERROR: Error. Status code 500 returned OSDSMPClient 7/25/2016 4:25:28 PM 5656 (0x1618) Received 1231 byte response. OSDSMPClient 7/25/2016 4:25:28 PM 5656 (0x1618) pReply != NULL, HRESULT=80004005 (e:\qfe\nts\sms\client\osdeployment\osdsmpclient\smpclient.cpp,2391) OSDSMPClient 7/25/2016 4:25:28 PM 5656 (0x1618) SMP Root share info response is empty OSDSMPClient 7/25/2016 4:25:28 PM 5656 (0x1618) ClientRequestToSMP::ClientRootShareRequestToSMP failed. error = (0x80004005). OSDSMPClient 7/25/2016 4:25:28 PM 5656 (0x1618) ExecuteRootShareInfoRequest(sRootShareList), HRESULT=80004005 (e:\qfe\nts\sms\client\osdeployment\osdsmpclient\smpclient.cpp,1717) OSDSMPClient 7/25/2016 4:25:28 PM 5656 (0x1618) ClientRequestToSMP::DoRequest failed. error = (0x80004005). OSDSMPClient 7/25/2016 4:25:28 PM 5656 (0x1618) Request to SMP 'http://myservername.domain.com'failed with error (Code 0x80004005). Trying next SMP. OSDSMPClient 7/25/2016 4:25:28 PM 5656 (0x1618) Sleeping for 60 seconds before next attempt to locate an SMP. OSDSMPClient 7/25/2016 4:25:28 PM 5656 (0x1618) Retry number 2 OSDSMPClient 7/25/2016 4:26:28 PM 5656 (0x1618) Microsoft's response ++ It looks like there is certificate issues while performing the restoration task. ++ Please run following command under PowerShell (As Admin ) · Remove-Item -Path ‘HKLM:\SOFTWARE\Microsoft\SystemCertificates\SMS\Certificates\*’ -force; · restart-service ccmexec Sunshine

If you are looking to get better writing reports, first I will tell you to stop using Report Builder and use SQL Server Data tools (SSDT) or Business Intelligence Development Studio (BIDS) instead. If you will be at MMS next week there are several presentation on writing reports. Lastly, if you are looking for a book on the subject then I would look at this one. :-) http://www.amazon.com/gp/offer-listing/0672337789

This list of guides (think of it as a living index) will be updated by me whenever I write a new guide for the new versions of System Center Configuration Manager (Current Branch) or System Center Configuration Manager (Technical Preview) and how they incorporate with Microsoft Intune. These guides are broken down into two different sections: System Center Configuration Manager (Current Branch) System Center Configuration Manager (Technical Preview) The Current Branch release is meant for your production deployments and the Technical Preview releases are for testing new upcoming features in the product, and are aimed at Lab use only. If you are looking for some of my other guides then please check below: Microsoft Intune (standalone) in Azure step by step guides are here Microsoft Intune (hybrid) guides look here (over 61,103 views as of July 2017) Configuration Manager 2012 guides then look here (over 1 million views as of July 2017) Configuration Manager 2007 guides then look here (over 948388 views as of July 2017) Microsoft Deployment Toolkit guides are here SMS 2003 guides are here (over 10423 views as of July 2017) cheers niall System Center Configuration Manager (Current Branch) Installation - How can I install System Center Configuration Manager (Current Branch) Configuring Discovery - How can I configure discovery for System Center Configuration Manager (Current Branch) Configuring Boundaries - How can I configure boundaries in System Center Configuration Manager (Current Branch) Using Updates and Servicing in Offline mode - How can I use Updates and Servicing in Offline mode in System Center Configuration Manager (Current Branch) Using Updates and Servicing in Online mode - How can I use Updates and Servicing in Online mode in System Center Configuration Manager (Current Branch) Setting up the Software Update Point - How can I setup Software Updates in System Center Configuration Manager (Current Branch) Installing the Client agent - How can I configure client settings and install the ConfigMgr client agent in System Center Configuration Manager Current Branch Upgrading to System Center Configuration Manager (Current Branch) version 1602 from System Center Configuration Manager (Current Branch) version 1511 How can I use the Upgrade Task Sequence in System Center Configuration Manager (Current Branch) ? How can I use servicing plans in System Center Configuration Manager (Current Branch) to upgrade Windows 10 devices ? How can I deploy Windows 10 with MDT 2013 Update 2 integrated with System Center Configuration Manager (Current Branch) How can I install Windows 10 language packs offline with an MDT Integrated Task Sequence in System Center Configuration Manager (Current Branch) How can I use PowerShell to populate Windows 10 CB, CBB, LTSB and Insider Preview collections in System Center Configuration Manager (Current Branch) A deeper look at the Upgrade task sequence in System Center Configuration Manager (Current Branch) How can I deal with languages in the Upgrade Task sequence using System Center Configuration Manager (Current Branch) How can I display custom messages in a task sequence using PowerShell in System Center Configuration Manager (Current Branch) Update rollup for System Center Configuration Manager current branch, version 1602 How can I use Windows 10 Servicing when a language pack is installed using System Center Configuration Manager (Current Branch) Now Available: Update 1606 for System Center Configuration Manager Now Available: Update 1610 for System Center Configuration Manager How can I install System Center Configuration Manager version 1606 (Current Branch) on Windows Server 2016 with SQL 2016 How can I change System Center Configuration Manager from an Eval edition to a Licensed edition ? Why Telemetry is great, and why the uptake of Configuration Manager Current Branch is unprecedented How can I use Express Updates when patching Windows 10 with Quality Updates in System Center Configuration Manager (Current Branch) First looks at Ciresons ConfigMgr Portal How can I upgrade to System Center Configuration Manager (Current Branch) version 1702 How can I forcefully upgrade one version of Windows 10 to the latest using System Center Configuration Manager (Current Branch) SCCM Query for All Windows 10 version 1703 ? How can I install System Center Configuration Manager version 1702 (Current Branch) on Windows Server 2016 with SQL 2016 How can I upgrade to System Center Configuration Manager (Current Branch) version 1706 System Center Configuration Manager (Technical Preview) Installation - How can I install System Center Configuration Manager and Endpoint Protection Technical Preview 4 Spot the difference, maintenance windows versus service windows, Microsoft is listening and fixing ! System Center Configuration Manager Technical Preview 1601 is now available ! System Center Configuration Manager Technical Preview 1602 is now available ! System Center Configuration Manager Technical Preview 1603 is now available ! System Center Configuration Manager Technical Preview 1604 is now available ! System Center Configuration Manager Technical Preview 1605 is now available ! System Center Configuration Manager Technical Preview 1606 is now available ! System Center Configuration Manager Technical Preview 1607 is now available ! System Center Configuration Manager Technical Preview 1608 is now available ! System Center Configuration Manager Technical Preview 1609 is now available ! System Center Configuration Manager Technical Preview 1610 is now available ! System Center Configuration Manager Technical Preview 1611 is now available ! System Center Configuration Manager Technical Preview 1612 is now available ! System Center Configuration Manager Technical Preview 1701 is now available ! What is the ContentLibraryCleanup tool and how can I use it ? System Center Configuration Manager Technical Preview 1702 is now available ! Video - Upgrading to System Center Configuration Manager 1703 Technical Preview System Center Configuration Manager Technical Preview 1704 is now available ! System Center Configuration Manager Technical Preview 1705 is now available ! System Center Configuration Manager Technical Preview 1706 is now available !

Okay, resolution to this was to basically create a new Configuration Manager Package which I did do, but what Microsoft did was basically Re-Create the Client Package as if we built in the CAS. Since my Client package was created in the Stand Alone initially and was Expanded to the CAS it might have caused some issues??? I don't really totally agree with that, but oh well. Here are the Resolution they did: 1. Create a new ConfigMgr client package with any name and no programs (Source: \\server\SMS_Site\Client) 2. Create a new ConfigMgr client upgrade package with any name and no programs (Source: \\server\SMS_Site\Client Upgrade) The packages you created manually will be automatically deleted; no need to remove them later. New default packages will be automatically created. 3. run the following queries in the CAS site database – change the old and new package Ids accordingly: update ClientDeploymentSettings set FullPackageID = 'new Client PkgID' where FullPackageID ='old Client PkgID' update ClientDeploymentSettings set UpgradePackageID = 'new Upgrade PkgID' where UpgradePackageID ='old Upgrade PkgID' 4. Restart SMS_Executive and SMS_Site_Component Services 5. Delete the problematic package after distributing the new default client package to the desired DPs. This is how it looks now: (You will see WFT000D2 is the new Client Package)

That helped me as well, after SP1, CU1, the Software Summarization was set to run every hour, and had my SQL pegged. We went from 4 to 6 cores, same thing, bumped it to 8, same thing... If you're looking for where summarization is, right click on "All Software Updates" under Software Updates in Software Library, and you'll see summarization. It was set to every hour, so I changed that to 1 day, and it's much happier now.