How to create an image using LiveState Delivery

Document Sample
How to create an image using LiveState Delivery Powered By Docstoc
					               How to create an image using LiveState Delivery




                                 Prepared By: Symantec Technical Support




How To Create an Image Using LiveState Delivery v2.doc
March 25, 2008                                                             Page 1 of 1
Table of Contents 

How to create an image using LiveState Delivery ........................................... 1

Use the latest imaging packages ....................................................................... 3

Using a custom “sysprep.inf” file...................................................................... 5

Create an image using LiveState Delivery ........................................................ 6

Application packages on the “master” image .................................................. 7

Screen shots ........................................................................................................ 8

What should happen during a successful “Prepare Image package run?” 13

After the “Prepare Image” package has run ................................................... 13

Appendix A - Possible problems and solutions ........................................... 14

Appendix B - Manually import newer imaging packages. ............................. 21




How To Create an Image Using LiveState Delivery v2.doc
March 25, 2008                                                                                     Page 2 of 2
Use the latest imaging packages
Import the latest “Symantec LiveState Delivery” imaging packages into the database. The
easiest way to get the latest imaging packages is to install the most recent “Symantec LiveState
Delivery” product release and patch.

The most recent Service Pack is available on the “LiveState Delivery Downloads” page at:
http://www.symantec.com/business/support/downloads.jsp?pid=52029

The latest hotfix files are available from Symantec Technical Support. See the “LiveState
Delivery Contact Technical Support” page at:
http://www.symantec.com/business/support/contact_techsupp.jsp?pid=52029

If a manual import of new or modified imaging packages into the LiveState database is desired,
please see Appendix B.

Note: In order to ensure proper functioning of the Image Delivery process, the most recent
packages must be used. Assigning a mixture of older and newer imaging packages will result in
a failure of the process. The latest imaging packages available in English are listed in the table
below.

Package Name                                                               Package ID
Symantec Image Delivery Image with Deploy Center                           sidpqd05.en
Symantec Image Delivery Image with Ghost                                   sidgho05.en
Symantec Image Delivery Install Agent                                      sidagt05.en
Symantec Image Delivery Post-Image Configuration                           sidpic05.en
Symantec Image Delivery Prepare Image                                      sidprp05.en
Symantec Image Delivery Windows 2000 Class                                 sidw2k05.en
Symantec Image Delivery Windows XP Class                                   sidxpc05.en

If the Microsoft (MS) Sysprep files have not already been copied to the LiveState Delivery
server, please refer to the “Symantec LiveState Delivery Implementation Guide”
(ImplementationGd.pdf) in the section entitled “Installing Microsoft Sysprep for Symantec Image
Delivery”.

If the MS Sysprep files were copied to the Delivery server prior to importing the latest imaging
packages, then the MS Sysprep files must be copied from the older MS Sysprep package into
newer one.

For example, assuming that the latest package is named “sidprp05.en”, then copy the contents
from the below directory:

C:\Symantec\LiveState\depot\sidprp04.en\1\sysprep\xpsp2

To this directory:

C:\Symantec\LiveState\depot\sidprp05.en\1\sysprep\xpsp2




How To Create an Image Using LiveState Delivery v2.doc
March 25, 2008                                                                    Page 3 of 3
Resolve the assignability of the latest "Symantec Image Delivery Image with Ghost" in
the Command Center.
   1. Open “Unassignable Packages”
   2. Right-click the new package
   3. Select Resolve Assignability.
   4. Browse to the folder that contains “ghost.exe” file
   5. Click OK.

         Note: Use the latest version of “ghost.exe”, to avoid potential issues with newer
         hardware. The same is true for the "Symantec Image Delivery Image with Deploy
         Center" package.



Populate the “Vendor Files” for the Microsoft Network Client 3.0 package in the
Command Center.
   1. Open “Unassignable Packages”
   2. Right-click the package
   3. Select Populate package with vendor files.
   4. Point to the location of the directory containing the “NETSETUP” directory files.


