All Activity

Sorry to hear that. Thank you for the reply.

Hi Anyweb, I’ve deployed BitLocker using your setup articles, but I’m encountering an issue where the devices aren’t encrypting the drives as expected. Any assistance you can provide would be greatly appreciated. It’s worth mentioning that the devices I’m testing with are all located in the same device collection where the MBAM encryption policy has been deployed. Additionally, all the devices have TPM 2.0, TPM is enabled and ready, and Secure Boot is also enabled. As for the logs, everything appears to be working as expected, except for the MBAM admin logs, which indicate that it cannot connect to the MBAM and hardware recovery services. However, according to Microsoft’s documentation, "Starting in version 2103, the implementation of the recovery service changed. It no longer uses legacy MBAM components, but is still conceptually referred to as the recovery service." Given this, I assume this error log should not affect the encryption process, correct? For reference, my environment is running Configuration Manager version 2409. I have attached a few screenshots for your reference. Thank you!

Unfortunately no. I even got on the horn with microsoft who was unable to help via the SCCM side. They wanted me to call to the OS side of the house, but I dont have that in the budget unfortunately as it's expensive as all get out. We're still using this via GPO's which sucks... it works, but ah well. When i was on the phone with SCCM support, the main issue we struggled with was we could set all the settings in bitlocker and would always go to success. However, once we did anything with encrypting the drive, it would completely fail. Sucks, but at least we have a work around still with the GPO's

Hi Nscott, I wanted to check in and see if you were able to find a solution to this issue. I’m experiencing the same problem and have gone through Anyweb's SCCM BitLocker setup and troubleshooting steps, but I still can't seem to identify the cause. Any insights you might have would be greatly appreciated!

I prefer third-party tools for Exchange backup and restore. Get help with article: https://learn.microsoft.com/en-us/exchange/recipients/disconnected-mailboxes/restore-deleted-mailboxes?view=exchserver-2019

Hi I am trying to apply the same but I guess the layout and GUI has changed a little bit so could you guide me to do the same in updated GUI

For those we don't have the canonical name for, make an entry in group policy under branch: User Configuration / Preferences / Windows Settings / Registry Create registry path if doesn't exist: HKCU\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer\DisallowCpl Value Name: 1 REG_SV value: Configuration Manager

