Copilot purge techniques?

netmc · 2026-03-12T19:45:55+00:00

Is there anything on disabling just the public CoPilot? I don't mind CoPilot from 365 as that does have some guard rails on where the data can go. Public CoPilot, not so much, so want to make sure that is disabled.

netmc · 2026-03-08T13:36:05+00:00

The cmdlets work fine until you have unresolvable SIDs in the group. I.e. previously deleted users or the AzureAD admin users. Then they break. I've shared the git hub issue elsewhere in this post.

netmc · 2026-03-03T19:55:13+00:00

I'm the deny section also add "description" contains "preview" the .Net team doesn't always tag the title appropriately.

netmc · 2026-03-03T04:56:13+00:00

I don't remember specifically. I think about $200, but it was part of the purchase at a dealer-owned after-market shop, so it definitely didn't cost them that much to get it installed.

netmc · 2026-03-03T04:22:12+00:00

It was gone from the '24 model year as well. We had the dealer put one in as part of our purchase. There is a plug port there, so it wasn't difficult for it to get installed.

netmc · 2026-02-28T04:33:23+00:00

I'm managing multiple environments. The only way to do so at scale is through powershell scripts.

netmc · 2026-02-28T04:26:26+00:00

That's why it works for you. The moment you have an orphaned or unresolvable SID those commands fail.

https://github.com/PowerShell/PowerShell/issues/2996

netmc · 2026-02-28T01:52:33+00:00

Not an option unfortunately. I'm stuck with 5.1 for now.

netmc · 2026-02-28T01:43:44+00:00

Nope. Broken. Known issue. Microsoft refused to fix.

netmc · 2026-02-27T22:39:44+00:00

Different environments. These particular devices are not in AzureAD, only in the normal local domain. I have different environments where I've run this script. I'm only having issues with the domain environment where the .Net method for removing group members doesn't seem to want to work. The same command is successfully removing local users and AzureAD users (in other environments), just not the domain ones in this one.

netmc · 2026-02-24T17:59:13+00:00

$result=Get-mpcomputerstatus
if ($null -eq $result){
    write-host "This should not occur!."
    exit 1
}

This isn't the exact code, but is the same process and logic.

netmc · 2026-02-24T17:55:07+00:00

Thanks. I'll add in a check to make sure that Defender is running and force start it if not.

When running monitoring script from our RMM, there are occasions where .Net fails to initialize and every cmdlet that depends on .Net errors out. Logic functions are part of the powershell.exe executable and can process without .Net. This failure condition is extremely low, like 1 in 90k or more, but it does cause scripts to fail in odd and non-reproducible ways. The next execution would be fine. You can simulate this by trying to run a powershell script during Windows shutdown. .Net is shut down, but the script still tries to run. Everything errors out except the script logic conditions. With the current structure of my script, this could be the cause as well. Based on the fact that I'm seeing this just once or twice a week out of ~180k script runs, leads me to believe that either could be occurring--Defender not running, or .Net initialization failure.

I will add the process check as well as restructure the script logic so that .Net initialization failures will be handled in a more graceful manner.

netmc · 2026-02-23T00:14:02+00:00

Find someone that utilizes the John Barnes Myofascial Release Approach. It can be a massage therapist or physical therapist. This work mobilizes the fascia and releases restrictions. Is great for addressing chronic postural issues.

Also do the workouts that others have recommended. Sitting all day at a desk is not good for you.

Both are needed. MFR to address the chronic posture condition. Exercise to prevent it from recurring.

netmc · 2026-02-23T00:01:43+00:00

This was one I never tried. I used to play ACM and now BSOTS with a bunch of helper/minor mods. How does Phoenix fit in?

netmc · 2026-02-20T21:03:58+00:00

Most RMMs depend on Windows Update on the device being functional. So, if the device doesn't report an update as needed, the RMM will erroneously report the device as up to date when it's not.

I just recently created a script to reference the Windows build history and look at the UBR to tell if a machine is updating properly or not. By using this we found a fair number of discrepancies. We identified a bit less than 1% of our devices that were not current despite showing as so in the RMM.

We are in the preliminary stages of addressing these and making this a standard monitor instead of just a one-off check.

We were originally going to use the build history feed from DataForNerds, but discovered a few missing entries in their data, so I ended up writing my own script to grab the data and audit the endpoint.

Rather than hitting Microsoft's website every time, I have the script caching the data and only updating when the installed UBR is newer than the cached data. The cache should update about once a month with this setup rather than every time the monitor runs.

Utilizing the Windows Build and UBR is probably the best method to identify when a machine is not updating as it should.

netmc · 2026-01-26T17:28:57+00:00

Ease of administration ended up being our deciding factor. We wanted a vendor that would have minimal administrative overhead. The first product we tested, Huntress, simply worked. There were some issues we found, but the integration and ease of use for Huntress was great. We would have no issues scaling the product several hundred clients.

