https://github.com/tommyvange/printer-management-scripts
PowerShell scripts for installing, uninstalling, and verifying network printers on Windows, optimized for both manual and automated deployments like Intune. Licensed under GPLv3.
https://github.com/tommyvange/printer-management-scripts
deployment intune powershell printer printer-management
Last synced: 5 months ago
JSON representation
PowerShell scripts for installing, uninstalling, and verifying network printers on Windows, optimized for both manual and automated deployments like Intune. Licensed under GPLv3.
- Host: GitHub
- URL: https://github.com/tommyvange/printer-management-scripts
- Owner: tommyvange
- License: gpl-3.0
- Created: 2024-06-06T08:04:38.000Z (almost 2 years ago)
- Default Branch: main
- Last Pushed: 2025-02-07T10:36:33.000Z (about 1 year ago)
- Last Synced: 2025-10-25T04:43:38.610Z (5 months ago)
- Topics: deployment, intune, powershell, printer, printer-management
- Language: PowerShell
- Homepage:
- Size: 76.2 KB
- Stars: 0
- Watchers: 1
- Forks: 1
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# Printer Management Scripts
These scripts are designed to install and uninstall network printers on Windows machines. They can read parameters from the command line, a configuration file (`config.json`), or use default values. If any required parameter is missing and cannot be resolved, the scripts will fail with an appropriate error message.
This repository is licensed under the **[GNU General Public License v3.0 (GPLv3)](LICENSE)**.
Created by **[Tommy Vange Rød](https://github.com/tommyvange)**. You can see the full list of credits [here](#credits).
## Configuration
The scripts use a configuration file (`config.json`) to store default values for the printer settings. Here is an example of the configuration file:
``` json
{
"PrinterHostAddress": "111.22.33.444",
"PortName": "IT_PRINT",
"DriverName": "HP Universal Printing PCL 6",
"PrinterName": "IT",
"Logging": true
}
```
## Install Script
### Description
The install script adds a printer port and a printer using the specified parameters. It checks if the port and printer already exist and takes appropriate actions to ensure they are correctly configured.
### Usage
To run the install script, use the following command:
``` powershell
.\install.ps1 -PrinterHostAddress "" -PortName "" -DriverName "" -PrinterName "" [-Logging]
```
### Parameters
- `PrinterHostAddress`: The IP address of the printer.
- `PortName`: The name of the printer port.
- `DriverName`: The name of the printer driver.
- `PrinterName`: The name of the printer.
- [Optional] `Logging`: Enables transcript logging if set.
### Fallback to Configuration File
If a parameter is not provided via the command line, the script will attempt to read it from the `config.json` file. If the parameter is still not available, the script will fail and provide an error message.
### Example
To specify values directly via the command:
``` powershell
.\install.ps1 -PrinterHostAddress "111.22.33.555" -PortName "CUSTOM_PORT" -DriverName "Custom Driver" -PrinterName "Custom Printer" [-Logging]
```
To use the default values from the configuration file:
``` powershell
.\install.ps1
```
### Script Workflow
1. Check if the printer port exists.
2. If the port exists, verify that it points to the correct IP address.
3. If the printer exists, remove it and its associated port.
4. Add the printer port if it doesn't exist or was just removed.
5. Add the printer.
## Uninstall Script
### Description
The uninstall script removes a specified printer and its associated port. It checks if the printer and port exist before attempting to remove them, ensuring no unnecessary errors are thrown. Additionally, it checks if any other printers are using the specified port and removes them before deleting the port.
### Usage
To run the uninstall script, use the following command:
``` powershell
.\uninstall.ps1 -PortName "" -PrinterName "" [-Logging]
```
### Parameters
-`PortName`: The name of the printer port.
-`PrinterName`: The name of the printer.
-[Optional] `Logging`: Enables transcript logging if set.
### Fallback to Configuration File
If a parameter is not provided via the command line, the script will attempt to read it from the `config.json` file. If the parameter is still not available, the script will fail and provide an error message.
### Example
To specify values directly via the command:
``` powershell
.\uninstall.ps1 -PortName "CUSTOM_PORT" -PrinterName "Custom Printer" [-Logging]
```
To use the default values from the configuration file:
``` powershell
.\uninstall.ps1
```
### Script Workflow
1. Check if the printer exists.
2. If the printer exists, remove it.
3. Check if any other printers are using the specified port and remove them.
4. If the port exists, remove it.
## Check Printer Script
### Description
The check printer script verifies if a specified printer exists and outputs "Detected" or "NotDetected". It uses exit codes compatible with Intune: `0` for success (detected) and `1` for failure (not detected).
### Usage
To run the check printer script, use the following command:
``` powershell
.\check.ps1 -PrinterName "" [-Logging]
```
#### Usage without `config.json` or Command Arguments
If you are running this as a check script in environments such as Intune, it is best to populate the variables directly in the code. Intune does not allow passing CLI arguments or using `config.json` for check scripts, so the only way is to set the variables within the script itself.
The script includes a section designed for this purpose:
``` powershell
# Manually fill these variables if using environments like Intune
# (Intune does not support CLI arguments or configuration files for check scripts)
#
# $ManualPrinterName = "PRINT (Color)"
# $ManualLogging = $false # Set to $true to enable logging
```
To use this feature, simply uncomment these lines and populate the variables with your desired values. The script will prioritize these manual settings over CLI arguments and config.json, ensuring that the specified data is used during execution. This approach allows seamless integration with Intune and similar deployment tools.
#### Detecting Printers via Registry (Intune)
When deploying printer settings via Intune, it's often necessary to detect whether a specific printer is already installed on the target machines. This can be achieved by checking the registry for the presence of the printer. Here are the detailed steps and settings required to create a detection rule in Intune using the registry:
##### Rule Type: Registry
1. **Rule Type**: Registry
##### Key Path
- **Key Path**: `HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Printers\`
- Replace `` with the actual name of the printer you want to detect.
##### Value Name
- **Value Name**: `Name`
##### Detection Method
- **Detection Method**: String comparison
##### Operator
- **Operator**: Equals
##### Value
- **Value**: ``
- Replace `` with the actual name of the printer.
### Parameters
- `PrinterName`: The name of the printer to check.
- [Optional] `Logging`: Enables transcript logging if set.
### Fallback to Configuration File
If a parameter is not provided via the command line, the script will attempt to read it from the `config.json` file. If the parameter is still not available, the script will fail and provide an error message.
### Example
To specify values directly via the command:
``` powershell
.\check.ps1 -PrinterName "Custom Printer" [-Logging $true]
```
To use the default values from the configuration file:
``` powershell
.\check.ps1
```
### Script Workflow
1. Check if the printer name is provided.
2. Start transcript logging if enabled.
3. Check if the printer exists.
4. Output "Detected" if the printer exists, otherwise output "NotDetected".
## Logging
### Description
Both the install and uninstall scripts support transcript logging to capture detailed information about the script execution. Logging can be enabled via the `-Logging` parameter or the configuration file.
### How It Works
When logging is enabled, the scripts will start a PowerShell transcript at the beginning of the execution and stop it at the end. This transcript will include all commands executed and their output, providing a detailed log of the script's actions.
### Enabling Logging
Logging can be enabled by setting the `-Logging` parameter when running the script, or by setting the `Logging` property to `true` in the `config.json` file.
### Log File Location
The log files are stored in the temporary directory of the user running the script. The log file names follow the pattern:
- For the install script: `printer_install_log__.txt`
- For the uninstall script: `printer_uninstall_log__.txt`
Example log file paths:
- `C:\Users\\AppData\Local\Temp\printer_install_log_IT_IT_PRINT.txt`
- `C:\Users\\AppData\Local\Temp\printer_uninstall_log_IT_IT_PRINT.txt`
**System Account Exception**: When scripts are run as the System account, such as during automated deployments or via certain administrative tools, the log files will be stored in the `C:\Windows\Temp` directory instead of the user's local temporary directory.
## Error Handling
Both scripts include error handling to provide clear messages when parameters are missing or actions fail. If any required parameter is missing and cannot be resolved, the scripts will fail with an appropriate error message.
## Notes
- Ensure that you have the necessary permissions to add and remove printers and ports on the machine where these scripts are executed.
- The scripts assume that the printer driver specified is already installed on the machine.
## Troubleshooting
If you encounter any issues, ensure that all parameters are correctly specified and that the printer driver is installed. Check the error messages provided by the scripts for further details on what might have gone wrong.
## Credits
### Author
You can find more of my work on my [GitHub profile](https://github.com/tommyvange) or connect with me on [LinkedIn](https://www.linkedin.com/in/tommyvange/).
### Contributors
Huge thanks to everyone who dedicates their valuable time to improving, perfecting, and supporting this project!
# GNU General Public License v3.0 (GPLv3)
The **GNU General Public License v3.0 (GPLv3)** is a free, copyleft license for software and other creative works. It ensures your freedom to share, modify, and distribute all versions of a program, keeping it free software for everyone.
Full license can be read [here](LICENSE) or at [gnu.org](https://www.gnu.org/licenses/gpl-3.0.en.html#license-text).
## Key Points:
1. **Freedom to Share and Change:**
- You can distribute copies of GPLv3-licensed software.
- Access the source code.
- Modify the software.
- Create new free programs using parts of it.
2. **Responsibilities:**
- If you distribute GPLv3 software, pass on the same freedoms to recipients.
- Provide the source code.
- Make recipients aware of their rights.
3. **No Warranty:**
- No warranty for this free software.
- Developers protect your rights through copyright and this license.
4. **Marking Modifications:**
- Clearly mark modified versions to avoid attributing problems to previous authors.
