Now a days i noticed taht lot of people have question about the creation of Enterprise Custom Field in Project Server 2007. Now finally Microsft add this topic into their Office Learning Material. I hope you will enjoy this stuff(Thanks to Microsoft Enterprise Project Management Content Publishing team for the updating.)

Create a custom field  

Use this article to learn how to create, import, insert, and rename a custom field.

Watch this: Create a custom field 

This video walks you through the process of creating a custom field that is associated with a list, and that uses graphical indicators.

Work with the Gantt Chart view 

This article provides information on how to use each part of the Gantt Chart view.

Project Server Quick Reference Guide for project managers 

This quick reference guide displays all the tasks a project manager is likely to do with Project Server. A team member version is due out soon.

Podcast: Britney Spears, the ultimate project manager

This is a link to an external podcast about Britney Spears as the ultimate project manager. It is a bit tongue-in-cheek, but makes good points about project management skills in general.

What’s all this talk about Web 2.0

This Office Hours article discusses Web 2.0 and software plus services model.

There are a number of factors that dictate how Microsoft Project “thinks”.

The two main factors are:

• The Scheduling Formula
• The Task Type

The Scheduling Formula leverages three variables:

• Units - The percentage of time required by a resource or resources to complete the task
• Duration - The number of working days required to complete the task
• Work - The effort required to complete the task

Many people say that the scheduling formula is: Units x Duration = Work

When you initially assign a Resource to a Task, this is the formula that is leveraged. Let’s demonstrate:

We will create Task 1 that is 5 days in Duration

 

We will now assign a Resource to this task

As soon as we assign this Resource to this task, Work changes to 40 hours.

Here is the how that number was calculated:

Units x Duration = Work
100% x (5*8) = 40
Or
100% x 40 = 40 hours

But using simple math, we can re-write our equation to solve for a different variable.

Our original formula solves for Work:
Units x Duration = Work

But we could re-write the formula to solve for Units:
Work / Duration = Units

Or we could re-write the formula to solve for Duration:
Work / Units = Duration

So we have shown that The Scheduling Formula can actually be written three different ways:

Units x Duration = Work
Work / Duration = Units
Work / Units = Duration

Now let’s prove that Microsoft Project also thinks this way.

In order to demonstrate this, we must introduce The Task Type or the Type field:

By default, Type is set to Fixed Units. But there are actually three different Task Type variables:

• Fixed Duration
• Fixed Units
• Fixed Work

 

Now to test Microsoft Project

Using our original scenario, let’s force Microsoft Project to solve for Duration.

 

We will leave Type set to Fixed Units and change Work to 80 hrs

Here is how Duration was calculated:

Work / Units = Duration
80 / 100% = 80
Or
80 / 100% = (80 / 8)
Or
80 / 100% = 10 days

 

Returning to our original scenario, let’s force Microsoft Project to solve for Work.

Leave Type set to Fixed Units and enter 10 days Duration

Here is how Work was calculated:

Units x Duration = Work
100% * 10 days = 80
Or
100% * 10 days = (10 * 8)
Or
100% * 10 days = 80 hours Work

 

Returning to our original scenario, let’s force Microsoft Project to solve for Units

Change Type to Fixed Duration and enter 20 hours Work

Here is how Units was calculated:

Work / Duration = Units
20 / 5 days = 50%
Or
20 / 5 days = 20 / (8 * 5)
Or
20 / 5 days = 20 / 40
Or
20 / 5 days = 0.5

 

To Review:

There are three different Task Types:

• Fixed Units
• Fixed Work
• Fixed Duration

There are three different variables of the Scheduling Formula:

• Units
• Work
• Duration

Depending upon how the Task Type is set in combination with which Scheduling Formula variable is altered dictates which variable Microsoft Project solves for.

The Task Type and Scheduling Formula Cheat Sheet will help you control how Microsoft Project “thinks”:

See The Microsoft Project Task Type and Scheduling Formula Cheat Sheet here.

See this article in Slide format here.

See this article in Video format here.

Purchase “The Cheat Sheet” Mouse Pad here.

