move ocs 2007 r2 from 2003 to 2008 server

Thanks for info (not easy to find it) will give it a go and let you know.
I was told we can't afford Lync licenses so most likely will be enrolling wildfire/open fire and asterisk to replace ocs (not sure if it integrates with exchange's free busy but again we may be using different mail server by then).

Thanks,
I have follow your advice and now have 2x standard ocs (1 pool each). Do you have any idea no how to safely transfer response groups across to new server?
Used ApplicationSettingsExport.exe but its all or nothing (can't test it on single response group and then repeat process for remaining 156 groups).

1. Do I need to change pool name to <pool>pool2</pool> when restoring to new server?
2. Do you know if  /restore requires AD/network presence (would like to do the restore/import while server is disconnected, disable all RGS and plug in to LAN again. That would allow me to move them one by one when convenient.
Thanks,

in my memory, you can "copy paste" to the new pool so both of them will exist

the response group (in my memory) only applies to the user in the pool it exist.

so you can move a test user to pool2 and test it, but of all RSG need to go in 1 go.

thanks,
1. do you remember by any chance if it was
lcdscmd

"C:\Program Files\Common Files\Microsoft Office Communications Server 2007 R2\LCSCmd.exe" /config /action:export
 /level:global,pool,machine /configfile:c:\temp\ocs_server_ocs_pool_export.xml /L:c:\temp\ocs_server_ocs_pool_export_log
.html

Select allOpen in new window

or
ApplicationSettingsExport

"C:\Program Files\Microsoft Office Communications Server 2007 R2\ResKit /ApplicationSettingsExport.exe" /backup /pool:poolA /app:Microsoft.Rtc.Applications.Acd /file:settings_file.xml

Select allOpen in new window

and then

"C:\Program Files\Microsoft Office Communications Server 2007 R2\ResKit /ApplicationSettingsExport.exe" /restore /app:Microsoft.Rtc.Applications.Acd /file:settings_file.xml

Select allOpen in new window

copy paste or both?

I have 2 standard servers so 2 separate pools. I know user of serverA/poolA can be member of response group on serverB/poolB.
2. Do I risk damaging my environment by importing RGS with exactly same name to serverB/poolB?
3. Do I need to import sql databases as well or can it be ignored?
Thanks,

RGS consist of agent groups, queues, and workflows so it could potentially handle calls and etc.

ApplicationSettingsExport backup the settings on the original servers. So, if anything really goes wrong, you will need to drop both (old and new) and restore the original (old).
meanwhile, i don't have a ocs 2007r2 anyway to test this so you are on your own on this.

at the moment, it is always risky so plan it during a weekend to perform such task.

hello,
we end up hiring 3rd party expert to do it for us.
in general we had to:
1. run lcdscmd to export/import pool settings (changed pool details by editing export file)
2. run ApplicationSettingsExport.exe to export RGS objects (groups and worklows) also changing destination pool details.

It moved objects across but unique attributes from objects were removed (e.g. phone No, line uri).
3. created new contact object on the new server (so receiving calls as uri works but phone No calls would not)
4. removed contact's phone No from existing RGS
5. adding contact phone No to contact on the new server.
6. removing contact from old server
Steps 3,4,5,6 needs to be repeated for every RGS

lacking some technical info but in general that's what needs to happen