Відео

Plan A: It's a visual metaphor for fixing something. Plan B: If all else fails, smack it with a wrench. It won't fix the computer but it might make you feel better.

Thanks! Glad it was helpful.

Thanks! I hope this one gains traction because it has a lot of promise if they keep heading in the direction they've been going, and some of the places they don't directly follow Exchange Server (like using OIDC for SSO rather than WS-Fed, or porting Graph to on-prem) are an improvement on it.

@@ProTechShow I will definitely spin this up in my lab and give it a go. The 5 mailbox limit made me think it wasn't worth trying but very pleased that can be worked around! This sort of thing has to be run for a while in the real world to see if it's got legs. And your right, 5 doesn't give you enough to put it into use in a "non critical" use case. I really don't understand their thinking here. They need to get the IT pros using it for personal use, then we are the people that will take it into production and that's where it will be licenced for full support. Let's hope they see this soon as they have potential for such a great product here. They have done the hard work building on all the great exchange protocols.

By "oversight", do you mean it was a bug? If this was not intentional I will re-test and pin a comment to that effect. On the Kopano/Gromox front the relationship between the different components seems to be somewhat obscured by time, name changes, and deleted articles, so I will take your word for it. I found multiple sources referring to Grommunio (at the time "grammm") as a fork of Kopano, and several references to Kopano making an accusation about stolen (proprietary) code by Grommunio/grammm. Most of the latter then linked to a statement by Grommunio refuting the accusation and stating that only free code was forked. The rebuttal by Grommunio largely concentrated on the number of changes to the Gromox component since a fork took place. As Grommunio chose to concentrate on Gromox in the rebuttal I believed this to be the component under contention; but articles provided for context by various sources have now been deleted along with the original accusation, so I can accept that some nuance has been lost to me.

@@ProTechShow It was not a "bug", the oversight was more of an editorial error. The pricing site has now been updated.

@@michaellangfermann5299 Yes, I can see the pricing page has been updated. I seem to recall having to get rid of a couple of shared mailboxes I used as personal archives because they pushed it over the limit, but I will check again and pin an update.

Confirmed and pinned a comment. Let me also take the opportunity to say thanks to you both and the rest of the team at Grommunio for the work you've put into this. I hope to see the project continue to grow and be a success.

I've been using Android with multiple Exchange accounts for years without any issues. I'm just using the default native app (currently on Samsung), not Outlook.

@@ProTechShow Samsung ships with exchange support, I think Sony did too, but that's not an integral part of Android neither Exchange nor Outlook accounts work in the generic case, specific ones may obviously you can handle emails using IMAP, but that's it also there are other apps that handle these, some made only for sync relying on the OS to expose data to other apps, but in my experience these were pretty unreliable

@@Z4KIUS Every non-Samsung Android device I've seen in years comes with the Gmail app as standard, which supports Exchange out-of-the-box

@@ProTechShow Gmail isn't a system provider but a 3p app and it doesn't seem to handle anything except mail, at least for personal accounts, even though they use the same protocol

@@Z4KIUS I just added an account to the app and it asked if I wanted to sync email, contacts, calendar, and tasks. Looks like the calendar opens in the Google Calendar app rather than Gmail itself, but it's all linked. I've honestly never come across a case of an Android phone not supporting ActiveSync out of the box, and we're talking tens of thousands of users - many doing BYoD. I'm sure if you get a raw de-Googlified Android image it could be a thing, but in terms of devices people actually use in the real world it's got to be pretty niche.

Thanks!

It's definitely a step up from the usual approach of slapping a web UI on top of Postfix + Dovecot and calling it done. There are some gaps, but being able to swap out the backend and keep the same familiar apps on the frontend makes it a lot more viable for me.

Worth a look indeed, and if you're on a budget it requires significantly fewer resources than a full Exchange server. My lab was starting to stretch at the seams and replacing Exchange with this gave me some space back to play with.

i don't but I hear that 0x00000050 is one of the hardest bsod to fix so good luck with that

This video is not about cracking BitLocker. It shows several legitimate methods to find your recovery key. In most cases there is no need to lose data just because you see a BitLocker screen. You should probably watch the video before commenting...

@@ProTechShow I did, and most people who have bitlocker setup also magically forget their windows account username and password

The manage-bde command is a preventative measure to make sure you have a copy of your key before you get locked out. If you're already locked out of your drive it won't work and you will need to use one of the other methods in the video to find your key. If your drive is unlocked and you still don't see a password then it's possible your drive was encrypted without creating a recovery key. You ought to be able to create one of your own with "manage-bde -protectors -add C: -rp", replacing C with the appropriate drive letter.

Glad to hear it!

Thanks!

You're welcome!

Glad it helped

Glad it was helpful, although it's worth noting that "CentOS Stream" is not the same thing as "CentOS Linux", which was originally just "CentOS" as referred to in this video. There have been a few changes since this video was published - check the pinned comment for a few updates.

If the root cause is a driver and you haven't identified it, you'll simply reinstall the problem. If the root cause is hardware, attempting to reinstall Windows is likely to make things worse and leave you with an unbootable machine. It's best to diagnose the root cause of the BSoD before reinstalling. A bluescreen crash will typically reboot back into Windows automatically once it's saved a memory dump. In the event the bluescreen occurs during the start-up process there's a section in the video with things you can try if Windows won't start. Finally, you can grab the dump file from the faulty device and run the analysis on another computer - it doesn't have to be the same one.

I can see that. Not sure if I like it, but I can see the appeal on the selling side. Extending tracking pixels beyond email and websites.

Aye. It was looking very promising for a while.

If you keep it on a completely isolated network that is a viable option. It's usually not practical for most use cases, but there are scenarios where the impact of a computer failure is so great that the safest thing to do is not let it talk to anything else. They're usually pretty specific scenarios, but in principle if you keep your computer disconnected from everything else then you're pretty secure.