Auto deploying a package after Windows feature update (1809 > 1903) possible?
Hey guys, first off I'd like to say we love PDQ here! We are a small 3 man IT shop who runs things for a large Electric Co-op. PDQ has literally saved our lives.
So, here's the issue we're facing. We use 'Classic Shell' company wide here. It brings back the old style start button for everyone if you're not familiar. No one has local admin rights here and after a windows feature update, every time a user logs in, they are prompted for admin credentials to "allow" classic shell to "reconfigure" itself.
We have 132 PC's still running Windows 10 1809 and I want to allow our WSUS to push down 1903 but once that happens, i'm going to have 132 people calling me about the classic shell popup every time they log in. I have a PDQ package that uninstalls/reinstalls Classic Shell which works beautifully and fixes this issue BUT... I need to be able to set up a schedule that recognizes when a PC changes windows versions, it will automatically deploy that package. That way, the user will never be prompted for admin creds and will never know any difference. Is this even possible?
If anyone has any suggestions or other ideas on how to resolve this, please let me know! I know we can just uninstall it company wide and say "deal with the change" but even I myself enjoy the old style button and would like to keep it if we can.
Thanks so much!
-Lee
Comments
On the deployment side of things -
Off the cuff here but something like this.
Create file in a folder on c drive and title the file CS_Fixed_1903.
have deployment condition of if doesn't exists c:\CS_Fixed_1903.txt
Final step create file in the folder.
Create a schedule to run every hour or whatever you decide.
Target the deployment to the Inventory group of Windows 10 1903
then if you need to fix it in the future just delete the folder/file on the users computer.
Brian, that's pretty smart! Thanks for that idea!
If you don't a bunch of "Failed due to run conditions"
Have Inventory scan for the file in the path you create.
Create an Inventory Group with the following conditions
change the path to where you create the file...
Target the schedule to this new group...
When you run the fix have Deploy scan for the file after deployment and it will leave the group and on the next run of the schedule it will not be there to attempt the deployment.
That's genius! Thank you! You sir, are a saint.