Introduction This is Part 4 of a new series of guides which will cover managing Windows 365 Cloud PCs using PowerShell and Microsoft Graph. This mini series should help you get started with automating and managing your Cloud PCs using PowerShell via Microsoft Graph. If you are new to Windows 365 Cloud PCs then please read our previous series called Getting started with Windows 365 available here. At the time of writing, Paul is a 8 times Enterprise Mobility MVP based in the UK and Niall is a 14 times Enterprise Mobility & Windows and Devices MVP based in Sweden. Below you can find all parts in this series: Automating Windows 365 part 1 - Introducing Graph and setting up Visual Studio code Automating Windows 365 part 2 - Using Graph X-Ray Automating Windows 365 part 3 - Provisioning Cloud PC's Automating Windows 365 part 4 - Managing your Cloud PC <- you are here Automating Windows 365 part 5 - TBD In this part of our guide to managing Windows 365 Cloud PCs via PowerShell and Microsoft Graph, we'll cover the following management actions: Resize Restore Reprovision Restart Resizing your Windows 365 Cloud PCs The Resize remote action for Windows 365 Cloud PCs retains user and disk data which is very cool, and allows you the IT Admin to resize the users device as required based on usage or requests. The resize action allows you to: Upgrade the RAM, CPU, and storage capacity of a Cloud PC. Downgrade the RAM and CPU of a Cloud PC. Note: The resize option does not support reducing disk space. Also worth mentioning, you cannot resize a Frontline provisioned Cloud PC. The available options when attempting to resize your Cloud PCs are also based on the Windows 365 licenses you have in your tenant. For example, in our tenant we have the following licenses available: Windows 365 Enterprise 2 vCPU, 8 GB, 128 GB Windows 365 Enterprise 4 vCPU, 16 GB, 128 GB Windows 365 Enterprise 16 vCPU, 64 GB, 512 GB There are various resize options available but for this guide we'll upgrade from 2vCPU to 4vCPU, we cannot downgrade the disk space from 128GB to something smaller as this is not supported and we don't have the licenses available anyway. With that in mind in the Microsoft Intune admin under Devices > Device onboarding > Windows 365 > All Cloud PCs, if you select a device and choose Resize, you are presented with the options to Resize. Selecting an inappropriate option results in you being informed that the selected license is not available in your inventory as shown below in the screenshot. Keep this in mind when you attempt to resize your Cloud PCs via Graph. To get started with Resize via Graph and PowerShell, we need to list all the service plans available. Remember, these are not all the sizes available, just a list of them all. Using the following code, we can list all of those service plans, this uses the following cmdlet Get-MgBetaDeviceManagementVirtualEndpointServicePlan documented here. Install-Module Microsoft.Graph.Identity.DirectoryManagement -Scope CurrentUser -Force -AllowClobber Import-Module Microsoft.Graph.Beta.DeviceManagement.Administration Connect-MgGraph -Scopes "CloudPC.Read.All" Get-MgBetaDeviceManagementVirtualEndpointServicePlan -Property "id,displayName,type,vCpuCount,ramInGB,storageInGB,category,provisioningType,supportedSolution" Launch Visual Studio Code give it a go. The results will be displayed similar to the below output. To demonstrate the Resize action, we will upgrade one of our Cloud PCs, you can try this out on one of your own Windows 365 Cloud PCs by substituting the relevant service plan information. Currently, our Cloud PC is 2 vCPU, 8 GB, 128 GB as you can see below. Looking at the output from Graph for our service plans, we can see that we need service plan with the ID 2de9c682-ca3f-4f2b-b360-dfc4775db133 as this matches the subscription we have available. In the code below, we use the Get-MgBetaDeviceManagementVirtualEndpointCloudPc cmdlet, documented here, to retrieve the details of the device we are going to resize. Remember, you will need to change the ManagedDeviceName from CPCnM7PRJ to one of your own Cloud PC device names and select an available target service plan Id. We store the service plan information in the variable targetServicePlanId in the $params array. You will also need to change this to your target service plan ID. Finally, we issue the Resize-MgBetaDeviceManagementVirtualEndpointCloudPc cmdlet to kick start the resize process. Read about that cmdlet here. Install-Module Microsoft.Graph.Beta.DeviceManagement.Administration -Scope CurrentUser -Force -AllowClobber Import-Module Microsoft.Graph.Beta.DeviceManagement.Administration Connect-Graph -Scopes "CloudPC.ReadWrite.All" $cloudPc = Get-MgBetaDeviceManagementVirtualEndpointCloudPc | Where-Object { $_.ManagedDeviceName -eq "CPCnM7PRJ" } $params = @{ targetServicePlanId = "2de9c682-ca3f-4f2b-b360-dfc4775db133" } Resize-MgBetaDeviceManagementVirtualEndpointCloudPc -CloudPCId $cloudPC.Id -BodyParameter $params If you have picked a service plan which is not applicable, based on the criteria we have mentioned previously, you will receive a failure to resize when you view the device in the Intune admin center. If however you have executed the code against a valid target service plan, you will see the Resize action taking place in Intune. Return to the All Cloud PCs view under Devices > Device onboarding > Windows 365 > All Cloud PCs you will notice that the device will be listed with its Status as Resizing. After some time, the resizing operation will complete and this will be reflected under Device actions status when viewing the targeted device. In the screenshot below however you can also see that the old device model is listed. Triggering a Sync of the device or just waiting will update the model to the correct specs. In the All Cloud PCs view, the Status will now report as Provisioned and the PC type should reflect the new service plan. We can see below that the device does indeed have the new changes (CPU/RAM). Also, if the user attempts to access the Cloud PC from the Windows app or Windows 365 website, the size details of the Cloud PC will be reflected with the new resized information. Finally, the quick check on the Cloud PC itself confirms the change in CPU/RAM. The resize via Graph was a success! The Restore action via Graph In our previous Windows 365 series about Windows 365 we covered the Restore action, a feature specifically available to Cloud PCs. These restore points allow you, as the admin, to choose from a series of long or short term restore points. Long term restore points are saved every 7 days and there are a maximum of 4 long term restore points. Short term restore points are saved based on the user settings interval, so can be every 4, 6, 12, 16 or 24 hours. Read more about restore points at our blog post, here. You can view the available restore points for a device by navigating to Devices > Device onboarding > Windows 365 > All Cloud PCs in Intune. You then select a device and choose Restore from the menu. You are presented with a list of the available restore points which can be selected to revert the Cloud PC to. When managing our Cloud PCs for Restore via Graph, we need to begin by querying those restore points for our device. Start off by running the relevant modules and connecting to Graph. Next, you need to obtain the details of the Cloud PC you want to run the Restore action on. We are reusing our code from previous to do this by running the Get-MgBetaDeviceManagementVirtualEndpointCloudPc cmdlet and filtering on a specific hostname. Then we utilise the Get-MgBetaDeviceManagementVirtualEndpointCloudPcSnapshot cmdlet to gather all the snapshots for this Cloud PC. Read more about that cmdlet here. Install-Module Microsoft.Graph.Beta.DeviceManagement.Functions -Scope CurrentUser -Force -AllowClobber Install-Module Microsoft.Graph.Beta.DeviceManagement.Administration -Scope CurrentUser -Force -AllowClobber Import-Module Microsoft.Graph.Beta.DeviceManagement.Functions Import-Module Microsoft.Graph.Beta.DeviceManagement.Administration Connect-MgGraph -Scopes "CloudPC.ReadWrite.All" # Get Cloud PC $cloudPc = Get-MgBetaDeviceManagementVirtualEndpointCloudPc | Where-Object { $_.ManagedDeviceName -eq "CPCnM7PRJ" } # Fetch snapshots for the current Cloud PC $snapshots = Get-MgBetaDeviceManagementVirtualEndpointCloudPcSnapshot -CloudPcId $cloudPc.Id After executing, all the snapshots will be stored in the $snapshots variable. Let's say that we want to create a new snapshot for this Cloud PC. We can execute the New-MgBetaDeviceManagementVirtualEndpointCloudPcSnapshot cmdlet to achieve this. Details of this cmdlet are here. #Create a new snapshot New-MgBetaDeviceManagementVirtualEndpointCloudPcSnapshot -CloudPcId $cloudPc.Id In the Intune console, if you take a look at the targeted device you will see that Take Snapshot: Active is reported and initially in a Pending state before becoming Active. Once the Restore action of taking the snapshot is compete, the Device action status will be updated to reflect this. You can now re-run the Get-MgBetaDeviceManagementVirtualEndpointCloudPcSnapshot -CloudPcId $cloudPc.Id command to see the newly created, manual, snapshot listed. Likewise, in the Intune console, the snapshot will be listed. Note that the Restore point type will be listed as manual. OK, let's look at how you can restore to a specific restore point. You previously collected all the snapshots for a device and stored them in the $snapshots variable. You can use the ID from that data to run the restore. These are the ID's starting with CPC. Find the ID you want to use for your restore point and use the code below, changing the cloudPcSnapshotId details to match the ID of your snapshot. The code runs the Restore-MgBetaDeviceManagementVirtualEndpointCloudPc cmdlet to restore the Cloud PC. You can read about this cmdlet here. Install-Module Microsoft.Graph.Beta.DeviceManagement.Actions -Scope CurrentUser -Force -AllowClobber Import-Module Microsoft.Graph.Beta.DeviceManagement.Actions $params = @{ cloudPcSnapshotId = "CPC_cea5e16c-bdda-4f5a-9742-7edc350a3243_db8e01ae-d20a-42d0-b81f-2f9af940705b" } Restore-MgBetaDeviceManagementVirtualEndpointCloudPc -CloudPCId $cloudPC.Id -BodyParameter $params Once again, check the device in the Intune console to observe the status of the action. Here you can see from the All Cloud PCs view that the device is Restoring. and the Device action status will show when that Restore action is complete. Whilst a restore takes place, the user is unable to access the Cloud PC. In the Windows app, or the Windows 365 website, the status of the device will report Restoring Cloud PC. How to Reprovision a Cloud PC with Graph Another action, which is unique to Windows 365 Cloud PCs, is Reprovision. This action effectively deletes a user's current Cloud PC and creates a brand new one for the same user. Note that all the user's data, applications, customisations, etc, are also removed as part of this process. The code, once again, utilize the Get-MgBetaDeviceManagementVirtualEndpointCloudPc cmdlet and, as before, remember to change the name of the Cloud PC to match your device. To reprovision the device you simply need to run the Invoke-MgBetaReprovisionDeviceManagementVirtualEndpointCloudPc cmdlet against that Cloud PC. Read about that cmdlet here. Install-Module Microsoft.Graph.Beta.DeviceManagement.Actions -Scope CurrentUser -Force -AllowClobber Import-Module Microsoft.Graph.Beta.DeviceManagement.Actions Install-Module Microsoft.Graph.Beta.DeviceManagement.Administration -Scope CurrentUser -Force -AllowClobber Import-Module Microsoft.Graph.Beta.DeviceManagement.Administration Connect-MgGraph -Scopes "CloudPC.ReadWrite.All" # Get Cloud PC $cloudPc = Get-MgBetaDeviceManagementVirtualEndpointCloudPc | Where-Object { $_.ManagedDeviceName -eq "CPCnTGYOI" } # Reprovison the device Invoke-MgBetaReprovisionDeviceManagementVirtualEndpointCloudPc -CloudPCId $cloudPC.Id Let's check the Intune console once again for the status of the Reprovision action. You will see it reporting as Active in the device view. In the All Cloud PCs view it will state Provisioning in the Status column. Since our Cloud PCs using a random naming template, the device will be created with a new name. In our case the device is now called CPCn4D8PH. Finally, in the device view, the reprovisioning will be marked as Completed. Restarting a Cloud PC As with the reprovisioning via Graph, the Restart action is fairly simple to implement. The Restart device action initiates a reboot of the selected device within five minutes. Keep in mind that the device owner won't receive an automatic notification, which could result in unsaved work being lost. Since we provisioned the Cloud PC previously, we have updated the hostname in our command to get the Cloud PC via the Get-MgBetaDeviceManagementVirtualEndpointCloudPc cmdlet. Be aware of that if you have followed along and also reprovisioned prior to running this action. As mentioned, the reprovision action may have changed the device name. With details of the Cloud PC gathered, you can execute the Restart-MgBetaDeviceManagementVirtualEndpointCloudPc cmdlet. Details here. Install-Module Microsoft.Graph.Beta.DeviceManagement.Actions -Scope CurrentUser -Force -AllowClobber Import-Module Microsoft.Graph.Beta.DeviceManagement.Actions Install-Module Microsoft.Graph.Beta.DeviceManagement.Administration -Scope CurrentUser -Force -AllowClobber Import-Module Microsoft.Graph.Beta.DeviceManagement.Administration Connect-MgGraph -Scopes "CloudPC.ReadWrite.All" # Get Cloud PC $cloudPc = Get-MgBetaDeviceManagementVirtualEndpointCloudPc | Where-Object { $_.ManagedDeviceName -eq "W365-5AMXD" } # Restart the device Restart-MgBetaDeviceManagementVirtualEndpointCloudPc -CloudPCId $cloudPC.Id The device will report as Restart: Active in the device view in the Intune console. As mentioned, the user will get disconnected from their Cloud PC. and when the action is complete, it will be reported as such in the Intune console and the user will be able to log back into their device. Summary Managing your Cloud PCs via Microsoft Graph is super simple and we have showed you how you can run effective code to execute the resize, restore, reprovision and restart actions against a specific device. You can take the code provided and expand this to create scripts which could run these actions against a collection of devices, similar to the Bulk actions options available in the Microsoft Intune admin center.

