Hi all,
The source files i have for Microsoft CRM 4.0 has an MSI and SetupClient.exe. If i attempt to install the MSI directly, it throws the following message: "Please run the installer from the appropriate source. For a new install run SetupClient.exe. To repair or uninstall select Microsoft Dynamics CRM 4.0 for Microsoft Office Outlook from Add/Remove Programs."
Inclusion of the property ISSETUPDRIVEN=1 didnt help. Also i dont have any custom actions with the names : OnCheckSilentInstall or CA_BlockDirectInstallOfMSI.XXXX.......XX.
Any other suggestions to make the installation possible with the MSI ???

Thanks.
0 Comments   [ + ] Show Comments

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.

Answers

0
The property and actions you posted are more related to InstallShield created MSIs and I don't think MS would use a 3rd packaging tool for their tool. More likely Wix, Visual Studio or a combination of both.

Install with the (verbose) Logging policy enabled and check the log which custom action or launch condition triggering the prevention.
Answered 06/30/2008 by: AngelD
Red Belt

Please log in to comment
0
Table : Launchcondition.
Condition : Installed OR ALLOWRUN
Description : Please run the installer from the appropriate source. For a new install run SetupClient.exe. To repair or uninstall select Microsoft Dynamics CRM 4.0 for Microsoft Office Outlook from Add/Remove Programs.

So hw do i overcome this ????

I just tried deleting this entry bluntly and tried ; still the installation fails though the above message doesnt pop up.[:'(]
Answered 06/30/2008 by: rayz_0020
Senior Purple Belt

Please log in to comment
0
Download "Microsoft Dynamics CRM 4.0 Implementation Guide"
https://ads.jiwire.com/JOS.aspx?http/www.microsoft.com/downloads/details.aspx?familyid=1CEB5E01-DE9F-48C0-8CE2-51633EBF4714&displaylang=en

Have a look at the "Microsoft_Dynamics_CRM_IG_Installing.doc" document as it may reveal the magic you need to deploy without the SetupClient.exe.
Answered 06/30/2008 by: AngelD
Red Belt

Please log in to comment
0
GDay Guys,

Just finished playing with this beauty (comments will now be tactfully edited...). Anyway, there is a Launch condition table value Installed or AllowRun which I dropped from my transform which allowed the msi to run. The major issue we had with the package transform:
  • Using a transform bypassed all the pre-req. checks, so make sure they are present on your test machine. MS Off. SP3, .Net 3 SP1 etc.
  • The proxy.pac issue with CRM 3 follows on with CRM 4.0 [:@] http://support.microsoft.com/kb/941874/en-us
  • The C++ redistributable check that is run using the setup.exe does not detect correctly and even if installed wants the CRM 4 installation to run the redistributable from the dialog. Using a transform bypasses this issue, it's documented here http://support.microsoft.com/kb/950421
  • Multiple Outlook profiles on 1 machine is not supported/recommended by MS.
  • There is a separate msi for the Outlook client offline access buttons for the Laptop installation. Which BTW wouldn't work in our environment because of policy restrictions (full admin access to PC) and appdata folder redirection to network share to create the offline database files.

Most of the focus of this app from the vendors appears to be on the CRM server setup and performance, however I feel that their Outlook client compatability leaves a lot to be desired.

In essence the transform was quite easy, just the implementation and information broadcast of the known issues with the cliemt would have been nicer. Not everyone in the enterprise is going to run around with CD disc installs. Which is what the nominated vendor was suggesting.

I investigated the admin install point option (which is documented) but was not able to achieve a desired result which eliminated using the setup.exe.
Answered 06/30/2008 by: WayneB
Blue Belt

Please log in to comment
0
Hey Wayne,
Thanks for tat info..
I was just starting to use the MSI craeted by Admin Install Point as given in the Microsoft_Dynamics_CRM_IG_Installing.doc. (Thanks Kim [:)]).

I investigated the admin install point option (which is documented) but was not able to achieve a desired result which eliminated using the setup.exe.

Even i can see a lot of complexities comin up considering my requirements.

But my installation failed even on the removal of the LaunchCondition.
Anyway, there is a Launch condition table value Installed or AllowRun which I dropped from my transform which allowed the msi to run.

