Installing Windows apps over the network still broken with 5278

[Steve Maser]

If the Windows application installer resides on a Mac OSX box (server
or not).

If UAC is on, there is an endless stream of authentication dialog boxes
that will come up if you try to run an application installer over the
network.


This will kill distribution of Vista in my department (or we distribute
it with UAC turned off -- which will be most likely at this point for
those that *must* have it now...)


And, yes, I've reported this on each and every post-B1 build (where it
worked in B1)...

- Steve

 

[David Wilkinson]

If the Windows application installer resides on a Mac OSX box (server
or not).

If UAC is on, there is an endless stream of authentication dialog boxes
that will come up if you try to run an application installer over the
network.


This will kill distribution of Vista in my department (or we distribute
it with UAC turned off -- which will be most likely at this point for
those that *must* have it now...)


And, yes, I've reported this on each and every post-B1 build (where it
worked in B1)...

- Steve

Steve:

I install almost all my apps on Vista over a Windows network (these are
downloads stored on my main (XP) machine). I have noticed that this
generates an extra dialog that is not present if the setup file is on
the local Vista machine. Also, for installers that are signed (but not
for unsigned ones, go figure) there is then a looooong delay before the
installation proceeds.

Is this related to what you see, do you think?

David Wilkinson

 

[Steve Maser]

Steve:

I install almost all my apps on Vista over a Windows network (these are
downloads stored on my main (XP) machine). I have noticed that this
generates an extra dialog that is not present if the setup file is on
the local Vista machine. Also, for installers that are signed (but not
for unsigned ones, go figure) there is then a looooong delay before the
installation proceeds.

Is this related to what you see, do you think?

David Wilkinson

I'm not sure. I don't have a Windows Server here, but I've connected
to other servers with this Vista build and things worked fine.

The usual steps that happen (with UAC on) is that:

0) You log into the remote server with your login/password

Find the app installer (any "setup.exe", actually...) Double-click on
it.

1) You get the warning that you are about to run something

2) You get the UAC warning to "allow" it to run.

3) You get *another* authentication box requiring you to reenter your
server login/password because it "cannot access network resource".


With Beta 1 -- that would have been it -- the installer would have run
at that point after you reauthenticated to the server (using the same
login/pw.)

With all the seeds *post* Beta 1 -- step 3 happens over and over and
over.

I've reported this repeatedly since then, but MS must think this is
"expected" behavior at this point.

So it's either an intentional screwup with UAC, or it's a bug in SAMBA
that needs addressing...

- Steve