fritvet

my guess would be deleting the files in your WSUS download location manually (where all you synchronized updates information is stored). After that you should be able to run a synchronisation again and you can start all over

Hey Iroqouiz, the best approach to include only the computers you want is to have included is to assign static IP addresses to your VMs and then create an IP range boundary in SCCM 2012 where you include the static IP addresses you assigned to your VMs. Also make sure this range isn't inside one of your IP Subnet boundaries from SCCM2012, this might conflict. @Willisj318: I haven't tested yet if it would give any problems, but your machines get detected anyway by SCCM, even if they don't have the client installed so i wouldn't go for setting up the boundaries in 2012 the same as in 2007, just to be safe!

i had the very same issue during my internship and couldn't execute the installation of forefront until i checked to only install the console extension and the FEP install. A new SQL Server was installed and was dedicated to host the SCCM site database. Then i retried to install FEP with the reporting module, and it succeeded! I don't know what the cause of the problem was, but installing a new SQL Server might be the solution.

As far as I understand SCCM2012, the client computers will be put in a site by your SCCM2012 infrastructure, so the clients will be managed by the SCCM2012 site. If you still want to be able to deploy software which is available in your SCCM2007, you should migrate your software packages and share your SCCM2007 distribution points.

Perhaps ticking the checkbox in the user experience tab in the deployment properties of the application could solve your problem: http://imageshack.us/photo/my-images/152/outsidemaint.png/

I guess so, since your ADR will only look into the windows updates which are known by your SCCM/WSUS server (so the updates which are synchronised). Correct me if i'm wrong

Hey Ellefson As i noticed earlier today, you can't import SCCM 2007 into your SCCM 2012 if they both have the same site code, so the only option is to use different site codes