RDP session for keepass

This is very nice way to add RDP sessions to keepass


Parameters ignored when passed to Crystal Reports .net

This is a crazy, crazy annoying bug. Basically, when the Crystal Windows Form Viewer is added, the auto-generated code adds two lines that will overwrite the selection formula!!!

Answer came from


To resolve the issue, follow these steps:

Expand Form1.vb|cs to show Form1.Designer.vb|cs. (form1 denotes the form that contains your viewer)

Double-click on Form1.Designer.vb|cs to show its code.

In the InitializeComponent method, you will find code where the CrystalReportViewer1 properties are set.

Comment out or delete the following two lines:

me.crystalReportViewer.SelectionFormula = ""

me.crystalReportViewer.ViewTimeSelectionFormula = ""



#Ravello #VEEAM and the chaos monkeys Part 2

So now I got a couple of ESX servers, next up, how to get a working vcenter running on them.

Hmm, looks like if I install vSphere Client on my desktop and open up all the ports I should be able to connect to one of the ESXi machines and then import in an image of a vcenter server… Wish me luck!

Ok, using ports of ‘ALL’ I can certainly reach my ESXi server 🙂


I then went to Deploy OVF template, and choose the downloaded OVF file from vmware site.

OK… scratch that. I think an easier method will be to just create a vcenter as a standalone VM, I will tackle the nested vcenter another day.

I followed the instructions here for the vcenter install.

One tip, after configging the port forwarding, you will need to use https://yourVcenterIP:5480 in order to access the web console.

I was amused at the steps to suppress the warning message about compliance 🙂

And with that I have a working vcenter! (I added the hosts to the vcenter)


Next post, some Veeam, and maybe some monkeys

OSSEC-VM 2.8.1 install on ESX5.1i Failed

— I actually managed to cause a PSOD, tread carefully

Unzip the OVA file

I got the error ” The OVF package requires unsupported hardware. Details: Line 522: Unsupported hardware family ‘virtualbox-2.2’. I did a search on the .ovf and removed


From this post

