Skip to main content

how to use dropbox to synchronize windows 7 sticky notes

you may remember awhile back, I wrote up some steps on how to use windows live mesh to achieve sticky notes synchronization. live mesh, sync, and now mesh again, was a great product to use for this purpose because you could point to the folder and tell it to sync it. unfortunately, I didn't find it very reliable and by the comments I read, neither did a lot of my readers.

this morning, I got quite frustrated by a couple of things going on. first of all, no sync! second, digsby! sticky notes and digsby are two things I've come to rely on. there's some talk about a protocol change (or using old protocols or something like that) I read that pointed to digsby's msn having connection problems while using windows live mesh. while live mesh was running, msn would drop off. according to their blog, it's a known issue and will be revised in a future release.

anyway, so here I am. I decided to get rid of mesh in favor of something I've been using awhile and have come to love: dropbox. the challenge with dropbox was that I had to find a way to synchronize the content (yeah that's easy I know) without having the content only in the dropbox folder.

the first thing I thought of doing was writing a script to copy the dropbox content on sync detection. this seemed like OVERKILL when I found someone else's brilliant solution: ntfs junctions.


configuring dropbox and junctions

this is a rundown of the steps involved, which is pretty dang easy. so let's get started...

  • close your sticky notes application. make sure it's closed. if it's still running, you'll see the StikyNot.exe process running.
  • create a new directory called "sticky notes" somewhere in your dropbox folder. I just put mine in the root for ease.
  • navigate to the "sticky notes" directory on your computer, where you'll find a file called StickyNotes.snt. (the directory path is c:\users\<userid>\appdata\roaming\microsoft\sticky notes)
  • copy the StickyNotes.snt file to the dropbox folder you created.
  • now get rid of the original "sticky notes" directory.
  • from a cmd prompt, type the following to create your junction:
mklink /J "%APPDATA%\Microsoft\Sticky Notes" "<Full Dropbox Path>\Sticky Notes"

  • once you open up sticky notes again, it'll be pointing to the file in your dropbox folder courtesy of the junction you just created. :)

if you open the path to the original stick notes directory, you'll notice there's a shortcut icon on the folder to indicate it's a junction. if you open up the folder, you'll find yourself in your dropbox folder.


okay, now you're syncing sticky notes to dropbox... but what about another computer?  simple.  just run through the same steps above, except this time, don't worry about copying your stickynotes.snt file since it already exists in dropbox.



there's one caveat I should mention. the synchronization can't take place while sticky notes is running. you'll want to close your sticky notes application every now and then so that dropbox has a chance to sync your changes.

this applies to computers receiving the files from dropbox as well. as long as sticky notes is running, it won't be able to sync the contents.


  1. Cloud Sticky Notes is an app that looks and acts like Windows sticky notes but syncs on all of your desktops. Avoid the hassle by visiting

  2. This comment has been removed by the author.

  3. Thank you, works well! I don't need to close SN, after each change it is synchronized automatic. I use Google Drive.


Post a Comment

Popular posts from this blog

how to retrieve your ip address with powershell...

update: this is how it’s performed in powershell v3 as demonstrated here.(get-netadapter | get-netipaddress | ? addressfamily -eq'IPv4').ipaddress update: this is by far the easiest.PS C:\temp> (gwmi Win32_NetworkAdapterConfiguration | ? { $_.IPAddress -ne $null }).ipaddress
are you laughing yet?  i know you probably find this topic amusing.  it's really interesting though.  whenever you get over it, i'll do this in the standard cmd.exe interpreter and then in powershell to show you what kind of coolness powershell does.done?  okay, good.  this is an interpretation of a demo that bob wells did at our smug meeting.  hope you like it.i should tell you, it's not as simple as the title would lead you to believe.  i like doing that little slight-of-hand thing since it gives the impression that i'm painting a very easy target on my back for your criticism (though it's probably true in other ways)!  the idea is that we want to retrieve just the ip ad…

understanding the “ad op master is inconsistent” alert

i use the term “understanding” loosely.  this is by far no definitive guide on this particular alert, just a few things i have picked up in my attempt to understand it.let’s look at the context of the alert:The Domain Controller's Op Master is inconsitent. See additional alerts for details.
first of all, it gives very little information.  the only particularly useful detail is that it indicates which server is having the issue.  other than that, just a spelling error as there are no additional critical alerts to look at for details.this rule, as you know, comes from a sealed mp.  therefore, we can’t modify anything in it except the overrides.  the couple i’ve tinkered with are:interval (sec) log success event to begin with, interval (sec) is just set way too high.  the default is 60 seconds.  why on earth would anyone want to know that your op master consistency may be off, every minute?  actually, i could think of a few reasons, but really, it’s overkill.  the way the script works…

sccm: content hash fails to match

back in 2008, I wrote up a little thing about how distribution manager fails to send a package to a distribution point. even though a lot of what I wrote that for was the failure of packages to get delivered to child sites, the result was pretty much the same. when the client tries to run the advertisement with an old package, the result was a failure because of content mismatch.I went through an ordeal recently capturing these exact kinds of failures and corrected quite a number of problems with these packages. the resulting blog post is my effort to capture how these problems were resolved. if nothing else, it's a basic checklist of things you can use.DETECTIONstatus messagestake a look at your status messages. this has to be the easiest way to determine where these problems exist. unfortunately, it requires that a client is already experiencing problems. there are client logs you can examine as well such as cas, but I wasn't even sure I was going to have enough material to …