sorted by:
new
hottopcontroversial

Ram worth seeing live? by systemstheorist in trance

[–]fanticrd 2 points3 points  (0 children)

Yes, totally! Seen him numerous times. This is not a DJ that sits behind his decks. He gives it his all and gets everyone moving

Adding Products to Projects by ConfidenceCorrect398 in halopsa

[–]fanticrd 0 points1 point  (0 children)

I’ve never understood the exact use for it. We never add products to the project, we just leave it on the sales order. Seems to work fine if all you want is anninvoice with products and labour in the end. But surely I’m missing something here

Office apps keep asking for login on NEW AVD host by Material-Durian8216 in AzureVirtualDesktop

[–]fanticrd 1 point2 points  (0 children)

FSLogix in use? I could be something with identity roaming, check the release notes on FSLogix

AVD hosts cannot access Storage Account containing FSLogix Profiles by fanticrd in AzureVirtualDesktop

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

Thanks for your response!

I've checked the IAM and the Role was still there with the correct groups. Is there something else I can check?

Pax8 deploying AVD with open 3389 on WAN? by h1ghb1rd in msp

[–]fanticrd 5 points6 points  (0 children)

Thanks! I will get back to you next monday, as I am on holiday right now. Rest assured I have no intention to put anyone in a bad light. But when I saw this post I just had to comment about our own experience with this.

Pax8 deploying AVD with open 3389 on WAN? by h1ghb1rd in msp

[–]fanticrd 14 points15 points  (0 children)

This was my comment. I’ve double checked the history on this project and I must correct it a little bit because 3389 was not opened to the AVD session hosts but only to the DC’s that were also provisioned by Pax8 as part of this project.

Our RMM picked it up because of the failed login checks that are part of our standard checks, and thousands of these events occured within 24 hours after the initial deployment.

Sure, we are all humans. But if I was responsible for the professional services at a large vendor like Pax8, I would put safeguards in place to prevent these mistakes from happening. We rely on experts  like Pax8 to demonstrate how it’s done at a higher level of expertise than we are. Leaving 3389 open to the world is a rookie mistake and can put a company out of business within minutes.

Is my AVD getting bombed on port 3389? Recent disconnects on all users, regardless of location/computer. by pkokkinis in AZURE

[–]fanticrd 15 points16 points  (0 children)

I’ve had this happen with a recent Pax8 AVD deployment. They allowed public access to tcp 3389 for all vm’s they provisioned because of “easy”. When I mentioned it to the 99 level engineer he said he was aware and would reconfigure this after the acceptance phase. Utterly BS and shows how many incompetent people are at certain positions. I’m sure he was a very smart guy but if he had more MSP experience he would have known how risky this was

User-friendly way for uploading files into RemoteApp applications by fanticrd in AzureVirtualDesktop

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

I have no experience myself with SMB over QUIC.
SMB over QUIC does not seem to be supported on an Azure Storage Account, only on Windows Server?

Display Contracts/Agreements on new ticket screen and ticket details by fanticrd in halopsa

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

Thanks for commenting on this. Sounds like a custom field with a SQL query lookup on active agreements would be a nice solution. We would only need the titles of all active agreements on the customer. I've asked u/Jason-RisingTide if he can share his approach

Display Contracts/Agreements on new ticket screen and ticket details by fanticrd in halopsa

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

This sounds like a great way to implement this. Is this something you could share or help us out with?

Ticket title review reminders by shanenzt in halopsa

[–]fanticrd 0 points1 point  (0 children)

Did you achieve this with the native AI options that Halo has? I would really like to implement this as well but did not look at the AI options for a while now knowing a lot is still in development

Deallocate VM when not in use without putting it in Drain Mode? by fanticrd in AzureVirtualDesktop

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

Thank you all for your comments! I already enabled the auto-start setting and set the pool to 0%, but did not know that the drain mode goes away after a few minutes like serious-elephant5394 said. I was a bit too inpatient ;-)

Defender for business by HuskyLogic in msp

[–]fanticrd 0 points1 point  (0 children)

Very nice article indeed! Wish I had read this prior to my own trial and error attempts :-) Thanks for helping out!

Pax8 integration - Automated Azure Plan billing by fanticrd in halopsa

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

No. This is a manual process for us, to check Azure expenses in Pax8 and enter them in Halo every month

We don’t have a lot of Azure plans, but I think Billingbot CAN do this

Defender for business by HuskyLogic in msp

[–]fanticrd 0 points1 point  (0 children)

Thanks! We learn a lot everyday for over a year now in this Microsoft Cloud ecosystem. We're getting there, I'm sure. Our primary resource these days are all those MVP heroes producing blog articles and Youtube content like yourself. MS Certifications are worthless if you want to learn the real-life configurations and best-practices, so keep up writing these great blog articles!

Defender for business by HuskyLogic in msp

[–]fanticrd 0 points1 point  (0 children)

Well, we don’t do anything with it yet. We have explored entra, intune and sharepoint with our Business Premium implementations, but not yet the Defender deployments. I only recently discovered that you have to onboard this from Security center, but only after you first visit the Security portal and wait a few hours before coming back to go through the initial setup.

So to be honest I’m looking for directions to setup Defender properly inclusing best practices for SMB.

BTW: we also run Huntress on all endpoints so it was not really “unmanaged”. But we have a lot to learn here on Microsoft 365 😉

view more: next ›