Sign in
 
HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs
Resources for IT Professionals >
> 
> 
> 
Version control in MDT 2010

Unanswered Version control in MDT 2010

  • Friday, September 21, 2012 11:43 AM
     
     
    Sign In to Vote
    0

    Hi all,

    We use MDT 2010 and use flash drives to deploy our OS. We however need some kind of versoin control implemented. Any ideas or maybe some of you have done something like this before?

     

All Replies

  • Friday, September 21, 2012 1:57 PM
     
     
    Sign In to Vote
    0

    I've never done this, what about using custom properties called BSVersion and CSVersion and setting them in the BootStrap.ini and CustomSettings.ini.  Then you could compare the versions in a user exit script and show a message and exit if they don't match.

     
  • Friday, September 21, 2012 2:10 PM
     
     
    Sign In to Vote
    0

    I've never done this, what about using custom properties called BSVersion and CSVersion and setting them in the BootStrap.ini and CustomSettings.ini.  Then you could compare the versions in a user exit script and show a message and exit if they don't match.


    Could you maybe elaborate on this? Sorry I'm new to MDT.
     
  • Friday, September 21, 2012 2:31 PM
     
      Has Code
    Sign In to Vote
    0

    In you Bootstrap.ini, add a custom property called BSVersion and set it to a value.

    [Settings]
    Priority=Default
    Properties=BSVersion

    [Default]
    BSVersion=1

    In CustomSettings.ini, create a custom property called CSVersion and set it to a value.

    [Settings]
    Priority=CheckVersion,Default
    Properties=CSVersion

    [CheckVersion]
    CSVersion=1
    OSInstall=#CheckVersion(%BSVersion%,%CSVersion%)#
    UserExit=UserExit.vbs

    [Default]
    OSINSTALL=Y

    Use a CheckVersion function in the userexit.vbs to compare the versions.

    Function CheckVersion(BSVersion, CSVersion)
	oLogging.CreateEntry "Comparing values of BSVersion and CSVersion.", LogTypeInfo
	If BSVersion = CSVersion Then
		oLogging.CreateEntry "Versions match.", LogypeInfo
		CheckVersion = "Y"
	Else
		oLogging.CreateEntry "Versions do not match.", LogypeError
		WScript.Echo "The version between the boot media and the deployment share do not match."
		CheckVersion = "N"
	End If
End Function

    the boot wim, you increment both version numbers so they match and if someone has an outdated boot wim on their flash drive, it will not let them install and image.

    NOTE: this is all from the top of my head.  I have not tested it.

     
  • Friday, September 21, 2012 2:44 PM
     
     
    Sign In to Vote
    0
    Thanx for the help so far. Just to make sure, where will it check againt the deployment share from the build stick?
     
  • Friday, September 21, 2012 4:56 PM
     
     
    Sign In to Vote
    0
    It will check after it prompts for credentials but before the wizard is presented.
     
  • Friday, September 21, 2012 5:53 PM
     
     
    Sign In to Vote
    0

    This is quite useful indeed, alternatively you can also embed an expiration date to the deployment:

    Standalone Media Expiration Date

    Keep us posted, and if helpful please rate! Kind regards