Could be a First for Microsoft! Intneral Technical Wiki now Pushed to Quickstartonlineservices.com.
Internally, the Technical Product Management team had a Wiki they were using to keep track of all kind of issues. FAQs that were being asked all the time about things like public folders, mail enabled lists, how to work with proxy servers, when is feature "X" coming , blah blah blah.
The cool thing about this particular wiki is that it is a living resource that is actively updated, and used to drive meeting agendas, workflows, feature priorities, and other details. In other words, it's an important tool that we use here.
Well, we had that thought that most of this information would be really useful to Partners as well. It's current. It often has details that are difficult to find, and is relatively comprehensive. What if we could find a way to push the internal Wiki into Quickstartservicesonline and flag items we wanted copied so that partners would have access to the same agile resources we have?! So that's what we did. We made this even more useful by adding all the checklist items from the Migration and Discover whitepaper I recently wrote as line items in the wiki making it a great place to go for the latest questions you should ask before tackling a migration plan.
You can of course search for any topic or click on one of the topic of interest. Say you're interested SSO Auth Proxy (Single Sign On Authentication with a Proxy), click on the link and you'll see :
BPOS-S Single Sign-In Client (SIC as some refer to it) currently does NOT support Outbound Internet Authenticating Proxy Server configurations. Users will receive SIC messages stating …”unable to establish a secure connection..”. This is typically due to a Connectivity Issues with the BPOS-S Single Sign-On Services (SSO Web Services), which has been seen when connecting over the Internet from an On-Premise Authenticating Proxy Server. These servers can be of any flavor, such as Blue Coat, ISA, Threat Management Gateway (v.Next of ISA), etc., as long as they are configured for Outbound Internet Authentication.
Resolution/Workaround
1. Outbound Authenticating Proxy Servers MUST be using the NTLM Authentication method for the below to work!!!!
2. When the below snippet is placed into the SignIn.exe.config file, this allows the SSO client to pass the logged in users Domain credentials to the Authenticating Proxy Server, allowing Outbound Internet Connectivity:
a. Caveat: The user must be logged into the machine as a Domain User Account and that account must be granted Outbound Internet Connectivity for the below to work.
1. Browse to the following location to modify the SignIn.exe.config file: x:\Program Files\Microsoft Online Services\Sign In
2. Modify the SignIn.exe.config file, using Notepad.exe or other Application of choice:
3. Save the File
a. Logout and Exit SIC
4. Restart SIC
<system.net>
<defaultProxy useDefaultCredentials="true">
<proxy usesystemdefault="True" />
</defaultProxy>
</system.net>
This gives the ability to get information out to partners faster and easier than ever before. This is all good news for partners who need ready information without having to wait for formal editing, vetting, and signoff. However, the downside is of course you'll find the content is bit rougher and there will be some inconsistencies. That's the trade off, but we think it's a good one. Hopefully you'll find this useful.
This is only available to Microsoft Partners.
Thanks,
brett
