Navigation Error: Page being updated by another user.

After restoring a site collection to a new managed path I keep getting an error when trying to modify the navigation that states: Pages is being updated by another user. After googling I came across a post stating corrupted navigation headings. This is how I resolved: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1691577&SiteID=1

To reset corrupted headings, you have to :
- remove all the lists under corrupted heading
- remove corrupted heading
- From the list settings, add a removed list to the quick launch (This regenerate a non corrupted heading)

Storage Space Allocation

Storage Space Allocation is available throughout site collections when site collection quotas are turned on. You can view the size of document libaries by default. If you close Show Only you can select lists and documents. Very nice feature. Easy to keep track of exactly what is taking up the most space.

Calendar View Webpart (Today view)

By default you can't add a webpart to display only today's calendar entries. I had to create a new view and modify the webpart on the home page to display only the newly created view.

Go to your calendar settings and create a new column called Begin Date. Add the formula =[Start Time] and select Date and Time for data type returned from this formula and click ok.

Create a new view called Today. Under Filter settings select Show items when the following is true: Column Begin Date, select is equal to, and type [Today].

Click ok.

Add or modify the existing calendar webpart on your home page. Select Today as the selected view.

Backup Farm

I have just finally completed the remainder of my backup tasks.

We are backing up:

IIS Metabase - (running on windows scheduler daily)
Backup IIS once before production and every time there is an IIS change or new WEB App created on ALL WFE’s

Syntax
iisback[.vbs] /backup [/b BackupName] [/v {Integer NEXT_VERSION HIGHEST_VERSION}] [/overwrite] [/e EncryptingPassword] [/s Computer [/u [Domain\]User [/p Password]]]
batch file to run is located at C:\WINDOWS\system32\inetsrv\MetaBack\BACKUP_IIS_METABASE.bat
Creates 2 files in:
C:\WINDOWS\system32\inetsrv\MetaBack\WeeklyBackup.MD0 (0 increments for each save)
C:\WINDOWS\system32\inetsrv\MetaBack\WeeklyBackup.SC0 (0 increments for each save)


IIS Configuration – (running on windows scheduler weekly)
Go to IIS, Right Click Local Computer – Choose All tasks – Backup/Restore Configuration – Create Backup
C:\WINDOWS\system32\inetsrv\MetaBack\IIS Configuration Backup 083107.MD0
NOTE: This backup method provides a way to restore only your IIS settings, not your content files. This backup method does not work if you reinstall your operating system. Backup files cannot be used to restore an IIS configuration on other computers that are running Windows 2000

MOSS – Index Server (full farm)
Full Farm Backup – GUI - Central Admin – Operations – Perform a backup. Backup location S:\FullFarmBackup (needs to have farm service account and sql service account sharing rights)

Batch file created to run on Window Scheduler every Saturday at 9:00PM. - S:\FullFarmBackup (FullFarmDiff) This is a full farm backup using the differential flag. This will only backup changes. You must first have a full farm backup before using the differential flag

Site Collection – Each Site Collection has been backed up to d:\moss_backup. The batch file is located in d:\moss_backup and has been added to the job scheduler to run every Saturday evening at 8:35pm. This works great but once your site collections get really big they will take a long time. Also if you are running this on a server that users are accessing it can hurt performance. We have this running on our Index server which users are not accessing.

I will add also that currently the SSP is very important. This is being backed up by the Central Administration site. I am working on creating a script to have this backed up by the windows scheduler also.

Database backups are done nightly

Microsoft Forefront For Sharepoint

I just finished configuring Forefront for Sharepoint.

This is a very useful users guide:
http://download.microsoft.com/download/A/A/1/AA13E922-FFA3-4EB1-BA3D-D177AB058746/SP_Users_Guide.doc

My next step is to test out the Management Console. We have 6 WFE's in our prd farm so it would make life easier to make configuration changes in 1 place. So far we are only using virus protection. Looking forward to using the file filters.

One thing I like about forefront is it catches files that are excluded by Sharepoint. It will actually look at the header of the file. So a user can't change a .mov extention to a .txt file and upload it to their mysite.

I have done a little testing on this and it works perfectly. I do not like the fact that if a file gets captured it displays a message as if the file has a virus. I do remember at Tech-Ed 08 someone stated in a session that this will be addressed in the next version. Due to this we are not using the file filter option because we don't want users to get confused.