SEP12.1.2 Package Export Issue

This week we upgraded the production Symantec Endpoint Protection Manager (SEPM) server to 12.1.2 (aka 12.1 ru2).   Unlike previous upgrades on the production server, this one was smooth as silk.   Before leaving, we exported the 32 bit workstation client packages and there was no issue with that.   The next day my officemate was trying to export the 64 bit packages, the Apple package and the unmanaged package and it wouldn’t work.

The error was something useless like “Failed to export client installation package for group <Group Name>. Try again later”

Searching found a plethora of theories.
1.  You only upgraded one SEPM server, and now you’re trying to export the client install package from an earlier version SEPM server.

Nope, that’s not it.

2.  You have database corruption or an incomplete install

That seemed conceivable since every other recent install has forced me to follow disaster recovery procedures.   However, its notable that in every thread on the Symantec Forums, I never really saw anyone fix the problem by running “repair” on the SEPM install or running the update.bat file.   People would find lots of errors running a database validation script.   But then they’d find the same errors running that validation script on a server that worked fine.   People would check file permissions, but even with the “Everyone” permission set they still couldn’t get it to work.   Some found  that they were missing the client group policies in “D:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\data\outbox\agent”.   That wasn’t the case for me.

I was wondering if I’d be able to export the client install files using the web interface (http://servername:9090/) at my computer rather than using the SEPM gui on the server.  But before doing that I decided to change the directory where I was saving the exports to my desktop.   That worked perfectly!   I had noted that when I deleted the files from the client install directory that I had created that I was prompted for a UAC elevation.   It seems weird that I would get a UAC prompt on files that I own in directories where I have full control permission.   But I suspect that UAC was the cause of my issue.

I don’t need to create a client install package often so saving to the desktop and moving isn’t a big deal.