Assistance with application deplyoment - Paperport

After a Reboot, It's stating that it can't "continue" the installation.

You may want to make sure that when you do your snapshot, that you had rebooted before completing the snapshot.
It sounds like the snapshot is placing some commands in the HKLM\Software\Microsoft\Windows\Currentversion\Run Once Key that are finishing the install.
Since they are not an admin, they are not completing.

If you do a reboot prior to completing the snapshot it should finish that stuff up.

--
Craig Wilson - MCNE, MCSE, CCNA
Novell Support Forums Volunteer Sysop

Novell does not officially monitor these forums.

Suggestions/Opinions/Statements made by me are solely my own.
These thoughts may not be shared by either Novell or any rational human.

"Alan Lew" <lewa@law.anu.edu.au> wrote in message news:48BD3162.CD2E.006E.0@law.anu.edu.au...
Thanks for the suggestion Craig,

You are right in that the install is via a snapshot. I did look through the registry and modified (also later deleted) the install path to point to a network share where I copied the contents of the CD, but this didn't make any difference as the user required local admin privileges to run the msi.

Making the application object system user equivalent didn't help either as the referencing of the CD\msi was a local process that did not involve the app obj.

Further testing revealed that the referencing of the CD\msi file is:

1. user specific - if I logged in as the local admin only, Paperport did not seek the CD\msi file until I ran the application. When the referencing of the CD was complete Paperport ran OK, but when I logged in as the user, the same looping occurred - Paperport would try to fine the CD\msi to complete whatever it was it need to complete.

2. possible registration related, but this was covered when doing the snapshot.

We have found a solution (although messy, does work) which is to also associate the application to the user's workstation object. What now happens is when Paperport tries to reference the CD\msi it will fail, we advise the user to go into taskmanager and end task the paperport process then start Paperport via the application object icon. Paperport starts up, references the CD and completes whatever it needed to do. All subsequent runnings of Paperport work fine, no need to areference the CD.

What I think is happening is the application is running as the system user via the workstation association when referencing the CD.

Alan

>>> Craig Wilson<craig_d_wilson@yahoo.com> 26/8/2008 6:06 am >>>

Sounds like the Install was done via a Snapshot which is why it can't find the install source.
Look for something like "InstallSource" in the Pushed Registry Keys and just remove it from the snapshot.
That should stop it from prompting.

--
Craig Wilson - MCNE, MCSE, CCNA
Novell Support Forums Volunteer Sysop

Novell does not officially monitor these forums.

Suggestions/Opinions/Statements made by me are solely my own.
These thoughts may not be shared by either Novell or any rational human.

"Alan Lew" <lewa@law.anu.edu.au> wrote in message news:48B2A101.CD2E.006E.0@law.anu.edu.au...
Hi All,

Problem application - Paperport Pro 9

Would like your advise\assistance with deploying Paperport, but first some background info:

Zenworks 4.01 on Netware 6.5 Sp7 server.
Clients are running WinXP Sp3 (+ post sp7 patches) with zdf agent 6.5 Sp2ir1

We have recently rollout new workstations and have locked down user accounts to standard users only via zenworks GPO, they were local admins previously - this was required to run specific programs in the past.

Prior to the rollout we tested the new user policy and deployment of applications - nearly all of them worked fine and deployed normally with some requiring modifications to registry and folder permissions. We did however have issues with Paperport and are still trying to resolve this, thus this posting.

We have network scanning services available, where users go to a central resource room, scan their document and go back to there room. The scanned images are ftp'd from the scanner to a network folder (one for each user) which is monitored from the user's workstations. Once the monitoring program detects the scanned images it will do two things:

1. move the images to a folder in the users home directory and
2. loads paperport so that the user can see the scanned document

Here's my problem with the application object:

1. the user deploys paperport and reboots at the end of the deployment when prompted
2. after logging in, paperport needs to access the paperport CD, I am assuming to install\update personal user information.

Stage 2. is where we are having the problem. In the past users were local admins which enabled them to install software, so they were given the CD and advised to load it when the computer was rebooting, paperport would then access the CD and finalise the install without any user intervention.

Now that we have reduced users to standard users they do not have the privileges to install software so when paperport tries to access the CD, the user receives a pop-up stating they are not administrators and cannot continue with the installation. If you run paperport after that, paperport will resume from where it left off and tries to complete the installation from the CD with the same result.

I have snapshotted the final stage where the CD is referenced to see what might be happening and I have also tried deploying this as a separate app, but without success.

The funny thing is, a straight install of paperport directly from the CD to a workstation does not require the CD again after you reboot, it just works that is why I think it might have something to do with personal user information when deployed to a different workstation.

Your assistance would be appreciated.
Alan