For more information, see “Loading the Microsoft Network Client Library” in the “Symantec
LiveState Delivery Implementation Guide” at:
ftp://ftp.symantec.com/public/english_us_canada/products/symantec_livestate_delivery/6.0/man
uals/ImplementationGd.pdf




How To Create an Image Using LiveState Delivery v2.doc
March 25, 2008                                                                   Page 4 of 4
Using a custom “sysprep.inf” file
Microsoft Sysprep provides the ability to create a custom image which contains all of the drivers
for every computer type in the organization. This is likely the motivation for using a custom
“sysprep.inf” file. Symantec LiveState Delivery was designed to integrate with a custom
“sysprep.inf.”

For more information on MS Sysprep, read the “deploy.chm” and “ref.chm” help files included
with each version of Sysprep from Microsoft.

For more information on known limitations of MS Sysprep read the Microsoft knowledge based
article “Summary of the limitations of the System Preparation tool” at:
http://support.microsoft.com/?id=830958.

When using a custom “sysprep.inf” file, it must be named “sysprep.inf” and it must reside in the
following directory before the “Prepare Image” (image capture) process is started.
C:\sysprep

In other words, the following Sysprep file and path must exist:
c:\sysprep\sysprep.inf

If the “cmdlines.txt” functionality provided by “sysprep.exe” is to be used, then the following path
and file must be used:
c:\sysprep\i386\$oem$\cmdlines.txt

Also, the “cmdlines.txt” file format must match the expected format. The first line must contain
the heading [Commands]. Subsequent lines should be quoted strings containing commands,
such as executable or batch files.
For example:
        [Commands]
        “runme.bat”

To leverage the functionality of a custom Sysprep file, the “Prepare Image” package must be
used to create the image.

Warning:
When using a custom “sysprep.inf” file with a [SysprepMassStorage] section, the “Prepare
Image” process will take much longer to complete than when using a standard “sysprep.inf” file.
Process time can be increased by as much as 2 hours because a master devise list is being
created.
Do not set the “EncryptedAdminPassword” option in the custom “sysprep.inf” file. Doing so will
prevent the required “AutoLogon” from running during the image deployment process and leave
the client computer in an “unmanaged” state.
In the custom “sysprep.inf” file, do not set the “AutoLogon” and “AutoLogonCount” values,
because the “Post-Image Configuration” package will set these values.
Finally, to deploy an image with a custom Sysprep file, set the value for the admin parameter:
“Use a custom sysprep.inf” to Yes.




How To Create an Image Using LiveState Delivery v2.doc
March 25, 2008                                                                      Page 5 of 5
Create an image using LiveState Delivery

Note: The value of the local administrator password must be set to <blank> during the imaging
process, so that particular MS Sysprep features can work. If a custom “Sysprep.inf” file is not
used then, the local administrator password can be set during image deployment with an Admin
Parameter in the “Post-Image” package.

Or, if a custom “Sysprep.inf” file is used, then a password can be specified with the
“AdminPassword=” value in the [GuiUnattended] section before the image is created as shown
below.

    1. Start with a client computer that has the packages assigned in the database that fulfill
       the dependencies of the “Prepare Image” package.
    2. To accomplish this, the "Default agent” package must not be assigned.
            • If a Ghost image is created from a computer that has the "Default agent” package
               assigned, then follow the below steps in the “Command Center”
                     i. Click the client computer.
                    ii. Select the Default package.
                   iii. Press and hold the Shift key and right-click the Default package.
                   iv. Select Delete Job Line.
                    v. Add a partition and format job in “Cooperative mode”
                            • Click OK-Coop
                   vi. Assign the following three packages in “Cooperative mode”:
                            • The OS (XP or Windows 2000)
                            • The Pre-OS (TCP)
                            • The Windows Agent (Symantec LiveState Agent for Windows
                                V7.1.5 (English)).
    3. Once the hardware and software jobs have been assigned, the “Symantec Image
       Delivery Prepare Image” package can be assigned. Only the “Prepare Image” package
       will be prompted for assignment.

