Sharepoint Gadget: 2009

fredag den 14. august 2009

Send mail i PowerShell

#####################################
function SendMail([string]$TextToSend)
{
$filename = "filename.txt"
$smtpServer = "SmtpServerName"

$msg = new-object Net.Mail.MailMessage
$att = new-object Net.Mail.Attachment($filename)
$smtp = new-object Net.Mail.SmtpClient($smtpServer)

[string]$tempFrom = $env:computername + ' <' + $env:computername + "@" + $env:userdomain + ".COM>"
$tempFrom $msg.From = $tempFrom
$msg.To.Add("sendto@domain.com")
$msg.Subject = "Subject"
$msg.Body = $TextToSend$msg.Attachments.Add($att)

$smtp.Send($msg)
$msg.dispose()
}
#####################################

onsdag den 5. august 2009

Sharepoint 2010 Links

Redirect SharePoint Site to New Location

1. Add a Content Editor Web Part to the Main Page of the site.
2. Modify the Web Part and click on Source Editor.
3. Paste in the following code while changing the URLs to match your target.
<HTML>
<HEAD>
<SCRIPT language="JavaScript">

</SCRIPT>
</HEAD>
<body>
Redirecting you to the new location. If you are not redirected, click <a href="http://sharepoint">HERE.</a>
</body>
</html>

4. I set the redirect time to 0, but you can set it higher if you like. 1 sec = 1000, 2 sec = 2000, etc.
5. Save the code changes.

The fun part of this solution is the fact that the code tries to load no matter what view you are in (i.e. Standard view, Edit Page, etc). So, if you have to make changes to the code you have to let the page load but then time a press of the ESC key to keep the Javascript from loading each time.

tirsdag den 26. maj 2009

Sharepoint Install Script

Her er en god artikel om sharepoint install script: http://stsadm.blogspot.com/2008/03/sample-install-script.html

Artikel om STSADM og PowerShell komandoer: http://stsadm.blogspot.com/2007/08/stsadm-commands_09.html

mandag den 2. marts 2009

InfoPath - Get the current user without writing code

With InfoPath opened go to Tools > Data Connections, and click 'add...' to add a new data connection to the form. This opens up the Data Connection Wizard.
We want to receive data from the WS about the current user, so choose receive data' and click next.
Our data source is a WS so choose 'Web Service' and next.
Now you will have to point the wizard to the WS. Type an address similar to this: http://ServerName/_vti_bin/UserProfileService.asmx and click next.
Here you get a list of all methods for that WS, choose GetUserProfileByName and click next.
In this screen you can specify what parameters are sent to the method, we are relying on the method's ability to return the current user name if no value is passed to it, so we will leave this as is (no value is passed to the method) and click next.
Click next and make sure 'Automatically retrieve data when form is opened' is checked.
Finish the wizard.

The GetProfileByName method returns a PropertyData array. You can think of it as a repeating table of name and value pairs. So Now that you have a data connection that can get the current users, you can use it values. In this example I will show the user's first name in a textbox.

Add a textbox to the form.
Go to the first textbox's properties (double click it).
In the 'Default Value' part, click the 'fx' button next to the 'Value' field. this opens up the formula builder dialog.
Click 'Insert field or group'.
In the data sources drop down, choose the GetUserProfileByName data source.
Expand all groups under the 'dataFields' group, and choose the 'value' field. Don't click OK yet!
With data 'value' field selected, click the 'Filter Data...' button and 'Add...'.
In the first drop down (value) select 'Select a field or group...' and choose the 'Name' field under the 'PropertyData' group.
Leave the middle drop down as is ('is equal to') and in the last drop down choose 'type a text...'.
This is the part where you specify which property to put in the textbox. As we said the method returns multiple properties about the user. For this textbox we want to put the user's first name in, so type 'FirstName' (this is case sensitive!). I have included the property list you can use here (just below), so if you want some other property, just type its name instead.
That's it, all we have to do is to confirm everything so Click 'OK' for every open dialog box until you are back in the design mode.
click 'Preview' and see the wonder!
If you want more details repeat steps 1-11 and enter different property names in step 10.

Finally, as I Promised, here is the complete list of default profile properties get returned by the userprofileservice. I think they are pretty self explained:
UserProfile_GUID
AccountName
FirstName
LastName
PreferredName
WorkPhone
Office
Department
Title
Manager
AboutMe
PersonalSpace
PictureURL
UserName
QuickLinks
WebSite
PublicSiteRedirect
SPS-Dotted-line
SPS-Peers
SPS-Responsibility
SPS-Skills
SPS-PastProjects
SPS-Interests
SPS-School
SPS-SipAddress
SPS-Birthday
SPS-MySiteUpgrade
SPS-DontSuggestList
SPS-ProxyAddresses
SPS-HireDate
SPS-LastColleagueAdded
SPS-OWAUrl
SPS-ResourceAccountName
SPS-MasterAccountName
Assistant
WorkEmail
CellPhone
Fax
HomePhone

mandag den 16. februar 2009

Simplifying SharePoint Server Roles

There is so much unnecessary confusion over server roles in SharePoint. Let me take the opportunity to simplify these roles, so you can see it is much much simpler than it is made out to be or even that original design.

SharePoint roles are really a description of what services are running on the server, and because of the past we've overcomplicated the way we think about servers roles, app servers, tiers, topologies, and farms.

The SharePoint Roles you've heard

Web Front End - Every farm has one of these. It's where IIS is
Query
Index
Calc
App server - another name for all the goo that isn't the WFE
Central Admin/SSP Admin
Infopath - NOT A ROLE (This can NEVER be taken off the web front end)
SQL - Not a SharePoint role and should not contain SharePoint code unless it's an all in one.

There are 2 server roles for 97% of the SharePoint World.

