caffrey

Yes via enablement package KB5003791 http://b1.download.windowsupdate.com/c/upgr/2021/08/windows10.0-kb5003791-x64_b401cba483b03e20b2331064dd51329af5c72708.cab My 0 day test ring isn't working though

I've a USG , unifi switch 8 , switch 8-POE-60w and a U6 lite I'm after another u6 lite, 16 port poe lite and a dream machine pro They don't seem to be doing anything about replacing the USG with something new TBF I'm considering other options too Shame it's not rack friendly but I do like it

I want to upgrade my Unifi stuff at home, but with global supply and demand being an issue I doubt there will be any bargains :/

Does it mean the 11th October 2021 21h2 update.... No under system requirements it says

It's just a azure vm print server that uses local ad to authenticate the clients. I don't like the setup as there are lengthy delays releasing print jobs (Can take minutes) - I'm hoping that there maybe some speed improvements upgrading the AAD Connect

Slight hijack so apologies Anyone upgraded from an early version to a later version without a problem ? Server I've took over has version 1.3.21 on it and I want to upgrade to the latest (Or even v2). I've download some older versions so I can update in increments if needed. Oh I'm doing this on a Azure VM with no backups too... (Not my doing)

I suppose you can mitigate some of the risk with trusted servers etc.

But does this expose the original vulnerability ?

You can get the MSI here https://docs.microsoft.com/en-us/microsoftteams/msi-deployment

You running with teams wide installer ? From memory I think it's msiexec /i Teams_windows_x64.msi ALLUSERS=1

Short version I pull the device ID from the machine at OOBE (https://www.thelazyadministrator.com/2020/01/27/get-a-new-computers-auto-pilot-hash-without-going-through-the-out-of-box-experience-oobe/ Import the device into intune, apply a deployment profile (Usually with a dynamic group via a group tag) Then at oobe do the konami code (press windows key 5 times) and pick windows autopilot provisioning then after it provisions, reseal then hand to user This is full AAD not HAAD

I liked Kyocera Taskalfa, had no problems with them. The only thing I had to do with them in the first year of the contract was just installing toner etc. It depends on your contract with the supplier I guess Don't get me started on Xerox, meh

Anyone want to share their update ring settings?

It can take longer, our fleet took more than 72

Has anyone come across this before ? I'm testing an Edge configuration profile and I have the Automatically import another browser's data and settings at first run setting enabled Problem I have is that it doesn't seem to apply if the user has already has a Edge profile and the only way I've got the setting to apply is by running "msedge.exe --force-first-run" ,then it works as advertised Is this correct or is there some other way round it ?

@Katy has a good blog on it @garethedmondson https://katystech.blog/2021/06/wufb-and-update-compliance/

It's what every Goth dreams of

It just decided to pick the moment that I'm learning about intune and whiteglove... I even went as far as bios updates

Is this why I was getting Attestation issues ? , thought it was just me and the rubbish hardware...

I'm not too sure of the history of patching in this new job, although I don't think any has been done for a while...

Killed it here too papercut print queue. Uninstalling the update fixed it

Think I figured out what was going on, it seems these devices were enrolled when there was still a Assign Profile option in intune (before it was endpoint) ? I changed the dynamic group rules to (device.enrollmentProfileName -eq "AutoEnrol") or (device.devicePhysicalIds -any _ -eq "[OrderID]:MYGroupTag") And added the group tag MYGroupTag to the enrolled device and it applied the profile fine and put the device in the correct group

I'm a bit green with Endpoint manager but since taking on this tenant I've ran into a few things I don't understand - I'm not even sure I'm explaining this right! In Endpoint manager I have a Dynamic Security Group that has the rule :- (device.enrollmentProfileName -eq "AutoEnroll") This group has members in it (PC's), but I can't move \ delete them because it's a dynamic group The deployment profile (Autoenroll), has the Dynamic Group set as an included group. I'm guessing when enrolling the device you can choose a group but I've not tested that far yet Question is, how do I move the device to another group ? I just want to make sure the device is picking up all the proper config profiles like the rest of the fleet. It's a tonne easier on GWFE for sure.

So I've just started a new job with an existing tenant, the domain is all AAD with a single VM with Papercut that has an AD connector. The PC's are all managed through Intune with no AD group policies I'm not sure what my predecessor has done or not done, so has anyone got some tips ? E.G. best practices, tricks and what I should be looking at first ? I've managed to work out how to deploy app including win32 apps, so it all seems straightforward enough but I've got to say, Azure Portal is a mess...

+1 on the Google cloud shell, more secure that way too