As we are using an open-source variant & no m$ domain controller this was not an option. The current set-up already forced windows clients to run a logon script. But untill now i never used that to maintain/administer systems. After looking around (tnx google ), i bumped onto an “open-source” solution that goes by the name of WPKG.

WPKG is an automated software deployment, upgrade and removal program for Windows.

It can be used to push/pull software packages, such as Service Packs, hotfixes, or program installations from a central server (for example, Samba or Active Directory) to a number of workstations.

It can run as a service to install software in the background, without user interaction.
It can install MSI, InstallShield, PackagefortheWeb etc. packages, and all other packages using repackaging or some batch scripting.

Source WPKG website.

Apparently this piece of (great) sofware, does not require a server side installation. The only requirements are a shared network resource & the installation of the WPKG client service (on the client machines). During installation you need to enter the location of 4 different scripts (3 configuration variables & engine .js script). As there was an existing netlogon samba share, i placed the all files in that share & pointed the installer to those files. After that you’ll need to set-up some user(s) & permission(s). I would advise to create a new samba user to access those scripts, this way you don’t need to update the cached password each X days (if samba password changes). I added that user as local administrator on the 4 Client’s & made sure the WPKG service was up & running.

Consider this post part1, i’ll post how i succeeded installing software on the clients the same hour (i am tired now).

Because we now had 3U’s space, we decided to look for a larger spot, so we would have more options afterwards. I convinced my cousin’s company to come along, and we decided to rent a 1/2 rack (colocation) in Amsterdam. At that moment we were still hosting gameservers, so we regulary did server updates (new hardware etc)…Now if you know that going to Amsterdam, without traffic, takes about 3hrs (and 3 hours back) by car, you can see that this is a terrible situation, and especially when your hardware malfunctions once in a while…

So at the end of my contract, i decided to move to Belgium with my servers. The prices of colocation in the Netherlands were booming because of energy pricing (that’s what they told me), and the service wasn’t all that either….

Because my network administrator has a small colocation company in Antwerp, Belgium. I decided to give it a go. Important detail is that i don’t profile myself as a webhosting company but i offer webhosting solutions to my webdevelopment clients. This way i do not have to keep 1000+ users in account, and i can guarentee maximum uptime to my clients (i know exactly which modules, dependancies, configuration these clients need).

Now as time is going by, my company has some decent clients that require maximum uptime. Because the location in Antwerp is fully dependant of realroot (a major player on the belgian colo market) we’ve had a few problems. Being dependant of only one company is a major flaw in any case, so i started looking for alternative solutions…And i did, a Brussels based colocation company, this company offers everything i need (multiple power feeds, independant network, own RIPE account), now let’s hope we could stay here for a while…