• Watch this: Use lag and lead timeThis demo shows how to use lag and lead time to create gaps and overlaps between tasks in a project.
• Watch this: Show the critical pathThis demo shows you several ways to display a project’s critical tasks. It also shows how to display multiple critical paths in a single project.
• Create work breakdown structure (WBS) codes This topic has been updated with more information about basic view usage.
• Set lead or lag time (float) between tasks This topic has had a number of terms added to make it more searchable from the perspective of the PMBOK.
• Use templates in Project 2007 More information on templates.
• Create a custom field   Use this article to learn how to create, import, insert, and rename a custom field.
• Watch this: Create a custom field  This video walks you through the process of creating a custom field that is associated with a list, and that uses graphical indicators.
• Work with the Gantt Chart view  This article provides information on how to use each part of the Gantt Chart view.
• Project Server Quick Reference Guide for project managers  This quick reference guide displays all the tasks a project manager is likely to do with Project Server. A team member version is due out soon.
• Podcast: Britney Spears, the ultimate project manager This is a link to an external podcast about Britney Spears as the ultimate project manager. It is a bit tongue-in-cheek, but makes good points about project management skills in general.
• What’s all this talk about Web 2.0 This Office Hours article discusses Web 2.0 and software plus services model.

 

 

 

This Include the following Topics:

 

1. Work with document libraries

2. Work with calendars

3. Work with slide libraries

4. Work with workflows

5. Work with Excel Services

 

 

 

 

The HotFix Package Covered the following Issues:

 

You click to select the Restrict Updates to Project Web Access check box in Project Web Access (PWA). Then, if you manipulate some data in Project Professional, you may experience the following symptoms:

• The data is de-synchronized between the client and the server. 
• Additional actual work is added for resources. 
• In the timephased data in the Resource Usage view, the work total is not updated correctly.
• If you change the size of some lookup table rows, the data of any existing customized field is corrupted.
• You have a blank row between tasks. When you copy and paste the tasks, the blank row is removed. Therefore, Project automatically re-creates predecessor links. However, the links are incorrect.
• Enterprise outline codes are not displayed correctly when the default currency is Turkish.
• Project 2007 may close unexpectedly (crash) when you open a project that has AutoFilter enabled.
• The Visual Basic for Applications (VBA) property Assignments.UniqueID does not work in Project 2007.
• The Beforeassignmentchange event does not occur in Project 2007.
• Task updates are submitted to a project manager other than the designated status manager.

 

 

 

Hey Guys,

 

I come to know lot of people facing problem at morning time when first user access the Sharepoint / PWA / WSS sites, its take a long time to display the page.

Normally IIS discards its cache overnight, which means that each Sharepoint site must be rebuilt the first time it is accessed. This can be very slow. This script will seek out every site and site collection on a sharepoint server, and send them an HTTP request, so that the site remains in cache.

 

 

You must run this application on a machine that has WSS or MOSS installed.
If you want to wake up a single site, you do not need sites.conf and it can be safely deleted.
If you need to wake up mulitple sites, list them in sites.conf, each on their own line.

The app recognizes 3 option switches (the switches can appear in any order):
-verbose --Displays the raw HTML of each site as it is woken.
-site:XXX.XXX -- specifies the starting URL. If you do not set anything, the app looks for sites.conf, and uses the sites listed there. If sites.conf does not exist, the default URL http://localhost is used.
-discover -- Searches the local server for all web applications.
-log:Filename -- specifies a log file to record the results. If a file is not specified, the log will be displayed on the console.

Examples:
spwakeup.exe
If the file sites.conf does not exist, runs against http://localhost. Displays log results on console.

spwakeup.exe -verbose -log:c:\log.txt -site:http://portal.mycompany.com
Runs against http://portal.mycompany.com. Displays verbose results. Stores results in c:\log.txt.

 

 

 

Avoid that COLD, SLOW request that baffles users...

Ever thought things on ASP.NET were a bit slow the first time accessing them?  Many of you are aware that ASP.NET from a web admin perspective know that things have to recompile and things just aren't as fast the first time.  In fact some times things are incredibly slow the first time and are incredibly slow.  Ever had users say, for some odd reason some times when I hit my SharePoint site it takes 30 seconds to load, then after a refresh it goes sub second, even clearing their cache the page is fast.  That's because it's not a user issue, its simply compiling, caching, etc... on the server after an IISReset or app pool reset or worker process cycle.

