How To: Strange but True – If you use a permanent marker on a White Board…a simple Fix to get it Off
So i would not believe it if I didn’t see it myself. Here is what I did. [Disclaimer] I wasn’t the one who put Permanent Marker and Dry Erase Marker in the same place.🙂
I am about to draw a line on the board to separate an are for “Parking Lot” information. I took a permanent marker “unbeknownst to me” and drew a 1 meter line from top to bottom. Only after I hear the crys of OMG, that is a permanent marker did i stop… but alas too late.
FIX – “Credited to one of the Sessions Participants…”
- Take a Dry Erase Marker
- Use the Dry Erase marker and cover, really cover, the entry made by the Permanent Marker, be generous in your application but not over kill
- Use the Dry Eraser to erase your entry… Voila, the Dry Erase Marker and Permanent Marker entry are gone.
- It really works…
Maybe i can get the Sham-Wow Guy to market this for me…
Service Pack 2 Update.
The public update for the Service Pack 2 expiration date issue is now available for download.
The update can be applied before or after Service Pack 2 installation. If the update is applied prior to installing Service Pack 2 it will prevent the expiration date from being improperly activated during installation of Service Pack 2, if it is applied after Service Pack 2 it will remove the expiration date incorrectly set during installation of Service Pack 2.
The update is applicable to all of the products that this issue affected (see the list in the KB linked below).
Installation instructions and download links for x86 and x64 are available in this KB: http://support.microsoft.com/kb/971620
The direct download link for x86 is: http://download.microsoft.com/download/2/F/5/2F51AB71-1325-49D2-9CB9-18DEC4780E99/office2007-kb971620-fullfile-x86-glb.exe
Q: How can I tell if the update has worked?
A: The License Type text on the Convert License Type page in Central Administration no longer contains the word “trial”.
Q: I applied the update and now I can’t enter anything in the Convert License Type page in Central Administration, is this right?
A: This is expected behavior if your license type is “Office SharePoint Server with Enterprise Client Access License”.
You install SharePoint in a Farm and you see the below error in the event viewer.
Usually this means that your SharePoint Timer Service Account is set to “Local Service Account” rather than the “Domain\Service Account” you created during Install.
You should change the Logon Account in the Services Applet to the Domain Account associated with that Service and your problem should be resolved.
Using a strategy of least privileges and domain accounts, here are the accounts listed in the best practice for installing SharePoint
Update on 05/21/09 :
A bug in Service Pack 2 could affect the server farm licensing information, for more information, please refer to the new post here:
KB Article Links
Description of Windows SharePoint Services 3.0 SP2 and of Windows SharePoint Services 3.0 Language Pack SP2
Description of 2007 Microsoft Office servers Service Pack 2 (SP2) and of 2007 Microsoft Office servers Language Pack Service Pack 2 (SP2)
Service Pack 2 for Windows SharePoint Services 3.0, x86 & x64
Service Pack 2 for Office SharePoint Server 2007, x86 & x64
Slipstream Builds For Windows SharePoint Services 3.0
Windows SharePoint Services 3.0 with SP2, x64
Windows SharePoint Services 3.0 with SP2, x86
To keep all the files in a SharePoint installation up-to-date, the following packages need to be applied on all servers in the farm. Service Pack 2 contains all fixes released through February of this year, so customers can install it directly on RTM build of the products.
- Service Pack 2 for Windows SharePoint Services 3.0
- Service Pack 2 for Windows SharePoint Services 3.0 Language Pack (if applicable)
- Service Pack 2 for Office SharePoint Server 2007
- Service Pack 2 for Office SharePoint Server 2007 Language Pack (if applicable)
After applying the preceding updates, run the SharePoint Products and Technologies Configuration Wizard or "psconfig –cmd upgrade –inplace b2b -wait” in command line. This needs to be done on every server in the farm with SharePoint installed. The version of content databases should be 188.8.131.5221 after successfully applying these updates.
For more in-depth guidance for the update process, we recommend that customers refer to the following articles. These articles provide a correct way to deploy updates, identify known issues (and resolutions), and provide information about creating slipstream builds.
Deploy software updates for Windows SharePoint Services 3.0
Deploy software updates for Office SharePoint Server 2007
Create an installation source that includes software updates (Windows SharePoint Services 3.0)
Create an installation source that includes software updates (Office SharePoint Server 2007)
Customers can be benefited from the following enhancements with Service Pack 2.
- Performance and Availability Improvements
Service Pack 2 includes many fixes and enhancements designed to improve performance, availability, and stability in your server farms, including:
- New Timer job automatically rebuilds content database index to improve database performance.
- When a content database is marked as read-only, the user interface will be modified so users cannot perform tasks that require writing to the database.
- Performance enhancement across nearly all the components.
- Improved Interoperability
Service Pack 2 continues to improve SharePoint interoperability with other products and platforms.
- Broader support of browsers
Internet Explorer 8 is added into Level 1 browser support.
FireFox 3.0 is added into Level 2 browser support. (Firefox 2.0 is no longer supported by Mozilla)
- Provide improved client integration user experience with Form Based Authentication. Now the client application can store user credentials instead of asking for them every time. For more technical details please refer to the updated articles on TechNet.
Configure forms-based authentication (Office SharePoint Server
Configure forms-based authentication (Windows SharePoint Services)
- Getting Ready for SharePoint Server 2010
A new preupgradecheck operation is added to stsadm tool. It can be used to scan your server farm to establish whether it is ready for upgrade to SharePoint Products and Technologies "14". It identifies issues that could present obstacles to the upgrade process. It checks for several SharePoint Products and Technologies "14" system requirements, including the presence of Microsoft® Windows Server® 2008 and a 64-bit hardware, and provides feedback and best practice recommendations for your current environment, together with information on how to resolve any issues that the tool discovers.
The full explanation of SP2 benefits can be downloaded here:
You may experience issues opening documents direclty from libraries using Office 2010, here is a work around to the error below:
set up a fake proxy (127.0.0.1) in Internet Explorer with an exception for *.*. Still don’t know why this works, but it has allowed me to actually check out, edit, and upload/check-in documents from our libraries.