ESET Prevents Bootup After Sysprep

Discussion in 'ESET Endpoint Products' started by bcrotty, Jan 7, 2013.

Thread Status:
Not open for further replies.
  1. bcrotty

    bcrotty Registered Member

    Joined:
    Jan 7, 2013
    Posts:
    4
    Location:
    United States
    I am installing ESET Endpoint 5.0.2126.0 in a VDI environment. When I sysprep the image, it gives a "Windows could not finish configuring the system error". After following the steps listed in a thread on Technet, it appears that the \REGISTRY\MACHINE\SOFTWARE\ESET\ESET Security\CurrentVersion\Plugins\01000400 key is the culprit, or at least the first one that it hung on.

    Any ideas?

    Thanks,
    Bobby
     
  2. jst3751

    jst3751 Registered Member

    Joined:
    Dec 11, 2009
    Posts:
    21
    Location:
    USA
    AV software should NEVER be part of an image. It should only be installed after a computer has been created from an image.
     
  3. bcrotty

    bcrotty Registered Member

    Joined:
    Jan 7, 2013
    Posts:
    4
    Location:
    United States
    Because the image gets rolled back whenever a user logs off, that would require it to install ESET every time someone logs on, which is too much of a performance drain.

    Any other thoughts?
     
  4. jst3751

    jst3751 Registered Member

    Joined:
    Dec 11, 2009
    Posts:
    21
    Location:
    USA
    There are 2 different types of imaging:

    The type used in rolling out multiple computers from a prepared base image. This involves the use of sysprep which strips the image of vital critical identity information which is then created and added when a computer is first boot from a syspreped OS. Is this case, you never install AV software or any other software which is directly dependant upon the OS UID.

    The second type of imaging I am familliar with is that used in places such as kosiaks and gaming centers and such. Once the computer is ready for use, a direct image is taken of that computer by software. Then, a user can do what ever they want to that computer and at the end of the day, the software reverts the computer back to the image.

    I am guessing what you are doing is similliar to the second type, BUT you are using a syspreped image.

    Maybe you need to go to the vendor for the imaging software and find out what they recommend.
     
  5. bcrotty

    bcrotty Registered Member

    Joined:
    Jan 7, 2013
    Posts:
    4
    Location:
    United States
    I'm using Hyper-V and Windows Server 2012 to create a pooled remote desktop collection. Server 2012 requires that the base image for the pooled desktops be sysprepped.
     
  6. rekun

    rekun Registered Member

    Joined:
    Jun 11, 2007
    Posts:
    89
    Maybe try to sysprep without the generalize option
     
  7. bcrotty

    bcrotty Registered Member

    Joined:
    Jan 7, 2013
    Posts:
    4
    Location:
    United States
    It needs to be generalized to be used as a reference image for the Remote Desktop pool.

    What I ended up doing was pushing ESET to the VMs after the pool had been created. Then I had to update the snapshot that it rolls back to every time a user logs off. That has to be done for all VMs whenever you update the reference image, but I'm working on a PowerShell script to automate a bunch of it.
     
Thread Status:
Not open for further replies.