jtotheb

If you haven't got fairly current ADMX installed you can also do it via a reg key HKLM\SOFTWARE\Policies\Google\Chrome Value: GenAILocalFoundationalModelSettings DWORD 1 Then in chrome://settings/system you will see On-device AI is disabled and showing as a managed policy.

It should. You don't need to migrate the config database over, it's entirely optional. Everything should still work as it was if you're running your config DB on MS SQL and PostgreSQL is also installed but not in use.

It installs it, but it doesn't automatically move your configuration database onto it if it is already running on MS SQL.

When I performed this it installs the PostgreSQL, but if you reconnect to your SQL config database during the upgrade it will still be using that. Look in the History node -> System. Look at your most recent Backup Configuration Job and open it. Up near the top you'll see a line: Active database type: ***** which should show you what the active database is. Check the Veeam support/the manual for the full steps, but the high level steps for migration are: 1. Have no running jobs. 2. Disable your jobs so that one doesn't start during the migration. 3. Take a config backup. 4. Restore the config backup from the Veeam menu, but to the PostgreSQL database that was created by the installer. 5. Wait for it to finish. It's clear from the onscreen messages that it's converting it to PostgreSQL. 6. Restart. 7. Stop MS SQL service and disable MS SQL Server from loading at startup. 8. Restart again. 9. Check Veeam is all happy. 10. Enable your jobs. 11. When you're happy everything is running as planned after a soak test you can uninstall MS SQL Server if it was only used by Veeam.

I must be getting old. It was in the back of my mind that I'm sure I've done this before (make a bootable USB to connect to an MDT network deployment) but rather than trial and error it I thought I'd run a quick Google search. One of the results was my own forum post from 6 and a bit years ago. Fingers crossed I was right

We create the Computer Device in SCCM prior to imaging and use the SMBIOS GUID when creating the Computer Device and leave the MAC blank. However, we did manage to buy a batch of cheap devices that all came out of the factory without having had the SMBIOS GUID programmed so they were all identical! This gave us the same issue as the duplicate MACs would have and took us a bit longer to discover as we'd never had machines delivered with identical SMBIOS GUIDs before.

Another Microsoft option is Migration Manager which is driven from 365 with an on-premise agent that does the data moving rather than it being an application like SPMT. The big plus is you can have multiple migration agents installed (assuming you have the resources) to really shift the data up into OneDrive. The end result is the same though. https://medium.com/@serenisoft/understanding-the-differences-between-migration-manager-and-sharepoint-migration-tool-spmt-for-72d43e0c3d75 It was a bit quick and dirty but I used some really basic Excel concatenate action to build my source Homefolder UNC paths and target OneDrive URLs and then put those into the Upload Template CSV from Migration Manager (which looks near enough identical to the SPMT one).

This might come too late if you've already done it but Microsoft's Storage Migration Service will shift your data retaining the permissions, recreate the shares with the same permissions, rename the new and old server and even migrate the IP configuration to the new server so it slots in as a direct replacement. However, you will need an extra orchestrator machine that actually manages the migration between source and destination servers. https://learn.microsoft.com/en-us/windows-server/storage/storage-migration-service/overview

We use GPP to push out a settings file that lives under appdata\Code\User\settings.json There's a line in there that points to the Python interpreter. You could take the file from an account with elevated privileges and work backwards. Ours looked a bit like this: { "python.defaultInterpreterPath": "C:\\program files\\python310\\python.exe" } You can also use that file to control loads of other settings if you play around with an elevated account and see what gets written to it.

Good spot! The addresses on the admin portal page where you would actually configure and test it are currently wrong. New addresses have been added to their KB. https://support.roombookingsystem.co.uk/article/104-how-to-set-up-ldap

Hi there, sorry to jump in but once you had registered the application ID in Azure did you have to use a global admin in "add the search base" section? We're being asked to do this, but that seems very odd given that the app has been delegated the permissions to read the directory.

You're probably well past the point of using it now, but even the last released version of Intelligent Provisioning for the Gen9 only supported Windows Server 2019 so if you were thinking of trying to update IP don't bother.

To turn off multicast deployment right click the Deployment Share in the Deployment Workbench MMC and bring up the properties. On the general tab there's a tick box for "Enable multicast for this deployment share" that will need unticking.

We're in a similar boat. I have the sinking feeling that the information that's released when it's available will be "LOL, use Intune now."

You would not do this with standard VLANs. You can isolate clients in the same subnet using Private VLANs, but it is not something you would normally use in a LAN. It's more commonly used in service provider environments to segregate customer equipment from each other when they all reside in the service provider's subnet.