Skip to main content

misc: cool things about onenote

onenote has been my constant companion for many years now. between onenote and outlook, i can’t think of very many things that can’t be effectively managed, tasked, or tracked -- at least from a day-to-day perspective. i found some pretty cool things about onenote recently that i thought i’d share: subpages and onetastic.

 

SUBPAGES

Snagit screen capturefor those of that don’t know, i’m an avid pool player. naturally, since i use onenote, i’m a pool player that likes to keep a lot of notes about billiards as you can see in the screenshot.

the first thing i want to point out is onenote allows the use of subpages. i went for far too long without knowing that. if you look at #1, you can see how onenote looks when you collapse subpages. #2 is the expanded view.

once you collect your pages as subpages, it makes managing them easier since you can work with them in bulk (move, copy, delete, cut, etc.)

to create a subpage, right-click the page tab and choose make subpage. the shortcut trick to make or promote a subpage is to drag the page tab left or right with your mouse as shown below.

Snagit screen capture
http://screencast.com/t/l5mpZ4vy

 

ONETASTIC

i stumbled on this gem while i was looking for a tool to apply styles like you can in pretty much every other office product. enter onetastic. onetastic for microsoft onenote is an amazing collection of tools Snagit screen capturethat integrate directly with onenote. since most of the tools are macros, it’s as extensible as you want to make it. so far, i’ve found that their collection of macros is more than enough for me.

if you’re a heavy onenote user, it’s definitely worth checking. i found all kinds of other cool macros like sorting pages, creating a table of content, search & highlight, etc.

 

 

BONUS

onenote 2013 keyboard shortcuts

Comments

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

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

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