Ward Vissers » Deployment

MDT 2010 Multiple Partitions Issues & hidden Bitlocker partition

Ward — Thu, 19 Aug 2010 09:33:48 +0000

I had a new laptop where I wanted to deploy Windows 7 x64 Enterprise and walked to a bug in MDT 2010. Default config.

I configured 2 partitions to use the whole disk. See screenshot.

When I deploy the task I get the following error

He wants to format partition D. But partition D is not availably.
I ended the task and opened the PE window and started Diskpart and listed the volumes.

The strange thing was that the extended partition has the drive letter S had and it was a raw partition.

After studying ZTIDiskpart.log (X:\MININT\SMSOSD\OSDLOGS\ZTIDiskpart_diskpart.log)

I found out that there was no space left to create a 300mb partition for saving Bitlocker information.

So what did ZTIDiskpart.wsf. ZTIDiskpart.wsf gave the last partition that was created the drive letter S. This is the default letter for the Bitlocker partition. So hey wanted to format the file system with fat32. Because in my case the partition size was 200GB he cannot format the disk.

Solution:

Setting the extended partition to use 95%. Then MDT have enough space to create a 300mb hidden partition for Bitlocker.

No tags for this post.

MDT 2010 Importing automatically the right driver

Ward — Mon, 19 Jul 2010 12:15:53 +0000

Microsoft Deployment Toolkit 2010 has some nice improvements to handle drivers. I will describe how I like to manage drivers in MDT 2010.

Some time I wrote i article about how to get the Name & Model from a computer. This is very important when you want to import only the right drivers automatically.

First we have to build the ‘Out-of-Box Drivers’ folder structure and import drivers. I have subdirectories for each architecture, brand and model. This is what my folder tree looks like:

However, you can build your own structure, as long as you respect the proper model & brand (make) name of the vendors.

Build Out-of-Box Drivers tree

To build up the folder structure you have to know the model name of your hardware. To retrieve the proper computer name execute at powershell command prompt: ‘Get-WmiObject -Class win32_computersystemproduct | fl Name,Model,UUID,Identifyingnumber,Vendor’, to get the exact name WMI queries to determine the computer model. In my case the computer name is “Latitude D830”.

Now that we have drivers imported in our Deployment Share, it’s time to move on.

1. DriverGroups

DriverGroups existed in MDT 2008 already, although the MDT Team added subdirectory support in MDT 2010.

At deployment phase MDT uses WMI to query the proper computer model and only the current model drivers will be injected. In order to get this working properly, you have to use the EXACT model name in your Out-of-Box Driver tree.

Inject the correct drivers in your Task Sequence

Add a new step in your Task Sequence to inject the correct drivers. MDT will query the computer name and inject the drivers which corresponds with the computer name from the Out-of-Box folder structure, right before applying the image at deployment.

I use ‘DriverGroup_001’ as Task Sequence Variable, and Win7×64\%Make%\%Model% as value for my Windows 7 x64. You have to adapt this to your Out-of-Box tree.

As I use a DriverGroup I’ve disabled the ‘Inject Drivers’ task.

Customsettings.ini

As my Task Sequence handles everything, there isn’t anything needed here.

If you don’t like to use a new Task in your TS, you can add DriverGroup variables in customsettings.ini like this:

DriverGroup_001=%Make%\%Model%

DriverGroup_002=Printers

2. Selection Profiles

New in MDT 2010 are DriverSelectionProfiles. These are easy for new MDT admins, very straight forward and easy to use.

Overview:

First you have to create a Profile (or use one of the default profiles):

You can even select Packages and Applications, use it for “bad drivers” aka driver setup packs.

Select what drivers you want to add to the profile;

After making the profiles you can use them in your Task Sequences. The default ‘Inject Drivers’ settings are on the left, the customized one on the right:

You can add Selection Profiles for drivers/packages or whatever you want. Just add an extra step in your task sequence like above.

Customsettings.ini

As with DriverGroups you can choose to handle the DriverSelectionProfile in customsettings.ini or in your TS.

