Microsoft Project 2010 Evaluation: Installation Pack and Demo Configuration GuideMicrosoft Project 2010 remains a useful example of a mature project management tool — especially for organizations that need to support legacy environments or want to compare older approaches to scheduling and resource management with modern offerings. This guide walks through obtaining and preparing an evaluation installation pack, installing Project 2010 for demonstration purposes, configuring a realistic demo environment, and tips for testing core features so stakeholders can assess fit and limitations.
Overview and objectives
This article helps you:
- Prepare an installation pack suitable for evaluation and demo use.
- Install Microsoft Project 2010 (standalone and as part of Office/Project Server scenarios).
- Configure a demo environment that highlights scheduling, resource management, reporting and Project Server integration.
- Run targeted demo scenarios and tests to evaluate functionality, performance, and compatibility.
Target audience: IT evaluators, project managers, trainers, and consultants who must demonstrate Project 2010 capabilities or validate compatibility with existing systems.
Pre‑installation planning
Before downloading or deploying anything, collect requirements and constraints:
- Supported OS: Project 2010 client is supported on Windows Vista SP2, Windows 7, and corresponding server OSs for Project Server components. Ensure demo machines run a compatible OS and have the latest service packs.
- Hardware: For smooth demos, use machines with at least dual‑core CPUs, 4 GB RAM (8 GB recommended for VM images), and SSDs if available. Project Server requires more resources.
- Licensing and evaluation keys: Obtain an evaluation key or licenses from your organization’s volume licensing portal or Microsoft’s evaluation center (historical note: Project 2010 evaluation media was available from Microsoft; if you don’t already have legal media, use licensed sources).
- Network & domain: Decide whether demos will run in a workgroup, domain, or inside isolated virtual network. Project Server demos work best in domain-joined environments.
- Dependencies: Office 2010 compatibility, SharePoint Server 2010 (for Project Server), SQL Server ⁄2008 R2 for Project Server databases, and IIS on the server role.
Create an installation checklist that includes OS patches, prerequisites (e.g., .NET Framework 3.5 SP1), SQL Server connectivity, and backup snapshots for VMs.
Building the Evaluation Installation Pack
An evaluation installation pack should be reproducible, contain installers, configuration scripts, sample data, and a demo playbook.
Contents to include:
- Installers: Project Professional 2010 (32‑bit and/or 64‑bit where applicable), Project Server 2010 components, Office 2010 installer if needed.
- Service Packs & Updates: At minimum include Project 2010 SP1 and the latest cumulative updates available for 2010 products.
- Prerequisite installers: .NET Framework 3.5 SP1, Visual C++ runtimes, SQL Server Express/Full installers for test DBs.
- Configuration scripts: PowerShell scripts or batch files to automate IIS settings, service accounts, registry tweaks, and Windows features required.
- Sample files: Several Project (.mpp) schedules of varying complexity, resource pools, baseline data, timesheets templates, and example SharePoint/Project Server content.
- Demo playbook: Step‑by‑step scenarios, expected outcomes, trouble‑shooting tips, and timing notes for a 15‑minute, 45‑minute, and 2‑hour demo.
- Virtual machine images (optional): Preconfigured Windows images with Project/Project Server installed to save demo setup time. Keep licensing compliance in mind.
Packaging: Use ISO images or compressed archives. Include a README with system requirements, installation order, and any required license keys or trial activation steps.
Installation: Client (Project Professional 2010)
- Verify OS readiness: Apply Windows updates and install .NET 3.5 SP1.
- Choose bitness: Most Office suites of that era were 32‑bit; installing 64‑bit Project while 32‑bit Office exists is not supported. Match bitness to installed Office.
- Run setup: Launch setup.exe from the Project installer. Enter product key when prompted (use evaluation key if available).
- Customize (optional): In setup customization, choose features such as Visual Reports, SharePoint synchronization, or VBA support depending on demo needs.
- Apply Service Pack 1 and cumulative updates after installation.
- Activate/Trial: If using evaluation media, activate or start the trial period per Microsoft’s instructions.
Post‑install checks: Open a sample .mpp, verify Gantt Chart rendering, task details, resource sheet, and Visual Reports export to Excel/Visio.
Installation: Project Server 2010 (high‑level)
Project Server 2010 relies on SharePoint Server 2010 and SQL Server. For demo purposes you can install Project Server on a single server (standalone) or distribute roles across VMs.
High‑level steps:
- Prepare the server: Install Windows Server (2008 R2 recommended), join domain, install latest updates.
- Install SQL Server ⁄2008 R2 and configure instance. Create service accounts with least privilege for SQL and Project Server services.
- Install SharePoint Server 2010 prerequisites and SharePoint binaries. Configure the SharePoint farm and Central Administration site.
- Run Project Server installation: Choose standalone or farm installation depending on environment. Configure Project Server service applications via SharePoint Central Administration.
- Create the Project Web App (PWA) site collection and configure service application associations.
- Apply Project Server 2010 SP1 and relevant updates.
- Verify by accessing PWA, creating an enterprise project, and connecting a Project Professional client to PWA.
For full steps, follow Microsoft’s documented installation guides; the pack should include a scripted sequence to speed repeatable demos.
Demo environment configuration
Design demos to highlight business value. Configure these areas:
- Enterprise Custom Fields and Views: Create custom fields (cost, priority, customer, risk level) and enterprise views in Project Server to demonstrate reporting and filtering.
- Resource Pool: Create shared resource pool, assign different roles, costs, and availability patterns; include overallocated scenarios.
- Project Templates: Provide 2–3 templates (small IT project, construction milestone plan, and a marketing campaign) with task dependencies, constraints, and baselines.
- Timesheets and Approvals: Enable timesheet submission and manager approval workflows to show governance capabilities.
- Portfolio and Demand Management (if applicable): Add sample requests and show how prioritization and scoring affects portfolio selection.
- Reporting: Configure Visual Reports and Excel Services reports to present dynamic dashboards. Include example dashboards: resource utilization, project health (RAG), and schedule variance.
- Security and permissions: Create groups and permission levels to show role‑based access (Project Manager, Resource, Portfolio Manager, Administrator).
- Backup and rollback: Snapshot VMs and export PWA configuration so demos can be reset quickly.
Include sample user accounts and passwords in a secure README for demo attendees.
Demo scenarios and scripts
Prepare time‑boxed scenarios:
15‑minute quick demo (executive overview)
- Show PWA dashboard with portfolio snapshot.
- Open a sample project in Project Professional, update percent complete for a few tasks, publish, and show immediate dashboard change.
45‑minute functional demo (project manager focus)
- Create a new enterprise project from a template.
- Assign resources from the enterprise pool; introduce an overallocations conflict and resolve using leveling and resource substitution.
- Save baselines, change schedule, show variance and earned value metrics.
- Submit timesheet and walk through approval.
2‑hour deep dive (technical & admin)
- Install/update a Project Server patch (demo the process on a snapshot).
- Modify enterprise custom fields and map to Project templates.
- Demonstrate Visual Reports creation and publish an Excel Services dashboard.
- Show backup/restore of PWA content database.
For each scenario, include expected outcomes, error conditions to demonstrate (e.g., permission errors, mismatch of Office bitness), and checkpoints where attendees can interact.
Testing & evaluation checklist
Use this checklist to evaluate fit:
- Core scheduling: task dependencies, constraints, recurring tasks, critical path calculation (yes/no).
- Resource management: shared pool, leveling, cost rates, availability, overallocations.
- Collaboration: PWA web access, timesheets, alerts/notifications.
- Reporting: Visual Reports, Excel Services, custom exports.
- Integration: SharePoint libraries, Outlook/Exchange synchronization, third‑party add‑ins.
- Performance: Open large .mpp files, publish changes, and measure publish/refresh times.
- Security: Role-based permissions, SSO (if configured), audit logs.
- Maintainability: Patch process, backup/restore, and scalability to more users.
Record results, screenshots, and reproducible steps for any issues found.
Troubleshooting common issues
- Installation fails due to prerequisites: Ensure .NET 3.5 SP1 and required Windows features are installed. Use logs (setup logs and ULS logs for SharePoint) to identify missing components.
- Client/Server bitness mismatch: Install matching bitness or use a matching Office/Project combination.
- Project Professional won’t connect to PWA: Verify network connectivity, service account permissions, and correct PWA URL. Clear Project cache on the client if stale metadata causes problems.
- Performance slowness: Increase RAM on VMs, use faster storage, and review SQL Server indexing and maintenance plans.
- Reporting errors: Ensure Excel Services is configured on the SharePoint farm and that service accounts have the required permissions.
Include pointers to log locations: Project setup logs, SharePoint ULS logs, and SQL Server logs; keep snapshots for recovery.
Security and compliance considerations
- Use least‑privilege service accounts for SQL, SharePoint, and Project Server services.
- For demos on shared networks, isolate VMs or use an internal demo network.
- Remove production data; use sanitized sample data in demos.
- If using evaluation keys, track expiration dates and remove trial installations after evaluation periods to remain compliant.
If the evaluation determines you need a more modern, supported solution, plan migration early:
- Inventory built‑in custom fields, templates, views, and integrations.
- Export enterprise custom fields and project data (PWA export, Project XML, or save .mpp files).
- Map features to a target (e.g., Project Online, Project Server with a newer SharePoint/SQL stack, or alternative PM tools).
- Test migration on a staging environment and validate reporting and resource mappings.
Appendix: sample Playbook excerpt (short)
- Pre‑demo (30–60 min): Boot VMs, verify PWA site health, ensure sample data loaded.
- 15‑min demo script: Show dashboard, make small schedule changes, publish, show dashboard updates.
- Post‑demo: Revert VM snapshot or run reset script to clear demo changes.
This guide gives you a structured approach to building an evaluation installation pack and running meaningful demonstrations of Microsoft Project 2010. If you want, I can create: (a) a downloadable checklist/README file, (b) PowerShell scripts to automate server prerequisites, or © a 45‑minute timed demo script with speaker notes. Which would you like?