Note: If “UDP Pre-OS” package was originally assigned as the “Prepare Image” package to
start the imaging process, there will now be a prompt to install the “TCP Pre-OS” package
because imaging requires TCP connectivity.
    1. Select the most recent TCP Pre-OS package
    2. Click Install if prompted.
    3. Select Replace if prompted, to assign the “Prepare Image” and “TCP Pre-OS”
        packages.

The only admin parameters that must be modified for the “Symantec Image Delivery Prepare
Image” package are the “Image System” parameter and the “Image File Name (8.3)”.
   • If a “Symantec Ghost image” is to be created then leave the “Image System” parameter
       at the default value of “Symantec Ghost”.
   • If a “Symantec Deploy Center image” is to be created then select Symantec
       DeployCenter in the “Image System” drop down list.
   • In the “Image File Name” box type in an 8.3 file name, including the “.gho” or “.pqi”
       extension. The resulting image file will be written to:



How To Create an Image Using LiveState Delivery v2.doc
March 25, 2008                                                                 Page 6 of 6
                   %SME_HOME1%\images

                   for example: C:\Symantec\LiveState\home1\images


The client computer may prompt to be restarted. The computer will start-up to the Pre-OS
agent, but the Pre-OS agent will not find any jobs to run and it will revert back to Windows. If
this occurs, wait for the “smeclnt” account to login and run the “Prepare Image” package. The
computer will restart and Ghost or DeployCenter will run to create the image.


Application packages on the “master” image
During execution of the “Prepare Image” package, application packages which are installed to
the “master” client computer are recorded. The list of application packages is written to the
image file.

During execution of the “Post-Image Configuration” package, the list of application packages is
assigned to the client in the database. That way, the application packages shown in the
“Command Center” are synchronized with those that were installed on the image.

The automated feature of package synchronization will work only if:
   • The “Prepare Image” package (sidprp05.en) is assigned to the master image computer
       for image creation.
   • The “Post-Image Configuration” package (sidpic05.en) is assigned to the client computer
       for image deployment.




How To Create an Image Using LiveState Delivery v2.doc
March 25, 2008                                                                    Page 7 of 7
Screen shots
Below is an example of how a “cooperative mode client computer” would appear in the
Command Center before assigning the “Prepare Image” package.

Note: The package versions shown in the following screenshots may not be the most current.




How To Create an Image Using LiveState Delivery v2.doc
March 25, 2008                                                               Page 8 of 8
    1. Assign the latest “Symantec Image Delivery Prepare Image” package.
    2. Click OK. It is necessary for this package to run.




    3. Click OK in the following dialog box.




How To Create an Image Using LiveState Delivery v2.doc
March 25, 2008                                                              Page 9 of 9
    4. Provide an Image File Name. It must be in 8.3 format: no spaces or long filenames.
       Click OK.




How To Create an Image Using LiveState Delivery v2.doc
March 25, 2008                                                              Page 10 of 10
    5. If the “TCP Pre-OS” package was originally assigned, then only the “Prepare Image”
       package should appear in the “Assigned phase” dialog box.




    6. If the “UDP Pre-OS” package was originally assigned to the client computer, a dialog
       box will request that a “TCP Pre-OS” package be installed. Click the latest version of the
       “TCP Pre-OS” package that is shown, then click Install.




How To Create an Image Using LiveState Delivery v2.doc
March 25, 2008                                                                 Page 11 of 11
    7. Next, a dialog box appears, requesting that the “UDP package” be replaced.




How To Create an Image Using LiveState Delivery v2.doc
March 25, 2008                                                              Page 12 of 12
What should happen during a successful “Prepare Image package run?”
    •    If the computer is running and the Windows Agent is installed on the client computer,
         then the Windows Agent should prompt “Logoff Now”.
    •    If the “Pre-OS” package is set to “Assigned”, then the client computer will restart and the
         “Pre-OS agent” will load. The “Pre-OS agent” will not find any jobs to run and will boot
         back into Windows.
    •    The Windows Agent will auto-logon and start the “Prepare Image” package.
    •    An error message may appear, referring to “NET HELPMSG 2245” in a Command
         Prompt box. This message may safely be ignored unless it repeatedly appears, for an
         unreasonable amount of time.
    •    The message “System error 1222 has occurred” may also appear. This message may
         safely be ignored unless it repeatedly appears, for an unreasonable amount of time.
    •    The computer will restart.
    •    After the computer has restarted, the “Prepare Image” package assignment will be
         automatically replaced with either the “Symantec Image Delivery Image with Ghost”
         package or the “Symantec Image Delivery Image with DeployCenter” package in the
         database.
    •    Ghost or DeployCenter will run, and the image will be created under:
         \Symantec\LiveState\home1\images
    •    Sysprep will run. If using a custom “sysprep.inf” file with a [SysprepMassStorage]
         section, then this may take 30 – 60 minutes.
    •    Mini-Setup will run on the client computer.


After the “Prepare Image” package has run
Once the “Prepare Image” package has run on a client computer and an image has been
created, the client computer will be in an “unusable” state. The mini-setup of the operating
system must be manually completed. This is an unavoidable result of running MS Sysprep.
The Windows Agent must be reinstalled because it was removed during the “Prepare Image”
process. Finally, ensure that the client can connect to the LiveState Delivery database.

If the "Unmanaged Computers" and "Deploy Agent" feature from the Command Center are used
to reinstall the Windows Agent, then the existing client must first be deleted from the database.
To accomplish this:
     1. Right-click the client
     2. Select Delete From Server.
     3. Ensure that the checkbox for Delete the computer's folder from the server's home
         directory is checked.
Click OK.

Or, if preferred, the Windows Agent may be deployed to the client computer another way, and
its entry in the database left intact.

Finally, to re-image the client from which the image was originally created:
   1. Delete the c:\needed and c:\sysprep directories if they still exist.
   2. Assign the “Prepare Image” package as described in the Symantec Knowledge Base
        article entitled “How to Deploy an Image Using LiveState Delivery”.


How To Create an Image Using LiveState Delivery v2.doc
March 25, 2008                                                                    Page 13 of 13
Appendix A - Possible problems and solutions
Problem: Error 4313
If error 4313 is produced, then the correct Sysprep vendor files have not been added to the
“Prepare Image” package depot directory.

Error.log for the client shows this:
        ERR ; 4313;03/17/2006 14:44:41;CCMAGENT.EXE;;;;
        ERR ; 4313;03/17/2006 14:44:41;CCMAGENT.EXE;;;;
        ====      Line 2, command: "..."...   ====
        C:\_integra\sw\sidprp05.en>start /w prepsystem.bat
        ERR ; 4313;03/17/2006 14:44:41;CCMAGENT.EXE;;;;
        ERR ; 4313;03/17/2006 14:44:41;CCMAGENT.EXE;;;;
        ====      Error detected, script aborted... ====
        C:\WINDOWS\SID.LOG on client computer shows this:

         Step 1: Start sidprp05.en prepsystem.bat
         folder to save _integra -
         Use SysPrepSet c:\_integra\vendor\sidprp05.en\1\SYSPREP\xpsp2
         Check if exist C:\sysprep\sysprep.exe
         "sysprep.exe NOT copied from
         depotfolder=c:\_integra\vendor\sidprp05.en\1\C:\sysprep\xpsp2"
         Step 13: Error in batch script prepsystem.bat exit 1

Solution: Manually copy the correct Operating system version of the Sysprep files into the
depot directory for the "Symantec Image Delivery Prepare Image" package, which should be
under:

\Symantec\LiveState\depot\sidprp05.en\1\sysprep

For example, if the “Prepare Image” package is run on a client with MS Windows XP SP2, then
copy the “Sysprep” files for MS XP SP2 into the directory

C:\Symantec\LiveState\depot\sidprp05.en\1\sysprep\xpsp2




How To Create an Image Using LiveState Delivery v2.doc
March 25, 2008                                                                Page 14 of 14
Problem: Error 61000
After the image is created, error 61000 appears on the client...

         NOTE;61000;03/10/06;19:54:33;MCMSG;Mcmsg message:
         ;S:\SIDPIC05.EN\1\OMNIFS\copynt.bat;dirclt.scr;Error_using_omnifs
         NOTE;61000;03/10/06;19:54:35;MCMSG;Mcmsg message:
         ;SIDPIC05.EN;system is not syspreped
         ERROR;61000;03/10/06;19:54:36;MCMSG;Mcmsg error:
         ;SIDPIC05.EN;error Error_using_omnifs
         ERROR;61000;03/10/06;19:54:37;MCMSG;Mcmsg error: ;Script Error in
         Line 88: 'mcmsg err SIDPIC05.EN;error Error_using_omnifs'

Solution: To avoid this issue, start with a client computer that has the packages assigned in
the database that fulfill the dependencies of the “Prepare Image" package.

To accomplish this, do not assign the "Default agent” package to the client computer. See the
section above entitled “To create an image using LiveState Delivery”.

In order to create an image based on a client computer which is successfully managed by the
LiveState Delivery server, the only additional package that should be assigned is the “Symantec
Image Delivery Prepare Image” package.




How To Create an Image Using LiveState Delivery v2.doc
March 25, 2008                                                                Page 15 of 15
Problem: Password policy issues.
If there are group policies in the environment for password length, complexity, uniqueness, etc.,
they may interfere with the functionality of Sysprep and lead to Sysprep errors during the image
creation or deployment processes.

Solution: Below are options to solve this issue.
   • Change the group policies to remove the conflicting objects.
   • If the problems are related to the password policies, run the following commands on the
       computer from which the image will be created, before assigning the “Prepare Image”
       package.

         The first command changes the password length to 0, the second command changes
         the number of passwords remembered to 0.

         net accounts /minpwlen:0
         net accounts /uniquepw:0

         Set the local administrator password to <blank>. As mentioned above in “To create an
         image”, this is a requirement. A different password can still be specified in the
         “sysprep.inf” file to be assigned during image deployment using the AdminPassword
         setting. However, before image creation, the actual local Administrator password must
         be blank.

    •    On the computer to be imaged, add a registry value so that the computer policies are not
         applied. This will bypass all of the computer policies, such as the legal caption (if the
         group policies define one). A legal caption can interfere with the auto-logon process
         after image deployment. The Symantec LiveState Windows Agent handles legal
         captions, but the Windows Agent is not running during the imaging process, hence a
         work-around may be necessary.

         The key is:
         HKEY_LOCAL_MACHINE\Software\Microsoft\WindowsNT\CurrentVersion\Wi
         logon\GPExtensions

         Under that key, add the following DWORD value:
         NoMachinePolicy = 1

         Remember that if this key is applied to a client before imaging, the “NoMachinePolicy”
         value should be set back to “0” on each client computer that receives this image. This
         can be done with a package once the client computer is running the Windows Agent.




How To Create an Image Using LiveState Delivery v2.doc
March 25, 2008                                                                  Page 16 of 16
Problem: Missing packages after image deployment or reset.
The original image was created using the “Prepare Image” package while additional application
packages were assigned to the client. The same packages will be assigned to other client
computers once the image is deployed using the “Post-Image configuration” package.
However, when the assigned package for a client computer is viewed in the Command Center
following image deployment, there are packages missing from the original image.

Solution: There was an issue when additional application packages were assigned to a client,
aside from the packages that were on the original “master” computer image.

For example, if an image is deployed to a client computer using the “Post-Image Configuration”
package and other application packages are assigned at the same time (such as in a profile),
then the packages originally stored on the image may no longer appear as assigned to the client
in Command Center.

Please contact Symantec Technical Support to obtain hotfix 1009252.




How To Create an Image Using LiveState Delivery v2.doc
March 25, 2008                                                               Page 17 of 17
Problem: Image Delivery fails when the "Resize Partitions" admin parameter is set to “Yes”
   • The Symantec Image Delivery Image with Ghost (sidgho05.en) package fails.
   • The client's error log displays "next try see for ghosterr.log in mode load".
   • The ghosterr.log file displays “destination drive invalid".
   • Ghost exits without imaging the client.