Example:

DriverSelectionProfile=Dell Latitude D520 x64

No tags for this post.

Microsoft Deployment Toolkit (MDT) 2010 Update 1 is RTM

Ward — Thu, 08 Jul 2010 11:00:30 +0000

Microsoft has released a new version of MDT 2010 named Update 1.

It’s a great tool im loving it.

What new:

For System Center Configuration Manager 2007 users:

New “User Driven Installation” deployment method. An easy-to-use UDI Wizard allows users to initiate and customize an OS deployment on their PCs that’s tailored to their individual needs.
Support for Configuration Manager R3 “Prestaged Media.” For those deploying Windows 7 and Office 2010 along with new PCs, a custom OS image can easily be loaded in the factory and then customized once deployed.

For Lite Touch Installation:

Support for Office 2010. Easily configure Office 2010 installation and deployment settings through the Deployment Workbench and integration with the Office Customization Tool.
Improved driver importing. All drivers are inspected during the import process to accurately determine what platforms they really support, avoiding common inaccuracies that can cause deployment issues.

Bug Fixes and small improvements

LTI Wizard performance improvement. The LTI Wizard now takes less time to initialize and shows up faster.
Issue in validating connection to the server fixed. In a few scenarios, MDT 2010 used to report the error message, "A connection to the distribution share could not be made" when a task sequence is run. The Microsoft Support article, “Error message when you use MDT 2010: ‘Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed,’” at http://support.microsoft.com/kb/977566 describes this issue in detail. This issue has been fixed in MDT 2010 Update 1.
Support for installing Windows 7 roles and features. MDT 2010 Update 1 adds support for installation of Windows 7 operating system roles and features.
Looping issue with x64 custom Windows images fixed. In MDT 2010, ZTI–System Center Configuration Manager deployments could get into an infinite loop when deploying an x64 Windows image captured by LTI. This issue has been fixed in MDT 2010 Update 1
Error handling improvements in MDT task sequence templates. In MDT 2010, task sequences appear to finish successfully even when they really failed. These issues are fixed in MDT 2010 Update 1.

Download the new version HERE

No tags for this post.

Deploy Office 2010 with Multiple Languages with MDT 2010

Ward — Thu, 24 Jun 2010 13:40:35 +0000

I Like Office 2010. For me it is the best Office version i ever worked with.
MDT 2010 it’s great tool that Microsoft created.
Now i will talk about how you deploy Office 2010 with Multilanguage packs with MDT 2010.

Step 1: Download the Office 2010 English version booth will be in x86 & x64

Step 2. Download the Office 2010 (language) Multilanguage iso only available from the Microsoft Volume Licensing site. Both in x86 en x64.

Step 3. Add the Office 2010 English version to MDT 2010 here office-2010-uitrollen-met-mdt-2010

Step 4. Extract the Office 2010 (language) Multilanguage iso with 7zip in the same application folder witch you created in Step 3.

Step 5. When you open MDT 2010 management console and you go to the Office 2010 Application that you added in step 3. You wil see that MDT sees more the one language. In my case it was en-us and nl-nl. The Screenshot is from the older MDT 2010 you MDT sees Office 2010 as Office 2007. MDT 2010 beta 1 supports Office 2010. I found till now no issues deploying Office 2010.

Step 6. Check the languages that you want. Check the Screenshot how i did it.

Step 7. Deploy the a Windows XP or Windows 7 client with Office 2010 Multilanguage versions.

Step 8. You can check with Microsoft Office 2010 Language Preferences or the languages that you configured are installed.

Step 9. Use Group Policy to set the language settings for users

Download the Office 2010 policy template files to your computer. You will find them HERE
Make a new GPO named Office 2010 languages settings it is a user policy.
Under User Configuration in the console tree, right-click Administrative Templates.
Click Add/Remove Templates, and then click Add.
In the Policy Templates dialog box, click the template that you want to add, and then click Open.
After you add the Office 2010 templates, click Close.
Open the Group Policy object (GPO) for which you want to set policy.
Double-click User Configuration and expand the tree under Administrative Templates.
Locate language-related policies in the Microsoft Office 2010 \ Language Settings node.
Select the languages that you want to use for each setting.
Save the GPO.
Go Testing

