Evernote Tags Tutorial

Evernote has become an important part of my filing process. However one thing I’ve been trying to get better at is tagging my Evernote notes for even easier locating. 

A recent vlog from Enrico Nahler contains some really useful tips on how to make the best of Evernote’s tags.

Have you found a unique way to keep track of your Evernote notes? Let me know in the comments below.

Read More

Resolve incorrect username on shared file lock

Locked FileRunning a 2003 file server, with files accessed by many across multiple geographical locations can come with its own challenges. One such challenge is that of file locking, especially on documents which don’t yet support true collaborative working. Such as Office 2007 documents.

Last week one of our end users suffered the same issue, documents being left locked open by a user. However, on this occasion the issue was accentuated by the server reporting the incorrect user name of the user with the read/write access. This has been a known issue for some files on our sites for sometime, however Friday I finally managed to get to the bottom of it. (more…)

Read More

Fix: Constant credential prompts in Outlook ’07 using 365

20130510-124333.jpg

Today I have mostly been fighting with Microsoft Office Outlook 2007 and our Office 365 setup, as we are still in the early stages of deployment we have not yet implemented our ADFS servers. Which means we have are experiencing some pretty frustrating issues with Office and authentication.

One machine in particular decided to really test my patience and blankly refused to authenticate, presenting the user with a constant reoccurrence of the “Welcome back to Outlook.Office365” login box.

As it happened the machine had seemed to avoid the installation of several service packs, including Office 2007 Service Pack 3, and also what turned out to be some pretty important KB hot fixes. Leaving me scratching my head for what seemed like a lifetime… That was until today! When I finally managed to find the relevant KB hot fixes and install them manually..

OFFICE VERSION NOTES
Latest version of Office System requirements for Office 2013 and Office 365 ProPlus
Office 2010 with Service Pack 1 Automatic updates:

  • Customers who sign up for Office 365 after February 27, 2013, must apply all automatic updates that were released before December 2012.
  • Customers who signed up for Office 365 before February 27, 2013, must complete the following:
    • By July 1, 2013, apply KB2553248.
    • By April 8, 2014, apply all automatic updates for Office 2010 that were released prior to December 2012.
Office 2007 with Service Pack 3 Automatic updates:

  • Customers who sign up for Office 365 after February 27, 2013, must apply all automatic updates that were released before December 2012.
  • Customers who signed up for Office 365 before February 27, 2013, must complete the following:
    • By October 1, 2013, apply KB2596598.
    • By April 8, 2014, apply all automatic updates for Office 2010 that were released before December 2012.
Office 2003 only through POP and IMAP For more information, see Office 365 will now support POP and IMAP connections to Outlook 2003.
Office for Mac 2011 with Service Pack 3 Mac OS X 10.6 or later is required.
Office 2008 for Mac 12.2.9 Support ends April 9, 2013.

The journey to 365 has been a long and winding one… This particular highlights the importance of ensuring all machines connecting to 365 are bang up to date with Windows and Office updates and service packs… Lesson learnt.

Read More

FIX: Check Point Endpoint Security unable to connect


UPDATE: it would appear this bug has since been resolved in the E80 release of the CheckPoint client.

Since my recent upgrade to OS X Mountain Lion I’ve been suffering a very frustrating issue with Checkpoint’s endpoint security client. For no reason at all it would frequently refuse to connect. Stating an error: “Connectivity with the Check Point Endpoint Security service is lost”
Despite trying countless things with the client I found the only fix each time was to reinstall the client.

That was until now at least, after further investigation it looks like the issue only occurs when the Trac.config file had been zeroed. Now, I’m still trying to figure out what’s happening to the file. But I found in the meantime if you kill the checkpoint client then perform the following in terminal:

$ cd “/Library/Application Support/Checkpoint/Endpoint Connect”
$ sudo cp Trac.config.bak Trac.config

Then client the starts working as expected. Alternatively you can download a compiled AppleScript from here to do just that!
NB:You will be prompted for your admin credentials when either executing the command, or the script.

If you’ve found an alternative solution, please let me know in the comments below.

Read More