Let me give you the steps tat i followed:
1. Created a blank MST and applied over the Client.msi.
2. Deleted the entry in the Launch Condition table.
3. On installing this i didnt get the message i have been discussing in the previous posts(as i have deleted the entry in Launchcondition), but still the installation fails.
Am i missing something ????
Answered 06/30/2008 by: rayz_0020
Senior Purple Belt

Please log in to comment
0
ORIGINAL: rayz_0020
3. On installing this i didnt get the message i have been discussing in the previous posts but still the installation fails.
Rayz, by now you should know that telling us that 'the installation fails' is utterly pointless. Besides anything else, you don't explicitly say whether the installation completed but the app failed to start properly, or whether the installation itself failed. We can assume the latter but we all know what ASSUME did...

Despite the above, let's do that: we'll assume the latter. Have you taken a verbose log of the install? If so, what did it tell you? If necessary, post the relevant section of the log here (making sure you use the 'code' tag by clicking the '<%' button).
Answered 07/01/2008 by: VBScab
Red Belt

Please log in to comment
0
Ah sry abt tat Ian..
the log file i got when trying to install the MSI (no modifications) is given below:

Action ended 21:28:58: AppSearch. Return value 1.
MSI (c) (98:7C) [21:28:58:193]: Doing action: LaunchConditions
Action 21:28:58: LaunchConditions. Evaluating launch conditions
Action start 21:28:58: LaunchConditions.
MSI (c) (98:A8) [21:28:58:209]: Note: 1: 2205 2: 3: Error
MSI (c) (98:A8) [21:28:58:209]: 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) (98:A8) [21:28:58:287]: Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg
Please run the installer from the appropriate source. For a new install run SetupClient.exe. To repair or uninstall select Microsoft Dynamics CRM 4.0 for Microsoft Office Outlook from Add/Remove Programs.
MSI (c) (98:7C) [21:29:02:912]: Note: 1: 2205 2: 3: Error
MSI (c) (98:7C) [21:29:02:912]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1709
MSI (c) (98:7C) [21:29:02:943]: Product: Microsoft Dynamics CRM 4.0 for Microsoft Office Outlook -- Please run the installer from the appropriate source. For a new install run SetupClient.exe. To repair or uninstall select Microsoft Dynamics CRM 4.0 for Microsoft Office Outlook from Add/Remove Programs.
Action ended 21:29:02: LaunchConditions. Return value 3.
MSI (c) (98:7C) [21:29:02:959]: Doing action: SetupCompleteError
Action 21:29:02: SetupCompleteError.
Action start 21:29:02: SetupCompleteError.
MSI (c) (98:A8) [21:29:02:974]: Note: 1: 2205 2: 3: Error
MSI (c) (98:A8) [21:29:02:974]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 2898
Info 2898. Tahoma8, Tahoma, 0
MSI (c) (98:A8) [21:29:02:990]: Note: 1: 2205 2: 3: Error
MSI (c) (98:A8) [21:29:02:990]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 2898
Info 2898. TahomaBold10, Tahoma, 0
Action 21:29:03: SetupCompleteError. Dialog created
MSI (c) (98:A8) [21:29:03:099]: Note: 1: 2731 2: 0
Action ended 21:29:12: SetupCompleteError. Return value 2.
Action ended 21:29:12: INSTALL. Return value 3.


I created an mst & deleted the launch condition and on trying to install it, the installtion itself fails. In the sense right at the start i get the following message : "Action Microsoft.CRM.SetUp.Common.Analyzer+CollectAction Failed. Data InstallInfo.InstallType is not available."
& I dont find these strings in any table. It is then follwed by a SetUp error Dialog. The log file reads as :

