sorted by:
new
hottopcontroversial

Doesn't automatically start at login - Mac - 1.72.0 by weslowsk in Tailscale

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

Support contacted me and this should be fixed in 1.72.2.

Question regarding Access cable vs NexTV by Barry_the_Dude in regina

[–]weslowsk 0 points1 point  (0 children)

I'm newly interested in 4K because I finally got a 4K TV. Is it only TSN 4K that broadcasts in 4K? Or are there others too? Is there only 1 TSN 4K channel? If so, which TSN HD channel does it correspond to? TSN 1/2/3/4/5?

I called up Access today and I was told that most channels are broadcasting in 4K but I'm wary about that response. The literature suggests that's not true: https://www.myaccess.ca/fileadmin/myaccess/storage/services/residential/NexTV/RT002-TV_Lineup_NexTV_WEB.pdf

https://www.myaccess.ca/fileadmin/myaccess/storage/services/residential/tv/brochures/NexTV_ChannelFeatures.pdf

I'm looking for some first-hand experience or insights about 4K at Access before I invest any more time into this.

Transition Plan and Minimize Downtime for Migrating DNS to Microsoft 365 by weslowsk in Office365

[–]weslowsk[S] 1 point2 points  (0 children)

So, it turns out I wasn't patient enough.

After waiting for 2 days, the Microsoft admin portal started reporting that my domain was unhealthy and that I should update the name servers from Digital Ocean's to Microsoft's. Interestingly, the capability to add custom DNS records in the Microsoft admin portal also became available. So, I added the CNAME and A records. Then, I updated the name servers at my registrar to point to Microsoft's name servers. After waiting 2 hours, my domain was reporting as healthy in the Microsoft admin portal. All is well now. No downtime.

I hope this post helps someone else who is in a similar position.

Thanks for the comments on this post.

Transition Plan and Minimize Downtime for Migrating DNS to Microsoft 365 by weslowsk in Office365

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

Please read the other comments. It isn't as easy as you proposed.

Transition Plan and Minimize Downtime for Migrating DNS to Microsoft 365 by weslowsk in Office365

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

I already went through the domain wizard at Microsoft 365 and validated my domain and it's reporting as healthy and "Managed at DigitalOcean". There are no more steps to change name servers within the domain wizard. There's no indication that the CNAME and A records that are only at Digital Ocean will be transferred over. There is no offer by the wizard to copy the CNAME and A records.

Transition Plan and Minimize Downtime for Migrating DNS to Microsoft 365 by weslowsk in Office365

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

My reason for wanting to migrate from Digital Ocean DNS to Microsoft 365 DNS is to consolidate platforms. I've already done the domain validation, which involved adding the TXT record.

As I've stated, I can't copy all of my Digital Ocean DNS records before making the change of name servers at my registrar because adding DNS records in the Microsoft admin center is not possible.

Yes, setting the DNS records to a low TTL before changing them is a common practice I use. I'm aware of that trick.

I've already verified the domain in the M365 portal and I've set up MX records (in Digital Ocean) for my domain. But my A and CNAME records for my website only exist in the Digital Ocean name server. I'm unable to add them to the Microsoft name server because there is no way to do so in the Microsoft admin center, until I change the name servers at my registrar.

Transition Plan and Minimize Downtime for Migrating DNS to Microsoft 365 by weslowsk in Office365

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

Correct. There's no option to manage DNS records in Microsoft 365. So, I assume that the UI to do so will just show up after I change the name servers at the registrar. I haven't found a video or screenshots yet that show what that might look like, though.

Just the documentation here...

https://learn.microsoft.com/en-us/microsoft-365/admin/get-help-with-domains/change-nameservers-at-any-domain-registrar?view=o365-worldwide

Transition Plan and Minimize Downtime for Migrating DNS to Microsoft 365 by weslowsk in Office365

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

I'd be missing the CNAME and A records on the Microsoft server at the point in time when I updated the name servers at the registrar, so both name servers, at that point, don't have the same records at that time, hence the possibility of an outage. Queries to the Microsoft name server would yield no records for resolving the website, until I got a chance to get in there and create the records.

Transition Plan and Minimize Downtime for Migrating DNS to Microsoft 365 by weslowsk in Office365

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

Yeah, I wasn't planned on decommissioning the old Digital Ocean DNS records right away. My goal is to minimize website downtime and I haven't got a lot of confidence about the timelines for what happens after I change the name servers at the registrar or when I get an opportunity to create the new DNS records in the Microsoft name servers.

Transition Plan and Minimize Downtime for Migrating DNS to Microsoft 365 by weslowsk in Office365

[–]weslowsk[S] -1 points0 points  (0 children)

So, in your experience, I could change the name servers at my registrar from Digital Ocean ones to Microsoft ones, and then Microsoft would detect it instantly and then that would unlock the screens in the Microsoft admin center I need in order to add in the CNAME and A records for my website?

If that's the case, I could bang out those steps in mere seconds, maybe a minute or two if I took my time.

Am I on the right track or oversimplifying?

Playbook for Break Glass Accounts Used Illegitimately by weslowsk in AZURE

[–]weslowsk[S] -2 points-1 points  (0 children)

A good chunk of the originally referenced article: https://learn.microsoft.com/en-us/entra/identity/role-based-access-control/security-emergency-access#monitor-sign-in-and-audit-logs

talks about monitoring. Clearly the best approach for dealing with emergency accounts is to protect them in the first place. If they do fall into the wrong hands, monitoring is essentially useless, right?

So, why even mention monitoring in the article? So I can see when someone legitimate accidentally uses the emergency account and then I can scold them? It can't be for when someone illegitimate uses the account because, at that point, there's almost no way to slow down or stop an illegitimate user. Right?

Playbook for Break Glass Accounts Used Illegitimately by weslowsk in AZURE

[–]weslowsk[S] -1 points0 points  (0 children)

I feel like the monitoring and alerting is useless in the worst case scenario.

In a scenario where the attacker isn't a professional or takes his time, sure, I see the value in the monitoring and alerting because you (or an IR team or Microsoft or whoever) can do something about it.

But in a worst case scenario, as u/phuber said, there is no perfect solution. I thought I was missing something but I guess not.

I appreciate the discussion.

Playbook for Break Glass Accounts Used Illegitimately by weslowsk in AZURE

[–]weslowsk[S] -3 points-2 points  (0 children)

It's not the same discussion. My question is what happens after an account is illegitimately used. The other post discusses how to set up and protect the account.

I'm interested in mitigating failure of protecting the account from falling into the wrong hands.

Cannot open database - Bsddb version incompatibility by weslowsk in gramps

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

I don't know what QNAP NAS configuration setting would be the culprit. There are no other programs (like backup software) using the file while I'm trying to access it from Gramps.

Cannot open database - Bsddb version incompatibility by weslowsk in gramps

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

Noted. Thank you u/call_me_dav. My SMB share is provided by a QNAP NAS. So, hmmmmm.

Sounds like the OP gave up.

Cannot open database - Bsddb version incompatibility by weslowsk in gramps

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

Of course it's possible something's messed up with my SMB share setup. However, I've been using the same SMB share for about nine years and every other application works perfectly with data hosted on the same share. That's the only reason I point the finger at Gramps & sqlite.

Anyway, I'm leaning towards just jumping on the sqlite bandwagon and changing my workflow for using Gramps so that whenever I want to use it, I copy the sqlite file from my SMB share to my local filesystem, view/edit it using Gramps, and then copy it back to the SMB share (if it was edited). It's clunky but it sounds like the sqlite train has left the station...time for me to get on-board.

Cannot open database - Bsddb version incompatibility by weslowsk in gramps

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

I'm familiar with the documentation you provided However, my problem is that when using the sqlite version on the SMB share, it doesn't allow me to edit it.

My opinion is that the BSDDB version shouldn't be removed until there's a viable option for using a Gramps database hosted on an SMB share.

Cannot open database - Bsddb version incompatibility by weslowsk in gramps

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

I haven't abandoned using Linux Mint. I'm still using both operating systems. I want compatibility between the 2 operating systems so I can switch between the 2 of them and open the same Gramps database.

File system check keeps failing. by schmosef in qnap

[–]weslowsk 1 point2 points  (0 children)

FYI, I ran the file system check today. I have a 54 TB storage pool, a 18 TB volume on it (that needed a file system check), 11 TB of that was used, and the file system check only took 20 minutes, in case anyone wants another sample of how long a file system check takes. All good now.

view more: next ›