Best posts made by Mike Davis

@dbeato said in incident response plan:

https://www.sans.org/reading-room/whitepapers/incident/incident-handling-process-small-medium-businesses-1791

I missed this one. That fits the bill.

It's not DNS
There's no way it's DNS
It was DNS

Can't find the original source of that gem.

If you rolled them with a static address instead of DHCP with a reservation, there is a possibility of a duplicate IP address on the network. That will cause symptoms like you are having.

It still applies. If something goes crazy and you get a flood of email, the mailbox database can grow and fill the drive, but your OS disk won't be full, so you can still work on your server.

Verizon has been rebranding the Yealink T46g for a while now and there are a ton of used ones out there. Does anyone know if you can flash the firmware back to Yealink's? The last time I tried to work with one, Verizon had disabled the web interface entirely.

Like @matteo-nunziati says, see if STP is turned on on your ProCurve. If it detects a MAC on two interfaces, it will shut one down. Then it doesn't see it, so it turns it back on. I had issues at one time with a Wireless controller (Nortel) that had proxy arp on that would cause a segment of the network (the switch the wireless AP was on) to get shutdown when a laptop would boot up.

to speed up troubleshooting, do a gpupdate /force and reboot.

@karlita said in spam filter ~ What do you use?:

I don´t even check them, just delete them.

I think people here are looking for domain wide solutions that protect end users from phishing attacks and the like. You may be able to spot a phishing email, but many end users fail....

I have a number of clients where they need a server, but Server Essentials on a small server is enough. Veeam for backup and if the box fails, they are down for an hour or two while we restore to something else. The licensing to go to a second AD server would more than double the cost of the project. (and isn't worth it for them)

https://azure.microsoft.com/en-us/status/

Summary of Impact: Starting at 04:39 UTC on 19 Nov 2018 customers in Europe, Asia-Pacific and the Americas regions may experience difficulties signing into Azure resources, such as Azure Active Directory, when Multi-Factor Authentication is required by policy.

Investigation: Engineers have explored mitigating a back-end service via deploying a code hotfix, and this is currently being validated in a staging environment to verify before potential roll-out to production. Engineers are also continuing to explore additional workstreams to expedite mitigation.

Next Steps: Engineers will continue to validate the hotfix. The next update will be provided in 60 minutes, or as events warrant.

@dbeato I was hoping I could save someone else the time of troubleshooting.

@Dashrender said in Server 2019 Essentials - Domain controller requirement:

@IRJ said in Server 2019 Essentials - Domain controller requirement:

@Dashrender said in Server 2019 Essentials - Domain controller requirement:

@IRJ said in Server 2019 Essentials - Domain controller requirement:

@Dashrender said in Server 2019 Essentials - Domain controller requirement:

@CCWTech said in Server 2019 Essentials - Domain controller requirement:

@Dashrender said in Server 2019 Essentials - Domain controller requirement:

No one here knows - we don't run that software.

No one here runs Server 2019 Essentials?

No - most here run standard Windows Server or some flavor or Linux. Essentials is only for SUPER tiny environments (I think it's limited to 25 connections)... a version that at least with 2012 didn't require User CALs, making it significantly cheaper for super tiny shops that required Windows, but once you hit over 25, you got a HUGE upgrade cost i.e. full server license and 25+ CALs.

Yep. It is generally not reliable either. At least earlier version weren't. Throw all MS services on one piece of underpowered hardware and then throw all your apps over it. What could go wrong?

I guess i was lucky - when they started calling it Essentials - there weren't that many services left - File/Print/AD/DNS/DHCP and what WSUS? that's all pretty typical single box stuff in my mind. WSUS could be shit for sure, but the rest can work together no issues.

Back when it was SBS server and had Exchange and possibly a corporate firewall and SQL server - OMG - yeah, kill me now!.

That's just the out of the box stuff that can be simple solved off windows very easily

Dont forget that these businesses like to throw quickbooks and other poorly made sofware on their Essentials server including these other services which are already too much to have on one box IMO. It's 2019, virtualize

It would be interesting to know if Essentials allows for the install of 3rd party software like that?
Probably does..

QuickBooks is the reason I have so many Essentials servers out there. If the environment is large enough where you can't just make one computer "the server" and share QuickBooks from there, Server Essentials goes in along with QuickBooks Database manager and its 25 year old architecture and you call it a day.

get-mailbox | export-csv
doesn't do it?

@mlnews Eliminating it and stopping production are two different things. We didn't need laws to stop production of steam cars...

How to download something with out getting a drive by download or some kind of malware.

That's kind of like google skills, but from what I understand lots of students get sucked in to drivers.com and the like.

Yes, it was a great meet up. A lot of talent in the room.

Has anyone had any luck deploying Office 2013 Click to Run on a LAN using the Office Deployment Tool kit? Microsoft doesn't have .msi files for this build, and you can't psexec it because it launches a bunch of other processes that need the logged in user to be admin of their machine. (yes, this is their best practice) I was able to push Lync/Skype 2013 via a login script, but Office 2016 isn't working.

In the log files, it's ending with:
01/14/2016 14:50:44.301 SETUP (0x1028) 0x1b9c Nexus Transport a426j Unexpected MsoGetRemoteHostNetworkStatusWithUrlType failed {"RemoteHost": "https://nexus.officeapps.live.com"}

google tells me others ran in to this when their source dir wasn't specified properly in the .xml file. I think my xlm path is right because it's what I used to do the download. This is what I'm using:

<Configuration>
<Add SourcePath="\\server\dfs01\apps\Office2016\OfficeProPlus" OfficeClientEdition="32" Branch="Current">
<Product ID="O365ProPlusRetail">
<Language ID="en-us" />
</Product>
</Add>

<Updates Enabled="TRUE" Branch="Current" />
<Logging Level="Standard" Path="%temp%" />
<Display Level="None" AcceptEULA="TRUE" />
<Property Name="AUTOACTIVATE" Value="1" />
</Configuration>

Does is strike anyone as odd that no one is concerned about the toxic heavy metals that are in PV cells?

It's cool that your goals are clear to you. That's the first step. So now, you're in a great spot to ask yourself, "What do I need to do today to get where I want to be tomorrow?" You can map out your self learning plan and look for opportunities for growth.

Thanks for sharing. I hope it saves others from making a similar mistake. I know I probably would have done just what you did.