cricketbird
Registered User.
- Local time
- Today, 09:06
- Joined
- Jun 17, 2013
- Messages
- 118
My IT department applied an update to our Office 2010 installations.
Previously, when a user opened a database for the first time, or from a new location, they would get a “friendly” yellow button warning them that this was not a trusted document, and giving them the option to trust it.
This was easy for everyone to do.
However, with the new update, the users instead get a scary-looking message box that says "A potential security concern has been identified". The main problem is that there is now no easy way for them to trust the database. Either they click “open”, and then the database opens with the code disabled, or they hit cancel and it quits.
Of course, they can manually add a particular location to their trusted locations, but this is long, complicated and I have almost no users who would actually do this. It’s hard enough to get them to use the databases without this issue.
The IT department is mostly network people and aren't sure exactly which setting in the update changed this behavior. Do any of you know what a network admin would set to use the old behavior instead?
Thank you!
CB
Previously, when a user opened a database for the first time, or from a new location, they would get a “friendly” yellow button warning them that this was not a trusted document, and giving them the option to trust it.
This was easy for everyone to do.
However, with the new update, the users instead get a scary-looking message box that says "A potential security concern has been identified". The main problem is that there is now no easy way for them to trust the database. Either they click “open”, and then the database opens with the code disabled, or they hit cancel and it quits.
Of course, they can manually add a particular location to their trusted locations, but this is long, complicated and I have almost no users who would actually do this. It’s hard enough to get them to use the databases without this issue.
The IT department is mostly network people and aren't sure exactly which setting in the update changed this behavior. Do any of you know what a network admin would set to use the old behavior instead?
Thank you!
CB