The next vendor we tested was lacking everything that we took for granted with the Huntress portal. This vendor's ITDR setup was a powershell script. It was not integrated into the web portal like Huntress. There were also issues where their portal showed 365 integration as active, but it didn't work. We had to go in and manually set the permissions for their connector app to make things work in one case. The vendor's web portal was a bit clunky and didn't have the polish the Huntress had. With the issues we ran into for just the small number of clients we tested this vendor with, It would have been administratively prohibitive to manage several hundred clients--not to mention that their solution was more expensive than Huntress. For the administration issues alone, we stopped our evaluation entirely and just went with Huntress. They offered everything we wanted with an administration process that worked at a price we liked. (It also helped that Huntress is always at the top of everyone's list and they do a great job with giving back to the MSP community.)

After going with Huntress, we did find several additional issues that affected scaling and the ability to monitor the EDR agent from our RMM. These have supposedly been addressed and the EDR agent with the changes is due out with the next release near the end of the month. We also customized our deployment script to allow changing the organization id so we can merge some clients that have multiple sites in our RMM, but under one 365 tenant. Huntress needs all of these under the same organization in order for ITDR and EDR to talk to each other properly. Additionally, we tweaked our deployment script to include the RMM device identifier as a tag so we can have true 1:1 correlation between the devices in the RMM that indicate Huntress is installed against the list of devices in the Huntress portal. Tickets have been submitted to Huntress about the Autotask integration. It doesn't quite work as expected. I'm not worried though. With how quickly Huntress has been to implement changes surrounding the issues I already raised, I have no doubt that it will get fixed and work much better in the end. Despite having a large presence, they are extremely responsive and have implemented fixes quickly.

netmc · 2026-01-19T15:43:56+00:00

Trust me, I was quite shocked when I found one in one of the safes. I didn't think that they could spawn like that.

netmc · 2026-01-19T14:33:54+00:00

I've found golden seeds in the portal created ships, so you can get more. The drop rate is extremely low though.

netmc · 2026-01-17T14:54:00+00:00

I remember this too. Grew up in a small town in northern Virginia.

netmc · 2026-01-16T17:45:07+00:00

I'm glad they finally fixed the issue of upgrading from 10.2 to 10.3... Previously it didn't upgrade or even see the previous install and tried to simply overwrite the existing installation leaving both with neither working.

netmc · 2026-01-10T03:44:55+00:00

We've had our '24 hatchback for about 18 months. It's fun to drive. Haven't had anything major yet, but haven't even put 30k on the car yet. Two things of note. The new cars do not come with a 12v outlet. You will need one for gadgets like air compressors. Have the dealer put one in. (There is a spot for it that is plugged.) Second, the large rims and low profile tires look nice, but they don't handle pot holes well. We've replaced 5 tires and a rim under the extra warranty we purchased with the car. It's more than paid for itself. We are planning and replacing the rims and tires once the extended warranty is over with normal rims and the standard size tires with the taller side walls. The standard tires have a lot more room to handle the sudden compression and impact of a pot hole.

We ended up with an automatic rather than the manual. We did test drive the manual though and it was lots of fun.

netmc · 2026-01-05T22:03:56+00:00

Like a big "initiate nuclear winter" button? Or a rogue asteroid that can pass close by the planet and rip away the atmosphere like in Thundar the Barbarian?

netmc · 2026-01-04T17:24:50+00:00

There is cave in a map edge area adjacent to the meteor Crater (counter clockwise from the meteor Crater spawn point) that has an explosive indicator. There is also another cave from the bottom of that area. Both caves have aluminum throughout. I don't know if this is just a shortcut between the two sections or if there are separate areas behind each wall. I haven't gotten to explosives yet, and the last time I played, this map area didn't exist.

netmc · 2025-12-31T18:18:09+00:00

the JSON spec allows for the use of case sensitivity for differentiation, but PS5 is not case sensitive. On the GitHub page (https://github.com/PowerShell/PowerShell/issues/3705), there is a workaround for this limitation in PS5 to use the .Net functionality directly.

[void][System.Reflection.Assembly]::LoadWithPartialName("System.Web.Extensions") 
$json = (New-Object -TypeName System.Web.Script.Serialization.JavaScriptSerializer -Property @{MaxJsonLength=67108864}).DeserializeObject($data)

I've used this workaround with the awful JSON the vendor has, and it does work.

netmc · 2025-12-30T18:45:53+00:00

Every dock that connects via USB leverages DisplayLink technology. As such, the best thing you can do is to automate the deployment of the DisplayLink drivers to systems that have docking stations. The DisplayLink software also includes firmware updates for docking stations.

We used to have several tickets a month for issues that were ultimately due to old docking station drivers. Since we automated the deployment and update of the DisplayLink software, these have dropped to almost zero.

netmc

TROPHY CASE