Beware!
If you are planning to update your AD schema for SCCM 2007 using ldifde and the supplied LDIF file ConfigMgr_ad_schema.ldf file, located in the \SMSSETUP\BIN\I386 directory of the Configuration Manager 2007 installation files.
Make sure you read to the bottom of the info at URL:
http://technet.microsoft.com/en-us/library/bb632388.aspx
And edit the LDIF file as directed, otherwise the update will fail with an error and you will need to rerun a partial LDIF. Personally I would also use an editor capable of displaying line numbers as the error output helpfully gives you the line in the LDIF where the error occoured.
If you already have the schema extensions for for SMS 2003 in AD then the update will also fail at the first instance of the section beginning:
# ----------------------------------------------------------------------
# SMS Assignment Site Code Attribute
# This section adds the SMS 2003 compatible attribute for SMS Sites
# This attribute will fail to be added if the AD schema has already been
# extended for SMS 2003.
# ----------------------------------------------------------------------
Why on earth Microsoft cannot provide an up-to-date LDIF file for SCCM 2007 is beyond me: they could even provide one for AD schemas that have already been updated for SMS 2003.
I always take the precaution of checking that each attribute has been added to the Schema master using the AD Schema MMC plugin. This at least give you a small amount of comfort when you start the task of resolving the critical errors from Components in the SCCM Site Status - which you will be doing!
If you are planning to update your AD schema for SCCM 2007 using ldifde and the supplied LDIF file ConfigMgr_ad_schema.ldf file, located in the \SMSSETUP\BIN\I386 directory of the Configuration Manager 2007 installation files.
Make sure you read to the bottom of the info at URL:
http://technet.microsoft.com/en-us/library/bb632388.aspx
And edit the LDIF file as directed, otherwise the update will fail with an error and you will need to rerun a partial LDIF. Personally I would also use an editor capable of displaying line numbers as the error output helpfully gives you the line in the LDIF where the error occoured.
If you already have the schema extensions for for SMS 2003 in AD then the update will also fail at the first instance of the section beginning:
# ----------------------------------------------------------------------
# SMS Assignment Site Code Attribute
# This section adds the SMS 2003 compatible attribute for SMS Sites
# This attribute will fail to be added if the AD schema has already been
# extended for SMS 2003.
# ----------------------------------------------------------------------
Why on earth Microsoft cannot provide an up-to-date LDIF file for SCCM 2007 is beyond me: they could even provide one for AD schemas that have already been updated for SMS 2003.
I always take the precaution of checking that each attribute has been added to the Schema master using the AD Schema MMC plugin. This at least give you a small amount of comfort when you start the task of resolving the critical errors from Components in the SCCM Site Status - which you will be doing!