So I have someone send out a joke .ppt file in my office, and now im getting requests from users to install powerpoint on their machine. I know its because of the joke email, because its from users who would never need powerpoint for their job.

How do you handle requests like this. I try to get them to explain to me exactly why they need it, that software is not free, the license is about $400 (for office 2010 STD OPL) and if they absolutely need it for business-related matters, I will seek approval from the vice president.

That usually gets them to be quiet.

How do you handle these types of requests?

Dani AI

Generated

A short, practical primer for handling requests like this: the problem isn’t a single PowerPoint file — it’s an entitlement and enforcement gap. The objective is simple: make the legitimate path easy and the ad‑hoc path impossible, while keeping a clear audit trail so decisions are defensible. ’s emphasis on compliance is the right starting point.

Put a lightweight policy and workflow in place. Keep the policy to one page (who gets what by default, who approves exceptions). Route every request through the ticket system with a one‑field business justification and manager sign‑off. Triage requests automatically against an “approved apps” catalog so common needs are fulfilled quickly; anything outside the catalog goes to a short approval chain (manager → procurement/IT). For one‑off viewing needs, offer a centrally managed read‑only render or PDF conversion so users don’t need full installs.

Use the right technical controls and inventory tools. Enforce least privilege (block local installs), push approved software from a central deployment tool, and implement application whitelisting or software restriction rather than ad‑hoc hacks. Keep a software asset register and reconcile deployed copies against purchased licenses on a schedule; use that data to justify purchases or denials. For people who genuinely need elevated rights, provide controlled, auditable elevation (temporary accounts, JIT privileges, or a managed admin pool) rather than full permanent admin rights.

Finally, make it cultural: publish an Acceptable Use note, train users briefly on why compliance matters, and measure a few simple KPIs (percent requests fulfilled from catalog, average approval time, license reconciliation rate). That gives you defensible rejections and makes the whole process repeatable. Credit to for highlighting formality and to and for reminding us of the operational tradeoffs — avoid destructive fixes and prefer documented, auditable controls.

Recommended Answers

All 10 Replies

Give them the free then fire them for wasting time viewing joke emails during work hours :)

Well but in all seriousness, why should I give them the free powerpoint viewer? Honestly. If there is no reason they would need it other than to view joke ppt files, which I dont want them wasting time with, why should they have even the viewer?

If there is no reason other than that, then no, they don't get it. But I've never worked in a place where the bosses didn't send out ppt slides of various company presentations (how well we are doing, how bad we are doing, why you need to work smarter, not harder, etc.) It always been pretty standard that they all get PPT viewer, Word viewer, etc.

One thing to consider: Will you spend more time explaining why they can't have the viewer software than you would spend giving it to everyone?

How do you handle these types of requests?

I would require them to fill out a software request form with business justification. Then if the justification doesn't have a suitable ROI for the license and maintenance costs, that would give me a defensible position for rejecting the request.

Will you spend more time explaining why they can't have the viewer software than you would spend giving it to everyone?

Frankly, yes. :)

Im fairly new here, about 6 months, as being the IT manager. Before me they hadno IT management. People got into the habit of asking for software and they would just install it. They gave little to no thought to licensing and software compliance.

Now im here and im changing that. If you have no use for it, you dont get it. We stay compliant.

Now I know that powerpoint viewer is free. But I want to break people of this habit that they can get whatever they want if they ask for it. If you dont need it, you dont get it.

And as we speak hes already admitted that it is in fact the joke ppt he wants to open, and now he knows if he wants powerpoint, he will have to speak to the vice president (who I answer to) for approval, and tell him why he wants it.

He wont.

Our problem wasn't that the users were requesting unnecessary software and upgrades. Outside agencies would upgrade to newer versions of programs like Word, Excel and Visio and we would be unable to open the files without the appropriate upgrades. For that we had no choice but to upgrade. Our biggest problem was users installing unauthorized software. We would uninstall and the software would reappear. Then I got creative. I wrote a zapper which would flip a byte in the exe so that the user would get "This is not a Windows application" on running the program. I had a list of authorized programs. Anything that wasn't on that list got zapped at regular and frequent intervals. The users couldn't complain about problems with software they weren't supposed to have and I never had to remove the software.

For reasons which I will not go into here, this certain class of users were required to have administrative access to their computers. It's partly political and partly technical.

For reasons which I will not go into here, this certain class of users were required to have administrative access to their computers. It's partly political and partly technical.

which means they were either managers (who get it for political reasons) or developers (who NEED it (and the ability to install and run software without your approval) for technical reasons).
If managers, you did right.
If developers, you hurt your company massively for your personal glory.

which means they were either managers [...] or developers [...]

That's an unwarranted assumption. I've seen quite a few organizations where regular employees who have no business with administrative accounts are local administrators.

They were system operators who used the computers to control several billion dollars worth of power grid equipment and would not accept the idea that they could not be trusted with admin rights on a $3000 PC. Also, there was a critical app developed by an outside company which required admin rights.

so you trust them with billions of equipment, but not with a cheap PC?
And you think it's strange they're p*ssed off about that?

Like I said, you're the problem here.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.