For those who are visually inclined and prefer webcasts, here is an awesome Project Server 2010 training for designing, planning a Project Server 2010 deployment.
More videos:
http://www.microsoft.com/en-us/showcase/channeldetails.aspx?channelid=microsoftproject
Have you installed Office Web Apps on your SharePoint 2010 production farm? If yes, then you have just married Office Web Apps with SharePoint 2010 for the rest of their lives (well almost!).
Microsoft states that Office Web Apps and SharePoint 2010 are ‘tightly integrated’ and thats absolutely right!
Problem:
Its so tightly integrated that Office Web Apps uninstalls may not work properly, SharePoint sites are removed, customisations are lost.. and so on.
Solution:
The solution is to DEACTIVATE Office Web Apps rather than uninstalling it. DONT think of uninstalling Office Web Apps unless you read this full article, clearly understand your environment, take full tested backups of everything and read the links that this articles has.
What happens when you uninstall Office Web Apps?
If you ever come across a situation where you have to do a migration and need to migrate ‘List Workflows’ created in SharePoint Designer, then there is a way!
I found a great article online..
Basically, you have to create a new dummy List workflow without any steps in the new (destination) site, then ‘export to visio’ in both the old (source) site.
Rename both source List Workflow and newly created destination List Workflow vwi files and add a .zip file extension to both of them. Copy the workflow.xoml.wfconfig from the new Workflow zip file to the old Workflow zip file.
Then remove the .zip in the file name and Import from Visio in the destination site.
Its been over a month since the release of SharePoint 2010 SP 1 and since the list of known issues has not grown, I have the confidence to recommend the installation of Service Pack 1. It was only two days ago when I installed SP1. Generally I recommend Admins to wait a while before installing into their Production servers.
Download it here:
SharePoint 2010 Foundation SP1:
http://support.microsoft.com/kb/2460058
SharePoint Server 2010 SP1:
http://support.microsoft.com/kb/2460045
The install process:
1. Run the exe to extract and install the binaries
Running the exe (installing the binaries) will take 15-25 minutes.
This can be run concurrently on all SharePoint Servers.
2. Ensure that you have ran the exe on all servers in the SharePoint farm.
3. Run the SharePoint Products Config Wizard on all servers in the SharePoint Farm.
The SharePoint Products Config Wizard would take about 5-10 minutes.
This step cannot be run before the previous steps.
This step cannot be run concurrently on other servers in the same farm.
4. Reboot.
Reboot is a requirement as it is listed in the ‘Known issues’ of SP1
5. Restart the User Profile Sync Service (through SharePoint). This can take about 10 minutes.
This is a known issue with SP1.
Some other points:
I had to install the Office Web Apps SP 1 first before I did the SharePoint 2010 SP1.
Since I run SharePoint 2010 Enterprise, I did not install the SharePoint Foundation SP1 – because I extracted the exe and compared it with the SharePoint Server SP1 and all the files have been included.
So, save time and just install the SharePoint Server SP1 and not the SharePoint Foundation SP1 if you run SharePoint Server Standard or Enterprise.
Some Features of the SharePoint 2010 Service Pack 1:
• Support for the next version of SQL Server Code Name “Denali”
• Shallow copy functionality allows you to move Site Collections from one Content Database to another Content Database without touching the underlying blob (unstructured) data. Only the pointers are updated. Functionality is provided in the Move-SPSite cmd in PowerShell.
• Site-level recycle bin allows administrators to recover Site Collections and sites that have been accidentally deleted by the owners.
• Improvements to storage management (StorMan.aspx)
SP1 introduces an improved StorMan.aspx, enabling users to better understand what is using up their quota and to act upon that information in order to reduce the size of their sites.
• Cascading filters for Performance Point services
New cascading filter support enables you to pass the value of one filter to another.
• Additional browser support
SP1 provides support for Internet Explorer 9 in Internet Explorer 8 Standards Mode and also provides support for the Google Chrome browser.
Cumulative Updates in SharePoint SP 1:
SP 1 includes all SharePoint 2010 updates upto and including April 2011 CU. It does not include the June 2011 CU. You must apply that separately. I encourage you not to rush and install the June 2011 yet. Only apply it if it fixes a specific issue you are experiencing.
SharePoint 2010 SP 1 also provides a number of fixes to improve the user experience.
IPv6 is becoming an issue and I hear more techs talking about it now than 5 or 10 years ago. I first learned about IPv6 and the IPv4 depletion issues about 10 years ago when I used to play with my own Cisco lab at home and aspire to be a Cisco Certified Internetwork Expert – CCIE 
.
Now, as I have been working full time with SharePoint for years, I thought its a good time to pull out a little bit about SharePoint with IPv6 from the net…
Watch this space for the known issues with installing SharePoint 2010 & Office Web Apps 2010 Service Pack 1.
Microsofts link:
http://support.microsoft.com/kb/2532126
The following are issues that you may experience when you install these service packs:
Service Pack 1 for SharePoint 2010 is now available for download. Questions may arise if it contained the June 2011 Cumulative fixes, but it DOES NOT.
Tip: I highly recommend you install and test all Service Packs and CUs in a DEV environment first, wait for more feedback from the public / forums/blogs and then install in your Production environment.
Download link to SharePoint 2010 Service Pack 1:
http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=26623
Admins, please note: you would have to download the June 2011 CU separately and install it after the Service Pack 1 is installed. The June Cumulative Update includes several important security and bug fixes that are not included Service Pack 1.
Download June 2011 CU here:
http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=2536599
Related links:
http://sharepoint.microsoft.com/blog/Pages/BlogPost.aspx?pID=984
http://blogs.technet.com/b/office_sustained_engineering
When you install a new farm, you might be curious to find out what the Health Analyzer results are. Instead of waiting for the checks to happen (basically timer jobs scheduled at different intervals), you could force them to run all at one go, so you can review the results and address them.
You can easily run this in PowerShell. All it does is start all the timer jobs with ‘Health’ in its name. That fires off all SharePoint 2010 Health Analyzer jobs for your new farm in one go.
# Check to ensure Microsoft.SharePoint.PowerShell is loaded
$snapin = Get-PSSnapin | Where-Object {$_.Name -eq 'Microsoft.SharePoint.Powershell'}
if ($snapin -eq $null) {
Write-Host "Loading SharePoint Powershell Snapin"
Add-PSSnapin "Microsoft.SharePoint.Powershell"
}
Get-SPTimerJob | Where {$_.Name -like "*Health*" -and $_.Name -like "*-all-*"} | Start-SPTimerJob
Ever wondered if there is a formula for calculating content database sizes? Want to have a start into learning more about SQL design and database capacity planning for SharePoint 2010?
Luckily, there is an awesome Technet document on SQL server design and capacity planning and it covers some great points to consider when planning your storage with SharePoint 2010.