I’m trying to install Microsoft CRM 3 onto a number of machines using GPO or SMS. I have followed the implementation guide and created the Admin install on the server and published the app to the Users with a GPO. The app turns up in Add new Program in Add/Remove programs and installs ok. But I can’t script it to be silent. So what I was trying to do was run the MSI from the share with a script to make it silent. But when I run the MSI from the share, it fails as the users don’t have Admin rights on the machine. This part of the app must be installed as the user, as it plugs into Outlook but I don’t want the users to be Admin on the box.

So can anyone please tell me what I’m doing wrong? [8|]

Thanks Jo
0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


Hi Jo,
what do you mean with: 'can’t script it to be silent'?
Are you trying to hide the install dialogs from the user?
If yes, have you checked the 'Basic' checkbox on 'Installation user interface options' in the 'Deployment' tab found in the properties of the published package?
Regards, Nick
Answered 10/31/2006 by: nheim
Tenth Degree Black Belt

Please log in to comment

Maybe that was a bit misleading, as the users are unable to see Add/Remove programs in the locked down OS. I was just trying it as a test.

What I would like to do is run the installation from the share (as stated in Chapter 16 of CRM doco) this fails with the message “You must have administrator privileges to run this setup” this shouldn’t happen according to the doco.
Answered 10/31/2006 by: JMWebster
Orange Belt

Please log in to comment

Are you installing as Per User instead of Per Machine. To me it seems to be the case and there may be some customactions running in immediate sequence that require admin privileges.
Answered 11/01/2006 by: AngelD
Red Belt

Please log in to comment
Hi Jo,
i wasn't writing about the ARP dialog. I was writing about the dialog for software installation in a GPO.
Please specify, exactly how the settings for the installation in your GPO are set.
Like AngelD is asking: We also need to know, if you are installing per machine or per user.
SMS would be complete different story.
Regards, Nick
Answered 11/01/2006 by: nheim
Tenth Degree Black Belt

Please log in to comment
Hi there we are also experiencing the problem described by JMWebster.

In Chapter 16 of the CRM implementation Guide it details how to create an administrative install for the CRM 3.0 client for outlook e.g. msiexec /a lightclient.msi and specify the admin point and it also prompts for a CRM server name which gets saved to an XML file.

Creating the administrative install is meant to allow users with normal user rights to install the software without being local administrators. The software needs to be installed as the user as it needs to connect to there outlook profile.

The software can be delivered by Group policy or by the user running the MSI from the administrative point share.

However I have created the admin point and then attempted to run the MSI directly from the admin point as a normal user which fails with the same error JMWebster reported above "You must have administrator privileges to run this setup".

I've had a look in the lightclient.msi and there is a CA called ExecPass which is set to run in defferred execution in system context which seems to be the cause of the error - see section of installer log below. The question is, has anyone got an idea of how to get round this? From reading other forums it seems people have done the admin install and installed the msi as a normal user as outlined in the documentation successfully so it should work??

Thanks in advance for the help.