if they click cancel then the required task sequence will not run and it will want to reboot the computer

Hi, thanks for this tutorial. If users click cancel, does the process fail or proceed as normal? More than likely, the only persons that will use the hidden ones are my team, which means no one else will know the deployment id.

check your messenger

Could I please get all the 2012 ones along with the 1702?

thanks for sharing !

I have the following prerequisites, take your pick

Does anyone have the prerequisites for SCCM 2012 R2 and SCCM 1606? I am using these versions in my labs and need the prerequisites.

Another point of reference I wrote a few years back can be found on our blog here!

Introduction Shortly after Technical Preview 2411 was released I predicted that Configuration Manager 2409 would be released within a couple of days, and it was more or less, well… 4 days later. This production release was late and people were waiting to see what the new release offered/fixed. To clarify what i mean by late, if we are going by the release name, it should have technically been released in September 2024 (Configuration Manager 2409) and yet was released in December 2024. Oh well, at least it’s out. 2409 Release dates Fast Ring: December 03, 2024 Slow Ring: December 16, 2024 I upgraded my lab to 2409 using the fast ring script as soon as it was available and I had no issues at all with the upgrade. Here are the update notes from Microsoft. What’s new ? Now that we have 2409 installed, what is new/changed/broken/depreciated. I’ll highlight the important ones, you can get the entire list here. SQL related Configuration Manager now supports SQL extended protection for authentication. It’s a security feature that enhances protection against MITM attacks, making SQL server more secure when connections are made using extended protection. Starting with version 2409, Configuration Manager no longer supports SQL Server 2012 and 2014. Upgrade to the latest SQL Server version or at least SQL Server 2016. If you don’t upgrade, CM upgrades are blocked, and you see an error during the prereq check. For more information, see Supported SQL Server versions for Configuration Manager. OSD related MDT is depreciated so it’s time to remove all MDT integration from your task sequences before October 2025. Windows 11 24H2 & Windows Server 2025 are added to the Product lifecycle dashboard and supported platform. Windows 11 24H2 & Windows Server 2025 client support is added. Boot image creation in CM on Windows Server 2025 now supports the latest Windows ADK. The Windows upgrade readiness dashboard now supports Windows 11 24H2 for upgrading clients. Configuration Manager now supports BitLocker task sequence steps for Arm64 devices. Cloud related The ‘Renew Secret Key‘ feature now opens a dialog with four options for the validity period. This update also prevents applications older than 800 days (approximately two years) from renewing their secret keys. The same options are available when creating a new app. CMG Setup now uses managed Identities and third-party Server App to interact with CMG’s Azure Storage account, instead of storage account keys. Other In BitLocker Management, policies that include OS drive encryption with a TPM protector and fixed drive encryption with the Auto-Unlock option are supported on Arm64 devices. Issues I observed (post upgrade) Upgrading to 2409 twice As I had originally upgraded to 2409 using the fast ring script, I went back to see if any HFRU was released to address any issues, and there wasn’t however there was a new version of Configuration Manager 2409 … not confusing at all. So before continuing I decided to upgrade my site to 2409 again :-). After some time (the next day) my site was upgraded again and looking good, this time with version 5.00.9132.1011. Enabling CMG Enhanced Security When enabling the CMG enhanced security, using an account that was a Global Admin in Azure, I got the following error: Subscription Configuration Error occurred when granting Contributor permission to the Microsoft Entra ID app for resource group cloudattachcmg. For more information, see SmsAdminUI.log. which pointed me to the SMSAdminUI.log. Here’s a snippet from that log: [1, PID:3620][12/18/2024 11:21:17] :Hyak.Common.CloudException\r\nFailed to complete the role assignment with status code Forbidden.\r\n at Microsoft.ConfigurationManagement.AdminConsole.AzureServices.EnhanceSecurityDialog.GrantRoleBasedAccessControlToAadAppOnResourceGroup(String subscriptionId, String servicePrincipalId, String resourceGroupName)\r\n I looked at the user I was logged in as and it was indeed a Global Admin and the role enabled using PIM, however it wasn’t a subscription owner as the following indicates you need to be. When I originally setup this CMG I used a different Global Admin account which was also the subscription owner. So I assigned the subscription owner Azure resource role to my new Global Admin user, PIM’d the role and tried again. This time, it went through the upgrade wizard without a hitch! I hope this helps someone ! New abilities Below you can see the new maintenance windows feature which is part of the CMG enhanced security The renew secret key option for your Cloud Management Server App opens the following wizard with new options for secret key expiry Centralized search means you can now decide which node to search in, or choose All Workspaces to search everywhere. Until the next time, cheers niall

