Tag Info

Hot answers tagged

5

Co-authoring will be revolutionary I reckon, it's in my 'top 5 drivers for clients to upgrade to 2010'. In answer to your questions: SharePoint Foundation is fine. Yes web and rich client (i.e. Word 2010) both support co-authoring, the experience is basically the same from what I've seen. Probably, but remember that whoever hosts the functionality also ...


3

The AutoSPInstaller (http://autospinstaller.codeplex.com/) was actually creating self-signed certificates on the server that the WAC did not trust. So we had to manually create the certs and a CA so that the trust would work properly. This corrected our issue.


3

The easiest way I have found is to use the [SPWebApplication.GrantAccessToProcessIdentity][1] method. It grants the specified user account access to the process identity and provides full control of the SharePoint Web Application. Office Web Apps can use this to access the content databases as the SharePoint Web Application's process identity, which already ...


3

I created a blog post about this today: Create a new document using Office Web Apps. ID is the URL to the document template that is associated with the content type. Ex.: http:// www.yourdomain.com/TeamSite/template.docx` SaveLocation is the location to the document library where the document needs to be saved. Ex: &SaveLocation=http:// ...


3

If you run your farm on least privilege settings, you can get the above error. Be aware of the security demand for the Word Viewing Service are quite high: When you create a new application pool, you can specify a security account that is used by the application pool to be either a predefined Network Service account or a managed account. The account ...


3

As a very general rule, and I hope I am not doing it an injustice, the Office Web Apps are great for viewing documents, but the editing experience will fall well short of the full client experience. If your end users are editing documents I would recommend going with the full Office client. If they are just viewing, OWA is probably good enough. If your ...


3

You do not have access to the DIP in Office Web Apps. Since you're using the web UI already it's easy to go the the item in the library and change it's properties there. If you need more advanced DIP's (for instance built with InfoPath) then you need to modify the edit, new and view forms of the page to get the "same" experience as in the full fledged Office ...


2

It's actually possible to rename/move a file, but you must do it programmatically using client object model or server object model - File.MoveTo Here is an ugly example (didn't test it, might be some typo): using Microsoft.SharePoint.Client; .... using(var ctx = new ClientContext("http://yoursharepoint/web_containing_library/")) { var lib = ...


2

I don't see how this would be possible as changing the file type from DOC to DOCX would create a new item...i.e. you can't change the name of a SPFile object. Your best bet is to probably write some code or a script to convert the docs as you migrate them to a new library along with their metadata and then retire the original doclib.


2

When slip streaming, ALL (SP, CU) your updates go into the updates folder in the installation source of your application. The language packs go into the language updates folder. When you install from the source, everything in the updates folder gets processed. Here is post by Ron Grzywacz on MSDN regarding this topic Service packs and LP slip-streaming. ...


2

I found the best programmatic solution: The SPUtility.MapToServerFileRedirect function. In the C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\XML directory are a bunch of ServerFiles XML files that tell SharePoint how to redirect certain types of files, etc. Office Web Apps uses this to redirect links to Office files to ...


2

We raised the issue with Microsoft Support and apparently it's a bug. Will know more soon. In the meantime, the fix is to disable PDF's from being rendered in OWA: Get-SPWOPIBinding –Application "WordPDF" | Remove-SPWOPIBinding -Confirm:$false Control whether PDFs open in Word Web App or the default PDF reader ...


2

Yes and No. If a user can read a document they can download and edit it if they so desire. They just can't edit the document as it exists in your list. This would include the Read and Restricted Read permissions (http://technet.microsoft.com/en-us/library/cc721640(v=office.14).aspx). You can, through Information Rights Management ...


2

As per your requirement you should go with the Office Web Apps. I will also works fine with Sharepoint 2010 Foundation and you can also download it from volume licensing program of Microsoft. Here is an post that shows system requirements of Web Apps. http://technet.microsoft.com/en-us/library/ff431682.aspx And these are the steps to install and configure ...


1

i am assuming you have SharePoint 2013, You need the Office web Apps installed and configure in order to open the word/office documents in Browser. Once installed, office documents will be opened in web apps by default - you can change it by activating site collection feature called "Open Documents in Client Applications by Default". After this setup, users ...


1

I did test this the other day, I had to run a PowerShell-script to get it deactivated right. $webAppsFeatureId = $(Get-SPFeature -limit all | where {$_.displayname -eq "OfficeWebApps"}).Id $singleSiteCollection = Get-SPSite -Identity http://<site_name> Disable-SPFeature $webAppsFeatureId -Url $singleSiteCollection.URL It did throw an error when I ...


1

I can offer to you a potential workaround. Maybe it's not best practice but may be acceptable in your environment. You can set trust mode in web application config to Full: <trust level="Full" originUrl="" /> It hepled me in similar situation (the same "That assembly does not allow partially trusted callers" exception) once. It's turn off some code ...


1

Office 365 exposes the Exchange Web Services in order to allow you to manage things like Calendar items. In order to use these services, you will need to do the following: Build a client application (in your favorite language) that authenticates with your Office 365 instance using OAuth. Have your client application use the Exchange Web Services to create ...


1

Office Web Applications does not require Office to be installed on the client machines (that's the point). As far as licensing, an Office 2010 license would not cover an Office Web App 2013 license. If you have SA or other upgrade rights, your Office 2010 licenses could be upgraded to 2013. I would contact your sales channel for more specific details on ...


1

Apparently this is a known issue. I've got two possible solutions for you. 1) Enable the "Open documents in client applications by default" site collection feature (from MSDN): http://social.msdn.microsoft.com/Forums/en/sharepointgeneralprevious/thread/90d251c3-43d4-4b05-b87c-7c25bb32a782 2) Modify the XSL to open the document in a new browser window ...


1

I never tried it myself but after a bit of research I can say Yes you can look at links below, publish-your-access-database-to-sharepoint Video for publishing to sharepoint using Access EDIT Since your updating Database outside sharepoint using VBA module, so it shouldn't interrupt sharepoint publishing it, you might come across few issues while ...


1

You'll need to use the Open XML SDK 2.0 from Microsoft to programatically create your Word document. Follow this link for more information: http://msdn.microsoft.com/en-us/library/office/bb448854.aspx You'll need to let us know how you want to initiate the creation of the Word document so we can recommend where to start from a Sharepoint point of view.


1

You cannot password protect at the page level in OneNote. You can only password protect a section or notebook. Also remember that audio recordings cannot be password protected, and protected sections will not appear in search results. OneNote can also be secured at the Notebook level using regular SharePoint permissions.


1

Maybe the problem is the DC role on the same machine. Try this: http://blogs.msdn.com/b/scicoria/archive/2011/04/14/getting-office-web-apps-to-run-on-a-domain-controller-appserverhost-exe.aspx


1

If I understand you correctly, your client wants to use OpenOffice documents with Microsoft Office on the Windows XP/Vista/7 client computer or with Microsoft Office Web Applications. To make SharePoint recognize OpenOffice documents you could modify the docicon.xml file (see http://msdn.microsoft.com/en-us/library/ms463701.aspx) to force OpenOffice ...


1

Here's one way I've been able to "convert" a DOC to DOCX, although it's all manual, is to Open the doclib in Explorer view/open in Explorer Open the file in question (check-out if needed) "Convert the file" Save the file locally Rename the file extension in Explorer view (if you have it opened in Word, SP will complain that the file is locked) Upload the ...


1

In my experience, order of operation is extremely important during an install and even more so when you start adding in other services like Office Web Applications or Project Server. Uninstalling SharePoint or any of those services are possible, but it is likely impossible to get back to the right starting point without just starting again with the base OS. ...


1

I would suggest to read this article: http://technet.microsoft.com/en-us/library/ff431682.aspx Especially scenarios which require client application. If you find your users into those scenarios, the default option could be opening in client app. In browser could be a nice fall back.


1

After a quick google, found this, might be of some help: http://www.softwaregeek.com/download/pdfapps_convert_pdf_to_html.html Previous post, disregard but I do point out some slightly related other tools out there: I know Bamboo do something along these lines here: http://store.bamboosolutions.com/ps-16-5-office-to-pdf-conversion-business-component.aspx ...



Only top voted, non community-wiki answers of a minimum length are eligible