Hands-On: Forefront Identity Manager 2010 RC1 Demo VHD Walkthrough

Quick Start: FIM 2010 RC1 Demo VHD Image with Setup Notes

Overview

A ready-to-run Virtual Hard Disk (VHD) image containing Forefront Identity Manager (FIM) 2010 RC1 configured for demo/testing. Includes preinstalled components (FIM Service, Portal, Synchronization Service) and sample data to explore core features like user provisioning, synchronization rules, and workflows.

System requirements

• Host OS: Windows 7 / Windows Server 2008 R2 (Hyper-V enabled) or any hypervisor supporting VHD.
• CPU: 2+ cores (4 recommended).
• RAM: 4 GB minimum (8 GB recommended).
• Disk: 40 GB free for VHD and snapshots.
• Network: NAT or bridged networking; static IP recommended for services.

Preparation steps

1. Verify host hypervisor support — ensure Hyper-V or other hypervisor supports VHD images.
2. Download VHD — obtain the demo VHD from a trusted source; verify checksum.
3. Create a new VM — attach the VHD as the boot disk. Configure CPU, RAM, and network per requirements.
4. Set networking — assign static IP or ensure DHCP provides consistent address; update DNS if needed.
5. Snapshot — take a snapshot/checkpoint before making changes.

First boot checklist

• Log in with provided demo credentials (check accompanying README).
• Confirm Windows activation / evaluation status.
• Start/verify services: FIM Service, FIM Synchronization Service, IIS (for Portal).
• Check event logs for startup errors.

Common post-deployment tasks

• Change default passwords for demo accounts.
• Set correct time zone and system time.
• Configure service accounts if you want to integrate with a production AD.
• Update SSL bindings in IIS if accessing the portal over HTTPS.
• Import/export management policies (MPs) to experiment with sync rules and workflows.

Troubleshooting tips

• If FIM services fail to start, check SQL Server connectivity and service account permissions.
• Synchronization issues: review miisclient logs and Synchronization Service Manager for error details.
• Portal errors: verify IIS application pool identity and account membership in FIM groups.

Security notes

• Treat demo images as untrusted—change passwords and remove any leftover test accounts before connecting to production networks.
• Disable unnecessary external network access if using the VHD in insecure environments.

Backup & cleanup

• Take a snapshot after configuring a working baseline.
• To revert testing changes, restore the snapshot rather than modifying the base VHD.

If you want, I can produce a one-page printable checklist or step-by-step commands for a specific hypervisor (Hyper-V, VMware, VirtualBox).