I would like to install the EMC on a WinXPProSP2-32bit (mobile?) PC that is not a member of a domain, nor is the current user - but has sufficient administrator/OS privileges to do so, but is a member of a workgroup (for 'home' networking, etc.), so that it could administer an Edge Transport E2k7 Srv that is also not in a domain/Enterprise AD environment (mostly for test purposes) via (eg.) VPN through the internet either accessing the Srv directly (if allowed? - RAS) or via its workgroup/local network/subnet - containing a RAS Srv. I have followed the above instructions, believing that I have satisfied all the necessary prerequisites, to get the following window: http://photos.orange.co.uk/shared/photo.html?c_photo=1084123266 On continuing with the custom install of the EMC, I get the following errors: http://photos.orange.co.uk/shared/photo.html?c_photo=1084123263 Namely: 1. Active Directory does not exist or cannot be contacted. Recommended Action. 2. This computer is not part of a Windows domain. 3. The user is not logged on to a Windows domain. 4. Warning: Setup cannot verify that the 'Host' (A) record for this computer exists within the DNS database on server 192.168.0.1. At the time of EMC installation attempt, the PC was a dhcp-enabled client on the home network (workgroup) set to obtain its IP address (IPv4) automatically from a Win2kAdSrv providing internet access to the home network via ICS (simplified NAT) - no address reservations present. The PC can also connect directly to the internet via a usb/adsl modem, without being connected to the home network, but this still doesn't allow installation of the EMC giving similar errors to those above. Please could you tell me if this installation route is allowed/possible and what steps I should take to successfully install the EMC (E2k7). Regards

I do not think it is possible to do this - some time back we had someone else on these forums with the same requirements and the only solution / work around for them was to join the workstation to the domain, install EMC then disjoin the domain. The thinking here is that Setup checks A/D for Exchange Org Objects and Exchange Server Objects during the install process. If you would like to try another option (doubtful of it workig but worth a try), you could change the FQDN of the workstation to match that of your domain, my computer properties > Computer Name > Change > More > primary dns suffix. then connect to your vpn before running setup so that the ip in use is of your local network. If it still cannot see your internal DC's & DNS though, I doubt it will work.