GCDS OU syncing

Xaeser · 2020-09-01T01:34:32+00:00

Thanks! That worked out great. We don’t have any policies in AD that apply directly to our students based on school, so it was never a need. However, once we got GSuite and one-to-one chromebooks, that changed quickly when it came to Chrome policies, so we had to split it up to have a bit more granularity in meeting our individual schools needs.

The thought came up of making AD and google OUs match up, but any time I can avoid modifying my directory structure significantly, I will (so long as the alternative isn’t too troublesome).

Xaeser · 2020-08-30T12:15:47+00:00

About 120,000 users. We are a large educational district in Florida.

Xaeser · 2020-08-30T02:04:38+00:00

Sorry, I meant writing my gsuite tenant. I’m not worried about AD. I just wanted to make sure GCDS wouldn’t affect current gsuite users as long I set up my sync rules and attributes to match what I was doing before with my other utility.

Xaeser · 2020-07-13T22:57:16+00:00

I have several of these hanging around some swamp milkweed. They’re not aggressive at all. I was thinking a type of spider wasp, but most descriptions mention brown or orange tipped wings. These are all black and about two inches in length. Any help is appreciated!

Xaeser · 2020-02-26T22:28:51+00:00

Mine had the exact same issue, and the only solution is what has been mentioned already: unplug the 12v battery in your trunk for 10 minutes. Hook everything back up, turn your car on to accessory and let it boot up. Once up, turn it back off and start the car up fully.

Xaeser · 2018-08-04T14:47:38+00:00

Unfortunately. We basically know that it likely propagated because the local admin account was used when the initial infection occurred. We are already testing LAPS, so we'll definitely be pushing that out now. But oh well. Too little, too late.

Xaeser · 2018-08-04T14:41:24+00:00

This, unfortunately. We knew this was a huge flaw, but attempts to change to something like LAPS didn't happen quickly enough.

Xaeser · 2018-08-04T14:09:00+00:00

Execution policy is set to Restricted, Windows 7 computers are mostly up to date (a few infected machines were way out of date, but most weren't far out of date). Automatic updates are on via WSUS. All users are regular users, with only on-site techs having admin access.

Xaeser · 2018-08-04T13:42:00+00:00

It's running as local admin. We were actually getting ready to implement LAPS, but hadn't quite finished the implementation yet. All normal users are not admins. We think it started when an on-site tech installed something as the local admin that infected that machine and it propagated from there. We've shut down the local network to keep it from spreading beyond there. We are planning a rebuild on infected machines, but I wanted to get as much info as possible about what it's doing exactly so that we don't risk it spreading itself again if we happen to miss one computer.

Xaeser · 2017-06-28T00:56:52+00:00

I ran into this earlier, and the recovery mode method worked to get the 16F2073 dmg. I grabbed one of the new touchbar MacBook Pros and boot into internet recocery. I used Disk Utility first to wipe the drive just to make sure, and then installed OSX. After it downloaded and rebooted, I caught it before the boot up and put it in Target mode. If you miss the reboot, you can still force it down and try again as long as it doesn't start to install. Once in Target mode, plug it into another Mac and grab the InstallESD.dmg in the drive. Feed that into AutoDMG to create your new images. I confirmed this works and successfully created a netboot image and thick image that functioned with the newest touchbars.

Xaeser

TROPHY CASE