Convert iniToOMACSVTemplate.ps1 Usage

This script can be used to capture an ini configuration to an Intune ADMX backed profile. The output can be uploaded using the Invoke-CSVToIntuneUpload.ps1 script.

Parameter

Name	Datatype	Description	Sample
FilePath	string	Specify the path to the file you want to capture.	c:\Users\MyUser\Appdata\Roaming\vlc\vlcrc
PathOnTargetSystem	string	This is the path to the file on the target system. You may use envoirenment variables here in the way you use them in the cmd (So with a %-sign the beginning and at the end).	%APPDATA%\vlc\vlcrc
AppName	string	This is the name of your app. This is used in the backend to generate the OMA-URIs and names in Intune. With AppPolicyName together this value should be unique.	VLC media player
AppPolicyName	string	This is the name of your your policy (so for example the file you capture). This is used in the backend to generate the OMA-URIs and names in Intune. With AppName together this value should be unique.	vlcrc
Context	User or Machine	This specified in which context the configuration gets applied. Use user to make the configuration user dependent and system for system wide configuration.	User
Operation	Create, Update, Replace (Default), Delete	This is the default operation of your created configuration. You should use replace here for policy like configuratins (That get enforced) or create for recommended configurations.	Replace
OutputFilePath	String	This is where the Intune configuration profile gets saved as a csv file. You can upload this file to Intune using the Invoke-CSVToIntuneUpload.ps1 script.	c:\PolicyApplicator\vlcrc_production.csv

Format of the input file

This script works on all kind of ini files that are written in the following format:

NoSectionKey=Value1

[Section1]
Section1Key1=Value2
Section1Key2=Value3

[Section2]
Section2Value1=Value4

The files does not need to define sections. In this case everything is treated like the NoSectionKey.