Thread-topic: Vista vs. Mac OSX Server -- problems with UAC/installing Windows apps
On 9/28/06 1:54 PM, "Steve Maser" <email@hidden> wrote:
> Hey all,
> I've already submitted a bug report on this to Apple (4704930)
> *and* Microsoft, but was hoping for some insight as to what might be
> an option for when Vista is released...
> On my OSX server, I put application installers (Mac and Windows)
> up so my users can follow e-mailed instructions to install them if
> they need them.
> With Vista (all seeds post b1), the following will occur if User
> Access Control (UAC) is on the Vista client (which it is by default)
> and the Vista user attempts to install a Windows app located on my
> OSX Server:
> 1) Vista User connects to my file server by typing in "\\<hostname>"
> and logging into the server.
Are the vista computer and the server both members of AD, or does the Vista
user need to authenticate as a local user on the server?
> 2) User navigates to Windows app installer directory
What happens if the Windows user connects directly to the app installer
directory "\\<hostname>\<app installer share>" ?
> 3) User double-clicks on Setup.exe (doesn't really matter what
> Windows app it is...)
> 4) User gets an "Open File -- Security Warning" box (click "run")
> (XP users see this now -- nothing new here...)
> 5) User Account Control box comes up -- click "continue"
> 6) "Cannot Access network resource box" comes up with a need to
> reenter the server login/password again.
> Now, with B1 of Vista -- after reauthenticating to the server -- the
> Windows app installer would run.
> What is happening with all the builds of Vista since Beta 1 (which
> means it's in RC1 and the post-RC1 build, so it's probably "expected
> behavior" now) is that Step 6 above comes up again. And again. And
> The Windows application installer will never fire up because that
> dialog box will never stop coming up.
> The only workaround I've been able to come up with is to turn UAC
> *off*. For which Vista nags you about it.
> Or put the Windows app installers on an honest-to-gosh Windows
> machine. Which I don't want to do.
> I'm taking this to mean it may be a SAMBA issue (as the problem seems
> not to be limited to OSX *Server* as it happens if I move the
> installer to OSX Client and turn Windows Sharing on it as well...)
> But OSX Server seems to have a bit more GUI options as to what might
> be toggled for Windows authentication/Samba (though toggling all the
> options didn't make any difference.)
> It's certainly 100% reproducable, but because MS hasn't changed the
> behavior back to beta1 behavior, I'm fully expecting this to be in
> Vista GM.
Speculating on final features based on betas has never been a good idea,
regardless of the stable existence or lack of a feature through many
> Vista is (for better or worse) going to hit here soon after release
> so it's becoming more of a pressing issue than I'd hoped.
> Anybody run across this yet and have any thoughts on this matter?
> Any Apple Engineers care to chime in on this one?
Samba will be umm... (searching for an NDA-friendly term) ... improved in
Leopard. It may or may not remedy the issue you are seeing. My crystal ball
is unable to determine which OS will be released first, but I sure as heck
will not be rolling either platform out as GM version 1.0s until other souls
braver than I have put them through their paces in production environments.
> - Steve
Peter M. Bukowinski
Sr. Support Analyst - IT
Janelia Farm Research Campus
Howard Hughes Medical Institute
Do not post admin requests to the list. They will be ignored.
Macos-x-server mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden