Image Layering Information > Deployment Forum Community Forums

Thursday, December 04, 2008

Library

Resources

Community

About

Community » Forums

Member Login

StandardLiveID

User Name:

Password:

Remember Login

Forgot Password ?


Guests can view and read messages in the community forums, but you must register and log in to Deployment Forum before you can post messages. Click Register at the top of this page. Before posting messages, please read the forum guidelines at the bottom of this page.

Unanswered Active Topics

Forums Search

Forums > Deployment Solutions > MDT 2008

Subject: Image Layering Information

Prev Next

You are not authorized to post a reply.

Author

Messages

Jim

Posts:2

05/28/2008 9:49 AM
Hi, I have been unable to find any information on how to layer images using MDT. Specifically, I want to have the following setup: Layer 1: OS, patches Layer 2: Layer 1 + Base/Common Apps and Settings, Additional patches Layer 3: Layer 2 + Deployment Specific Apps and Settings So far, this is where I'm at: Layer 1 Task Sequence - Install XP SP3, disable run sysprep step, boot LTI disc, New Computer deployment, choose the option to copy and run sysprep, enable Windows Update steps. Post install, note sysprep hasn't run b/c the step is disabled, boot to LTI, capture L1 image. Add the image to the OS's in the workbench. Choose the option to not copy sysprep files. Layer 2 Task Sequence - Install L1 image, sysprep is enabled, installs base apps and settings, enable Windows Update steps. Boot to LTI, choose the Layer 2 Task Sequence, New Computer deployment (to bare metal system), choose run sysprep. At this point, the WIM is loaded fine, but the process doesn't start automatically. There is no link the Startup folder. When I run the Litetouch.wsf manually from the MININT folder, the task sequence starts its execution, although I’m not sure about autologin as I’ve not tested it. That’s neither here nor there though, as this isn’t behaving as expected. I’d expect the Litetouch process to kick off automatically and execute the task sequence like any other deployment. How can I make this work? Thanks, Jim

Konrad

Posts:67

05/28/2008 7:55 PM
You might have to add your own Task Sequence step to copy in a shortcut to Litetouch.wsf after applying the WIM image file. Normally the sysprep.inf file is used to tell XP to run Litetouch.wsf in the [GuiRunOnce] section. As you're not using sysprep on your layer 1, this won't be initiated. Something that initially caught me out when I was modifying the standard Task Sequence to create an image to send to a manufactuer (see: http://www.deploymentforum.com/Community/Forums/tabid/124/forumid/16/postid/1035/view/topic/Default.aspx) was that when you run the image capture step, there is a file in the tools\x86 folder named wimscript.ini that tells imagex which folders not to include in the wim file and this includes LTI folders I needed to keep. If you need any of these folder to be included in your WIM file, you need to: 1. create your own version of the ini file and name it what you want (I put mine in the scripts folder) 2. copy the ZTIBackup.wsf file and modify it so that the command line that runs imagex has the "/config yourini.ini" option. I did it by changing the appropriate line in the code to: sCmd = "cmd /c """"" & sImagex & """ /capture /config """ & oEnvironment.Item("DeployRoot") & "\Scripts\_myown_imagex_config.ini"" /compress maximum " & oDrive.Path & " """ & sBackupPath & """ """ & sPrefix & Left(oDrive.Path, 1) & "Drive""" By telling imagex to use a specific ini config file, it ignores the default one. 3. changing the Task Sequence command that does the imaging to use my script instead of the original ZTIBackup.wsf. Of course, this might not be a part of the issue for you. I like your idea of having separate layers for the OS and the apps, so if you get it working would you mind posting back what you did? Cheers, Konrad.

Jim

Posts:2

05/29/2008 8:40 AM
Konrad, I can't begin to tell you how important the information you provided is as I believe it to be the key to get this working. Regarding layering the images, I believe that the MDT team has dropped the ball in this arena as, obviously, this wasn't a consideration. We believe this is the best method for keeping the core image, apps and settings consistent across the corporation while allowing flexibility at a granular level at layer 3. This also plays nicely into SMS. What MDT will do nicely is automate change management. When something changes at L1 or L2, reproducing the L1 and L2 images is automatic, something that wasn't at all simple to do with Ghost and a stack of documentation. I'll update as necessary. Jim

You are not authorized to post a reply.

Forums > Deployment Solutions > MDT 2008 > Image Layering Information

ActiveForums 3.7

Forum Policies

These forums are a user-supported community for IT professionals to exchange deployment tips, solutions, and techniques. For the benefit of all Deployment Forum members, please observe the following guidelines when posting to these forums:

We reserve the right to remove any message. Our moderators will remove all messages that are not respectful or productive. Profanity, racism, prejudice, and flaming are not tolerated.
Do not advertise products or services. Our moderators will remove all advertisements or service announcements. Product and service recommendations from active Deployment Forum members are encouraged, however.
Make sure your question isn't already answered. Before posting questions, search the forums. After ensuring that your questions are unique, post them to the most appropriate forum. This will help reduce noise in the forums.
Help make the most of each thread. Do not post unrelated messages to a thread. Also, if you've resolved a question outside of these forums, please share the solution with other members by posting it back to the thread.
Do not share confidential information. Confidential information includes product keys and addresses. Our moderators will edit any message containing confidential information, so double-check messages and their attachments before posting them.
Post messages using only the English language. For the benefit of all Deployment Forum members, please post your messages using the English language.

We hope that you enjoy using this community. Please submit your comments and feedback on the Comments and Feedback page or post them to the Comments, Feedback forum.

Privacy Statement | Terms Of Use