No tags for this post.

Where to find the right MDT 2010 logs

Ward — Fri, 11 Jun 2010 11:52:06 +0000

Each MDT 2010 script automatically creates log files during its execution. The names of these log files match the name of the script—for example, ZTIGather.wsf creates a log file named ZTIGather.log. Each script also updates a common master log file (BDD.log) that aggregates the contents of the log files that MDT 2010 scripts create. MDT 2010 log files reside in C:\MININT\SMSOSD\OSDLOGS during the deployment process. Depending on the type of deployment being conducted, the log files are moved at the completion of the deployment to either %WINDIR%\SMSOSD or %WINDIR%\TEMP\SMSOSD. For Lite Touch Installation (LTI) deployments, the logs start in C:\MININT\SMSOSD\OSDLogs. They end up in %WINDIR%\TEMP\DeploymentLogs when task sequence execution is complete.

MDT 2010 creates the following log files:

BDD.log: This is the aggregated MDT 2010 log file that is copied to a network location at the end of the deployment if you specify the SLShare property in the Customsettings.ini file.

LiteTouch.log: This file is created during LTI deployments. It resides in %WINDIR%\TEMP\DeploymentLogs unless you specify the /debug:true option.

Scriptname.log: This file is created by each MDT 2010 script. Scriptname represents the name of the script in question.

SMSTS.log: This file is created by the Task Sequencer and describes all Task Sequencer transactions. Depending on the deployment scenario, it may reside in %TEMP%, %WINDIR%\System32\ccm\logs, or C:\_SMSTaskSequence, or C:\SMSTSLog.

Wizard.log: The deployment wizards create and update this file.

WPEinit.log: This file is created during the Windows PE initialization process and is useful for troubleshooting errors encountered while starting Windows PE.

DeploymentWorkbench_id.log: This log file is created in the %temp% folder when you specify a /debug when starting the Deployment Workbench.

No tags for this post.

MDT 2010 Update 1 Beta Released

Ward — Fri, 14 May 2010 15:02:44 +0000

The Solution Accelerators Team have released Microsoft Deployment Toolkit 2010 Update 1 Beta and would like your feedback.

Download the beta now at https://connect.microsoft.com/site14/Downloads/DownloadDetails.aspx?DownloadID=8689

MDT 2010 Update 1 provides new capabilities, such as:

· Support for Microsoft Office 2010.

· A new User-driven Installation (UDI) deployment method (formerly known as “Modena”) for Microsoft System Center Configuration Manager 2007. UDI gives information technology (IT) staff control over the deployment experience while empowering users to interact with and customize their operating system deployment through an easy-to-use wizard.

· Improvements to the Deployment Workbench driver import process, detecting each driver’s true supported platforms.

· Many bug fixes and other small improvements.

This release supports the deployment of the Windows® 7; Windows Vista®; Windows XP; Windows Server® 2008 R2; Windows Server 2008; and Windows Server 2003 operating systems. See the Microsoft Deployment Toolkit Documentation Library, which is included with MDT 2010 Update 1, for the complete documentation for this release.

Tags: 2003, 2008, 2008 R2, Deployment, MDT 2010, Microsoft, Office 2010, System Center, Vista, Windows, XP

MDT HP,Lenovo,Dell tools for getting the right drivers for a specific model

Ward — Wed, 12 May 2010 06:35:11 +0000

When you search a driver for a specific model you always go to the HP, Dell, Lenovo, Dell site and then you go to download section and chose the model of your pc/laptop and os version and download the drivers.

The Are some handy tools for you:

Dell Tool:
Dell makes drivers driver CABs which incluse all your drivers for your model and OS.

HP Tool:
HP SoftPaq Download Manager provides a simple, powerful way to download software updates for the HP client PC models in your environment. HP SDM can significantly reduce the amount of time it takes to locate and download updates. SoftPaqs can be downloaded in as few as three easy steps from a single user interface after initial setup.

Lenovo Tool:
ThinkVantage Update Retriever enables you to download update packages from the Lenovo Help Center Web site to a network share repository folder.
This is a search tool. You give the model nummer en os and Update Retriever and scan the Lenovo Help Center Web site for the latest driver

Tags: Deployment, Tools

WAIK Add Drivers to a Wim File

Ward — Sun, 09 May 2010 12:16:34 +0000

Some handy Windows 7 Waik commands to add drivers to a wim file.
Before you start copy the wim file to your harddisk

1. Some information about the Wim:
Dism /Get-WimInfo /WimFile:d:\boot.wim

2. Mount the wim file to a folder:
Dism /Mount-Wim /index:1 /WimFile:d:\boot.wim /MountDir:d:\mountpe

3. Add the Driver:
Dism /Image:d:\mountpe /Add-Driver /Driver:d:\nic\b57nd60x.inf

4. Close the wim file and saving the file:

Dism /Unmount-Wim /MountDir:d:\mountpe /Commit

Tags: Windows, Windows 7

Restore an Windows 7 Capture with MDT 2010

Ward — Fri, 23 Apr 2010 10:19:37 +0000

Step1: Import the Capture Image.

You can find the capture file at \\server\deploymentshare$\Capture or x:\deploymentshare\capture.

If you have already imported Windows 7 DVD.
You can chose for Sysprep and Setup files are not needed. The Setup will copy them automatically when de Capture wil be deployed.

Step 2. Create a Normal Client Task with the OS Capture that you imported.

Tags: Deployment, MDT 2010, Windows, Windows 7

Capture an Existing Windows 7 install with MDT

Ward — Wed, 21 Apr 2010 12:21:45 +0000

You can With MDT capture an existing Windows 7 Install.
1. Creating the Task in MDT

Jou must Chose the OS version witch you want to capture.

2. Create a copy from the Customsettings.ini
Edit the Customsettings.ini with de following text.

[Settings]
Priority=Default
Properties=MyCustomProperty

[Default]
OSInstall=Y
SkipAppsOnUpgrade=YES
SkipCapture=NO
SkipAdminPassword=YES
SkipProductKey=YES

4. Connect to the deployement share \\server\deploymentshare$ and go to the folder script and double click on LiteTouch.vbs

4. Don’t forget after the Capture to restore the original customsettings.ini file.

Tags: Deployment, Windows, Windows 7

Solution for "Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed"

Ward — Tue, 20 Apr 2010 07:05:07 +0000

When you use MDT you see many times the following error:
"Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed"

Solution 1:
To fix the problem you should edit the ztiutility.vbs file in the deployment share under the scripts folder. Open the file in notepad and replace the following code in the MapNetworkDriveEX function:

Case Else
‘ Case &h800704C3 ‘ Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed.
‘ Case &h8007052E ‘ Logon failure: unknown user name or bad password.
‘ There was a some kind of fatal error.
If ErrDesc <> "" then
MapNetworkDriveEx = ErrDesc
Else
MapNetworkDriveEx = "Unable to map UNC Path " & sShare & " :" & "( 0x" & hex(HasError) & " ) "
End if
oLogging.CreateEntry MapNetworkDriveEx & "", iLogType
Exit function
End select

With this code:

Case Else
Err.Clear
On Error Resume Next
oNetwork.MapNetworkDrive chr(sDrive)&":", sShare, False
HasError = err.number
ErrDesc = err.Description
On Error Goto 0
If Err.Number <> 0 Then
‘ There was a some kind of fatal error.
             If ErrDesc <> "" then
                                        MapNetworkDriveEx = ErrDesc
             Else
                                        MapNetworkDriveEx = "Unable to map UNC Path " & sShare & " :" &    "( 0x" & hex(HasError) & " ) "
             End if
             oLogging.CreateEntry MapNetworkDriveEx & "", iLogType
             Exit function
Else
      Exit Function
End If

End select

Solution 2

Download ZTIUtility.7z and replace the ztiutility.vbs with the one in the ZTIUtility.7z. You need 7zip to unpack the file.

http://support.microsoft.com/kb/977566

Tags: Deployment, Microsoft

MDT 2010 Health Care

Ward — Tue, 23 Mar 2010 14:38:07 +0000

MDT 2010 Health Care is een samenvatting van best practices voor het aanpassen, bouw en migreren, en beveiligen van Windows XP, Windows Vista of Windows 7 machines. Ook wordt hier kort beschreven hoe men applicaties kan uitrollen (scripted installs,silent installetie, application packages) als onderdeel van de uitrol. Het gaat om het uitrollen van een standaard desktop voor gemeenschappelijk gebruik. Tevens wordt besproken hoe men de gegeven van een gebruiker mee kan nemen naar de nieuwe werkplek.

Handleidingen:
Healthcare Desktop User State Migration Guide
Automated Build Application Integration Guide
Healthcare MDT 2010 Administrators Guide
Automated Build Healthcare Desktop and Server Guide

Downloaden van de MDT HealthCare doe je hier: MDT HealthCare

Installatie:

Voorbeeld wat Health Care automatisch aanmaakt:

Tags: MDT 2010, Microsoft, Vista, Windows, Windows 7, XP

MDT 2010 Deploy per Computer of per Model MDT DataBase Config

Ward — Mon, 15 Mar 2010 18:31:31 +0000

Met MDT 2010 kun je ook Applicaties per Model of per Computer deployen.
In het artikel MDT 2010 Deploy per Computer of per Model heb ik uitgelegd om de juiste te achter halen.

Per Computer:

Per Model (Getest met een Virtuele XP Machine):

Tags: MDT 2010, XP

MDT 2010 Deploy per Computer of per Model

Ward — Fri, 12 Mar 2010 15:26:58 +0000

Met de volgende commando’s krijg je de info om per Computer of Model te Deployen.

WMI Model & Manufacturer:
Get-WmiObject -Class win32_computersystem | fl Name,Model,manufacturer

WMI UUID, Vender:
Get-WmiObject -Class win32_computersystemproduct | fl Name,Model,UUID,Identifyingnumber,Vendor

Tags: MDT 2010

MDT2010 Configure Database Options

Ward — Wed, 10 Mar 2010 18:48:51 +0000

Zorg dat NT AUTHORITY\ANONYMOUS LOGON toegang heeft tot de MDT 2010 Database en de rechten db_datareader krijgt.

Tags: MDT 2010

MDT 2010 Aanmaken Database

Ward — Wed, 10 Mar 2010 18:47:26 +0000

Tags: MDT 2010

Microsoft Security Essentials voor XP uit rollen met MDT

Ward — Sat, 09 Jan 2010 18:13:18 +0000

1.Maak onder Application een map aan genaamd Microsoft Security Essentials
Kopieer naar deze map de file mssefullinstall-x86fre-nl-nl-xp. Dit kun je natuurlijk ook voor de Windows 7 versie doen.

2. Open MDT . Ga naar Applications en kies voor New Application without source files or somewhere else on the network

3. Vul de juiste gegeven in. Microsoft Security Essentials voor XP

4. Command Line: mssefullinstall-x86fre-nl-nl-xp.exe /s /runwgacheck
working directory: .\Applications\Microsoft Security Essentials

6.

Klaar om uitgerold te worden

Tags: Microsoft, Windows, Windows 7, XP

Mcafee framepkg.exe uitrol met MDT

Ward — Sat, 09 Jan 2010 18:12:23 +0000

Mcafee framepkg.exe in MDT hangen voor automatische uitrol.
1.Maak onder Application een map aangenaamt Mcafee Epo Agent. Kopieer naar deze map de file framepkg.exe

2. Open MDT . Ga naar Applications en kies voor New Application without source files or somewhere else on the network

3. Vul de juiste gegeven in. Mcafee EPO Agent 4.5

4. Commando: Framepkg.exe /install=agent /s
working directory: .\Applications\Mcafee Epo Agent\

Klaar om uitgerold te worden.

No tags for this post.

MDT AMD PCNET32 (AMD Am79C790A0) driver voor VMWARE

Ward — Mon, 28 Dec 2009 19:36:09 +0000

Heel veel mensen gebruiken MDT om via windows PE boot via PXE Boot om een nieuw OS uit te rollen binnen VMWare. Heel veel mensen rollen standaard een XP of een 2003 machine uit. Standaard kiest VMWare voor de flexible adapter de AMD PCNET32 adapter. Alleen als je de driver gebruikt die standaard met VMWare meegeleverd wordt krijg je de volgende error tijdens het opstarten de Lite Touch Image.

Je krijgt dan de volgende error:

De standaard driver die VMWare mee levert in VMWare Tools werkt niet binnen een Windows PE image. Wel als Windows een maal geïnstalleerd is.

Oplossing:
Download van de AMD site de NDIS5 driver voor Microsoft Windows Server 2003, Windows XP

PCNET Family Software vind je HIER en de juiste driver voor MDT (WinPE) vind je HIER

Tags: 2003, Microsoft, Tools, VMWare, Windows, XP

MDT 2010 Geen Extra Systeem Partitie Windows 7 & 2008 R2 ivm Bitlocker

Ward — Sun, 20 Dec 2009 13:09:17 +0000

Wanneer je een Windows 7 of een Windows 2008 R2 machine uitrolt wordt er een extra partitie aangemaakt van 100 tot maximaal 300mb voor bitlocker.

Ga je toch geen gebruik maken van Bitlocker dan moet je de volgende regel toevoegen aan Customsettings.ini: DoNotCreateExtraPartition = YES dan wordt namelijk er geen extra partitie aangemaakt.
Bron: Frontslash

Tags: 2008, 2008 R2, MDT 2010, Windows, Windows 7

MDT 2010 Join Domain

Ward — Sun, 20 Dec 2009 13:00:09 +0000

Kopieer de volgende gegevens in Customsettings.ini.

Indien de computer al bestaan blijft hij in de huidige OU staan. Indien het een nieuwe computer is zal in mijn geval onder de test ou terecht komen.

SkipDomainMembership=YES
JoinDomain=wardvissers.local
DomainAdmin=administrator
DomainAdminDomain=wardvissers.local
DomainAdminPassword=************
MachineObjectOU=OU=Test,DC=wardvissers,DC=local

Tags: MDT 2010

MDT 2010 Unattend.txt error The Specified Setup script file c:\minint\unattend.txt is inaccessible of invalid.

Ward — Wed, 09 Dec 2009 13:50:16 +0000

Ik krijg de volgende error bij MDT bij het uitrollen van een XP Machine.
The Specified Setup script file (c:\minint\unattend.txt) is inaccessible of invalid.
Contact your system administrator.

litetouch.log

bdd.log

Overige logs zijn allemaal succesvol.

Overzicht LOG’s

Ik heb van alles geprobeerd ik krijg steeds de volgende melding terug. OS & KEY zijn geldig 100% zeker. Nieuwe virtuele machine geïnstalleerd met MDT 2010 krijg steeds de zelfde melding terug.
Rechten opnieuw door laten lopen geen idee wat het is. Wel steeds oude bootstrap.ini en customsettings.ini gebruikt. Schone deployment share aangemaakt. OS Deployment loopt goed.

Oplossing:

Heb een nieuwe customsettings.ini gemaakt en het werkt weer weer een irritant probleem opgelost

Tags: Deployment, MDT, MDT 2010, XP

MDT Wachtwoord Wijzigen van een OS taak

Ward — Sun, 06 Dec 2009 13:19:49 +0000

Voor de desbetreffende Windows XP, Windows 2003 task klik properties en ga dan naar het tabblad OS info. Pas het wachtwoord aan in de sysprep.inf & unattend.txt

Voor de desbetreffende Windows 7 & Windows Vista & Windows 2008 & Windows 2008 R2 task
klik properties en ga dan naar het tabblad OS info. Klik op Unattend.xml

Onder oobeSystem –> amd64_Microsoft-Windows-Shell-Setup_neutral –> UserAccounts –> AdministratorPassword

Tags: 2003, 2008, 2008 R2, MDT, Microsoft, Vista, Windows, Windows 2003, Windows 2008, Windows 2008 R2, Windows 7, Windows XP, XP

MDT IT Organisatie wijzigen

Ward — Tue, 01 Dec 2009 14:00:00 +0000

Stel je bent aan het deployen en je ergert je aan de naam IT Organization

Wijzigen doe je met de variable _SMSTSORGNAME in de customsettings.ini file.

Bijvoorbeeld

[Settings]
Priority=Default
Properties=MyCustomProperty
[Default]
OSInstall=Y
_SMSTSORGNAME=Ward ICT Test Omgeving

Tags: MDT

MDT Achtergrond Wijzigen

Ward — Tue, 01 Dec 2009 13:59:23 +0000

Open de MDT Deployment Share Properties

In de twee tabs Windows PE x86 Settings & Windows PE x64 Settings vind de instellingen.

Bijvoorbeeld: Windows PE x86 Settings

Onder Windows PE Customizations vind je Custom Background Bitmap file:
Deze verwijst standaard naar: %installdir%\Samples\Background.bmp
Eigenlijke map is: C:\Program Files\Microsoft Deployment Toolkit\Samples

Her noem het de huidige Background.bmp naar Background Oud.bmp
Plaats in de zelfde map nu de nieuwe achtergrond met de naam Background.bmp

Je moet nu nog Update Deployment Share doen en zorg er voor dat regenerate boot image aanvinken.

Voeg als laatste de twee wim files opnieuw toe aan WDS en als je alles goed hebt gedaan heb je nu een custom achtergrond tijdens deployen in je achtergrond n.

Tags: Deployment, MDT, Microsoft, Toolkit, WDS, Windows

Ward Vissers » Deployment

MDT 2010 Multiple Partitions Issues & hidden Bitlocker partition

Related posts

MDT 2010 Importing automatically the right driver

Related posts

Microsoft Deployment Toolkit (MDT) 2010 Update 1 is RTM

Related posts

Deploy Office 2010 with Multiple Languages with MDT 2010

Related posts

Where to find the right MDT 2010 logs

Related posts

MDT 2010 Update 1 Beta Released

Related posts

MDT HP,Lenovo,Dell tools for getting the right drivers for a specific model

Related posts

WAIK Add Drivers to a Wim File

Related posts

Restore an Windows 7 Capture with MDT 2010

Related posts

Capture an Existing Windows 7 install with MDT

Related posts

Solution for "Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed"

Related posts

MDT 2010 Health Care

Related posts

MDT 2010 Deploy per Computer of per Model MDT DataBase Config

Related posts

MDT 2010 Deploy per Computer of per Model

Related posts

MDT2010 Configure Database Options

Related posts

MDT 2010 Aanmaken Database

Related posts

Microsoft Security Essentials voor XP uit rollen met MDT

Related posts

Mcafee framepkg.exe uitrol met MDT

Related posts

MDT AMD PCNET32 (AMD Am79C790A0) driver voor VMWARE

Related posts

MDT 2010 Geen Extra Systeem Partitie Windows 7 & 2008 R2 ivm Bitlocker

Related posts

MDT 2010 Join Domain

Related posts

MDT 2010 Unattend.txt error The Specified Setup script file c:\minint\unattend.txt is inaccessible of invalid.

Related posts

MDT Wachtwoord Wijzigen van een OS taak

Related posts

MDT IT Organisatie wijzigen

Related posts

MDT Achtergrond Wijzigen

Related posts