Action ended 16:37:34: AppSearch. Return value 1.
MSI (c) (B8:F8) [16:37:34:866]: Doing action: LaunchConditions
Action 16:37:34: LaunchConditions. Evaluating launch conditions
Action start 16:37:34: LaunchConditions.
MSI (c) (B8:F8) [16:37:34:866]: Transforming table LaunchCondition.
Action ended 16:37:34: LaunchConditions. Return value 1.
MSI (c) (B8:F8) [16:37:34:882]: Doing action: ManagedEDW
Action 16:37:34: ManagedEDW.
Action start 16:37:34: ManagedEDW.
MSI (c) (B8:F8) [16:37:34:991]: Creating MSIHANDLE (1) of type 790542 for thread 3576
MSI (c) (B8:B4) [16:37:34:991]: Invoking remote custom action. DLL: C:\DOCUME~1\RAJESH~1.1\LOCALS~1\Temp\MSI90.tmp, Entrypoint: ClientCustomAction
MSI (c) (B8:80) [16:37:35:007]: Cloaking enabled.
MSI (c) (B8:80) [16:37:35:007]: Attempting to enable all disabled priveleges before calling Install on Server
MSI (c) (B8:80) [16:37:35:007]: Connected to service for CA interface.
MSI (c) (B8!9C) [16:37:35:679]: Creating MSIHANDLE (2) of type 790531 for thread 3740
CAPACK: CAPack::InvokeManagedCustomAction(Microsoft.Crm.Setup.Client!Microsoft.Crm.Setup.Client.ClientSetup.ClientCustomAction)
MSI (c) (B8!9C) [16:37:35:679]: Closing MSIHANDLE (2) of type 790531 for thread 3740
MSI (c) (B8!9C) [16:37:35:679]: Creating MSIHANDLE (3) of type 790531 for thread 3740
CAPACK: Extracting custom action to temporary directory: C:\DOCUME~1\RAJESH~1.1\LOCALS~1\Temp\MSI90.tmp-\
MSI (c) (B8!9C) [16:37:35:694]: Closing MSIHANDLE (3) of type 790531 for thread 3740
MSI (c) (B8!9C) [16:37:36:632]: Creating MSIHANDLE (4) of type 790531 for thread 3740
CAPACK: Binding to CLR version v2.0.50727
MSI (c) (B8!9C) [16:37:36:632]: Closing MSIHANDLE (4) of type 790531 for thread 3740
MSI (c) (B8!9C) [16:37:37:147]: Creating MSIHANDLE (5) of type 790531 for thread 3740
CustomActionProxy.InvokeCustomAction(Microsoft.Crm.Setup.Client!Microsoft.Crm.Setup.Client.ClientSetup.ClientCustomAction)
MSI (c) (B8!9C) [16:37:37:163]: Closing MSIHANDLE (5) of type 790531 for thread 3740
MSI (c) (B8!9C) [16:37:37:475]: Creating MSIHANDLE (6) of type 790531 for thread 3740
Calling custom action Microsoft.Crm.Setup.Client!Microsoft.Crm.Setup.Client.ClientSetup.ClientCustomAction
MSI (c) (B8!9C) [16:37:37:475]: Closing MSIHANDLE (6) of type 790531 for thread 3740
MSI (c) (B8!9C) [16:38:20:567]: Closing MSIHANDLE (1) of type 790542 for thread 3576
Action ended 16:38:20: ManagedEDW. Return value 3.
MSI (c) (B8:F8) [16:38:20:911]: Doing action: SetupCompleteError
Action 16:38:20: SetupCompleteError.
Action start 16:38:20: SetupCompleteError.
MSI (c) (B8:00) [16:38:20:958]: Note: 1: 2205 2: 3: Error
MSI (c) (B8:00) [16:38:20:958]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 2898
Info 2898. Tahoma8, Tahoma, 0
MSI (c) (B8:00) [16:38:20:958]: Note: 1: 2205 2: 3: Error
MSI (c) (B8:00) [16:38:20:958]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 2898
Info 2898. TahomaBold10, Tahoma, 0
Action 16:38:20: SetupCompleteError. Dialog created
MSI (c) (B8:00) [16:38:21:067]: Note: 1: 2731 2: 0
Action ended 16:38:27: SetupCompleteError. Return value 2.
Action ended 16:38:27: INSTALL. Return value 3.
MSI (c) (B8:F8) [16:38:31:473]: Destroying RemoteAPI object.
MSI (c) (B8:80) [16:38:31:473]: Custom Action Manager thread ending.
Answered 07/01/2008 by: rayz_0020
Senior Purple Belt

