This equation takes a phone number with area code and strips the 7 numbers after the area code, leaving only the area code:

=LEFT(TEXT(E1,"0"),LEN(TEXT(E1,"0"))-7)

You can change the variables to clip and prune whatever info off either side of a number to get what you need.

"To restore your Sticky Notes backup, first you must delete all of the existing Sticky Notes on your desktop. Then, replace the current StickyNotes.snt file with your backup file by copying and pasting it in the %AppData%\Microsoft\Sticky Notes\ folder."

Source & more details here: http://carlcheo.com/how-to-recover-accidentally-deleted-sticky-notes

Turns out that .camrec files created by Camtasia are actually zip files that contain the .avi that was recorded. You can use a program like 7-Zip to extract the .avi file

And if you want to save some space, you can always compress that .avi file with WinRar. It looks like the .camrec zip file is not compressed - however I've been able to take a 5GB+ avi file from Camtasia and compress it down to under 400MB.

From my archive notes: 10/25/2012

While trying to integrate an Avaya IP Office into Exchange 2007 I found that there was no "Unified Messaging Server Role" service installed. So I went to the control panel to change the install for Exchange Server 2007 to enable that Role. Two address paths were defined when adding this service.

First for the Exchange Server installation files:
C:\Program Files\Windows Small Business Server\Bin\CMPNENTS\EXCHSRV80

Second for the Exchange Server installation path:
C:\Program Files\Microsoft\Exchange Server

Our server did not have any folder located in the default installation files path and I didn't have my Exchange server install CD handy. Looking at several guides online, users have complained that using the original files from their install CD caused issues. So I went online and found the latest service pack that I had installed and decided to extract the files from there. Turns out I had Exchange Server 2007 Service Pack 1 (x64) installed.

I was able to download the "Exchange Server 2007 Service Pack 2" files from here:
http://www.microsoft.com/en-us/download/details.aspx?id=4479

The exe file was about 884 MB. After extracting the file using WinRAR, the file size was about 1.22 GB (now I can see why the files were not on my server). At one point or another, a previous tech had cleared out these files to save space on the server. From my workstation where I extracted the files, I opened the shortcut to my server and copied the files to the C:\Program Files\Windows Small Business Server\Bin\CMPNENTS\ under a new folder named "EXCHSRV80"

I decided on waiting a couple of days for the weekend as I didn't want to take the server down for updates in the middle of the workweek...

Notes and Resources:
http://social.technet.microsoft.com/Forums/en-US/exchangesvrclients/thread/64a9409a-e57a-4431-932e-b1426a17f66e

Found this guide to stop the EAccessviolation error associated with Windows 2003 server when running Avaya's CallStatus program. A user named cascadia on the http://www.pbxtech.info Forum had this to say and it worked for me:

====================

There is a very easy fix to this. I was advised to update the server fully with MS patches. Did that, but no help. So I did the following on a hunch and it worked!

My Computer > Properties
Advanced Tab
Performance > Settings
Data Execution Prevention Tab
This is turned on by default with a blank exception list.
Click Add...
Locate your copy of callstatus.exe
Mine was in C:\Program Files\Avaya\IP Office\CallStatus\callstatus.exe
Click Apply > OK > OK

And now you should be able to execute the Call Status monitor and run it like you used to.

Source: http://www.pbxtech.info/showthread.php/3114-EAccessviolation-error

Souce & Resources:
http://msmvps.com/blogs/bradley/archive/2011/03/11/exchange-server-2007-sp3-does-not-update-the-exchange-server-active-directory-schema.aspx

After you install Exchange 2007 service pack 3, and or rollup #1 or rollup #2 and you attempt to create a new receive connector, you receive the following error:

Summary: 1 item(s). 0 succeeded, 1 failed.

Elapsed time: 00:00:00

test

Failed

Error:

Active Directory operation failed on SBS01.ks.local. This error is not retriable. Additional information: The parameter is incorrect.

Active directory response: 00000057: LdapErr: DSID-0C090C26, comment: Error in attribute conversion operation, data 0, v1772

The requested attribute does not exist.

Exchange Management Shell command attempted:

new-ReceiveConnector -Name ‘test’ -Usage ‘Custom’ -Bindings ’0.0.0.0:25′ -Fqdn ‘test.test.com’ -RemoteIPRanges ’0.0.0.0-255.255.255.255′ -Server ‘SBS01′

Elapsed Time: 00:00:00

This is caused by service pack #3 not extending the schema properly, or not at all. To resolve this issue, download service pack 3 again at http://www.microsoft.com/downloads/en/details.aspx?FamilyID=1687160b-634a-43cb-a65a-f355cff0afa6&displaylang=en and then extract it.

Open a command prompt and go to the extracted folder. Now execute the following command:

Setup.com /PrepareSchema

Now attempt to create your receive connector, and it will work fine. Please note, you do NOT have to remove rollup #1 or rollup #2 to fix this issue. I found one post that mentioned waiting for rollup #2 to come out to fix the issue http://msmvps.com/blogs/bradley/archive/2010/10/12/can-t-do-a-new-receive-connector-after-exchange-2007-sp3-rollup-1.aspx , but the issue is not fixed in the rollup as it is a schema extension that was introduced in service pack #3. Upon further reading and investigation, on the Microsoft TechNet site, at http://technet.microsoft.com/en-us/library/ff607233(EXCHG.80).aspxit clearly states

“You must prepare Active Directory and each domain before you perform the first installation of Exchange 2007 SP3 in an organization. This process includes updating the Active Directory schema for Exchange 2007 SP3″

Guess no one read this part, including me!

Open Group Policy Management from the Administrative Tools.

Right click the ‘Default Domain Controllers Policy’ and choose ‘Edit’.

Choose Computer Configuration –> Policies -> Windows Settings –> Security Settings –> Local Policies –> User Rights Assignment and double right click in the right pane ‘Allow log on locally’.

Click ‘Add User or Group’.

Click Browse

Type in the box ‘besadmin’ and click ‘Check Names’.

Click ‘OK’.