Daniel Bell's avatar

posted by
3421 views

Microsoft Project 2010 Overview PowerPoint Deck

reposted, Thanks to Christophe's blog

 
  • Microsoft Project 2010 Overview - OFS214
    This session provides an overview of the key investment areas and capabilities of Project Server 2010 and Project Professional 2010, including demand management, portfolio analysis, time tracking, and reporting.
  • Microsoft Project Server 2010 for IT Professionals and Developers - OFS206
    This session provides details of what Project Server 2010 offers IT professionals and developers, including new features for easier deployment and management, and developer-related enhancements across Server and Client.

 

The files can be downloaded here.

image


anonymous's avatar

posted by
3790 views

How to move a sub Project Workspace to another programme site

This is a helpful blog link for Sub-Project workspaces - check it out.


Daniel Bell's avatar

posted by
15830 views

Task Statusing and the new Grid

Posted from Microsoft Project Team Blog A few weeks back Patrick Conlan posted an overview of some of the Time Tracking investment areas for Project Server 2010. Today we are going to drill in on one such investment area, na ...


Daniel Bell's avatar

posted by
3425 views

Project Server 2010 Portfolio Analysis

Posted from Microsoft Project Team Blog In Project Server 2010, a rich set of new Portfolio Strategy features are now available in the core Project Server product serving to more closely unify project and portfolio managemen ...


Daniel Bell's avatar

posted by
1518 views

Portfolio Server 2007 Gateway Gotchas

Portfolio Server 2007 Gateway GotchasCASE 1: They are in different domains, you need to use PS forms authentication and to specify the credentials in Project definition page.

 

CASE 2: I If both PPS and PS are on the same machine and only 1 ssp is defined in central admin, no extra configs in PS  need to be done.

 

CASE 3: If both PPS and PS are on the same machine but there are 2 ssps defined in central admin, you need to follow 1. ii) step and add as a user “Network service”

 

1. Project Server Configuration for PPS integration

- If PS is located in a different and untrusted domain, no project server configuration should be made.

- If PS is located in the same domain as PPS, there are 2 scenarios that can happen:

i. PPS application pool is running under a domain account, follow these steps:

a. Enter Central Administration page – Shared Services Administration

b. Edit Shared Services properties 

c. Add the domain account that’s running PPS app pool into Process Account with access to this SSP field

d. Press OK. Then go to 2. Project Server Management, to add this project server in PPS.

 

 

ii. PPS application pool is running under Network Service

a. Enter Central Administration page Application Management

b. Click on Grant or Configure Shared Services between farms

c. Select This farm will provide shared services to other farms

d. In Provide Shared Services to users for the specified SSP, add the <domain>\<PPS machine>$.

e. Press OK. Then go to 2. Project Server Management, to add this project server in PPS.


Daniel Bell's avatar

posted by
1792 views

Cloud Tag Issue

posted from Telligent forums

The day, I upgraded the Community Server 2007 to 2008 in IIS7 (Windows Server 2008), and encountered one problem. The tag cloud links became ooo+xxx when the tag include space character. Of course, the link was broken.

The message from IIS as below

Untitled

Most likely causes: The request contained a double escape sequence and request filtering is configured on the Web server to deny double escape sequences.

Things you can try:Verify the configuration/system.webServer/security/requestFiltering@allowDoubleEscaping setting in the applicationhost.config or web.confg file.

The discussion in the Telligent is as windows server 2008 - IIS7 - tags with space in name give 404.

The the clear steps as this KB.

  1. Locate the following directory: %windir%\System32\inetsrv\config
  2. Open the applicationHost.config file in a text editor such as Notepad.
  3. In the applicationHost.config file, locate the following code:
    <section name="requestFiltering" overrideModeDefault="Deny" />
  4. Replace the code that you found in step 3 with the following code:
    <section name="requestFiltering" overrideModeDefault="Allow"/>
  5. Locate the following diretory:
    %windi%\System32\com
  6. Double-click the directory of the SOAP-enabled server that you want to activate.
  7. Open the web.config file in a text editor such as Notepad.
  8. In the web.config file, locate the following code:
    </configuration>
  9. Replace the code that you found in step 8 with the following code:
    <system.webServer>
    <security>
    <requestFiltering allowDoubleEscaping="True"/>
    </security>
    </system.webServer>
    </configuration>


Daniel Bell's avatar

posted by
3840 views

Allow log on through Terminal Services

posted from TechNet

Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2

Allow log on through Terminal Services

Description

This security setting determines which users or groups have permission to log on as a Terminal Services client.

Default:

  • On workstation and servers: Administrators, Remote Desktop Users.
  • On domain controllers: Administrators.

Configuring this security setting

You can configure this security setting by opening the appropriate policy and expanding the console tree as such: Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment\

For specific instructions about how to configure security policy settings, see Edit security settings on a Group Policy object.

Important

  • This setting does not have any effect on Windows 2000 computers that have not been updated to Service Pack 2.

image

 

 

Edit security settings on a Group Policy object

Updated: January 21, 2005

Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2

 

To edit a security setting on a Group Policy object

Choose the appropriate environment for which you want to edit a security setting:

For your local computer

  1. Open Local Security Settings.

     
  2. In the console tree, click Security Settings.

     
  3. Do one of the following:

    • To edit Password Policy or Account Lockout Policy, click Account Policies.

       
    • To edit an Audit Policy, a User Right Assignment, or Security Options, click Local Policies.

       
  4. Double-click the security setting in the details pane that you want to modify.

     
  5. Modify the security setting, and then click OK.

     

Notes

  • To perform this procedure, you must be a member of the Administrators group on the local computer, or you must have been delegated the appropriate authority. If the computer is joined to a domain, members of the Domain Admins group might be able to perform this procedure. As a security best practice, consider using Run as to perform this procedure.

     
  • To open Local Security Policy, click Start, point to Settings, click Control Panel, double-click Administrative Tools, and then double-click Local Security Policy.

     

For a Group Policy object, when you are on a workstation or server that is joined to a domain.

  1. On the taskbar, click Start, point to Run, type mmc, and then click OK.

     
  2. In the console, on the File menu, click Add/Remove snap-in.

     
  3. In Add/Remove Snap-in, click Add, and then, in Add Standalone Snap-in, double-click Group Policy Object Editor.

     
  4. In <


Daniel Bell's avatar

posted by
1734 views

Using a Custom Group with Project Server 2007

http://integent.com/Blog/tabid/142/entryid/2/Default.aspx