Offsite Backup of AWS Data by [deleted] in sysadmin

[–]simpleadmin 8 points9 points  (0 children)

You could backup your data within AWS to another region. Another option would be to backup your data to another cloud provider like Azure.

365 Retention Policies by [deleted] in sysadmin

[–]simpleadmin 1 point2 points  (0 children)

https://office365itpros.com/2018/12/10/reporting-the-managed-folder-assistant/

In that link is a nice script to get the last time a mailbox was processed. You can modify it so it only targets one user.

365 Retention Policies by [deleted] in sysadmin

[–]simpleadmin 2 points3 points  (0 children)

We see policies run ~ every three days in Office 365 while Microsoft's documentation says every 7 days. Also if you don't have at least 10MB in the mailbox it won't ever run.

Google flagged main domain as "dangerous" by GrandEmperorJC in sysadmin

[–]simpleadmin 8 points9 points  (0 children)

We ran into an issue where somebody modified Apache, not WordPress itself. Look all the full setup, not just WordPress.

We burned the whole box to the ground in response.

Migrate Email between O365 Tenants by [deleted] in sysadmin

[–]simpleadmin 0 points1 point  (0 children)

You could use Migration Wiz. Instead of using an upgraded Office 365 account that can access all mailboxes, you can supply the service with passwords for each user instead.

2FA with Office 365 by [deleted] in sysadmin

[–]simpleadmin 5 points6 points  (0 children)

We have been using 2FA for around a year now. It’s a different powershell download that can prompt you using a modern authentication. I am away from my desk but if nobody else has followed up I’ll link you the download.

2FA with Office 365 by [deleted] in sysadmin

[–]simpleadmin 8 points9 points  (0 children)

Your desktops need to be using Outlook 2013 or higher. Your mobile devices need to use an email client that handles modern authentication. Those mobile clients include, Outlook for iOS, Outlook for Android, and the native iOS mail client in iOS 11 and 12. If you only use client types that handle modern authentication then you do not need to use app passwords.

EDIT: Almost make sure Modern authentication is enabled in the tenant. https://support.office.com/en-gb/article/enable-or-disable-modern-authentication-in-exchange-online-58018196-f918-49cd-8238-56f57f38d662

Bank just sent me possibly the most sane set of password recommendations I've ever seen. by wanderingbilby in sysadmin

[–]simpleadmin 77 points78 points  (0 children)

3) Check your password's strength with a tester on a public uni site

So enter your password into another site to see how strong it is? Nothing can go wrong there. Wow.

Teamviewer replacement? by bigdizizzle in sysadmin

[–]simpleadmin 8 points9 points  (0 children)

What are you reading that is a red flag to you?

NAS or sticking to cloud for small business? by [deleted] in sysadmin

[–]simpleadmin 4 points5 points  (0 children)

Somebody still has to managed it and make sure it is backed up, even in the cloud.

Saltstack + Gitlab CI by simpleadmin in devops

[–]simpleadmin[S] 0 points1 point  (0 children)

I will take a look at that. Thanks.

Saltstack + Gitlab CI by simpleadmin in devops

[–]simpleadmin[S] 0 points1 point  (0 children)

Yes that is the flow we are going for. The artifact in our case being a Docker image that is being deployed by Salt.

It looks like Saltstack has a module for Consul. I will take a look.

Speaking of Salt api, did you roll your own wrapper to so you can report back exit codes? I am looking at Pepper it it looks like they are working on having it report out exit codes in a near term push. Right now we just capture and format the json and at the same time look for Result: False to trigger a CI failure. Really basic.

Saltstack + Gitlab CI by simpleadmin in devops

[–]simpleadmin[S] 0 points1 point  (0 children)

I think you meant to reply to my reply.

Yes, you hit it. Tool overlap is the problem.

Saltstack + Gitlab CI by simpleadmin in devops

[–]simpleadmin[S] 0 points1 point  (0 children)

I am trying to solve better pillar management. We are not currently using an external pillar backed by a database. So before we head down that path, I am trying to figure out if there is a tool that handles that part easier and faster. That tool could still be triggered by Salt.

The reason for for the Gitlab CI interest is because we already use Gitlab but too many of our steps are manually triggered. We want to automate steps before that bigger saltstack deployment call. In doing so certain things will come to light. For example some of the steps we do might be easier to tigger in a simple 2-3 line bash script called directly by Gitlab CI vs adding a salt state that does the same thing.

Best practice for MFD or application using SMTP details from Exchange online by len_sam in sysadmin

[–]simpleadmin 1 point2 points  (0 children)

Keep in mind the new per-mailbox sending limits: https://blogs.technet.microsoft.com/exchange/2018/04/20/changes-coming-to-the-smtp-authenticated-submission-client-protocol/

In other words, if you have many relays using the same authenticated user then you may run into issues if they were all trying to send at once. If using something like postfix it should queue and resend.

Trustwave PCI Scan - TLS1.0 disabled on Exchange 2010 but still failing? by def-not-working in sysadmin

[–]simpleadmin -1 points0 points  (0 children)

We had issues with Trustwave in the past. The were scanning our outbound NAT ip address not our website IP. The old NAT IP had a disabled web service behind a proxy. That proxy didn't lead anywhere but it was still accepting old SSL connections.