Skip to main content

How to launch Java control panel applet via command line


To launch windows control panel applet via command line.

You type "control" plus windows panel applet that has ".cpl" extensions.

But a third party application that is on the control panel does not have ".cpl" extensions.

So how would you launch those applications?

Why on earth would you need to launch the application via command line when there is a GUI?

If you're working in Active Directory domain environment you can’t just give the user an admin rights just for the sake of disabling something.

And users are requesting to disable the "Auto Update", early in the morning Java is asking for updates and they haven't finished their cup of coffee.

So what would you do?

Well, Java is quite friendly and they provide some command line tool to disable it.

Run the command prompt as "Administrator" key in the user domain admin details.

Once inside the elevated domain admin prompt.

Just type:
  
          javaws  -viewer

Voila! the control panel applet pops up and just one tick away to disable the "Auto Update".


That's it.. But it's not good to disable "Auto Update".. Anyway choice is yours option is there.


Cheers!!! Till next time…

=====================
Android app to learn multiplication for kids:

https://play.google.com/store/apps/details?id=com.xmultiplication

Linux Android App cheat sheet:
https://play.google.com/store/apps/details?id=com.LinuxMobileKit



Comments

  1. When attempting to launch a Ubisoft, Uplay displays the error "A Ubisoft service is momentarily unavailable." Every Ubisoft game must have Uplay, which controls digital distribution, DRM, multiplayer, and chat. The problem notice shows when you try to launch a game or log into Uplay on your PC. The techniques used by numerous people to fix A Ubisoft Service Is Currently Unavailable on their machines were shared online.a ubisoft service is currently unavailable

    ReplyDelete

Post a Comment

Popular posts from this blog

WMIC get computer name

WMIC get computer model, manufacturer, computer name and  username. WMIC is a command-line tool and that can generate information about computer model, its manufacturer, its username and other informations depending on the parameters provided. Why would you need a command line tool if there’s a GUI to check? If you have 20 or 100 computers, or even more. It’s quite a big task just checking the GUI to check the computer model and username. If you have remote computers, you need to delegate someone in the remote office or location to check. Or you can just write a batch file or script to automate the task. Here’s the code below on how get computer model, manufacturer and the username. Open an elevated command prompt and type:     wmic computersystem get "Model","Manufacturer", "Name", "UserName" Just copy and paste the code above, the word “computersystem” does not need to be change to a computer name. A...

Print error 016-799 - Fuji Film Xerox

016-799 Fuji Xerox or Fuji Film print error code. That shows a description error as “Print instruction Fail detected in decomposer.” The error code and error description are alien languages for users and even system administrators who are not familiar with Fuji Xerox error code. The error code is quite simple and easy to fix, if the job print goes to the printer but print out doesn’t come out. So, basically the print job was received by the printer, but the printer just doesn’t know what type of paper or what size to use or which tray to utilize for the print out. In some instances, this is just a paper mismatch but the error description; if using Windows 10 to print does not exactly points to what is the issue. First thing to check, is the paper size selected by the user to print. Example, if the printer configuration is A3 and A4 sizes only. But then the person printing the file accidentally chooses “A4 Cover” then this error 016-799 will occur. ...

How to check office version from command line

The are quite a few ways to check office version it can be done via registry, PowerShell or VBScript and of course, good old command line can also do it. Checking Windows office version whether it is Office 2010, Office, 2013, Office 2016 or other version is quite important to check compatibility of documents; or just a part of software inventory. For PowerShell this simple snippet can check the office version: $ol = New-Object -ComObject Excel.Application $ol . Version The command line option will tell you where’s the path located; the result will also tell whether office is 32-bit, 64-bit and of course the version of the office as well. Here’s the command that will check the office version and which program directory the file is located which will tell whether it’s 32-bit or 64-bit. Command to search for Excel.exe: DIR C:\ /s excel.exe | find   /i "Directory of"  Above command assumes that program files is on  C: drive. Sample O...