First step is to enable anonymous access under the Central Administration section:
• Navigate to Central Administration site
• Click on “Application Management” either in the Quick Launch or across the top tabs
• Select “Authentication Providers” in the “Application Security” section
• Click on the “Default” zone (or whatever zone you want to enable anonymous access for)
• Under “Anonymous Access” click the check box to enable it and click “Save”
NOTE: Make sure the “Web Application” in the menu at the top right is your portal/site and not the admin site.
You can confirm that anonymous access is enabled by going back into the IIS console and checking the Directory Security properties.
Now the second part is to enable anonymous access in the site.
• Navigate to your site’s home page and click on Site Actions -> site settings page
• Under the “Users and Permissions” section click on “Advanced permissions”
• On the “Settings” drop down menu (on the toolbar) select “Anonymous Access”
• Select the option you want anonymous users to have (full access or documents and lists only)
Now users will be able to access the ones you have configured without logging in.
A couple of notes about anonymous access:
• You will need to set up the 2nd part for all sites unless you have permission inheritance turned on
• If you don’t see the “Anonymous Access” menu option in the “Settings” menu, it might not be turned on in Central Admin/IIS. You can manually navigate to “_layouts/setanon.aspx” if you want, but the options will be grayed out if it hasn’t been enabled in IIS
If you have a site running in windows authentication or in forms authentication.
If you need to design an application page that can be accessed by the anonymous users as well.
We will inherit the application page by LayoutPageBase class, right? Yes, so first thing to note is instead of inheriting from this class, we are required to inherit from class named UnsecuredLayoutsPageBase.
In addition to this, you also need to override one more method which is
protected override bool AllowAnonymousAccess
I just came across a presentation which listed down some of the features included in SQL Server 2008 to support Disaster Recovery and Maintenancec of MOSS 2007 environment.
You can find the presentation MOSS and SQL Server 2008 – Better Together (Webcast).
Also, I would like to thank Rich Crane and Bob German for sharing the presentation.
Pradeep Narsimhula MCT, CAPM, ITIL(Foundation) certified
1. Deploy the web part in your web application as you do normally.
2. Check whether the web part is showing up in the web part gallery.
3. Create a web part page by navigating to the site settings, create web part page.
4. Add your custom web part on the web part page.
5. Start SharePoint designer and open the newly created web part page.
6. You will now find two entries corresponding to the web part you added on the page
i. In the page declaration you will find a entry which looks something like this:
ii. Click on the web part section in the page and you will see an entry like this:
7. Copy these entries in separate notepad, and close the page opened in the SharePoint designer.
8. Now open the master page in SharePoint designer and add the first entry in the declaration section and second entry at the place where you want to add the web part to.
9. Save the page, check in and publish it and that’s it. Your job is done.
Here are the main benefits & limitations of each technology:
- Database Mirroring benefits:
- Instantaneous synchronization of changes
- Easy setup and maintenance
- Automated failover (in High Availability Mode)
- Easy to perform failover
- Fast failover. (if no transactions are queued)
- Applications can be mirroring aware using failover partner parameter in connection string
- Database Mirroring limitations:
- Limited number of databases can be mirrored per SQL instance. (however, this number is higher than the 10 you see plastered everywhere, but really depends on your hardware)
- Mirrored database cannot be queried, backed up, or basically touched in any way (snapshot can be taken however)
- Only supports one to one server pairings
- Cannot mirror a database more than once
- Synchronous mirroring is intolerant to latency and bandwidth constraints (Asynchronous mirroring has no problems with latency or bandwidth)
- Log Shipping benefits:
- Very flexible – Independent jobs govern backup/copy/restore behavior
- Delay of restore job can protect from database corruption
- Log shipped database can be queried. (in standby mode)
- Log shipping allows multiple standby databases
- Perhaps more tolerant to latency than sychronous mirroring.
- Doesn’t affect performance of primary server
- Easy setup
- Log Shipping limitations:
- No automated failover
- Cannot synchronize faster than once a minute
- Failover is more complicated than mirroring
- Harder to view status of log shipping
Configuration – One per farm, stores information about the farm topology and settings
Content – Stores all content; it is usual to have several content databases
WSS Search – Property store for WSS search
SSP Search – Displayable document properties/metadata for MOSS Search Single Sign-On – SSO credential mappings
SSP – Other Shared Services such as user profiles, audiences, etc.