If you're doing demos of an ASP.NET app such as WSS or SPS or Office SharePoint Server 2007, or you simply want your home page to load faster after an IISReset so it's not your users hitting the page for the first time, you may be *very* interested in this post. 

The scripts attached to this post are warm up scripts.  I did not write them.  I asked the guy (Bryan Hart) who built our awesome VPCs (virtual images) if he wrote them.  He did some work on them, but he doesn't claim to have originally authored them.  They are shared via the SharePoint beta 2 Resource DVD (handed out at TechEd 2006 and the World Wide Partner Conference as part of the SharePoint Server VPC image.  I think they're super cool so I'm attaching them for use on your environments.  None of the scripts are compiled so you can feel free to modify them, make them even greater and share them back out to the world. 

Let's say you know that you cycle your app pools at 1am, what if you executed this script to "warm up" the common pages following the cycle?  I'm sure you'll find other creative uses of this script outside of demos which is our most common usage of this script.  I do recommend you compare an iisreset and hit your home page, then try an iisreset and run this script then hit the page.  HUGE difference.  I personally think the warmupscript is more efficient than a browser request in terms of "warming" things up.

Here's the gist of the attached batch and command line executed vbscript...

In the words of the script itself... "This script will run stsadm to warmup the admin interfaces [and] hit each page in the portal to force their JIT."

warmupserver.zip contains the following 3 files:

Startup.bat - Calls the warmupserver.cmd script and passes in the servername parameter (modify this to fit the hostname of your server)

Warmupserver.cmd - checks for servername parameter then leverages the HttpRequest.vbs script to hit the relevant admin pages (change the pages and ports to the relevant ones)

HTTPRequest.vbs - This script executes an HTTP query using the XMLHTTP object

 

Added 8/21:

I recommend checking out some additional tips on this topic from Andrew Connell

I'd say these tips are beyond just for developers.  It's very efficient to cycle just an app pool, or isolate a worker process and kill the process rather than cycling IIS.

