Chris Spera Contact Information - Per Gabe Aul Tweet

Chris - I'm dangerous with the little amount I know, but I have managed to set up 2 exchange accounts in all releases including the latest of 2016.  I think you're being a bit heavy handed in your response.

The key was figuring out how AutoDiscover works...or in my case didn't work with me having little access to the DNS side of things.  But, there is a solution - you can use an override to force it to use a local XML to follow the path to your correct AutoDiscover server.  There is a thread in the forums here somewhere that I wrote a very waffly reply outlining it....find that and hopefully it helps.

Sorry if I am telling you stuff you already know, but I didn't, and I fretted, and then I figured it out and haven't looked back since. 

I'm even loving the feature I've just discovered with Outlook when you insert an attachment - your most recently accessed / created files are automatically shown.  This may have been a feature in earlier versions  but I've just discovered it and hot dawggg it's awesome!

Digittt

Digitt,

You may be right. Perhaps I did vent a bit here. I apologize to all for that. I'd appreciate you pointing out the specific post you're referencing. I spent about 2 hours on the phone with my hosted Exchange provider last night trying to figure this out, and neither of us were able to get anything synchronizing.  Currently Outlook 2016 Preview only offers options for POP/iMAP or Outlook.com/EAS (which isn't Exchange, BTW, its Exchange Active Sync, which isn't quite the same in my experience, though you'd think it would be...)

Anyway, neither of us could find the magic words to get the account to register or sync, AND when I tried to upgrade from Office 2013 to Office 2016, with Outlook already configured and working prior to the upgrade attempt, Outlook would not open afterwards.  There's still something not implemented here, and it just seems silly not to have that baked in and working prior to a public beta release.

But again, if you can send me a link to the specific post you're referencing, I'd appreciate it.

Chris - I'm dangerous with the little amount I know, but I have managed to set up 2 exchange accounts in all releases including the latest of 2016.  I think you're being a bit heavy handed in your response.

The key was figuring out how AutoDiscover works...or in my case didn't work with me having little access to the DNS side of things.  But, there is a solution - you can use an override to force it to use a local XML to follow the path to your correct AutoDiscover server.  There is a thread in the forums here somewhere that I wrote a very waffly reply outlining it....find that and hopefully it helps.

Sorry if I am telling you stuff you already know, but I didn't, and I fretted, and then I figured it out and haven't looked back since. 

I'm even loving the feature I've just discovered with Outlook when you insert an attachment - your most recently accessed / created files are automatically shown.  This may have been a feature in earlier versions  but I've just discovered it and hot dawggg it's awesome!

Digittt

The next time the ink disappears, could you check if the OneNote canvas is responsive: you can scroll the page, type and navigate to other pages.

Please also see this thread:

http://answers.microsoft.com/en-us/insider/forum/insider\_office-insider\_onenote/inking-in-onenote-on-surface-pro-3-disappears/b6c5f168-f4dd-48ef-996b-8b933a28da9c?page=5&msgId=631809d5-6d11-4714-9a35-61a9cc6db85e

I have reported in that thread that it has happened with me as well.  There was hesitation in Build 10061, Ink floats and disappears when trying to move the OneNote canvas up to create more writing room.

When you describe the ink as floating, does it mean that the ink doesn't scroll along with the page?

Does the bug appear as frequently as before?

Please try the Office 2016 preview version that came out today. It would be version 16.0.3930. It has some changes that may help avoid this bug.

Mavis,

I am unable to complete any testing with OneNote 2016, as OUTLOOK 2016 has a blocker bug for my use case.

As of this date, Outlook 2016 Public Preview for Windows doesn't support Exchange accounts.  I understand that this is a preview and not finished software, but I use OneNote at work, and need my work calendar synchronized with Outlook so that my meetings, their agendas, invitation notes and attachments etc., are included in the meeting header when its pulled into OneNote.

Since Outlook doesn't support Exchange Accounts from ANY supported Exchange Server as of this writing, my retesting efforts are at a stand still. As soon as that support is included, I will be happy to retest with OneNote 2016.

(BTW... the fact that Outlook 2016/Office 2016 Preview was released to the public LACKING Exchange support (not EAS, but Exchange Server 2010/2013 support) is BEYOND outrageous. It seems ludicrous that an Exchange email client won't work with either an on-prem or hosted Exchange Server 2010 account, even as a preview.  

Who signed off on this release?!?! This isn't sour grapes. As an SQA VP, I'm asking a legitimate question...)

No it only happened the once during the day, but I have now reset my surface and reinstalled everything, so I'll see if it happens again before I try 2016

Thanks

The next time the ink disappears, could you check if the OneNote canvas is responsive: you can scroll the page, type and navigate to other pages.

Please also see this thread:

http://answers.microsoft.com/en-us/insider/forum/insider\_office-insider\_onenote/inking-in-onenote-on-surface-pro-3-disappears/b6c5f168-f4dd-48ef-996b-8b933a28da9c?page=5&msgId=631809d5-6d11-4714-9a35-61a9cc6db85e

I have reported in that thread that it has happened with me as well.  There was hesitation in Build 10061, Ink floats and disappears when trying to move the OneNote canvas up to create more writing room.

When you describe the ink as floating, does it mean that the ink doesn't scroll along with the page?

Does the bug appear as frequently as before?

Please try the Office 2016 preview version that came out today. It would be version 16.0.3930. It has some changes that may help avoid this bug.