I am integrating EZCD Creator 5 in to a corporate environment via SMS 2003 on XP SP-1. Because a standard user is calling the installation they can not log back in after reboot as an administrator. The installation routine indicates this is required. Does any one know how to bypass this and why the reboot and log in as admin is required. The RunOnce registry key shows that some DLLs require registration. I am guessing that some PendingFileRename operations may be required. I also believe the driver is installed only after a reboot. Has anybody experienced anything like this?
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
If you are using group policies then there is a policy that is "Always Install With Elevated Priviledges". I wuold add that to your domain policy and deply the software via Group Policy "software installation settings". Actually what i would have done is deployed Nero, you might run into problems with regualr user accounts not having the proper access rights to "Burn". Nero has a utility that sets the proper local rights to allow Nero to burn, it is a great utility, and Nero is cheaper, but for you I fear it may be too late as you have probably already purchased the software. You may want to do a bit more research on softwares that you deploy before purchasing them, most companies are willing to send you a full version for testing if they have the chance to make a sale, at least this has been my experience. At least you are here, that is a good first step.
Answered 05/21/2004 by: cdupuis
Third Degree Green Belt

Please log in to comment
0
I havent attempted to repackage this app but I know you wont have an easy time of it.

cdupuis is correct about setting "Elevated Rights" in Group Policy but you have to set the policy on both the Machine policy and the user policy. If you dont then it wont work. See the MS site for instructions.

Your DLL registration problem is easy to fix depending on your packaging software. Create a custom action to manually register the dll's during installation.
Answered 05/23/2004 by: MSIMaker
Second Degree Black Belt

Please log in to comment
0
The Roxio isn't easy to repackage. I have attempted repackaging it in several ways vis-a-vis: Creating a transform for the MSI and MST from the vendor; Creating an MSI from both the Install.exe and Setup.exe supplied by the vendor but they all seem to have the same problems. Some applications can't be launched. You can't really isolate the problem to the registration of the DLLs as you encounter this same problem when the only transformation you attempt to do is the License key.
Answered 07/30/2004 by: oofemioo
Blue Belt

Please log in to comment
0
To my understanding you can 'drop' system events onto computers without userintervention
Make sure the ALLUSERS Property is set to 2.
Deploy the package via SMS to the machine (with an Administrative account), then, make sure it reboots.
It can also be a pain as to what type of cdwriter is used (IDE/SCSI).
Nero would indeed be a 'better' choice for they have the Nero Burnrights Installer,
it's a shame there's no cli for this tool.
Answered 07/30/2004 by: inert
Orange Belt

Please log in to comment
0
I eventually imported the whole registry on a working machine. Afterwards I used Beyond Compare to compare the differences between a working version of the registry and a non-working version and it worked. But kindly note you have to take very painstaking efforts to ensure no unecessary reg keys are added to your installation. That really takes time!!!
Answered 09/24/2004 by: oofemioo
Blue Belt

Please log in to comment
Answer this question or Comment on this question for clarity