AWS CodeDeploy vs. Microsoft System Center

Getting the code from Git Hub, uploading it to the repository, making changes, and deploying it to a specific environment makes AWS tremendous and easy to work with. Once you know how to do it, it is easy to replicate. On the other hand, if you are new, it gets confusing, and you need guidance on the steps to take not to compromise the application.

Incentivized

For companies with more than 10 Windows devices and needing to standardize the OS, AV, access, share resources, and install software. SCCM is the way to go. This software is unnecessary if the business is all remote users and not in an office-type setting. There are cloud offerings or none to accomplish what a business needs.

Incentivized

• Integration with other AWS services
• No administration required
• Unified and easy process for dev teams

Incentivized

• Allows the grouping of devices by user.
• Allows controlling updates being deployed to user devices.
• Allows for the repurposing of machines by being able to load new or updated software on machines that already are in the system.
• Allows us the ability to wipe a machine clean and restore it back to the configuration that was assigned the machine.

Incentivized

• There is one limitation is it can't do multi-tier apps
• It is not possible to control the order in which deployment occurs if more than one deployment attempts to run at the same time
• AWS CodeDeploy does not integrate with GitHub

Incentivized

• Needs web based storefront for requesting new software
• Needs ability to manage the packaging work flow better
• Sometimes is slow to download and there is no indication the entire catalog is being loaded, resulting in confused users not being able to find common software in the available list.

Incentivized

Here is where AWS as a whole stepped up big. The UI is more intuitive and easy to use. The separation is clear, and the guides are abundant. They still need to create starter tutorials for newcomers so we don't lose much time learning/teaching others. Having someone with basic knowledge and examples where they can gain experience will make it better.

Incentivized

It is not user-friendly for the most part. With IT infrastructure, sometimes it cannot handle excess requests. Every few months, you will need an upgrade in terms of server resources to keep up with incoming alerts and requests. This does not happen all of the time, but it does happen when there are too many requests.

Incentivized

If I had to dislike something about the system it would be how much it changes once you upgrade. This could be more of a problem of mine since I get used to one way and don't like it when it changes so much. I am enjoying the newest update, but it is a mess when you are actually going through the upgrades.

Incentivized

Jenkins supports a lot of plugings. Also with Jenkins, it is possible to manage everything through our own server. Those are 2 points where I rate Jenkins as one of the best DevOps Tool

Incentivized

We previously used a mix of FOG and Clonezilla to image machines. The biggest issues with these products is that changing one piece of the image required you to rebuild the entire image itself. These pieces of software also did not allow you to manage applications and Windows Updates, causing IT to have to constantly touch machines after they were imaged and update or manage them with a much more hands on approach.

Incentivized

• AWS CodeDeploy has reduced the engineer involvement in deployments
• Our QA team has been able to effectively deploy tickets for testing, and our Release Managers can manage production deployments
• Progress indicators have given us a better baseline for deployment times, which is helpful for time-sensitive releases

Incentivized

• We have been able to automate our patch management, firmware and other security concerns.
• We have a standardized "image" ensuring our setup is consistent across the enterprise. This alone has saved us in time to support and time to understand how to use our desktops.

Incentivized