Windows knowhow

Windows: Installing a language pack

Leave a comment

Hi,

if your Windows installation should support multiple langauges you can install some Windows language pack.

Language packs, formerly known as MUI, are installable on Windows 7 Enterprise and ultimate and Windows 8/8.1.

The Download locations for individual language packs are:
Windows 7
Windows 8

Or, if you have a MSDN account, download the Language Pack DVD with the whole compilation.

Install the language pack in batch mode with the following command line, for example the german one:

C:\>dism.exe /online /add-package /packagepath:D:\langpacks\de-de\lp.cab

Deployment Image Servicing and Management tool
Version: 6.1.7600.16385

Image Version: 6.1.7600.16385

Processing 1 of 1 - Adding package Microsoft-Windows-Client-Refresh-LanguagePack-Package~31bf38....

[==================         32.7%                          ]

reboot the system after installation.

Check for installed languages

C:\Windows\system32>dism /online /Get-intl

Reporting online international settings.

Default system UI language : en-US
System locale : de-DE
Default time zone : W. Europe Standard Time
Active keyboard(s) : 0407:00000407, 0409:00000409
Keyboard layered driver : PC/AT Enhanced Keyboard (101/102-Key)

Installed language(s): de-DE
Type : Fully localized language.
Installed language(s): en-US
Type : Fully localized language.

The operation completed successfully.

Now you change the UI from command line language by  intlcfg.exe, which is included in the Windows Automated Installation Kit (WAIK) or form the Regional Settings Control Panel intl.cpl.

 

To installing the language pack by GUI start:

lpksetup.exe

by selecting language lp.cab file.

Language Pack GUI
Language Pack GUI

Michael

Powershell, Windows knowhow, Windows Scripts

Windows: Powershell script to fix and repair WMI

6 Comments

Hi,

this script repairs and recreates the WMI Repository of a Windows. For example, this occurs sometimes if you clone a Windows machine with an installed SCCM/SMS Client. The typical error in this case is “Failed to open to WMI namespace ‘\\.\root\CCM\SoftwareUpdates\DeploymentAgent’ (8007045b)”

Lasts start. Start a Powershell console as Administrator. Stop all services. Sometimes other services depends on the WMI Service and does not accept a stop request. Therefore you cannot stop the WMI service. TrendMicro Office is such a service. You have to kill them by TaskManager.

# Stop WMI
# Only if SCCM/SMS Client is installed. Stop ccmexec.
Stop-Service -Force ccmexec -ErrorAction SilentlyContinue
Stop-Service -Force winmgmt

(Re)Register WMI binary components

[String[]]$aWMIBinaries=@("unsecapp.exe","wmiadap.exe","wmiapsrv.exe","wmiprvse.exe","scrcons.exe")
foreach ($sWMIPath in @(($ENV:SystemRoot+"\System32\wbem"),($ENV:SystemRoot+"\SysWOW64\wbem"))){
	if(Test-Path -Path $sWMIPath){
		push-Location $sWMIPath
		foreach($sBin in $aWMIBinaries){
			if(Test-Path -Path $sBin){
				$oCurrentBin=Get-Item -Path  $sBin
				Write-Host " Register $sBin"
				& $oCurrentBin.FullName /RegServer
			}
			else{
				# Warning only for System32
				if($sWMIPath -eq $ENV:SystemRoot+"\System32\wbem"){
					Write-Warning "File $sBin not found!"
				}
			}
		}
		Pop-Location
	}
}

Reregister WMI Managed Objects
Continue reading Windows: Powershell script to fix and repair WMI →

Powershell, Windows Scripts

Powershell: Check for Administrator rights

Leave a comment

Hi,

for a lot of powershell scripts Administrator permissions are necessary. In powershell, you can check if you are elevated by the following script code.
Insert the snippet at the top of your script. It checks the credentials and exits the script if the administrator permissions are missing.
Continue reading Powershell: Check for Administrator rights →

EIB/KNX, Linux, Raspberry PI

EIB/KNX: Upstart startup script for eibd

4 Comments

Hi,

as a follow up of the 2 previous posts(compiling eibd and SysV startup script) here is a sample Upstart script for the eibd daemon. Some Ubuntu based distributions uses the upstart start mechanism.

Login as root at your machine where eibd is installed and add a user under  which the eibd process should run.

useradd eibd -s /bin/false -U -M

Create the upstart conf file /etc/init/eibd.conf

#######################################################################
# eibd - startscript for the eibd daemon
description "eibd daemon Upstart script"
author "Michael Albert info@michlstechblog.info"

start on (filesystem or resume)
stop on (suspend or runlevel [!2345])
expect fork
normal exit 0

pre-start script
route add 224.0.23.12 dev eth0 2>&1 > /dev/null || true
end script

script
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
DAEMON=/usr/local/bin/eibd
DAEMON_OPTS="-d -D -T -R -S -i -u --eibaddr=1.1.128 ipt:192.168.56.1"
exec start-stop-daemon --start -c eibd --exec $DAEMON -- $DAEMON_OPTS
end script

post-stop script
route delete 224.0.23.12 2>&1 > /dev/null || true
end script
#######################################################################

Continue reading EIB/KNX: Upstart startup script for eibd →

EIB/KNX, Linux

KNX/EIB: System V startscript for eibd

13 Comments

Hi,

in a previous post I have descriped how to compile the eibd daemon for the Raspberry PI. Here is a sample debian startscript to start eibd at system boot.

Login as root at your EIBd box and  created a user under which the daemon should run.

useradd eibd -s /bin/false -U -M

Create the script eibd in /etc/init.d
Continue reading KNX/EIB: System V startscript for eibd →

My Knowledgebase for things about Linux, Windows, VMware, Electronic and so on…