Questions from TechNet Webcast: Deploying System Center Configuration Manager 2007 Clients (Level 300)

I am publishing some of the questions from the webcast I attendad.

Question: Will XP/2003 based clients require an upgrade to BITS 3.0, or will BITS 2.5 suffice?
Answer: BITS 2.5 is sufficient and will be installed by client install/upgrade.

Question: Is reboot on win2000 when installing BITS 2.0 forced or can wait until normal macheni restart
Answer: ccmsetup will wait until a normal restart has taken place

Question: Can the SMS 2003 client and the SCCM client coexist on the same workstation/server?
Answer: No, they are mutually exclusive, if you try to install Config Mgr 2007 client on an SMS 2003 client, it will be upgraded.

Question: Are the SCCM 2007 AD schema extentions compatible with the SMS 2003 AD schema extensions? i.e. can I extend the AD schema for SCCM before upgrading my SMS 2003 site?
Answer: Yes, we use some of the schema extensions that exist in 2003 for SCCM 07 as well. We do not decrement any of the SMS 2003 functionality when we update the schema for SCCM 07.

Question: Can a SMS2003 site and a separate SCCM 07 site coexist in the same AD domain?
Answer: Yes

Question: can you have your own internal certificate authority or does it need to be from external?
Answer: You can use your internal CA

Question: Why would you be in Mixed Mode if your site only contains ConfigMgr 2007 clients?
Answer: If your organization does not have a PKI infrastructure you would not be able to implement native mode.

Question: Is State Migration only used in an environment that only uses Vista?
Answer: If you are referring to User State Migration in OS Deployment: No. You can use State Migration via the User State Migration Toolkit to migrate user settings to/from other Windows Operating Systems, primarily Windows XP, but I believe migration from Windows 2000 Workstation is also supported.

Question: I noticed there was nothing about site boundaries as a prerequisite for client deployments or auto discovery. Is this correct and if so how do clients determine which site is in scope?
Answer: Good point. If you use SMSSITECODE=AUTO, you need to specify correct boundaries and make sure they’re published.

Question: Is the group policy template provided in SCCM 2007 Beta 2?…If not, will it be in RC1?
Answer: No, not provided in Beta 2, but will be in RC1.

Question: Could SUP be used in this manner to push other required software in the environment (i.e. firewall software)?
Answer: Via the Updates Publisher functionality, you could publish custom or 3rd party updates to WSUS, which we would then synch with and could deploy. Out of the box we can scan for and deploy everything published in Microsoft Updates, and push our CCMSETUP client bootstrap via the SUP Client Installation Method.

Question: How does SCCM 2007 integrate/share date/etc with SCOM 2007?
Answer: The main functionality is the ability to put the Operation Manager agent on managed computers into “maintenance mode” so that they’re not reported as down during a software installation or update.

You can read the full list of questions here.