-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathREADME.md
More file actions
85 lines (59 loc) · 2.92 KB
/
Copy pathREADME.md
File metadata and controls
85 lines (59 loc) · 2.92 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
# Win32 Application Deployment with Microsoft Intune
## Google Chrome Enterprise Packaging, Assignment and Detection
A hands-on Microsoft lab demonstrating the end-to-end packaging and deployment of a Win32 application through Intune.
> **Lab environment:** This project was completed independently in a personal Microsoft lab. All identities, devices and configuration details are lab data.
## Project Summary
| Area | Implementation |
|---|---|
| Business requirement | Deploy software consistently to managed Windows devices |
| Application | Google Chrome Enterprise |
| Package format | .intunewin |
| Installation method | Silent MSI installation |
| Validation | MSI product-code detection and endpoint verification |
## Architecture
```mermaid
flowchart TD
A["Chrome Enterprise MSI"] --> B["Win32 Content Prep Tool"]
B --> C[".intunewin package"]
C --> D["Microsoft Intune"]
D --> E["Required assignment"]
E --> F["Managed Windows device"]
F --> G["Detection and reporting"]
```
## Scenario
Manual software installation is difficult to control and scale. This project tested whether a standard enterprise application could be packaged, deployed silently and detected reliably through Microsoft Intune.
## What I Implemented
### Application Packaging
- Downloaded the Google Chrome Enterprise installer
- Packaged the source files using the Microsoft Win32 Content Prep Tool
- Created an `.intunewin` package for upload
### Intune Configuration
- Added the application as a Win32 app
- Configured a silent `msiexec` installation command
- Set x64 and minimum Windows-version requirements
- Created an MSI product-code detection rule
- Assigned the application as Required to managed devices
### Validation
- Reviewed application deployment reporting in Intune
- Confirmed successful installation on the endpoint
- Verified that the detection rule recognised the installed application
## Validation Results
| Test | Expected result | Observed result |
|---|---|---|
| Device receives required assignment | Installation begins without user interaction | Silent deployment started |
| Installation completes | Chrome is available on the endpoint | Application installed |
| Detection rule evaluates | Intune reports application as installed | Installed status reported |
## Outcome
The lab demonstrated a complete Win32 application lifecycle from packaging through silent deployment, detection and reporting.
## Skills Demonstrated
- Microsoft Intune
- Win32 application deployment
- Microsoft Win32 Content Prep Tool
- MSI and msiexec
- Detection rules
- Application requirements
- Assignment and reporting
## Technical Documentation
[View the full technical documentation (PDF)](https://github.com/guyleonchen/Intune-Win32-Application-Deployment/blob/main/Lab10%20Deploying%20a%20Win32%20Application%20(Google%20Chrome)%20Using%20Microsoft%20Intune.pdf)
---
[Return to Guy Cheneval's GitHub profile](https://github.com/guyleonchen)