Bulk MySite Creation

By -
Because SharePoint will display active links to MySites that might not exist, I was asked to "pre-create" all of the MySites before an upcoming rollout to prevent any confusion from "broken" links. I found a tool at codeplex called TIN that seemed to do what I needed, but it was a little clunky so I rewrote it. The new version is incredibly simple, but it might save somone some time so I thought I'd share. Basic features include:
  • Bulk creation of MySites for entries in the ProfileManager
  • Bulk deletion of MySites for entries in the ProfileManager
  • List profiles from the ProfileManager and whether they have a MySite
  • Robust logging and error handling
  • Save-to-File for log results
  • Multiple threads for long-running operations and smoother screen updates
The source code isn't so beautiful, but here it is. Feel free to make any changes you like, and let us know if it worked for you. Also, if you do make changes and want to share, just send it in and we'll post an update.

Here's a shot of it in action:

Note: Generating a large number of personal sites can take a while, so you may want to run this sometime off-peak.

Comments

Ni said…
Hi,

What the most MySites have you created in one go using your tol? How long does it take?

I'd love to know if you can share your experience in large farm deployment and auto-creation of MySite.

Thank you!
February 27, 2009 at 10:48:00 AM PST
Byron said…
Ni-

I created about 450 MySites in our test environment (virtual servers), and the process took about an hour, if I remember correctly. I'm sure the code could be optimized though.

Byron
February 27, 2009 at 11:09:00 AM PST
Anonymous said…
800 Sites in just under two hours, thanks a bunch you saved my bacon!

-Grimloque
March 11, 2009 at 1:16:00 PM PDT
Anonymous said…
Hello, This tool looks very good, however do you have any user instructions? What address to put where, which files to put on which server etc etc? That would be very useful.
March 23, 2009 at 8:28:00 AM PDT
Post a Comment

Popular posts from this blog

ERROR: Failed to create feature receiver...

By -
I was working on a STSDev project which deployed a feature with a feature receiver. I had the feature working without the FeatureReceiver but as soon as I added the FeatureReceiver related attributes to my <Feature> element I got the following error: Failed to create feature receiver object from assembly "Org.Project.Solution, Version=1.0.0.0, Culture=neutral, PublicKeyToken=c632353d405b3209", type "Org.Project.Solution.MyFeature.FeatureReceiver" for feature 6a9b2358-ea4e-486d-a4e4-4f813c52ce88: System.ArgumentNullException: Value cannot be null. Parameter name: type at System.Activator.CreateInstance(Type type, Boolean nonPublic) at System.Activator.CreateInstance(Type type) at Microsoft.SharePoint.Administration.SPFeatureDefinition.get_ReceiverObject() After much digging around I discovered that STSDEV's Solution config file refers to a namespace as well as the dll. My FeatureReceiver's namespace was not prefixed with the right namespace So just
Read more

Programmatically Update Page Layouts

By -
I updated my page layouts that I deployed as a feature, but found that I could not overwrite the Layout File. The solution was to add a new page layout and then you would have to associate the new layout with every page on your site that used it. Obviously with a site of any size you'd have a lot of manual work to get this done, so doing it programmatically makes for a much better (and thorough) approach. After you've got your new page layouts, you could do something like this (in your event receiver class): public override void FeatureActivated(SPFeatureReceiverProperties properties) { //replace current page layouts with new page layouts on all pages SPWeb web = SPContext.Current.Web; SwapPageLayout(web, "FullWidthContentWithTitleV1.aspx", "FullWidthContentWithTitleV2.aspx"); } private void SwapPageLayout(SPWeb web, string oldPageLayoutName, string newPageLayoutName) { PublishingWeb pubWeb = PublishingWeb.GetPu
Read more

Microsoft Virtualilzation Headaches

By -
As a SharePoint consultant, I am constantly moving from client to client and the best way to develop and test the code, designs and configurations for each client while maintaining complete separation is to virtualize. Since I work for a Microsoft partner, we try to use Microsoft tools and technologies as much as possible, which can be quite frustrating, as you will find out below. I recently started working for a large client with a global presence whose IT policies are well-established, difficult to change and not always up-to-date. In that vein, enter the corporate VPN: it's a web-based signin with a host checker that doesn't support any x64 OS. This prompted me, running Win 7 x64, to try to get a co-worker's Hyper-V Win2k3 x86 MOSS VM and run it in Windows Virtual PC . Seems like a logical thing to do, right? I mean, a Microsoft VHD should work, and be able to be imported by other Microsoft tools, right? Wrong. After spending quite a bit of time trying to attach the VHD
Read more