I hvae just upgraded from SCCMR3 on a 2003 X86 server to SCCMR3 on a 2008 X64 server and now i have no 'unknown computer collection' What i have done so far was: Backup old site server Install SCCM R2 on new server Installed prerequisite hotfix for R3 Tried to install R3 but got an error 'Setup was unable to create unknown machines. 0x80070003' which turned out to be fixed by doing the following http://social.technet.microsoft.com/Forums/en-US/configmgrsetup/thread/4b000774-42e5-4db4-aa17-661eb582c460/ Tried to install R3 again and got the error “Setup was unable to update the sms_def.mof file” which i fixed by copying the \inboxes\clifiles.src\hinv folder from the backup to C:\Program Files (x86)\Microsoft Configuration Manager\inboxes\clifiles.src\hinv Then i finally installed R3 and it finished successfully Now when i go in to the Console i get no 'unknow computers' collection, one other thing i have noticed is in the console if i go to 'Tools' then 'Configmgr Service Manager' i get a message 'error communicating with the specified Configmgr Site Server' Any ideas??

'error communicating with the specified Configmgr Site Server' Any chance that this error is related to SPNs http://blogs.technet.com/b/configurationmgr/archive/2010/10/26/troubleshooting-duplicate-or-missing-spns-for-a-configmgr-2007-sql-database.aspx ? In addition, to be sure that R3 was installed without any problem, you can check ConfigMgr2007R3.log under %temp% Bechir Gharbi | http://myitforum.com/cs2/blogs/bgharbi/default.aspx

well i have narrowed down the issue slightly. if i install SQL then SCCM then R3 i can go to in the console if i go to 'Tools' then 'Configmgr Service Manager' i get a DONT get the error message 'error communicating with the specified Configmgr Site Server' If i then do the restore of the old database from the 2003 server i then have the issues as outlined previously. so i am thinking it might not be an issue with SCCM itself as it seems to work when installed but more to do with the restoration of the backup. Any Ideas????

well built a new server and started from scratch seems the issues all stemmed from the programe files director and programe files (X86) directory and how the thing gets all confused.. Advise if you are upgrading from 203 32bit to 2008 64bit dont do it or just start from scratch and use the same site code.

If you migrate from x86 to x64, you still have teo stick to Program Files folder (without (x86)). R3 then gets confused and will look for binaries in (x86). Just make a link to the proper folder with: mklink /D „C:\Program Files (x86)\Microsoft Configuration Manager” „C:\Program Files\Microsoft Configuration Manager" R.E.M. - YEAH!