Please log in to comment
0
In any WI log, failed actions return '3' so we look for the string "Return value 3." (Tip: I shorten this to "ue 3.")

Action ended 16:38:20: ManagedEDW. Return value 3.

This tells us that the CA called ManagedEDW failed. My suspicion is that the setup stub dumps a bunch of files and/or registry junk which this CA is looking for.

You could try disabling that CA by conditioning its execution with an impossible-to-meet condition (I normally use "If 0=1"). However, my route would be to run the MSI through your authoring tool's Debugger and set a breakpoint on that CA *and* the one following. When the install stops at that breakpoint, I'd start up ProcMon. Then, use the Debugger to "step into" the 'ManagedEDW' CA. When it completes, stop ProcMon's monitoring. You should now have a complete display of what that CA has done. You can then add the relevant files and/or registry junk to a transform for the MSI.

EDIT:
BTW, to save you the trouble, I already Googles for 'ManagedEDW'. All I got was questions in three forums (two, actually, seeing as TechTalkz is a redirect to the first hit, just with a different stylesheet).
Answered 07/01/2008 by: VBScab
Red Belt

Please log in to comment
0
Ian, disabling the custom action ManagedEDW didnt help as one more action fails n the Installtion doesnt start, yet again [&:]... So just thought of lookin into this CA 2 kno wat exactly is happening der. I just took the log files at both success & failure states n has given it here.
The log file below is wat i get by installing the Exe:


Action 20:08:16: ManagedEDW.
Action start 20:08:16: ManagedEDW.
CAPACK: CAPack::InvokeManagedCustomAction(Microsoft.Crm.Setup.Client!Microsoft.Crm.Setup.Client.ClientSetup.ClientCustomAction)
CAPACK: Extracting custom action to temporary directory: C:\DOCUME~1\SWATHI~1.1\LOCALS~1\Temp\MSI9D.tmp-\
CAPACK: Binding to CLR version v2.0.50727
CustomActionProxy.InvokeCustomAction(Microsoft.Crm.Setup.Client!Microsoft.Crm.Setup.Client.ClientSetup.ClientCustomAction)
Calling custom action Microsoft.Crm.Setup.Client!Microsoft.Crm.Setup.Client.ClientSetup.ClientCustomAction
Action ended 20:10:32: ManagedEDW. Return value 1.



And the log file i got after disabling/removing the launch condition is given below:

Action 21:27:01: ManagedEDW.
Action start 21:27:01: ManagedEDW.
MSI (c) (20:88) [21:27:01:647]: Creating MSIHANDLE (1) of type 790542 for thread 3976
MSI (c) (20:6C) [21:27:01:663]: Invoking remote custom action. DLL: C:\DOCUME~1\SWATHI~1.1\LOCALS~1\Temp\MSI111.tmp, Entrypoint: ClientCustomAction
MSI (c) (20:D4) [21:27:01:663]: Cloaking enabled.
MSI (c) (20:D4) [21:27:01:663]: Attempting to enable all disabled priveleges before calling Install on Server
MSI (c) (20:D4) [21:27:01:663]: Connected to service for CA interface.
MSI (c) (20:44) [21:27:02:209]: Creating MSIHANDLE (2) of type 790531 for thread 3396
CAPACK: CAPack::InvokeManagedCustomAction(Microsoft.Crm.Setup.Client!Microsoft.Crm.Setup.Client.ClientSetup.ClientCustomAction)
MSI (c) (20:44) [21:27:02:209]: Closing MSIHANDLE (2) of type 790531 for thread 3396
MSI (c) (20:44) [21:27:02:209]: Creating MSIHANDLE (3) of type 790531 for thread 3396
CAPACK: Extracting custom action to temporary directory: C:\DOCUME~1\SWATHI~1.1\LOCALS~1\Temp\MSI111.tmp-\
MSI (c) (20!44) [21:27:02:224]: Closing MSIHANDLE (3) of type 790531 for thread 3396
MSI (c) (20!44) [21:27:03:239]: Creating MSIHANDLE (4) of type 790531 for thread 3396
CAPACK: Binding to CLR version v2.0.50727
MSI (c) (20!44) [21:27:03:239]: Closing MSIHANDLE (4) of type 790531 for thread 3396
MSI (c) (20!44) [21:27:04:784]: Creating MSIHANDLE (5) of type 790531 for thread 3396
CustomActionProxy.InvokeCustomAction(Microsoft.Crm.Setup.Client!Microsoft.Crm.Setup.Client.ClientSetup.ClientCustomAction)
MSI (c) (20:44) [21:27:04:830]: Closing MSIHANDLE (5) of type 790531 for thread 3396
MSI (c) (20!44) [21:27:04:971]: Creating MSIHANDLE (6) of type 790531 for thread 3396
Calling custom action Microsoft.Crm.Setup.Client!Microsoft.Crm.Setup.Client.ClientSetup.ClientCustomAction
MSI (c) (20:44) [21:27:04:987]: Closing MSIHANDLE (6) of type 790531 for thread 3396
MSI (c) (20:44) [21:27:34:340]: Closing MSIHANDLE (1) of type 790542 for thread 3976
Action ended 21:27:34: ManagedEDW. Return value 3.


