|
|
Our Hot Pick: Rising Antivirus 2006 - Certified by TUV & Checkmark! Get 10% discount by entering this coupon code: ONDISCOUNT10
I'm using the wise installation system/Sagekey script to config an
Access 2003 installation that will run on terminal services. An aspect
that I don't understand, and which surprisingly does not seem to have
come up before to Sagekey, is the need to install distinct copies of the
app front end. The normal 'client server' Sagekey script installs the
app in such a way (via admin install of be and fe) that TS users are
running copies of the same front end (say installed at c:\myapp
\myapp.mde)
I have some pretty sophisticated homebrew routines that handle distinct
front ends and updates to them on ts boxes; but they are not oriented
towards runtime or wise installer. To set up a new user with my prev TS
installs, I simply copy the interface stuff to a distinct folder for
that user; create shortcuts on their desktop that ref the distinct mde
they're to run. But I'd far prefer it with the runtime setup that I'm
getting in to now if an admin didn't have to log in and hand wire that
sort of stuff before the end user was able to run the app. I'd like
either the admin or the regular user to be able to run the client side
of the installer routine and get it all wired up properly.
Is there anything obvious that would help provide a 'simple' solution to
this issue? I'll be able to cook something up but it'd be great to get
some kind of assist from the systems I'm working with, either TS
profiles or Access profiles, etc. I have some ideas, and Sagekey is
kicking it around, but input from anyone else would be appreciated.
BTW Sagekey has been great, support has been brilliant and fast, script
seems to work well, caveat this issue.
|
|
kiln wrote:
[Quoted Text] > I'm using the wise installation system/Sagekey script to config an
> Access 2003 installation that will run on terminal services. An aspect
> that I don't understand, and which surprisingly does not seem to have
> come up before to Sagekey, is the need to install distinct copies of
> the app front end. The normal 'client server' Sagekey script installs
> the app in such a way (via admin install of be and fe) that TS users
> are running copies of the same front end (say installed at c:\myapp
> \myapp.mde)
>
> I have some pretty sophisticated homebrew routines that handle
> distinct front ends and updates to them on ts boxes; but they are not
> oriented towards runtime or wise installer. To set up a new user with
> my prev TS installs, I simply copy the interface stuff to a distinct
> folder for that user; create shortcuts on their desktop that ref the
> distinct mde they're to run. But I'd far prefer it with the runtime
> setup that I'm getting in to now if an admin didn't have to log in
> and hand wire that sort of stuff before the end user was able to run
> the app. I'd like either the admin or the regular user to be able to
> run the client side of the installer routine and get it all wired up
> properly.
>
> Is there anything obvious that would help provide a 'simple' solution
> to this issue? I'll be able to cook something up but it'd be great to
> get some kind of assist from the systems I'm working with, either TS
> profiles or Access profiles, etc. I have some ideas, and Sagekey is
> kicking it around, but input from anyone else would be appreciated.
>
> BTW Sagekey has been great, support has been brilliant and fast,
> script seems to work well, caveat this issue.
It seems to me you only need Wise/Sagekey to get the runtime installed one
time on the server. To set up each user you can just put a copy of the MDE
in their profile folder and create a published application that points to
it.
--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com
|
|
In article <Sw7rg.60402$Lm5.31065[ at ]newssvr12.news.prodigy.com>,
rickbrandt2[ at ]hotmail.com says...
[Quoted Text] > kiln wrote:
> > I'm using the wise installation system/Sagekey script to config an
> > Access 2003 installation that will run on terminal services. An aspect
> > that I don't understand, and which surprisingly does not seem to have
> > come up before to Sagekey, is the need to install distinct copies of
> > the app front end. The normal 'client server' Sagekey script installs
> > the app in such a way (via admin install of be and fe) that TS users
> > are running copies of the same front end (say installed at c:\myapp
> > \myapp.mde)
> >
> > I have some pretty sophisticated homebrew routines that handle
> > distinct front ends and updates to them on ts boxes; but they are not
> > oriented towards runtime or wise installer. To set up a new user with
> > my prev TS installs, I simply copy the interface stuff to a distinct
> > folder for that user; create shortcuts on their desktop that ref the
> > distinct mde they're to run. But I'd far prefer it with the runtime
> > setup that I'm getting in to now if an admin didn't have to log in
> > and hand wire that sort of stuff before the end user was able to run
> > the app. I'd like either the admin or the regular user to be able to
> > run the client side of the installer routine and get it all wired up
> > properly.
> >
> > Is there anything obvious that would help provide a 'simple' solution
> > to this issue? I'll be able to cook something up but it'd be great to
> > get some kind of assist from the systems I'm working with, either TS
> > profiles or Access profiles, etc. I have some ideas, and Sagekey is
> > kicking it around, but input from anyone else would be appreciated.
> >
> > BTW Sagekey has been great, support has been brilliant and fast,
> > script seems to work well, caveat this issue.
>
> It seems to me you only need Wise/Sagekey to get the runtime installed one
> time on the server. To set up each user you can just put a copy of the MDE
> in their profile folder and create a published application that points to
> it.
>
>
Hi Rick
What do you mean by creating a published application? Is there such a
thing in TS? Citrix has this sort of stuff...it'd be great if TS has
something like it too.
Published on time...the app must be installed via control panel
add/remove apps, by an admin. Normally that sets it up for all users. Is
there some other way to install that does not publish to all?
|
|
kiln wrote:
[Quoted Text] > Hi Rick
>
> What do you mean by creating a published application? Is there such a
> thing in TS? Citrix has this sort of stuff...it'd be great if TS has
> something like it too.
Sorry, yes I was thinking of Citrix. However; I think the part about the
executable only needing to be installed once should still apply.
> Published on time...the app must be installed via control panel
> add/remove apps, by an admin. Normally that sets it up for all users.
> Is there some other way to install that does not publish to all?
If you are using SageKey scripts it's possible that they are configured for
"This User Only". I would ask them about it. As long as it's set up for
"All Users" then each user should just need a shortcut to a copy of the MDE
and Windows file associations should automatically direct that the runtime
be used as the executable.
--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com
|
|
|