Tool: OSConfig

OSConfig is a script that I am using to configure my Operating Systems (Windows XP – Windows 10) in MDT and OSD. Changes are made to the Operating System after reboot from WinPE prior to first Logon. This allows changes to the System and the Default User Profile to be made and bypasses the need to use Sysprep Unattend CopyProfile (which may have issues in Windows 10).

This page is not complete and I will keep adding information as new functionality is added.

OSConfig Pre-Release Overview
OSConfig (Preview)
OSConfig (Preview) Why?

Downloading OSConfig from GitHub (Updated 20151204)
OSConfig Download (Updated 20151204)

Configure OSConfig with MDT (SCCM Guide Coming Soon)
OSConfig MDT Integration (Updated 20151204)
OSConfig MDT First Run (Updated 20151204)

OSConfig Features
OSConfig Logs (Added 20151204)
OSConfig Registry Backup (Added 20151204)
OSConfig Registry Snapshot (Added 20151204)
OSConfig Settings (Added 20151204)

Settings Files
OSConfig Sample Settings
OSConfig Default User Customizations
OSConfig Undo Settings
OSConfig Architecture Settings
OSConfig Task Sequence Only Settings
OSConfig RunOnce Settings
OSConfig Standalone

Working with OEM Folders
OSConfig OEM Folders

Working with Themes, Wallpaper, and Start Customizations
~~OSConfig Theme Customizations (Windows 10)~~
OSConfig Theme Sample – Windows 10 (Added 20151204)

Advanced Functions
~~OSConfig Removing Unnecessary Appx Packages~~
OSConfig Appx Packages (Added 20151204)

vs Task Sequence Steps
OSConfig for GaryTown (Added 20151206)

OSConfig News
OSConfig News 20151209
OSConfig News 20151208
OSConfig News 20151204

Pingback: Tool: OSConfig News 20151204 | David Segura
Pingback: Tool: OSConfig Settings | David Segura
Pingback: Tool: OSConfig Theme Sample – Windows 10 | David Segura
Pingback: Tool: OSConfig Appx Packages | David Segura
Pingback: Tool: OSConfig News 20151208 | David Segura
Pingback: Tool: OSConfig for GaryTown | David Segura
Pingback: Win10: Start Menu Cleanup using DefaultLayouts.xml | David Segura
Pingback: Tool: OSConfig News 20151209 | David Segura
Jonathan Topping 6:26 AM on March 30, 2016

Great tool! I wish Google led me here earlier! This saved me a ton of time developing a new win 10 image!

Bug: the vbs that sets the user account pictures copies the image files into the folder above user account pictures. A simple code tweak and redeploy fixedfixed it for me.

LikeLike
- segura 2:48 PM on May 10, 2016
  
  I had made a change in OSConfig.vbs dated 20151217, but never updated the change. This has been corrected in OSConfig.vbs line 699 should read:
  objFSO.CopyFolder MyWindir & “\OSConfig\Theme\User Account Pictures”, MySystemDrive & “\ProgramData\Microsoft\User Account Pictures”, True
  
  LikeLike
air0ne 7:54 AM on April 6, 2016

It’s working well but only with English ISO, Windows 10 Entreprise in my case. Do have any idea to make it work for French ISO ?

LikeLike
- segura 2:46 PM on May 10, 2016
  
  What are the issues you are having?
  
  LikeLike
Anonymous 3:51 AM on May 12, 2016

Dear Segura
we are currently experiancing the same issue that the osconfig vbs script is not working correctly on French ISO – it just goes through without processing any of the screens – in additon it doesnt copy to _TS tas Sequence folder located on C Drive

LikeLike
Anonymous 6:59 AM on May 12, 2016

Dear Segura seems that he problem is related with variable “_SMSTSMDataPath” that is not processed
within french image correctly.

Regards

LikeLike
segura 11:19 AM on May 12, 2016

Can you email me a copy of your BDD.LOG?

LikeLike
Mavesar 6:52 PM on May 18, 2016

Strange issue here, I am running the script on a VM from a stand alone ISO disk mostly all defaults was just testing it out. I get “ZTI ERROR – Unhandled error returned by ZTIOSConfig: Permission denied (70)” when it is copying the “Windows 10” folder? If I move the scripts to a Deploy\Scripts and OSConfig folder that is writeable (in my case the X drive) it works fine not sure what to do.

LikeLike
Mavesar 7:34 PM on May 18, 2016

Follow up to last comment: Do I need to put a “\” after OSConfig as below
Change: “oFSO.CopyFolder oEnvironment.Item(“OSConfig”) & “\” & oEnvironment.Item(“MyOSName”), oEnvironment.Item(“_SMSTSMDATAPATH”) & “\OSConfig”, True”
To: “oFSO.CopyFolder oEnvironment.Item(“OSConfig”) & “\” & oEnvironment.Item(“MyOSName”), oEnvironment.Item(“_SMSTSMDATAPATH”) & “\OSConfig\”, True”?

LikeLike
- segura 7:39 PM on May 18, 2016
  
  I’ll check later tonight to see if I can see what’s happenings
  
  LikeLike
Mavesar 8:38 PM on May 18, 2016

The additional “\” solved the problem and it works as expected now.
One additional note; the files on the ISO are marked read only during creation, as a result the script only works the first time it is run (Since CopyFolder fails on replacing read only files). if you decide to add the \ into the script it would be helpful if you also removed the read only attribute from the files (only to help with testing).

Thank you! this tool will save me an incredible amount of time.

LikeLike
Mavesar 2:41 AM on May 19, 2016

Read only attribute being set on all the files kills the vbs file called from OSConfig.cmd too. I am just removing it during Win PE by adding /Copy:D to your robocopy command in ZTIOSConfig.wsf when it creates the .cmd file. Is there a way to stop MDT Update 2 from setting all files in the ISO when creating stand alone media to read only?

LikeLike
Xavier 5:19 AM on November 10, 2016

Will you update it to work with build 1607?

LikeLike
Jonathan Topping 1:52 PM on February 15, 2017

Xavier, I was about to do a new customized 1607 install. What do you know of that doesnt work with 1607?

LikeLike
Carl R 12:11 PM on May 10, 2017

I second that. Has this been vetted against 1607+

LikeLike
Xavier 3:13 AM on May 18, 2017

I’ve just tried with build 1703. All works fine, except for these bits:

+ User account picture on logon
+ New shortcuts in apps menu, that I want to remove:
– Cortana
– Feedback hub
– Get help
– Mixed reality portal
– Paid wifi & mobile
– Tips
– View 3D

I’ll play a bit with the scripts David made, I think it’s possible to get rid off those things by tweaking the scripts a little bit

LikeLike

Share this: