RSS Feed   View my LinkedIn profile!   Twitter

Archives

May 2008 (2)
June 2008 (3)
April 2008 (1)
July 2008 (2)
August 2008 (4)
September 2008 (6)
October 2008 (5)
November 2008 (4)
December 2008 (4)
January 2009 (2)
February 2009 (4)
March 2009 (1)
April 2009 (8)
May 2009 (6)
June 2009 (4)
July 2009 (5)
August 2009 (3)
September 2009 (2)
October 2009 (7)
November 2009 (3)
December 2009 (3)
January 2010 (4)
February 2010 (1)

Other Blogs

David McWee's Blog

Links

SA SharePoint Users Group
SharePoint Team Blog
SharePoint Designer Team Blog
Ian Morrish's WSS Demo
Fabian William's Blog

Tag Cloud

Administration, Blogging, Branding, Business Data Catalog, Certification, Development, Maps, Office System, Other, SASUG, Search, Security, SharePoint 2010, SharePoint Conference, SharePoint Designer, SharePoint Events, Social Networking, vNext, Web 2.0, Wikis,

Certifications

Microsoft Certified Technology Specialist
Microsoft Certified Technology Specialist
  • Microsoft Office SharePoint Server 2007
    • Application Development
    • Configuration
  • Microsoft Windows SharePoint Services 3.0
    • Application Development
    • Configuration

Word 2010 Technical Preview and SharePoint 

Tags: Office System, vNext

A warning for users of the Word 2010 Technical Preview and SharePoint. Following guidance from the Microsoft SharePoint Product Team Blog, do not use a "fake proxy" for any kind of workaround.

Specifically, if you encounter the issue where documents, including Word and Excel types, do not open when selected from a web browser, save the file locally before opening in Word 2010 or Excel 2010.

The fake proxy method, as also described in TechNet Forums, will allow you to open documents from a SharePoint site. However, the side effect is a very large security hole. As Lawrence said, "it will reduce the security for default Internet sites by interpreting them as intranet sites instead."

Update October 13th, 2009: I have been testing a modified version of the "fake proxy" method that I am relatively comfortable with. It doesn't work when I connect to my work VPN, but I feel it is safe enough for me at other times. Microsoft Technet Forums User Rhett has this tip:

a better approach: by default IE is set to automatically detect what qualifies as the local intranet zone (LIZ) which seems to be the source of the proxy-workaround "problem". If you uncheck this option by: selecting Local intranet, clicking on Sites and clearing the checkbox "Automatically detect intranet network" public sites no longer show up in the LIZ. Then, to preserve any desired LIZ functionality, you can specify what networks, sites, etc should qualify as the LIZ either by checking the sub-checkboxes or by clicking the Advanced button.

 
Posted by Tom Resing on 29-Sep-09
0 Comments  |  Trackback Url  |  Link to this post | Bookmark this post with:        
 

Comments

Name:
URL:
Email:
Comments: