Re: Issue running advertised programs and roaming profile,
From: Michael Waterman (MichaelWaterman_at_discussions.microsoft.com)
Date: 12/24/04
- Next message: Shehzad Khoja [MSFT]: "Re: Client Push Installation Security"
- Previous message: Kim Oppalfens: "Re: Programatic way to reset advertisment counts"
- In reply to: Shehzad Khoja [MSFT]: "Re: Issue running advertised programs and roaming profile,"
- Next in thread: Shehzad Khoja [MSFT]: "Re: Issue running advertised programs and roaming profile,"
- Reply: Shehzad Khoja [MSFT]: "Re: Issue running advertised programs and roaming profile,"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 24 Dec 2004 01:57:06 -0800
Hello Shehzad,
Thank you so much for replying! My answers are inline.
"Shehzad Khoja [MSFT]" wrote:
1 - msi deploymnet with SMS is not exactly same as GPO install. For example,
behavior of switches like /jm or /jv is different in SMS deployment versus
GPO deployment.
I, know. I recently discovered that if you Advertise a program using the /ju
or the /jm switch, SMS does advertise the program and runs the command line
that you specify, but when the user clicks the icon in the start menu it will
not install because SMS didn’t put the application in a managed state.
2 - When you specify a MSI to be installed in User context, SMS tries to
elevate it. Of course it is the msi which supports elevation or not. And
depending upon the case you might be able to install the program in user
context even if it requires admin context. For example, if you install
Office XP or Office 2003 using SMS, a low rights user will be able to
install is just fine.
Yes this it totally true. BUT…. Here’s the problem. When a user has a
roaming profile the MSI information is stored in the profile. When he logs on
a new machine the managed state of the MSI packages is not yet “know” on the
local system. Therefore the user lacks the rights to install (Actually repair
the app).
3 - When you are specifying command line, there is a property called
ALLUSERS. See details
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/msi/setup/allusers.asp
This property defines which profile to use to store shortcuts. You can
install the application in user's profile or in 'All Users' profile.
This is the property we use. Our command line usually looks like this
Msiexec /I “someapp.msi” ALLUSER=”” /qb!
Does this solve your problem?
Not really. Perhaps it’s best to give it a try. You can do the following to
reproduce the problem:
1 SMS Server, 2 Windows XP clients and 1 Roaming user profile.
Create a package and set it to “only when a user is logged on” and “Run with
users’s right”. Leave the rest of the settings to default. You can use a
similar command line that I specified above.
Log on the first XP client machine. After a while SMS advertisement will
display a new program for the user. Now, let the application install. This
will successfully run, because one of the new features of SMS 2003 is that it
will elevate the MSI even when running under the user context (hence the gpo
alike feature). Now, log off so your roaming profile is stored on the server.
Move to the other XP machine and log on with the same account. Since the MSI
information is stored in your profile the shortcuts are available and you can
start using the application. Once you click on the icon a MSI repair will be
invoked. This will result in an “Access is denied” error.
Hope this will clarify the issue I’m facing.
Hope to hear from you.
Kind regards,
Michael Waterman
- Next message: Shehzad Khoja [MSFT]: "Re: Client Push Installation Security"
- Previous message: Kim Oppalfens: "Re: Programatic way to reset advertisment counts"
- In reply to: Shehzad Khoja [MSFT]: "Re: Issue running advertised programs and roaming profile,"
- Next in thread: Shehzad Khoja [MSFT]: "Re: Issue running advertised programs and roaming profile,"
- Reply: Shehzad Khoja [MSFT]: "Re: Issue running advertised programs and roaming profile,"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
