none
SCM 2.0 fails to import 'Windows-7-Settings.cab' (A problem may have occurred in the database.)

Answers

  • The settings pack became obsolete with the release of SCM 2.0 because all of the settings in the setting packs are not built into the SCM database. There's no reason to try to add them, and you're probably seeing the error because the setting pack would overwrite data that's already in SCM.

    Kurt


    Kurt Dillard http://www.kurtdillard.com

    • Proposed as answer by Kurt DillardModerator Thursday, March 29, 2012 4:47 PM
    • Marked as answer by EbyK Friday, March 30, 2012 3:41 AM
    Thursday, March 29, 2012 4:47 PM

All replies

  • The settings pack became obsolete with the release of SCM 2.0 because all of the settings in the setting packs are not built into the SCM database. There's no reason to try to add them, and you're probably seeing the error because the setting pack would overwrite data that's already in SCM.

    Kurt


    Kurt Dillard http://www.kurtdillard.com

    • Proposed as answer by Kurt DillardModerator Thursday, March 29, 2012 4:47 PM
    • Marked as answer by EbyK Friday, March 30, 2012 3:41 AM
    Thursday, March 29, 2012 4:47 PM
  • That makes sense; thanks a ton Kurt.


    Microsoft Forum Thanks, Eby K. Kuriakose

    Friday, March 30, 2012 3:42 AM
  • Cool Eby, you should be able to add other administrative template settings when you have selected one of your custom baselines. Just click the Add Setting command in the action pane on the right and use the wizard to add 1 or more settings to whatever setting group you wish.

    Kurt Dillard http://www.kurtdillard.com

    Friday, March 30, 2012 1:41 PM