chaoticsoul

Moved the test SharePoint farm moved behind the F5, though I still haven’t gotten it working yet. Mysites seem to work fine, but all the other sites, i.e. its, dar, etc don’t.  I’ve spent a large portion of my time learning the F5 this month, and have had quite a bit of assistance from Peter when he could spare the time.  Hopefully when I get back from vacation I can figure out why the core SharePoint sites on the test farm are unavailable through the F5.

I upgraded the ePolicy server to 4.0 Patch 5 to resolve a weak encryption vulnerability.  Only to discover a new more severe security vulnerability with patch 5.   I have an open ticket with McAfee on this, but have made very little progress.  They have escalated the ticket to tier 3 support, who in turn pushed it over to the security team.  I’m still waiting to hear back.

I opened a ticket with Microsoft about the recurring event 6614 that we’re getting on our production SharePoint farm.  Naturally once opening the ticket we have not seen the error.  Microsoft suggested that we remove some old application pools that are no longer in use, which we did, but ultimately the we have yet to receive the error again, so the ticket has been closed.

I applied Windows patches on all of the ECS servers, and in the process discovered several discrepancies, some of which have been resolved, and the rest will be resolved shortly. Hopefully next month we can do this as part of our regular WSUS patching schedule.

Built a few servers for the ECS guys, and during the process had to make several updates to our Windows 2008 build doc.  We are now deploying VSE 8.7 instead of VSE 8.5, as well as using a newer version of IBM director, pointed to our new IBMDir server.

I also finalized 4 new VSE installation packages for use on new server deployments.  Two for VSE 8.5 and two for VSE 8.7.  On all 4 builds the built in autoupdate task is disabled, which prevents some false alerts from behind sent out.  As we discovered recently the built in autoupdate tries to patch applications that don’t exist on the server, thereby generating Install/Upgrade failure notifications.  The other change in the 4 builds is that two of them install to our default installation path on the D drive.