Posts made by PSX_Defector

@tim_g said in Office 365 Email Gone After Forced Logoff:

@psx_defector said in Office 365 Email Gone After Forced Logoff:

@scottalanmiller said in Office 365 Email Gone After Forced Logoff:

@jaredbusch said in Office 365 Email Gone After Forced Logoff:

As I recall, your O365 accounts were tied to some AD sync server.

This is all the fault of whoever set tings up and never properly disconnected stuff.

Microsoft themselves set that up without permission.

Let's say that I know that's not the case, for very specific reasons you should know already.

MS never sets up your stuff. Especially with AD Sync, considering it has to be installed locally.

We use AD Sync for O365, and that has nothing to do with licensing.

If I create a new AD user, it gets synced to O365, but is unlicensed until I go in and manually assign an E1 or E3 license.

It's like that by default, and I want to keep it that way... so I don't know if there's a way to assign those licenses on-prem or not. I don't want anything automatically assigned.

https://gallery.technet.microsoft.com/office/Assign-Office-365-Licenses-b7385ebe

Anything can be done if you know what to do.

@scottalanmiller said in Office 365 Email Gone After Forced Logoff:

@jaredbusch said in Office 365 Email Gone After Forced Logoff:

As I recall, your O365 accounts were tied to some AD sync server.

This is all the fault of whoever set tings up and never properly disconnected stuff.

Microsoft themselves set that up without permission.

Let's say that I know that's not the case, for very specific reasons you should know already.

MS never sets up your stuff. Especially with AD Sync, considering it has to be installed locally.

Federate with Azure, turn on multifactor, hit the gym.

Network stops or the network drops?

If it stops, try static config.

If it drops, you got a flapping port on the switch. Set it to 10Mbps half, go up from there. Replace jack, swap port, etc.

Best practice isn't up to date.

Set it to PCI 1.2, that disables TLS1.0, all the AES stuff, etc. etc. You can also disable them manually in the first screen.

@travisdh1 said in IIS Security setup:

@psx_defector said in IIS Security setup:

@travisdh1 said in IIS Security setup:

Realized the Church I work part time at is still on 2012 R2. It's only being used as a file server right now, so it's probably jump ship.

Why?

2K12R2 is still fully supported by Microsoft. Has continuous updates, battle tested, and you are talking about a file server. There is little to no reason to change it out except because you want to get some feature in 2K16, which for file services, is nothing.

Who said I was going to 2K16? That's a lot of licensing money at a place so small for no benefit, imo. When the time comes for more CALs, I'll probably change it out to a KVM host and just remove the Windows Server entirely.

Apples and Chryslers.

Removing a Windows server because its out of date, that's one thing. But switching it to KVM is a completely different beast. One is for compliance issues, the other is to get higher density of compute.

You are calling 2K12 old. It's not. The only reason to switch would be because of shiny object syndrome.

@krisleslie said in Is there a legal age limit to computer systems when HIPPA is concerned?:

Well with the Intel fiasco with the cpu's, what's the likely chance they will update a system such as a Gateway profile 5.5? For a small non profit I am working with they had half of their existing systems running Windows XP and a hodgepodge of 7 and 8, 8.1.

I have installed Windows 10 and will be finishing up their deployment with a few months.

Given that there is a patch for Spectre/Meltdown for the OS side of things, and you can mitigate it via switches in Windows, the hardware is not the problem.

@scottalanmiller said in Is there a legal age limit to computer systems when HIPPA is concerned?:

@psx_defector said in Is there a legal age limit to computer systems when HIPPA is concerned?:

HIPPA is how you handle your data, not how you handle your hardware. Closest thing would be not patching issues because they are no longer supported.

And does patching something make it "older" or "younger"?

It's like putting in a new engine in a car. Yeah, it's patched against problems, but you are still driving around a 20 year old car.

@travisdh1 said in IIS Security setup:

Realized the Church I work part time at is still on 2012 R2. It's only being used as a file server right now, so it's probably jump ship.

Why?

2K12R2 is still fully supported by Microsoft. Has continuous updates, battle tested, and you are talking about a file server. There is little to no reason to change it out except because you want to get some feature in 2K16, which for file services, is nothing.

https://www.nartac.com/Products/IISCrypto

Use IIS Crypto. Set it to the level you are looking for. Has templates for the settings. Just apply and reboot.

Coax cable means lots of things. What kind of cable? How high quality is the cable?

You could covert it over to ethernet, depending on the quality/length. But most coax should be sufficient for enough high res video, just depends on the camera.

Why would something being old would cause it to suddenly not be HIPPA compliant?

HIPPA is how you handle your data, not how you handle your hardware. Closest thing would be not patching issues because they are no longer supported.

Here is the one thing that will shut the dumbasses up about RDP being "insecure".

Multi factor authentication.

Microsoft even supplies wonderful application for it.

https://azure.microsoft.com/en-us/services/multi-factor-authentication/

Eliminates all the shit password problems, even if its 'password', has a mobile app to just hit a button to approve login, and is pretty easy to set up to boot.

@dave247 said in Constant WSUS issues (Connection Errors):

I'm so used to them not helping me...

That might be a problem going forward. All event logs have information and tell you every possible problem, just have to get used to reading them. Never just gloss them over.

I'm assuming you are opening the snapin via the local machine versus a remote. That screen happens when you can't connect to it. Your error in the event log means that it can't connect to the site via SSL. Open IIS and make sure that it has a self-signed cert generated for the site. Or make sure the site is up on HTTP and open it that way in MMC. That should fix the problem.

Well, decided that I should network and shit. I'm crashing your party. Fuck your couch Charlie Murphy.

Only every once in a while.

Although going to Austin and crashing a party sounds like a wild PSX appearing situation.

Was just talking to someone about the Scale booze cruise. Maybe I should crash the party on Wednesday, not like it takes a long time to drive to Austin.

The actual SW event, meh, not worth my time or money, even if I crashed it. Pretty much repeat repeat repeat from the last 5 years. Has anyone told them that yet another set of Powershell breakouts are not that interesting?

@texkonc said in Hurricane Harvey:

@scottalanmiller said in Hurricane Harvey:

@psx_defector said in Hurricane Harvey:

@scottalanmiller, @Dominica, @Texkonc, @NetworkNerd, and I are far enough inland that we won't get any thing more than a scattered shower or thunderstorm from one of the arm bands of Harvey.

Nice to see that I'm forgotten...

You are even farther north than me.

And me.

Technically, you are further north.

@nerdydad said in Hurricane Harvey:

@psx_defector said in Hurricane Harvey:

@scottalanmiller, @Dominica, @Texkonc, @NetworkNerd, and I are far enough inland that we won't get any thing more than a scattered shower or thunderstorm from one of the arm bands of Harvey.

Nice to see that I'm forgotten...

And how often are you on here? I forgot that you're on here.

http://mostlyscience.com/wp-content/uploads/2015/05/Ralph1.png

@scottalanmiller, @Dominica, @Texkonc, @NetworkNerd, and I are far enough inland that we won't get any thing more than a scattered shower or thunderstorm from one of the arm bands of Harvey.

Nice to see that I'm forgotten...