Happy Thanksgiving 🦃 week from all of us at the Connect IT Community! Our US offices will be closed beginning on Thursday, November 24, 2022 in recognition of the holiday. Limited Support staff in the US will be on-call and available for critical Service(s) Down issues only. Normal Support operations in the US will resume on Monday, November 28th, 2022.

Windows OS Language

Onno de Vries
Onno de Vries Member, Kaseya Certified
edited January 24 in Solutions

Product Name: Windows OS Language

Description : This looks up the Locale ID in WMI and then matches it against Microsoft's official list of Locale Ids with their corresponding language. The result is displayed in a Custom Field as is part of the Audit Module in VSA.

Typically used in non-us countries where OS Language might not be English. Any command line command feedback is given in the OS Language used. For instance, when using Chkdsk to fight defragmentation, the analyses result is given in the OS language, when just using English language checks to see if defragmentation is required, defragmentation will actually never run.

Instructions :

  1. Download and unzip the file into a temporary folder
  2. Login to your Kserver
  3. Go to Audit Module > Machine Summary and create a custom field called "OS Language"
  4. Go to Agent Procedures Module > Schedule/Create, select any folder (Private or Shared) and the press "Manage Files" button just below the Machine Filter options.
  5. Select 'Shared Files' in the new windows that shows
  6. Upload the LocalIDs.txt file that you unzipped in step #1 to the root of 'Shared Files'
  7. Close this "Manage Files" window to return to the Agent Procedures Module > Schedule/Create function in VSA
  8. Again select a folder (Private or Shared) to import the Agent Procedure in
  9. Select "Import Folder/Procedure" button just below the Machine Filter options.
  10. Select the "Procedure Get Windows OS Language.xml" file that you unzipped in Step #1.
  11. Click "Save"
  12. Have a test run on a couple of machines to try it out, schedule if going forward in your Policies 

To make use of this value in your other produces, like in the example with CHKDSK, the simplest way is to call this same agent procedure from the that CHKDSK procedure (or any other), and then call out the language using variable "#global:OSlanguage#'.

Comments

  • pjose
    pjose BrisbaneMember, IT Pro CHOCOLATE MILK

    This procedure does not work on the cloud version