User Profile
gwblok
Iron Contributor
Joined 7 years ago
User Widgets
Recent Discussions
Re: How to capture BIOS Version through MECM/Intune
krishna2320 You can look at Intune Portal, pick a device and then drill down into the Hardware option under monitor. You can probably use graph to gather it from all of your devices and build a report. or ConfigMgr collects this data, you can retrieve it via SQL query select the data from: view: v_GS_PC_BIOS for a bit nicer query: SELECT DISTINCT SYS.Netbios_Name0 as 'Computer Name' ,WS.LastHWScan ,DATEDIFF(day,WS.LastHWScan,GETDATE()) as 'Days Since HWScan' ,SE.SerialNumber0 AS [Serial Number] ,bb.Product0 ,cs.Model0 AS Model ,cs.Manufacturer0 AS Manufacturer ,SYS.BuildExt ,SYS.User_Name0 [Last Logon User Name] ,BIOS.SMBIOSBIOSVersion0 FROM v_GS_WORKSTATION_STATUS WS LEFT JOIN v_R_System SYS ON WS.ResourceID = SYS.ResourceID LEFT JOIN v_GS_PC_BIOS BIOS ON WS.ResourceID = BIOS.ResourceID LEFT JOIN v_GS_COMPUTER_SYSTEM cs ON CS.ResourceID = SYS.ResourceID LEFT JOIN dbo.v_GS_SYSTEM_ENCLOSURE SE ON SE.ResourceID = SYS.ResourceID Join v_GS_BASEBOARD bb on bb.ResourceID = SYS.ResourceID join dbo.v_FullCollectionMembership FCM on FCM.ResourceID = SYS.ResourceID Where FCM.CollectionId = 'MCM00035' (Make sure you modify the Collection ID for the collection you want to limit the query to)2.6KViews0likes1CommentRe: upgrade windows 10 with task sequence
If you're running it in a Task Sequence, you should control the entire process once the TS starts and ideally, prevent the user from doing anything on the device until the upgrade is over to reduce the risk of upgrade failure. The goal of using a task sequence is to upgrade the device as fast as possible, and get the device back to the end user after the TS is done. If you want to allow the user to have control over reboots, I'd recommend using Servicing. For the Task Sequence, I'd suggest adding native popups to when the TS starts (when launched from software center) to warns the end user that the upgrade is starting and the device will be rebooting several times. For very detailed processes of using a Task Sequence, check out this info: https://garytown.com/waas https://garytown.com/waas-1909-ts-download Note, if you're upgrading anything Windows 10 2004 (20H1) and newer to 22H2, don't use a Task Sequence, use enablement packages.897Views0likes0CommentsAutopatch Telemetry Setting
Hello, I'm looking for the doc that says which Telemetry Level AutoPatch requires. For Windows Update Compliance, I set "AllowTelemetry" to 1, but after enrolling machines in AutoPatch, I see the setting is now set to 2 on the endpoints. Was this caused by AutoPatch? I'm sure there is a doc somewhere that says AutoPatch Requires Basic or Enhanced, just can't find it. Thanks3.3KViews1like3CommentsRe: /postoobe not working on setup.exe
Thomas_Toka If you're starting the Setup from WinPE, that option isn't available: https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/windows-setup-command-line-options#postoobe See Applicability If you're deploying an Image (vs running setup), you can slip in a SetupComplete.cmd File into the c:\Windows\Setup\Scripts folder, and the Setup Engine will run that for you. However, is you're kicking off the setup engine manually from WinPE.. you'd have to come up with something creative to trigger that file.4.1KViews0likes1CommentRe: CreateProcessAsUser Error 5 - ServiceUI.exe
Shandiaak Can you please put your syntax you're using to call ServiceUI in your task Sequence? I have not had any issues with launching Service UI in my 1809 -> 1909 Task Sequence, before OR after the upgrade. I'll often launch a command prompt to pause the TS at certain points for troubleshooting, and I've had no issues using this command: ServiceUI.exe -process:tsprogressui.exe "%WINDIR%\System32\cmd.exe" Just make sure you're not hiding the TS Progress UI.10KViews0likes2CommentsRe: Whiteboard App silent install
Are you talking about the Whiteboard App from the MS Store? You can use intune or CM Deploying Store Apps with CM: https://docs.microsoft.com/en-us/mem/configmgr/apps/deploy-use/manage-apps-from-the-windows-store-for-business Deploying Store Apps with intune: https://docs.microsoft.com/en-us/mem/intune/apps/apps-windows-10-app-deploy Depending on the tools available to you, the deployment method will be different.17KViews0likes3CommentsRe: Active Setup Registry keys are removing after upgrading to 1909
Brett_Bowron I can't tell you why, but this has been the norm for the past few build upgrades. You can either backup those keys before the upgrade and import them after, or run a repair on the MSI that originally put them there. We are working with our vendors to avoid using Active Setup in their products, otherwise for now, we trigger repair on the MSI installers that created the Active Setup keys so they get put back again.4.1KViews0likes0CommentsRe: Win7 to Win10 1803/1809 in-place upgrade Task Sequence breaks with no apparent error code
norcMike On machines that I've had the TS hang like that, I've got a script for clearing things out and resetting them. I've put a portion of it on github, which should be enough to do what you're hoping to clear out the "installing" TS. https://github.com/gwblok/garytown/blob/master/ResetTSlite.ps1 Typically I've seen this behavior when: Machine is rebooted PRIOR to the first reboot created by the Setup Engine (End User, or other process that reboots the process while the TS has kicked off and the Setup Engine is in Phase 1.) If you're using the latest 1809 media and CM 1910, most of the times I've seen this have been resolved. More details HERE: https://www.recastsoftware.com/blog/windows-10-rollback-setuprollback-cmd-and-configmgr Good luck with your upgrades!2.8KViews0likes1CommentRe: CreateProcessAsUser Error 5 - ServiceUI.exe
Elliot_the_Goose Ok, our Splash screen (which is completely PowerShell) didn't have any issues between any of the CM Upgrades. https://garytown.com/windows-splash-screen-for-the-task-sequence-progress Feel free to take a look. There have been changes in the TS engine with each build, but I haven't seen any issues with any of the places I've used ServiceUI.exe in my testing. If you use ServiceUI to launch a Command Prompt, do you get the same issue? Basically do you get error anytime you use ServiceUI in your TS, or just with your Splash Screen? Other examples of using ServiceUI: https://garytown.com/launch-application-in-task-sequence-in-os-serviceui11KViews0likes6CommentsRe: CreateProcessAsUser Error 5 - ServiceUI.exe
Elliot_the_Goose What OS are you running this on? 1809? 1909? We had issues with our Splash Screen as well when running on 1909. There is change in how powershell uses run spaces in 1909. More Details here: https://smsagent.blog/2020/03/12/windows-10-splash-screen-issue-fixed-for-w10-1909-configmgr-task-sequence/11KViews1like8CommentsRe: SetupDiag information next release of Windows 10
Steve_DiAcetis Thanks Steve We currently run SetupDiag on each upgrade. We grab the setup time for reporting metrics on how long it takes for the upgrade to run. If upgrade fails, we then inventory some of the keys which are populated into custom reports I've written for our upgrade process. Based on some of the SetupDiag output, we also flag some machines for reimage as we've learned some SetupDiag return codes point to issues that aren't worth resolving (or able to resolve) and the best course is Wipe / Load. Very excited for SetupDiag to be integrated. Question, if SetupDiag is integrated into the upgrade, will we still be able to call it standalone? Where will the upgrade process place it? During upgrade does it get copied into a specific folder? Does it get autoatmically "cleaned up" after upgrade, (windows.old folder?), or will it stick around forever? Panther folder?1.8KViews0likes1CommentRe: Upgrading OLD windows 10 versions
Karen_Simpson Karen, You mean using the enablement package, which isn't the question John is asking. Looking for documentation on supported jumps to 1909 from previous versions running Servicing (in place upgrade). Enablement Package 1903 -> 1909 https://support.microsoft.com/en-us/help/4517245/feature-update-via-windows-10-version-1909-enablement-package Servicing: (Previous Windows 10 -> Newer Version of Windows 10) https://docs.microsoft.com/en-us/mem/configmgr/osd/deploy-use/manage-windows-as-a-service3.5KViews2likes1CommentRe: SetupDiag information next release of Windows 10
Is there any additional documentation on how it will work? Will we be able to control the options in the setup command line? Like, can I force it to run setupdiag on ALL upgrades, even successful, can I redirect the output logs to a specific folder? Are there any new options like redirecting the registry keys to a different location as well? Did you work with the CM Team to have these Key automatically inventoried? Would really like that if these were automatically inventoried then a new report / dashboard in CM to surface the data easily.1.9KViews1like3CommentsRe: Windows Servicing Model
John_Dahl Hey John, I'm in the camp where you'd want to update your Firmware before an upgrade. (But on average, keeping your environment constantly updated. Ideally not coupled with the upgrade itself, but sometime before the upgrade. You'd slip in the vendor tested driver pack during IPU We're planning to leverage Setup Based Drivers during the upgrade as well, but it would be a "Sub Task Sequence" that we'd also be able to update and level set drivers whenever we need (Security Vulnerabilities, Stability issues, etc). We'd use this same "Module" to apply these setup based driver installers in OSD, IPU and Live Production machines. Goal is to have entire environment always consistent, patched, and stable. Of course, this all goes with extensive testing on each platform before deployment.1.2KViews2likes0CommentsRe: Factory Reset Windows 10 without user intervention
Claire_4 If you have the ability to pull down content, you can pull down Windows 1909 Installer, then run the command to upgrade and clean the system. The entire thing can be scripted. https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/windows-setup-command-line-options#auto220KViews0likes0CommentsRe: Upgrade win 10 entreprise evaluation copy to fully copy
NASRY Try using the KMS key: NW6C2-QMPVW-D7KKK-3GKT6-VCFB2 Then once you're off the EVAL Edition, you should be able to activate using your E3 license via AD Account https://docs.microsoft.com/en-us/windows-server/get-started/kmsclientkeys#windows-10-all-supported-semi-annual-channel-versions30KViews0likes0Comments
Recent Blog Articles
No content to show