Package Distribution on CC3, alternatives?

[CHR1S]

I have a package that refuses to appear in the package list and needs to be sent out to 30 machines by the end of the day (dont ask) Circumstances are againsed me today and I need a quick and dirty way to get it out. Can I assign it as a package via group policy without RM having a fit?

The package itself works fine and installs fine but all I get atm from RM is "Please recreate the package as per this PDF".

 

Thanks

 

Chris

[Butuz]

Does it have a PackageName.ini file in the Package Folder? If it doesnt - the Management Console will not pick the package up.

 

Butuz

[CHR1S]

Hi Butuz, yes it does, this is why im stumped

[Butuz]

hmmz

 

Firstly, have you updated the package list in the managment console by right clicking on "main Site" and clicking "Update package list"? You need to do this every time you add a package to the RMPackages folder on the server.

 

Couple of other things it could be are:

 

1) The package name may not be unique - are you sure there are no other packages with the same name?

 

2) The package name could contain invalid characters like # $ £ & etc

 

3) Try running Healthcheck.exe on the server in D:\RMNetwork\RMManage\Station Manager as this can sometimes fix weird package problems.

 

If it's neither of those then I am stumped too! Maybe you could send me the package ini file?

 

Butuz

[CHR1S]

The package name is unique and the ini is as follows -

 

[Package]

Description=Longman Planning tool

Version=1.0.0.0

OS=5.WS

WIPackage=MW_Planner_CC3.msi

 

[General]

Name=Longman Maths Works Planning Tool

[Butuz]

The package name is unique and the ini is as follows -

 

[Package]

Description=Longman Planning tool

Version=1.0.0.0

OS=5.WS

WIPackage=MW_Planner_CC3.msi

 

[General]

Name=Longman Maths Works Planning Tool

 

Ok the [Package] section looks good - the [General] section should not be needed - try taking those lines out and see if it helps?

 

One thing to bear in mind is that because you have a version number specified the whole package must be in a folder with the same version number. Eg:

 

Q:\Applications\Longman Planning tool\V1.0.0.0\EverythingGoesHere

 

Butuz

[russdev]

If cant get it to work then dirty way of doing it is using psexec and batch file to copy it across and run on all machines in network.

 

 

Also have look at TEC21757 on rm support has complete ref guide for package ini files.

 

Also make sure not got it in tools as rmmc will not pick that up.

 

Russell

[Butuz]

Oh and if the worst comes to the worst - it is possible to create a GPO, attatch an MSI to it, and apply this to RM CC3 workstations. When the workstations boot, the application will be installed before even RM Application Agent fires up!

 

Dont ask me exacly how to do this, I cant remember, but I was shown it by RM and it does work Maybe a search on technet will yeild results.

 

Butuz

[CHR1S]

Thanks guys, RM gave me a call in the end and said it was a bug somewhere in the longman creation process and to do use app wizard to recreate it.

 

The ironic thing is the package and ini is identical to the original but this time it shows up in the list. Hey ho...

 

Thanks again

 

Chris