ActiveSync 4.5 via Group Policy
Doesn't seem to work. Does anyone out there have experience getting this to work via a GP deployment?
It's already a vendor MSI (Microsoft), not entirely sure why it's not working at the moment.
Thanks
It's already a vendor MSI (Microsoft), not entirely sure why it's not working at the moment.
Thanks
0 Comments
[ + ] Show comments
Answers (5)
Please log in to answer
Posted by:
dm1
16 years ago
The installation fails with a message saying 1: The ALLUSERS property is not 1 - This MSM cannot be used for a Per-user or fallback to Per-user install.
ALLUSERS = 1 in the installation and I've tried changing it to 0 & 2 to no avail.
I dug up some info on MSMs compiled for different VC++ runtimes on Aaron Stebners blog but didnt understand it particularly well!
Cheers
ALLUSERS = 1 in the installation and I've tried changing it to 0 & 2 to no avail.
I dug up some info on MSMs compiled for different VC++ runtimes on Aaron Stebners blog but didnt understand it particularly well!
Cheers
Posted by:
AngelD
16 years ago
Could you post which one of Aaron's blog (URL) you're referring to?
Which merge module(s) are you including in the package?
Look for any LaunchCondition table entry that could prevent this.
Verify that no custom action is changing the ALLUSERS property, a verbose log should tell you this quickly.
Are you adding the package to the group policy in the Computer Configuration section?
Which merge module(s) are you including in the package?
Look for any LaunchCondition table entry that could prevent this.
Verify that no custom action is changing the ALLUSERS property, a verbose log should tell you this quickly.
Are you adding the package to the group policy in the Computer Configuration section?
Posted by:
dm1
16 years ago
http://blogs.msdn.com/astebner/archive/2007/01/30/resolving-net-framework-2-0-setup-error-related-to-the-allusers-property.aspx
MFC and CRT are the merge modules that are being installed. Both have version 8.0.50727.42.
I had removed the LaunchConditions but no luck.
To be honest, I'm not sure where to look for the verbose log, or if one is even created because it's a GP deployment and I can't specify command line parameters in the package.
MFC and CRT are the merge modules that are being installed. Both have version 8.0.50727.42.
I had removed the LaunchConditions but no luck.
To be honest, I'm not sure where to look for the verbose log, or if one is even created because it's a GP deployment and I can't specify command line parameters in the package.
Posted by:
AngelD
16 years ago
You can enable windows installer logging through policy (group policy) or manually adding the registry entries on the client your trying to install the package on.
HKLM\SOFTWARE\Policies\Microsoft\Windows\Installer
Logging (REG_SZ) = icewarmupvx
If you deploy the package through group policy per-machine the verbose log will be located under C:\windows\temp with a name of MSIxxxxx.LOG (sort by date to).
HKLM\SOFTWARE\Policies\Microsoft\Windows\Installer
Logging (REG_SZ) = icewarmupvx
If you deploy the package through group policy per-machine the verbose log will be located under C:\windows\temp with a name of MSIxxxxx.LOG (sort by date to).
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.