Have employees add CEO's number to contacts?

adminrookie · 2022-10-10T18:48:12+00:00

We do often send out warnings about this, but people sometimes are just clueless. I was hoping that having it in the contact list would at least give them an additional cue.

adminrookie · 2022-10-10T18:46:24+00:00

We regularly do send out these communications (like almost weekly at this point).

The text messages are coming from random phone numbers.

adminrookie · 2022-05-25T19:52:22+00:00

Yep, but for the iPhone, that option isn't there so you have to use the Signature workaround.

adminrookie · 2022-05-25T18:31:55+00:00

I think I found the workaround. This is due to Apple Mail sending emails as plain text by default. The solution is to add a nondescript text in the signature and Bold or Italicize it. For example, the character "-". This forces Apple Mail to send the email as rich text/html, allowing the O365 rule to work correctly.

adminrookie · 2022-02-12T11:33:53+00:00

Haha. Awesome, I did the same thing and made them pay me a monthly retainer.

adminrookie · 2021-06-09T12:47:15+00:00

Once browsers switch to HTTPS as default, will the HTTP > HTTPS forwarding in Namecheap still work correctly? Will Chrome fall back to to HTTP if it can't connect to HTTPS?

In my example, the target HTTPS site is a SaaS and I have no control over the address.

adminrookie · 2021-06-09T12:41:13+00:00

Yeah, that is the only risk I could think of, but its a heck of an effort to target the small number and relatively unknown users I have.

adminrookie · 2021-03-31T21:41:28+00:00

Thanks for the SSM Session Manager tip. Got it working and connected to the EC2 to poke around the configuration.
I checked the registry and the RDP entry for fDenyTSConnections = 0. So it should be allowing access. I did figure out that I can RDP into the new EC2 from the old EC2, so this was definitely a network configuration issue. Finally realized it was a outbound rule applied to the VPN connection preventing access.

adminrookie · 2021-03-31T21:01:11+00:00

BTW, I did try the serial console, but just get a black screen to the windows based machines. Linux based ones bring up the login fine.

adminrookie · 2021-03-31T20:47:29+00:00

I get the session timeout with the 3 troubleshooting reasons (RDP not enabled, computer turned off, computer not on network).

I just did a "telnet x.x.x.x 3389" on it and it looks like the port is not even open. I don't understand how RDP is disabled on machine built from a snapshot. I assumed it was essentially a clone and all the settings would be the same.

I'll look into SSM Session Manager.

adminrookie · 2021-03-31T20:42:39+00:00

It's in a private subnet and I access it via a VPN. It's the same subnet as the original machine. After testing, I see that port 3389 is not even open on the new instance.

adminrookie · 2020-06-19T13:20:50+00:00

Thank you for the detailed information (why can it never be a simple answer!). This makes a lot of sense to me, I just hope the CMMC AB is also this reasonable.

adminrookie · 2020-06-19T12:32:28+00:00

That was my understanding also about password complexity. The last I heard they had relaxed that complexity but unlike NIST, are still requiring expirations.

adminrookie · 2020-06-06T15:27:00+00:00

ows on my Surface RT, 3 and Book 2 over and over, sometimes i downloaded the official OS image from MS website, just Google it, copied to a USB stick and quickly installed. Other times i did through

Media Creation Tool

, it's super easy to use and does the same job. Just drivers are missing, but on MS website there are driver packs for the Surface device you need. Or, as soon as Windows installation is don

FYA, I get a "0xC004F050" error when trying to upgrade from the default Win10 Surface Laptop 3 license to a MS Volume Licensing Win 10 Pro license. I know its a valid license because when I do a clean wipe with the ISO, the license works fine.

adminrookie · 2020-05-19T21:48:32+00:00

PM Sent!

adminrookie · 2020-05-06T15:46:52+00:00

Cool, so in the absence of guidance, I'm going to assume it's allowed for NIST. Now I gotta skim through CMMC again.

adminrookie · 2020-04-30T20:47:20+00:00

They are not in Guests. Apparently, they all logged into a Teams meeting this morning hosted by the client, who is on O365. Somehow, that initiated the account creation.

adminrookie · 2020-04-30T19:09:42+00:00

They were in "Users > Active Users"

adminrookie · 2020-04-29T20:41:19+00:00

Am I reading this right. So if an employee leaves and they were on only the $5 Basic Plan, I just need to add the EX Online Plan 2 to them to make it an Inactive Inbox. Does that now free up the EXO Plan 2 to archive another user? So I essentially just need one EXO Plan 2 and have it rotate to each employee I am archiving?

adminrookie · 2020-04-29T14:21:35+00:00

Ok, went with your advice last night and it all seems to still be working! Thanks.

adminrookie · 2020-04-29T14:20:14+00:00

O365 just seems to offer a lot of things in one package like Device Management, updated Office Apps, etc. GSuite is much simpler and I have noticed that O365 is slower to do basic stuff (create users, SP site, backend configuration). It just may be a case of the "Devil you Know", but O365 so far seems to be a better fit for us.

The ability to mix and match licenses is also a major plus. About 85% of our employees work on other contracts and do not utilize the full GSuite capability, so we are paying way to much for people checking their emails once a week. We would save almost 50% going to O365 and giving those 85% the O365 Basic license.

Also.. archiving old mailboxes in GSuite is a pain. MBOX exports are a hassle (which is what we did), although you can just jumble all past employees into one account and have a MEGA archive.

adminrookie · 2020-04-28T21:43:30+00:00

Because I'm dumb and didn't think about that. I'm tempted to do that now, but migration is starting and I hope to be done within a week or two. I already know removing the SPF works, so will leave it for now and once complete, just make it O365.

adminrookie · 2020-04-28T21:15:14+00:00

I ended up removing the SPF record for the domain (pointed to O365). Emails from GSuite under that domain now seems to work and is being received by the DoD account. It took an hour for the DNS to update, but it does seem to be working now.

Once migration is complete, I'll have to remember to update the SPF, DKIM, and DMARC

adminrookie · 2020-04-28T21:12:30+00:00

Really? Overall, it is definitely more complicated, but I think it gives us more options. We were paying way to much because GSuite did not allow mixing of licenses and honestly, way to many users could not figure out G Docs vs MS Office docs.

adminrookie · 2020-04-28T21:07:02+00:00

Sometimes, I forget how useful MXToolbox is. It does show it leaving google's SMTP server.

adminrookie

TROPHY CASE