(please move to appropriate place if the place i selected is not adequate)
I've been looking for an answer to this for quite some time. Hopefully you guys can help me out.
Currently, client software (such as the Agent and HIPS) can be deployed from our ePO to clients without issue. However, upon attempting to deploy VSE, VSE880.MSI gets blocked by our 3rd party white-listing software.
Further investigation reveals:
-VSE880.MSI is dynamically genterated whenever it is deployed. This results in a unique file with a distinct HASH every time it is deployed to a client
-VSE880.MSI has an invalid Digital Signature (see attached screenshot)
With an ever-changing HASH, and an invalid Digital Signature, this executable cannot be white-listed.
I can't be the first person to run into this issue. Is something configured incorrectly on the ePO causing the invalid signature? Is there anything I can do to get the signature recognised as valid? Or is there a way to have ePO deploy a static installation that can be white-listed via HASH? I've looked through product guides for both ePO and VSE and cannot find anything useful.
ePO is 5.9 on 2012R2 (also tested/confirmed on 4.6 on 2008)
VSE is 184.108.40.2066 [patch 10] (also tested/confirmed with 220.127.116.119)
Agent is 18.104.22.168 (also tested and confirmed with 22.214.171.1248)
Tested and confirmed on Windows 7 and Windows 10 clients
Don't forget, when your helpful posts earn a kudos or get accepted as a solution you can unlock perks and badges. Those aren't the only badges, either. How many can you collect? Click here to learn more.
Community Help Hub
New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.