Sign in
 
HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs
Resources for IT Professionals >
> 
> 
> 
Customsetting.ini to skip time zone request deploying Windows 7

Answered Customsetting.ini to skip time zone request deploying Windows 7

  • Thursday, March 29, 2012 8:42 AM
     
     
    Sign In to Vote
    0

    Hi, I'm new on MDT 2010 and I'm studing it to update my enviroment from Windows XP to Windows 7.

    After some good test and lot of time reading various forums I realize my customsettings.ini file, and seem to work nice; my last problem is the fact that always procedure stop asking me time zone, even though in the cs.ini there are all the setting required to skip this step.

    This is my cs.ini

    [Settings]
    Priority=CSettings, CApps, CAdmins, CRoles, Locations, LSettings, LApps, LAdmins, LRoles, MMSettings, MMApps, MMAdmins, MMRoles, RSettings, RApps, RAdmins, Default
    Properties=MyCustomProperty

    [Default]
    OSInstall=YES
    SkipAdminPassword=YES
    SkipApplications=YES
    SkipDomainMembership=NO
    ;JoinDomain=****
    ;DomainAdmin=****
    ;DomainAdminDomain=****
    ;DomainAdminPassword=****
    ;MachineObjectOU=OU=****,OU=****,DC=****,DC=****
    SkipAppsOnUpgrade=YES
    SkipBDDWelcome=YES
    SkipBitLocker=YES
    UserLocale=it-IT
    SystemLocale=it-IT
    UILanguage=it-IT
    KeyboardLocale=it-IT
    TimeZoneName=W.Standard Europe Time
    TimeZone=110
    SkipCapture=NO
    SkipComputerName=NO
    SkipComputerBackup=YES
    SkipDeploymentType=YES
    DeploymentType=NEWCOMPUTER
    SkipFinalSummary=NO
    SkipPackageDisplay=YES
    SkipProductKey=YES
    SkipSummary=YES
    SkipLocaleSelection=YES
    UserDataLocation=NONE
    SkipTimeZone=YES
    SkipUserData=YES
    WSUSServer=http://wsus.****.****

    [CSettings]
    SQLServer=****
    Database=MDT
    Netlib=DBNMPNTW
    SQLShare=DeploymentShare$
    Table=ComputerSettings
    Parameters=UUID, AssetTag, SerialNumber, MacAddress
    ParameterCondition=OR

    [CApps]
    SQLServer=****
    Database=MDT
    Netlib=DBNMPNTW
    SQLShare=DeploymentShare$
    Table=ComputerApplications
    Parameters=UUID, AssetTag, SerialNumber, MacAddress
    ParameterCondition=OR
    Order=Sequence

    [CAdmins]
    SQLServer=****
    Database=MDT
    Netlib=DBNMPNTW
    SQLShare=DeploymentShare$
    Table=ComputerAdministrators
    Parameters=UUID, AssetTag, SerialNumber, MacAddress
    ParameterCondition=OR

    [CRoles]
    SQLServer=****
    Database=MDT
    Netlib=DBNMPNTW
    SQLShare=DeploymentShare$
    Table=ComputerRoles
    Parameters=UUID, AssetTag, SerialNumber, MacAddress
    ParameterCondition=OR

    [Locations]
    SQLServer=****
    Database=MDT
    Netlib=DBNMPNTW
    SQLShare=DeploymentShare$
    Table=Locations
    Parameters=DefaultGateway

    [LSettings]
    SQLServer=****
    Database=MDT
    Netlib=DBNMPNTW
    SQLShare=DeploymentShare$
    Table=LocationSettings
    Parameters=DefaultGateway

    [LApps]
    SQLServer=****
    Database=MDT
    Netlib=DBNMPNTW
    SQLShare=DeploymentShare$
    Table=LocationApplications
    Parameters=DefaultGateway
    Order=Sequence

    [LAdmins]
    SQLServer=****
    Database=MDT
    Netlib=DBNMPNTW
    SQLShare=DeploymentShare$
    Table=LocationAdministrators
    Parameters=DefaultGateway

    [LRoles]
    SQLServer=****
    Database=MDT
    Netlib=DBNMPNTW
    SQLShare=DeploymentShare$
    Table=LocationRoles
    Parameters=DefaultGateway

    [MMSettings]
    SQLServer=****
    Database=MDT
    Netlib=DBNMPNTW
    SQLShare=DeploymentShare$
    Table=MakeModelSettings
    Parameters=Make, Model

    [MMApps]
    SQLServer=****
    Database=MDT
    Netlib=DBNMPNTW
    SQLShare=DeploymentShare$
    Table=MakeModelApplications
    Parameters=Make, Model
    Order=Sequence

    [MMAdmins]
    SQLServer=****
    Database=MDT
    Netlib=DBNMPNTW
    SQLShare=DeploymentShare$
    Table=MakeModelAdministrators
    Parameters=Make, Model

    [MMRoles]
    SQLServer=****
    Database=MDT
    Netlib=DBNMPNTW
    SQLShare=DeploymentShare$
    Table=MakeModelRoles
    Parameters=Make, Model

    [RSettings]
    SQLServer=****
    Database=MDT
    Netlib=DBNMPNTW
    SQLShare=DeploymentShare$
    Table=RoleSettings
    Parameters=Role

    [RApps]
    SQLServer=****
    Database=MDT
    Netlib=DBNMPNTW
    SQLShare=DeploymentShare$
    Table=RoleApplications
    Parameters=Role
    Order=Sequence

    [RAdmins]
    SQLServer=****
    Database=MDT
    Netlib=DBNMPNTW
    SQLShare=DeploymentShare$
    Table=RoleAdministrators
    Parameters=Role

    I don't understand where is the trouble, can someone halp me?

    Thank a lot.

     

