1. Site Actions
2. More Options
3. Library
4. Dashboards Library

Enter a name for your new library and click Create. Now, go back to Dashboard Designer and try to deploy your dashboard. Once the Deploy To box pops up, you'll see your newly created Dashboard Library that you can deploy your dashboard to.

Today I ran into an odd problem when trying to publish an InfoPath form to a site collection in MOSS 2007. When publishing the form, I got a fairly nondescript error that told me to check the logs for more info. Well, off to the logs I go where I am surprised to see "Activation could not be completed because the InfoPath Forms Services support feature is not present."

Huh? How is InfoPath not present? All my other forms are working just fine. No problems anywhere else I can see. And it's not like InfoPath is like Excel Services or Project Server that I can just disable/enable in Services on Server in CA. Well, after some looking around on my favorite search engine, I found a great post by bphillips76 that said they were able to resolve the problem by simply deactivating and reactivating the "Office SharePoint Server Enterprise" features at both the site collection and the site level.

So, having exhausted all other options I could come up with on my own, I decided to give this simple trick a try and was plesantly surprised to see it worked. Moments later, I was able to activate my form and I was back in business.

Thanks for the tip, bphillips76!
http://bphillips76.spaces.live.com/blog/cns!F9B548E4C21D6166!371.entry

I recently completed a deployment of Office Communications Server 2007 R2 and in my search for many technical articles, I stumbled across the ability to create custom presence in Office Communicator 2007 R2. (Microsoft TechNet article here) Obviously, for most people, myself included, there isn't a real business need for this so I kind of tucked it away in my "This would be kinda cool to try out some day" pile.

Well, eventually I was looking for a distraction and turned to the pile, finding this little nugget and gave it a try....to no avail. It didn't work! Oh well, stick it back in the pile.... I revisited this occasionally here and there over the next couple months, never able to get it working, never caring about it enough to invest any real amount of time in it. Well, tonight I ran across this article while looking up some security information for OCS that answered why this wasn't working.

In OCS 2007 R2, High Security SIP is enabled by default. (awesome!) so, it expects all transmissions to be secure. Well, had tried having the presence.xml file out on a network share, on my local hard drive, and in a SharePoint document library. None of which are considered secure transmissions. However, just slap an 's' at the end of the http for my SharePoint document library and voila! My custom presence works!

So, moral of the story is, if you want to use custom presence in OCS 2007 R2 and you haven't disabled secure SIP (and hopefully you haven't....) then you have to store the file in an https enabled location. So, something like, https://server.domain.com/folder/presence.xml

Now, I wonder how long it will take before someone notices that my presence is "out of my mind, be back later"...

I was running into this problem sometimes when doing a P2V conversion in Hyper-V. The conversion would get to exactly 40% and fail. Every time. Well, after a little searching around, it turned out to be a common problem with the VSS writer on the source machine that is getting converted. Thankfully, the fix is simple and doesn't even require a reboot.

Error (13243)
The snapshot creation failed because the VSS writer {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f} on source machine MACHINENAME did not respond within the expeted time interval.
(Internal error code: 0x809933BB)
Recommended Action:
Ensure that VSS writer is functioning properly and then try the operation again. 4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f is the Shadow Copy Optimization Writer

You may also see an event ID 8193 in the Application Event Log on the source machine.

The Fix:

1. Open regedit and go to HKLM\Software\Microsoft\Windows NT\CurrentVersion\ProfileList
2. Under the ProfileList key, delete any subkey that has ".bak" on the end.

Done! You can now complete your P2V conversion.

We are in the process of migrating our sited from WSS to MOSS and found that one of the biggest time cost comes mainly from dealing with fixing broken links since our new MOSS farm has a different address than our current WSS farm. This presented an interesting problem. How do we make sure that the transition is as seamless as possible without re-writing hundreds or even thousands of links.

Links inside of SharePoint are easy since we've long since taught our users to use relative paths. However many of our users have bookmarks or home pages set to the old location and there are countless hundreds of saved emails and corporate documents that refer to the previous site. Well, Microsoft IIS URL Rewrite to the rescue!

This neat little free tool has saved us TONS of time in our migration plan by allowing us to have IIS redirect users automatically to the new location but on a department-by-department basis. In addition, it takes the parameters after the site location and passes them to the new location as well. So, if someone goes to http://wss.company.com/hr/vacationrequest.doc they are automatically redirected to http://moss.company.com/hr/vacationrequest.doc meaning that nobody has to update their links and nobody has to call helpdesk wondering why their links don't work anymore. Since once the migration is complete we plan to give the old name to the new site anyway (and keep the new name too) this makes for an excellent solution for us that means we spend absolutely ZERO time fixing broken links.

Pretty sweet, huh? So, how does it work?

First, install the IIS URL Rewriter which you can get on the iis.net site (prominant link in the upper-right corner) or you can go straight to the source and get it here: http://www.microsoft.com/web/spotlight/urlrewriter/?WT.mc_id=aff-web-corp-spotmar_iisnet2

The nice thing is that the install is non-disruptive and does not require a system restart. Then, you edit the web.config of the web applications on your WSS servers that you want to do redirects on, adding the following lines inside of the section:



Notice the match url section where the different subsites are listed. So, in this case, http://wss.company.com/credit and http://wss.company.com/finance and http://wss.company.com/hr will all be redirected to their moss.company.com equivalent whereas other sites like http://wss.company.com/informationsystems and http://wss.company.com/facilities will NOT be redirected.

As you want to add more sites to the migrated list, you just add more names to the match url section with each site separated by a pipe symbol. So, for instance, to add the informationsystems site to the list of redirected sites, you would change the match url section to look like this:



Note: the IIS URL Rewriter must be installed on all of your Web Front Ends and the web.config changes will need to be made on all Web Front Ends as well.