Jump to content

Recommended Posts

Posted

Hi,

 

I'm currently deploying applications like Adobe CS4 using the CLI. So for CS4 I'm using the AdobeUberInstaller.exe fired from a command prompt. Does anyone deploy this from SCCM 2012 and if so how do they go about it? Add it as a package or an application? I find this is the most confusing part of SCCM. Also I would love to deploy SolidWOrks 2013, has anyone done this via SCCM 2012 too?

 

Thanks for your help

Posted

We tried for weeks to get it to work with SCCM 2012 - we ended up moving down to MDT.

 

One thing that I'd like to just say is to remember to change the install path in the AdobeUberInstaller.xml file, if you move the installation files to another location.

Posted
Adobe's enterprise tool creates the AdobeUberInstaller.exe and AdobeUberInstaller.xml files - I wish that they would create a msi file...

 

There is one to do it. I did it with CS6, the name slips my mind. Anyways calling a .exe from SCCM is no trouble.

Posted
So with the AdobeUberInstaller.exe, just create a standard program package with the source files pointing to the CS4 setup files, then point to the exe in the command box?
Posted
Basicchannel - how did you get this to deploy through SCCM in the end then? Did you create a package with source files and then create a standard Program and simply run the Uberinstaller.exe from the directory containing the xml file?
Posted
Basicchannel - how did you get this to deploy through SCCM in the end then? Did you create a package with source files and then create a standard Program and simply run the Uberinstaller.exe from the directory containing the xml file?

 

Haven't tested yet but that's the idea. Going to run this today and let y'all know

Posted
Haven't tested yet but that's the idea. Going to run this today and let y'all know

 

Good luck! I've tried that plus running a batch file, tried creating a program with no source files and running the installer from an anonymous share. Tried all sorts of combinations - i cannot get this to work. I'd be delighted if you could get this to work and share the knowledge.

Posted
Good luck! I've tried that plus running a batch file, tried creating a program with no source files and running the installer from an anonymous share. Tried all sorts of combinations - i cannot get this to work. I'd be delighted if you could get this to work and share the knowledge.

 

It probably won't work and I'll be resorting to GPO installation but you gotta have faith. Why oh why couldn't they make it easier for enterprise deployment?

  • 2 weeks later...
Posted
Basicchannel - did you ever get this working?

 

Nope, so given up. The UberInstaller works fine when run manually inside Windows yet I can't get it to run via SCCM or even as a startup script.

  • 5 years later...
Posted

Hi,

 

I realise this an ancient thread for an ancient bit of software, but.....we can't afford to buy the latest version so we are still using CS4 here and I've been working on incorporating it into our latest SCCM CB and Windows 10 1803 deployment. So I'm posting my findings here should anyone else find themselves in the same boat as us and without any solutions available online...

 

After several days wrestling with this I'm pleased to say it is possible to deploy this through and SCCM OSD task sequenece! The steps are....

 

1. Create a customised install using the Creative Suite 4 Deployment Toolkit (currently available here http://download.macromedia.com/pub/developer/creativesuite/ADBECSDT1_Mul.exe). You input your serial number and then select all of the options you require. This will create four files - AdobeUberInstaller.exe, AdobeUberUninstaller.exe and their respective XMLs.

2. Create a share on a server somewhere and in it, put your original installation files. Ensure full control permissions for all on the share itself. Also copy the 4 files created in step 1 to the root of this share

3. Ensure the permissions on the folder itself has read permissions set for the 'everyone' group (I tried giving permission to just the SCCM Network Access account and then running the command in step 4 using this account but it failed...) - obviously you can hide the share by putting a dollar on the end of your share name

4. In your SCCM task sequence, create a 'run command line' step. The command line needs to point to the UNC location of your AdobeUberInstaller.exe file, e.g. \\server\CS4$\AdobeUberInstaller.exe. The 'start in' field needs to point to the UNC path, e.g. \\server\CS4$\

5. !!IMPORTANT!! ensure that on your command line step, tick 'continue on error' on the options tab. This is critical, because under Windows 10 the installation always completes 'with errors'. The Flash element says it has failed to install but has installed successfully. You could find the exit code for the error (for us it was 6) and then include this as a success code but easier all round to 'continue on error' and then just verify installation was successful manually post OSD

 

That's it - for some reason if you do the same steps as above but incorporated into an SCCM software application or package it fails.

 

Hopefully this helps someone - just need to figure out the updates now....

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...