Solution:
   1. Open the Symantec Image Delivery Image with Ghost (sidgho05.en) package in
       Package Manager
   2. Select Scripts
   3. Click Pre-Install to view the pre-installation script.
   4. Search for the following string:
       if "%partart%"=="APORTION"

    5. Change the text in the second set of quotes from “APORTION” to “yes” (lower case), so
       that the entire line reads:
       if "%partart%"=="yes" set partart=

    6. Save the package and publish it to the Delivery server.
    7. Re-run the imaging process.




How To Create an Image Using LiveState Delivery v2.doc
March 25, 2008                                                               Page 18 of 18
Problem: DIRECT admin parameter does not work.
The DIRECT Admin Parameter of the Symantec Image Delivery with Ghost (sidgho05.en)
package does not work as expected. The Admin Parameter DIRECT has the values "IDE" and
"SCSI", but in the “Pre-Install script” of the package, the following commands perform case
sensitive string comparison:

if "%direct%"=="ide"
if "%direct%"=="scsi"

Therefore the admin parameter does not work.

Solution: Similar to the solution described in the previous problem, edit the package with
Package Manager. Change the Pre-Installation script commands so that the string comparisons
are to uppercase values, such as:

if "%direct%"=="IDE"
if "%direct%"=="SCSI"




How To Create an Image Using LiveState Delivery v2.doc
March 25, 2008                                                             Page 19 of 19
    Problem: Symantec Image Delivery Prepare Image package does not complete, logs error
    9000

    The “Symantec Image Delivery Prepare Image” package does not complete. The client
    system is stuck in a loop and pings the LiveState Delivery server repeatedly.

    On the LiveState Delivery server, the file:

    %SME_ROOT%\log\imagedelivery.log

    C:\Symantec\LiveState\config\log shows the following messages:
    2 Prep package 'sidprp05.en' associated with pre-os package
    'TCP60_04.EN'
    1 TCP Pre-OS package TCP60_04.EN, error retrieving job.
    3 PrepareClient.prepareClient end, return=9000


    Solution: This issue is caused by a dependency of the “Symantec Image Delivery Prepare
    Image” package on a specific version of the “Symantec LiveState TCP Pre-OS Agent”
    package. The most recent “Symantec Image Delivery Prepare Image” package (package ID
    sidprp05.en) requires “Symantec LiveState TCP Pre-OS Agent V6.0” (package ID
    tcp60_04.en).




How To Create an Image Using LiveState Delivery v2.doc
March 25, 2008                                                           Page 20 of 20
Appendix B - Manually import newer imaging packages.

If imaging packages are manually imported with newer versions into the LiveState database,
then the following must be completed:

1. Ensure that the “web.xml” file for the imaging servlet lists each of the new package files.
   The location is as follows:

    %SME_ROOT%\services\tomcat\webapps\imagedelivery\WEB-INF\web.xml

    The “web.xml” format can accommodate more than one version of the imaging package, but
    it requires that each set of package versions be listed in the same order.

    For example:

       <!-- package names required by servlets -->
    <context-param>
        <param-name>prepare_image_package_id</param-name>
        <param-
    value>sidprp01.en;sidprp03.en;sidprp04.en;sidprp05.en</param-value>
    </context-param>
    <context-param>
        <param-name>pre_os_package_id</param-name>
        <param-value>TCP60_02.EN;TCP60_03.EN;TCP60_04.EN;TCP60_04.EN
    </param-value>
    </context-param>
    <context-param>
        <param-name>english_w2k_package_id</param-name>
        <param-
    value>sidw2k01.en;sidw2k03.en;sidw2k04.en;sidw2k05.en</param-value>
    </context-param>
    <context-param>
        <param-name>english_xp_package_id</param-name>
        <param-
    value>sidxpc01.en;sidxpc03.en;sidxpc04.en;sidxpc05.en</param-value>
    </context-param>
    <context-param>
        <param-name>restore_client_package_id</param-name>
        <param-
    value>sidpic01.en;sidpic03.en;sidpic04.en;sidpic05.en</param-value>
    </context-param>

2. Once the “web.xml” is correct, restart the “Symantec LiveState Web service” so that the new
   “web.xml” is used.




How To Create an Image Using LiveState Delivery v2.doc
March 25, 2008                                                                  Page 21 of 21