RDCSite Tool for Microsoft Project Central 2000 — Setup, Tips & Best Practices
What RDCSite Tool is
RDCSite is a third‑party utility written to extend Microsoft Project Central 2000 (the web-based front end for Project Server 2000). It automates common site management tasks, streamlines deployment of project sites, and can assist with templating, permissions, and bulk operations that the out-of-the-box Project Central interface handles slowly or not at all.
Setup (assumes Windows Server + Project Central 2000 environment)
-
Prerequisites
- Windows Server (same era OS: e.g., Windows ⁄2003 compatible).
- Microsoft Project Central 2000 / Project Server 2000 installed and configured.
- Administrative access to SharePoint (Project Central uses SharePoint Team Services) and Project Server.
- Backup of Project Server databases and SharePoint site collections.
-
Install
- Place RDCSite installer or files on the server with Project Central.
- Stop relevant IIS services (or put site in maintenance) to avoid conflicts.
- Run installer as an administrative user, following prompts to point the tool at the Project Central site URL and Project Server database if required.
- If the tool uses service accounts, configure credentials with least privilege necessary.
- Restart IIS and validate the tool’s services/processes are running.
-
Initial configuration
- Connect RDCSite to the Project Central site: enter site URL and admin credentials.
- Configure default templates, site naming conventions, and any folder mappings.
- Set logging level and retention for audits.
- Test against a non-production site or a test project first.
Common Uses & Features
- Create or provision project team sites in bulk from templates.
- Apply consistent permissions across project sites.
- Bulk import/export site content or configurations.
- Synchronize lists, calendars, and document libraries between project sites.
- Clean up orphaned or stale project sites.
- Automate repetitive site administration tasks via scheduled runs or scripts.
Tips
- Test first: Always validate actions on a test Project Central instance or a single project site before bulk operations.
- Keep backups: Export site templates and back up SharePoint/Project Server databases before major changes.
- Use templates: Standardize templates for lists, libraries, permissions, and web parts to ensure consistency.
- Run off-hours: Schedule heavy operations during low usage windows to minimize service impact.
- Audit logs: Enable detailed logging during initial runs, then reduce verbosity once stable.
- Least privilege: Give service accounts only the permissions they need; avoid running as full domain admin.
Best Practices
- Maintain a versioned library of site templates and configuration scripts so you can roll back changes.
- Document naming conventions, permission roles, and template contents for your team.
- Regularly review and remove unused project sites to reduce clutter and maintenance overhead.
- Automate recurring maintenance tasks (site cleanup, permission audits) but keep alerts so admins approve destructive actions.
- Combine RDCSite operations with Project Server housekeeping: archive old projects, shrink databases, and apply SharePoint updates.
- Keep the environment patched—use compatible OS and SharePoint updates according to your enterprise policy.
Troubleshooting (quick checklist)
- Connection failures: verify site URL, credentials, and network connectivity; confirm IIS and Project Server services are running.
- Permission errors: ensure the service account has required SharePoint and Project Server rights.
- Template application issues: check template compatibility, feature activation, and web part availability.
- Performance problems: stagger bulk jobs, monitor server resources, and consider running smaller batches.
If you want, I can:
- Provide a concise runbook for a safe bulk site-provisioning operation, or
- Draft sample PowerShell/command steps (compatible with a ⁄2003-era environment) to automate a common RDCSite task. Which would you prefer?