Introduction Windows 365 Cloud PC’s have evolved a lot in the last couple of years, and with the Windows app you can access them from practically any device. The Android based Motorola ThinkPhone is not new however, but I’ve been using it to access my Cloud PC’s from various locations (Sweden, Texas, Florida) over the last several months to get a good idea of it’s capabilities. To assist with that I’ve connected it to the following for ease of use: External monitor (Lenovo ThinkVision portable monitor) Phone stand (cheap eBay stand) USB C port extender Wireless keyboard and mouse This combination might mean that you need to pack less computing power as the Cloud PC does the heavy lifting. You could even skip the portable monitor and use the ThinkPhone’s built in screen but that might be a stretch if your eyesight isn’t up to it. ThinkPhone & Windows 365 So what does this phone offer exactly in relation to Windows 365 Cloud PC’s ? Well if has built in integration with Windows 365 allowing you to quickly access your Cloud PC’s with a rich experience over the native Android experience via the Window app. When you connect an external monitor you’ll see the Windows 365 integration first hand and it’s conveniently the first icon shown. Clicking it shows you what looks like a connection to a Cloud PC but the text at the bottom of the screen informs you to: Select a Cloud PC on your phone to connect. I don’t quite get why this is necessary, or why you are not shown the Cloud PC’s on your display to choose from, but this is how it works with this solution currently. It’s a step I’d like to see improved in a later release of this solution. Returning to your phone, you select the Cloud PC you want to connect to. and after doing so you are prompted to confirm your preferences in relation to what the remote PC can access on your device. your Cloud PC magically launches, how cool is that? You can do your work as normal, browse websites, use Teams for meetings and so on. It actually works very well for general office tasks. This entire blog post, from start to finish was composed on my Cloud PC using the ThinkPhone while away from my normal office environment. What needs improvement As I’ve said already I’ve used this combination (ThinkPhone + External portable monitor + wireless keyboard + mouse) in various locations around the world and for most scenarios it works really well. However there is room for improvement. Multiple monitor support Most people that dock anything to a USB-C or Thunderbolt dock do so with multiple monitors, and straight away, this scenario fails, as it can only utilize one monitor. This is probably why the online demos are always with one monitor. I’ve 3 monitors in my home office and that’s how I like to work with my Cloud PC’s. Cloud PC license support Currently it doesn’t support Frontline licensing, why ? I did notice for a brief few weeks that my Frontline Cloud PC showed up on the ThinkPhone, but it has once again disappeared. Text markup I’m not sure if this is an Android thing or a Cloud PC + ThinkPhone thing, but when I mark text (for example an entire paragraph) and want to do an action such as delete that selected text, it doesn’t let me complete that action so I have to delete the text letter by letter instead. Locking the screen When using the shortcut (windows key + L) to lock the screen, or when choosing the option to lock screen from the start menu, it completely disconnects the ThinkPhone from the session even though all I wanted was a lock screen, why is this the default behaviour ? Docking behaviour When docked, the external web camera connected to the docking station is ignored, only the phones cameras are available, why ? Watching videos When watching videos on your Cloud PC via the ThinkPhone, audio lags, you can watch a video but when you focus on what people are saying there lips don’t sync up to the actual audio. Summary The Motorola ThinkPhone is a brilliant phone in it’s own right and offers cool features that any phone efficiando would appreciate. But when it comes to Windows 365 connectivity, this is the icing on the cake. It really does offer you the ability to work remotely using just a phone, by docking to an existing USB-C docking station or by connecting external peripherals. This phone and this solution gets two big thumbs up from me and I’m definitely excited to test the next generation of this release from Motorola and Microsoft.