The details regarding the CA ManagedEDW are:
Condition : If (NOT PATCH) AND (NOT MSIPATCHREMOVE) AND (NOT REINSTALL)
Call Dll from Installation:
CA Name: ManagedEDW
Dll File: Setup_ManagedCustomActions_cab.dll
Function - ClientCustomAction

This really doesnt make much sense to me [:(].... All i can understand is tat this dll file is stored binary table and is extracted during run time...
And i cud not debug this app as the installtion itself doesnt start.. [:@] [It throws the error right at the start and exits]

Any suggestions on how to proceed ????
Answered 07/02/2008 by: rayz_0020
Senior Purple Belt

Please log in to comment
0
rayz_0020,

How are you planning to deploy CMS, which tool/solution?
Answered 07/02/2008 by: AngelD
Red Belt

Please log in to comment
0
Kim,
I really dont have much idea about deployment, as my job is restricted to packaging only. Deployment is done by another team. And for packaging, i use Wise Packaging Studio.
Answered 07/02/2008 by: rayz_0020
Senior Purple Belt

Please log in to comment
0
What I mean is if this application is going to be installed in your corporate environment and the deployment solution supports command line based execution (such as SMS) then why not use the SetupClient.exe instead?
If so, you may want to have a look at:
How to deploy Microsoft Dynamics CRM Client through SMS
http://blogs.msdn.com/crm/archive/2008/02/22/how-to-deploy-microsoft-dynamics-crm-client-through-sms.aspx
Answered 07/03/2008 by: AngelD
Red Belt

  • Hello,

    Thanks!

    You may also check the following solution that allows to send SMS messages from MS Dynamics CRM 4.0 using Ozeki NG SMS Gateway: sms-integration.com/p_85-microsoft-dynamics-crm-sms.html

    BR
Please log in to comment
0
ORIGINAL: rayz_0020
And i cud not debug this app as the installtion itself doesnt start.
I didn't say to debug the application, but the MSI.

In WPS:

- open the MSI
- on the extreme right-hand bottom corner is a button 'Debug'. Click it.
- when the Debugger screen opens, you'll see a list of Actions down the left, a Properties window on the right and probably an 'Immediate' window ascross the bottom 1/5th of the screen.
- locate the 'ManagedEDW' Action and highlight it. Hit F9 to set a break-point at that Action.
- hit F9 at thhe *next* action also.
- hit F5. The install starts. Click through the 'Next' buttons to get the thing started.
- switch back to the Debugger so you can watch it. When the internal script reaches the rogue Action, execution will stop.
- start ProcMon or, if you prefer, use a lightweight snapshot tool (I use Ziff-Davis's In Control) to take a 'Before' snapshot.
- hit F8 to step into the ManagedEDW. Execution will stop at the next break-point.
- stop ProcMon or, if using a snapshotter, take an 'After' snapshot.

You know have a window or log fileof everything that ManagedEDW did to your workstation.
Answered 07/03/2008 by: VBScab
Red Belt

Please log in to comment
0
Ian, Thanks for taking so much effort to explain tat...
I can see that the text "..debug the app...." is misleading..
Actually i did follow exactly as u have explained...
Open MSI - Select Debug - set ChkPoint -.......
But when i click F5 it throws the error and then the installtion ends....
The only two dialogs i can see are 1. the error message ; 2. <etup did not complete....Click finish....>.
This is wat i meant by "cud not debug"....... For nw i have stopped proceeding on tat track and i have actually created a MSi using admin install point and have started working on it.... This MSI actually invokes the exe to install...... BTW thanks for all the replies...
Cheers.
Answered 07/03/2008 by: rayz_0020
Senior Purple Belt

Please log in to comment
0
ORIGINAL: rayz_0020

Hi all,
The source files i have for Microsoft CRM 4.0 has an MSI and SetupClient.exe. If i attempt to install the MSI directly, it throws the following message: "Please run the installer from the appropriate source. For a new install run SetupClient.exe. To repair or uninstall select Microsoft Dynamics CRM 4.0 for Microsoft Office Outlook from Add/Remove Programs."



Hello, did you ever find a solution to package CRM 4.0 properly? Or use the MSI?

EDIT: okay, thanks to PM's with WayneB and rays_0020 I now know that post #5 is working. "Yes, a .mst file. I would use a program called InstEdit (or Orca) to create the transform. However, if you are new to packaging; I certainly would not recommend attempting this application as it is quite involved. I'm not even sure it would run on a Citrix box. Maybe one of the other members can answer that one. "

So I'll try Orca and/or InstEdit and post my findings...
Answered 06/04/2009 by: toco
Senior Yellow Belt

Please log in to comment
0
Hey Toco,

See my post #5 which worked; kind of, but with lots of issues which were not compatable in the enterprise environment. I have moved jobs since then, but last I heard, they hadn't implemented it.

Regards
Wayne
Answered 06/04/2009 by: WayneB
Blue Belt

Please log in to comment
0
Ok. So I downloaded InstEd. Edited the client.msi file and dropped the table "LAUNCHCONDITION". Then applied transform, resulting in a new msi. When I launch this new msi, it throws an error:
"Action Microsoft.Crm.Setup.Common.Analyzer+CollectAction failed. Data InstallInfo.InstallType is not available."

This exactly the same thing as user raz_0020 exerienced.

@ WayneB: how did you overcome this? Since you managed to create a working msi + mst.
Answered 06/04/2009 by: toco
Senior Yellow Belt

Please log in to comment
0
Is there any free tools that will step through an msi install? That would sure be handy to have.


However, my route would be to run the MSI through your authoring tool's Debugger and set a breakpoint on that CA *and* the one following. When the install stops at that breakpoint, I'd start up ProcMon. Then, use the Debugger to "step into" the 'ManagedEDW' CA. When it completes, stop ProcMon's monitoring. You should now have a complete display of what that CA has done. You can then add the relevant files and/or registry junk to a transform for the MSI.
Answered 06/04/2009 by: joedown
Second Degree Brown Belt

Please log in to comment
0
Search this forum for the word 'DebugView'.
Answered 06/04/2009 by: VBScab
Red Belt

Please log in to comment
0
Is there anyone who actually successfully packaged CRM 4.0 for Outlook client?

And then were able to autiomatically deploy the MSI to his clients and/or terminal servers ?
Answered 06/05/2009 by: toco
Senior Yellow Belt

Please log in to comment
0
Hi,
Joe Down's post has got all the answer that you need...

I managed to make the MSi installable by doing this:
1. Dropped the LaunchCondition
2. Set an impossible-to-meet condition for the Custom Action, "ManagedEDW" in both InstallExecuteSequnce and InstallUISequence. (ie., change the condition for this CA to something like, 1=2)

But i would not recommend you to use the same as it is quiet amateurish to comment out a Vendor provided CA. Do exactly what Joe Down has suggested:

Is there any free tools that will step through an msi install? That would sure be handy to have.

quote:


However, my route would be to run the MSI through your authoring tool's Debugger and set a breakpoint on that CA *and* the one following. When the install stops at that breakpoint, I'd start up ProcMon. Then, use the Debugger to "step into" the 'ManagedEDW' CA. When it completes, stop ProcMon's monitoring. You should now have a complete display of what that CA has done. You can then add the relevant files and/or registry junk to a transform for the MSI.


My package didn't give any issues though and it was successfully deployed thru AD and SCCM.
Terminal server - i have not tested it any time.

Hope this helps....

Cheers,
Rajesh.
Answered 06/09/2009 by: rayz_0020
Senior Purple Belt

Please log in to comment
0
Great! This seems to work!

1. Dropped the LaunchCondition
2. Set an impossible-to-meet condition for the Custom Action, "ManagedEDW" in both InstallExecuteSequnce and InstallUISequence. (ie., change the condition for this CA to something like, 1=2)


I managed to edit the client.msi with program "InstEd". Then created an mst with "InstallTailor". Then deployed the msi with Citrix (4.5) Installation Manager. When I launch Outlook, the CRM 4.0 client plugin is present.

Thank you all!
Answered 06/11/2009 by: toco
Senior Yellow Belt

Please log in to comment
0
I managed to edit the client.msi with program "InstEd". Then created an mst with "InstallTailor" You should never edit vendor-supplied MSIs. Always use a transform: that's what they're for! Move the edits into your transform and restore the back-up that you took of the original MSI.
Answered 06/11/2009 by: VBScab
Red Belt

Please log in to comment
0
Indeed. It worked fine until now. The customer wishes to deploy Roll Up packs 7 and 8. Roll Up pack 7 will not install. It only provides the "repair" or "uninstall" options. so my tweaking of the original MSI only lasted so far...

that's why I tried this "Run SetupClient.exe at the command prompt by using the /A and /targetdir parameters. The /A parameter specifies an administrative installation, and /targetdir specifies the target directory. After Setup is complete, you can share the location." from Microsoft: http://technet.microsoft.com/en-us/library/dd979249.aspx

But when I try that, I get following errors: "Microsoft Dynamics CRM Client for Outlook imgae creation failed." and "Client refers to a location that is unavailable..."! [:(]

without the "/A" option, the installer seems to proceed. anyone any ideas of how to receive the nice and clean MSI with this administrative install?
Answered 04/07/2010 by: toco
Senior Yellow Belt

Please log in to comment
0
1. Create Transform Using Orca
2. Drop the LaunchCondition
3. Set an impossible-to-meet condition for the Custom Action, "ManagedEDW" in both InstallExecuteSequnce and InstallUISequence. (ie., change the condition for this CA to something like, 1=2)
4. Property ISSETUPDRIVEN=1
5. MSIEXEC /I "Client.msi" TRANSFORMS="Client.mst" ALLUSERS=1
6. Extract the Patches from the Provided Exe's for 7,8,9 & 10 Rollups ( Use WinZip to extract)
7. msiexec /p "Rollups\7\client_i386_kb971782_1033.msp"
8. Install the 8,9 & 10 Rollups as per the above command

*9.
Note : ( By default the Path to exe points to the wrong location to activate the addin "C:\\Client\\ConfigWizard\\CrmForOutlookInstaller.exe" which failes for the Lockdown User to get the CRM Addin for Outlook)

After Installing the msi and Patches change the Registry Path as below

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run]
"MSCRM"="\"C:\\Program Files\\MSCRM\\Client\\ConfigWizard\\CrmForOutlookInstaller.exe\" /activateaddin"

On Uninstalling make sure to do the following

1. Stop and delete "CrmSqlStartupSvc" Service.
2. delete the Folder C:\Program Files\MSCRM


*** Thanks to all the AppDeploy Members who posted their valuable information to get me thru the package
Answered 05/20/2010 by: Newsy
Senior Yellow Belt

Please log in to comment
0
After Installing the msi and Patches change the Registry Path as below

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run]
"MSCRM"="\"C:\\Program Files\\MSCRM\\Client\\ConfigWizard\\CrmForOutlookInstaller.exe\" /activateaddin"
It would be simpler to incorporate the above into a transform, applied to the newly-patched MSI at deployment time.
Answered 05/21/2010 by: VBScab
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity