Permissions within MDT Deployment Workbench

We are using ConfigMgr with a MDT Integrated task sequence.
We recently had an issue where a developer made changes to the production role, instead of the development role causing all builds in production to fail.
Short of telling devs 'dont do that' is there any way to secure what an individual can and cannot edit within MDT? Ideally we'd have only our validation team able to edit the production roles, with the developers only modifying the non-production roles.
This is accomplished through scoping in SCCM, but I see nothing similar in MDT.
Has anyone else successfully implemented something to this end?
Will
Will

I'm slightly confused. Are you using ConfigMgr for all of your deployments or do you have ConfigMgr as well as an MDT Litetouch environment?
As you mentioned, ConfigMgr access is controlled with RBAC. MDT Litetouch (standalone) doesn't have anything like RBAC; at best, you would be relegated to looking at security permissions on the deployment share or perhaps setting up a second deployment share
for non-production tasks.
-Nick O.
We are using ConfigMgr for deployment, but storing different load configurations in MDT. The build configuration is populated in MDT, and the task sequences determines which applications to install by querying the role from MDT.
One role within MDT will be 'finance', while the other will be 'finance-dev'. Unfortunately these are just rows in a database, so I think MDT lacks in any way to limit which items a user can edit.
Hoping someone can tell me otherwise...
Will

Similar Messages

Keyboard doesn't work in vmguest.iso created by Deployment Workbench program

Hello,
I created the boot image for reference computer using MDT Deployment Workbench and wanted to run it on a virtual machine using HyperV for testing.
The vmguest.iso image boots succesfully but the keyboard input in windowsPE doesn't work, neither the hyper-v "Paste from clipboard" option.
Any ideas how to solve it?
Regards
Mario

You really should keep all correspondence on the same issue on the same thread. That is good forum ettiquette. Please continue in this thread.
I am sorry but I don't have any more information that could help you.

MDT 2012 Deployment Workbench cannot genererate catalog for any images

It just hangs generating a catalog for the operating system (Windows 7 64-bit) and says it "could take a long time."
I have tried with multiple images.
I have waited a long time (more than 30 minutes) and the progress bar will not move.
I click Stop Execution and it tries to stop, but doesn't compete the process of stopping.
The only way to get out of it is to use task manager to force it to quit. Then the Deployment Workbench will no longer load until the entire server is restarted.
How can this be fixed?

If you're storing the image on a filer, it can take a bit sometimes to process a catalog file. If you're really curious what the heck it's doing and think it's frozen -- because I've gotten into the same place and thought what is this thing doing?? Check
the logfile it generates at %temp%\Microsoft.BDD.Catalog.log . It doesn't log much but will log progress for you.
Also, the image needs to be open for a catalog to be created. It will mount it in the same %temp% directory, under a long path named after the tasksequence ID. That error you saw when on another account was most likely that the WIM you were building
a catalog for was already mounted, or the mount was corrupted at that point. To resolve an error like that in the future -
1. dism /get-mountedwiminfo -- note the really long pathed image mounted to the temp directory.
2. dism /unmount-wim /mountdir:%TEMP%\whateverthefolderis /discard
3. Retry catalog creation. Usually any errors during catalog creation will be from a stale image or image in use. Checking /get-mountedwiminfo will often tell you right away if there's an issue and mark the status : Needs Remount.
Best bet with creating catalogs, watch the bdd catalog log in temp and just don't touch anything else for 15-60mins depending on network latency. Hope this helps.
Ryan

Help With Deployment Workbench Defaults

I have inherited a WDS box that seems to have images on it when I PXE boot to it. But when I go to the Deployment Workbench, nothing is listed under Deployment Shares.
How is this box deploying images? It does boot into Lite-Touch X64 when I PXE to it.
When I create a new share, it still boots to the old Lite-Touch image with the outdated images on it.
Any help you could provide would be great! Thanks in advance.

I think there is a disconnect here.
The Bootstrap.ini file is stored on your Deployment Share \\server\DeploymentShare$\control\bootstrap.ini
You can edit this file all you want... However... the changes won't get reflected in your WDS boot image ... until ... you perform the "Update Deployment Share" task within the MDT Console *AND* upload the new
\\server\DeploymentShare$\Boot\LitetouchPE_x??.wim image to your WDS Server.
If you are unsure if you performed the "update" step properly, then use a tool like 7-zip to Open the *.wim file and verify the <WIM>:\deploy\scripts\bootstrap.ini file within the *.wim file was updated correctly.
If you are still having problems logging in, then press F8, and verify the x:\deploy\scripts\bootstrap.ini file points to the *CORRECT* server. Then, use your System Administrator Experience to manually connect to the server specified in the bootstrap.ini
file:
net.exe use * \\server\deploymentShare$ /u:server\username *
If you can not connect to the server, then the problem is on your end with your server, user account or permissions, if you can connect to the server, then there is some other problem, I don't know.
Keith Garner - Principal Consultant [owner] -
http://DeploymentLive.com

