During a OSD task sequence in Configuration Manager, we ran into an error with a VBS script that has worked previously.
The error in the SMSTS.LOG file was: CScript Error: Can’t find script engine “VBScript” for script
The problem appears to be caused by a changed registry value: HKEY_LOCAL_MACHINE\Software\Microsoft\COM3\REGDBVersion
After some searching on the internet the solution was to add the modify the REGDBVersion to a value of hex:01,00,00
Add to task sequence via a Command Line: REG ADD HKLM\Software\Microsoft\COM3 /v REGDBVersion /t REG_BINARY /d 010000 /f
In order for MDT to join machines into the contoso.com domain you need to create an account and configure permissions in Active Directory.
These steps will show you how to configure an Active Directory account with the permissions required to deploy a Windows 10 machine to the domain using MDT. These steps assume you have downloaded the sample Set-OUPermissions.ps1 script and copied it to C:\Setup\Scripts on DC01. The account is used for Windows Preinstallation Environment (Windows PE) to connect to MDT01.
- On DC01, using Active Directory User and Computers, browse to contoso.com / Contoso / Service Accounts.
- Select the Service Accounts organizational unit (OU) and create the MDT_JD account using the following settings:
- Name: MDT_JD
- User logon name: MDT_JD
- Password: P@ssw0rd
- User must change password at next logon: Clear
- User cannot change password: Select
- Password never expires: Select
- In an elevated Windows PowerShell prompt (run as Administrator), run the following commands and press Enter after each command:
Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Force
.\Set-OUPermissions.ps1 -Account MDT_JD -TargetOU "OU=Workstations,OU=Computers,OU=Contoso"
- The Set-OUPermissions.ps1 script allows the MDT_JD user account permissions to manage computer accounts in the Contoso / Computers OU. Below you find a list of the permissions being granted:
- Scope: This object and all descendant objects
- Create Computer objects
- Delete Computer objects
- Scope: Descendant Computer objects
- Read All Properties
- Write All Properties
- Read Permissions
- Modify Permissions
- Change Password
- Reset Password
- Validated write to DNS host name
- Validated write to service principal name
I was needing to disable some devices on a Windows 7 x64 computer. Did the usual download from Microsoft then constructed the syntax. I kept getting: Disable failed.
I have this working on WIndows XP x86. After some googling it turned out that the 64 bit version of Devcon.exe that is available to download from Microsoft is not compatible for windows 7 64 bit. Go figure.
You need to extract it from Windows Server 2003 x64 DVD.
Here is a link for the x64 version of Devcon.exe (zipped):
Disabling devices using Devcon
- List all devices to a text file: devcon find *> d:\list.txt
- Verify the device is unique: devcon find *VEN_1113
- devcon disable *VEN_1113
Get NETDOM>EXE and NETDOM.MUI (remember there are x86 and x64) from the Windows 7 RSAT.
NETDOM JOIN %computername% /DOMAIN:local.net /UserD:local\BuildAccount /PasswordD:pa$$word
Great guide to optimise your virtual Windows 7 build using Microsoft Deployment Toolkit. Takes you through services, profiles and registry setting in an easy to read document.
The WMI Code Generator 7.03 tool is similar to Scriptomatic but even more powerful. It is a great tool to quickly learn and create WMI management scripts. WMI Code Generator can create code that can be run on the Local Computer, Remote computer or a group of remote computers, based on what you choose from the Target Computer menu.
Check it out at: http://www.robvanderwoude.com/wmigen.php
Use the chr(34) to help passing the MSI commands:
sCmd = chr(34) & sFile & chr(34) & ” /s /v” & chr(34) & “/qb REBOOT=R” & chr(34)
Needed a script that completes this task for my deployment task sequence. Finally found it on the web: http://acidfighter.com/content/it-knowledge/unpin-ie-explorer-media-player-from-taskbar.php