User Profile
nclinch
Iron Contributor
Joined 6 years ago
User Widgets
Recent Discussions
Re: Universal Print PowerShell reliability
Saurabh_Bansal The output from PowerShell cmdlets have changed (See attached)... breaking my scripts... I see you do have some reliability/retry added to help out when you do not get all of the output from the cmdlet. Anyway did I miss an announcement that the PowerShell module was updated with breaking changes? Using ContinuationToken https://learn.microsoft.com/en-us/universal-print/fundamentals/universal-print-ps-printer-properties-sample#using-continuationtoken I have attached some output from cmdlets before the change. Now instead of the properties "name" (Get-upprinter) and "sharename" (Get-UppPrintershare). we now have DisplayNameTrusted certificate profile in Intune Stuck at Pending
We need to deploy our Root CA and subordinate issuing CA Certificates to our Intune managed AAD only devices to support SCEP. We created a trusted certificate profile in Intune to provision these certs but however comma this profile is stuck at pending... How do I troubleshoot what is going on? Microsoft how have I failed you 😞 Intune supports use of the Simple Certificate Enrollment Protocol (SCEP) to https://learn.microsoft.com/en-us/mem/intune/protect/certificates-configure. SCEP uses the Certification Authority (CA) certificate to secure the message exchange for the Certificate Signing Request (CSR). When your infrastructure supports SCEP, you can use Intune SCEP certificate profiles (a type of device profile in Intune) to deploy the certificates to your devices. https://learn.microsoft.com/en-us/mem/intune/protect/certificates-scep-configure#certificates-and-templates To use a SCEP certificate profile, devices must trust your Trusted Root Certification Authority (CA). Use a trusted certificate profile in Intune to provision the Trusted Root CA certificate to users and devices.Universal Print PowerShell reliability
I have a script that checks on if our Technicians Add Printers to Universal Print (UP) Correctly. 1) Ensure That Universal Print Printers Are Shared 2) Ensure All Users Are Granted Access To Printer Shares 3) Ensure Location Site Property Is Set To 4 Digit Store Number 4) Report Printers That Do Not Match The Naming Convention Anyway this relies on the UP PowerShell module and the results it gives are inconsistent. We had similar issues in the past with the MSGraph API. I need the cmdlets in the module to return an error if they are not working right. that way I know when the data I am getting is not correct.
