Entra joined devices can find DCs when they’re on the same network and when DNS is configured correctly, also name resolution works fine. Directly on the same network, but also via VPN/ zero-trust solutions

As written in the post, we have to be creative 🙂
I think a lot of different approaches are used to overcome these kind of challenges.

And I even pasted an incorrect code (facepalm)
It should be ‘return $returnCode’

function Set-NewPrinter {
[cmdletbinding()]
param (
[Parameter (Mandatory=$true)][string]$printerName,
[Parameter (Mandatory=$true)][string]$printServer
)

$returnCode = 0 # successfully mapped – at least added a job that will map it

$printer = “\\” + $printServer + “\” + $printerName
Write-Verbose “Printer: $printer”
$printerFound = Get-Printer -Name $printer -ErrorAction SilentlyContinue
Write-Verbose “Printer found: $printerFound”

if (-not $printerFound) {

$pingtest = Test-Connection -ComputerName $printServer -Quiet -Count 1 -ErrorAction SilentlyContinue
Write-Verbose “Ping test: $pingtest”

if($pingtest){

try {

$addPrinter = Add-Printer -ConnectionName $printer -AsJob -Verbose
Write-Verbose “$printServer;$printerName;Add-Printer-AsJob”

} catch {
Write-Verbose “Exception while adding printer.”
Write-Verbose $_ -ForegroundColor Red
$returnCode = 99 # Exception
}

} else{
Write-Verbose “$printServer is not reachable”
$returnCode = 50 # printServer is not reachable
}

} else { # if (-not (Get-Printer -Name $printer))
Write-Verbose “$printServer;$printerName;printerFound”
$returnCode = 1 # OK, printer found – already mapped
}

return $errorCode

}

Set-NewPrinter -printServer MyPrintServer -printerName MyPrinter