Deployment Workbench MMC Error

Problem,
I am getting MMC console error while opening deployment Workbench at few locations.
Error:
MMC has detected an error in a snap-in and will unload it
FX:-{ffb8695a-66b4-4929-abb6-15cb8bd2ae3d}
Type 'Microsoft.BDD.Workbench.WrapperException' in assembly
Exception type:
System.Runtime.serialization.SerializationException
Thanks in Advance
Dinesh Vinay
Thanks & Regards, Dinesh Sundaram

I've just had this issue. Here's how I fixed it.
PS C:\> Import-Module 'C:\Program Files\Microsoft Deployment Toolkit\Bin\MicrosoftDeploymentToolkit.psd1'
PS C:\> Get-MDTPersistentDrive
Name Path Description
DS001 \\Server01/Distribution MDT Deployment Share
PS C:\> Remove-MDTPersistentDrive -Name DS001
Messed up rights to the remote server share or something.
Blog: http://scriptimus.wordpress.com

Deployment Workbench Adding Applications Using Task Sequence

I am trying to figure out how to add applications in Deployment Workbench. My biggest issue is what to put in the command line to get it to work. Someone else created folders with everything that would needed along with a batch file. Now I am trying to
figure out how to get that to work in Deployment Workbench. I am also trying to figure out how to then get it to work in Task Sequence since it is not currently working the way I have tried. Thanks.

Hi,
Here is a guidance for you:
Installing Applications with MDT.
http://lethewookiewin.wordpress.com/2011/04/21/84/
You referred that something didn’t work for you, can you kindly provide the error message? If you were using any scripts you can also attach them.
Thank you.

Folders are Empty in Deployment Workbench - Can See Monitoring Though?

When I use the deployment workbench on my primary machine, every primary folder is empty except Advanced Configuration and Monitoring. I can't see any sub-folders (ex: we have our Drivers divided into folders). I can go inside of Advanced Configuration
and edit any item. I can go to monitoring and interact normally. My client OS is Windows 8.1 Update 1.
If I remote into our deployment server, the workbench behaves normally - I can see the contents of every folder (including sub folders). Our server is Windows 2012 R2 Update 1 - we are running MDT 2013
If my answer helped you, check out my blog:
DeployHappiness. Subscribe by
RSS or
email.

Follow up. If I open the deployment share as
\\SERVER\c$\deploymentshare, I can see it. I can't see it as
\\server\deploymentshare$\
I can browse both paths fine in Explorer. I have FC to the share and the folders. I am an admin to the server.
If my answer helped you, check out my blog:
DeployHappiness. Subscribe by
RSS or
email.

MDT Deployment share and SQL Share on different servers

Hello Technet,
I would like help to figure out how to deal with my MDT Deployment share being on a different server than my SQL Share. I am trying to use the MDT Database in MDT 2013 and SQL Server Express 2014. My deployment share is located on a Linux File Server share,
and my MDT Server and SQL Express Server are located on the same Windows Server 2012 VM.My Bootstrap.ini therefore looks like this:
[Settings]
Priority=Default
[Default]
SkipBDDWelcome=YES
DeployRoot=\\192.168.1.10\DeploymentShare$
UserID=user
UserPassword=password
my Customsettings looks like this:
[Settings]
Priority=CSettings, CPackages, CApps, CAdmins, CRoles, Locations, LSettings, LPackages, LApps, LAdmins, LRoles, MMSettings, MMPackages, MMApps, MMAdmins, MMRoles, RSettings, RPackages, RApps, RAdmins, TaskSequenceID,Default
[Default]
CaptureOS=YES
[CSettings]
SQLServer=SQLServer
Instance=SQLEXPRESS
Database=MDT
Netlib=DBNMPNTW
SQLShare=Logs
Table=ComputerSettings
Parameters=UUID, AssetTag, SerialNumber, MacAddress
ParameterCondition=OR
Therefore, the problem is that during winPE Bootup, WinPE connects to the deploymentshare using the provided credentials just fine, and tries to process customsettings. However, I can map a network drive to the SQL Share as seen in the logs by the following
errors:
1.ERROR-Unable to map a network drive to \\SQLServer\Logs
2. ZTI Error opening SQL Connection:[DBNETLIB][ConnectionOpen(Connect()).]SQL Server does not exist or access is denied.
3.Unable to establish database connection using [CAPPS] properties.
In WinPE, as soon as I hot F8, and use net use \\SQLServer\Logs, the deployment works fine and the properties are read from the database during each section process..
Why is MDT Unable to map the \\SQLServer\Logs , and it requires the manual use of net use? Must I move the deployment share to the same server as my SQL Server Server? Thanks so much.

