All Activity

Changed WSUS directory during installation via Powershell. C drive don't have enough space , so created E drive for Wsus specifically. Getting error alerts as below: Log file is located at :\users\name.domain name\appdata\local\temp\wsuspostinstallation is starting Fatal Error: Time out has expired and the operation has not been completed. Note that, I never used SQL data for this, just been using wid and internal directory and deleted during removal Would appreciate any help please. Thanks. RK

I'm having an issue with company portal only showing some of the apps deployed from ConfigMgr (Intune apps show up fine). On a closer look, apps assigned to device collections shows up in both software center and in company portal while apps assigned to users only show up in software center. This issue only occurs while I am on-prem and only on hybrid joined devcies. If I move the device to an Internet connection or force the client into alwaysOnInternet via the registry (or use a co-managed Entra ID joined device) all apps show up in Company Portal. I tried a few different types of deployments; packages, applications, custom, msi, weblinks, deployed as required, deployed as available -no difference noted. Is this the expected behaviour? I'm seeing this both in a prod environment and in lab Setup (both in prod and lab): ConfigMgr 2403 Entra ID hybrid joined devices CMG in place Client apps workload moved to Intune Client setting deployed to use company portal instead of Software Center User / device allowed to retrieve policies from Internet MP allows CMG traffic ConfigMgr in HTTPS only mode policyAgent.log shows device recieving user and device policies Win10 (22H2) and Win11 (23H2) clients

Hi there, I hope you are doing well. I have a question, how can we automate updating the domain profile GUID on remote Windows 10 devices for users who connect to VPN post logon? Thank You, Mike Taku.

Hey there, Welcome to the forum. If you need any kind of help fro me I am here to assist you, feel free to ask me. Thanks, Mike Taku.

Hello Everyone! Excited to join this tech forum! I’m new here, so I’m still figuring things out, but I’m eager to dive into discussions. If I get stuck or need help navigating, I'd appreciate any pointers. Looking forward to learning from and contributing to this community! Thanks for the warm welcome! Mike Taku.

here's some info to assist you https://www.niallbrady.com/2023/12/03/arm64-support-for-osd-added-to-configuration-manager/

We just updating ADK think we were a couple out of date(22H2) version, waiting to do some testing, will keep you updated

did you add support for ARM pxe ?

Hi, Getting this error while installing the SCCM . Need help !!!.

I used this script but when logging off and on it wont show the message prompt anymore. Is there a way to keep this popping up when an user logs on?

HI All We took receipt of a new Surface Laptop 7 to try from Microsoft, but for the life of me i can't get it to PXE boot (waiting for approval) or boot from standalone stick (loops). I am assuming i need to put some additional drivers in from the Microsoft pack but the extracted pack has some 174 folders ...... Also our ADK is a couple of version out of date. but within the version supported 'I think' Anybody had any joy with these.

hi @RobsonM, thanks ! this tool does not migrate any of the users data, but ... it also doesn't delete anything so the users data (files apps etc) is still stored and hidden in their old profile located in C:\Users\<username.old> if you really want to migrate their data then you'll need to customize the scripts and/or use a 3rd party tool for that cheers niall

Hi Niall, Hope you are doing well and thank you for the great stuff you put together 😉 I have a small question, would it be possible to migrate the data from the old profile to the new one created after the migration of the machine? I know all the data will be on OneDrive, but just in case user start to download all the data again and end up facing storage problems.

