activesync & drivers, permissions required
hi there
I repackaged activesync 3.7.1
unfortunaty, our users do not have local admin or power user right (closed client).
How do I manage to "integrate" the drivers to the package?
I tried to import the regkeys required but that does not work.
thx for your help
Olivier
I repackaged activesync 3.7.1
unfortunaty, our users do not have local admin or power user right (closed client).
How do I manage to "integrate" the drivers to the package?
I tried to import the regkeys required but that does not work.
thx for your help
Olivier
0 Comments
[ + ] Show comments
Answers (38)
Please log in to answer
Posted by:
olivier
19 years ago
Posted by:
olivier
19 years ago
Posted by:
MSIMaker
19 years ago
Posted by:
subsense
19 years ago
Hi
I have the same problem.
We have a locked down environment for our users
When I install ActiveSync (3.8) manually (as an admin), every iPAQ we have is working great under the user credentials.
But as soon as I Package the application SOME iPAQ's won't work, System keeps asking for a admin password
So I tried the following:
I took the PNPDriverInstall.MSI
Added the wceusbsh.inf and the wceusbsh.cat to a directory C:\Programs files\Microsoft ActiveSync driver, A different directory, I know the files come with the ActiveSync Installation but I want the MSI to be the same as the template.
Changed the Custum Action (SETUPCOPYOEMINF) to the new path of the INF file (C:\Program Files\Microsoft ActiveSync drivers\wceusbsh.inf)
Did the same for the Custum Action SETUPADDTOSOURCELISTA
Removed the HP things in the MSI
Compiled it again with Wise Package Studio 4.61
Installed my packaged ActiveSync 3.8 MSI
Installed the newly made MSI
(reboot)
Problem not solved.
Am I forgetting something or did I made a dumb mistake?
Any help would be great!!
I have the same problem.
We have a locked down environment for our users
When I install ActiveSync (3.8) manually (as an admin), every iPAQ we have is working great under the user credentials.
But as soon as I Package the application SOME iPAQ's won't work, System keeps asking for a admin password
So I tried the following:
I took the PNPDriverInstall.MSI
Added the wceusbsh.inf and the wceusbsh.cat to a directory C:\Programs files\Microsoft ActiveSync driver, A different directory, I know the files come with the ActiveSync Installation but I want the MSI to be the same as the template.
Changed the Custum Action (SETUPCOPYOEMINF) to the new path of the INF file (C:\Program Files\Microsoft ActiveSync drivers\wceusbsh.inf)
Did the same for the Custum Action SETUPADDTOSOURCELISTA
Removed the HP things in the MSI
Compiled it again with Wise Package Studio 4.61
Installed my packaged ActiveSync 3.8 MSI
Installed the newly made MSI
(reboot)
Problem not solved.
Am I forgetting something or did I made a dumb mistake?
Any help would be great!!
Posted by:
olivier
19 years ago
Posted by:
subsense
19 years ago
Posted by:
olivier
19 years ago
Posted by:
subsense
19 years ago
Olivier,
Thanks for your reply,
I'm fighting with the downloaded template from Wise, copied the DLL' s in de system32 dir
And added the files to the file table.
But ik keep getting an error message, here is a part of the MSI installation log with the error.
MSI (s) (F8:7C): MainEngineThread is returning 1603
MSI (c) (2C:80): Back from server. Return value: 1603
MSI (c) (2C:80): Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
Action ended 11:27:20: ExecuteAction. Return value 3.
MSI (c) (2C:80): Doing action: Fatal_Error
Action start 11:27:20: Fatal_Error.
Action 11:27:20: Fatal_Error. Dialog created
I don't know why the MSI is not working, Have to investigate it more.
If you can mail me your MSI with an webmail account or from home you'll make me a very happy man!!
(Maybe renaming will do de trick for your proxy)
Thanks anyway!!
Thanks for your reply,
I'm fighting with the downloaded template from Wise, copied the DLL' s in de system32 dir
And added the files to the file table.
But ik keep getting an error message, here is a part of the MSI installation log with the error.
MSI (s) (F8:7C): MainEngineThread is returning 1603
MSI (c) (2C:80): Back from server. Return value: 1603
MSI (c) (2C:80): Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
Action ended 11:27:20: ExecuteAction. Return value 3.
MSI (c) (2C:80): Doing action: Fatal_Error
Action start 11:27:20: Fatal_Error.
Action 11:27:20: Fatal_Error. Dialog created
I don't know why the MSI is not working, Have to investigate it more.
If you can mail me your MSI with an webmail account or from home you'll make me a very happy man!!
(Maybe renaming will do de trick for your proxy)
Thanks anyway!!
Posted by:
subsense
19 years ago
Posted by:
olivier
19 years ago
Posted by:
subsense
19 years ago
Okay,
That's a good idea to place those dll's in a seperate directory.
I have a working package but as an admin but.....
One custum action is not being installed [:@] when I install the MSI with elevated priveleges (user and machine) as a user
Its this one:
MsiProcessDrivers funtion name ProcessDriverPackages
I keep getting the message Windows Installer Meseage 1603 in the MSI log
Ofcourse, when I make the user a local admin I've got no problems at all.
I've also tried to run the custom action under the Deferred execution - system context (instead of immediate execution)
But then the MSI doesn'y work anymore....
Any Ideas??[&:]
That's a good idea to place those dll's in a seperate directory.
I have a working package but as an admin but.....
One custum action is not being installed [:@] when I install the MSI with elevated priveleges (user and machine) as a user
Its this one:
MsiProcessDrivers funtion name ProcessDriverPackages
I keep getting the message Windows Installer Meseage 1603 in the MSI log
Ofcourse, when I make the user a local admin I've got no problems at all.
I've also tried to run the custom action under the Deferred execution - system context (instead of immediate execution)
But then the MSI doesn'y work anymore....
Any Ideas??[&:]
Posted by:
subsense
19 years ago
Posted by:
subsense
19 years ago
Posted by:
subsense
19 years ago
Posted by:
olivier
19 years ago
Posted by:
subsense
19 years ago
Posted by:
subsense
19 years ago
Posted by:
GregAU
19 years ago
Hi I am having the same problem.
Active sync repackages and installs successfully with admin privs but a restricted user needs a username and password when the PDA is going through the detection phase at first plugin.
I take it you guys are using Wise going by your replies. I am using Installshield and cant get it to work by trying to put together your responses.
Does anyone have a clear cut way to do this with Installshield?
Many thanks.
Active sync repackages and installs successfully with admin privs but a restricted user needs a username and password when the PDA is going through the detection phase at first plugin.
I take it you guys are using Wise going by your replies. I am using Installshield and cant get it to work by trying to put together your responses.
Does anyone have a clear cut way to do this with Installshield?
Many thanks.
Posted by:
olivier
19 years ago
Posted by:
subsense
19 years ago
Posted by:
olivier
19 years ago
Posted by:
bkelly
19 years ago
You can use the email links provided to contact people offline, but as of now MSI files may not be shared. At some point I hope a safe means of sharing packages can be realized- but for now there is too much risk in the possibility of including license information (and even source files).
In the future I hope to take a look at MSI2XML as a means of allowing people to share packages via AppDeploy. With some tweaks, we could build in license/serial filtering so only the installation logic would remain (to compile such a package, you'd have to install the software so source files would resolve, and finally you'd have to enter your own license info). However, this is still something on the drawing board that should not be expected any time soon.
In the future I hope to take a look at MSI2XML as a means of allowing people to share packages via AppDeploy. With some tweaks, we could build in license/serial filtering so only the installation logic would remain (to compile such a package, you'd have to install the software so source files would resolve, and finally you'd have to enter your own license info). However, this is still something on the drawing board that should not be expected any time soon.
Posted by:
olivier
19 years ago
Posted by:
subsense
19 years ago
Posted by:
subsense
19 years ago
Posted by:
subsense
19 years ago
Solved!
During logon I check if a user is a member of de ActiveSync Security group, I Also check on a certain reg value.
When both conditions are true and an installation of ActiveSync in present the MSI will install. (doing this with VBS)
The MSI writes the certain reg value, so during the next logon the ActiveSync Device Driver installation wil not fire up anymore.
The provided MSI works, but not with our distribution application (VAI Deployment Center, keep getting Windows installer error 1603 in the MSI logfile)
All your support has been great!
Thanks!
During logon I check if a user is a member of de ActiveSync Security group, I Also check on a certain reg value.
When both conditions are true and an installation of ActiveSync in present the MSI will install. (doing this with VBS)
The MSI writes the certain reg value, so during the next logon the ActiveSync Device Driver installation wil not fire up anymore.
The provided MSI works, but not with our distribution application (VAI Deployment Center, keep getting Windows installer error 1603 in the MSI logfile)
All your support has been great!
Thanks!
Posted by:
sejacru
19 years ago
Posted by:
sejacru
19 years ago
Posted by:
mgroover
19 years ago
With Active Sync I have so far been successful with installing the drivers in the following manner. We have win2k clients and SMS AP-installation via the SMS account which is admin, it doesn't always work as it should either I might add.. =oD :
Put the Active Sync 3.8 drivers in a separate folder called driver under the main program files folder
Create a dpinst.xml in this folder containing the following information:
<?xml version="1.0"?>
<dpInst>
<quietInstall/>
</dpInst>
Create a custom action that runs, during installation and repair, the dpinst.exe tool with the correct folder as working directory. I had to solve this using a bat-script, a bit aggrevating but needed for it to get the correct working directory since our SMS can't handle the "Run in" property for some reason.
Create a custom action that runs, during uninstall, the uninstallstring for the dpinst-package (get this from HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall).
Voila, works like a charm. As long as the installation is run from an account with adminprivs, you have no problems.
// martin
Put the Active Sync 3.8 drivers in a separate folder called driver under the main program files folder
Create a dpinst.xml in this folder containing the following information:
<?xml version="1.0"?>
<dpInst>
<quietInstall/>
</dpInst>
Create a custom action that runs, during installation and repair, the dpinst.exe tool with the correct folder as working directory. I had to solve this using a bat-script, a bit aggrevating but needed for it to get the correct working directory since our SMS can't handle the "Run in" property for some reason.
Create a custom action that runs, during uninstall, the uninstallstring for the dpinst-package (get this from HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall).
Voila, works like a charm. As long as the installation is run from an account with adminprivs, you have no problems.
// martin
Posted by:
subsense
19 years ago
ORIGINAL: sejacru
Hello subsense,
I have the same problems. I downloaded from wise the driver template, so i thougt this was a piece of cake.
Ihave done exactly the same as on the wise site but i get an error. Could help me of email me the driver.msi?
That would me great.
greetings
sejacru
the netherlands
Okay dan,
Stuur even ene mailtje naar SubSenseNOSP@Mgmail.com
Uiteraard zonder NOSPM!
Grt Sub
Posted by:
olivier
19 years ago
Posted by:
subsense
19 years ago
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.