MSI (s) (58:64) [15:49:58:967]: Doing action: InstallExecute
Action 15:49:58: InstallExecute.
Action start 15:49:58: InstallExecute.
MSI (s) (58:64) [15:49:59:037]: Running Script: C:\WINDOWS\Installer\MSI6B.tmp
MSI (s) (58:64) [15:49:59:037]: PROPERTY CHANGE: Adding UpdateStarted property. Its value is '1'.
MSI (s) (58:64) [15:49:59:037]: Machine policy value 'DisableRollback' is 0
MSI (s) (58:64) [15:49:59:037]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (58:64) [15:49:59:037]: Executing op: Header(Signature=1397708873,Version=301,Timestamp=896892480,LangId=1033,Platform=0,ScriptType=4,ScriptMajorVersion=21,ScriptMinorVersion=4,ScriptAttributes=0)
MSI (s) (58:64) [15:49:59:037]: Executing op: ProductInfo(ProductKey={CA7BE522-8026-4E85-A432-1C9EB6BCFC00},ProductName=Microsoft CRM desktop client for Microsoft Office Outlook,PackageName=LightClient.msi,Language=1033,Version=50336948,Assignment=0,ObsoleteArg=0,,,PackageCode={8D5F3CFD-12C0-494E-9839-45215F23EF86},,,InstanceType=0,LUASetting=0,RemoteURTInstalls=0)
MSI (s) (58:64) [15:49:59:037]: SHELL32::SHGetFolderPath returned: D:\Documents and Settings\ftuser\Application Data
MSI (s) (58:64) [15:49:59:037]: Executing op: DialogInfo(Type=0,Argument=1033)
MSI (s) (58:64) [15:49:59:037]: Executing op: DialogInfo(Type=1,Argument=Microsoft CRM desktop client for Microsoft Office Outlook)
MSI (s) (58:64) [15:49:59:037]: Executing op: RollbackInfo(,RollbackAction=Rollback,RollbackDescription=Rolling back action:,RollbackTemplate=[1],CleanupAction=RollbackCleanup,CleanupDescription=Removing backup files,CleanupTemplate=File: [1])
MSI (s) (58:64) [15:49:59:037]: Executing op: SetBaseline(Baseline=0,)
MSI (s) (58:64) [15:49:59:037]: Executing op: SetBaseline(Baseline=1,)
MSI (s) (58:64) [15:49:59:037]: Executing op: ActionStart(Name=ExecPass,,)
Action 15:49:59: ExecPass.
MSI (s) (58:64) [15:49:59:037]: Executing op: CustomActionSchedule(Action=ExecPass,ActionType=3073,Source=BinaryData,Target=ExecPass,CustomActionData=en|D:\admin\LightClient.msi|0|1)
MSI (s) (58:60) [15:49:59:037]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI6D.tmp, Entrypoint: ExecPass
MSI (s) (58:2C) [15:49:59:037]: Generating random cookie.
MSI (s) (58:2C) [15:49:59:037]: Created Custom Action Server with PID 1412 (0x584).
MSI (s) (58:08) [15:49:59:057]: Running as a service.
MSI (s) (58:08) [15:49:59:057]: Hello, I'm your 32bit Impersonated custom action server.
MSI (c) (04:00) [15:49:59:908]: Note: 1: 2205 2: 3: Error
MSI (c) (04:00) [15:49:59:908]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 2867
DEBUG: Error 2867: The error dialog property is not set
The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2867. The arguments are: , ,
MSI (c) (04:00) [15:49:59:918]: Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg

You must have Administrator privileges to run this Setup.
MSI (s) (58!30) [15:50:03:093]: Note: 1: 2205 2: 3: Error
MSI (s) (58!30) [15:50:03:093]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1709
MSI (s) (58!30) [15:50:03:093]: Product: Microsoft CRM desktop client for Microsoft Office Outlook -- You must have Administrator privileges to run this Setup.

Action ended 15:50:03: InstallExecute. Return value 3.
Answered 11/20/2006 by: carlosg
Senior Yellow Belt

Please log in to comment
Hi folks,
running a installation in the Users context with 'msiexec /i xxx.msi' isn't just the same as assigning a package to a user with a GPO.
A GPO by default has 'evelated priviliges to this job.
This behaviour is exactly what Jo was describing in his initial post.
Please try this stuff from a GPO, assigned to 'Users'
To run this silent, you have to set the appropriate properties with an MST.
Hope this clarifies the situation.
Regards, Nick
Answered 11/21/2006 by: nheim
Tenth Degree Black Belt

Please log in to comment
Hi there thanks for that. I have configured this to deploy via group policy and the install then works ok as you say with elevated rights.

The problem we have is that we need to deploy this application via SMS, not group policy, in production.

We have run some tests and this package fails to install under SMS (we have set the sms job to run as the user i.e. elevated privileges and run when user is logged on). The install starts but then we receive an error message indicating that it has failed as there is already an installation of this product in progress.

As far as I can tell the only difference between this and deployment via group policy is that the initial msiexec.exe process that launches under SMS runs in the user context and not the system context. From what i can see the Microsoft CRM MSI has a bootstrap process built into it which appears to relaunch an MSI somehow from a custom action and this appears to cause a problem under SMS due to the msiexec.exe's running in different context.

If anyone has any ideas on this it would be greatly appreciated.

Answered 11/21/2006 by: carlosg
Senior Yellow Belt

Please log in to comment
Hi there just to update on this. We have heard back from microsoft and the CRM clients can only be deployed via group policy and not SMS (although you can get this to work if users have elevated rights already e.g.. local admin and execute a script which calls the CRM msi with the SMS job set to run under the users context) due to issues with elevated rights.
Answered 11/28/2006 by: carlosg
Senior Yellow Belt

Please log in to comment