One of the privileges of working on OneNote is working with a bunch of fun, creative folks. It makes it such a joy to come to work every day. As an example, here's a funny parody of One Day More from Les Miz they wrote and recorded after hours in their offices just for fun. It was written, sung and recorded by team members. Nicole wrote the lyrics. Scott, Tom, Victoria, Edan, Greg, Anav, Nicole and others sang and recorded the vocal track one night in Scott's office. Scott did the audio editing. And lots of team members joined in hamming up the lip sync video. And Greg, Nicole and Scott put it all together.

This gives you a little inside glimpse on why we love working here.

https://youtu.be/WUsAPdv8JZ4

[View:https://www.youtube.com/watch?v=WUsAPdv8JZ4&feature=youtu.be]

I just released an update to that solution that:

• Fixes a number of issues some people had on Windows 7 64 bit.
• Enables the option to print to a single page, or print each page to a separate sub page (frequently requested).
• More easily enables scaling the print outs to a custom size.

Note: this also works on Vista 64 bit and 32 bit Windows 7 or Vista.

Go to the codeplex site for XPS2OneNote to download it and install it. Please read the instructions for how to use it. You’ll need to restart your machine or manually start XPS2OneNote after installing it.

NOTE: this is not necessary for OneNote 2010 Beta. OneNote 2010 has full 64 bit support for the Send to OneNote 2010 print driver.

In this post I’ll give a 30,000 foot overview of the major investments for OneNote 2010, and then in subsequent posts we’ll go into more detail on the feature areas with screenshots and more.

OneNote 2010 Investments Overview

1. Universal Access

We repeatedly hear that access to your notes and the ability to take them anywhere is very important, whether you’re at work, home or on the go. OneNote 2007 already provides offline availability and seamless sync, and a basic OneNote application for Windows Mobile. But we knew that was just the beginning. With OneNote 2010 we’ve added:

• Sync to Cloud (Windows Live): Your notebooks sync and are available anywhere from any machine. Of course this is in addition to all the existing ways you can sync notebooks (file shares, SharePoint, USB drives etc.)
• OneNote Web App: You can access and edit your entire notebook from a browser. Even on a machine that doesn’t have OneNote installed.
• OneNote Mobile: A more complete OneNote version for Windows Mobile phones. Syncs whole notebooks. Syncs directly to the cloud. No need to tether your device. Richer editing support.

Note: The above are not yet available in the Tech Preview unfortunately. We’re still finishing some integration work for sync to Windows Live.

2. Sharing and Collaboration

With OneNote 2007 we pioneered simultaneous multi-user editing of notebooks. OneNote 2007 auto-magically merges the edits, even simultaneous edits on the same page. This is valuable for single users (you can edit on desktop and laptop and not have one machine lock the file), but it’s even more valuable for  teams sharing a notebook for plans, ideas, meetings and so on. Or perhaps a family notebook shared with your significant other. We’ve heard lots of positive feedback about this, and  it has completely transformed the way many teams work and collaborate. We’ve also heard about many families that use it for sharing home renovation plans, gardening info, recipes, wedding planning and so on.

In OneNote 2010 we’ve added a number of features to make the experience of sharing with others more productive and intuitive. These include:

• What’s new (aka Unread) highlighting: New content that someone else added or changed since you last looked at a page is highlighted so you can see what’s new on that page. Also, the notebook name, section tabs and page tabs are shown in bold so you can quickly navigate to pages with new content.
• Author indicator: Content written by anyone other than you has a small color coded bar to the right with their initials. At a glance you can tell who wrote something.
• Versioning: Quickly show past versions of any given page, who wrote it and when, with changes relative to previous versions highlighted.
• Fast sync on same page: When multiple people are working on the same page we speed up the sync of that page so you can see other peoples edits in near real time.
• We also added capabilities to be able to quickly search for recently added content (last day, week, month etc.) or get an overview of what given people changed on what days.
• Merge two sections: This feature is more of a detail but it fits here. Sometimes people share notebooks using Live Mesh or Dropbox or other file sharing solutions. And you can end up with two forked copies of a section if you happened to make changes on two machines at once (you can read earlier posts for context, but OneNote cannot auto-magically merge simultaneous edits when working on these systems that copy files around underneath OneNote). So we’ve added the ability to manually merge any two sections if you ever get into this situation. Just tell OneNote which two sections you want merged and OneNote will take care of it.

3. Better ways to Organize and Find your Notes

Capturing, organizing and finding your information has always been at the heart of what OneNote does. We’ve made several enhancements in this core area. Some of these will be more understandable once we have detailed blog posts with screenshots.

• Section and page tab improvements: making notebook navigation work better with a larger number of sections and pages, easier to create new sections, better page tab hierarchy visualization, collapse sub page groups, just drag left and right to create sub pages and organize your pages, insert new pages directly anywhere in your page tabs.
• Fast “word wheel” search for navigation: the goal of this is to make search a super fast way to get to your regularly used notes. Historically search has been more of a “last resort” feature when you couldn’t find something. We’ve completely revamped this experience so it is now designed to make it the fastest way to get to any page including pages you visit regularly like your To Do list.
• Wiki linking: you can easily create a link to an existing page or to a new page for a topic. You can do this by just typing the Wiki link syntax (e.g. just type [[The Page Title I Want]] ), or use our new page search experience from within the link dialog. This enables you to easily create Wiki like notebooks with lots of cross links across pages.
• Quick filing: there are many ways to send content to OneNote (Print to OneNote, send mails from Outlook, send pages from Internet Explorer and so on). Our new Quick Filing experience pops up to let you pick where in your notebook you want to send it. It remembers the last places you sent things. You can search in Quick Filing to find a specific section or page if you want it somewhere else.

4. Research and taking notes linked to documents, web pages

OneNote is often used as a companion while researching topics and collecting information (e.g. a market analysis study, a class paper, a home renovation, a car purchase and so on). This often involves looking at web pages or documents and taking notes. You could also be reviewing a document or class lecture slides and taking notes as you’re looking through them. We’ve enhanced a number of things to make this experience better.

• Docked OneNote: you can dock OneNote to the side of your screen. It docks alongside other windows (e.g. browser, Word, PowerPoint). OneNote minimizes UI and just shows the notes page alongside your document/browser.
• Linked Note Taking: while in this mode, OneNote automatically links the notes you take to what you’re looking at – the web page URL, the selection point in Word, the current slide in PowerPoint. Later in OneNote you can hover on that link and you’ll see a thumbnail preview of the original document, you can click on it and it will open and take you back to what you were looking at when you wrote the note.
• Auto text wrapping: this goes well with Docked OneNote but is useful in other cases too. OneNote now wraps text outlines to fit the windows size if there is only one outline on the page. This makes it easy to see all your notes even when OneNote is docked to a relatively narrow window on the side.
• IRM protected printouts: this is mainly for enterprise and training scenarios. The idea is that companies can distribute things like product manuals or class notes in OneNote that are protected intellectual property. The recipient can view these in OneNote and take their own personal notes on top of these materials and beside them. If for some reason the materials were viewed by an unauthorized person they would not see any of the protected material.
• 64 bit print driver: Yes, OneNote 2010 has a new native print driver that fully supports 64 bit. It’s based on the XPS technology from Windows. It also has other virtues like better rendering quality when scaled.

5. Editing improvements

There are a number of basic editing improvements in OneNote. Below are some more prominent ones.

• Basic styles: OneNote 2010 adds very basic styles like Heading 1,2,3. This does not have the power of Words styling features. OneNote is not designed for that level of document formatting. But it does give you a way to quickly have your meeting notes have a little structure.
• Bullets improvements: this is a simple one but oft requested. First level bullets now indent from previous text.
• Equations: OneNote 2010 now supports the ability to add math equations. Great for students or people who need to input math into their notebooks. OneNote will also support the ability to recognize hand written math equations and convert them when running on Windows 7.
• Mini-Translation tooltips: OneNote can now show you a tooltip with a translation into your native language when your mouse hovers over a foreign language word. Great for language students, or if you’re working in a bi-lingual situation and need help understanding a word in a shared notebook or that you clipped from the web. This is thanks to integration of work from our GXP team mentioned in their blog.

6. Touch support

With the rapidly increasing availability of touch enabled PCs and the enhanced touch experience in Windows 7, this was a natural thing for OneNote to support.

• Finger panning and auto-switch: you can use your finger to scroll and pan around any page in OneNote. OneNote auto switches between pen, pan, and selection depending on your input device. So for example you can pan around a drawing with your left finger and draw with a tablet pen in your right hand. This makes for a very natural two handed interaction model.
• Pinch zoom: we enabled pinch zooming within OneNote centered on the fingers.
• Navigation controls improved for touch: we’ve made some small optimizations to make the UI easier to use with touch.

7. Fluent UI

OneNote now adopts the Fluent UI along with the other Office applications.

• Ribbon: OneNote now has the Ribbon. We’ve designed this to optimize for the key OneNote scenarios and make them easier to use. This is also what enables us to more easily add features like math equation editing (the common controls for that use the Ribbon), and potential future features.
• Office Backstage: This is new for Office 2010. OneNote will be taking advantage of it to make tasks like creating new notebooks, and new shared notebooks on the web easier (we’re still doing work on this).

We’ll write more in future posts to explain each of these areas in more detail. We hope you enjoy OneNote 2010!

David Rasmussen

Group Program Manager, OneNote

_______

Short version: I have a solution for those of you needing a 64 bit OS solution for printing to OneNote. Read on for details.

Well… it’s been a long time between posts. Without making excuses, suffice it to say we’ve been crazy busy working on the next release of OneNote. And given strong feedback about the 64 bit print driver issue, I decided to put what little spare time I had into trying to develop a 64 bit OS solution for printing to OneNote 2007 for you, rather than blogging.

So after spending some time over Thanksgiving and Christmas vacations and more than a few evenings coding I now have a solution you can download to enable you to print to OneNote 2007 from 64 bit Vista (and Windows 7 beta if you have it…).

You can see the details, download, installation and usage instructions for the XPS2OneNote 64 bit OneNote print driver solution on codeplex.

I hope it works well for you. Please feel free to leave me comments and suggestions here.

Some additional comments

You can ignore all of this… unless you’re interested in context.

• First, please let me repeat my sincere and humble apology that the included print driver didn’t work for 64 bit OSes as I wrote in my original post explaining why the Send to OneNote 2007 print driver doesn’t work on 64 bit OSes. I know it seems lame.
• Second, please note that while this solution I’ve created works quite well, it’s something of an expedient hack. It leverages the XPS print driver included with Vista and watches a folder for XPS files landing in it. It’s not the sort of solution we could ship as an integrated part of OneNote in its current form. It’s not architected in a way to cleanly integrate into the product  (it’s basically a separate watcher exe…). There is a whole lot to shipping release quality software that this doesn’t cover (handling numerous edge cases and exceptions, internationalization and support in a hundred or so languages, patching support, accessibility, full test passes on a multitude of configurations, the ability to support the code base for 10 years and an abundance of other details). 
• Given that, here are some caveats: I’m releasing this as a CodePlex project. It was created in my own personal time. It’s not Microsoft officially supported software. I will endeavor to do my best to address any issues that come up. I will make the source code available on CodePlex (once I’ve cleaned up a couple of things), so others can feel free to improve it too. And don’t judge Microsoft by the quality of the source. I’m actually the Group Program Manager for OneNote and I’m not paid to write code professionally these days. We have much smarter people to do that…
• As I wrote in my previous post, the MODI print driver that the original Send to OneNote 2007 print driver is based on is a very old code base that’s frankly a big hairball. Making it support 64 bit wasn’t really viable. I’ve gotten some feedback along the lines of “surely this must be doable, or easy because how hard can a print driver be… or some other print driver supports this”. Well, yes in software anything is possible. And sometimes if you have the right code to start with it’s even easy. But that’s really not the case with the MODI code base. Our solution is to migrate OneNote in the next release to use a print driver code base (that was developed by printing experts elsewhere in Microsoft) that IS modern, DOES support 64 bit and has all these nice flexible characteristics you expect software should have. But unfortunately it didn’t exist yet when we originally created OneNote 2003…
• This migration involves a significant enough shift in the way it integrates with OneNote that it’s not practical to do this as a patch to OneNote 2007 (i.e. it would very materially impact other important things customers have told us they want). So we’re doing it as part of the work for the next release of OneNote.
• I’ve gotten a few heated comments (yes I was even told I was “a gimp” who should “suck rotten eggs”), implying that somehow we’re malicious and conspiratorial, don’t care about our customers and this is all a secret plot to make people pay us more money to upgrade. I will confess that kind of hurt. I can assure you it’s not true. We love OneNote. We want our customers to love OneNote. We work ridiculous hours to try and make that happen and bring you the best product we can. We’re actually a pretty small team. We’re just doing what we can with finite resources.
• And while I know it’s not much consolation, we wrote in the System Requirements from day one that the print driver was not supported on 64 bit OSes. That’s on the box, and it’s on the web site. I know, no one reads System Requirements these days but really we weren’t trying to hide it and 64 bit OS support for the print driver never was a feature of OneNote 2007. So we didn’t remove a feature that was already there as somebody implied.

With that all said I hope this solution works for you and feel free to leave me comments about it.

UPDATE: Please see my recent post on a solution for Printing to OneNote on 64 bit OSes.

__

We've been getting quite a few questions and concerns about the "Print to OneNote" print driver that comes with OneNote 2007 not being supported on 64 bit OSes. I just wrote the following in response to a blog post and some comments about it on the GottaBeMobile site. I'm posting it here too for reference. It explains some of the context behind where we're at on this, and why. We fully understand how important the print to OneNote feature is, and we apologize that the print driver for this that shipped with OneNote 2007 doesn't work on 64 bit OSes. We plan to address this in the next version of OneNote.

In mid December Office 2007 SP1 was released on Microsoft Update. It contains lots of good improvements and a few for OneNote. However, it turns out we also broke something with one of the fixes. You can't create notebooks on a Windows file share that is also running WebDAV. This is what we call a "regression" (when in fixing something you break something else). We feel very bad about this and we're working hard to address it.

Please leave a comment below if you have hit this problem. We'd like to get a sense of how common this is and any affected configurations beyond the ones we know. Prevalence affects how urgently we can get a fix through the pipe. And please mention anything you know about your server (what the server OS is, whether it's also running SharePoint or some other web server etc.).

