RM CC3 Custom Packages..

[cbeeching]

Alright, so I had an MSI I wanted to send out as a package across our CC3 network, and I know I can just use the RM application wizard, add an existing windows installer etc, and it will then become available as a packge within the RMMC.

 

 

However, i'm intrigued to know what the application wizard actually does? It seems to me, when you look in the 'packages' drive, you've got a folder for each 'package' as such, which just includes a little ini file, an msi, and sometimes extras like shortcuts etc. So I figured I could just go into this drive, add a folder for a custom package, add in an msi, configure the .ini file so it targets to the correct msi, add a description and it would appear within the management console, but it doesn't seem so.

 

Also if I go in and edit the 'description' field within an .ini file of an existing 'package', no change is reflected within the RMMC. So where does the link lie? Is it a standard RM thing, or subject to network?

 

If anyone has any clues that'd be great,

 

Thanks!

[sparkeh]

If you have a .msi then yes you can just create your own folder structure in the packages folder.

 

Ok a couple of silly things first, have you remembered to update the package list? Also did you put a version folder at the root of your package (ie MyApp -> v1.0.0.0 -> all the app files)

[Jamo]

You need to create a new folder inthe packages drive, plonk an MSI in the folder called the same as the folder and then you need to refresh the packages by right clicking on main site and click update package list.

 

This will refresh the AD files and I believe create the INI file for you. You can create shortcuts usign the shortcut bank and the resources section on the RMMC then.

[gibbo_ap]

i have done this several times - altho you need to mess with the ini file as i ended up with 2 packages in the rmmc called v1.0.0.0 neither with a description lol fixed it after fiddling

[webman]

Not all MSI packages are built the same though, so they aren't guaranteed to "just work" using this method, or by importing using the Application Wizard.

[Jamo]

Well the MSI will work, but the permissions may be wrong. You may have to then customize the writeaccess.ini file which the RM Appagent uses to adjust permissions on folders as it installs the package.

[cbeeching]

Wow, you guys are quick!

 

Cheers for all the replies

 

I hadn't used the 'update packages list' command before.. it seems if you use the wizard it updates automatically, as i've never had a problem with not seeing packages.

 

I ended up have 2 versions of this program in the list because I made my custom folder first, then made a package using the application wizard afterwards (before I updated the list). So 2 appeared. To try and differentiate between the two different versions (the one I made, and the one the wizard made), I altered the 'description' of one of them, but this change is still not reflected in the RMMC. So it must be stored somewhere else? Not that this really matters, but I like to know whats going on underneath the table if you know what I mean..