Microsoft Intune (formerly Microsoft Endpoint Manager), combining the capabilities of the former Microsoft System Center Configuration Manager, SCCM or ConfigMgr, is presented as a unified endpoint management option. Microsoft Intune is an endpoint management solution for mobile devices, an MDM solution that allows the user to securely manage iOS, Android, Windows, and macOS devices with a single endpoint management solution. The component Endpoint Configuration Manager (the…
$5
per user/per month
Red Hat Enterprise Linux (RHEL)
Score 9.2 out of 10
N/A
Red Hat Enterprise Linux is a Linux distribution mainly used in commercial data centers.
Windows Autopilot makes provisioning user Windows PC laptops a breeze. A user only needs to turn on the laptop, join it to their local WiFi, login with their O365 account then sit back and let Windows Autopilot handle the app installations required for work, configure the laptop settings to meet my organization requirements. I have seen this all completed in less than 30 minutes depending on how fast the internet connection is. Where Microsoft Intune needs to improve I think is the part where it can push out software updates to 3rd party apps. Right now I have to use Automox to fill in this gap.
I guess to give it more context, my first job in the Linux ecosystem was in web hosting. And that was basically a Cintas shop and it was all run extremely lean and very bootstrappy do it on your own. You don't get any support. And for that environment, it was kind of just the way it is. It's very cutthroat. You have to move super fast. Once I moved over to the corporate side, every company I've worked with has been on rail. And the thing that really kind of makes it the best choice compared to using another operating system, another flavor of Linux and just kind of figuring out your own is the amount of support that Red Hat gives rail as far as extra tools like Satellite Insights and what's coming up now with Ansible and especially Ansible. Lightspeed, but also SLAs and stuff like that. Because yeah, I mean it was good learning in that first environment because there were no tickets, there was no support. It was figured out. But nowadays it's just nice to have an SLA agreement. I can just open a ticket. I say that that's something that does really well, but I also want to see it expanded, just more like vendor support at an enterprise level. I'm not sure yet what that would mean. I just have that every time we come up for renewal, I look at the price tag and it's like, what else can we do here? I like what Red Hat is doing just more.
[Microsoft Endpoint Manager (Microsoft Intune + SCCM)] helps to speed up the deployment of patches/software throughout our environment. I can easily build a package and then deploy across all endpoints.
The ability to supercede software is also quite handy. This automates the removal of old versions and replacing them with newer versions.
The Intune Autopilot option is very useful if you want to deploy software to devices straight out of the box. You can configure them to download software when a user opens a new PC and turns it on for the first time.
For us, it's going to be the deployment and the patching. It does a good job because you can put your no reboot tags and things like that because working with production systems and so we don't want them just rebooting suddenly because they were patched in the Linux world. So the non-reboot tags and the operating system deployment is the biggest thing we find that saves time and that's the biggest thing that we like. The tools. The tools that save time.
The program itself can be challenging to use, especially if there hasn't been any formal training on the use of the product. Either training/reviewing documentation is recommended prior to using SCCM.
At times, it can be difficult to try and find out why a certain machine that's listed in SCCM says that the endpoint has the SCCM client and shows as Active, but in fact, it's not. It's also difficult at times to try and figure out why the client can't be pushed down to the endpoint.
Even though the remote assistance features in SCCM are really good, it can be challenging at times when the remote options don't work for a particular endpoint, even though the machine is active, online, etc.
From an automation perspective. RHEL is really moving forward, but some of their ideas are still not ideas, but their implementations of it still feel half-baked, like the functionality's there, but it's not the kind of functionality that to me makes it a full-on solution with OpenShift in particular as we're bringing this in and we're getting more into containers because it's more important for the banking industry and other industries. Justice General, well you can do this by script and we don't have an interface for this and sort of things sort of like that. I'm trying to think if there's anything else that RHEL does that bothers me as a general rule.
Mascom Wireless is a Microsoft shop and SCCM has proved to be helpful in keeping our Microsoft products up to date every month without fail. We also have a Microsoft Enterprise Agreement which we renewed for three years ending 2022. The remote access utility works wonders for the organisation and have saved travel bills including subsistance allowance. We have been able to fulfill security audits both internal and external. We have been able to keep a robust inventory of our computer assets and nothing falls of the cracks
The console is not intuitive and does not work well often. Due to the complexity of the product, documentation can be confusing. When properly configured, routine tasks like OS deployment, remote control, and software deployment are easy to do. Troubleshooting of System Center Configuration Manager issues is hard, as there are various logs, and their content can be hard to understand.
RHEL has most of the features that are required by an ERP solution. If you need any additional packages, RHEL has a great repository and a very easy package installation/upgrade process.
It's a 'heavy' system, which demands a lot of resources form the datacenter perspective. So, make sure you followed the requirements to avoid frustration in the future. From the 'client' perspective, it's fine. I've never had any issue with that.
Being a Microsoft product, support was good. Out interaction was limited to our in-house IT team which was installing the Intune app in our mobile device. The installation was smooth and we haven't faced any difficulties with the app while using it. Provides a smooth and secure access to all Office 365 apps in mobile while separating the personal and professional data.
Red Hat support has really come a long way in the last 10 years, The general support is great, and the specialized product support teams are extremely knowledgeable about their specific products. Response time is good and you never need to escalate.
Work with a "test group" of users who you have a good relationship with so that when things don't work properly they understand! Work with your partner nicely without forcing things especially timelines as you are bound to make mistakes and create oversights in the project Management can also interfere with the implementation (which can cause delays) if you make too many mistakes which takes me back to having a "test group" where you have good relations
We did not evaluate or use other products like Microsoft Endpoint Manager (Microsoft Intune + SCCM). The main reason we did not evaluate or use other products is because Microsoft Endpoint Manager (Microsoft Intune + SCCM) integrates seamlessly with Microsoft 365 and Windows PCs. Expenses would have increased as well if we had purchased another similar product.
The biggest thing about RHEL that makes it stand out for enterprise users is the support that we get from the vendor. Whereas with the other ones, you're basically left on your own. There's no official repo, there's no satellite for patching. You're very left on your own with the community.
In our current environment, this System Center Configuration Manager had replaced several standalone solutions for patching, imaging, remote assistance, reporting, etc. That saved a lot of time and resulted in money to manage the IT infrastructure.
Once SCCM is deployed and fully configured, all agents are deployed and it is easy to automate a lot of processes and just control them from time to time to make sure that everything is working as supposed to be.
SCCM + Windows 10: great built-in endpoint protection solution. As a result, there is no need to buy additional software for that purpose.
The imaging process is better compared to WDS because you can modify deployment packages and apply patches to a newly imaged machine. This saves tons of time for new employees deployment.
Auditors are happy that we use an enterprise class distribution
Patch process is easy and fairly predictable
Information Security is fully satisfied with the speed of the fixing the errata and general state of the security patches, including the backporting process
