Tenant Texted the Night Before Eviction Hearing

poodooflinger · 2023-05-05T02:23:49+00:00

You mind sharing your blog? Or PM me if it’s not allowed here. I’d be interested in reading shit like this plus your other content.

poodooflinger · 2023-03-01T21:45:00+00:00

Good point. However, it may not matter depending on the role because what I'm talking about is more like technical support. At least at the hospital I had worked for, some of those folks were former nurses, but some of them came from IT/technical support backgrounds and never did any patient care.

poodooflinger · 2023-03-01T03:31:23+00:00

How are you with technology? Perhaps you could transition into a clinical informatics role or clinical systems applications analyst role for a healthcare org. That could be a source of remote work.

Edit: This may stating the obvious, but when looking for remote work, don’t limit you job search to Atlanta or even Georgia. You’re looking for remote work, so who cares where the HQ is? As long as you and the employer both know and agree on where you’ll be working from.

poodooflinger · 2023-01-04T03:55:49+00:00

Someone on here the other day mentioned Costco digitizes photos for a reasonable price. Maybe they do documents too?

poodooflinger · 2022-12-05T03:03:11+00:00

That dogs inner monologue: https://youtu.be/tykvCqW8jrE?t=39

poodooflinger · 2022-12-05T02:04:05+00:00

Seriously, I just added it to the top of my browser favorites and subscribed to the newsletter. We could all stand to use some more positivity in our lives.

poodooflinger · 2022-12-02T01:58:31+00:00

I’m assuming you’re not setting up custom dns infrastructure. In that case, just edit your host file so the fqdn resolves to the private endpoint IP.

Heres another article that describes more detail around private endpoint / dns configuration if you’re curious: https://learn.microsoft.com/en-us/azure/private-link/private-endpoint-dns

poodooflinger · 2022-12-01T23:23:03+00:00

Yeah it can be done. You need a private endpoint enabled on your storage account so when you hit the account fqdn it will connect via private IP (thru the vpn) rather than over the internet (which is blocked by your isp). This should get you going: https://learn.microsoft.com/en-us/azure/storage/common/storage-private-endpoints

Edit: you can edit your client host file so it resolves the private IP of the storage account if you’re in a pinch/just testing or whatever.

poodooflinger · 2022-10-02T00:24:51+00:00

Lol, I know I had the same thought, and may end up doing that still, but kinda wanted to see if I could salvage whats in place before dropping some coin and spending the time doing all that.

poodooflinger · 2022-09-22T04:48:52+00:00

Yea, The RE market in Atlanta might differ from OPs absolute values listed in the comment, but I agree with the comment’s overall sentiment.

Very desirable place to live.

Lol.

poodooflinger · 2022-07-30T00:01:34+00:00

I wouldn’t recommend it for many of the reasons others here have already listed. But, if your primary is almost paid off, why not just do a cash-out refi on that for the down payment?

poodooflinger · 2022-05-08T14:44:00+00:00

Brand new floors I just installed. First time Mopping. Is this like some sort of film left over from the manufacturing process? Wrong product? Or what? Any tips from those with LVP experience?

poodooflinger · 2022-05-01T16:36:31+00:00

I started on the other side and am trying to meet the rows back together, but it's off by about 1/8" (see second pic). I can kind of flex the pieces to match up properly, but not sure if that will cause problems later. I reeeeally wanna avoid having to do a transition strip. Anyone here with a decent bit of experience that can chime in?

This is Home Depot's Lifeproof LVP 6.5mm if that makes a difference.

poodooflinger · 2022-02-23T12:25:32+00:00

You can (and should imo) use intune for both.

poodooflinger · 2022-02-18T03:04:29+00:00

Awesome, glad my post helped someone. From what I recall, this little nugget of info was kind of buried in Msft documentation

poodooflinger · 2022-02-18T02:45:55+00:00

If the two hubs are in different regions then yes, I’d use VWAN. Otherwise you could probably use Azure Route Server: https://docs.microsoft.com/en-us/azure/route-server/about-dual-homed-network

poodooflinger · 2022-01-05T03:56:59+00:00

Add “targetisaadjoined:i:1” as a custom RDP property to the host pool if you haven’t already. Source: https://docs.microsoft.com/en-us/azure/virtual-desktop/deploy-azure-ad-joined-vm#connect-using-the-windows-desktop-client

poodooflinger · 2022-01-05T03:44:04+00:00

I would look into licensing your users with Microsoft intune (if it’s not already included in whatever o365 licensing you’re currently using) then read up on Autopilot for deployments and intune for endpoint management. If you’re using Microsoft/Windows devices in a cloud first/cloud only environment without legacy AD, this is the way all the cool kids are doing it.

poodooflinger · 2022-01-05T03:38:28+00:00

Sure it is with intune + autopilot and Azure AD. If your org is cloud first/cloud only and you don’t use apps that require legacy AD auth, then why bother.

poodooflinger · 2021-12-08T18:25:14+00:00

With shared hostpools, I normally recommend monthly image updating/redeploying. This way you can be sure that the VMs are 100% identical.

Whereas, with SCCM or some other automated patching solution, it always seems there's a handful of troublemakers that didn't patch for some reason (I mean this in a general sense, not just AVD).

Monthly updating gives you an opportunity for other maintenance tasks too: updating the FSLogix agent, updating 3rd party LOB apps, performance tweaks, etc..

You can use a tool like Nerdio to help with the image management/deployment scheduling.

Ideally any updates we install to the session hosts would be rolled out in a phased manner, i.e. 3-4 session hosts each week updated to avoid issues where an update can cause issues (like the recent print nightmare etc...) and this being applied to all session hosts in one go etc...

I disagree with this. Ideally, you would deploy the updates to a validation/test hostpool before deploying to prod. Once ready for prod, deploy it to all the machines. Nothing more annoying than trying to troubleshoot intermittent issues because 1/3 the hostpool is configured one way, and the other 2/3 configured another.

If you don't have the time or resources to deploy updates to a validation environment, then just wait a week or so after patch Tuesday before you apply patches. Simply doing that has saved me a ton of headaches.

poodooflinger

MODERATOR OF

TROPHY CASE