So, what can you do?
This method is not supported by Microsoft and most Microsoft geeks will tell you not to do this, but it works and if you are willing to chance it then go for it. But, before doing anything, make a backup of your SCCM database so you can go back in case it all goes wrong! You should open up your SQL console and we will need to edit the following table within your SCCM database:UserApplicationRequestsFirst of all, you can run a SQL statement against your SCCM database to see what is in the table, to do this, run this SQL script:
SELECT * FROM UserApplicationRequestsIn this table, you will see your users information and the details of their software request from the Application Catalog. In the CurrentState column, this will give you the current state of the request. Each number is represented as per below: 1 – Requested 2 – Cancelled 3 – Denied 4 – Approved From here, you can now change the status of the requests, like changing an Approved request (4) to a Denied request (3) – this means that the person that has requested the software that had previously had it approved, will now not be able to install the software on any machine. If you want to completely clean up your requests, you can delete all the information in this table.
Feedback
If you have any questions or comments on this guide, then please feel free to leave us a message using our comments system below.Gear We Recommend
Testing configs is easier with a dedicated admin machine set up right. Here’s the kit we use.
Browse our Windows Admin Toolkit picks on AmazonAs an Amazon Associate, TechyGeeksHome earns from qualifying purchases.
Discover more from TechyGeeksHome
Subscribe to get the latest posts sent to your email.