Waqas Sarwar's profilewaqas's spaceBlogListsGuestbookMore Tools Help

Blog


    How To: Hide/Remove the View All Site Content link in SharePoint

    Article: http://www.crsw.com/mark/Lists/Posts/Post.aspx?ID=36

    Summary
    This article covers how to hide (remove) the View All Site Content link and/or the Recycle Bin link from the quick launch navigation without having to customize the master page.  Additionally, I cover how I accomplished along with other options, all using the standard functionality provided in Windows SharePoint Services 3.0.

    Important:  This solution is not an answer for security.  The user will still have access to the View All Site Content page.  The View All Site Content link is simply removed or hidden from the page.

    Applies To

    - Windows SharePoint Services 3.0
    - Microsoft Office SharePoint Server 2007

    Downloads

    Hide View All Site Content - Solution Package
    Hide View All Site Content - Solution Package and Source Code

    Installation and Activation
    (Very easy, no coding required)

    For those interested in how to install this solution, it is very easy and does not require any coding, compiling, or editing.

    Basic Install Steps:

    Note: This command must be executed on the (only one) SharePoint web server, and you must be a local administrator.

    1. Add the solution using the STSADM command: stsadm -o addsolution -filename [path]\VASCSiteAction.wsp
    2. Deploy the solution using the STSADM command: stsadm -o deploysolution -name VASCSiteAction.wsp -allowgacdeployment -immediate -allcontenturls
    3. Optional - to restart IIS: iisreset /noforce

    Using (Activating) the new feature:

    1. Navigate to the site you want to hide the View All Site Content link.
    2. Go to the Site Settings for that site (Site Actions > Site Settings).
    3. Click the Site Features (not the Site Collection Features) link under the Site Administration section. 
    4. Activate the new feature named "Hide the View All Site Content link".

    Your View All Site Content link should now be hidden and the View All Site Content link should now appear in the Site Actions menu.

    For those only interested in using this solution, you do not need to read any further.  However, for those who are interested in how this is accomplished, the rest of this article discusses just that.

     

    So, How'd You Do That?

    Update

    This solution can also be used to hide the Recycle Bin.  Simply add the following code to the custom core.css file in the sample solution project and your Recycle Bin will also be hidden.

    #ctl00_PlaceHolderLeftNavBar_idNavLinkRecycleBin
    {
           Visibility:hidden;
    }
     

    Overview
    Windows SharePoint Services (WSS) 3.0 has provided a tremendous leap forward from WSS 2.0 in securing and dynamically rendering links to the user based on their access.  This much needed improvement is also applied to the View All Site Content link in SharePoint 3.0.  The View All Site Content link will only be rendered to users who have at least a minimum level of access to a given site such as adding items to any list or document library on the site.  For sites that allow anonymous access users to have only read access, this View All Site Content link will not appear.  However, there are times when a user’s level of access causes the View All Site Content link to appear, even when the site designers or administrators would rather not volunteer this link so freely to the user.  For this reason it is sometimes desired to have this link removed from the page for all users except maybe for site administrators or designers.  This is when the old adage of “Out of sight, out of mind” is an option site administrators would like to have.

    The result of this article is to hide View All Site Content link from the users.  An additional View All Site Content menu item is added to the Site Action menu and is accessible only to users having the AddAndCustomizePages right.

    Here is a picture of the typical View All Site Content link as it appears on a SharePoint web site and how it looks after it is hidden.

    Before (Normal)
    After (Hidden)
     
     

    Additionally I add a new custom menu item to the Site Action menu.  Here is the result of the new link.  This link will only appear for users having the AddAndCustomizePages right such as designers and administrators.

    And finally, this functionality is wrapped up into feature allowing it to be activated or deactivated for each site as needed.  Here is the new feature that will appear in the list of Site Features for a web site.

    All of this is wrapped in to a single SharePoint solution package (.wsp) file and can easily be installed on a SharePoint farm by a server administrator.

    Note:  From this point forward in the document, any reference to the View All Site Content link will be abbreviated to VASC.

    Consideration

    There are a couple ways to in which to accomplish this.  The first and most obvious method is to modify the master page that contains this link.  This involves a fairly simple process of modifying the master page and removing the VASC link, then redeploying the new master page.  The drawback from this is that you do have to modify the master page which is sometime not desirable, plus the master page is likely to have more than one site based on it, and it may be desirable to have this View All Site Content link remain on those sites.

    However, if you are willing to modify the master page, there is another posting you may find of value.  Keep in mind the security you define in the master page will be the same for all sites on your SharePoint farm.  If that is desirable, you may find this post on SPSecurityTrimmedControl: Conditionally display contents by security of use.

    My Approach

    I had a couple goals I wanted to my solution to meet.  They were:

    1.       To be able to selectively choose the sites where the VASC link is hidden.

    2.       Avoid having to modify the master page if possible.

    3.       Provide a simple way for users to hide/remove the VASC link.

    After a little investigation, a few things about SharePoint (3.0/2007) surfaced that allowed me to achieve all of my goals and provide a solution that can easily be implemented. 

    Hidden by Style

    The approach I have decided to use is to simply hide the VASC link using a style sheet modification.  The VASC link for most, if not all of the sites assigns an ID (ctl00_PlaceHolderLeftNavBar_idNavLinkViewAll) to the anchor tag containing the VASC link.  This makes it easy pretty darn easy hide this link by simply adding a bit of style code to the page.  In fact, just for giggles, you can copy the following style sheet code into a Content Editor Web Part.  This web part can even be strategically placed at the bottom of the page; optionally hide the title bar and nobody would even know it was there.  Here is the sample style to try it just for fun.  This will hide the View All Site Content link on your page.

    #ctl00_PlaceHolderLeftNavBar_idNavLinkViewAll
    {
           Visibility:hidden;
    }

    But this is not really good enough.  At least, not alone this isn’t. 

    I needed a way to do this for every page on a given site.  And copying this code to each and every page on a site is not only extremely tedious; it is almost guaranteed to be incomplete and error prone.  Microsoft Office SharePoint Server (MOSS) 2007 does provide an easy way to do this, but Windows SharePoint Services (WSS) 3.0 does not.  Using MOSS 2007, you can apply a custom style sheet to a web site and optionally apply it to every sub site.  For SharePoint servers where this is desired, and if you are using MOSS 2007, this will work for you.  Also keep in mind; you just removed the VASC link for every user – including your site designers and administrators.  Although this is not the worst of all problems, it is probably not the absolute desired solution either. 

    I still like the idea of using the custom style code to hide my VASC link.  But I also need to place a link on the page for users who will need easy access to the VASC link such as designers and administrators.  I know I can easily accomplish this by adding an access controlled link to the Site Actions menu, but I will come back to this in a moment.  I still need to address how to easily apply a customized style to every page on a given site.

    CustomizeCss

    So how can I apply a custom style to every page on a given site?  SharePoint provides a way to do this using the SharePoint object model.  With a bit of custom C# code I use the SPWeb.CustomizeCss method to specify a custom style sheet to be used on every page of my site.

    The CustomizeCss method on the SPWeb class provides way to specify the style sheet file name of an existing style sheet used by SharePoint.  SharePoint utilizes a number of different style sheet files.  The one we are interested in is the style sheet file that is applied to each and every page on the site.  One such style file is the core.css file, and this will do just for our needs.  The standard default core.css file is located in …\12\TEMPLATE\LAYOUTS\1033\STYLES.  This STYLES folder is a virtually mapped via the /_layouts virtual directory that is mapped to each and every site in SharePoint.  So, the core.css file is accessible to every site by simply using the URL of “[site-root-url]/_layouts/1033/styles/core.css”.  For every page that SharePoint renders, it renders a link to the core.css using this path. 

    However, for any site that has been configured to use a custom core.css style sheet via the CustomizeCss method on the SPWeb class, the URL rendered in each page references a core.css file located in a different location.  This is accomplished in C# by the following code where web is an instance of the SPWeb class for the web site of your choice.

    web.CustomizeCss(“core.css”);
    web.Update();

    The CustomizeCss(“core.css”) statement tells SharePoint to use a custom copy of the SharePoint core.css file.  Once this CustomizeCss method is executed, a copy of the core.css file found in the …\12\TEMPLATE\LAYOUTS\1033\STYLES folder is copied to the folder (not a document library) named _styles on the applied site.  The resulting URL to this new core.css file can be found at
    “[site-root-url]/_styles/core.css”.  Modifying this core.css file will affect only the current site. 

    Reverting this site back to using the original global (un-customized) copy of the core.css file can be accomplished just a easy using the following code.

    web.RevertCss(“core.css”);
    web.Update();

    Executing the RevertCss method does not remove the custom core.css file on the web site’s “/_styles” folder.  It simply tells the site to no longer use it and to use the original core.css found in the C:\…\12\TEMPLATE\LAYOUTS\1033\STYLES folder; which is the same folder as the as the “[site-root-url]/_layouts/1033/styles” folder.

    So we now know how to use the CustomizeCss and the RevertCss methods on the SPWeb class provide an easy way to point the site to a new custom style sheet file.  Now that we have an easy way to point our site to a custom core.css file, all we need to do is copy our custom core.css file that contains all the original core.css contents plus the extra style code to hide the VASC link and copy it into the _styles folder of the site.  All of this can easily be implemented using a SharePoint feature.  Using a feature provides a standard way to enable or disable functionality with a site in a safe and secure manner.  I won’t cover all the details on how to create the feature here, but the source code provides all the code you need.

    Now that we know how to hide the View All Site Content link easily using a feature and the CustomizeCss and RevertCss methods, we need to provide an easy way to allow site designers and administrators to quickly and easily use the View All Site Content link.

    Site Action Link

    To provide web managers such as designers and administrators with a convenient link equal to the View All Site Content link, we will add a new custom action menu item.  I won’t go into the details of the code and how to create the feature here, but I will briefly cover the expected functionality.  Again, the source code is available for those interested in the technical details.

    The Site Action is usually located in the upper right corner of the web site and contains links used by site administrators such as the Site Settings link.  The nice thing about the Site Actions menu is that it is collapse and consumes a minimal amount of screen real estate.  So, adding an additional menu option to the Site Actions menu will not only be convenient for site administrators, it’s pretty easy to implement in a SharePoint feature.  This new View All Site Content link on the Site Action can be secured in a manner that best suits your needs.  In the solution sample I provide, this new View All Site Content link on the Site Actions menu is only visible to users who have the “AddAndCustomizePages” right which allows designers and administrators to see it, but is not visible to typical users of a site.

    There are plenty of examples on how to add a custom item to the Site Action menu so I will not cover that in any detail here, but the solution sample I provide does include all the code – and the nice thing is, it isn’t much code.

    Installation and Activation

    Basic Install Steps:
    1 - Add the solution using the STSADM command: stsadm -o addsolution -filename [path]\VASCSiteAction.wsp
    2 - Deploy the solution using the STSADM command: stsadm -o deploysolution -name VASCSiteAction,wsp -allowgacdeployment -immediate -allcontenturls
    3 - Optional - to restart IIS: iisreset /noforce

    Activating the new feature:
    1 - Navigate to the site you want to hide the View All Site Content link. 
    2 - Go to the Site Settings for that site (Site Actions > Site Settings). 
    3 - Click the Site Features (not the Site Collection Features) link under the Site Administration section. 
    4 - Activate the new feature named "Hide the View All Site Content link".

    Your View All Site Content link should now be hidden and the View All Site Content link should now appear in the Site Actions menu.

    Conclusion

    The result is a single feature that a site administrator can activate and deactivate on any web site to hide and show the standard View All Site Content link in the quick launch navigation.  Additionally, it adds a useful new View All Site Content to the Site Actions menu that is visible only to users having the AddAndCustomizePages right on that site.

    References:

    Enjoy!

    Customizing the WSS 3.0/MOSS 2007 Menu Control -- MossMenu source code released

    The AspMenu class that ships with WSS 3.0 (and by extension MOSS 2007) is nearly identical in behavior to ASP.NET 2.0’s Menu class (as the name implies). AspMenu derives from Menu and adds tweaks to work around a few reasonably well known annoyances and provides improved highlighting support.

     

    Unfortunately, this class was marked sealed and is therefore not eligible to be used as the base class for derived types. Effectively, this means that customers cannot inherit the additional functionality of the AspMenu class when trying to provide further customization of the menu.

     

    We realized this problem too late in the release process and were unable to remove the sealed marker from the AspMenu class that ships with WSS. However, we are instead providing the source code for that class here (as an attachment to this blog entry) under the name MossMenu.

     

    Note: MossMenu is provided as is and will only work on sites built with WSS 3.0 or MOSS 2007. MossMenu relies on some JavaScript which has been included along with the C# source. This is really just for completeness’ sake [aside: some trival about the use of the apostrophe for the possessive forms of nouns] as this script is automatically included on most pages through the core.js script include reference.

     

    Issues with the ASP.NET 2.0 menu, which have been worked around:

    1)     If the mouse pointer happens to be hovering over a menu item that exposes a fly-out as the page is loading, it is possible that an error dialog will appear stating: "Internet Explorer cannot open the Internet site, Operation aborted" and a blank page will be shown upon clicking OK. It seems that the problem arises from attempting to append to the DOM before it is properly initialized.

    2)     If SSL termination is employed on a site with a menu, users will be greeted with “This page contains both secure and nonsecure items. Do you want to display the nonsecure items?” when hovering over a menu item which exposes fly-outs. (http://support.microsoft.com/?id=910444)

    3)     In right-to-left locales, the fly-out indicator arrow still points from left-to-right.

     

    Improvements to default highlighting behavior of ASP.NET 2.0 menu:

    ·         When hooking the menu up to a SiteMapProvider through a SiteMapDataSource, the menu automatically highlights the node that matches that returned by the provider’s CurrentNode property. However, if the particular node returned by CurrentNode is not shown by the menu nothing will be highlighted at all. The improved behavior determines if there is an ancestor of the current node which is displayed in the menu and highlights this node instead.

     

    Hope this helps.

     

    Chris Richard, Software Design Engineer, WCM Features

    Back to Basics: Connecting to Project Server (video)

    If you are a project manager who wants to create a project using Project Server 2007, you have two ways of connecting to it. You can connect directly using a Web browser and a URL given to you by an administrator, or you can connect through Project Professional 2007 on your desktop, which is explained explain in this video.

    http://office.microsoft.com/en-us/project/HA102910371033.aspx?pid=CH100948801033

    Thanks
    Waqas Sarwar

    Posted by Heather O'Cull at Friday, November 07, 2008 11:09 PM

    TechNet Security Resource Center for SharePoint Products and Technologies

    Hey Guys!

    Just launched today: Security Resource Center for SharePoint Products and Technologies

    This page provides IT pros with security resources for Windows SharePoint Services 3.0 and Microsoft Office SharePoint Server 2007. 

    image

    Thanks
    Waqas Sarwar

    Special thanks to  chrisfie for this entry at Christophe Fiessinger’s Blog on November 13, 2008, 8:35pm

    PM Boot Camp: Up to speed with Project 2007

     
    Hi Guys!
     
    If you're new to Project 2007, or even new to project management in general, the Up to speed with Project 2007 video series might be the basic training you're looking for. This six-part series covers the basic elements of project management and the Project 2007 interface, as well as how to start a new project, create relationships between tasks, use calendars, build a team, identify project costs, check project progress, and generate reports. The entire series can be viewed in less than an hour, providing a quick way to ramp up and get started managing your projects using Project 2007.
     
    Thanks
    Waqas
    Special thanks to Heather O’Cull this entry at Microsoft Office Project 2007 on November 12, 2008, 6:55pm

    See whats new at Michael Jordan's Series of Presentations

    Hey Guys!
     
    Michael Jordan, a Lead Architect at Microsoft, has been delivering a great series on Project Server 2007. In the series, he presents on the aspects to consider when you evaluate, plan, deploy, and operate Project Server 2007. You can register for the upcoming webcasts and catch up on the ones you have missed at the Microsoft Project Webcasts page.
    Thanks
    Waqas
     
    Special thanks to Do More Than Manage for this entry, released on November 12, 2008, 12:00am

    How to deploy cumulative updates for Project Server 2007

    The TechNet team has just published this key article Deploy cumulative updates (Project Server 2007)

    Please read this article prior to deploying any Project Server Cumulative Update.

    As a reminder the last cumulative update was released on October 28th: Announcing the release of the October Cumulative Update for Project and Project Server 2007

    Thanks
    Waqas Sarwar

    Special Thanks to Christophe Fiessinger for this Blog, released on November 13, 2008, 8:41pm

    Configure PDF IFilter in WSS 3.0

    There are various posts around on setting up MOSS 2007 to use the PDF IFilter, and some stuff on Windows SharePoint Services 3.0 as well.  I’ve found a method which works for me, so I wanted to put this together in one place - not least of all so I can find it when out on site with a client. 

    Out of the box neither WSS 3 nor MOSS 2007 will index content located in Acrobat PDF files, so you need to set up the IFilter.  I’ve also found that that PDF files loaded prior to the installation of the filter won’t be re-crawled automatically, so to be on the safe side you might want to kick off a full crawl.

    Here is what I’ve found works for WSS 3.0:

    1. First, you need to download the Adobe PDF IFilter 6.0, which you can find at this URL.  You should also get hold of a suitable Icon to use with PDFs, so that when they are listed in a document library they are easily recognisable.  There is a 17 x 17 one available on the Adobe web site here.
    2. Once you’ve downloaded the IFilter, install it on your WSS 3.0 server, and then follow the instructions on registry settings in Microsoft KB Article 927675.  I’ve always found that providing the Adobe IFilter installed properly, the only setting I need to add is the Search Extensions one listed in step 2.  Also note step 5 re stopping and re-starting the search service.
    3. Now you need to set up the Icon file.  If you downloaded the icon file in step 1 above, you will have a file called pdficon_small.gif.  You need to copy this onto your WSS 3.0 server, into drive:\Program Files\Common FIles\Microsoft Shared\Web Server extensions\12\TEMPLATE\IMAGES.
    4. Next you need to edit the XML file which WSS uses to link file extensions to icons.  This file is called DOCICON.XML and is located at drive:\Program Files\Common FIles\Microsoft Shared\Web Server extensions\12\TEMPLATE\XML.  Navigate to that folder and locate the file.  I would suggest making a backup copy first, then opening the file in NotePad.  You need to add a mapping key for PDFs at the bottom of the file, above the </ByExtension> closing tag.  The new key will be <Mapping Key=”pdf” Value=”pdficon_small.gif” OpenControl=”"/>  (note that XML is case sensitive so make sure you use same case as previous entries).  Then save the file.
    5. That’s pretty much it, but if you already have PDFs uploaded to your WSS server I would recommend starting a full crawl.  You can do the with STSAdm, the command syntax is Stsadm -o spsearch -action fullcrawlstart .  More on this on TechNet here.

    Thanks
    Waqas Sarwar

    Special Thanks to Worker Thread

     

    Microsoft Ramp Up Program: Just Launched SharePoint for Developers Track

    The Ramp Up program (www.MyRampUp.com)  has just launched a brand-new learning track: SharePoint for Developers, Part I today. This includes:

    • Level 1: Web Parts
    • Level 2: Data Lists
    • Level 3: Event Handlers
    • Level 4: Workflow
    • Level 5: Silverlight Web Parts

    Ramp Up is a free, online, community-based program that can help users save time in learning Microsoft technology. The easy-to-access content (provided by subject-matter gurus) is specifically tailored to the Ramp Up program, and offered in a variety of forms (whitepaper, v-lab, codecast and slidecast). This SharePoint track, along with the other currently offered tracks (eg, Visual Studio 2008), teaches the important skills in a guided path, making the learning process easier and more efficient. Currently, there are no assessments in the program, so it’s quicker than ever to graduate and receive the reward (25% off on certification and 50% off on e-Learning - only for graduates of Ramp Up).

    image

    Thanks
    Waqas Sarwar

    Originally by chrisfie from Christophe Fiessinger’s Blog on November 6, 2008, 3:58am

    Announcing the Microsoft patterns and practices: SharePoint Guidance

    This is a great assets for all SharePoint and Project Server developers: http://microsoft.com/spg

    Overview

    This guidance helps architects and developers build SharePoint intranet applications. A reference implementation (RI) demonstrates solutions to common architectural, development and lifecycle management challenges.
    This guidance discusses the following:

    • Architectural decisions about patterns, feature factoring and packaging.
    • Design tradeoffs for common decisions many developers encounter.
    • Implementation examples demonstrated in the RI and in the QuickStarts.
    • How to design for testability, create unit tests, and run continuous integration.
    • Set up of development, build, test, staging, and production environments.
    • Managing the application life cycle including upgrade.
    • Team-based intranet application development.

    image

    Regards
    Waqas

    Originally by chrisfie from Christophe Fiessinger’s Blog on November 6, 2008, 3:58am

    Enforcing MS Project Settings using Group Policies

    Microsoft have released new contents regarding using Active Directory GPO to enforce settings. The process can be used for Microsoft Project 2007 deployment to standardize the usage of the tool.

     In a MS Project Server 2007 EPM environment, there are settings your should check or uncheck based on how you are planning to use the system. Standardizing those settings make it easier from the user experience of the tool & make things easier for later issues.  

    Review the following links for details.

    Best Regards
    Waqas Sarwar


    src="http://pagead2.googlesyndication.com/pagead/show_ads.js">div>

    Originally from MS Project Server on November 3, 2008, 5:34pm

    10 Signs You Don't Really Know Microsoft Project

    You manually create a Project Summary Task
    Wrong:

    Wrong1


    2.  You "hard code" dates

    Wrong:

    Wrong4


    3.  You don't input the teams estimated Duration on all tasks

    Wrong:

    Wrong5


    4.  Your tasks don't start with a verb


    5.  You assign Predecessors to Summary Tasks

    Wrong:

    Wrong6


    6. You assign Resources to Summary Tasks

    Wrong:

    Wrong7


    7.  You never inspect the critical path tasks

    8.  You never search for (or eliminate) Resource Over-Allocations

    9.  You never Baseline your schedule

    10. You never update your schedule to align with reality
     
    Best regards
    Waqas Sarwar
     
    Special thanks to http://www.pmconnection.com/modules.php?name=News&file=article&sid=32 for this outstanding post.

    25 Microsoft Project Tips and Tricks

    25 Microsoft Project Tips and Tricks

    The following is a collection of Tips and Tricks for Microsoft Project that we have accumulated over the years and teach in our training classes. Unless otherwise noted, these tips and tricks work with all versions of Microsoft Project.

    1. In the Gantt Chart, doubleclick on the right edge of a column header to "best fit" the column.

    2. To quickly change the name of a column, doubleclick in the column header and enter a new name for the field in the Title field. For example, you may want to abbreviate the Duration field name to Dur to allow the field to be narrower.

    3. To quickly change the field in a column, doubleclick in the column header and select the new field from the Field Name list. While in the Field Name list, press the first letter of the desired field to go to that field.

    4. In the Gantt Chart Table (or any table), to quickly hide a column, click on the right edge of the column header and drag it to the left until it disappears (becomes a 0 width column). To display this hidden column, place the cursor a little to the right of the column separator bar where the column used to be, click and drag to the right.

    5. You can wrap text in the Gantt Chart to display text on multiple lines if you increase the row height. To increase the row height, place the cursor between any two row numbers (if the ID field is displayed in the first column and is "locked"), click and drag down to increase the row height. Only Text fields wrap and only if the column is narrower than the text in the field.

    6. When printing Gantt Charts (or other timescaled charts) you can adjust the width of the timescale to fit the page without changing the timescale units. Doubleclick on the Timescale and increase the number in the % field (or Enlarge field in some versions of Project) to make the timescale take up more of the page or decrease the number in the % (or Enlarge) field to make the timescale narrower. The latter step is useful when a chart is just a little too wide to fit on a page.

    7. To select two or more non-adjacent tasks, click on a task (in the table area), hold down the Ctrl Key and click on another task in the chart. Continue holding the Ctrl key to select other tasks. This is especially useful for linking or unlinking tasks that are not on consecutive rows.

    8. To change information for a number of tasks at once, highlight the desired tasks (select non-adjacent tasks using the method described above) and select the Task Information button. Enter the common information in one of the fields displayed in the "Multiple Task Information" dialog box.

    9. To remove a date constraint from a task, select the task (or multiple tasks) and select the Task Information button. Click in the Advanced tab, change the Type field to As Soon As Possible and click OK. This removes any date constraint in the task and allows it to be scheduled based on the dependencies rather than a date entered (perhaps accidentally) by a user.

    10. If a task does not move (reschedule) based on a dependency, it may contain a "fixed" date of some kind. A fixed date could be an Actual Start or a constraint such as Must Start On or Start No Earlier Than. Use the Tasks with Fixed Dates Filter to view only those tasks in a plan that contain fixed dates. You can then determine if these tasks should have these types of fixed dates. Use the previous tip to remove an unwanted constraint.

    11. If after removing the Actual Start and any constraint (such as Must Start On or Start No Earlier Than) a task still does not reschedule based on a dependency, check the Resource Leveling feature. Make sure Automatic Leveling is turned off by selecting Resource Leveling from the Tools menu and choosing Manual. If a task still does not move, it may contain a delay based on a previous Resource Level. Select Resource Leveling again from the Tools menu and choose Clear Leveling. Select whether or not to remove Leveling from the selected tasks or for the entire project.

    12. After applying a Filter in a Gantt chart press F3 to view all tasks again instead of applying the All Tasks filter.

    13. Press Alt-Home in the Gantt chart to position the chart on the start of the project.

    14. If you have indented tasks to create Summary Tasks and Detail Tasks, click the little box with the minus sign to the left of the Summary Task name to quickly hide the detail tasks below it. Click the box with the plus sign to display the detail tasks that were hidden.

    15. In the Gantt chart, you can create dependencies by clicking on the Gantt bar of a task and dragging to another Gantt bar to create a Finish-to-Start dependency between the two tasks.

    16. To quickly modify or delete a dependency, doubleclick on the dependency line between the two tasks to display the Task Dependency form (be sure to place your cursor directly on the dependency line).

    17. In any drop down list such as the list of Resource Names or the list of Filters you can press the first letter of the item you are looking for to quickly go that item.

    18. Use the Insert key on your keyboard to quickly insert rows and columns. In the Gantt chart, click on a row and press the Insert key to insert a blank row above the selected row. Click on a column header to highlight a column and press Insert to insert a column to the left of the selected column. You can also use the Delete key to reverse this process but be careful…

    19. In the Network Diagram (or PERT Chart in some versions of Project), to move multiple task boxes, click in the chart area, drag the cursor to select any number of boxes and release the cursor. Then, click on the border of a box and drag the entire selection of boxes to a new location. In Project 2000, 2002 and 2003 you must first select the Format menu, Layout and then Manual Box Positioning to enable the ability to move task boxes around. 

    20. An often overlooked but handy report is the Calendar view using a Resource Filter. Select Calendar from the View menu. Select the Using Resource… Filter and type in the name of the desired resource to display the Calendar for a particular resource. This produces a nice printout of a resource’s tasks with each month of a project on a separate page.

    21. For Project 2000, 2002 and 2003, to prevent an item from appearing in the legend for the Gantt  chart, select the Format menu, Bar Styles and place an asterisk (*) before the name of the item that you do not want to appear. In Project 98 you can delete the bar styles you do not use to avoid displaying them in the legend.

    22. Right click in the Toolbar area to display the list of available Toolbars. A check next to a Toolbar indicates that it is currently displayed. Click on a Toolbar to display or hide it.

    23. In the Gantt Chart (or any chart with a table and a chart area) doubleclick the separator line between the table and chart to automatically push the separator line to the closest column edge.

    24. To split the screen and place a specific View into the lower pane, hold the shift key while selecting an item from the View menu. You can also split the screen by selecting Split from the Window menu or doubleclick the small horizontal split bar in the lower right corner of the screen. Doubleclick it again to remove the split (or choose Remove Split from the Windows menu).

    25. Just for fun - Create two 10 day tasks. Place the cursor in the Finish field of the first task and click the Copy button. Place the cursor in the Start field of the second task and select Paste Special-Paste Link from the Edit menu. Place the cursor on the Finish field of the second task and click the Copy button. Place the cursor on the Start field of the first task, select Paste Special-Paste Link and watch the tasks "walk" across the chart. Delete one of the tasks to stop.

    We hope you have found these tips and tricks useful. If you have a tip that you would like to share, please send it to us and we will gladly add it to the above list the next time we update it. Send all Tips and Tricks to: info@criticaltools.com

    Thanks

    Waqas Sarwar

    This post is orginally from http://www.criticaltools.com/Tips.htm

     

     

    Prepare for the Upcoming Office SharePoint Server 2007 and Windows SharePoint Services 3.0 Service Pack 2

    We’re pleased to announce that Service Pack 2 (SP2) for the 2007 Microsoft Office system is expected to be released in the near future.  Although we aren’t yet announcing the exact release date, it will fall between February and April of 2009.

     

    Historically, we have waited to communicate details about service packs until their release (or very shortly before).  As we communicated with SP3 for Office 2003 and SP1 for the 2007 Office System, we will be taking steps to increase transparency and visibility into the Office servicing model at the request of our customers.  To that end, we would like to start sharing some details into what will be included in SP2 for the 2007 Office system.  This is by no means an exhaustive list of everything included in this service pack and we will share more details prior to the final release, but we want to start communicating to customers what they should be aware of at a high level. 

     

    To be fair, this is not the first time we have talked about SP2.  Several months ago, we announced that we’ll be further demonstrating our increased commitment to interoperability by including support for Open Document Format (ODF), XML Paper Specification (XPS), and Portable Document Format (PDF) in SP2.  In addition to those file format additions, some other highlights that you’ll find in SP2 include:

     

    For Office Desktop Programs:

    ·         Improved Outlook Calendaring Reliability

    ·         Improved Outlook Performance

    ·         Enabling Object Model support for Charts in PowerPoint and Word

    ·         Improved cryptographic functionality by supporting all cryptographic algorithms offered by the operating system

    ·         Improved functionality in Excel’s charting mechanism

    ·         Ability to ungroup SmartArt graphics (and as a result, the ability to add animations to them in PowerPoint)

    ·         Ability for Visio to export UML models to an XML file compliant with the XMI standard

    ·         Tool that enables the uninstall of Office client Service Packs

     

    For Servers:

    ·         Performance and manageability improvements to variations in Enterprise Content Management (ECM) including STSADM commands for repairing links between source and target pages

    ·         Improvements around processing status approvals from Office Project Web Access into Office Project Professional 2007

    ·         Improvements to read-only content databases and index rebuild timer jobs in Windows SharePoint Services 3.0

     

    In the coming weeks, individual product teams across Office will begin updating their blogs and highlighting some of the specific work that they’ve included in SP2.  You can find the links to some of the blogs at the end of the post.

     

    In the next few days we will also invite a select set of Office enterprise customers to a private SP2 beta.  From these customers we hope to gather great feedback about the service pack, including areas that we’ll need to improve upon before we release it to the general public.  Based on the success of the SP2 beta program and customer needs, we will certainly evaluate whether to expand this in the future.

     

    Please check back for additional updates!

     

    Thanks,

    Office Service Pack Team

     

    Access Team Blog

    Daniel Escapa’s Blog (OneNote)

    InfoPath Team Blog

    John Guin’s Blog (OneNote)

    Excel Team Blog

    Project Team Blog

    Outlook Team Blog

    PowerPoint Team Blog

    SharePoint Designer Team Blog

    SharePoint Designer Support Blog

    Windows SharePoint Services Blog

    Word Team Blog

     
    Thanks for reading the article and SPecial Thanks to the Microsoft Team.
     
               "Published Wednesday, October 22, 2008 6:04 PM by The Microsoft Office Sustained Engineering Team "
    Regards
    Waqas

    Some AAM guidance from the front lines

    The ISA Server team recently wrote a nice blog post explaining some of the issues you may face when deploying SharePoint in an extranet.  Many of these issues can be avoided by spending some time up front on planning and testing.  Close collaboration between your firewall/proxy administrators and your SharePoint administrators during this phase is often the key to a smooth deployment.  Here are some helpful articles on TechNet to get you started:

    Thanks.
    Waqas Sarwar

    Troy Starr, Windows SharePoint Services:
    Test Published Monday, October 13, 2008 12:56 AM by sptblog

    Announcing New Daylight Saving Time Update for Windows SharePoint Services 3.0

    Daylight Saving Time (DST, in some countries it is called summertime) exists in many countries. The start dates and end dates of DST change from year to year, and countries may change their policies for DST occasionally. This DST update is an effort of SharePoint product team to reflect these new changes. It includes updated time zone definition information for the following countries:

    • Iraq
    • Argentina
    • Chile
    • Iran
    • Morocco
    • Pakistan
    • Venezuela

    For more detail of this update, please refer to

    http://support.microsoft.com/kb/956612

    The update can be download here: x86 x64

    You can always refer to this article for Windows SharePoint Services 3.0 update deployment guidance.

    Special Thanks to Jie Li, Technical Product Manager, SharePoint, Published Thursday, October 16, 2008 10:49 AM

    Announcing August Cumulative Update for Office SharePoint Server 2007 and Windows SharePoint Services 3.0

    The Microsoft Office team has changed the way that it delivers hotfixes for reported problems. This change comes in the form of cumulative updates and critical on-demand hotfixes. The objective is to deliver high-quality fixes in an acceptable time and on a predictable schedule. Cumulative updates are scheduled for every two months, so customers can be better prepared to test and apply new updates. Those who need an emergency fix can request critical on-demand (COD) fix. For information, please refer to http://support.microsoft.com/kb/953878.

    The detail of August Cumulative Update (CU) for Office SharePoint Server 2007 and Windows SharePoint Services 3.0 can be found here:

    Description of the Windows SharePoint Services 3.0 hotfix package (Wssmui.msp): August 26, 2008

    Description of the Windows SharePoint Services 3.0 hotfix package: August 26, 2008

    Description of the SharePoint Server 2007 hotfix package: August 26, 2008

    Customers are not needed to install these updates unless they are affected by specific problems described in the KB articles. And these cumulative updates will be rolled in to Service Pack 2.

    To upgrade from RTM to this new CU, you need to follow the path below:

    1. Windows SharePoint Services 3.0 Service Pack 1

    2. The 2007 Microsoft Office Servers Service Pack 1

    3. the Microsoft Office Servers Infrastructure Update x86 x64

    4. KB 953397: Excel Server Security Update x86 x64

    5. KB 955586: Document Lifecycle Workflow Update

    6. August Cumulative Update for Windows SharePoint Services 3.0 (Global)

    7. August Cumulative Update for Windows SharePoint Services 3.0 (Local)

    8. August Cumulative Update for Microsoft Office Servers

    After applied all these updates, run SharePoint Products and Technologies Configuration Wizard or “psconfig –cmd upgrade –inplace b2b” in command line. This need to be done on every server in the farm with SharePoint installed.

    The version of databases should be 12.0.6327 after all these updates.

    For a better guided update process, customers would also like to check out the following guides. These articles provide a correct way to deploy updates, as well as known issues and how to do slipstream builds.

    Deploy software updates for Windows SharePoint Services 3.0

    http://technet.microsoft.com/en-us/library/cc288269.aspx

    Deploy software updates for Office SharePoint Server 2007

    http://technet.microsoft.com/en-us/library/cc263467.aspx

     

    Thanks Jie Li Technical Product Manager, SharePoint for this Nice Post, Published Monday, September 29, 2008 12:23 PM

    Project Server 2007: Moving a copy of Production to Test – Part 2

    I will be going deeper in this posting, particularly on the scenario of moving just the databases and then re-provisioning the site.  But don’t expect me to be mentioning every single dialog box and permission that you require.  I will be writing at a level whereby if you don’t understand what I am saying then perhaps you shouldn’t be doing this – or at least you need to read around a bit and then come back.  For permissions see this blog posting, and for full details of full farm restore go here.  Remember that any additional Process Accounts added to the SSP must still exist and be verifiable in the new system.  Forgotten this one?  Then go here.

    So the only extra I intend to say about full farm backup and restore is that it does not keep such things as LDAP forms based authentication extended sites and settings (Thanks Boris Bazant for this tip!).  As I mentioned in my part 1 post – some external customization will need to be re-applied (e.g. additional web parts, server side event handlers in the GC).

    The scenario for the main part of the post is moving from my Production Server (BriSmith620) to my test system (A Hyper-V image called BriSmithV0832).  I already have a working site which I don’t want to break, so this is a partial move – and the projects in my Production Server have workspaces both in the root site under PWA (the instance I am interested in is actually called CAL – created to troubleshoot some Calendar issues)  and in another web application at Port 94.  So I will be moving over 4 project databases and 2 content databases.  I can’t move my port 80 to port 80 as it will break existing stuff – so I will move 94 to 94 and 80 to 8080.  I have Issues lists with items in several projects – the aim will be to see these still working post migration…

    I’ve already backed up my 6 databases – and restored them with names Blog_Archive etc for the Project ones and Blog_80_Content and Blog_94_Content (actually on the same server with different names) so on with the restoration of my PWA site and content.  First I just provision a site against the 4 databases.  If you have restored the content db at this point it will fail – if you use the same name for the site – as a collection will already exist.  And if you delete the site away goes your content – Catch 22.  So we are leaving the content stuff for now…

    Usual stuff is entered for creation of a site

    image

    Click OK and wait for it to be provisioned…

    image

    And here we have it!  (Must get round to those timesheets)  Any customizations we had made in SharePoint would be gone (themes, top links etc.) but customizations in PWA would be retained (Notice the My Timecard edit to the menu name in the left nav bar).  But of course none of the workspaces are found, and the issues and risks link also find no active issues for me.

    Next I will add the port 94 content db to a new Web Application on Port 94.  I create a new Web Application and name the database the one I have restored.  Didn’t bother with a screen shot, just changed the port to 94, put in a suitable account for the new application pool and put in the Blog_94_Content database name.  Once this is active I can browse to the workspaces (assuming I know the names) and the issue is there – but clicking through to the issue detail gives a File Not Found SharePoint error.

    image

    The workspaces listed on the home page don’t link to port 94, but port 80, and the Project Workspaces page shows blank for the sites.  By going to the Edit Site Address option the site can be entered for the project.

    image

    Once this is set and the workspace provisioning setting matched to the port 94 address that was in use on the other server the home page then shows the correct links and sees that I have active issues.

    image

    If I follow the link to the workspace, then the issues and click through to the issue detail it works – the file not found is resolved!

    image

    For larger jobs than this simple set of Projects the RelinkAllWSSSite tool from the Project Resource Kit comes in very handy.  Now we have our port 94 sites all sorted – and we could just do the same for our ones that were on port 80 – and leave them on port 8080 – but that doesn’t get them back were they started.  Stsadm export and import comes to our rescue.  First I will add a new web application on port 8080 and use the port 80 content database from the original server.  At this point we can browse to the sites just substituting http://brismithV0832:8080 for http://brismith620 to confirm they are there.  To export and import we use stsadm –o export –url <full url> –filename <path to save site> –nofilecompression.  In this case

    C:\Program Files\Common Files\microsoft shared\Web Server Extensions\12\BIN>stsadm -o export -url "http://brismithv0832:8080/CAL/Project1 with Workspace in PWA" -filename "C\backup\savesite.bak" –nofilecompression

    If on Windows Server 2008 then your command prompt will need to be running as administrator to avoid an Access Denied.

    You will get a long listing of progress (or you can use the –quiet flag) and hopefully it should finish with success!

    Now we can import, just using the default port 80 address to get our site where we want it (just change the URL and export to import.  In my case I can also change CAL to Blog in the URL as my PWA site has changed.  Once this is complete we have the site where we want it – we edit the site address as we did earlier and all should be working!

    image

    image

    Along the way with the export/import we lost the task links – I will dig into this a bit more but I guess you might expect this as the export probably has nowhere to keep that information, and also I see my Active Issues count isn’t picking up the moved workspace issues.  The best approach is certainly keep the workspaces away from your PWA site to start with.  But the issue is still there – it still understand which project it belongs to.

    image

    I’ve stepped through with a single project so you understand the idea – you can speed things up with Powershell or just creating a batch file.  If you go this route then stsadm –o enumsubwebs –url <url where sites are> >> c:\sitelist.txt will enable you to get a quick list of sites into a text file.

    Every requirement will be slightly different – full farm backup/restore will hopefully work for most, but the details I’ve given here should help when you want perhaps a partial move of single instances.  Always consider customization too – usually you will need some manual steps for those.

    Let me know how this works for you.

    Thanks Brian Smith's for this outstadning Blog: Posted on Friday, September 26, 2008 6:58 AM

    Announcing the release of the August Cumulative Update for Project and Project Server 2007

    The Microsoft Office team has changed the way that it delivers hot fixes for reported problems by moving away from the current priority-driven hot fix release model to a scheduled delivery model. This change comes in the form of cumulative updates and critical on-demand (COD) hotfixes. The objective is to deliver high-quality fixes in an acceptable time and on a predictable schedule-every two months so its creates more predictability for customers.

    Customers who need an emergency fix can request a shorter turnaround time for a COD hotfix.

    Please refer to the following knowledge based article for more information: http://support.microsoft.com/kb/953878

    The August Cumulative Update (CU) for Project 2007 and Project Server 2007 (as well as the rest of the Office suite) is the first CU release. Releases will now happen very two months so the next ones are scheduled for October 08, December 08, etc…

    Install or not to Install?

    Our general guideline for applying hotfix is:

    • Each hotfix package is intended to correct only the applications that are listed in the knowledge base article.
    • Apply the packages only to systems that are experiencing these specific problems.
    • If you are experiencing any of the two known issues described in KB 953750 (Infrastructure Update).
    • If you are not severely affected by any of these problems, we recommend that you wait for the next 2007 Office suites service pack that contains the hotfixes in these cumulative update packages.
    • If additional issues occur or any troubleshooting is required, you might have to create a separate service request.
    • The usual support costs will apply to additional support questions and issues that do not qualify for a specific cumulative update package. To create a separate service request, visit the following Microsoft Web site: http://support.microsoft.com/contactus/?ws=support

     

    Installation Order

    Assuming you are running the released version of Project Server 2007, here is a high level procedure, please refer to the TechNet articles for detailed deployment steps:

    Step

    Related Links

    1. Deploy Service Pack 1

    Announcing the release of EPM 2007 Service Pack 1 (includes links to KB, downloads and deployment documentation)

    Deploy Service Pack 1 for Office Project Server 2007

    2. Deploy the Infrastructure Update (IU). We recommend deploying the IU first because you will get all the latest updates for WSS and SharePoint Server.

    Announcing the availability of the Project and Project Server 2007 Infrastructure Update

    Microsoft Project Infrastructure Update Webcast Slides

    Deploy the Infrastructure Update for Office Project Server 2007

    Install the Infrastructure Update for Microsoft Office Servers (Office SharePoint Server 2007)

    3. Deploy the August Cumulative Update. Since the August CU are individually package (one EXE for Project Server and another one for SharePoint Server for instance), then you will have to deploy each one depending on the hotfix required.

    4. Run hotfix EXE

    5. Run PSCONFIG on each server within your farm to finalize the update

    6. Verify Installation by verifying the version of each of the four PS database using the following command:

    SELECT * FROM VERSIONS

    Result should be: 12.0.6327.5000

    See links below for KB and download location.

    Ideally Project Professional 2007 and Project Server 2007  should be on the same version but it is not a requirement:

    • Project + IU with Project Server + IU + August CU
    • Project + IU + August CU with Project Server + IU

     

    Knowledge Base Articles and Downloads

    Title

    ID

    KB URL

    Download URL

    Cumulative update packages for August 2008 for the 2007 Microsoft Office core suite applications and 2007 Microsoft Office servers

    957022

    http://support.microsoft.com/kb/957022

     

    Description of the Project 2007 hotfix package: August 26, 2008

    956060

    http://support.microsoft.com/kb/956060

    http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=956060

    Description of the Project Server 2007 hotfix package: August 26, 2008

    956061

    http://support.microsoft.com/kb/956061

    http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=956061

    Description of the Windows SharePoint Services 3.0 hotfix package: August 26, 2008

    957109

    http://support.microsoft.com/kb/957109

    http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=956057

    Description of the SharePoint Server 2007 hotfix package: August 26, 2008

     

     

    Thanks for the Post:Provide best practices as well as tips and tricks on Microsoft Enterprise Project Management (EPM)

    Microsoft Project Server 2007 IT Professional TechNet Webcast Series

    I just wanted to pass on word that starting October 1st, 2008, Michael Jordan (Lead Architect – MCS EPM Global Practice | WW COE for EPM) will present a series of Project Server 2007 webcast on TechNet targeted at IT Professionals

    These 60 minutes webcasts will present in details key aspects to consider when you evaluate, plan, deploy, and operate Project Server 2007 specifically:

    ·         Solution Overview and System Elements

    ·         Solution Elements and Data Flow

    ·         Workload Scenarios and Reference Architecture

    ·         Network Communication

    ·         Server Administration

    ·         Maintenance and Monitoring

    ·         Deployment into a SharePoint Server Intranet Farm

    ·         Disaster Recovery

    ·         Virtualization

     

    You need to register for the free of charge webcast by clicking the link; then you get emailed a link to sign on and participate in the web cast on its date and time (please note only the first two webcast are available for registration at this stage).

    Each TechNet webcast is recorded for later viewing which should be through the same registration URL.

    For a listing of all EPM webcasts on TechNet check the following: http://www.microsoft.com/events/series/epm.aspx

     

    Webcast Title

     

    Abstract

     

    Date

     

    Microsoft Office Project Server 2007 - Solution Overview and System Elements

     

    In this webcast, we introduce the Microsoft Office Project Server 2007 solution and the main product components. We describe key concepts such as high availability and scalability, which should be taken into account when planning and deploying Project Server 2007. This introductory webcast is part of a webcast series targeted at IT professionals. In the series, we present in detail key aspects to consider when you evaluate, plan, deploy, and operate Project Server 2007. We discuss the main considerations when planning for high-availability deployments—when to scale up and out, points of failure, and software/hardware boundaries.

     

    Wednesday, October 1, 2008

     

    11:00 A.M.–12:00 P.M. Pacific Time

    Microsoft Office Project Server 2007 - Solution Elements and Data Flow

     

    In this webcast, we describe the elements of the Microsoft Office Project Server 2007 solution (Microsoft Office Project Professional 2007, Application Server, Microsoft SQL Server), and we cover Data Flow components and key areas for scalability. This webcast is part of a webcast series targeted at IT professionals. In the series, we present in detail key aspects to consider when you evaluate, plan, deploy, and operate Project Server 2007. We discuss the main considerations when planning for high-availability deployments—when to scale up and out, points of failure, and software/hardware boundaries.

     

    Wednesday, October 22, 2008

     

    11:00 A.M.–12:00 P.M. Pacific Time

    Microsoft Office Project Server 2007 - Workload Scenarios and Reference Architecture

     

    This webcast covers Microsoft Office Project Server 2007 Workload Scenarios and Reference Architecture to help you plan your deployment. We discuss typical product operations broken out by user roles and how it affect performance.  We present typical reference architecture based on key capacity planning characteristics.  This webcast is part of a webcast series targeted at IT professionals. In the series, we present in detail key aspects to consider when you evaluate, plan, deploy, and operate Project Server 2007.

     

    Wednesday, November 12, 2008

     

    11:00 A.M.–12:00 P.M. Pacific Time

    Microsoft Office Project Server 2007 - Network Communication

     

    This webcast covers Microsoft Office Project Server 2007 Network Communication and specifically ports, protocols and network traffic. We present network considerations when deploying Project Server and Project Professional 2007, this includes an overview of the Project Professional's Active Cache mechanism.  This webcast is part of a webcast series targeted at IT professionals. In the series, we present in detail key aspects to consider when you evaluate, plan, deploy, and operate Project Server 2007.

     

    Wednesday, December 3, 2008

     

    11:00 A.M.–12:00 P.M. Pacific Time

    Microsoft Office Project Server 2007 - Server Administration

     

    This webcast covers Microsoft Office Project Server 2007 Server Administration best practices. We discuss SharePoint's Central Administration, Shared Service Provider Administration and Project Web Access Administration.  This webcast is part of a webcast series targeted at IT professionals.  In the series, we present in detail key aspects to consider when you evaluate, plan, deploy, and operate Project Server 2007.

     

    Wednesday, January 14, 2009

     

    11:00 A.M.–12:00 P.M. Pacific Time

    Microsoft Office Project Server 2007 - Maintenance and Monitoring

     

    This webcast covers Microsoft Office Project Server 2007 Maintenance and Monitoring best practices. This session will cover maintenance plans that should be put in place as well as performance counters that should be monitored.  We also discuss how to deploy software updates for both Project Server and Project Professional 2007. This webcast is part of a webcast series targeted at IT professionals. In the series, we present in detail key aspects to consider when you evaluate, plan, deploy, and operate Project Server 2007.

     

    Wednesday, February 25, 2009

     

    11:00 A.M.–12:00 P.M. Pacific Time

    Microsoft Office Project Server 2007 - Deployment into a SharePoint Server Intranet Farm

     

    This webcast covers Microsoft Office Project Server 2007 Deployment best practices into a SharePoint Server intranet farm (out of the box Project Server 2007 is deployed on top of Windows SharePoint Services V3). We discuss SharePoint Server deployment pre-requisites, deployment scenarios and best practices. This webcast is part of a webcast series targeted at IT professionals. In the series, we present in detail key aspects to consider when you evaluate, plan, deploy, and operate Project Server 2007.

     

    Wednesday, March 18, 2009

     

    11:00 A.M.–12:00 P.M. Pacific Time

    Microsoft Office Project Server 2007 - Disaster Recovery

     

    This webcast covers Microsoft Office Project Server 2007 Server Disaster Recovery options and best practices. We discuss how to recover from a catastrophic failure on your SharePoint/Project Server far;, this includes what are the options to recover from a loss of any component of your SharePoint/Project Server farm: SQL server, Application Server, Disk etc … We present farm and database restore options.  This webcast is part of a webcast series targeted at IT professionals. In the series, we present in detail key aspects to consider when you evaluate, plan, deploy, and operate Project Server 2007.

     

    Wednesday, April  8, 2009

     

    11:00 A.M.–12:00 P.M. Pacific Time

    Microsoft Office Project Server 2007 - Virtualization

     

    This webcast covers Microsoft Office Project Server 2007 Server Virtualization best practices using Windows Server 2008's Hyper-V. We discuss deployment best practices with respect to virtualization, including optimum architecture configuration (which component should be deployed on a  virtual environment and which ones should be deployed on a physical environment), and how to architect a high availability virtual farm.  This webcast is part of a webcast series targeted at IT professionals. In the series, we present in detail key aspects to consider when you evaluate, plan, deploy, and operate Project Server 2007.

     

    Wednesday, April 29, 2009

     

    11:00 A.M.–12:00 P.M. Pacific Time

     

    Michael Jordan’s Biography

     

    Michael Jordan is the Lead Architect for Microsoft Services’ EPM Global Practice and member of the World Wide Center of Excellence. Michael has been with Microsoft for 8 years serving in technical roles from Application Development, Systems Engineering, SQL Database and Project Management. He has been working with EPM for the last 4 years architecting, troubleshooting and implementing large deployments at priority customer sites. As a member of the EPM Global Practice he performs a role as an extension to the Product Group by providing field feedback, spec reviews, product guidance and running customer programs for marketing initiatives.

     

    Key Resources

    Enterprise Project Management

     

    ·         EPM Connect: The Business Exchange for EPM Solutions and Services

     

    ·         EPM University: Online, instructor-led, deep dive technical training on EPM

     

    ·         EPM Solution Office online EPM Home Page

     

    Project Desktop

     

    ·         Easier with ProjectProject Desktop Home Page

     

    ·         Microsoft Project on Office Online

     

    IT Professionals

     

    ·         Project TechCenter on TechNet

     

    ·         Project Portfolio TechCenter on TechNet

     

    Developers

     

    ·         Project Developer Home Page

     

     

     

    Thanks to robert.m.hoover for this post, which is posd on  Wednesday, September 24, 2008 9:30 PM