gr4z

Hi I am trying to setup two SCCM sites across untrusted forests: DomainA with SCCM1 (Parent) DomainB with SCCM2 (Child) I know about the manual key exchanges but all documentation states you must add the computer account SCCM1 into the SMS_SitetoSiteConnection group on SCCM2 and vice versa. But without a trust in place, how do you do it? You cannot navigate to DomainA from within DomainB as it doesn't know anything about it. Thanks for any help. Graham

OK but if you set once per day does that introduce a random interval - I assume it does? I am sure I read somewhere that SCCM always introduces a random lapse in time to prevent say 10000 workstations all polling at the same time. Thanks

I know WSUS introduces a random interval of up to 2 hours when polling the WSUS server within SCCM, but what about advertising apps and the SCCM client? I thought SCCM always introduces some sort of random interval on top of the fixed schedule to prevent network storms. Can anyone confirm? Thanks

OK thanks. I will continue with leaving them separate.

Because I don't see any real huge benefit to integrate them. The build guys have their own offsite platform independent of the live production system used solely to create WIMs. These are then shipped to the production system and imported into SCCM. Once a WIM is deployed SCCM takes over and pushes out remaining applications and WSUS updates. Am I missing something here? Thanks

Hi I am planning on keeping my MDT deployment and SCCM separate. We have our own team of MDT/desktop image guys in one location and our own SCCM team offshore. While we plan to import any WIM images made by MDT into SCCM and advertise them over a PXE service point the current plan is to NOT integrate. Is this a good idea - what are the disadvantages/advantages? Many thanks

As a FYI, just tried this with SQL2008 SP3 and it doesnt work - fails on the DB creation. Went back to SP1CU14 and all was fine.

You need to download MDOP available here: http://www.microsoft.com/windows/enterprise/products/mdop/default.aspx