Exploring the Role of Automation in Systems Administration: Current Trends and Future Prospects

• The webpage is a thread from the subreddit r/SCCM, titled “What did you automate in SCCM that you would not live without now”
• Posted 2 years ago, it contains user suggestions for automating functions in SCCM
• Users suggest automating remote control service to start automatically for easier access after reboots
• Users recommend making a script that creates collections for specific computer models, including an “All model” collection, and sorting them into manufacturer folders
• Suggested automations include software update management and patch management
• Users recommend using Automatic Deployment Rules (ADRs) to recreate software update groups every month.
• The ADR can have tiered deployments to test, pilot, production groups, specials, and catch all.
• Other recommended SCCM automations include compliance settings, task sequences, and creating collections
• The compliance settings are to ensure less issues in the environment.
• One user suggests automating single computer collection creation with 24 deadlines for specific application deployment
• Another user suggests using SCCM scripts to automate the process of gathering motherboard codes because it can be very time consuming
• A recommendation for everyone is to consider what tasks consume significant time and energy, and to plan automations around these areas
• Another user recommends the use of a driver automation tool to download and import drivers from manufacturers into SCCM
• A suggestion is to break down tasks into manageable scale, rather than a heavy overhaul
• Other recommended automations in SCCM include:
  • Adding personal emails to all email templates when sending new computer deployment emails
  • Automatically redistributing DP content to SCCM site for a specific branch
• The thread discussions also include some problems users have experienced with automation, to be cautious of
• Some users can’t specify a specific available/deadline time for an ADR, and the syncing duration time may differ
• One user mentions it’s important to have an adequate amount of ADR rules
• Several users express surprise that certain automations are still not a standard practice in all environments.
• The thread has a total of 30 comments with 64 points.
• Users show interest in sharing and learning new SCCM automations to make work quicker and easier.

• The Reddit post is asking about automation and how it is used in the field of system administration. It was posted 1 year and 5 months ago under the subreddit r/sysadmin and has gained 75 points.
• Users share examples of different automation projects they have tackled at their workplaces, such as improving server patch management, automating end-user device configuration, tackling user and device onboarding, and creating automation for the IT support tickets.
• There is discussion of using Powershell to backup switch configs, and some users recommend the use of PDQ for automating certain tasks.
• One user mentions that implementing automation within the IT department has met with resistance from other departments, with concerns that automating tasks will result in job loss within support teams.
• There is discussion on the limitations of current tools used in automation and the challenges faced when implementing automation solutions, highlighting the importance of balancing automation with human support when it comes to break-fix issues.

These are all the key points present in the webpage that may be helpful to answer your query.

• Automation is the top trend in technology as per McKinsey, and over 80% of organizations will continue or increase automation spending in 2022 (per Gartner survey).
• In 2022, CIOs will develop enterprise-level approaches to automation strategy, governance, and platform technology.
• Automation mandates are being issued by boards to ensure wise and strategic spending of automation investment. CIOs are being tapped to deliver these mandates.
• CIOs are moving closer to revenue growth and new business opportunities by using RPA in operations like customer self-service, contact centers, and sales and marketing operations.
• RPA (Robotic Process Automation) adoption continues to grow, and RPA-plus platforms will be the winner of the automation convergence battle. The “plus” will incorporate enterprise-critical functionalities like governance, low-code/no-code build environments, and support for “democratization” and scalability.
• RPA platforms will move into adjacent categories like LCAP and also invest in interoperability and easy integrations with other automation technologies.
• In 2022, an “automation layer” will add automation to the top of enterprise application stacks. Robots will create digital joins between systems of record, and will take on repetitive tasks like inputting data from one system into another or opening and closing programs.
• Instead of people going to separate business applications to get their work done, just-in-time tasks will be delivered to them directly. This approach will free people from technology fragmentation and let them focus on valuable work.
• Automation is being used to address the “last mile” problem in AI execution. Organizations are using automation to put models into production and also cover AI and ML deployment.
• Semantic automation lets developers move away from rules-based approaches. Semantic software robots will observe an activity and begin to emulate it without step-by-step instructions. Developers and even business users will be able to initiate automation development just by asking robots to perform a task or complete a workflow.
• The 2022 Trends: Automation Accelerates report provides more details on each of these trends.
• UiPath won the 2021 Forbes Cloud 100 “Top Companies in AI and Machine Learning” award.
• People interested in learning more about these trends can join the Automation Summit or UiPath FORWARD IV.

• “Do you need to know scripting/automation to be a system administrator?” is a question addressed in a post on Reddit in r/sysadmin.
• A Reddit user with 335 karma believes that while it is not a must to know scripting/automation to become a system admin, it is highly encouraged since not doing so could lead to inefficiency and consume more time.
• Learning at least some scripting knowledge can make you a more attractive candidate when applying for system admin jobs.
• Another user with one karma agrees with this and suggests starting in a technical support role where one can learn scripting skills on the job, which is a common path for many people in the field.
• Some users with varying amounts of karma suggest that scripting knowledge will lead to better job opportunities and possibly higher pay.
• One user with the highest karma in the thread stated that sysadmin is about optimizing and automating business processes rather than making servers spin. In IT today, programmers of basic scripts/programs are preferred candidates.
• A user with two karma said that even if someone can do their job without scripting, they can’t do it at full efficiency.
• Learning PowerShell is a great way to start to learn scripting as a sysadmin, according to some users.
• Several users provided anecdotes about how scripting saved them time and gave them more productivity.
• One user detailed an incident where they were able to finish the fixing of servers quickly after creating a script while their colleagues stayed for hours doing it manually.
• Non-scripters who do their work manually still exist in the field according to several users, but scripting knowledge is still very important.
• Another user shared their experience that new policies, addresses, and firewall rules on a handful of Fortigates can be created and updated quickly through scripting.
• One user expressed their disbelief and frustration over people who consider lack of scripting skills as job security, while some users argued that scripting knowledge can also be considered as a form of job security.
• The object of automation is not limited to server administration as indicated by one user.
• Several users provided recommendations for tools and scripts that a sysadmin could start learning, from using Python to automate mundane tasks to utilizing the Ansible Automation Platform to create playbooks to automate system tasks.
• While scripting is important, some users believe that it is something you can pick up on the job, abstract to learn without the real-world scenarios if you have never been a sysadmin, with the intention of encouraging people who want to pursue the sysadmin path.

• Business leaders face immense pressure to deliver results in challenging economic times.
• An investment in business process automation is one of the fastest ways to improve efficiency and productivity across every department, including IT.
• Automation reduces the repetitive and monotonous tasks humans have to do by relegating those tasks to software, which usually means a better experience for customers, reduced error rates, improved compliance, and lower stress for teams.
• The ability to quickly and easily automate workflows helps companies achieve faster time to value, whether by reducing case handle time, boosting conversion rates, providing faster quotes, expediting client onboarding, or streamlining order processing.
• Automation, especially when real-time data and AI are combined, can enable organizations to deliver highly personalized customer experiences at scale, while driving higher levels of productivity and efficiency.
• Nearly 90% of workers recently surveyed said automation solutions increased their productivity, and 85% said these tools boosted collaboration across their teams.
• Automation tools improve the overall employee experience: nearly 90% said they felt more satisfied with their jobs since they began using the technology, and 84% were more satisfied with their employer.
• An inefficient organization will eventually need to respond to business pressures or go out of business, and automation helps protect companies from the burden of inefficiency.
• Companies should listen to business partners across the company and work on automation initiatives that will generate the most business value by partnering closely with key business leaders, CIOs can help elevate core priorities amid budget constraints and deliver the right technology to achieve teams’ most pressing goals.
• A critical step to automating business processes and drawing useful insights from enterprise data is to bring together information locked away in disparate systems. Look for technologies that can connect and harmonize data from a variety of sources into a single platform that provides a seamless view of the business.
• Companies need low-code solutions that give anyone, not just admins, the ability to build and deploy automation quickly.
• Encouraging team members to think about and share ideas on ways to remove inefficiencies and eliminate repetitive and manual processes can build an environment in which employees feel they are part of the automation strategy.

• Power Automate is a user-facing service that can automate a wide range of tasks within the 365 tenant.
• It provides a user-friendly drag-and-drop GUI and pre-built connectors and triggers to automate workflows.
• Power Automate is not only for non-technical audiences, but also can be used to build custom connectors.
• It can be used for personal productivity such as organizing mailboxes, business process automation, or robotics process automation.
• It can be triggered from Power Apps and Logic Apps, which makes it more versatile.
• PowerShell is a scripting language that can be used to automate technical and non-technical processes for cloud and on-premises infrastructure management.
• For example, monitoring, managing, and automating Active Directory, Azure AD, Exchange, and Exchange Online.
• PowerShell is typically used by more technical audiences, but can become more accessible with learning and practice.
• PowerShell modules can be used for advanced functions and features of management and administration tasks.
• Azure Automation and Hybrid Workers can be used to execute PowerShell scripts on on-premises infrastructure.
• There is some overlap between Power Automate and PowerShell, but both have different use cases and can be complementary.
• Power Automate can be used to automate anything within the 365 tenant, but it does not replace PowerShell.
• Comments in the Reddit thread discuss how to handle service accounts and users’ dependency on them if the user who created the flows leaves the company.
• Making a new account to build workflows is recommended for critical tasks.
• Example use cases of Power Automate include automating reminders, onboarding processes, document management, and AI-powered document processing.
• Power Automate can be used by users to manage their workflows while IT teams own the workflows in terms of service accounts.
• Configuring PowerShell takes more setup for simple tasks than Power Automate.
• Power Automate is easy and intuitive to use, and comes with example flows that can be tried.
• Some users suggest Logic Apps instead of Power Automate for Forms and automated stuff based on personal preferences.
• There is some confusion on whether Power Automate works with Google Chrome.

💭  Looking into

Comparison of current and future state of automation in systems administration

💭  Looking into

3 key benefits of automation in systems administration