Sign up for the quarterly Flings Newsletter here!

Workspace ONE Configuration Tool for Provisioning

The Workspace ONE Configuration Tool helps you build special-purpose unattend.xml configuration files to be applied in the Dell factory as part of Factory Provisioning. This helps to domain join (domain, workgroup, AAD, AAD Premium) and enroll devices automatically on first-boot. This simplifies the creation of the unattend.xml configuration file for Windows 10.

Features

  • It's a stand-alone .exe app that helps IT administrators configure general and Out-of-the-Box Experience Windows setups to automatically enroll users in Workspace ONE.
  • The User Interface is made simple with explicit instructions about each field for easy and quick use by IT admins.
  • The User Interface has dynamic and efficient validations in Clarity and Angular, preventing the user from building the unattend.xml until all the validations are correctly satisfied. This makes the UI fool-proof and reduces the chances of generating an invalid xml file.
  • The tool is made as a .Net Core 2.0 web app with Angular 5 and Clarity, which eases the integration of v2.0 into the AirWatch Console.
  • Windows 7 and later are supported
  • Intel Pentium 4 processor or later that's SSE2 capable
  • 512 MB of RAM
  1. Extract the downloaded .zip file to any location
  2. Launch VMWareWorkspaceONEConfigurationToolforProvisioning-v{x.y}.exe, where {x.y} represents the current version number

Release Update - Version 2.0.0

Improvements 

  • The version number is shown in the window title 
  • The version number is shown as a comment in the generated XML
  • The product key is now validated to conform with the 11111-11111-11111-11111-11111 pattern 
  • Split the locale settings into 'Operating System Language', and 'Region and Keyboard Settings'.
  • 'Operating System Language' maps to the language of the operating system installation media, and 'Region and Keyboard Settings' maps to the locale settings available to the user during OOBE 
  • 'Operating System Language' is now a required field as it is needed for certain customizations, such as adding a user to the administrators group 
  • Removed the ability to set a custom computer name. The computer name now defaults to '*', which causes the Windows OS to generate a random name, taking up to seven characters from the 'Registered Organization' field plus eight random characters. This change makes sure every computer has a unique name on the network. 
  • The 'Auto Admin Logon' feature is no longer selectable. Instead, it will be activated when it is required by the deployment scenario. 
  • All deployment scenarios now allow for the creation of a local user. 
  • Moved the node from the 'oobeSystem' pass to the 'specialize' pass 
    to be consistent with the node

Bug Fixes 

  • Auto Admin Logon would only work with an unattend XML generated for an en-US installation image 
  • Enabled the ASSIGNEDTOLOGGEDINUSER=Y flag to enable the WS1 agent to correctly enroll the user in the 'Workgroup' deployment scenario 
  • Fixed an issue where the 'Show Privacy Settings' option would have no effect
Report a Bug