– uncompress the ova file (with an unzip-like utility)
– modify the ovf file to reflect what’s been said by Daimonji
– recalculate the checksum of the ovf file and enter it in the mf file (you can use the FCIV tool if you’re under Windows :
– Deploy this new OVF, ignoring any warning.

— Ok found even more explicit instructions here

  • Used 7zip to extract the .ova file from the .gz file.
  • Found this web site:
  • Downloaded the VMWare OVF Tool from VMWare
  • Installed the OVF Tool on my PC.
  • Ran the OVF Tool as command line:  ovftool.exe –lax <source.ova>  <destination.ovf> Do not forget the option –lax   There are TWO dashes in front of lax.
  • This converts the .ova file to multiple files that end in:   .ovf, .mf and –disk1.vmdk
  • Found this web site:
  • Open the .ovf file with an editor (notepad) and make the following changes:
  1. Change the line:  <vssd:VirtualSystemType>virtualbox-2.2</vssd:VirtualSystemType>
  2. To:  <vssd:VirtualSystemType>vmx-07</vssd:VirtualSystemType>
  3. Change the line:  <OperatingSystemSection ovf:id=”80“>
  4. To:  <OperatingSystemSection ovf:id=”101“>
  • Download Microsoft Checksum Verify utility : (Need to check SHA1)
  • Install the Microsoft Checksum Verify utility.
  • Run this command line:  fciv.exe -sha1 <filename.ovf>
  1. Replace <filename.ovf> above with the name of the .ovf file you edited in step 7.
  • Edit the .mf file.  Take the SHA1 value calculated above and replace the SHA1 value in the .mf file for the .ovf entry (line 1)
  • Use vSphere to deploy the OVF.   Select the .ovf file.
  • DONE

So the OVFtool makes you accept a license… quite annoying and it complains about the following system identifier ‘RedHat_64’ which it maps to ‘Other <32-bit>’ also didn’t like the ‘virtualbox-2.2’ with an unsupported hardware family.

grrr…. for what ever reason I only got two files out of the .ova, oh well I just recreated a 64bit centos virtual machine and added the ossec-vm-2.8.1-disk1.vmdk

That was…. easy.

And then on boot it PSODed the whole kit and kaboodle… hmm this virtual machine is quite the pain

automate juniper switch backup

From KB11194

JUNOS Command Line interface allows the user to export the configuration file into an FTP server and to import it back to the switch. The information below describes the steps to backup and restore JUNOS configuration file on FTP server.

Backup configuration file on FTP.

The following configuration sample shows how to backup the JUNOS configuration file on FTP server.

On every commit applied on CLI, the EX switch will transfer a copy of the configuration file to an ASCII file on FTP server. The filename created on the FTP server contains hostname, date and time signature.

system {

archival {

configuration {


archive-sites {






BizLink install part 3

Now that we got some AS2 action going on I needed to figure out how to handle some incoming purchase orders. With a little bit of poking around I was able to get it to go.

The first thing I needed to configure was the ‘parties’

I wanted to emulate an invoice coming in so I took the external partner and set their identifiers to match a real partner but it was really pointing my other AS2 box. Then for the server owner I set it to one of our real id’s. These Identities are not AS2 identities but are ISA (EDI x12) identities. So for example the EDI might be like

ISA*00*          *00*          *ZZ*666791NF       *08*999485US00

you would set the server owner to ZZ 666….  and the external to 08 999…

on this screen



So now you have parties setup, but now we need to instruct BizLink what to do with the files when it gets them!

The simplest thing to do is under transports, set a file copy (upload) on your server owner, set the file path and the format of how you want the file named and you will be good to go.


That will work, but what if you want say all 810’s from a certain partner to go to a certain directory? In this case create another File Copy (Upload) rename it to say Export Walmart 810 and then set its export folder to a 810 walmart specific one. That’s all nice and dandy but what actually tells it to use that particular export? The processing rules of course!

processing rulesGo ahead and click add, to add a new processing rule. We want a Recipient rule (for when our server is the recipient)

First give it a name.


Then you get to set the conditions they can either be AND or they can be OR conditions. We want an AND so both conditions evaluate as true.


We set the Sender Qualifier + Id to match our sender ID (in the ISA) and the we set the Transaction_IdCode to = 810.

Ok, now we need to tell it an action to do when the conditions are met.

Set that underneath in the actions dialogue


The first action will send back a 997 if requested and the second is for the routing. If we looking into the routing rule it is simple enough, give it a name, and then select a transport.


There you have it, when the doc matches it will get exported to the correct folder. Next we will mess with some scripts, until next time.

#OpenSim #OpenSimulator with Dispatcher

I recently started messing with OpenSim. Such a fascinating piece of software! My kids have gotten quite the kick as I have been building virtual worlds around them.

Next on my agenda was the ability to move\change\etc… objects externally somehow. That is where Dispatcher comes in.

So, I first needed to get dispatcher up and running.

You need the ‘master’ version from (Just download Zip)

Unzip it to say c:\Opensim-master

No, get a copy of Dispatcher from

Next, copy the two modules (folders named dispathcer and rcontrol) (Inside dispatcher-master\modules)



Install yourself a copy of Visual C# Express 2010

Run the c:\Opensim-master\runprebuild.bat

Double Click the c:\Opensim-master\OpenSim.sln

DispatcherModule should be at the top of your Solution Explorer

Build it.

If you are lucky your build will succeed 🙂

You should now have a Dispatcher.dll inside your C:\opensim-master\bin directory

You will need to do some configing before anything will work.

I just used the defaults in the Dispatcher.ini

You also need an OpenSim.ini (I used the config-include/Standalone.ini) and setup the


(I got my config from the binary package from

To check that it is there,

run dispatcher stats (All lower case)