Deployment Solution

 View Only
  • 1.  DS 7.1 Windows 7 Image Best Practice?

    Posted Oct 14, 2011 06:57 AM

    Does someone have exact steps or a document or can point me in the right direction for the proper way to do a Windows 7 Image from start to finish?

    I know we are suppose to use ghost over RDeploy now.  But if you would so kind if you have a documnet on exactly how you are doing this succesfully or would point me in the right direction that would be great... If not, when ever I figure it out I will post for the next me :-)

    If you need additonal information from me to assist let me know and I will supply what I know... Thanks!



  • 2.  RE: DS 7.1 Windows 7 Image Best Practice?

    Posted Oct 14, 2011 08:42 AM

    Hi,

    You can refer to DS user guide / manual. Topic 'Imaging Computers' in manual will help you. Also you can find many thread on this forum which might help you.

    http://www.symantec.com/connect/articles/deployment-solution-beginning-part-1

    Please go through above URL. This is old article but it might be useful to you.

    To Create Backup image - Create a client job with following task: 1. Reboot to Automation 2. Create Image - set image type as backup in it.

    To Create SysPrep Image - Create a client job with following task: 1. Prepare for Image Capture 2. Create Image - set image type as Disk in it.

    Hope this helps you.

    Thanks



  • 3.  RE: DS 7.1 Windows 7 Image Best Practice?

    Posted Oct 14, 2011 08:53 AM

    Here are the quick steps

    1. Install Windows (manually or using Scripted OS installation)

    2. Update windows

    3. Install Softwares

    4. Install Altiris Agent, plugins and Automation Folder.

    5. Disable HIbernate option

    6. Defrag hard disk

    7. Run Task, Prepare for Image Capture (this will sysprep machine and boot in automation environemen)

    8. Run Create Image task using Ghost with all default settings

    This is what i follow

     

     

     



  • 4.  RE: DS 7.1 Windows 7 Image Best Practice?

    Trusted Advisor
    Posted Oct 14, 2011 09:19 AM

    I'd add a step in between 6 and 7 above and run "create backup image"  before you try creating a disk image.  This way if something goes wrong with sysprep (if you're just getting the hang of it), you don'th ave to start over... you can just restore the backup image.



  • 5.  RE: DS 7.1 Windows 7 Image Best Practice?

    Posted Oct 14, 2011 09:34 AM

    Imaging in DS 7.1 uses two tools Ghost and Rdeploy. Both the tools supports following methods

    Create Image as:

    1. Syspreped Image or Disk Image [Supported methods are Standard and HTTP]
    2. Backup Image

    Deployment of an Image:

    1. Deploy Image task for Syspreped image [Supported methods are Standard, Muticast and HTTP]
    2. Restore Backup Image

    There are few prerequisite needs to be done to achieve end to end imaging you are looking for and these are:

    1. Install Syamntec Management Agent [If you already have Windows 7 installed ]
    2. Install by enabling Deployment Plugin and Automation Folder plugins for corresponding architecture [If you already have Windows 7 installed ]
    3. Go to Deployment and Migration
      • Add the PXE images for Win [Option if planning to use Automation Preboot method]
      • Add the required drivers for DA/Preboot [Optional but a good practice ]
      • Add the Multicasting values as per setup need [Optional required only if this method is in use]
      • Add OS licenses for corresponding OS (just make sure of correct OS selection and also put description eg. architect and OS [Optional for Windows 7]

    To proceed further make sure of Deployment and Automation folder plugin installed successfully on client.

    ___________________

    Create Image Process:

    Go to Manage-> Jobs & Tasks -> Deployment and Migration -> {Right Click} -> Create Client Job for Image Create (By adding following Tasks in it)

    1. Prepare for Image Capture using “specific” Windows 7 OS, License and Domain credentials if Domain is in use, Reboot environment as Automation/PXE [Only if PXE has configured]
    2. Create Disk Image Task by giving corresponding name to image
      • Can also use tokens like %OS%-%COMPNAME%-Disk and for Ghost/Rdeploy both
      • Image tool as Ghost
      • Image Type as Disk [For Backup image no need of Prepare for image capture task and just need to reboot the client in Preboot environment]
      • From advance tab can create image at HTTP location [HTTP configuration required]
    3. Reboot to Production

    When the imaging process is running you will see the Ghost console with imaging progress on client machine. After this imaging process is done you will see the image created under \\{Server}\Deployment\Task Handler\Image\{GUID}\ImageByName.gho

    ________________

    Deploy Image task:

    “This can be done on same/different client for Syspreped [Disk image] where as can be done on ONLY on same client for Restore Backup Image”

    Go to Manage-> Jobs & Tasks -> Deployment and Migration -> {Right Click} -> Create Client Job for Image Deploy (By adding following Tasks in it)

    1. Erase the disk [Option]
    2. Deploy Image
      1. Select the Windows 7 image to deploy
      2. Select the Product Key [Optional because “Current Key” can also be used]
      3. Select the DA [Which will insert the correct required drivers to OS]
      4. Select the option of
      • Using inventory [If client is managed by NS (SMP agent installed) and its inventory is up to date in NS database also use domain credential if it was in domain earlier]
      • Or can also use Custom Answer file with your modifications to process Sysprep
    3. Reboot to Production

    This is it and once the execution is completed you should be able to see the client into production with the deployed Windows 7 image.

    Ghost Create & Deploy image also supports partition based creation or deployment but with few limitations. Like

    1. For Ghost only one partition can be selected during deployment
    2. Windows 7 System Reserve Partition (100MB) can be stored only with System partition in a “single job” [Means in the same Preboot environment without rebooting the client ]
    3. DA can be used only with System partition and not with System Reserve Partition or Data Partition


  • 6.  RE: DS 7.1 Windows 7 Image Best Practice?

    Posted Oct 14, 2011 06:59 PM

    Deploy Anywhere is not syncing drivers to the Task/Package/Deployment and I tried these steps with no luck as the bootwiz.exe does not show up in the Windows Processes and the file are not coming over.

     

    http://www.symantec.com/business/support/index?page=content&id=HOWTO52988



  • 7.  RE: DS 7.1 Windows 7 Image Best Practice?

    Posted Oct 15, 2011 01:33 AM

    You've been given some great advice so far. One thing I would emphasize, as arjain mentioned, is that to create your master image, first build a Scripted OS Install job. This makes making brand new images so fast and easy, you don't ever even need to concern yourself with making backup images, as long as you keep your image lightweight and you don't bog it down with software installs and millions of custom Windows settings. The nice thing about the Scripted OS install task is that it automatically installs the Altiris Agent for you.

    With regards to custom Windows settings, you can set almost everything through Group Policy. If you have this ability, then do so. Don't waste your time changing settings manually when you can let GP do all the work for you! And as for software installs, Managed Software Delivery policies are your friend. You can add Quick Run tasks of all your standard load software into your "Deploy Image" job, but do your best to keep software installs out of your image. You'll end up having to update your image a lot less if you can keep these things out.

    Good luck to you!



  • 8.  RE: DS 7.1 Windows 7 Image Best Practice?

    Posted Oct 20, 2011 03:54 AM

    Does the issue of drivers not getting sync in Site Servers still persist in your setup? Because this has been observed that after adding new drivers; some time (inconsistent) it takes 6-8 hours in syncing of drivers to Site Server. Fast workaround would be once drivers are added to DS using console; short it by time and copy/paste them to Site Server to utilize it immediately.

    Also does the issue of Bootwize not getting invoked still persist in your setup? Where after adding any Preboot image and doing update from SMP agent; bootwiz.exe process in not active.



  • 9.  RE: DS 7.1 Windows 7 Image Best Practice?

    Posted Oct 20, 2011 03:58 AM

    Hope that by now you would be able to do a successful Windows 7 Image from start to finish :)