Trend OfficeScan Causes Unexpected Task Sequence Failures

I have been working with a customer on a migration and consolidation project, moving from ConfigMgr 2007 and removing secondary sites for field offices and replacing them with distribution points, during this process I identified a number of task sequence issues and issues with their existing environment due to Trend OfficeScan.

The main issue we had was with the installation of applications. Always every run of the task sequence, we would encounter hash verification errors. However, after verifying the hash of the content on the distribution points it was clear to me this wasn’t the issue.

We had previously had issues deploying distribution points to remote site locations, eventually we traced this back to interference with Cisco WAAS devices, the network team helped in resolving this issue but we still had an issue with the task sequence.

The main error I noticed was in the Content Access Service (CAS) log file on the client after it booted back up from the failure screen. Here we consistently noticed the following error.


To begin with I noticed the 0x80091007 error which is related to a hash error, we continued some investigation work with the network team to discover if any other devices may be causing this behaviour. The error in fact was right under our nose, I had noticed the symbols in the error but not really paid much attention to it to begin with, then the error code next to these symbols gave the answer away. Here we also have a 0x80070020 which is the error for “The file is currently in use by another process”. I knew that only a few applications before we were installing the local anti-virus solution Trend OfficeScan.

After some further testing we moved this further down in the task sequence and it completed without any errors. Another discovery was that before Trend even contacts the server for it’s policies and exceptions a full scan is taken during the installation to check for infection, as this is a fresh build it seems kind of pointless however after another installer was written disabling the prescan feature we had the same issues.


So in summary, Trend is not happy with something at all, it seems to cause all sorts of problems with our task sequence, while exclusions are required and highly recommended to prevent this in live software distribution having them at this stage because of the nature of Trend will make no difference.


Tags: , , , , , , , , , , ,

About Martyn

Martyn is one of the Senior Cloud Architects and DevOps Team Leader at one of the worlds leading Cloud Transformation Specialists Inframon. Martyn is responsible for the architecture of some of the largest Azure deployments in EMEA and is a advisor to a many businesses on their strategies. Martyn is a regular speaker at Microsoft events and community events on Azure and DevOps, giving his insight to a growing number of audiences.

2 responses to “Trend OfficeScan Causes Unexpected Task Sequence Failures”

  1. ESET Coupon says :

    Hmm is anyone else having problems with the pictures
    on this blog loading? I’m trying to figure out if
    its a problem on my end or if it’s tthe blog.
    Any responses woould bbe greatly appreciated.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: