Lecture on Automatic Software Installation using Microsoft Endpoint Manager

Introduction

• Speaker: Irvin (aka Kabumet)
• Topic: Using Microsoft Endpoint Manager for software distribution (formerly SCCM)
• Objective: Understand software installation automation using Endpoint Manager

Setup and Environment

• Virtual Lab Machines: Provided by Microsoft
  • Tools: Hyper-V, Microsoft website link for virtual machines (require high-spec computer)
• **Servers and Clients: Setup: **
  • Client machines (1-6)
  • Central servers (Content Manager, Main Controller)

Core Software: Microsoft Endpoint Manager

• **Components: **
  • Front End: Microsoft Endpoint Configuration Manager interface
  • Devices Tab: Shows active online devices
  • Software Center on client side (executable: ccm.exe) for local control
• Old Name: SCCM (System Center Configuration Manager)
• Functions: Software updates, Windows updates, new software installations

Client-Side Setup

• Software Center: Local client tool for installing/removing/updating software
• **Common Software Examples: **
  • Google Chrome: Showed the installation interface, reinstall feature
  • Putty
• Tabs in Software Center:
  • Applications
  • Updates (e.g., Windows updates)
  • Operating Systems
  • Installation Status
  • Device Compliance

Installation of Client Software on Endpoints

Manual Installation Process

1. Identify Device: Use device name (client1, client2, etc.)
2. Check Network and Domain: Ensure devices are connected and online
3. Locate Client Software: (ccmsetup.exe)
   • Found under Program Files -> Microsoft Configuration Manager -> Client
4. **Copy and Run Installation: **
   • Copy ccmsetup.exe to the client UR several showing C$ as root
   • Run as administrator
5. Verify Installation: Check Task Manager for background processes
6. **Software Center Installation: **
   • Should appear in Start menu
   • Configuration Manager properties in Control Panel for policy updates (e.g., application deployment evaluation)
7. Troubleshoot: Utilize action cycles in Configuration Manager properties to force policy updates

Server-Side Software Deployment

• Microsoft Endpoint Configuration Manager: Central control for pushing software updates
• Devices Status: Active (green check mark) vs. inactive/offline
• Deployment Process:
  • Create Package: Using various software (e.g., ccm.exe, 7-Zip, Adobe Reader)
  • Distribute to Clients: Push package to clients, ensure distribution points are accessible

Detailed Deployment Steps

• **Create Software Package: **
  1. Identify Needs: Selection dependent on business requirements
  2. Package Files: Ensure files are accessible to domain users and computers
  3. Package Creation: Using Microsoft Endpoint Manager
  4. Use Network Path: Essential for distributed access
  5. Deploy Package: Specify distribution points, client installation behavior
  6. Testing: Confirm availability on client machines

Advanced Features and Tools

Client Center for Configuration Manager

• **Purpose: **Remote management of client installations without server admin access
• Functions:
  • Remotely install/repair client software
  • Monitoring software distribution (e.g., advertisements, updates)
  • Inventory management: View installed software, execution history

Automation and Scripting

• **Potential Uses: **Automate repetitive tasks (e.g., refresh cycles, reboots)
• **Creating Scripts: ** Within Endpoint Manager—scheduled tasks for large-scale management

Summary

• **Key Takeaways: **
  • Automated software installation simplifies IT operations
  • Utilization of Endpoint Manager ensures central control and efficiency
  • Understanding server/client relationship crucial for troubleshooting
  • Advanced tools like Client Center enhances remote management capabilities

Future Topics

• Windows Updates Management: Pushing and managing updates
• Scripting: Creating and deploying scripts within Endpoint Manager
• Further Q&A: Encouragement to ask questions and interact for deeper understanding