Einbinden von YouTube Videos auf SharePoint 2010 Seiten (via SharePoint and relevant Technologies)

Danke für den Post – ich nutze sonst eine andere Möglichkeit (Inhaltseditor mit .txt File) .. dieser Workaround hier ist eleganter.

Einbinden von YouTube Videos auf SharePoint 2010 Seiten Vor kurzem kam die Frage auf, wie man am besten YouTube Videos in SharePoint Seiten einbindet (embedded). Out-of-the-Box gibt es dazu keine einfache Funktionalität. Bloßes Copy & Paste in den HTML Editor des Inhalts-Editor-Webparts führen zu keinem Erfolg, da der Editor den eingefügten Code nochmals modifiziert/encodiert (XHTML). Ich habe nun zwei Lösungen gefunden: man benutzt den HTML Form Web Part und bindet den auf der YouTube abgerufenen … Read More

via SharePoint and relevant Technologies

Migration strategies and Step by Step – Migrating from MOSS 2007 to SharePoint 2010 (via Mrin’s Blog)

Thx 4 this post …

Migration strategies and Step by Step – Migrating from MOSS 2007 to SharePoint 2010 I was reading a post from Apoorv Durga, about migration strategies on software development. It is a fantastic post. It is really true that many of the migration falls due to poor planning or sometime negligence towards the basic. SharePoint 2010 lunched yesterday and a very interesting product from Microsoft. Many organisations already considering migrate from the existing version of MOSS 2007 to SP 2010. Organisations need to be very careful as … Read More

via Mrin’s Blog

SharePoint 2010 Service Accounts

Da grad die Frage bzgl. der Service Account´s in SP2010 an mich herangetragen wurde hier eine kurze Aufstellung zu den benötigten Accounts mit Berechtigungen als Zusammenfassung aus dem Todd Klindt´s Admin Blog:

Source: Todd Klindt´s Admin Blog

Author: Todd Klindt

Account name

Role

Domain rights

Local SharePoint Server rights needed

SQL rights needed

sp_install Used to install SharePoint binaries. Domain User Local administrator on all SharePoint boxes dbcreator and securityadmin SQL roles
sp_farm Farm account. Used for Windows Timer Service, Central Admin and User Profile serve Domain User Local Admin during UPS provisioning, log on locally right None
sp_webapp App pool id for content web apps Domain User None None
sp_serviceapps Service app pool id Domain User None None, unless using Office Web Apps. Them must give access to content databases manually
sp_search Search process id Domain User None None
sp_content Account used to crawl content Domain User None None
sp_userprofile1 Account used by the User Profile services to access Active Directory Must have Replicating Change permissions to AD. Must be given in BOTH ADUC and ADSIEDIT. If domain is Windows 2003 or early, must also be a member of the „Pre-Windows 2000“ built-in group. None None
sp_superuser2 Cache account Domain User Web application Policy Full Control

Web application super account setting

None
sp_superreader2 Cache account Domain User Web application Policy Full read

Web application super reader account setting

None

 

1) See http://technet.microsoft.com/en-us/library/ee721049.aspx and http://www.harbar.net/articles/sp2010ups.aspx

2) http://www.sharepointchick.com/archive/2010/10/06/resolving-the-super-user-account-utilized-by-the-cache-is.aspx

Daneben ist dies hier eine hilfreiche Quelle: http://technet.microsoft.com/en-us/library/ee662513.aspx

SharePoint 2010 Datenbanken – SQL Server Backup und Recovery mit Quest Recovery Manager

Hach, ich liebe das Internet! .. Da ich heute auf der Agenda das Thema SQL Server Backup für SharePoint zu stehen habe (als Einweisung der neuen Kollegen in die Betriebsthematik) freue ich mich umso mehr über den Artikel von Todd Klindt in seinem SharePoint Admin Blog!

Der Artikel beschreibt kurz und knapp die Einrichtung eines Wartungsplans im SQL Server 2008 über den Wizard bei gleichzeitiger Integritätsprüfung. Der Kommentar „Nice start .. but .. “ ist darüber hinaus hilfreich da ich bei allen Kunden und auch intern die Transaktionsprotokolle mit sichere. Auf Basis dieser Backups kann ein effektives Backup & Recovery Management im Rahmen eines Desaster Recovery Plans mit Quest Recovery Manager for SharePoint realisiert werden. Mit der Möglichkeit die SQL Server eigenen Backups zu nutzen und trotzdem bei einer Wiederherstellung alle Informationen zurückholen zu können ist das Tool im Preis/Leistungsverhältnis die erste Wahl für mich!. So, aber jetzt zum Artikel:

Source: Todd Klindt´s Admin Blog / Author: Todd Klindt

by  Todd O. Klindt on 1/16/2011 7:29 PM

Category: SharePoint 2007SharePoint 2010Sharepoint

