16.01.2013 Views

Microsoft Sharepoint Products and Technologies Resource Kit eBook

Microsoft Sharepoint Products and Technologies Resource Kit eBook

Microsoft Sharepoint Products and Technologies Resource Kit eBook

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

856 Part IX: Maintaining a Server in Windows SharePoint Services<br />

Web Part Display<br />

Web Parts in Windows SharePoint Services sites are displayed in FrontPage 2003<br />

with live data. However, some Web Parts in portal sites created with SharePoint Portal<br />

Server 2003 might be displayed with static previews that do not include live data.<br />

Moving or Backing Up Websites<br />

Portal sites created with SharePoint Portal Server 2003 should be moved or backed up<br />

by using SharePoint Portal Server 2003 backup tools instead of using FrontPage 2003<br />

Backup, Restore, or Web Package options. Therefore, these features are disabled<br />

by default in FrontPage 2003 when editing sites created with SharePoint Portal<br />

Server 2003.<br />

Working with Areas <strong>and</strong> Sub-Areas<br />

SharePoint Portal Server 2003 sites can include Areas <strong>and</strong> Sub-Areas, which can be<br />

nested many levels underneath the root web. When opened in FrontPage 2003, all<br />

areas <strong>and</strong> subareas are represented as subordinate sites, <strong>and</strong> all are displayed underneath<br />

the root of the site. For example, if Area1 is below the root-level site <strong>and</strong><br />

Area11 is below Area1, Area11 is simply a subsite of the root-level site <strong>and</strong> not a<br />

subsite of the Area1 site.<br />

FrontPage 2003 users are not able to delete an Area or Sub-Area in a site created<br />

with SharePoint Portal Server 2003. When the root site of a site created with<br />

SharePoint Portal Server 2003 is open in FrontPage 2003, it is possible to create subordinate<br />

sites under that root. Subsequently, subordinate sites under those newly<br />

created subordinate sites are also possible, thus nesting them multiple levels deep. Yet<br />

Areas <strong>and</strong> Sub-Areas of the portal, represented as subordinate sites in FrontPage 2003,<br />

cannot have nested subordinate sites. When an Area or Sub-Area is open in<br />

FrontPage 2003, the Subordinate Site option seen when you right-click on a folder in<br />

the Folder List <strong>and</strong> then click New is unavailable. Visually, in the FrontPage 2003<br />

user interface, you cannot differentiate between a subordinate site <strong>and</strong> an Area; both<br />

are represented with the same folder icon.<br />

Editing Personal Sites<br />

One of the biggest advantages to My Sites in SharePoint Portal Server 2003 is that<br />

each user browses to the same URL but each sees his or her own unique content.<br />

SharePoint Portal Server 2003 does this by assigning a unique GUID to each user<br />

<strong>and</strong> storing customization <strong>and</strong> content options for each GUID. The My Site template<br />

is shared by all users, so if a FrontPage 2003 user edits the default.aspx page in the<br />

My Site website, the change would affect all users with My Sites. The easiest way to<br />

open the My Site default.aspx page in FrontPage 2003 is by browsing to it in Internet<br />

Explorer, <strong>and</strong> then choosing Edit With <strong>Microsoft</strong> Office FrontPage from the File<br />

menu or clicking the Edit button on the St<strong>and</strong>ard Buttons toolbar.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!