AWS Config vs Microsoft Endpoint Manager (Microsoft Intune + SCCM)

• It can help you define rules for provisioning and configuring of your AWS. We use it for this purpose.
• It maintains configuration history. So you can use the AWS Management Console, API, or CLI to obtain details of past configurations
• It gives you a configuration snapshot of all of your AWS resources and you can store it in AWS S3.
• You can integrate it with AWS CloudTrail to correlate configuration changes to particular events in your account.

Read full review

• [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.

Read full review

• Vendor lock-in, no easy migration path for example if you want to move some workloads to Azure, you'd not be able to lift and shift.
• Only at an AWS resource perspective - cannot do desired state configuration at an OS level (which makes sense but be good if you could even as a separate feature within AWS Config).

Read full review

• 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.

Read full review

• Security awareness. With multiple teams deploying provides easy visibility on any security risks. Security breaches would have a substantial impact on business so a vital investment with little costs.

Read full review

• Cuts down our software deployment and patch management time compared to our old tools.
• Better reporting capability to determine the success to fail ratio of a deployed software or patch and additional information provided to mitigate the failed deployment.
• Consistent tool usage across our global units with centralized reporting to monitor monthly patch and software deployment results.

Read full review