I do a lot of SharePoint installs and one question I always ask before the engagement is over is „How are you going to back this all up?“ More often than I’m comfortable with, the answer is, „I don’t know.“ In those cases I tell them the very, very least they can do is to do database level backups with SQL. Many times I hear silence on the other end of the phone. Seems many SharePoint folks just aren’t comfortable in SQL and aren’t sure how to do backups. I decided to write up this quick walk through to send to folks to get them started. I hate it when people lose SharePoint data.

To do this you’ll need to an account that is a serveradmin on the SQL server and you’ll need to log in as that account and start SQL Server Management Studio (SSMS). This walk through was done on SQL 2008 R2, but it’s very similar on SQL 2008 and SQL 2005, so if you’re using either of those you should be able to follow along. Under Management right click on „Maintenance Plans“ and click „Maintenance Plan Wizard.“


Give the plan a name, like „Backup Database.“ You can also schedule the backups to run on this screen by clicking „Change…“


Next we’ll pick the things our maintenance plan will do We’ll check „Back Up Database (Full)“ as well as „Check Database Integrity.“ Corrupt databases back up just as well as uncorrupted databases. It’s good to run an integrity check just to make sure you’re backing up something that will actually help you if you need to do a restore.


Next choose the order the two jobs will run in. We’ll leave this at the defaults.


Next we pick which databases the integrity check will run against. Choose „All databases.“


Next we get to configure the backups. We are also going to back up „All databases“ to make sure we get everything. I also leave the defaults that create one file per database but do not create a folder for each backup. If your SKU of SQL supports backup compression you can also enable it here. I highly recommend it if it’s available to you.


Tada! The Maintenance Plan is created. Of course it needs to run before it does us any good. To run a Maintenance Plan right click on it and click Execute.


If this is the first time you’ve tried to run a Maintenance Plan on your SQL instance you might get the following error:


Just like the error says, this is because the SQL Server Agent is not started. To fix that, right click on the SQL Server Agent and click Start.


Now try to execute your Maintenance Plan again. It should work. Your next question should be, „This is freakin‘ cool! How do I schedule this?“ I’m glad you asked. To add a schedule right click on the Maintenance Plan and click Modify. At the top of the modify screen click the calendar to the right of the line that says, „Not scheduled (On Demand)“.


This will bring up a scheduling dialog that will let you schedule when your Maintenance Plan will run.

Thanks for reading this far, no go out there and back up some database.

tk

Comments

Nice start … but

 

A couple of points that I would add;
– include another job for backing up of the Transaction Log.  If no one is able to provide direction, a good general timeframe is Daily for Full Backup and Hourly for Transaction Log Backup
– add a cleanup job otherwise you’re going to run out space … especially with SharePoint.  Retain as long as you can, but allow for growth.
– I prefer to use the „Create a sub-dir for each database“.  With all of the SharePoint DB’s, Transaction Logs. etc, it can get pretty messy
– Change the path that the backups are made to different to where the databases are stored (if possible)
– Notification is also a good idea … but beyond the scope of a comment!

on 1/16/2011 8:35 PM

Need to backup Logs after full backup

 

Hi,
you also need to backup logs as well if its SQL 2008/R2.
Other wise your log files will grow up like a hell.

on 1/16/2011 8:36 PM

Re: Nice start … but

 

Thanks for the comment.

– I purposely avoided the topic of Recovery Models.
– Probably not a bad idea
– Cool
– It is a good idea to save the backups to a different drive or machine. I should have mentioned that.
– I didn’t want to cover operators either, so I ignored notifications.

tk

Todd O. Klindt on 1/16/2011 9:09 PM

Re: Need to backup Logs after full backup

 

I didn’t want to cover transaction logs or recovery models in this blog post. Maybe I’ll cover it in a later one.

tk

Todd O. Klindt on 1/16/2011 9:11 PM

 

SharePoint Fehleranalyse und -behebung – Wie gehe ich am besten vor …

Da die Einarbeitung von 2 neuen Kollegen in meine SharePoint Projekte das Thema dieser Woche war und wir gleichzeitig neben den Arbeiten zur Projektrealisierung auch Aspekte des Serverbetriebes, der Administration sowie der Fehlersuche und -behebung behandelt haben, kommt der untenstehende Artikel von Sahil Malik (thx 4 the article) auf code-magazin.com gerade recht!

Source: code-magazine.com

Author: Sahil Malik

The 12-Step Recovery Program from a SharePoint Error

Hello, my name is Sahil, and I am a worsening SharePointoholic. SharePoint is built on ASP.NET 2.0 – pretty much like human beings are made up of carbon and water. There is a lot in SharePoint that isn’t in ASP.NET. Not only is SharePoint a complex ASP.NET 2.0 application, it also has numerous concepts for things such as profiles, role providers, authorization etc., that are different from ASP.NET.

In addition, underneath the hood there is lots of COM, legacy database models, technologies that have come and gone, that are in some way, shape or form being used inside the depths of SharePoint. In addition, SharePoint uses the latest technologies such as WF, WCF and claims based authentication, which forms the bones and flesh of this amazing product.

