Page 2 of 4

How to modify the Configuration Manager Client Cache Size

31-Oct-2016 / David / 0 Comments

Intro

When using SCCM 2012, the default cache size for the ConfigMgr client is 5 GB (5120 MB). This setting could cause problems when you have large applications to deploy during an OSD. These deployments could fail simply because the size of the SCCM Client Cache is not big enough to cache all of the application installation files.
Note that Software updates also use the client cache, but software updates are not restricted by the configured cache size and will always attempt to download to the cache folder. The cache folder is usually C:\Windows\ccmcache.

How to set the SCCM client cache size

Changing the cache size can be done using the wmic command. You also need to restart the CCMEXEC service on the client computer to have it use the new cache size. The following script shows you how:

@echo off
cls
REM -- in this example, set cache size to 12000 MB
wmic /namespace:\\ROOT\CCM\SoftMgmtAgent path cacheconfig set size=12000

REM -- then restart SCCM client service
sc.exe stop ccmexec
timeout /T 4
sc.exe start ccmexec

Save it as .bat file, create a package for this script, include it in your OSD task sequence, or deploy it to your clients collection.

Enjoy 🙂

Upgrade MariaDB 5.5.x to 10.0.x on Slackware 14.1 x64

15-May-2016 / David / 0 Comments

Update for Slackware x64: latest version of MariaDB 10.0. This package was build on a Slackware 14.1 system. To build this package succesfully on a 14.1 system, you also need to install the jemalloc package.

Downloads:

How to upgrade from MariaDB 5.5.x to MariaDB 10.0.x

1. Start by downloading the 2 packages above.

2. Transfer these packages to the server you want to upgrade.

3. First install the jemalloc package:

installpkg jemalloc-3.6.0-x86_64-1.txz

4. Stop the running mysqld service:

/etc/rc.d/rc.mysqld stop

5. backup ALL your databases (make a copy of the entire /var/lib/mysql directory).

cp -a /var/lib/mysql/ /var/lib/mysql-BACKUP

6. Uninstall the MariaDB 5.5.x package (use removepkg or pkgtool).

7. Install the new MariaDB 10.0.25 package:

installpkg mariadb-10.0.25-x86_64-1.txz

8. Make sure /etc/rc.d/rc.mysqld is updated (overwrite the old rc.mysqld with rc.mysqld.new).

9. Start the mysqld service:

/etc/rc.d/rc.mysqld start

10. Check if mysqld is running now:

ps aux | grep mysql

11. Run mysql_secure_installation. Maybe this is not really necessary, but it doesn’t hurt to start clean. While you’re at it, you can set a new mysql root password here as well.

12. Run mysql_upgrade (MUST DO):

mysql_upgrade -u root -p

10. Restart the mysql service again (just to be sure).

/etc/rc.d/rc.mysqld restart

11. Now go check your DB’s and applications.

Enjoy 🙂

EDIT 27-Oct-2019: The above procedure is also valid when upgrading from say MariaDB 10.0 to 10.2 or later versions.

CalDAV sync for MS Outlook

04-Sep-2015 / David / 0 Comments

Good news for people who are looking to sync their CalDAV calendars (like the one from OwnCloud server) with MS Outlook: there is finally an opensource plugin that actually works 🙂

I have tested this with MS Outlook 2010 and OwnCloud server 8.1.1, and so far it just works, giving you full 2-way sync.

More info here:

Download:

OutlookCalDavSynchronizer-1.0.4

Update (08-Sep-2015), version 1.1.0 is already out:

OutlookCalDavSynchronizer-1.1.0

And this is wat ik looks like (account settings):

Enjoy 🙂

Fix the Gallery 2.3.x “This GD version is too old” error

13-Jul-2015 / David / 0 Comments

For any one out there running Gallery 2.3.x (a web based photo album), this posting gives you a fix for the problem with he GD plugin.

The problem

Gallery 2.x is a web based photo album, written in PHP. As such, you can create albums and upload photos into these albums. Gallery then takes care of creating thumbnails and intermediate sized versions of your photos. For this purpose, Gallery needs some graphics toolkit, like GD or NetPBM.
GD is the most widely used toolkit, as it usually comes bundled with PHP. However, Gallery fails to properly detect the version of GD available on the system.

The GD config fails with this message:

GD Version: 2.1.0 (bundled) Required:2.0
Failed
This GD version is too old and is not supported by this module! Please upgrade your PHP installation to include the latest GD version.

It seems weird: the GD version bundled with PHP (2.1.0) meets and even exceeds the required version. Yet Gallery fails to properly detect this, and hence refuses to activate the GD plugin.

The solution

In your Gallery installation, make the following change on line 286 from …/modules/gd/classes/GdToolkitHelper.class:

Change this:

 if (preg_match('/^>?2\.0/', $gdVersion))

into this:

 if (preg_match('/^>?2\.[0-9]/', $gdVersion))

So, just change the .0 to .[0-9], and save the file. Afterwards, in Gallery, you can activate the GD plugin, and it should work.

How to set the Belgian azerty keyboard layout in Xorg

22-Feb-2015 / David / 0 Comments

These days, on modern Linux systems, Xorg pretty much configures itself. Gone are the days of carefully assembling a working xorg.conf file. Xorg even seems to ignore any xorg.conf available. That’s nice if it all works great, but what if Xorg decides to ignore your non-US keyboard layout ?

Around here (Belgium), most of us use keyboards with Azerty layout. In most GUI environments (KDE, XFCE, …) , you can select the Belgian keyboard layout, and that’s it. It appears to work just fine. But does it always work as expected ?
Well, no, it doesn’t: some applications, like say xscreensaver, xlock or graphical login managers seem to ignore the keyboard layout as set by your GUI. This can lead you to the rather embarassing situation where you have trouble logging in, once xscreensaver has kicked in, because it appears to use the qwerty keyboard layout.

To get rid of this problem, you have to create the following configuration file:
/etc/X11/xorg.conf.d/10-keyboard.conf .

The content looks like this:

    Section "InputClass"
       Identifier "system-keyboard"
       MatchIsKeyboard "on"
       Option "XkbLayout" "be"
       Option "XkbModel" "pc104"
    EndSection

Restart Xorg, and your Azerty keyboard should now always work correctly, in every X application.

Server goes virtual

27-Sep-2014 / David / 0 Comments

After relocating to a new appartment, I found myself somewhat cramped for space. As I already had a Proxmox server running, I decided to virtualize the webserver (which was still a physical server). This would be a nice Proxmox exercise, would save me some space under the desk, and help me cut down on my electricity bill.

So, this website now resides on a virtual machine, more precisely, a Linux KVM machine, running on Proxmox VE 3.3 server. This server has following specs:

Part	Proxmox server
CPU	Intel Core2 Duo E8400
CPU speed	3.00 Ghz
Memory	8.0 GB DDR2
Chipset	Intel Q35
Storage	800 GB

You can find out more about Proxmox VE here.

FreeUnix.davidleemans.be