Should work, Don't know why it's failing.
Can you post your full bdd.log file to a public site like OneDrive and share the link?
There are some inconsistencies with your written summary above.
Keith Garner - Principal Consultant [owner] -
http://DeploymentLive.com

Adobe Reader deployment via SCCM/Deployment Workbench/WDT

We're trying to deploy Reader 9.3.4 and basically I have the slipstreamed file and have customized transforms file (MST) to suppress the EULA and disable all Acrobat.com and Adobe Updates.
The only thing that works is the suppression of the EULA. The updates are still there and the Acrobat.com account things are still there.
The weird thing is if I copy off the folder via the share and run the msiexec /i AcroRead.msi TRANSFORMS=AcroRead.mst /qn via the command line - it installs and disables everything perfectly.
We are deploying brand new computers and via Deployment Workbench (Windows Deployment Toolkit) it will run the installer + the added command line parameters. The weird thing is that it obviously works since the EULA gets suppressed but the disable updates does not run whatsoever. It's like it is forgetting to do this and or the proper changes are not taking place. I even tried adding a registry key via the Adobe Customization Wizard tool but even that did not take.
Any ideas?
Computers are Windows XP with SP3.

Hi,
Can you please let me know, how is it that you are trying to disable the update to both Adobe and Acrobat.com? Are you doing it through the "Online and Acrobat.com Features" section? If so, then are the corresponding registry entries getting created in the HKLM section or is it that inspite of the registries getting created, the features are not getting disabled.

MDT Deployment for Windows 8 (Sysprep failes with generalization setting)

Here's my issue...
I'm trying to capture and redeploy Windows 8. In of itself, the capturing and deploying works well. Except for one thing, I can't default the desktop nor can I default the Start Tiles for the start tiles. Upon a visit with Microsoft and
confirmation of a few colleagues, I tried the tutorial listed here, http://msdn.microsoft.com/en-us/library/jj134269, using method 1 the copyprofile.
I have this set up for the unattended on the MDT deployment, but my problem is the issue that I'm running into which is the failure in sysprep running the /generalize tag. Whether I use OOBE or Audit results in the same thing. I have built a
couple of fresh images as well and sysprep keeps failing. I've attached the error log below. So far research has come up with nada, so I can't even getting started on troubleshooting the error.
Here's the error log below.
2012-10-03 14:36:09, Error                 SYSPRP Package Microsoft.VCLibs.110.00_11.0.50727.1_x86__8wekyb3d8bbwe was installed for a user, but not provisioned for all users.
This package will not function properly in the sysprep image.
2012-10-03 14:36:09, Error                 SYSPRP Failed to remove apps for the current user: 0x80073cf2.
2012-10-03 14:36:09, Error                 SYSPRP Exit code of RemoveAllApps thread was 0x3cf2.
2012-10-03 14:36:09, Error      [0x0f0082] SYSPRP ActionPlatform::LaunchModule: Failure occurred while executing 'SysprepGeneralize' from C:\Windows\System32\AppxSysprep.dll; dwRet = 0x3cf2
2012-10-03 14:36:09, Error                 SYSPRP ActionPlatform::ExecuteAction: Error in executing action; dwRet = 0x3cf2
2012-10-03 14:36:09, Error                 SYSPRP ActionPlatform::ExecuteActionList: Error in execute actions; dwRet = 0x3cf2
2012-10-03 14:36:09, Error                 SYSPRP SysprepSession::Execute: Error in executing actions from C:\Windows\System32\Sysprep\ActionFiles\Generalize.xml; dwRet = 0x3cf2
2012-10-03 14:36:09, Error                 SYSPRP RunPlatformActions:Failed while executing SysprepSession actions; dwRet = 0x3cf2
2012-10-03 14:36:09, Error      [0x0f0070] SYSPRP RunExternalDlls:An error occurred while running registry sysprep DLLs, halting sysprep execution. dwRet = 0x3cf2
2012-10-03 14:36:09, Error      [0x0f00a8] SYSPRP WinMain:Hit failure while processing sysprep generalize internal providers; hr = 0x80073cf2

Did you ever figure out how to make this work?
I have the same problem with my Win8 64 image -- as soon as I installed the 11 Microsoft Metro app updates from "Store", I can no longer sysprep my image without getting the same "fatal error" (with the exact same log -- except for a different "Package"
listed):
2012-10-10 15:58:47, Error SYSPRP Package Microsoft.WinJS.1.0_1.0.9200.20512_neutral__8wekyb3d8bbwe
was installed for a user, but not provisioned for all users. This package will not function properly in the sysprep image.
2012-10-10 15:58:47, Error SYSPRP Failed to remove apps for the
current user: 0x80073cf2.
2012-10-10 15:58:47, Error SYSPRP Exit code of RemoveAllApps thread
was 0x3cf2.
2012-10-10 15:58:47, Error [0x0f0082] SYSPRP ActionPlatform::LaunchModule: Failure occurred while executing
'SysprepGeneralize' from C:\Windows\System32\AppxSysprep.dll; dwRet = 0x3cf2
2012-10-10 15:58:47, Error SYSPRP ActionPlatform::ExecuteAction:
Error in executing action; dwRet = 0x3cf2
2012-10-10 15:58:47, Error SYSPRP ActionPlatform::ExecuteActionList:
Error in execute actions; dwRet = 0x3cf2
2012-10-10 15:58:47, Error SYSPRP SysprepSession::Execute: Error
in executing actions from C:\Windows\System32\Sysprep\ActionFiles\Generalize.xml; dwRet = 0x3cf2
2012-10-10 15:58:47, Error SYSPRP RunPlatformActions:Failed while
executing SysprepSession actions; dwRet = 0x3cf2
2012-10-10 15:58:47, Error [0x0f0070] SYSPRP RunExternalDlls:An error occurred while running registry
sysprep DLLs, halting sysprep execution. dwRet = 0x3cf2
2012-10-10 15:58:47, Error [0x0f00a8] SYSPRP WinMain:Hit failure while processing sysprep generalize
internal providers; hr = 0x80073cf2
The app updates are *coming from Microsoft* -- so why would I need to provision them (according to that article?)
This seems like a bug...
(The workaround, of course, is to just not update Metro apps on my main image, but that seems rather silly to not be
allowed to do that...)

MDT Deployment Error

Hi
I'm having an issue with MDT deploying windows 7 on one particular Workstation. The same MDT environment works with other machines no problem.
the error message given is "Litetouch deployment failed, Return Code = -2147467259 0x80004005   LiteTouch   04/06/2014 06:42:56   0 (0x0000)"
The result is I have the OS files copied and seemingly installed correctly however on reboot the dreaded
"BOOTMGR is missing Press Ctrl Alt Del to restart" message appears
I have tried to use bootrec with all the different parameters to fix the problem to no avail
Errors from The BDD log as below
Console > [ RETRY ] Restoring C:\Windows\winsxs\Manifests\amd64_microsoft-windows-gadgets-cpu.resources_31bf3856ad364e35_6.1.7600.16385_en-us_a9893e83c110fe46.manifest again (Error = 8)   LTIApply   04/06/2014 06:42:27
0 (0x0000)
Console > [ RETRY ] Restoring C:\Windows\winsxs\Manifests\amd64_netathrx.inf_31bf3856ad364e35_6.1.7600.16385_none_cf0144fd71b44a1a.manifest again (Error = 8)   LTIApply   04/06/2014 06:42:34   0 (0x0000)
Console > [ RETRY ] Restoring C:\Windows\winsxs\Manifests\amd64_netbvbda.inf_31bf3856ad364e35_6.1.7600.16385_none_fa388bc43a1db8d8.manifest again (Error = 8)   LTIApply   04/06/2014 06:42:38   0 (0x0000)
Console > [ RETRY ] Restoring C:\Windows\winsxs\Manifests\wow64_microsoft-windows-security-identitystore_31bf3856ad364e35_6.1.7600.16385_none_a80db2b3efe7af3c.manifest again (Error = 8)   LTIApply   04/06/2014 06:42:43
0 (0x0000)
Console > [ RETRY ] Restoring C:\Windows\winsxs\Manifests\x86_microsoft-windows-vcm-core-codecs_31bf3856ad364e35_6.1.7600.16385_none_6c79173539c35f69.manifest again (Error = 8)   LTIApply   04/06/2014 06:42:47
0 (0x0000)
Command completed, return code = -2147467259   LiteTouch   04/06/2014 06:42:56   0 (0x0000)
Litetouch deployment failed, Return Code = -2147467259 0x80004005   LiteTouch   04/06/2014 06:42:56   0 (0x0000)
STMS LOG Errors
<![LOG[ContinueOnError: false]LOG]!><time="06:36:32.109+000" date="06-04-2014" component="TSManager" context="" type="1" thread="1932" file="tsxml.cpp:566">
<![LOG[ContinueOnError: false]LOG]!><time="06:36:32.109+000" date="06-04-2014" component="TSManager" context="" type="1" thread="1932" file="tsxml.cpp:566">
<![LOG[uRet == ERROR_ALREADY_EXISTS, HRESULT=80070003 (e:\nts_sms_fre\sms\framework\tscore\utils.cpp,916)]LOG]!><time="06:36:57.802+000" date="06-04-2014" component="TSManager" context="" type="0"
thread="1932" file="utils.cpp:916">
<![LOG[Failed to create user-specified local data path D:\_SMSTaskSequence. Error 0x80070003]LOG]!><time="06:36:57.818+000" date="06-04-2014" component="TSManager" context="" type="2" thread="1932"
file="utils.cpp:1004">
Unknown error (Error: 00000030; Source: Unknown)]LOG]!><time="06:42:55.511+000" date="06-04-2014" component="TSManager" context="" type="3" thread="1932" file="instruction.cxx:3101">
Operation aborted (Error: 80004004; Source: Windows)]LOG]!><time="06:42:55.573+000" date="06-04-2014" component="TSManager" context="" type="3" thread="1932" file="instruction.cxx:2424">
Unknown error (Error: 00000030; Source: Unknown)]LOG]!><time="06:42:55.573+000" date="06-04-2014" component="TSManager" context="" type="3" thread="1932" file="engine.cxx:214">
<![LOG[Task sequence execution failed with error code 80004005]LOG]!><time="06:42:55.604+000" date="06-04-2014" component="TSManager" context="" type="3" thread="1932" file="tsmanager.cpp:790">
<![LOG[Error Task Sequence Manager failed to execute task sequence. Code 0x80004005]LOG]!><time="06:42:55.979+000" date="06-04-2014" component="TSManager" context="" type="3" thread="1932"
file="tsmanager.cpp:689">
<![LOG[Sending error status message]LOG]!><time="06:42:55.979+000" date="06-04-2014" component="TSManager" context="" type="1" thread="1932" file="tsmanager.cpp:690">
If the complete logs files are required please let me know.

Yea, I can't tell what commands were running from the log snippets above. Can you copy to t public sire like Onedrive and copy the link here.
Keith Garner - Principal Consultant [owner] -
http://DeploymentLive.com

MDT Deployment Share on USB

Hi everyone..
can I use an external HDD to host my MDT deployment share.. Basically, I don't have enough drive space in my laptop to host the deployment share & the WIM's/Apps...
thanks in advance..

USB 3.0 drives are more than fast enough (over 1GB)
USB 2.0 drives are not as fast, but should be OK.
When combined with WDS Multicasting, I would feel confident using a 3 year old laptop to service a single install.wim over a hundred clients using USB 2.0.
However, if you are servicing more than 10 clients over unicast, you will start to get IO bound. Do your performance testing.
Keith Garner - Principal Consultant [owner] -
http://DeploymentLive.com

Using LabVIEW Packed Library within TestStand Deployment Tool

I am wondering what could be the interest of generating Packed Library within the TestStand Deployment Tool since the sequences using these VIs will not be able to find the dependant VIs included into the build Packed Library on the deployment target.
Any experience using Packed Library within TestStand Deployment Tool ?
Jean-Louis SCHRICKE
├ CTA - Certified TestStand Architect (2008 & 2010 & 2014)
├ CTD - Certified TestStand Developer (2004 & 2007)
└ CLD - Certified LabVIEW Developer (2003 & 2005)

