Thursday, January 9, 2014

Dealing with 1618 Errors in a Task Sequence

A co-worker came up with this brilliant email about a recent issue when trying to install McAfee 4.6 in an OSD task sequence:

<quote>
The error 1618 usually means that there is another installation “already in progress”.  Now this doesn’t always mean that there really is one in progress, but there may still be a “PendingFileRenameOperations”.  In my task sequence, I have a reboot occur after the installation of “McAfee EPO Agent 4.6” as well as a reboot after the install of “McAfee Virus Scan Enterprise 8.8.02004”.

A quick way to verify if indeed a reboot is needed in between would be to check for the existence of the following registry key after the “McAfee EPO Agent 4.6” is installed:

[HKLM\SYSTEM\CurrentControlSet\Control\SessionManager]
      PendingFileRenameOperations  (If this exists, then it is a good bet that you need to reboot the computer before trying to install anything else)

Also, you if desired you can copy the code below and paste it into a VBS.  This will help to determine if a reboot is required.  I have used it in the past for patches, but should work as well for packages.

=================  Copy Below  =================
Set objSysInfo = CreateObject("Microsoft.Update.SystemInfo")
Wscript.Echo "Reboot required: " & objSysInfo.RebootRequired

=================  Copy Above  =================
</quote>