Windows 10 and Virtual Desktops with X-Mouse

Since my first introduction to Linux, I have found virtual desktops to be a very interesting and intriguing concept. However, I could find no practical use for myself to be able to utilize them. That, and the fact that I really only used Windows to get things done for work and play, meant I never had much opportunity to try them out fully.

Then, a few years ago, I started using OS X (10.8) and with its wonderful trackpad (both on the laptop and external), virtual desktops became something much more useful. I could swipe between screens of programs seamlessly and loved it, but the implementation on multiple monitors (3) was less than extraordinary (at least, when I first started working with OS X).

Enter Windows 10 and its virtual desktops! Wait... How exactly do these things work? I have to hit WinKey+Tab on the keyboard then click a button with the mouse and to switch desktops I have to use WinKey+ArrowKey? This is never going to work for me. I am mostly navigating with the mouse and my fingers are on the home keys if I am typing. Then, it donned on me: What if I could make use of all these "buttons" on my mouse (Logitech M705) that I never use?

This is where X-Mouse comes in. The typical Forward and Back buttons on the thumb side of the mouse are now mapped to open and close virtual desktop and the mouse wheel that tilts (which I never have had any use for before) is now able to switch between these desktops.

I can now keep all of my applications open instead of being hid behind one another or trying to locate the little button on the taskbar. Now, I would be happier if Windows 10 would remember how many desktops I had open and where I wanted my programs, but it is a small annoyance and doesn't take long to get things set back up in the morning.

Note: Logitech's SetPoint software interferes with X-Mouse and also does not support the WinKey for mouse button assignment. If Logitech will update SetPoint to work with WinKey, then it could do all the work and provide access to the Application Switcher button (where the thumb rests) which does not work without SetPoint. X-Mouse does not see this button, so I have to hit WinKey+Tab manually (*shudder*) in order to move windows around between desktops, but that is rare.

by Christopher Scott via Everyone's Blog Posts - SharePoint Community

Web Application Proxy with SharePoint 2013 and Open with Explorer

After working with Microsoft for over a month to try to resolve an issue where Open with Explorer does not work when access externally through WAP (Web Application Proxy), we finally have a workaround/resolution.

The issue comes down to a hand off of authentication between protocols/services. This works properly for almost everything once you have configured the session cookies to a value above the default of 0. If you leave the PersistentAccessCookieExpirationTimeSec value at the default, your users will get prompted to log in for opening documents or anything that would pass authentication to another application or service. On top of this, though, is the fact that ADFS requires SNI (Server Name Indication).

The Open with Explorer option uses WebDAV which does not support SNI, however. Once it was determined that this was where things were breaking, a "fallback" certificate was able to be configured on the WAP server so that if a service does not support SNI, it could still authenticate properly. The instructions for this are very well detailed in a TechNet blog: http://ift.tt/1pmSo7F

The only place where this workaround may cause an issue would be if your WAP needed to be accessed by multiple services/protocols that did not support SNI (assuming each may need a different certificate). It is still possible to do this by binding different fallback certs to different IP addresses, but I did not need to go down that road.

by Christopher Scott via Everyone's Blog Posts - SharePoint Community