Sign in
 
HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs
Resources for IT Professionals >
> 
> 
> 
"Grey out" or disable one application version when another version is selected...

回答済み "Grey out" or disable one application version when another version is selected...

  • Saturday, January 26, 2013 8:26 PM
     
     
    Sign In to Vote
    0
    Hey guys,

    We have a current requirement that forces us to run a mixture of Microsoft Office versions in our environment. I have 2010 and 2013 loaded as checkable Applications in the MDT Wizard. I'm looking for a way to disable one if the other is checked (ie if a helpdesk checks the box to install Office 2010, then the checkbox for Office 2013 gets disabled and vice versa). Is there any way to achieve this in the MDT Wizard interface?
     

All Replies

  • Monday, January 28, 2013 9:12 AM
     
     
    Sign In to Vote
    1

    I think you would have to create a new wizard screen using radio buttons instead of checkboxes.

    I'm not at work at the moment but you could quite easily do it using some simple HTML to create the page and the use MandatoryApplication001=  and 002 etc to set them using the GUID.  Then just hide them from the application list.

    If I get some time tomorrow at work I can have a quick look (public holiday here in AUS)

     
  • Tuesday, January 29, 2013 12:59 AM
     
     
    Sign In to Vote
    0

    I think you would have to create a new wizard screen using radio buttons instead of checkboxes.

    I'm not at work at the moment but you could quite easily do it using some simple HTML to create the page and the use MandatoryApplication001=  and 002 etc to set them using the GUID.  Then just hide them from the application list.

    If I get some time tomorrow at work I can have a quick look (public holiday here in AUS)

    I've never attempted anything like that before but it sounds like it would be what I'm looking for. Any help you can give would be greatly appreciated. 
     
  • Wednesday, January 30, 2013 1:43 AM
     
     Answered Has Code
    Sign In to Vote
    1

    I haven't even had a chance to look at it man but I'll show you how I have done something similar and you might be able to take it from there.

    For some of our service Techs they require local admin rights and we had a pretty clunky system before so I added a custom screen to the wizard to accept a username and add that user as an admin:

    I created a xml file to the %deployroot%/scripts folder called DeployWiz_localadmin.xml (can call it whatever but just to maintain the convention) and add the following:

    <?xml version="1.0" encoding="utf-8"?>
<!--

' // ***************************************************************************
' // 
' // Copyright (c) Microsoft Corporation.  All rights reserved.
' // 
' // Microsoft Deployment Toolkit Solution Accelerator
' //
' // File:      DeployWiz_localadmin.xml
' // 
' // Version:   1
' // 
' // Purpose:   Wizard pane for custom settings
' // 
' // ***************************************************************************

-->
<Wizard>
  <Global>
    <CustomScript>DeployWiz_localadmin.vbs</CustomScript>
  </Global>
  <Pane id="Local Admin" title="Custom Deployment">
    <Body><![CDATA[
<H1>Wedderburn User Account</H1>
    <span style="width: 95%;">
        <p> This is the  user account for the laptop.  The user will be created as a local administrator.</p>

        <p><span class="Larger">User Account:</span>

        <input type=text id="Administrators003" name="Administrators003"  size=20 language=vbscript>
	</p>

        <p>  ('DOMAIN\' not required.  Example: jsmith).</p>
]]></Body>
    <Initialization><![CDATA[InitializeAdministrators]]></Initialization>
    <Condition><![CDATA[UCASE(Property("Skiplocaladmin"))<>"YES" ]]></Condition>
  </Pane>
</Wizard>


    Then create a DeployWiz_localadmin.vbs file

    ' // ***************************************************************************
' // 
' // Copyright (c) Microsoft Corporation.  All rights reserved.
' // 
' // Microsoft Deployment Toolkit Solution Accelerator
' //
' // File:      DeployWiz_localadmin.vbs
' // 
' // Version:   6.0.2058.0
' // 
' // Purpose:   Main Client Deployment Wizard Validation routines
' // 
' // ***************************************************************************

Option Explicit

Function InitializeAdministrators

    If oEnvironment.Item("Administrators003") = "" then
        Administrators003.Value = Administrators003.Value 
    End If

End Function

    and finally add a section to the top of your DeployWiz_Definition.xml that looks similar:

    ...

	<Pane id="localadmin" reference="DeployWiz_localadmin.xml">
		<Condition><![CDATA[UCASE(Property("Skiplocaladmin"))<>"YES" ]]></Condition>
	</Pane>

...

    add the pane part above anywhere in the first section.

    This looks like this in MY deployment (I removed the company name etc in the example above so it looks slightly different):

    So what this does is basically:

    1. Take a text box input
    2. Assign that input to "Administrators003"
    3. MDT uses "Administrators00X" to assign local admin rights

    (We do have two other local administrator accounts that are static.

    Hope this helps!

    EDIT:  Forgot to add that adding SkipLocalAdmin=YES in your CS.ini will skip this screen!
    • Edited by mhouston100 Wednesday, January 30, 2013 3:34 AM
    • Proposed As Answer by mhouston100 Wednesday, January 30, 2013 3:34 AM
    • Marked As Answer by ZeusABJ Thursday, January 31, 2013 2:03 PM
    •  
     
  • Thursday, January 31, 2013 2:03 PM
     
     
    Sign In to Vote
    0
    Thanks man! I think I can adapt this to my needs. I actually just finished modifying one of the HTA pages to include a computer description field. Appreciate the code sharing.
     
  • Thursday, January 31, 2013 8:19 PM
     
     
    Sign In to Vote
    1

    My HTML skills aren't much chop but using that as a template you can roll out new screens pretty quickly.

    Good luck!

     
  • Thursday, March 07, 2013 4:43 PM
     
     
    Sign In to Vote
    0
    BTW - This worked for me, thanks!