Re: SBS Client Application Launcher ERROR Message - THANKS for the guidance

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

From: dhibbeln (dhibbeln_at_nospam.com)
Date: 02/14/04 

Date: Sat, 14 Feb 2004 10:25:28 -0500

Mike,
IMHO - The ability to easlily leverage AD & Group Policy to deploy third
party aps with and without MSI files would sure be
big selling point. I have this feeling that I can do what I used to do in
the enterprise versions of Win2K Server
in SBS2003 - however but I also know that it could be a hard thing to
"wizardize".

The firms that I deal many times have many small apps that they need to
deploy. When you have 20 users + 50 apps on 75 devices,
you that can be a lot of clicking and billable hours...<grin>

Regards,
David R. Hibbeln

"Mike Stokke [MSFT]" <mstokke@online.microsoft.com> wrote in message
news:%23ghCJxl8DHA.2524@TK2MSFTNGP11.phx.gbl...
> Our current mechanism for deploying extended applications does not
leverage
> group policy. The wizard that I was referring to will create a link to
the
> setup executable on the desktop that the end user can click on to launch
the
> setup. There is some discussion about extending the scope of this feature
> to do the deployment as well, but that does not currently exist. For what
> you are trying to accomplish, I would recommend looking into group policy
> documentation.
>
>
> --
> Mike Stokke
> -------------------
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
>
>
> "dhibbeln" <dhibbeln@nospam.com> wrote in message
> news:u6Wxmoi8DHA.1356@tk2msftngp13.phx.gbl...
> > Mike,
> > I thought that was what the wizward was, just a macro to point to a
setup
> > file.
> > I am used to packaging apps ala novell's zenworks, windows installer,
with
> > setup files, putting stuff into GPO's
> > and all that. I suspision that if you do all that and extend the setup
> > executable you do the same thing, but simpler....
> >
> > That was the kind of info and references I was looking for.
> >
> > Again, thanks much.
> > David R> Hibbeln
> >
> > "Mike Stokke [MSFT]" <mstokke@online.microsoft.com> wrote in message
> > news:e9Kqiob8DHA.2404@TK2MSFTNGP11.phx.gbl...
> > > I am glad to hear that we made some progress on this. For preparing
> > > applications for installation, I think you are refering to the assign
> > > applications wizard. This wizard allows you to assign applications to
a
> > > computer, but it also allows you to extend the list of applications
that
> > you
> > > are installing. Basically, it will put a shortcut to the setup of the
> > > executable you are launching on the desktop of the client so that it
can
> > be
> > > kicked off from there. Once you open the wizard, there is more
> > information
> > > buttons and help that should point you in the right direction. Let me
> > know
> > > if this isn't what you mean.
> > >
> > >
> > > --
> > > Mike Stokke
> > > -------------------
> > > This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> > >
> > >
> > >
> > > "dhibbeln" <dhibbeln@nospam.com> wrote in message
> > > news:%238lPJaa8DHA.2044@TK2MSFTNGP10.phx.gbl...
> > > > Mike,
> > > >
> > > > I tried a different box and \\sbs2003\connectcomputer worked !!!
> > > > It was the "relucant box" - must be some bad hardware in that
puppy..
> > > >
> > > > in \<client\.... \windows small business server\clients\
> > > >
> > > > I found 5 files
> > > > the three *.log files (attached as sbsmig.zip)
> > > > and
> > > > sbscert.cer
> > > > sbsdefault.prf
> > > >
> > > > I got options to do things, etc, a couple of automatic reboots, etc.
> > > >
> > > > Outlook2003 and Fax Client Loaded,
> > > > Service Pak and IE 6.0 did NOT since they had allready been
> upgraded...
> > > >
> > > > Looks like I have a piece of hardware I am going to have to go and
> check
> > > > for BIOS updates, bad NIC's, cables, etc....ah well...
> > > >
> > > > Question: Can you point me to a knowledge base article that detail
> how
> > to
> > > > prepare applications for
> > > > install via \\sbs2003\clientconnect? I think I got some learning to
> > > > do....<grin>
> > > >
> > > > Thanks for all your help on this one. It had me stumped for a
> while.....
> > > >
> > > > Regards,
> > > > David R. Hibbeln
> > > >
> > > >
> > > >
> > > > "Mike Stokke [MSFT]" <mstokke@online.microsoft.com> wrote in message
> > > > news:OTrdlhZ8DHA.2712@tk2msftngp13.phx.gbl...
> > > > > The problem with the inpage error in this case is probably due to
it
> > > > running
> > > > > an application across the network and then the application needs
to
> > load
> > > > > more of itself. When it get to that point, it tries to go back
> across
> > > the
> > > > > network. However, the network seems to have dropped off and so
the
> > > > > connection is lost. At this point, the program throws an error
> > because
> > > it
> > > > > can't load what it needs. This is probably the same reason why
> > > > applnch.exe
> > > > > failed. According to the logs, it seems to lose the application
> when
> > it
> > > > > goes across the network to install various items. The outlook log
> > files
> > > > > would be located in the %temp% folder on the client. You might
try
> > > > pinging
> > > > > your server with the -l 65500. This will attempt to ping the
server
> > > with
> > > > > some data so you can see how the latency is working for data
> > transfers.
> > > > > Alternatively, is there some kind of firewall on this network or
NAT
> > at
> > > > work
> > > > > on your internal network? Second, if you have an antivirus on the
> > > client,
> > > > > you may try disabling until the applications install because this
> > could
> > > > also
> > > > > be intercepting the network transfers.
> > > > >
> > > > >
> > > > > --
> > > > > Mike Stokke
> > > > > -------------------
> > > > > This posting is provided "AS IS" with no warranties, and confers
no
> > > > rights.
> > > > >
> > > > >
> > > > > "dhibbeln" <dhibbeln@nospam.com> wrote in message
> > > > > news:e0rE9XX8DHA.3112@tk2msftngp13.phx.gbl...
> > > > > > Mike
> > > > > >
> > > > > > I ran the command line as you suggested (see below) via cut and
> > paste
> > > > to
> > > > > > start|run
> > > > > > and got back:
> > > > > >
> > > > > > *****************
> > > > > > \\SBS2003\ClientApps\Outlook2003\setup.exe
> > > > > > Error performing inpage operation
> > > > > > ***********************
> > > > > >
> > > > > > No new log files created on WKS.
> > > > > >
> > > > > > Mapped a drive to \\sbs2003\clientapps and did dir /s: got lot
of
> > > > files.
> > > > > > See edit of dir below.
> > > > > >
> > > > > > **********************
> > > > > > Directory of \\sbs2003\clientapps
> > > > > >
> > > > > > 02/11/2004 10:12 PM <DIR> .
> > > > > > 02/11/2004 10:12 PM <DIR> ..
> > > > > > 01/30/2004 04:43 PM <DIR> activesync
> > > > > > 02/11/2004 10:12 PM 28 clientapps.text
> > > > > > 02/03/2004 07:26 PM <DIR> Connection Manager
> > > > > > 01/30/2004 04:36 PM <DIR> FaxXP
> > > > > > 01/30/2004 04:44 PM <DIR> ie6
> > > > > > 01/30/2004 05:02 PM <DIR> outlook2003
> > > > > > 01/30/2004 06:05 PM <DIR> SBScert
> > > > > > 01/30/2004 04:43 PM <DIR> ShadowCopy
> > > > > > 01/30/2004 04:44 PM 482 Shared Fax Client.lnk
> > > > > > 01/30/2004 04:36 PM 452 tsclient.lnk
> > > > > > 01/30/2004 04:36 PM <DIR> w2ksp4
> > > > > > 01/30/2004 04:40 PM <DIR> wxpsp1
> > > > > > 3 File(s) 962 bytes
> > > > > >
> > > > > > 3 File(s) 586,325 bytes
> > > > > >
> > > > > > Directory of \\sbs2003\clientapps
> > > > > >
> > > > > > 01/30/2004 05:02 PM <DIR> .
> > > > > > 01/30/2004 05:02 PM <DIR> ..
> > > > > > 01/30/2004 05:02 PM <DIR> FILES
> > > > > > 01/30/2004 05:02 PM 3,429,888 OUTLS11.msi
> > > > > > 07/25/2003 02:31 PM 6,581 README.HTM
> > > > > > 07/15/2003 12:57 AM 416,824 SETUP.EXE
> > > > > > 02/20/2003 08:06 PM 19,697 SETUP.HTM
> > > > > > 4 File(s) 3,872,990 bytes
> > > > > > *********************************
> > > > > > Did ping test and got back:
> > > > > >
> > > > > > ********************************************
> > > > > > Pinging sbs2003.Hibbeln.local [192.168.20.50] with 32 bytes of
> data:
> > > > > >
> > > > > > Reply from 192.168.20.50: bytes=32 time=2ms TTL=128
> > > > > > Reply from 192.168.20.50: bytes=32 time=2ms TTL=128
> > > > > > Reply from 192.168.20.50: bytes=32 time=2ms TTL=128
> > > > > > Reply from 192.168.20.50: bytes=32 time=2ms TTL=128
> > > > > >
> > > > > > Ping statistics for 192.168.20.50:
> > > > > > Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
> > > > > > Approximate round trip times in milli-seconds:
> > > > > > Minimum = 2ms, Maximum = 2ms, Average = 2ms
> > > > > > ******************************************
> > > > > >
> > > > > > My next steps, unless you have some other idea, are
> > > > > >
> > > > > > 1) Do diags on WKS NIC and Server NIC
> > > > > >
> > > > > > 2) do a load from \\sbs2003\connectcomputer to a new box.
> > > > > > This will rull out any "box with with an attitude issue".
> > > > > >
> > > > > > 3) If it fails on the new box, I will take out a cross-over
cable
> > and
> > > > > > connect
> > > > > > direct to the server to rule out any switch/cable plant issues.
My
> > > test
> > > > > > network
> > > > > > is a frankenstein monster and one never knows....
> > > > > >
> > > > > > Will advise later this afternoon (Thursday 12 Feb)
> > > > > >
> > > > > > "Mike Stokke [MSFT]" <mstokke@online.microsoft.com> wrote in
> message
> > > > > > news:OhykG1P8DHA.2480@TK2MSFTNGP10.phx.gbl...
> > > > > > > Can you verifiy that the server shares exist for
> > > \\sbs2003\clientapps
> > > > > and
> > > > > > > that outlook2003 exists in that share? Next, can you try
> running
> > > this
> > > > > > > command line manually
> > > > > > >
> > > > > > > "\\SBS2003\ClientApps\Outlook2003\setup.exe"
> > > > > > > TRANSFORMS="\\SBS2003\clients\setup\sbsdefault.mst" /qn
> > > > > > > Reboot=ReallySuppress /wait INSTALLLOCATION="C:\Program
> > > > Files\Microsoft
> > > > > > > Outlook" /Lv
> "C:\DOCUME~1\NADINE~1.HIB\LOCALS~1\Temp\verbose.log"
> > > > > > >
> > > > > > > It appears that we failed to launch this application and
seemed
> to
> > > > > > terminate
> > > > > > > unexpectedly after that. Are you having any issues with the
> > network
> > > > > > > dropping off from this client machine? Since the application
> runs
> > > > > across
> > > > > > > the network, dropping the connection could be an issue here.
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > Mike Stokke
> > > > > > > -------------------
> > > > > > > This posting is provided "AS IS" with no warranties, and
confers
> > no
> > > > > > rights.
> > > > > > >
> > > > > > > "dhibbeln" <dhibbeln@nospam.com> wrote in message
> > > > > > > news:%23Og8WTP8DHA.2556@TK2MSFTNGP09.phx.gbl...
> > > > > > > > Mike,Thanks the directions to the log files. I will be
taking
> a
> > > look
> > > > > at
> > > > > > > them
> > > > > > > > in a few minutes to see if I can figure them out.....<grin>
> > > > > > > >
> > > > > > > > I went digging around and found computer in AD and also
user.
> > > Things
> > > > > > > looked
> > > > > > > > okay there.
> > > > > > > > I forgot to mention that I had attached to the domain prior
> to
> > > > useing
> > > > > > the
> > > > > > > > client connect wizard,
> > > > > > > > but I had removed computer and user from domain and
converted
> > back
> > > > to
> > > > > > > > workgroup before using the wizard. System load was XP with
SP1
> > and
> > > > all
> > > > > > > > patches and drivers from windows update. Only app loaded
other
> > > then
> > > > > > that
> > > > > > > is
> > > > > > > > MS Baseline Security Analyzer.
> > > > > > > >
> > > > > > > > I found some logs files at \\ <server> \clients\response\
> > > > <clientname>
> > > > > > > > app.dat
> > > > > > > > this file is attached as apps.zip.
> > > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>

Quantcast