If you try to edit the Collaboration Publishing home page in SharePoint Designer, you will be presented with the following warning message.
Basically, this is because the default page of the Collaboration Publishing Portal uses the Publishing Infrastructure and the page is associated to a Layout Page.
If you really need to edit it, you need to detach the page from the Layout Page. You can do this by right mouse clicking on the home page and then clicking Detach from Page Layout.
After you click to confirmation to detaching the page, all the mark-up of the page to the default.aspx file.

You must check the file out to complete the process.
You will then be able to edit the page as it it was any aspx page.
If you need to revert the page back to the layout page you can do this by right mouse clicking on on the default.aspx page and clicking Reattach to Page Layout.
Any changes to the layout of the pages will be lost, but changes to the webparts that exist in webpart zones of the layout page will be retained.
You can do this with any page that is based on the publishing pages framework.

Just received my new 500 GB USB drive. From my initial first glance it seems to be as solid and robust as advertise. Not been brave enough to drop it yet, but considering the amount of knocks my laptop get’s it will only be time before it is put to the test.
One annoying feature I’ve noticed from the out set is that the USB connector is larger than normal and actually blocks the second USB port on my laptop. I’m sure I’ll be able to live with it but its a bit of a design floor.
It’s slightly larger than I imagined and I’m not sure what the large whole at the top is for. Maybe it’s there for when I’m next rock climbing with my laptop and hard drives! Also it comes with a Carabineer for those climbing experiences:)
I have to say though the Password protection software is really quick and easy to install and its great to know that your data is safe.
Also the NTI Shadow software was also quick and easy to install and configure. Great for backing up files from your primary partition. All those mp3, photos and .pst files are now that much safer!
Anyway if I find any faults with it I will surely update it here. Otherwise from my initial assessment I definitely recommend it.
Enjoy!
Microsoft Windows PowerShell command line shell and scripting language helps IT professionals achieve greater control and productivity. Using a new admin-focused scripting language, more than 130 standard command line tools, and consistent syntax and utilities, Windows PowerShell allows IT professionals to more easily control system administration and accelerate automation.
A free book called Mastering PowerShell is available to download here:
http://powershell.com/Mastering-PowerShell.pdf
Source: An article written by Sudeep Gopalakrishnan
IISreset.exe is a magical command that resolves many problems! Err… well, yeah that command restarts all IIS related processes and thus essentially running it cleans up all the “mess”. So is there anything special about IISReset.exe in Windows 2008? Yes and I do not recommend using it and here’s very useful information that you must know about what this command does.
Windows 2008 introduced a new service called Windows Process Activation service aka WAS. In IIS 7.0 you can run HTTP and non HTTP services (like net.tcp) in the same application pool. WAS manages application pools and worker processes for HTTP and non HTTP protocols. IIS uses the HTTP protocol with WAS. With WAS we opened it up for others to use our process model. The IIS process model is very efficient and I believe we made this change due to good feedback.
Back to IISERSET…. IISReset.exe restarts the following Windows Services
So do you see what would happen if your ran IISReset.exe with the intention to restart ONLY IIS, but you also have other services dependent via WAS?
Conclusion: Running IISReset.exe will restart WAS and restarting WAS will restart all services that are dependent on it, including IIS, if installed. This can be problematic in production environments where you have non HTTP services implemented with WAS but your intention is to only restart IIS. An example to this will be with Small Business Server.
Therefore, the recommended way to restart IIS on Windows 2008 machines will be to use one of the following methods:
- Open IIS Manager and then select the server node. In the right side pane, you will have an option to restart IIS.
- Open a command prompt as Administrator and run the following commands
- net stop w3svc
- net stop IISAdmin
- net start IISAdmin
- net start w3svc
If you are experiencing the following symptoms:
Unable to enter text into text boxes;
The About box fields indicating the browser version and patch level, are blank ;

Unable to right-click on pages;
Unable to select text in a HTML document or a Web page;
When you open the About box, the following error occurs and the dialog closes;
You need to either reinstall Internet Explorer or run the following commands:
REGSVR32 MSHTMLED.DLL
REGSVR32 JSCRIPT.DLL
REGSVR32 /i MSHTML.DLL
While assisting a client in moving content from one environment to another for testing purposes, it was noticed that the site of the stsadm backup file was considerably larger than the Content Database size as defined in the stsadm enumsites report.
As can be seen in the from the out put of the enumsites, the StorageUsedMB for the HRTemp site collection is reported to be 158.4 MB. However the size of the backup file is 3.1 GB.
<Sites Count="5"> <Site Url=http://portal Owner="domain\spadmin" ContentDatabase="WSS_Content"StorageUsedMB="1.7" StorageWarningMB="0" StorageMaxMB="0" /> <Site Url="http://portal/teamsite/hr" Owner="domain\spadmin" ContentDatabase="WSS_Content_HR2" StorageUsedMB="3171.1" StorageWarningMB="0" StorageMaxMB="0" /> <Site Url="http://portal/teamsite/HRTemp" Owner="domain\spadmin" ContentDatabase="WSS_Content_Temp" StorageUsedMB="158.4" StorageWarningMB="0" StorageMaxMB="0" /> <Site Url="http://portal/teamsite/it" Owner="domain\spadmin" ContentDatabase="WSS_Content_IT" StorageUsedMB="8840.7" StorageWarningMB="0" StorageMaxMB="0" /> <Site Url="http://portal/teamsite/research" Owner="domain\spadmin" ContentDatabase="WSS_Content_Research" StorageUsedMB="14.5" StorageWarningMB="0" StorageMaxMB="0" /></Sites>
I asked if they had deleted any files and if so had they deleted the files from the recycle bin. They said that they had deleted files and removed them from the recycle bin. As it transpires they had removed the files from the users recycle bin and not the site collection recycle bin.

Once the files were removed from the site collection recycle bin the backup file was reduced to the expected size.
It is therefore important to ensure that files are deleted and removed from the recycle bin properly before executing a stsadm backup as files in the recycle bin for the site collection will also be backed up and this will not be reflected in the enumsites report.
Note: You can disable the recycle bin thus purging the recycle bin using the setproperty method of the stsadm command. Beware that this property is for the Web Application and not the site collection, and will as a result empty (delete) the recycle bins for all site collections in the web application. This is OK for testing purposes, but not recommended in production environments.
Best Practices for SharePoint Content Databases in SQL Server
http://www.mssqltips.com/tip.asp?tip=1777
Deploy using DBA-created databases (Office SharePoint Server)
http://technet.microsoft.com/en-us/library/cc262869.aspx
Whitepaper: Database Maintenance for Microsoft SharePoint Products and Technologies
http://go.microsoft.com/fwlink/?LinkId=111531&clcid=0×409