PMC pushing wrong fscs version to client

Aspirant

PMC pushing wrong fscs version to client

Hi community,

 

lately I'm confronted with the issue of pushing fscs-12.00.648.jar to my clients in the corporate network, and getting fscs-9.31-rtm.jar installed, about which the PMC sais: "Failed: setup error. Partial Success. ..."

Now under normal circumstances, I'd give it some time and eventually I'd see that fscs12 gets installed. But as of today this has turned into an issue that I can't live with, because before the 'eventually...' my boss got in the way and asked me why for heavens sake this OLD version is installed!

 

The way I've been going about pushing new version to clients is as follows:

1. get new version from f-secure as .jar file.

2. Import new .jar file into PMC.

3. push new .jar to all clients on the network.

 

since lately: 4. wonder why version 9 gets installed first and 12 some time after that.

 

Somebody please tell me that I'm doing it all wrong!

 

PMConsole / -Server  version 11.30.60634 running on Windows Server 2008 R2 x64

Clients all Windows 7 x64 within a Domain structure.

 

Regards

Mozzy

 

 

1 ACCEPTED SOLUTION

Accepted Solutions
F-Secure
F-Secure

Re: PMC pushing wrong fscs version to client

Hello Mozzy,

 

Do you have 9.31 package imported in Policy Manager Console (PMC)?

If yes, please, check that you don't have any rules configured to install 9.31 package, or simply delete it from PMC.

If no, please, contact support. We'll need more details for investigation.

 

Best regards,

Vad

2 REPLIES 2
F-Secure
F-Secure

Re: PMC pushing wrong fscs version to client

Hello Mozzy,

 

Do you have 9.31 package imported in Policy Manager Console (PMC)?

If yes, please, check that you don't have any rules configured to install 9.31 package, or simply delete it from PMC.

If no, please, contact support. We'll need more details for investigation.

 

Best regards,

Vad

Aspirant

Re: PMC pushing wrong fscs version to client

Thanks Vad!

 

Up until recently I didn't have this issue, and I didn't see any reason to delete packages from the PMC package collection. Nevertheless, I did as you advised, cleared out all the old packages and with that all old rules were vaporized. Set one new rule to deploy the current version 12 and guess what: works like a charm!Smiley Very Happy

 

Thanks!

Mozzy