Multiple DBs - keeping various FE's updated

I sup****t 15+ individual databases for 6 different company sections. Each
FE 
is link to multiple BEs (1 BE is shared by almost all). I've incor****ated 
ideas gained here in these forums and most everything works great. 

My issue is I need a way to force download of a newer FE (if needed) to an

employee. My current setup is a Update Front-Ends DB that everyone
'should' 
have a shortcut to. They can open this and then download whatever DB they 
want. When I make changes to a particular DB FE, I let the section know
and 
then it's on them to get the newer version. I'd like a way to force a new 
download if their current DB FE is outdated.

I've looked into Tony Toews' AutoFE and feel, with all these different
FEs, 
it probably doesn't quite fit the bill. Our IT Dept. frowns heavily on
what 
software is installed on their systems.

I've looked at Danny Lesandrini's 'Automatically Deploy a New Access
Client' 
at http://www.databasejournal.com/features/msaccess/article.php/3286111.
This 
setup looks like it would call for a seperate 'Update.mdb' for each FE.
This 
just feels clumsy for what I need to do. Also, this way requires code in
the 
OnTimer even for a hidden form. I already use a hidden form with my 'Check

for LogOut' code in the OnTimer event. Would combining these cause any 
problems?

Would there be a way to use a single 'Update.mdb' to drive the downloading

of the FE? The questions that spring to mind are:

1 - Can the current outdated FE pass it's file name to the Update.mdb for
it 
to know which FE to grab?
2 - Would a single Update.mdb containing macros for each FE to download 
work? The current outdated DB could then open the Update.mdb with an /x 
<macro> argument.

Thanks for any assistance you guys can give.