Jump to content


Established Members
  • Content Count

  • Joined

  • Last visited

  • Days Won


Westy182 last won the day on May 4 2018

Westy182 had the most liked content!

Community Reputation

2 Neutral

About Westy182

  • Rank

Recent Profile Visitors

1,104 profile views
  1. Hi all, I hope someone can help me, even if it's just to say this isn't possible.... We currently have an SCCM 1806 environment with HTTPS/PKI enabled. All domain joined machines receive their personal PKI cert to allow SCCM client communication via GPO and this works fine. We have a need to build servers that are in a DMZ workgroup and at present these are built using a standard OSD task sequence which joins them to the domain. The server then has to be manually removed from the domain and added to the DMZ workgroup, then a certificate needs to be requested from the Certificate A
  2. I think the following blog answers my question as to what's happening with the Recovery partition during an OSD via SCCM: https://miketerrill.net/2017/07/12/configuration-manager-osd-recovery-partitions-and-mbr2gpt/ "Behind the scenes, it creates a diskpart answer file that it uses to partition and format the disk. The Recovery partition is getting set to type 7 instead of type 27 (hidden). When the Windows 10 Setup runs, it does not recognize (or use) the Recovery partition that was created by Configuration Manager" It doesn't clarify whether this is a bug in SCCM or whether an
  3. Hi all, I hope you can help as I've been search for some clarity on this matter for the last 2 days. Sorry for this, it's going to be a long one..... I'm working for a company who finished migrating to Windows 10 (1703 & 1709) last year. There are around 10k Windows 10 devices which are predominately legacy BIOS configured and now need to be converted to UEFI using the MBR2GPT tool. The devices were built using an SCCM task sequence (SCCM 1802) with MDT 2013 Update 1 integrated. I've just started to do some testing with the MBR2GPT tool using the guide linked below and have f
  4. Thanks for you reply. I think we're going to be logging a ticket to Microsoft for this problem now. I've tried manually deleting things from the content library to try and trick a full redistribution but I think the record may need deleting from the database which I don't really want to do without knowing exactly what I need to delete. I found the following query that can be run on the DB to detect the status of a package: Select * FROM PkgServers WHERE PkgID = 'ABC00123' AND NALPath Like '%MYSERVERNAME01%' You can set the "RefreshTrigger", "UpdateMask", and "Action" tables to tri
  5. Hi all, A problem that seems to be occurring more and more frequently in the environment I'm currently working in is content not successfully distributing to Distribution Points. We have over 130 secondary site servers in the environment and it's common to find "Invalid" content when using the Content Library Explorer tool. If a piece of content is "Invalid" I normally can't successfully remove it via the SCCM console as it then goes into a orphaned state in the content library. If left for any period of time and then re-distributed to the problem DP, the files never go through the
  6. Apologies as I was rushing when I posted that snippet above. Open the "MigUser.xml" which is a standard file with USMT. Search for "This component migrates user files with known extension" and then add the following line into this section: <script>MigXmlHelper.GenerateDrivePatterns ("* [*.snt]", "Fixed")</script> This should then migrate any W7 .snt files from APPDATA/Roaming/MICROSOFT/Sticky notes to the same place on a W10 machine. Then the first time you launch Windows 10 Sticky Notes it will check this location for any legacy .snt files for that user profile and
  7. <!-- This component migrates user files with known extension--> <component type="Documents" context="UserAndSystem"> <displayName _locID="miguser.userdata">User Data</displayName> <role role="Data"> <rules context="System"> <include> <objectSet> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.snt]", "Fixed")</script> </objectSet>
  8. I found that if you confirm that your USMT scripts have a migration rule for the .snt extension and you let it migrate from a W7 machine to the same location on a W10 machine, the W10 modern app will check the old W7 location and auto migrate any .snt files to the new area on first run.
  9. Found the infor relating to this issue from Microsoft too: https://support.microsoft.com/en-us/help/4093120 Known issues in this update Symptom Workaround After you install the March 13, 2018 or later Cumulative Update for Windows 10 Version 1607, only the latest Windows 10 feature update is returned as applicable. This prevents the deployment of previously released feature updates using ConfigMgr (current branch) and Windows 10 servicing plans. Decline all feature upda
  10. Just to confirm, I've removed "2018-04 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4093119)" and now the 1703 Feature Update has appeared in Software Center! I'll get the CUs for each month of this year and try to find out where it's breaking.
  11. Hi Niall, That is a good shout as we did have issues with Feature Updates at the end of last year on machines with old SCCM clients. Updating those clients did indeed fix them. We're now on SCCM 1710 and client version 5.00.8577.1108. I've actually just found some info online where someone else with a similar issue found that some of the recent 2018 Cumulative/Security updates have caused clients to now report in as being compliant. I'm removing the 2018-04 patches I have installed and testing again.
  12. Hi all, I've headed here to post my problem as I've spent the best part of 2 weeks on and off troubleshooting and I'm not getting anywhere. The company I'm currently working for now have a mixture of Windows 10 clients in their environment. 1511, 1607, 1703, 1709. We've been plugging away for months now to try and clear the last few hundred 1511 clients as we suffered from the WSUS decryption key issue with Feature Updates, but this was resolved and seemed to be working fine. We don't use servicing plans at all as we prefer to control the deployments more manually via direct deploym
  13. Hi all, I'm hoping that someone can help as I'm really struggling to find anyone else that's had this specific problem. When trying to build brand new HP equipment with an SCCM (MDT integrated) OSD task sequence I am seeing the following error when the machine runs the "Invoke-MbamClientDeployment.ps1" script: Failed to escrow TPM owner-auth to http://MBAMSERVER.domain/MBAMRecoveryAndHardwareService/CoreService.svc. HRESULT: 0x80280012 I've found that 0x80280012 means "There is no Storage Root Key (SRK) set." but I'm struggling to understand why this error only effects some
  14. Hi all, I really hope someone can help as I've spent an unbelievable amount of time trying to get this working with no success. I'm using USMT from the 1607 ADK and I'm trying to relocate a legacy Sticky Note file (.snt) from a windows 7 machine to the new Sticky Note modern app location on a Windows 10 machine. W7 location = %AppData%\Roaming\Sticky Notes\StickyNotes.snt W10 (1607) location = %LocalAppData%\Packages\Microsoft.MicrosoftStickyNotes_8wekyb3d8bbwe\LocalState My USMT script is currently able to sucessfully collect up the snt file from a W7 machine a
  15. Hi all, I have an application is SCCM that runs a vbs to install Office 2016 click to run. The packaging team have used a VBS so they can cover installing Office 2016 on different versions of Windows and also trigger the appropriate Office scrub tool if applicable. Anyway, in my instance I am running the application on a Windows 7 Enterprise X64 machine which has Office 2013 C2R already installed. If I run the script out of SCCM it upgrades O2013 to O2016 in around 15 mins but when installing via the SCCM Application it hangs sometimes for an hour before the actual install occurs. T
  • Create New...