All Replies

  • Thursday, March 29, 2012 8:46 AM
     
     
    Sign In to Vote
    0

    If you change TimeZoneName to the valid value "W. Europe Standard Time" i believe you will be good to go.

     
  • Thursday, March 29, 2012 9:06 AM
     
     
    Sign In to Vote
    0

    Hi Eirik, thank for your reply; I set the value as you suggested, but nothing changed.

     
  • Thursday, March 29, 2012 10:02 AM
     
     
    Sign In to Vote
    0

    This is what I use and it works:

    SkipTimeZone=Yes
    TimeZone=110
    TimeZoneName=W. Europe Standard Time

    I noticed you didn't have a space after "W." in your original file. Do you have that now?

     
  • Thursday, March 29, 2012 10:15 AM
     
     
    Sign In to Vote
    0

    Yes, I have it.

    This is what I wrote on the CS.ini

    TimeZoneName=W. Europe Standard Time

     
  • Thursday, March 29, 2012 10:55 AM
     
     
    Sign In to Vote
    0

    I Suspect that the problem is not on the cs.ini, because two days ago, after the two last addictions (TimeZoneName and UserDataLocation), it worked fine.

    I started to prepare some applications, like Office 2007 and Access Runtime 2010; looking for some options on Access runtime I had an error on the Deployment Workbench snap-in that close it.

    Re-opening the snap-in all seemed to work fine, but after this my deploy started to ask for the time zone.

    I simply went on the Office Product tab and looked for selection on Office Product to install; Let Office decide Setup is the default, but changing on AccessRT produced the error. After this Time Zone selection was a problem.

    Maybe the error on the snap-in caused some important configuration lost on the MDT?

     
  • Thursday, March 29, 2012 11:15 AM
     
     
    Sign In to Vote
    0

    That's a bit weird... Does everything else work?

    I see that you have set your keyboard locale to it-IT while it should be 0410:00000410.

     
  • Thursday, March 29, 2012 11:34 AM
     
     
    Sign In to Vote
    0

    All seem working; I deleted all database entry, task, operating system.

    Now I re-created the OS from a captured image, new task and changed CS.ini; these are my new settings

    SkipTimeZone=YES
    TimeZoneName=W. Europe Standard Time
    SkipLocaleSelection=YES
    KeyboardLocale=0410:00000410
    UserLocale=it-IT
    UILanguage=it-IT
    UserDataLocation=NONE

    It doesn't work!

    It's strange the fact that when wizard appear I can choose Time and currency format, keyboard, but Language to Install is set to English without any other choice.

    For the last, I could capture another image and start with it, but I don't think that it can resolve the problem.

     
  • Thursday, March 29, 2012 12:54 PM
     
     
    Sign In to Vote
    0
    Sorry, but I cannot see anything else that could be wrong with customsettings.ini itself so I believe the problem to be elsewhere.
     
  • Thursday, March 29, 2012 2:17 PM
     
     
    Sign In to Vote
    0

    Ok, thanks a lot. I'll try searching for some other info and continue with my tests. Hope I'll find the solution.

     
  • Thursday, March 29, 2012 6:41 PM
     
     
    Sign In to Vote
    0

    Hi,

    Is it the Windows Out of the Box experience that you're seeing where you're being asked for the timezone?

    If that's the case, you can try the following method to enforce the timezone settings to be skipped; http://technet.microsoft.com/en-us/library/dd744353(v=ws.10).aspx

    Normally everything should work, as far as I can see from your customsettings.ini. However try this method if you cannot seem to get it to work any other way.

    You will have to either mount your .wim file and add the xml file and then commit and dismount, or make a step in your task sequence to copy the xml file to the specified location.

    Kind regards,

    Stephan Schwarz.

    If one of these posts answered your question or issue, please click on "Mark as answer".

    My Blog | Twitter: @Schwarz_Stephan | MCTS, MCITP, MCC.
    How to configure Windows RE/OEM Recovery Partition with MDT

     
  • Friday, April 06, 2012 8:35 AM
     
     
    Sign In to Vote
    0

    Hi, sorry for the delay but I was trying to understand more about the problem.

    Now I can reply to you, hoping to have right understood what I've read.

    When the timezone request appeared I noticed that there was no possibility to change system language and the only choice was English; strange, because the original OS was created in italian.

    I thought that the system was using the wrong image and I remembered that before the issue appeared I deleted another OS fron the list; this OS was created directly from the ISO and had a different structure.

    My original OS was imported as a single wim file, while the other OS seemed to be copied from the CD, having a structure of files and folders; what I discovered is that it seem that an OS captured as a single wim file need others operating systems files to be deployed, and it seem that my wim was using those from the other OS.

    When these files were deleted, original wim was not able to be deployed and it started to ask me for timezone; to solve the problem I re-captured an OS from ISO image and now all it's working good.

    The solution is so strange and I don't feel so sure about it, but I'm sure that the only thing I did was to re-captured the ISO.

    I hope that this can be confirmed from someone and that it could be helpful.

     
  • Friday, April 06, 2012 9:08 AM
     
     Answered
    Sign In to Vote
    0

    When deploying OS's in multiple languages, it's definitely recommended to include windows setup files of the language that's being deployed (when importing a OS wim file, you can select to copy the windows setup files from a location).

    While generally it >should< work to use the Windows Setup in any language to deploy any language image, it however sometimes does cause issues.

    Kind regards,

    Stephan Schwarz.

    If one of these posts answered your question or issue, please click on "Mark as answer".

    My Blog | Twitter: @Schwarz_Stephan | MCTS, MCITP, MCC.
    How to configure Windows RE/OEM Recovery Partition with MDT

    • Marked As Answer by emenoncin Friday, April 06, 2012 12:25 PM
    •