Dynamics AX 2012: Deploy Client using SCCM 2012

I have been trying to deploy the Dynamics Ax 2012 R2 client with SCCM 2012 , as described in this Technet document
It all works, but the only problem is I have been supplied with the Dynamics disk, which is 5GB, the above instructions say to copy the whole disk which is then downloaded to the local machine - which takes ages and requires a cache size change . I have tried cutting stuff out of the disk and recreating the package, but it fails.
Is there a smaller installer or which bits of the disk do I need?
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Nagendra Pratap SinghDesktop Applications SpecialistCommented:
What is the size increase in the hdd utilization  if you install it manually?

if it is taking like 5 gb then there is no point finding a smaller installer because the whole disk is getting installed.

Try running it from a share if you don't want to install it via cache.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
bentham1Author Commented:
Yes if I run it from a script it is like that and reasonably small, but the Technet guidelines are to download the installer first.
1.In the Configuration Manager console, click Software Library.

2.In the Software Library workspace, expand Application Management, and then click Packages.

3.Select the package to deploy, and then, on the Home tab, in the Deployment group, click Deploy.

4.On the General page of the Deploy Software Wizard, specify the name of the package and program to deploy, the collection to deploy the package and program to, and optional comments for the deployment.

5.On the Content page of the wizard, click Add. Select the distribution points to which to deploy the content that is associated with the package and program.

6.On the Deployment Settings page of the wizard, accept the default values.

7.On the Scheduling page of the wizard, specify when this package and program are deployed or made available to client computers.

8.On the User Experience page of the wizard, select the options that are appropriate to your implementation.

9.On the Distribution Points page of the wizard, under Deployment options, select Download content from distribution point and run locally.

I know nothing about AX (We are downgrading,from what I have seen, from Sage) It is being handled by an external team, who just handed me a disk and shrug their shoulders when I asked them this question.
What files do I need for a client install 32 and 64 bit or is there just a client only disk or similar.
bentham1Author Commented:
The only way to do it without downloading the whole install disk seems to be scripting it. I sometimes think Microsoft is losing the plot, why not just create a client installer you can use with SCCM - they are both their own products.
For info, I created as an application and a script within that. Then I created all the prereqs as applications and then you can add dependencies that are auto installed by the main deployment. I am beginning to hate AX.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Dynamics

From novice to tech pro — start learning today.