MDX ShareFile 4.4 on Android cannot access the file browser.

Asharefilenother quick hit little bug for you.

Despite enabling Gallery access on the MDX App settings, for some reason on Android access to the upload from device page was being blocked when “document Exchange (open in)” was set to restricted.

If you lifted this restriction, all worked well. but Nobody wants that.

Anywho, with much pain and wandering around the Google Android Developer documentation, the following exception list allows you to restrict the App successfully while still allowing access to local files for upload.

{action=android.speech.tts.engine.CHECK_TTS_DATA}{action=android.app.action.SET_NEW_PASSWORD}{action=android.app.action.START_ENCRYPTION}{action=android.intent.action.GET_CONTENT}{action=android.intent.action.PICK}{action=android.intent.action.CHOOSER}{action=android.intent.action.OPEN_DOCUMENT}{action=android.intent.action.RINGTONE_PICKER}{action=android.intent.action.DIAL}{action=android.intent.action.MAIN}{action=android.media.action.IMAGE_CAPTURE}{action=android.provider.MediaStore.RECORD_SOUND}{action=android.media.action.VIDEO_CAPTURE}[action=android.intent.category.APP_GALLERY}

While using the ShareFile mobile applications, NTFS last modified date is updated each time a user accesses an NTFS connector

Here’ssharefile a weird little bug I caught in the wild while deploying XenMobile Enterprise. While browsing NTFS shares, published as connectors in the ShareFile Mobile clients, or the ShareFile desktop application for windows, all the directories in the directory you are currently browsing will have their “Last Modified” timestamp updated as below: sharefilebug Continue reading

XM

Cannot Log into XenMobile 10.3 Appliance after initial deployment.

XM<FYI, this was resolved in version 10.3.5>

Here’s a horrendous bug I just came across in the field today while deploying a XenMobile 10.3 Proof of Concept with a customer.

Post the initial deployment of the OVF on vSphere, i ran the usual CLI wizard to IP the appliance and create the database. After restart the web ‘Administrator’ user account just would not accept the password i provided during the wizard.

On closer inspection of the database by comparing with my own lab (never POC without a LAB!) , the ‘administrator’ username was completely missing from the database under ‘dbo.security_principal’…dbo.security_principal

what the ‘crappity crap’ went wrong I don’t know. but I reproduced it 4 times in numerous tests.

 

I managed to find a workaround involving specifying a different username. I.E. delete your deployment and database and when the wizard prompts for the ‘administrator’ name with default value, specify something different.

In my case I specified ‘zdmadmin’ and this worked correctly allowing me to get the hell out in time for a Friday beverage.

working

I hope this helps anyone else facing this issue!

 

Threadlocker 128x128

ThreadLocker 2.1 is available.

Threadlocker 128x128Shortly after it’s initial launch and great reception! I’m proud to announce the general availability of ThreadLocker 2.1.
This is a minor update but does include some new key features and functionality.

What’s new in 2.1:

ThreadLocker Priority:

There is now the ability to assign a custom priority to a process when it has been ThreadLocked, allowing you to not only control which cores a ThreadLocked process runs on but also the priority it runs at.

Included Processes Only:

This new option allows you to specify which processes you want to apply ThreadLocking to. Previously the Enterprise Edition could apply ThreadLocking to any running process on the system but now you can now control this on a per process basis.

Logging:

Certain ‘error’ events were being incorrectly logged to the Windows Event log, these have now been removed.

Availability

ThreadLocker 2.1 is available from today and can be found at:

http://www.thinscaletechnology.com/threadlocker.