Deployment and Imaging Group

 View Only

Preparing for Image Capture for Windows Client Video 

Nov 07, 2012 12:41 PM

This is a how to video on preparing for image capture for Windows client. In this video, you will learn about how to prepare a Windows client for image capture task.

For more information, please see the guide at the following location:
www.symantec.com/docs/DOC4468

Statistics
0 Favorited
0 Views
1 Files
0 Shares
1 Downloads

Tags and Keywords

Comments

Nov 22, 2012 12:47 PM

ACassar , In the video i am using a latest Beta release of Deployment Solution where DS will be using WinPE3.1 ; For this task there is no change in UI and in functionality so have used this version.

In the upcoming release of DS you should see WinPE3.1

Nov 22, 2012 05:22 AM

I notice at about 2:40 in the video that you are running DS WinPE 3.1 Automation environment.  Could you please advise in which version of SMP this was implemented?  I wasnt able to find it in any of the release notes..

Thanks

Nov 22, 2012 04:18 AM

I know what 'Prepare for image' & sysprep is doing and why it is used. Its a small point but I just dont see when I would use these options to add it to the domain after imaging. Once the image is captured then I deploy 'that' image.  I just cant see a situation where I would image my machine, and then straight away join it to the domain and deploy that same physical machine that I have just captured. Its no big deal but just wondered if anyone has used it in any capacity in the 'real' world.

Joe.

Nov 22, 2012 03:48 AM

Joe,

What you mentioned is correct When a 'Prepare for image capture' is created it will be on a machine which is a reference machine . But in this process DS actually performs a Sysprep task where all the settings for the new image will be saved and the Domain information which you provide from this task page will be used when this image deployed on new client machine as a Sysprep will be get executed and all the settings will be applied.

So the scenario is when you want to have a generic image which can be deployed on any machine [or more than one machine] and all new machines [after imaging] will have new identification; and they may be connected to a domain which you mentioned while preparing an image by using this task.

Hope you this clarifies your doubt.

 

 

 

Nov 20, 2012 04:00 AM

Hi, thanks for the replies. I suppose I was thinking in terms of this machine being a reference machine as its used to capture the image, and not a machine to be added to the domain and deployed. I know what it does, just dont see a situation where I would use it after capturing a machine. Maybe someone can tell me if they have used t and why.

Thanks

Joe.

 

Nov 20, 2012 01:57 AM

Joe, As Nelo mentioned . these credentials are to rejoin the domain ,Or you can also make it to join  some other domain .

Nov 13, 2012 05:41 PM

the credentials are for the client to rejoin the domain after an image is capture.

1. Prepare for imaging.  sysprep runs, shutdown

2. Capture image,

3. The client that the image was captured uses that information to rejoin domain.

Nov 09, 2012 09:47 AM

Quick question that I dont understand. You put in credentials to add it to the domain in the task. When does it use these credentials, how does it know the domain name to add it to. There is already a default task for adding to domain which I have in my jobs - so this seems redundant to me as far as I can see, unless i'm missing something

Joe.

Related Entries and Links

No Related Resource entered.