you can use one boot image, if you check my devmode follow up blog post it shows up it all fits together and yes you can use an x64 boot image, I was simply using x86 at the time for this example

Understood, but with two different boot images, one with and without the startup command, how is that controlled in terms of which one comes down when imaging is initiated? Unless the idea is that one boot image can be used even with the startup command, but bypassed if the deploymentID is not input, then the process continues to the ones not hidden. Also, can the x64 boot image be used? I noticed in your tutorial you used the x86, not sure if that is a requirement or just your choice at that time. Thanks again for your response.

you can deploy multiple task sequences to the same collection with a purpose of Available, some hidden, some not, the hidden ones just 'won't appear' unless acted upon using my script or a modern version of it (Powershell), the thing that matters here (for hidden task sequences) is the deploymentID

I gave this a try but it did not work. Not sure if it is because I used the x64. However, it did raise a concern that I was afraid would happen. When I PXE booted, the correct WIM did come down, but as mentioned in my other post, what if this was someone else and they wanted to access the visible TSes? Aside from assigning to a known collection, how do you use this on the unknown computers collection for baremetal imaging while still using the other normal boot images for traditional imaging?

Apologies, so with the boot image in place and used by our main TS. how would have an additional boot image for the hidden TS work or affect the unknown computers collection when it is time for OSD? My concern or wonder is what happens when a new/BareMetal computer is PXE booted, how is the "correct" boot image selected to be presented for the correct imaging process?

Great post, thanks will give this a try because now that we are deploying win11, but want to keep a win10 ts but have it restricted to "as requested". By hiding it, a ticket would need to be submitted and the deployment ID provided. Is there a way to use another form of "id" that we can rotate let's say monthly? Maybe overkill, but just trying to find a way to keep this as restricted as possible, because I suspect someone will get wise and know the deployment ID is not changing so they won't ask for it anymore. Now that I think of it, maybe we can just create a new deployment every month so the ID get changed. I will see how that works, but definitely open to some ideas.

Ive also been looking for these files for a couple weeks at this point. Any chance I could get a copy? Thanks!