This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Hello. I was wondering and can't find a definitive answer via Google (maybe the search is kinda broad)...
if VBA, for example, a Document_Open() event, is signed for an Excel and/or Word file and within the two years until cert expiration, 1000s of Excel workbooks and Word docs are made from copies of the two originals, does each of the 1000s all have to be resigned, individually, when the cert is renewed?
It looks like they will all throw up warning messages and VBA won't run, in this case, on Document_Open().
Read about Time Stamping but anything messing with Registry settings is kinda cumbersome, imho, and met with skepticism from desktop/network admins.
It seems VBA code signing poses a huge scalability problem. Basically, I was looking into Document_Open() VBA and wanting to avoid Enable Macros? prompt for users but with assurance. Thank you so much for reading and for your time.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Based on your description, you may send a file with new certificate for signed VBA to users agian.