I also recommend having the path to the /bin directory in your path variables. (More insight in andrew's post.

One of the first things I do when installing a sharepoint server is creating a command short cut to the bin directory, even though I like to have it in my path.

1. Right click desktop, choose "shortcut"

2. Put in this path: "c:\winnt\system32\cmd.exe" click next

3. Enter "STSADM" or shortcut to bin or something like that and click "next" (Now you've got a command prompt looking icon on your desktop)

4. Choose the new icon on the desktop.  Right click choose properties, change "start in" path to the path to the bin directory: "c:\Program Files\Common Files\Microsoft Shared\web server extensions\12\bin" (path may be slightly different based for x64)

Double click the shortcut...  You now are at the path where you can run stsadm commands, prescans, etc...

 

Dwonload the Attachement Click here:

 

Office Online has a new commenting feature that I mentioned in an earlier post about Community Tips. When you have questions or advice about the content you find, you can sign in with a Windows Live ID and post questions or bits of advice for the rest of the community. It’s similar to comments on a blog, except that Community Tips comments are not actively monitored by the authors. That said, it’s a way to have a conversation that’s focused on content such as articles and templates.

Why mention it again? My earlier post mentioned how you could only comment in select areas of the site. Now you can comment on all types of content from Help articles to training and templates. However, the feature is not on some pages, such as home pages or search results pages. You have to be deeper down, for example, on an actual article page like the Roadmap for using SharePoint Server 2007. If you need a visual, here’s a quick video of how to submit a tip for a template on Office Online:

Office Online Community Tips about templates

Go ahead and try it out.

Orginaly this blog from Matt Evans Published Thursday, September 11, 2008 9:39 PM

Thanks

Waqas

This Utility from EchoTechnology is awsom, Called Sharepoint Spy tool.This powerful free tool will allow you to spy into the internal data of SharePoint and compare the effects of making a change. Sharepoint Spy also allows you to compare settings between sites, lists, views, etc helping you troubleshoot configurations

For more information and freely download this tool from http://www.echotechnology.com/products/spy

In secured environments, these controls might not have been downloaded and the user might be prevented from downloading them because of security restrictions. You must download and enable these controls on the client for these features to work. The ActiveX controls reside in two .cab files that are located on your Project Server site in the following folder: C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\LAYOUTS\PWA\OBJECTS\1033 The following are the two .cab files: Pjclient.cab Pjcintl.cab (in the 1033 subfolder or other language folders) These two cab files contain the following files: Pjcintl.cab: langcabENU12.inf (This file is not required to manually install controls.) Pj12ENUc.dll Pjclient.cab: Microsoft.vc80.crt.manifest (This file is not required for the manual installation of controls.) Msvcr80.dll Pjgrid12.ocx Pjprint12.dll Pjquery12.ocx Pjres12c.dll Pjtextconv12.dll To enable client-side controls: 1. Log on to the client computer as Administrator. 2. Connect to the Project Server, and then copy the Pjclient.cab file and the Pjcintl.cab file from the following folder: C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\LAYOUTS\PWA\OBJECTS\1033 3. Paste the files in a folder on the computer. 4. Double-click the Pjcintl.cab file to open it, and then click the Pj11enuc.dll file. 5. On the File menu, click Extract. 6. Expand My Computer, expand Local Disk, expand Windows, and then click Downloaded Program Files. 7. Click Extract. 8. Close the Pjcintl.cab file. 9. Double-click Pjclient.cab to open it, and then click Select all on the Edit menu. 10. On the File menu, click Extract. 11. Expand My Computer, expand Local Disk, expand Windows, and then click Downloaded Program Files. 12. Click Extract. 13. Close the Pjclient.cab file. 14. Click Start, click Run, type CMD, and then click OK. 15. Type CD %windir%\Downloaded Program Files, and then press ENTER. 16. Type regsvr32 pj12enuc.dll , and then press ENTER. 17. Type regsvr32 pjres12c.dll, and then press ENTER. 18. Type for %i in (pj*.dll) do regsvr32 %i, and then press ENTER. 19. Confirm that registration was successful in each window that opens. Click OK to close each regsvr32 window. 20. Type for %i in (pj*.ocx) do regsvr32 %i, and then press ENTER. 21. Confirm that registration was successful in each window that opens. Click OK to close each command window.

Microsoft SharePoint Team Blog

Today represents the start of a new era in Enterprise Content Management (ECM) interoperability as Microsoft, EMC and IBM announced a jointly developed specification that leverages SOAP, REST and Atom to enable communication with and between ECM systems.  The new specification known as Content Management Interoperability Services (CMIS) defines a platform and language independent means of accessing ECM repositories and will be submitted to OASIS for advancement through its rigorous standards development process.

As well as enabling communication between ECM systems, CMIS will also enable rich, content centric applications and mashups to be developed independent of the underlying storage repository.  For more details, you can download a draft of the specification or take a look at Ethan's post on the ECM team blog.

Ryan Duguid
Technical Product Manager
Microsoft Corp

Thanks

Waqas

 

Microsoft announced the latest Infra Structure update and it contains a fixes to the claimed bugs.

For more details please visit MSDN Official blog for Project 2007

To download this infrastructure you can follow this link . Install Infrastructure update for Project Professional

Thanks & regards

Waqas Sarwar

Ryan Korock from F5 has shared the following suggestions when discussing load balancing for Project Server:

• Load Balancing Method - Because of the nature of HTTP, any of the load balancing methods will work fairly well (this is not always true for other protocols). I suggest using least connections or predictive, as they start to take into account system performance when determining where to send the next connection.
• Persistence – Although most Project Server deployments do not require persistence (aka stickyness), there is a small benefit of enabling it. A SharePoint server does build a small cache, and so getting sent to the same server as before may generate a small performance gain. I recommend using ‘cookie’ persistence, which will persist a user based upon http cookies. BIG-IP allows you to create a ‘backup’ method of source IP based persistence, which is also recommended.
• Health Monitoring – I always recommend monitoring the servers at an ‘application layer’. This means building an http based monitor for the Project Server, which can give us more insight into the server health, beyond just a ping or tcp port check.

g F5 hardware for load balancing the following are  recommended by Ryan:

• Cookie persistence is a great way to make sure http users are resuming their sessions on the same front end they were originally sent to
• Least Connection load balancing is also great option for sending new users to the currently least utilized servers

Last but not least F5 and HP have also published a recent study that could be of interest depending on your deployment topology: Deploying F5 Networks BIG-IP Local Traffic Manager with WebAccelerator for Microsoft Office SharePoint Server 2007

Originally by chrisfie from Christophe Fiessinger’s Blog on April 22, 2008, 5:54pm