WFE - WFE/Query/Calc/Central Admin/SSP Admin
Index (the most common offloaded server role) (Note: Don't get carried away with what I'm saying. There is a Query/Index Gotcha.)

(Another 3% should know the all in one where WFE and all that jazz are combined with the Index.)

Why would I say you really only need to know about 2 roles?

First the Query role is the lightest role and doesn't really need to be offloaded. If it does you really are better off with an SSP farm which is focused on Search which would turn that Query server back into a WFE/Query box.

The Calc role is oversold. Excel services is cool, but no one is really able to stress it to the part where it needs separate servers. If you find a case, it's a .01% case, completely uncommon. MS IT had to reallocate and they

Infopath - not a server role, there was a license for forms server, that was never really used. Forget you ever heard about it. It's a dead end.

Central Admin/SSP Admin - I've heard people putting this on it's own server, totally unnecessary you don't have to put it on every server in the farm, but you don't have to buy a server for this purpose either.

Target - you can use existing roles for doing that.

What about MASSIVE farms?

In massive farms you have two choices. You put WFE/Query together and have a bunch of em, or you specialize search into it's own farm, maybe even two search farms, but you don't ever really need to offload query. Don't let an architect push you into having 2 WFE, 2 Query, 1 Index, 2 SQL. You are better off with 4 WFE/Query and 1 Index and 2 SQL or a Content farm of 2 WFE/Query and 2 SQL and a separate Search farm 2 WFE/Query 1 Index box and Shared SQL backend. Make sense?

Does this turn your world upside down or is it game changing?

Need an Exception?

A special customer that has a requirement for no data of any type in their public DMZ. They HAVE to have their data in the 2nd tier. Hence they put the WFE ONLY (remember that option no one uses) box in the pub DMZ and the 2 Query and Index boxes and SQL in their APP DMZ. They likely could have configured ISA publishing rules or used IAGin the pub DMZ and put the 3 SharePoint boxes in the App DMZ, but that's a design decision.

SharePoint Server Topology - Server Roles and Services on Server

All Services on Server (WFE/Query/Calc/Index) - Choose "Single Server or Web Server for small server farms" start the things it tells you to, and click on the things that look like links to configure them. In "Office SharePoint Server Search" you'll be checking both boxes since you're query and index are on this box. (Hint: Don't forget about SSP for further configration) You might not be using the document conversions, most likely you're not. These are optional.

WFE/Query/Calc - Choose "Web Server for medium server farms" and run the recommended services, and be sure to click on everything that is a link as in Office SharePoint Server Search. Be sure to check "Use this server for serving search queries." Doc Conversions is optional. (This role is very common in medium or high availability farms)

WFE - Windows SharePoint Services Web Application. Both of the document conversion services are "nice to have" if you use them in your SharePoint Standard or Enterprise publishing scenarios where you are converting your word to HTML for publishing. It's not common that these are used. During install you can choose WFE only, understand what you're doing, but this will limit the services you'll see in services on server.

Forms Rendering - I'm listing this here, since a lot of people think of this as a server role. This is automatically always on the WFE. You can't offload this.

Excel Calculation - Choose Excel Calculation, this service should be running. Configuration for this is in the SSP. It's a MOSS Enterprise configuration.

Query - In Services on Server choose "Search Indexing" then actually click, yes click on the text (under Service) "Office SharePoint Server Search." You'll see two options. Make sure "Use this server for indexing content" is unchecked and "Use this server for serving search queries" is checked.

By the way, if you ever decide to build a query server, I would nearly always recommend considering an SSP farm. Why? Cause if you're offloading query because you have that many search requests, then you'll need at least 2 Query servers and you'll have already offloaded your index, so that's 3 servers that could easily be load balanced and create a decent SSP farm.

Index - In Services on Server choose "Search Indexing" then actually click, yes click on the text (under Service) "Office SharePoint Server Search." You'll see two options. Make sure "Use this server for indexing content" is checked and "Use this server for serving search queries" is unchecked. You do need to add the Windows SharePoint Services search you don't need to go with the "every 5 minutes" by default, daily is sufficient. You will later create your rules for your content sources anyway. The service accounts will be configured when you configure indexing.

This is the first server I offload for performance. I do recommend making the index role also a WFE, so I wouldn't usually recommend this just be an index server unless it's in the SSP farm (a farm by itself with no content).

Index/WFE and WFE out of load balancing (Target) - here's where you could pick custom then start the Windows SharePoint Services Web Application and the Office SharePoint Server Search and be sure to check only "Use this server for indexing content." I did a whole post on this in a post called "Use a dedicated web front end for Indexing." A target server might be a WFE that's out of load balancing that only the index servers in your environment know about (host file entries on the index servers). The other configurational you'll see is index servers that have WFE components that are configured to index themselves and hence have the WFE services (Windows SharePoint Services Web Application) and also not in load balancing. There is an option to configure the "use a dedicated WFE on the bottom of the Index server configuration page (Office SharePoint Server Search Configuration page), don't use this if you have multiple IPs or multiple NICs. It is very possible it will choose the wrong IP and better that you configure this in hosts where you manage what is in.

WFE/index/Query and WFE/Query - If you ever have index and query on the same server and plan on doing another server with Query.... or are thinking about doing something like this please refer to my post about the Index/Query Gotcha. The Index server will NOT propegate if the Query components are enabled on the farm. In a sense this means if both boxes are checked (Query (search requests) and Index (crawling)) in "Office SharePoint Server Search" it will NOT propegate the index to any other query server. It assumes there is not another query box no matter how many you have.

Want to force changes after a role change of a server where you need to push down the web apps to a new box?

stsadm.exe -o execadmsvcjobs

This stsadm command will force timer jobs to execute.