Here are the details and a work around.

Issue: can't create notebooks on Windows file share running WebDAV

• If you try to create a new notebook on a Windows file share server that also runs WebDAV then you will fail to create the notebook.
• For example if you try to create a notebook called notebookname at \\fileservername\filesharename you'll get an error message like: "OneNote cannot create a new notebook at: https://fileservername/sharename/notebookname"

Workaround:

To work around this follow these steps.

1. Go to the folder where you want the notebook in Windows Explorer (e.g. go to \\fileservername\filesharename )
2. Create a new folder with the name you want the notebook to have (e.g. notebookname )
3. Right click that folder and choose "Open as Notebook in OneNote"
4. The folder will open up as a blank notebook in OneNote. Then click on the message in the middle of the screen to create the first section and you're good to go.
5. Alternatively: instead of step 3 above you can start OneNote then go to "File"->"Open" -> "Notebook" and then select the folder you created in step 2.

Background:

• For the curious, the bug is related to how we check the folder path and decide under the covers which client side file redirector will handle the remote file access when working against web servers. When you're actually trying to access the plain Windows file share on the server with a UNC path, and the server is also running a WebDAV server then this logic has a flaw in it that causes it to try the WebDAV redirector (UNC paths can be valid WebDAV paths...).
• This won't affect many people in larger companies where Windows file servers and Web servers or SharePoint servers are usually kept distinct for clear role separation.
• It is more likely to affect small business scenarios where a server may play multiple roles and is potentially acting as a web server as well as a file share. Examples might be Windows Small Business Server depending on how it's configured.

