Now I don’t do Sametime very much, its a area of horror I leave to people like Gab Davis, but this this was a fix that Gab found that I felt needing sharing

So it was a standard install on a client site on clean windows 2012 servers built by the client. with only basic services to be provided, simples eh?

nope…

instead we get this bundle of fun when trying to login on the web client for meetings

CommunityServ W com.ibm.collaboration.realtime.stproxy.services.community.CommunityService doService, SID:
12345678-AAAA-1234-ZZZZ-123456789555 CLFRX0030E: Login is not completed in 10 seconds. User XXXX XXXX will be logged out.
that login is not completed in 10 secs

After a good deal of grumbling and checking of settings it was decided to make sure IP6 was not used, I checked in the windows setting and it did not look as if it was enabled, Gab however point out that that would not be enough and sent me to this

https://support.microsoft.com/en-us/kb/929852

which is a little download to completely disable the feature, I ran it on a the various servers and voilà , suddenly everything works.

Just a tip in case it is needed……

I do pardot implementations amongst my other salesforce stuff, which always seem to involve a number of hacks to bend the Salesforce and Pardot functions to meet the existing behaviours that the client wants.

Now pardot has “completion actions” these are very useful jobs that are performed when a form is submitted, but limited in that they are not conditional, i.e. you cant say “if field X = Y then do W action else do Z action”, Pardot them selves show you a way round this using form field based completion actions.

This is a nice trick and can be used as a base for more complex things, namely running MULTIPLE completion actions, an example of which is shown below

<script type="text/javascript">
var email = encodeURIComponent('%%email{js}%%')
switch('%%CheckBox_1{js}%%')
{
case 'true': document.write('<iframe src="FORM_HANDLER_1_URL?email=' + email + '" height="1px" width="1px" ></iframe>');
break;
case '': document.write('<iframe src="FORM_HANDLER_2_URL?email=' + email + '" height="1px" width="1px" ></iframe>');
break;
};
switch('%%CheckBox_2{js}%%')
{
case 'true': document.write('<iframe src="FORM_HANDLER_3_URL?email=' + email + '" height="1px" width="1px" ></iframe>');
break;
case '': document.write('<iframe src="FORM_HANDLER_4_URL?email=' + email + '" height="1px" width="1px" ></iframe>');
break;
};
</script>

This means that you can run a lot of conditional rules based on the fields in the one form, the most common use I make of this is of a [Custom Email Preference Center Pages](http://help.pardot.com/customer/portal/articles/2125807-creating-custom-email-preference-center-pages) but one where a user can fill in more details than just their email address.
Oh one final note, you will see on the pardot instructions they close their iframes with a “/>” this wont work if you have multiple iframes on one page you need to close of iframes properly with “</iframe>”

Silly little post and more an aide-memoire than anything, but recently I have been doing a bit of work on a VERY secure site, one that does not permit bluetooth of any form even for such things as mice, resulting in a quick pound down to PC World, after a squint down the rows of mice I realised that wired is really dead and there was none that I would not feel ashamed to use, dead that is apart from serious gaming, in that area there was a very pleasant and quality mouse in the form of the Razer deathadder chroma.

All was fine till I plugged the darn thing in and discovered its ultra sensitivity meant it was nearly uncontrollable and the normal UI sensitivity settings went nowhere near far enough down to make it usable, so back to command line we go.

So first lets get a list of the input devices on the system with:

xinput list

Now lets check this list for the first instance of “Razer Razer DeathAdder Chroma” in the pointers list and get its id number (in this case 12), then change its sensitivity as below, I find a value of 3 takes it down to the same level as a normal mouse

xinput set-prop 12 "Device Accel Constant Deceleration" 3

There we go, a usable mouse.