The good news here is that all of this put together makes it the ultimate Microsoft product – something that benefits from everything Microsoft does. The bad news, of course, is that diagnosing an error sometimes is not as simple as looking at exception text and searching for it on Bing.com.

In this article, I will share with you my 12-step process that has so far helped me diagnose every SharePoint error I’ve run into. If you have additional diagnosis tricks, please send them to me via email.

The three C’s: The three C’s stand for callstack, compilation, and customErrors. These are three attributes you can change to true, @debug=true, and @mode=Off, that allow you to view an exception text right on the web page.

Developer Dashboard: The Developer Dashboard is a new addition in SharePoint 2010. It gives you a convenient way to view the details of any particular page rendering down to the database and WCF calls complete with exception traces, warnings, and time durations. You can enable Developer Dashboard by using the following command:

stsadm -o setproperty -pn developer-dashboard -pv OnDemand

Event Viewer: The Event Viewer in Windows is an amazing insight into the innards of SharePoint. Some errors will surface only within the Event Viewer. Anecdotally I can tell you that many WCF errors, including those for out-of-the-box WCF services such as those for claims based authentication, seem to merrily log their errors in the Windows Event Log.

ULS Viewer: ULS is the unified logging service – which in itself has seen enhancements as compared to the SharePoint 2007 version. You can download this tool from http://code.msdn.microsoft.com/ulsviewer, which lets you view ULS errors at runtime as they occur, and filter using CorrelationIDs.

CorrelationIDs: Technically this is a part of the ULS log, but not really. Classically reading ULS logs has been tough. Those multiple log files are quite wide, so you have to scroll around and sift through many such log files, line breaks, etc., to find the error trace you are looking for. Starting with SharePoint 2010, Microsoft gives you a unique ID, a GUID, for each error that occurs. This is the CorrelationID. You can use CorrelationIDs to put together the full error message as it occurred, even across multiple machines. And this can be done easily using the ULS Viewer that I mentioned above.

Fiddler: You can download Fiddler from http://www.fiddlertool.com. Fiddler introduces a proxy for your browser and starts to sniff all local http traffic going back and forth from your machine. It is an invaluable tool for debugging REST-based APIs and client object model calls. Starting with Internet Explorer 9, you have a network monitor built right into your browser, or you can also use Firebug, Chrome extensions, etc.

Internet Explorer extensions: Open any SharePoint page, and hit F12. This will bring up the developer extensions for Internet Explorer. Using this you can very easily run small JavaScript commands, change CSS on the fly, and change the DOM of the page entirely if you wish, or even step through JavaScript. In crafting up modern day rich client side applications, I have found this utility to be extremely valuable.

IIS 7 trace and logs: Managed code is awesome. And as more and more Microsoft products are whole heartedly adopting the managed code bandwagon, they are reaping amazing benefits from it. One such product is IIS7. With its integrated pipeline and error logging and tracing, it literally tells you what line an exception occurred at – along with a full stack trace, and http error codes. I can’t tell you how much I have found this useful in diagnosing really hard to discover HTTP 401s (HTTP Unauthorized), especially when diagnosing search, reporting services, etc. Security is a good thing, but it can also be a real pain sometimes.

WCF Error Tracing: System.ServiceModel comes with a diagnostics element that lets you create listeners to error messages. As messages go across a WCF boundary, errors, or even non-errors, can be logged into a store of your choice. The simplest, of course, is an XML file, which is right out of the box in .NET.

.NET Reflector Pro: .NET Reflector is this amazing product that lets you decompile any non-obfuscated .NET assembly and peek into its source code. .NET Reflector Pro takes it to a whole other level – it lets you debug and step through that generated code – as if it was your own code. Amazing! This is extremely useful, and is demonstrated in this video – http://blah.winsmarts.com/2010-9-Ninja_SharePoint_2010_Debugging_with_NET_Reflector_Pro.aspx

Ninja debugging skills: No, ninjas do not need debugging. What I mean is that in working with a big product that you didn’t write, such as SharePoint, it helps to develop some advanced debugging skills. I describe some of these black belt techniques in this article here – http://www.code-magazine.com/Article.aspx?quickid=0907041.

Call in sick: I haven’t ever had to use this advanced technique, but if all else fails, call in sick, blame it on a coworker, and take the day off. It’s amazing how much some chillaxing can help.

Summary

„Starting with SharePoint 2010, Microsoft gives you a unique ID, a GUID for each error that occurs. This is the CorrelationID. You can use CorrelationIDs, to put together the full error message as it occurred across multiple machines even. And this can be done easily using ULSViewer.“

This list is not complete. SharePoint is a complex product, and in working with it I continue to discover new tricks and new techniques all the time. I hope you found these techniques useful. If you have more to contribute, I would love to hear from you at http://www.winsmarts.com.

 

Until next time, Happy SharePointing.