Jiggawax,
Sorry for the confusion,
My question concerns the developement of Custom Step Types.
For example, within a project or as an independant product.
The best practices is to avoid using main module when developing CST in order to preserve evolutivity (main module calling paramters are copied within CST instances and could need prototype updating). I prefer using PostStep (as NI does for its own CST).
Thus, when creating the CST palette, I have to configure the EditStep and the PostStep and define each VI call.
If I want to distribute these VIs through a .lvlibp, then I need to build a .lvlibp very early and use it within my CST palette.
This .lvlibp will be used on deployed benches and may not contain VI diagrams and debug options (best performance).
But during the development of my CSTs, if I need to debug the VIs called when using CST whitin a sequence, and if I don't want to change the called VIs defined in my CST palette, then I need to regenerate this .lvlibp with debug option (different from the deployment .lvlibp) in order to allow debug.
May be it could be interesting that the TestStand deployment tool take into account SubSteps when selecting the Packed Library option. This tool is able to modify sequences, it could be able to change also palette configuration file.
This will allow to have only two levels :
> Source and Debug (VIs)
> Deployment (.lvlibp)
instead of three :
> Source (VIs)
> Debug (.lvlibp with debug option)
> Deployment (.lvlibp)
Jean-Louis SCHRICKE
├ CTA - Certified TestStand Architect (2008 & 2010 & 2014)
├ CTD - Certified TestStand Developer (2004 & 2007)
└ CLD - Certified LabVIEW Developer (2003 & 2005)

Dart tool not added in MDT 2013 deployment workbench

Hi, I have MDT 2013 installed, copied tools.cab for Dart 6.5 in the C:\Program Files\Microsoft Deployment Toolkit\Templates\Distribution\Tools\x86 and C:\Program Files\Microsoft Deployment Toolkit\Templates\Distribution\Tools\x64 folders. x86 version
can in x86 folder and x64 in x64 folder. However, I don't see dart tools in the WINPE Features packs in the deployment share properties. I need to deploy Windows 7. Can someone suggest what is wrong? I have tried copying the dart tools.cab files for dart 6.5
7.0 and 8.1 without success.

Finally i fixed it. I created a new deployment share and the dart components appeared in winpe feature packs list but still they did not the appear in already existing old deployment share properties. I check the folders tools\x86 folder and there was
no tools.cab even though i copied the cabs under C:\Program Files\Microsoft Deployment Toolkit\Templates\Distribution\Tools\x64
folders. So for some reason mdt was not copying the tools.cab into existing deployment share. I am not sure this is by default or issue with my environment. Anyways, i copied the relevent tools.cab in tools\x64 and tool\x86 folders of existing deployment
share and not am able to see the dart tools in winpe feature packs.

Deployment Workbench - how to capture an image after customisation?

I have deployed Vista to a machine using WinPE (Created through Workbench) and chose the option when deploying "Prepare for capture"
I then customised Vista - in this case removing the Fax applications and ran Sysprep with OOBE, Generalise and Shutdown.
In workbench I created a new task sequence 'Standard Client Replace task sequence' which seems to be the right task to capture an image.
When selecting the task when booting the machine with WinPE, it forces me to capture the user data - I cannot select 'Do not save data and settings'
I must be doing something wrong!
What I want to do is:
Deploy Vista
Install some apps manually i.e. not using a task sequence
Capture the image
Deploy to machines
How can I do this using Workbench? Thanks.

Hi,
Thank you for the reply.
I suggest referring to the following article:
Creating a Computer Image
http://technet.microsoft.com/en-us/library/bb977918.aspx
If you select “Capture an image of this reference computer” on the “Specify whether to capture an image” page when running Deployment Wizard, it will sysprep and capture the system for you automatically.
If you would like to
“Install Vista and prepare for capture
Install my own applications WITHOUT using task sequences
Capture the OS”,
I am afraid that you do not need to use MDT (you cannot perform a LTI without running Task Sequences). You can do this by only using WDS.
1.   Install and configure the WDS Server.
2.   Add the default Windows Server 2008 boot image to the WDS Server.
3.   Create Capture Boot Image and add it to boot image in WDS Server.
4. Create a reference computer (install the operating system, applications, and make any other changes)
5. Sysprep.
6. PXE boot the reference computer into capture image on the boot screen and then capture the image (If non-PXE supported, make a discover image to boot)
7. Upload the captured image to WDS server.
8. Clients can PXE boot and install Windows (If non-PXE supported, use a discover image to boot).
Hope it helps.
Tim Quan - MSFT

Permissions within MDT Deployment Workbench

Similar Messages

Maybe you are looking for