Event banner
Event details
43 Comments
- MS need to do a better job at helping break legacy thinking and publishing information on things like why you don't need to hybrid join devices. In fact, much of the information is there at aka.ms/cloudnativeendpoints, but not a day goes by that I'm not explaining to someone why they don't need to be doing HAADJ.
- So most NAC tools require an AD object to control 802.11x authentication. Some applications require specific naming conventions to operate. Thats why we need hybrid join. There are so many reasons people cant just drop on prem AD. Many environments that had 20+ years of legacy operation, are going to need time to redesign everything, re-solution, budget, plan.
- Things like Cisco ISE can integrate with Intune to actually provide a *more secure* solution based on things like device compliance. Changing from device-based to user-based auth is also a better route. 802.1x is like an armadillo, a hard shell around a squishy centre. I'm 100% aware that there are going to be challenges, but if your business is not prioritising moving away from those legacy systems, then the problem is them, not the technology.
- Most projects I do are focused on cloud native. However, customers are not always ready or need more time to move their data to the cloud. So we almost always have a hybrid situation where we need drive mappings for example. I would rather not have those, but this is the reality. Will there be any support from Intune on creating drive mappings of printer mappings? Or will there never be any support for those because of the cloud focus of the product and we need to solve that hurdle by using scripts or 3rd party tooling?
- Jason_Sandys
Microsoft
This is ultimately a bit of a soapbox for me, but I'd like to stress here that accessing on-prem file shares is different from mapping drives. Mapping drives is in no way required for users to access a UNC path. There are many alternate and (arguably) better ways for users to access UNCs including common methods that users are already fully versed with and use much more frequently as they browse the web including shortcuts and favorites. Forced and micro-managed drive mappings are not the best way ultimately -- yes, this is somewhat subjective, but most folks have never tried anything else so they simply fall back on "this is the way we've always done it" instead of actually evaluating the possibilities. As noted, a bit of a soapbox, but the reality is that the work environment is changing and so much the paradigms that users use.- You are absolutely not wrong on any point, but we have to remember that telling a user to click the "Shortcut to Shared Folder Blah" icon on their desktop instead of opening the "S:" drive like they've done every day for 20 years is a big shift. It's generally not the IT folks who care about whether it's a drive letter or a UNC path (unless some awful legacy app requires it) but making huge changes in the user experience generates complaints and makes our lives harder. I see both sides here and completely understand what it's like to be told "Just make the drive letter work" by upper management.
- Heather_Poulsen
Community Manager
Your guide to going cloud-native at the Microsoft Technical Takeoff starts soon. Have a question? Post it here in the Comments.
