RightFax MSI printer creation

I'm trying to deploy RightFax using group policy, but the printer is not being created.
I'm working with Captaris technical support, but they keep pointing me to alternative methods for deployment, or saying it should work as is.

I'm positive that the MST I created functions properly. If I run msiexec /i ... TRANSFORMS=... under my domain admin account everything installs just fine. The problem comes when the installer runs under the system account, either using group policy, or with psexec.
IIt almost seems like a permissions problem, but I don't see how that can be the case with the system account.
LVL 1
timbrighamAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

timbrighamAuthor Commented:
Update - I have tried running the install under one DA account while logged in to the console under a second account. The problem manifests itself here as well. The problem appears to be the lack of console interaction during the installation process.
0
Vadim RappCommented:
ideas:

1. they indeed have put some custom action that creates the printer into the user sequence. Such things have to be in the deferred sequence. You can verify this by running the msi with switch /qb or /qn, so user sequence is bypassed. If it's the case, then find out what the action is by visually looking at the script, and move it to the right sequence.

2. the printer is created, but for the machine "user".
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
timbrighamAuthor Commented:
I looked at the registry for all the users under HKEY_USERS, and I didn't see any of the keys for the printer created there. I'll try running with /qb or /qn and report back.
0
Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

timbrighamAuthor Commented:
Running with /qb results in an execution error. I'll fire up WISE and try to track down where they are creating this printer. I'm not too familiar with the internals of the various sequences - all I've ever done is write a couple simple wrappers for a scripted install. Where exactly is the deferred sequence?
Also, I poked through the DLLs and found how the printer is being created. Will the function name I found for the DLL be the same thing I'm looking for in the MSI stream?
0
timbrighamAuthor Commented:
I've located the custom action creating the printer. It was under execute immediate.
I've moved the section to execute deferred, but where in the stream should I place it? Directly above install finalize, the same as have for my scripted installs in the past?
0
Vadim RappCommented:
> Where exactly is the deferred sequence?
on the picture - "execute deferred"

see http://juice.altiris.com/article/3594/guidelines-custom-action-location for guidelines.

> Will the function name I found for the DLL be the same thing I'm looking for in the MSI stream?
only msi author would know. But you will see it in the script.

Capture-10-23-00001.png
0
Vadim RappCommented:
Yes, before install finalize.
0
Vadim RappCommented:
you can also experiment with pausing the installation before and after the action by placing "display message" action; during the installation when it shows the message, go and see if the printer is already created or not. Also you can run regmon after the "before" message and see, maybe some registry write fails.
0
timbrighamAuthor Commented:
I ended up contacting RightFax again and got a hold of an engineer. We were on track as to the cause of the problem. They had a patch that addressed this issue, but the original tech didn't know about it.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Software

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.