KiXtart is a free-format scripting language written by Ruud van Velsen of Microsoft Netherlands. Many companies have used KiXtart as there login script processor although as time goes by people are switching to purely GPO’s or VB script. I personally still use it for my login scripts, it’s easy to understand and simply to deply. Just copy a exe to each machine through GPO and edit your users profiles to run the exe and script at login. In fact I was using it so much that wrote a KiXtart script editor with color highlighting of the keywords, a insert menu with all the commands, and some wizards for commonly used things.
The last update brought the software to v4.12 and will most likely be the last version released. Download it here:
Kixtarter v4.12 – KiXtart Script Editor Installer
EDIT: I’m still using this program so I made some optimizations to it and brought it up to targeting the .Net Framework 4.7 as the old one was still running on 3.5. This is now considered v4.13 and is the newest version:
Kixtarter v4.13 – KiXtart Script Editor Installer
A couple years ago I helps setup a SSL certificate for a AX Supervisor, a product that is used as a web interface front end to a automation product called a JACE, usually. The software was installed on a Microsoft Server 2008 R2 system and was serving up the information through a B2B VPN and the other company, even though the traffic was “internal”, requested a SSL. No biggie I thought, I’ve installed SSLs many times. So I installed the certificate on the server but the AX software didn’t see it. I went into the software’s platform and into the Certificate Management section to import a certificate. It only accepted pem files so I converted my Windows certificate over but it didn’t like that either. So I started reading the only guide I could find on the subject titled “NiagaraAX SSL Connectivity Guide”. Ironically it has page after page of how a SSL works and how to generate a self signed certificate then export it out and import it onto all of the computers accessing the system but nothing on importing a existing certificate as a pem file. Long story short the way a AX Supervisor wants the pem is to have it include the key, the certificate, the intermediate certificate, and the root certificate in that order all in one file. So for the 9 people in the universe that will actually need to do this sometime in their life and can’t figure it out here is what I had to do.
First I downloaded the Windows 32 bit binaries of OpenSSL ( from https://slproweb.com/products/Win32OpenSSL.html ) and installed them. I copied my pfx file that I exported out of my server (with key/password) and put it in the same directory as openssl.exe (the bin folder usually). I opened up a command prompt, navigated to the bin directory, and ran the first command to get my private key:
openssl pkcs12 -in CertExport.pfx -nocerts -nodes -out key.pem
Then another command to export out my certificate:
openssl pkcs12 -in CertExport.pfx -nokeys -out cert.pem
I now needed my intermediate and root certificates which since I was using GoDaddy were downloadable from their site ( https://certs.godaddy.com/repository ). I imagine its the same for any other certificate authority. I created a new text file and first took the contents of the key.pem file (minus the headers keeping the begin and end tags) then followed it with the contents of my cert.pem file (again no headers) then, and this is important, followed those with the intermediate then the root. I saved this as MYFullCert.pem and that imported right in without a issue. I was then able to use that for both the Platform SSL certificate and for the Stations WebService certificate. Rebooted the server and everything looked good.
Note: This applies to a AX 3.7. I have found the certificate will not import into 3.8 using the same instructions. What does work however is importing it into 3.7 then exporting it out. The exported file appears to have a extra line added which does work on 3.8.
So something I was recently tasked with was finding a “could” service for our technicians to easily share files with each other. We also have multiple people using things like DropBox, Google Drive, Microsoft’s OneDrive, etc with our companies data and no way to really secure it which is a problem. So I started looking into business version of these services and what I found was they were ridiculously expensive.
And that’s kinda where it stopped. It just didn’t make sense for a company that already has it’s own server infrastructure. To that end I decided to do it in house and started researching alternatives of which I found two main ones, ownCloud and Pydio. I did some beta tests with both and in the end found that Pydios overall interface was the winner: Fast, “pretty”, and pretty intuitive. The problem was getting it to run on Server 2012 R2 / IIS 8.5 was not easy and none of the guides online had everything needed to get it to function. So long story short after a couple days of playing I wrote my own which is now posted on the Pydio website:
Hopefully if someone else is looking for a DIY cloud storage system it will help them out.
Update: I have been asked by multiple people to upload my web.config files for the root and public directories as the copy and paste from the tutorial aren’t working real good. Here they are: WebConfigRoot WebConfigPublic
Also the guide as a PDF: Installing Pydio on Windows Server 2012 R2