Uable to assign new Product to Client for deploy

[rmaxwell]

Hi All,

New Guy here, test driving OPSI using VMPlayer and version 4.0.4 of the ServerVM. Worked my way through the server setup, did a couple of client agent installs, deployed the software and hardware audit packages to my clients. So far so good.

Built a new Product Package, tested it out, got it loaded on the server. Now I want to deploy it to one of my test clients. When I first logon the OPSI Config Editor and before I select a Client I verify my Product Package is ready. Yep, there is on the Product Configuration. Yay, I'm feeling good. Now I want to assign the Product to the client. According to the videos it seems easy enough. When I select the client, the Product Configuration immediately displays the Products for the Client. Naturally, my new package is no longer available to mark it to perform setup. Further I can no longer "Unselect" the client and return to the Product Configuration and display my package to try some else. Reloading does nothing to display my new package. I generally have to logoff and back on to once again see my product package in the Product Configuration.

I've tried numeous ways to "make" the assignment of the package to the client with no luck. I figure I'm going to feel pretty foolish once some kind soul in the community has mercy and educates me on the simplier things of life.

Thanks!

[n.wenselowski]

Hello,

the first thing that comes to my mind is that this behaviour is normal with multiple depots that may not have the same software installed on them and you then select an client that belongs to a different depot.
How many servers are shown above the client list - there is a small part that shows a list of your opsi servers.

You did install your package with the opsi-package-manager as shown in the getting-started document I assume.
What is the output of the following command? Is your product listed in there?

Code: Alles auswählen

opsi-admin -d method productOnDepot_getHashes

What version of the configuration editor are you running?


With kind regards

Niko

[rmaxwell]

I'm running version 4.0.4.1.3 of the editor and yes there are two depots listed. On is the original based on an incomplete domain name (that I used first, then I reran the network setup with the revised domain name and the second was generated, and yes the software is not the same in both. Can I remove the original depot name? At this point I can simply re-install the server from the original VM server file if that would work better.

[rmaxwell]

Neglected to answer "output opsi-admin -d method productOnDepot_getHashes..." question - No my product does not show in thosed listed by the command and nearly as I can tell I followed the guide in the video series.

Thanks!

[n.wenselowski]

Hello,

I'm running version 4.0.4.1.3 of the editor and yes there are two depots listed. On is the original based on an incomplete domain name (that I used first, then I reran the network setup with the revised domain name and the second was generated, and yes the software is not the same in both. Can I remove the original depot name? At this point I can simply re-install the server from the original VM server file if that would work better.

Different opsi-depot-servers can have different products and this is your problem: one of your depots does have this product installed and the other one doesn't.

IMHO the easiest way would be to re-deploy the VM and blaze through the getting started (you probably have this done in a couple of minutes once you know what you are doing ). After that install your products on the server. An easy way to save your custom products is to backup the .opsi-files of your products.


With kind regards

Niko

[rmaxwell]

Yes - I agree not further along in the evaluation process than I am, reloading would be the most sensible option. Thanks for your Help!