Jump to content

Recommended Posts

Posted

We have just moved to PMP 7 from 6, we were running V6 with the Access Db but have used SQL 2005 with V 7. It seems to be slower that before when opening the console, before it took about 30 seconds to drag in all of the users now it seems to take about 2 mins?

 

Anyone else using it that can comment?

Posted

SQL 2005 is much more resource hungry than Access, but I'm sure I don't need to tell you that :)

 

If v6 worked fine with Access, then v7 should too - unless you've had a sudden increase of users? From memory, I think Access is suitable for upto 700 print jobs per day.

Posted (edited)

The server has pleanty of resources but yes i know it's a bit more resource hungry, we had a few niggles while using the access Db and their support suggested that using the SQL Db might sort them. Also we aren't going to be far short of the 700 print jobs limit.

 

@ Diello: i'll have a look at trimming the fat cheers.

Edited by cookie_monster
Posted

@cookie_monster - basically unticking that option stops the software searching the whole domain for anyone who doesn't have an entry in the database, once they print the first time, they get added.

 

Your delay isn't from the database, it's because your whole domain is being queried outside the db.

Posted (edited)

Once i set some restrictions by group they all seem to have an account created so i don't think that will work e.g the students group has 1400 members, when i apply propertied to that group all of the accounts are affected (is there a better way). I've filtered out any users that aren't members of active groups so that's reduced it a bit.

 

 

Ah don't worry i see what you mean now.

 

 

EDIT: Oh the end user tool seems to be an msi at last, JOY!!!

 

 

.

Edited by cookie_monster
Posted
Do either of you use the End user tool that sits in the system tray? I've got it to roll out via msi but it won't find the print server unless i edit a registry key is there a way to get it to browse for the server automatically.
Posted
Do either of you use the End user tool that sits in the system tray? I've got it to roll out via msi but it won't find the print server unless i edit a registry key is there a way to get it to browse for the server automatically.

 

Yes I do. Seeing as you've updated to PMP v7 (on the server), make sure you're using the latest EUIT, otherwise it won't work with PMP v7. Strange I know, but I found this too a while ago.

Posted

Yeah I am in the process of upgrading the print manager version 7

 

as for the end user enquiry yeah I remember the reg fix for this to see the server

 

Windows Registry Editor Version 5.00

 

[HKEY_LOCAL_MACHINE\SOFTWARE\Software Shelf International Inc\Print Manager Plus - Client]

"EUIT"=dword:00000001

"SERVER"="APPS1" <<<<< Your server :troll:

Posted

I have this same problem, it takes forever to download the user list, whether that option is ticked or not!

 

I am now going to upgrade the RAM on the server to see what happens, but it was fine on V6, even with SQL 2005. I don't know if this is something that Print Manager is aware of, or it is something to do with SQL server (or both). I will report back to you in a few days on what happens!

 

Mark

Posted

What a pain having to edit the registry grrrr i wonder if you can use Orca to add the key rather than having to do it via logon script, the EUET seems to be one let down after another.

 

We haven't tried the add credit web tool yet, we were using the user enquiry web page but it seemed to be a bit flakey so i tried the app version.

Posted (edited)

Yep i added a create registry key into the msi file, i used the Wininstall LE console but you could easily do it with Orca.

 

Select add row in the Registry section then enter this data with your server name:

 

Registry = WIREG00000001

Root = 2

Key = SOFTWARE\Software Shelf International Inc\Print Manager Plus - Client

Name = Name

Value = Yourservername

Component = CheckPages.exe

 

.

Edited by cookie_monster
  • Thanks 1
Posted

Have you had any odd issues like people not being able to logoff? I've only seen it a couple of times but since i rolled it out a few people have not been able to logoff, you click logoff and you see the AV software scan the A: drive then it pauses and doesn't logoff. I was beginning to suspect that the PMP client in the system tray was refusing to quit.

 

I'll keep an eye on it.

  • 2 weeks later...
Posted (edited)

I think i have solved the issue.

 

When the client is deployed it doesn't force a reboot at the end of the install. When a user then logs on there seems to be two versions of CheckPages.exe running one runs as the user and one runs under local system, when this happens the user cannot logoff unless they kill the process that is running as local system first. As our users are not local admins they cannot do this (so they have to cycle the power not ideal on 500 clients) but i have tested as a local admin and once the process is stopped a successful logoff can take place.

 

To try to prevent this from happening i have added REBOOT=FORCE to the property table of the PMP_EUIT.MSI using Orca, this forces a reboot at the end of the install which seems to of solved the issue.

Edited by cookie_monster
  • Thanks 1
  • 1 year later...
Posted
To try to prevent this from happening i have added REBOOT=FORCE to the property table of the PMP_EUIT.MSI using Orca, this forces a reboot at the end of the install which seems to of solved the issue.

Yet another post I wish I'd seen before I deployed this software. Thanks for the fix :)

Out of curiosity what version of the client are you running? Ours is "Client7.0.131.56_En_EUIT.msi".

The Property table already had "RebootYesNo=Yes" but there was definitely no reboot after install.

I added "REBOOT=FORCE" to my .MST file (which I had created to add the registry key for the server) and the PCs now reboot after installation and this seems to have fixed the unable-to-logoff problem...

Posted

The checkpages.exe file shows as 7.0.0.118 it's quite old i've not updated it as it works. This also has RebootYesNo=Yes in the property table but I had to add REBOOT=FORCE to make it restart after install.

I rang software shelf and told them about this and they added it to their support notes but it seems they didn't get as far as adding it to the msi.

  • Thanks 1
Posted
Glad I read this as I was going to roll the MSI out this week for ours as I forgot to put the old client on the images, whoops! So looks like more work :(

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...