Skip to main content

how to synchronize sticky notes in windows 7

do you like sticky notes?  when i heard about it, the concept seemed pretty hokey to me.  there are an assortment of ways to capture notes on the desktop.  notepad, remember the milk, outlook, etc.  i thought i’d give it a try to see if i could capture random, short-lived things that you tend to quickly forget.

imageas it turns out, it worked – and i’m hooked.  i don’t just like sticky notes, i love sticky notes.  i keep notes for new music i want to explore later, short errands to run, and topics i want to look further Live_Mesh[1]into later.

the one short coming is that i can’t sync the notes.  i’m sure there are an assortment of ways to making this magic happen, but i decided to use a service i’ve been using for awhile: live mesh.

now really, all you have to know is the path where sticky notes keeps all its information:

C:\Users\<your user profile name>\AppData\Roaming\Microsoft\Sticky Notes

 

there’s a file called stickynotes.snt.  when synchronized, this file carries all the information from your sticky notes “environment” so to speak.  here’s what you need to do:mesh1_web[1]

  1. install live mesh on all computers where sticky notes synchronization needs to take place.
  2. on the first computer, navigate to the path noted above and choose “add folder to live mesh”.
  3. on the other computers, open up the live mesh program.
  4. in the news feed, locate where you created the live mesh folder.
  5. when you click the folder, it’ll ask to set the synchronization on the computer.  locate the path noted above and insert that as the “location”.
Labels:

Comments

  1. Marius1/28/10, 6:57 AM

    Hi. The synchronization seems to be working a bit dodgy.
    1. when you synchronize the first note, and it's done synchronizing to the second computer, how do you open the note?
    2. since I didn't find a good way to solve this, i copied the information from the primary file and added it to the new note.
    Then Added new information, and the file does still not synchronize when the change to the file is done (new time stamp).

    So. If you have any tips on how to actually sync the file, open it and it automatically updates the information, it would be much appreciated :)

    ReplyDelete
  2. ::marcus1/28/10, 7:35 AM

    hey marius -

    i found that i have the best success when i close sticky notes on the machine that has the changes, and let mesh sync the changes. on the opposite computer, i can open or close/open sticky notes and get the updates. it is a little dodgy. i'm still trying to figure out exactly the nuance behind it, but it seems elusive as sometimes i expect it to update, and it doesn't.

    the other trick i found is to copy the stickynotes.snt directly to the live mesh online desktop folder. your connected clients should sync down the copy from the web.

    thanks for the comment!

    ReplyDelete
  3. andythorpe2/28/10, 4:40 PM

    I've been thinking there should be a way to do this. Thanks for the info. I'll give it a try.

    ReplyDelete
  4. ::marcus3/1/10, 8:43 AM

    i found some interesting behavior about live mesh -- which seems to make sense. unless you close the notes (which saves it), live mesh doesn't see an update. once closed and the update synchronized, you can manage it again... otherwise you do run the risk of an update from a different computer writing over the one you're using.

    ReplyDelete

Post a Comment

Popular posts from this blog

using preloadpkgonsite.exe to stage compressed copies to child site distribution points

UPDATE: john marcum sent me a kind email to let me know about a problem he ran into with preloadpkgonsite.exe in the new SCCM Toolkit V2 where under certain conditions, packages will not uncompress.  if you are using the v2 toolkit, PLEASE read this blog post before proceeding.   here’s a scenario that came up on the mssms@lists.myitforum.com mailing list. when confronted with a situation of large packages and wan links, it’s generally best to get the data to the other location without going over the wire. in this case, 75gb. :/ the “how” you get the files there is really not the most important thing to worry about. once they’re there and moved to the appropriate location, preloadpkgonsite.exe is required to install the compressed source files. once done, a status message goes back to the parent server which should stop the upstream server from copying the package source files over the wan to the child site. anyway, if it’s a relatively small amount of packages, you can
11 comments
more »

How to Identify Applications Using Your Domain Controller

Problem Everyone has been through it. We've all had to retire or replace a domain controller at some point in our checkered collective experiences. While AD provides very intelligent high availability, some applications are just plain dumb. They do not observe site awareness or participate in locating a domain controller. All they want is the name or IP of one domain controller which gets hardcoded in a configuration file somewhere, deeply embedded in some file folder or setting that you are never going to find. How do you look at a DC and decide which applications might be doing it? Packet trace? Logs? Shut it down and wait for screaming? It seems very tedious and nearly impossible. Potential Solution Obviously I wouldn't even bother posting this if I hadn't run across something interesting. :) I ran across something in draftcalled Domain Controller Isolation. Since it's in draft, I don't know that it's published yet. HOWEVER, the concept is based off
3 comments
more »

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.   DETECTION status messages take 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 m
3 comments
more »