Search This Blog

Showing posts with label Software Installation. Show all posts
Showing posts with label Software Installation. Show all posts

04 December, 2024

The Curious Case of the Incomplete SCCM Request

The Curious Case of the Incomplete SCCM Request

It was another Monday morning, and you’d barely settled into your chair when the email popped up: “Hey, can you automate the install of [Insert Application of the Week]? Thanks!”

Simple enough, right? Except experience told you that “simple” was a trap. Behind every “simple install” lurked unspoken dependencies, forgotten configurations, and that one obscure setting buried in a 200-page admin guide. This time, though, you were ready. You’d developed a system—a foolproof way to gather all the prerequisites and turn chaos into a smooth, automated masterpiece.

Here’s how you do it.

Start With a Gentle Interrogation

Your first move? Respond to the request with some polite but pointed questions. You’re not grilling a suspect—you’re just… clarifying.

  • What exactly do you want this to do?
    Is the goal to install the app and call it a day, or are there follow-ups like configurations, license activations, or mysterious registry keys?
  • What does “working” look like to you?
    Is it just sitting there quietly installed, or does it need to hum a specific tune on startup?
  • What could go wrong?
    If you’ve ever been told, “It works fine on the test machine,” you know this question is worth its weight in log files.

Asking the right questions upfront saves you from playing a game of “Who Broke It?” later.

Gather the Sacred Prerequisites

Every automation project has its holy relics—those bits of information and tools you must collect before starting your quest.

  1. The Installer
    Is it an MSI, an EXE, or something rarer, like a proprietary installer with no silent mode (cue dramatic sigh)? If it's an MSI, confirm the silent install switches (/quiet /norestart) and any custom properties.

  2. Dependencies
    Does this app need .NET, Java, or the collective hopes and dreams of the IT department? Make a list. Don’t forget drivers, libraries, or network permissions.

  3. Configuration Settings
    Are there configuration files to edit? Registry keys to add? Licensing servers to point to? Clarify if these need to be machine-wide or user-specific.

  4. Testing Criteria
    How will you verify the installation? Write a script or a test plan. Even a basic "open the app and poke at it" plan is better than crossing your fingers.

  5. Rollback Plan
    No one likes to think about failure, but it’s better to plan for it than to discover mid-install that your only rollback strategy is "unplug the computer and pray."

Beyond MSI: Tackling Configurations

Let’s say the install is only part of the job. Maybe the app needs some post-install TLC:

  • Configuration Files: You can automate edits to .INI, .JSON, or XML files with PowerShell.
  • Registry Keys: A little Set-ItemProperty action in PowerShell works wonders.
  • Service Connections: Does the app need to talk to a server or database? If yes, automate the setup and test the connection.

The key here is modularity. Each step should work on its own, like a Lego block. If the post-install fails, the install itself should remain intact.

The Magic of Application Groups

Now, what if you need to install not one but several applications, each with its quirks and dependencies? Enter SCCM application groups, the Swiss Army knife of multi-app deployments.

With application groups, you can:

  • Maintain Order: Specify the install sequence to avoid, say, installing the app before its dependencies.
  • Keep It Modular: Each application can have its detection methods and install/uninstall scripts.
  • Make Updates Easy: Need to tweak one component? No problem—you can update it without redoing the whole group.

For example, automating a developer workstation setup might include:

  1. Installing Visual Studio.
  2. Configuring Git.
  3. Setting up Node.js.
  4. Running a custom PowerShell script to pull environment settings.

Each step is managed individually but deployed as a seamless package. Efficiency and control? Check and check.

The PowerShell Angle

PowerShell is your best friend here. Let’s break it down:

  1. Pre-Checks: Before you do anything, make sure the system is ready. Check for disk space, existing dependencies, or incompatible versions.

    if ((Get-Volume -DriveLetter C).SizeRemaining -lt 10GB) { Write-Error "Not enough disk space!" exit }
  2. Silent Installation: Automate the install with Start-Process or SCCM cmdlets.

    Start-Process "msiexec.exe" -ArgumentList "/i MyApp.msi /quiet /norestart" -Wait
  3. Post-Install Tasks: Add configurations, apply registry keys, or start services.

    Set-ItemProperty -Path "HKLM:\Software\MyApp" -Name "ConfigKey" -Value "ConfigValue"
  4. Validation: Always test. Whether it’s as simple as checking for a file or as complex as running a test script, make sure you verify success.

The Final Word

Automation isn’t just about making life easier (though it definitely does that). It’s about creating robust, repeatable processes that reduce errors and free you to tackle more exciting challenges. By asking the right questions, gathering prerequisites, and embracing tools like PowerShell and SCCM application groups, you’ll deliver solutions that go beyond "just works" to "works beautifully."

And the next time someone asks for a “simple install,” you’ll smile, knowing you’re already three steps ahead.

11 November, 2024

Installing Winget: The Secret Weapon for Windows Package Management

Installing Winget: The Secret Weapon for Windows Package Management

What’s This "Winget" Everyone’s Talking About?

If you’ve ever wished Windows had a quick, no-nonsense way to install, update, and manage software—without hunting down installers and clicking through dialogs—Winget is the answer. Think of Winget as the Windows version of app managers like Homebrew (Mac) or APT (Linux), built for getting software onto your computer faster, easier, and in a techie-cool kind of way.

In this article, I’ll walk you through what Winget is, why it’s worth using, and how you can get it set up on your system.

Why Use Winget?

Installing apps manually on Windows can be, let’s face it, a bit of a hassle. Open your browser, find the right download page, hope you don’t accidentally click on an ad, and then slog through the setup steps. But with Winget, that all changes.

Here’s what Winget lets you do:

  • Install software in seconds: Just a quick command and you’re good to go.
  • Update everything: One command can update all installed apps, sparing you from those annoying update notifications.
  • Manage installations easily: No need to hunt through the Control Panel to uninstall a program—Winget handles it.

In short, Winget saves you time and makes managing your apps easy and fast.


Setting Up Winget on Your System

There are two main ways to install Winget: manually, through GitHub, or via the Microsoft Store. Let’s cover both.


Option 1: Installing Winget through the Microsoft Store (Quick and Easy)

If you’re using a compatible version of Windows, this is the quickest way to get Winget.

  1. Open the Microsoft Store: Click on the Microsoft Store icon in your taskbar or search for “Microsoft Store” in the Start Menu.

  2. Search for “App Installer”: Type "App Installer" in the Microsoft Store’s search bar. Winget is packaged with App Installer, so installing this will give you access to Winget.

  3. Install the App Installer: Click on the App Installer result and hit the Install button. This will automatically install Winget on your system.

  4. Verify the Installation: After installation, open PowerShell or Command Prompt and type:

    winget

    Press Enter. If everything installed correctly, you should see the Winget command-line interface.


Option 2: Manually Installing Winget via GitHub

Prerequisites

Before you dive in, make sure you have:

  • A computer running Windows 10 (version 1809 or later) or Windows 11.
  • Administrator privileges (you’ll need this to install Winget).
  • An internet connection to download Winget.

Step 1: Download the Installer

  1. Go to the official Winget GitHub releases page.
  2. Find the most recent release and download the .msixbundle file. This is the all-in-one package for getting Winget installed on your system.

Step 2: Install Winget with PowerShell

  1. Open PowerShell with Administrator Privileges: Press Win + X, and click on Windows PowerShell (Admin).

  2. Run the Installation Command: In PowerShell, type the following command, substituting C:\Path\To\File.msixbundle with the path where you saved the file:

    Add-AppxPackage -Path "C:\Path\To\File.msixbundle"

    Hit Enter, and PowerShell will take care of the rest.

Step 3: Check If It’s Working

Once installed, you’ll want to make sure everything’s set up correctly.

  1. Open PowerShell or Command Prompt.
  2. Type winget and hit Enter. If Winget is installed, you should see the Winget command-line interface with a list of available commands.

If you see that, congratulations—Winget is now your new Windows package manager!


Playing Around with Winget: Basic Commands You’ll Love

Now for the fun part. Here are some basic Winget commands to make managing your applications a breeze.

  • Search for an application: Find apps available for install.

    winget search <appname>
  • Install an application: Get any application onto your system quickly.

    winget install <appname>
  • Upgrade all your apps: This command saves you from updating everything individually.

    winget upgrade --all
  • Uninstall an application: When it’s time to let go of an app, Winget’s got you covered.

    winget uninstall <appname>

Winget’s Little Superpowers

One of the best things about Winget is its automation power. You can script commands for deploying applications across multiple machines, which is a lifesaver if you’re setting up multiple computers or managing software for a small team. Plus, it’s the kind of geeky automation that just feels cool to use.


Troubleshooting Tips

If something goes wrong, here are a few things to check:

  • Admin Privileges: Make sure PowerShell is running as Administrator.
  • Windows Version: Confirm that your system is on Windows 10 version 1809 or newer.
  • Download Issues: Sometimes, re-downloading the .msixbundle file can solve mysterious errors.

Summary of Installation Options

Installation Method Description
Microsoft Store Easiest option with automatic updates. Just search for and install App Installer in the Microsoft Store.
Manual Installation Best for users who want the latest release directly from GitHub. Requires PowerShell and a download of the .msixbundle file.

Conclusion: Welcome to the World of Winget

With Winget installed, you’ve officially leveled up your Windows game. Now, you can download, install, update, and manage software without ever opening a browser. Whether you’re a power user or just like the efficiency, Winget is a tool worth mastering.

Sources and Further Reading

  1. WinGet Documentation
  2. Winget GitHub Repository