Install SCCM Console on Windows 10: 3 Methods

• Windows 10 workstation with local administrator rights.
• Network access to the SCCM site server or a local copy of installation media.
• SCCM current branch 1902 or later (the four-file requirement applies from this version onward).
• All four required files in the same folder: ConsoleSetup.exe, AdminConsole.msi, ConfigMgr.AC_Extension.i386.cab, ConfigMgr.AC_Extension.amd64.cab.
• The fully qualified domain name (FQDN) of your primary site server.
• A user account with an assigned SCCM role-based access control (RBAC) security role.

CISA's 2026 endpoint management advisory explicitly recommends applying least privilege when designing administrative roles and using RBAC to assign only minimum permissions necessary. Verify your account's RBAC role before connecting the console for the first time. For a deeper look at configuring co-management roles alongside the console, see the ConfigMgr Device Configuration Workload Switch Guide.

Where Do You Find the SCCM Console Source Files?

Two canonical locations hold the source files. Pick based on what is reachable from the target machine.

From the site server share (preferred when the environment is already live):

\\<SiteServer>\<ShareName>\Tools\ConsoleSetup

From SCCM installation media (use this when the site server share is unreachable):

\SMSSETUP\BIN\I386

Copy the entire ConsoleSetup folder to a local path before you run anything. Partial copies, especially those missing the .cab files, produce a broken install. In our lab environment running CB 2309, omitting the .cab files caused exit code 1603 in ConfigMgrAdminUISetup.log every time, with no other warning during the wizard itself.

How Do You Install the SCCM Console Using the Setup Wizard?

Method A works best for one-off installs or when configuring a new admin workstation for the first time. No command-line interaction is needed.

1. On the Windows 10 machine, browse to the root of the SCCM installation media.
2. Launch splash.hta to open the Configuration Manager splash screen.
3. Under Tools and Standalone Components, click Install Configuration Manager Console.
4. The setup wizard opens. Click Next.
5. Enter the FQDN of your primary site server and click Next.
6. Accept or change the default installation directory, then click Next.
7. Click Install to begin, then Finish when complete.

This method guides you through every option visually. It is the slowest of the three, but also the least likely to produce a misconfigured install for admins who are new to the product.

How Do You Install the SCCM Console from the ConsoleSetup Folder?

Method B skips the splash screen entirely. It works best for IT teams who maintain a file share pre-staged with the console source files.

All four files must be present in the same folder before you begin.

1. Copy the entire ConsoleSetup folder to the local machine, for example C:\Temp\ConsoleSetup.
2. Right-click ConsoleSetup.exe and select Run as administrator.
3. On the Configuration Manager Console Setup window, click Install.
4. Click Finish when the wizard reports success.

This saves time for teams that pre-stage shares centrally, because there is no need to mount or distribute full installation media. The Microsoft Learn console installation reference documents the exact folder structure expected at this path.

How Do You Install the SCCM Console via Command Line?

Method C gives you the most control and is the right choice for scripted deployments, remote installs, or software packaging. The /q switch runs the install with zero UI.

Open an elevated command prompt and change to the directory holding the console source files.

Basic silent install:

ConsoleSetup.exe /q TargetDir="%ProgramFiles%\ConfigMgr Console" DefaultSiteServerName=MyServer.Contoso.com

Replace MyServer.Contoso.com with your actual site server FQDN.

Silent install with language packs:

The console defaults to English. To add language packs, include the LangPackDir parameter pointing at the folder that holds the language files:

ConsoleSetup.exe /q TargetDir="C:\Program Files\ConfigMgr Console" DefaultSiteServerName=MyServer.Contoso.com LangPackDir=C:\Downloads\ConfigMgr

Because the install runs unattended, there is no on-screen confirmation. Check the log files in the next section to confirm a clean exit code.

Where Are the SCCM Console Log Files?

Log files are your first stop when an installation fails or the console misbehaves after launch. Three files matter.

ConfigMgrAdminUISetup.log

SmsAdminUI.log

Smsprov.log

Open these with CMTrace or any text editor. Filter for lines tagged ERROR or WARNING and cross-reference the timestamp with when the failure occurred. The Install SCCM Fallback Status Point guide covers CMTrace usage in more detail if you are not familiar with the tool.

How Do You Verify the SCCM Console Installation Succeeded?

Run through these checks after any of the three methods before handing off the workstation.

• Open the Start Menu and search for Configuration Manager Console. It should appear as an installed application.
• Launch the console and confirm it connects to your site server without a certificate or authentication error.
• Go to Administration > Site Configuration > Sites and confirm the site name and code are visible.
• Review ConfigMgrAdminUISetup.log for a clean completion entry with no error codes.

If the console opens but cannot connect, verify the site server FQDN entered during setup. Also confirm the user account has an assigned SCCM security role. Missing RBAC assignments are a common cause of a successful install that still cannot reach the site.

A Note on Console Security and Credential Risk

The SCCM console is a high-value target. CISA warned that Configuration Manager "typically runs with elevated privileges and maintains deep integration with enterprise systems," making it capable of enabling malware deployment, credential harvesting, or silent manipulation of entire device fleets when compromised.

The 2025 Verizon Data Breach Investigations Report found that stolen credentials were the initial access vector in 22% of all breaches. That same report found that 46% of compromised enterprise systems with corporate logins in stolen credential data were unmanaged devices hosting both personal and business credentials. Installing the SCCM console on unmanaged or personal workstations puts admin credentials directly in that risk category.

Install the console only on managed, domain-joined workstations with endpoint protection in place. For Intune-managed environments, the Intune Assignment Groups targeting guide covers how to scope admin tools to specific device groups so personal machines are excluded automatically.