Notebooks on SharePoint Servers

Overview

• SharePoint is a great team repository,  a place to share documents, lists, calendars, and so on.
  • You can access documents from a browser with more context than just a file list on a file share.
  • There are lots of nice features for custom solutions like workflow support, metadata support, search and query by metadata across an entire enterprise and so on that I won't go into.
• Many teams  have all their shared documents on SharePoint servers for these benefits.
• In that case, it makes sense to have your OneNote shared notebooks in the same place on SharePoint.
• Internet access to your notebooks is one significant benefit
• SharePoint is accessible via http over port 80.
• It can be made available more easily across the internet.
• Many service providers offer SharePoint hosting services
• If you have a OneNote shared notebook on a publicly hosted SharePoint server you will be able to access it with OneNote from anywhere, and collaborate with people anywhere.
• Note: you still need OneNote to access the notebook, not just a web browser. However, you can optionally publish an html web view of your notebook using the OneNote Web Exporter PowerToy.

Performance and Reliability

More things can go wrong when syncing OneNote notebooks to SharePoint vs syncing to a Windows file share. As there is more complexity and variety in the components and configurations involved.

• Sync times are much longer on SharePoint
• OneNote syncs every 10 minutes to SharePoint, whereas it syncs every 30 seconds on Windows file shares.
• The worst case time between making a change and others seeing it is 20 minutes (vs a minute on a file share).
• A change to a OneNote section file on SharePoint requires the whole file to uploaded or downloaded
• On Windows file shares, OneNote can read/write just the bits in the file it needs to update. This is very efficient.
• However, file access on SharePoint uses WebDAV
• WebDAV does not support byte range read/write (also known as Partial Get/Put)
• Thus OneNote must upload or download the entire file.
• This uses more bandwidth, hence the reason for the 10 minute sync interval.
• This is also the reason why Embedded files are stored alongside the section file in a thicket folder on SharePoint (whereas they are stored inside the .one file on Windows file shares).
• Authentication is a common problem area
• SharePoint supports multiple authentication types - including Windows Integrated (Kerberos or NTLM), Basic, Digest, Forms, and in some cases Windows Live ID.
• They each have some unique characteristics, and subtleties in behavior
• Vista vs XP client makes a significant difference
• Vista has a completely new improved WebDAV stack that OneNote uses
• Vista's WebDAV uses WinHTTP instead of WinInet. WinHTTP is new in Vista, it has some different behaviors to WinInet. Some calls to SharePoint (like file enumeration) still use WinInet. This introduces some complexities in things like authentication when the two networking stacks behave differently.
• On XP, Office uses a technology named"Rosebud" (also known as MSDAIPP, often referred to as "Web Folders") to access files on SharePoint. It's a very complicated mix of technologies, and frankly prone to issues ... not my favorite and we're transitioning away from it as of Office 2007 and Vista in favor of WebDAV. It uses something called "Microsoft Office Protocol Discovery" [scroll down halfway to 'Understanding Microsoft Office Protocol Discovery] to talk to the server. It attempts to discover what services the server supports then decides whether the user should have read only browse access, or read/write access. It determines if it can use WebDAV or Web Extender Client (WEC), otherwise it falls back to HTTP GET and read only. In general when talking to SharePoint Rosebud uses WEC which talks via FPSE (Front Page Server Extensions) to SharePoint and avoids the XP WebDAV stack altogether.
• See my earlier post on SharePoint - Access Denied for some more details on differences between behavior on XP and Vista
• [there's a lot more technical background information I could write here, but that's enough for now, and if I get many questions I'll add further clarifications later...]

Troubleshooting Tips

The most likely problems you'll see with OneNote notebooks on SharePoint are related to authentication.

• Getting "Access Denied" infobar prompts
• Getting password prompts that keep popping up
• Failing to open a notebook (possibly after getting password prompts)
• Having read only access to the notebook (you can't type anything)

Below are some steps that commonly solve these issues:

1. Install Office 2007 SP1. It's available through Microsoft Update (so you may already have it installed) or for direct download. You can check if you have this installed by clicking "Help" -> "About Microsoft Office OneNote" in OneNote. The version number at the top should be 6211.1000 and say "SP1" in it. It has some relevant fixes to improve this.
2. Confirm that "Auto Detect Settings" is on in Internet Explorer if you're using Vista.
3. Install Vista SP1 (if you have Vista) from Microsoft Update as soon as it's available (soon). It has some relevant fixes.
4. If your SharePoint site uses Basic Authentication (some hosting service providers use it) then you must use https:// for the URL path.
5. Confirm whether you have write access to the SharePoint document library where the notebook exists. Go there in your browser, and try to make an edit to a non-OneNote file.  If you can't edit any files then it's possible you don't actually have correct write permissions to that location and should speak to the administrator about the permissions.

[Sorry, it took a while to get around to part 2. I was out on vacation.]

Sometimes things go wrong, or you have trouble setting it up in the first place. Mostly due to issues in the underlying file system chosen. Not all file storage systems are created equal. Some are great, some are not. Some are great for some purposes but not others. I'm going to write a series of posts as a comprehensive overview. I'll explain each, and include pointers to trouble shooting potential issues. I'll update this over time as I get questions and may add links to more details.

The key deciding factor in sharing your notebook is the location you choose to share it from and the technology used to access that. These include.

1. Windows File Shares (otherwise known as SMB or CIFS shares)
2. SharePoint servers
3. USB drives / SD cards / other removable drives
4. Windows Home Server
5. WebDAV servers
6. Peer replication technologies like FolderShare or Groove
7. Other web storage services (Sky Drive, Office Live, etc.)

I realize this list makes things look complex. In the basic scenarios things just work. But there's a great diversity of file sharing technology options out there that at least some people somewhere are using and it's worth being comprehensive.

There are sub categories within each of these. I'll go over each in a separate post. This one will cover Windows File Shares.

Windows File Shares

Overview

• Windows File Shares are generally the best performing, fastest and most reliable place to share OneNote notebooks (I use them mostly)
• Work very well on home networks, or work networks
• Usually not available over the internet (although they can be with VPN software like Hamachi)
• Use the SMB (otherwise known as CIFS) protocol
• Available on Windows Servers (common in work environments), or personal Windows XP or Vista machines
• Mac OS and Linux also provide support for Windows File Shares using SMB
• On Linux SAMBA is the technology most often used to provide Windows File Shares using SMB
• Home network hard drives that are small Windows Files Share/SMB servers are becoming more popular and are cheaply available under brands like Western Digitals "My Book", iomega, Maxtor, Buffalo, Linksys, DLink etc.  Technically these are NAS devices, and are usually small servers inside running Linux and SAMBA. I don't recommend these for reasons discussed below.

Performance and Reliability

• Performance is very good.
• OneNote can access only the parts of the file it needs. It does not have to update the whole file when syncing.
• Syncs every 30 seconds.
• Generally very reliable, with the big exception of all SAMBA based shares (see below) and some issues if you're using Windows Offline Files

Troubleshooting tips

Below are some potential issues, explanations and resolutions.

1. Can't write to the notebook. Can't create it or save it to the windows share.

   • Confirm you have permissions
   • As a simple test copy a small file (text file or something) up to the same folder location as the notebook using Windows Explorer.
   • If this fails you don't have permission to access the share or file system. You need both share permissions and file system permissions (that's the most confusing aspect for some people). Here's a technical article about the distinction between Share permissions and File System permissions. I'll try and post a simpler guide later [TODO]. In general, if you setup a Share on Vista the normal way, then it takes care of these two types of permissions automatically (I think XP SP2 does too...).

2. On your networked hard drive or SAMBA share sections disappear (and other issues including possible corruption)

   • This applies to things like the Western Digitals "My Book", iomega, Maxtor, Buffalo, Linksys, DLink  networked hard drives.
   • Recovery: If you look in the folder on the network share, you'll often see an extra file with a name like "foo~RF12345678.tmp". Rename this to "foo.one" then open OneNote and sync and you'll probably have your file back.
   • Details on this (and why I don't recommend SAMBA shares) below. I'd suggest you consider storing your OneNote notebooks somewhere else.
   • Most of the network hard drives use a small Linux OS and SAMBA to provide the file share
   • Many versions of SAMBA are badly behaved and don't fully and correctly implement SMB
   • In particular many SAMBA implementations seem to have problems with ReplaceFile failing, which OneNote uses
   • SAMBA, like much open source, has many different versions (100s) that have been picked up by the various different hardware manufacturers (running on multiple trimmed down variants of Linux), they've individually tweaked them, forked the code, and do not necessarily update them. The result is that while some of the latest versions of SAMBA do seem to implement ReplaceFile correctly, many of the networked hard drives seem to use versions that don't implement ReplaceFile well. Such is the nature of open source. [Whereas if you have a Windows Server, XP or Vista machine and you stay fully up to date on your Windows Updates they are all the same (well each OS is) and known to work and be reliable. ]
   • This tends to hit OneNote more than other apps, because most apps don't use ReplaceFile. Most apps just open a file, with an exclusive lock on it, then save it and release when they're done. Because OneNote has multiple simultaneous users on a notebook things are a little more complicated. Also we use ReplaceFile to safely do operations like optimizing the file (we optimize a copy then replace the original, ReplaceFile is supposed to be atomic and safe). Other applications that tend to behave a little more like OneNote are Money and Quicken and things that have database type continual access. So these apps will often exhibit issues working against these networked hard drives too.
   • Basically the most common and therefore well tested aspects of the SMB protocol and file system semantics work fine on these devices. But if you have an app that uses a broader set then they can run into trouble.
   • Because of these issues above I'm not sure how much I'd trust these SAMBA hard drives, given other things that aren't well tested (like ReplaceFile) may be buggy too. We've seen other issues on SAMBA shares, including corruption.

3. Password prompts

   • You may get an infobar on the notebook (yellow message bar at the top of the page) saying that you need a password.
   • Click this and then enter the user name and password for the notebook on which the server is located
   • If you check "remember this password" then you won't get asked for it in future and OneNote will just be able to automatically sync. Otherwise you'll need to reenter it every time you restart.
     

4. Windows Offline Files causes duplicate copies of sections if edited from more than one machine, or edits from one machine don't seem to be showing up or are lost.

   • Windows Offline Files might deserve a post all of its own... see this article on Windows Offline Files  for an overview.
   • Windows Offline Files provides cached access to network file shares when you're offline from them. Note that OneNote also has its own cache that enables it to work offline, and do things like multi-user edit, sync and merge automatically.
   • Windows Offline Files is great for things like work laptops that connect to your network share at work, and you want access to the same files while traveling or out of office. It's used when you have your Documents folder redirected to a network share for example.
   • However, it means that when you are offline, OneNote is working against a local cached copy of the file (cached by Windows separate to the OneNote cache). This interferes with OneNote's ability to merge changes from multiple machines. Basically machine A and B both sync to a Windows Offline Files local cache copy. To OneNote it looks like it wrote to the server (because the Windows Offline Files cache is meant to be transparent in this respect). Then later when you're online Windows Offline Files replicates these two (now different) files up to the server. Windows Offline Files doesn't know anything about how to merge OneNote files, so it just gives you the option to keep both copies or replace one with the other.  Depending on what you choose you'll either end up with duplicate section files in the notebook (that are slightly different) or losing one set of changes. And on Vista if you don't resolve the Windows Offline Files conflict (it shows up in the Sync Center in the taskbar) then you'll be continuing to work against the local copy in the Windows Offline Files cache and won't even see the changes from the other machine at all.
   • How to avoid this:
     • If it's only you accessing the files (e.g. laptop and desktop both pointing to the same server Documents folder), then before switching machines and making edits:
       • Make sure OneNote is in sync (F9 on the keyboard will force sync) on the machine you're leaving
       • Make sure Windows Offline Files is in sync (can force sync from the sync center in notification area on Vista)
       • Then when you get on the other machine make sure Windows Offline Files is in sync there before starting to edit in OneNote
     • If multiple people are sharing the files
       • Don't use Windows Offline Files on this share. Or move the notebook to another  file share.
       • On Vista, you can check which shares Windows Offline Files is syncing from the Sync Center partnerships.
   • I personally choose to keep my OneNote notebooks on shares that don't have a Windows Offline Files partnership syncing it (I use Windows Offline files for other shares). OneNote does a fine job caching, syncing and merging all by itself. And multiple layers of syncing and caching tend to get in the way of merge technologies like OneNote's.
   • There a bunch of useful information online about managing Windows Offline Files like:
     • How to make folders available offline (and conversely if you reverse this you can stop Windows Offline Files from syncing a folder)
     • Windows Offline Files sync conflicts, how they occur, and how you resolve them
     • Windows Offline Files sync errors (problems with sync rather than conflicting file changes)
       

5. Windows Offline Files on Vista causes corrupt OneNote files

   • There was a bug in Windows Vista's new Offline Files implementation that could cause corruptions in OneNote files (and some other like Money)
   • It has been fixed in Windows Update. It's a "recommended" update because it's not a security fix. So you have to choose to install it. Having said that, you really should install it when you see the list of issues it addresses.
   • Details of the fix are here https://support.microsoft.com/kb/938979 
   • So if you're using Vista, OneNote and Windows Offline files make sure you have installed all the latest Windows Updates.

OneNote notebooks on SharePoint coming up in the next post...

• An 'infobar' appears at the top of the page in OneNote saying you don't have permission to sync to that section file
• You may have failed to create a new notebook on that SharePoint location
• You may have failed to open the notebook

One obvious reason you might get this is that you don't in fact have permissions to write to the SharePoint location. You should check that first, for example, by trying to write a simple text file there. But there could be other causes for this, most of which should be quite rare*. But if you're running on Vista there is one very simple reason that is likely to be quite common.

Automatically Detect Settings needs to be on

• You need to ensure that "Automatically Detect Settings" is checked on in the "Internet Options" settings in Internet Explorer, as shown below.
• You can get to this from Internet Explorer -> Tools -> Internet Options -> Connections -> LAN Settings

• If this option doesn't work for you because it messes with your browsing in Internet Explorer then go back to your original settings and read the rest of the nitty gritty in this post for other ways to possibly fix this.

* there's actually another possibly common cause, depending on your network conditions you may get time outs when connecting to your server that get falsely reported to OneNote as permissions denial. We have made some changes to address this issue that you'll see in a future service pack soonish. This should be intermittent though (unlike the auto detect settings issue) and likely fixed just by restarting OneNote once the network condition has improved.

Why do you need Automatically Detect Settings on?

There's a lot of details behind this that may be hard to follow if you don't know much about HTTP etc. I'll try and explain it briefly.

Background

• "Automatically detect settings" talks to a server on your network to get basic configuration information like proxy server
• In XP HTTP traffic goes over a protocol stack called WinInet
• In Vista there is also a new network stack called WinHTTP for HTTP traffic. This is a much improved HTTP specific stack. It was originally created for Windows Server 2003.  WinInet still exists on Vista for backwards compatibility.
• WebDAV (a protocol for accessing files over HTTP) was re-written in Vista to use WinHTTP. This was a significant improvement over the WebDAV stack in XP.
• However, many applications still use WinInet because they haven't been re-written to use WinHTTP on Vista. Internet Explorer for example still uses WinInet. And many parts of Microsoft Office still use WinInet. Parts of OneNote included.
• So on Vista when OneNote is accessing files on SharePoint it makes some calls to check on things like which files have changed and so on, that ultimately end up using the WinInet stack. But when it actually tries to write up changes to the file it uses WebDAV which uses the WinHTTP stack.
• Now there is a subtle difference in behavior between WinInet and WebDAV over WinHTTP. WebDAV on Vista has a rule that it never proactively sends your credentials over the wire unless you have auto detect settings on (because that's how it gets configured to know when to send your creds proactively and when not to). WebDAV defaults to assuming you're on open public internet when this is not set and doesn't send credentials proactively at all.
• Note: that your credentials are always encrypted anyway, so I'm not talking about plain text transmission here. WebDAV still thinks it's a good idea not to send them unless needed on public internet. It's good surface minimization.
• In theory, if WebDAV gets a permission denied response the user will be explicitly prompted for the credentials and WebDAV will then proceed to send them and you'll successfully connect.
• The reason for the difference in behavior is that inside a work environment people generally expect to just be able to connect to all their server resources without having to enter credentials for each server.

The problem

• OneNote syncs in the background relatively frequently. It's not just saving when the user hits save. OneNote is also syncing potentially several notebooks on different servers.
• That means OneNote can't just pop up random dialogs asking you for credentials every time it syncs, otherwise you might be working on one notebook, and get bothered by credential prompts randomly popping up from a second notebook syncing in the background. That would be pretty weird.
• So as a result, OneNote makes file access calls in a 'UI-less' mode. The layers under OneNote are told not to show credential prompts if there are permissions failures. The various networking layers below OneNote return "permissions denied" error codes. OneNote should then display an infobar saying you need to enter a password and give you the option to click it to enter the password. This is less intrusive than random cred prompts. And this infobar only shows when you're on the relevant notebook.
• However, in the situation above, the initial WinInet calls all succeed (checking the notebook is there, checking for which files changed etc.) and only writing the file up fails. This messes with this workflow a little and you get a slightly different infobar just telling you that OneNote got an access denied failure. This isn't very helpful...

This affects other apps too

• This problem manifests in different ways for different apps
• It's slightly less of a problem for traditional apps. Because they generally save in response to a specific user command only, and do it synchronously. They make all file access calls and network calls requesting full UI showing. This allows the underlying network stacks to just pop credential prompts whenever needed (it's also the reason they can hang while you're saving to a slowly responding network server...).
• So for many apps this manifests as you getting one to three credential prompts while trying to open a file. Sometimes these may fail and you'll end up with a read only copy of the file open.
• See this post on the SharePoint team blog for more details on this
• By the way I would NOT "stop and disable the WebClient service" as suggested as one of the possible solutions on this blog post. It turns off WebDAV which will break OneNote syncing, and likely other apps too. And the "install Web Folder and run in XP compatibility mode" option has some unpleasantness too... Look to the bottom of the post for "Problem Description" and "Potential Workarounds" for other options.
• Note, that in theory the result should just be that you get a manual cred prompt and entering credentials should succeed. However, in practice I have noticed that there appear to be occasions and configurations where even after entering the credentials the access fails with other apps too. Still investigating.

What's being done to address this?

We're paying lots of attention to this issue. And here are a couple of things that are being done among others:

• There are hot fixes coming from the Windows team to help deal with this as mentioned on the SharePoint team blog post. The hotfixes are KB941853 and KB941890. These fixes are only available through support right now (e.g. if you're a corporate customer) but should be available in a future service pack after further testing and work.
• OneNote will also be doing work to have a better response to this particular kind of partial failure in the network calls, so the user gets more helpful information in the infobar and OneNote can prompt appropriately where possible.