RE: Deployment of in-house apps

Tech-Archive recommends: Fix windows errors by optimizing your registry

The problem then probably lies with the network access.
Try to make a script that first gets access to those files (mounting a
drive) before beginning the installation. It should then work without problem.
Another solution is to subdivide your install process in two: One part that
could be installed as such, the other part (if at all possible) might run as
logged on user and access the network.

Hope it helps

bruno
"lb" wrote:

Yes, the setup (w/in the sms pkg). Yes, the pkg tries to get network access
to some files during install.

"Bruno" wrote:

When you say that it does work when logged on with admin priviledges on the
local computer, do you launch the setup from within sms (Run Available
programs) or manually from the command line / interactively ?
Does your package try to get network access to some files or directory at
install ?
(the local system account has no network access)
I think the best way to troubleshoot it would be to get a log of the setup
errors.

"lb" wrote:

The setup.exe was created from VB6 Wizard. Then packaged again using Wise
Package Studio.

"Bruno" wrote:

Hi,
How was your application packaged ?
Did you try to set the 'allow users to interact with program' on so that you
see if you are prompted for something or if you get an error message ?
If your package checks for local administrator's membership, and does not
run even with local system account, then the problem lies with your package
and this would be where you have to fix the problem. Try to get a log of the
installation process so that you can get a more precise view of what happens.

brgds

bruno

"lb" wrote:

I'm trying to distribute an in-house developed software pkg via SMS2003 but
the pkg won't install unless the logged-in user is a member of the local
Admins group on the pc. I've tried every combination on Environment tab I
can think of...btw, firewall turned off (xpsp2). What am I doing wrong?
.

Relevant Pages

  • Re: Deployment of in-house apps
    ... to some files during install. ... Does your package try to get network access to some files or directory at ... >> run even with local system account, then the problem lies with your ...
    (microsoft.public.sms.swdist)
  • RE: Windows 95 - DSCLIENT
    ... I think you will only need to install the dsclient on your 95 ... > B. Microsoft network client: ... > D. Network access: Do not allow anonymous enumeration of SAM accounts ...
    (microsoft.public.windows.server.migration)
  • Re: Install via Computer Logon Script
    ... It's not network access rights, as the network access portion works fine ... I used WinInstall SE to create the MSI files. ... The final size of the install ... call the .exe with /a to expand and get directly the right MSI. ...
    (microsoft.public.windows.group_policy)
  • Re: Use of Advanced Client Network Access Account
    ... >>From what I've seen SMS will only failover and try the ... >account if it first gets an access error to the package ... network ressources outsite the SMS-Site (a share on any ... >decide if the network access account can be used. ...
    (microsoft.public.sms.swdist)
  • Re: Making a shared folder accessible to anyone from network
    ... would not like to install something that requires that they enable anonymous ... You need to look at the policy called ... Network access: Restrict anonymous access to Named Pipes and Shares ... the computer with the shared folder is not in a domain ...
    (microsoft.public.security)