MySite Redirection and MOSS Service Pack 2
MOSS 2007 SP2 has a bug fix that it seems a number of people don’t want. It enables redirection from the userdisp.aspx page in a local site collection to the MySite portal page even when a portal site connection is not configured.
Thankfully, a quick feature scoped at the farm level can remedy the situation. The following feature disables profile redirection and also hides the “My Site” global navigation link. Note that this feature is scoped at the Farm level, making it applicable to all web applications/site collections within the farm.
The feature
feature.xml
<?xml version="1.0" encoding="utf-8"?>
<Feature Id="6768ca75-6afb-4b70-80e6-7964abf4fb68"
Title="Disable MySites Redirection"
Description="Disables MySites redirection to person.aspx (pre-SP2 behavior) and removes the My Site global navigation link"
Version="12.0.0.0"
Hidden="FALSE"
Scope="Farm"
DefaultResourceFile="core"
xmlns="http://schemas.microsoft.com/sharepoint/">
<ElementManifests>
<ElementManifest Location="elements.xml"/>
</ElementManifests>
</Feature>
elements.xml
<?xml version="1.0" encoding="utf-8" ?>
<Elements xmlns="http://schemas.microsoft.com/sharepoint/">
<Control Id="GlobalSiteLink1" Sequence="50" ControlSrc="" />
<Control Id="ProfileRedirection" Sequence="50" ControlSrc=""/>
</Elements>
Reference
Dirt and Apple In-Ear Headphones
I have a pair of the Apple In-ear Headphones with Remote and Mic and have been quite happy with them to date. However, one problem they have is that any type of dirt/pocket lint/earwax/etc. that makes its way into the mesh covering the speaker will severely dampen the sound; to the point that you will think the headphones are broken.
You’ll be happy to know that they aren’t broken, just dirty (even if they look clean). Apple has a help document titled Apple In-Ear Headphones with Remote and Mic: Getting optimal audio quality that can walk you through restoring your headphones to their original glory.
Try it. It just might work for you.
Event ID error messages 10016 and 10017 are logged in the System log after you install Windows SharePoint Services 3.0
More fun SharePoint errors in the system log. If you’re seeing 10016/17 errors in the Event Log and want to resolve them, perform the steps outlined in KB920783.
Note that these errors are more of a nuisance than anything. The existence of these errors is expected and will not impact the functionality of your farm. That being said, less errors being generated is a “good thing” in my mind.