Introduction In previous blog posts such as this one, I've shown you how to create http triggers within Function apps in Azure to do magic with Intune managed devices, however in my examples for brevity I used secrets, and pointed out that the more secure method is to use Azure Key Vault. In this blog post I'll show you how to set that up so that your triggers are more secure. But first, let's see what Microsoft describes Azure key vault as and explains why it's important. In this blog post the scenario we are going to use is basically how to replace previously created app registration secrets used within your http triggers with Azure key vault secrets. Note: After spending a few days at MMS it was clear that there's an even better way of doing this and that is to use managed identities (step 5 onwards in this post) instead of app registrations to replace the need for expired secret renewals, I'll post an update as soon as I get a chance coming soon. Step 1. Create or reuse a resource group As we'll base this guide upon a previously created solution, we'll re-use our previously created resource group, but if you want you can go ahead and create a new one for this purpose. Resource groups are a way of grouping resources within Azure and to protect secrets within that resource group you'll use key vault. Below I'm highlighting the previously created PC Buyback resource group which we will reuse in the next step. Step 2. Create a key vault Now that we have a resource group, let's go ahead and create out Key Vault. In https://portal.azure.com search for key vaults, select the service from the list of services displayed. Next, click on + Create to create a key vault. In the UI that appears, the first screen is dedicated to the Basics or general information about your key vault. You'll need to select a valid Azure subscription and then select a previously created resource group (or create new). In this example we'll reuse the PC Buyback resource group. You also need to assign the key vault a name, so give it something descriptive (you cannot use spaces). Next select the region where this will be used, and that should match your Resource Group region. Finally select the pricing tier, in my example Standard is fine, you'll only need to use Premium if you need to avail of HSM capabilities (Hardware Security Module), for more info on the pricing plans see here. There are some additional options available relating to how long to key keep vaults after they are deleted and the default settings are good enough for us here. Click Next to see the Access Configuration screen. In here you can once again choose the defaults, as we'll be using RBAC (role based access control) in a later step. Click Next to proceed to the Networking screen. In the Networking screen you have the option to use All networks to allow access from your PowerShell scripts and more, or if in a locked down environment you can select Selected networks which may involve you setting up a virtual network with it's own private endpoint connection. In this example however we'll use the All networks setting. Note: These settings can be changed later in the Key Vaults Networking settings and some of the settings may be disallowed by your own internal policy if an initiative of Public network access should be disabled for PAAS services is enabled in your ARM policy. Click next through the Tags screen and review and create your key vault. After the deployment is complete, select it to see the properties. Step 3. Assign role permissions In your newly completed key vault, click on the secrets section highlighted below, and take note of the permissions error. So even though I'm a Global Admin in Azure I'm not authorized to review those secrets. To resolve this we need to click on Access control (IAM) and assign some roles. You could simplify things and assign the Key Vault Administrator role to your chosen user or group which would give you the access you need to create secrets, keys and certificates, but as we only care about secrets in this blog post we'll assign the following role. Key Vault Secrets Officer To assign these roles in Access control (IAM) clcik on + Add and select Add role assignment from the drop down. Next search for key vault in the search field, and select Key Vault Secrets Officer from the list. Click Next and then click on + Select Members and browse to your chosen user Finally click on Select and then select Review and Assign. At this point you can now select the Secrets option in your key vaults Objects node and no longer get permission errors. It will state that there are no secrets available but we'll get to that shortly. Next select Key Vault Security User from the list and repeat as above (add role assignment). Step 4. Create a key, secret or certificate Now that you've configured your key vault, it's time to create your first resource, this can be a key, secret or certificate. Note: As we are replacing previously created App registrations secrets with azure key vault secrets we'll select that option for this blog post. Therefore, you'll need to know your previously created secrets when you created them back in the PC Buyback tutorial, steps 7 and 8 here. In key vaults secrets, click on + Generate/Import to start that process. Give the secret a suitable name and paste in the value from the previously created app registration secret. We can see that secret taken from a http trigger within my PC Buyback functionapp. The contents are blurred. and paste in that value into your key vault secret creation. You should also configure the activation and expiration date and make the expiration date to one day before the actual secret expires to allow you time to recreate a new one. Below you can see the app registrations secret expiry details. and that is reflected (minus 1 day) in the key vault secret creation. after creation, your secret is listed in the key vault. Step 5. Grant functionapp permissions to consume the key vault Next we'll grant permissions to our previously create functionapp to allow it to consume the key vault. To do that, open up the PC Buyback functionapp and click on the Settings drop down, select Identity and change the Status to On. After clicking Save you'll get the following message. Click Yes to proceed. After clicking Yes the results are displayed. Step 6. Grant the key vault permission Next open your key vault and browse again to Access control (IAM). In the role assignments click on Add and add the Key Vault Secrets User role. Click Next and select Managed identity, then in the wizard that appears select function app from the managed identity field and select your PC Buyback function app. once done, click Select and your PC Buyback function app is added. Don't forget to click on Review + Assign. Step 7. Configure function app environment variables Open up the previously created PC Buyback function app and expand Settings, select Environment variables and click on + Add, give it a suitable name such as var_pcbuybackappregistration. paste in the following string in the value line @Microsoft.KeyVault(VaultName=mykeyvault;SecretName=mysecret) edit the VaultName and SecretName values to match your environment... click on Apply when done. and click Apply again once the environment variable is added. At this point you'll need to confirm the change as it needs to restart the function app. Step 8. edit the http triggers Now you are finally ready to apply the key vault secret variable to your previously created http triggers, so let's do that. Select a trigger and review the contents, find the line that pointed to the Access Secret and replace the with the new environment variable, like so: $env:var_pcbuybackappregistration when $env:var... is your environment variable created above. Below is the result, and after saving the code and doing a Test/Run we can see it's working just fine using Azure Key Vault, Summary Using app registration secrets in your http triggers is a bad idea, use Azure key vault to protect those resources, this blog post helps you to to just that. See you in the next one !

invalid namespace in WMI, i would do a manual uninstall of the ccm client, and do a software updates reset using WURESET "should be on github" "Manuel Gil" I believe. After WUREST, reboot, reinstall the client, and view logs while it installs. Keep a copy of CMTrace on your desktop before deleting the CCMClient.

Hi Everyone, Can we add 2022 key on 2016 server and what should be the command to add the key

what does the log file reveal ? can you attach it here

I have followed all steps, but when the script runs it keeps saying: "Precentage Encrypted 0%." and the Autopilot will timeout. This is on a Microsoft Surface device (Surface Laptop 5). Also I tried to run the PowerShell command Clear-Tpm at the beginning of the script but it didn't make any difference. Great job btw, thanks for all your work!

Hi, can anyone help here I have tried with this command to install locally .\ccmsetup.exe /AllowMetered /MP:XXX SMSSITECODE=XX the installation starts but then performs a roll back now i see that the computer shows a green tick but inactive, however ping and c$ does work from server please find log attached ccmsetup-20241010-153416.log

Hi, Did anyone solve this. Getting same error after migrated to new hardware (New hardware created with same Hostname and IP address)

bumping back up as i'm trying this again. Imaged fresh computers and am no longer receiving that error pop up saying bitlocker could not be enabled. it's all silent now... so i've got that going for me. I am however still getting the bitlocker "unable to connect to the MBAM recovery and hardware service" under > microsoft windows mbam / admin in event viewer Anyone else got any ideas? https is enabled and cert bound on the IIS site on the MP.

They're all using the same image. So same OS version and same client version.

Hi Anyweb, I've managed to create and get the HTA to open in OS, however my issue is that is in the background and the user don't/won't see it unless they close all their open windows to show the HTA. Any and all assistance would be greatly appreciated.

is there anything different OS wise with the 50 that have issues versus the rest that don't ? are they using the same client version ?

Hello , The CVE dose not applied to my version. Loading the driver package to the boot image via CMD did not work as well. what works for me is ,I created the .cat file for the driver and signed with our CA( dont know if that needed). added it to the MDT out of box driver. Hope that will help other, Thank you Best regards,