Hi.

Deploying Microsoft DirectAccess Connectivity Assistant from SCCM 2007 to windows 7 clients.

Client is rebooting automatically during  / after? program instal.

In Advertisement status i get this message:

Windows Installer per-user elevation of this program ("C010023F" - "DirectAccess client x64") failed for advertisement "C0120415". The operating system reported error 1603: Fatal error during installation. This program was started. Please check the status of this program to determine whether or not it was completed sucessfully
Possible causes: The version of Windows Installer on the computer is less than version 2.0, or the setup program does not support Windows Installer per-user elevated rights installations.
Possible solutions: Update the version of Windows Installer on the computer to version 2.0 or later, or contact the software vendor that supplied the install program to determine if a version of setup that supports per-user elevated rights is available.

I have tried two different instal strings:

msiexec.exe /qb! /i "DirectAccess_Connectivity_Assistant_2_0_x64.msi" ALLUSERS=2 /m SIIITTT

msiexec.exe /i "DirectAccess_Connectivity_Assistant_2_0_x64.msi" /qn

Application log on client says Installation completed successfully.

What is the reason for the unwanted reboot?

I have installed the sw manually, that works fine. No reboot there.

Hi,

This error can be caused by the WMI issue. Please go to check the WMI permission to test.

Regards,

Sabrina

• Edited by Sabrina Shen Thursday, May 30, 2013 9:05 AM
• Marked as answer by Nicholas Li Friday, June 07, 2013 4:11 AM

Hi,

This error can be caused by the WMI issue. Please go to check the WMI permission to test.

Regards,

Sabrina

• Edited by Sabrina Shen Thursday, May 30, 2013 9:05 AM
• Marked as answer by Nicholas Li Friday, June 07, 2013 4:11 AM

Hi,

This error can be caused by the WMI issue. Please go to check the WMI permission to test.

Regards,

Sabrina

• Edited by Sabrina Shen Thursday, May 30, 2013 9:05 AM
• Marked as answer by Nicholas Li Friday, June 07, 2013 4:11 AM

Error code 1603 is a generic error, Could you please check the Event Viewer (Application Log) of the machine and confirm... Possibly you may get reason behind cause...

Raman Katoch

• Edited by Raman Katoch Thursday, May 30, 2013 10:59 AM
• Marked as answer by Nicholas Li Friday, June 07, 2013 4:11 AM

Error code 1603 is a generic error, Could you please check the Event Viewer (Application Log) of the machine and confirm... Possibly you may get reason behind cause...

Raman Katoch

• Edited by Raman Katoch Thursday, May 30, 2013 10:59 AM
• Marked as answer by Nicholas Li Friday, June 07, 2013 4:11 AM

Error code 1603 is a generic error, Could you please check the Event Viewer (Application Log) of the machine and confirm... Possibly you may get reason behind cause...

Raman Katoch

• Edited by Raman Katoch Thursday, May 30, 2013 10:59 AM
• Marked as answer by Nicholas Li Friday, June 07, 2013 4:11 AM

Hey Roar66,

did you find a solution for your problem? I've some troble with DCA2.0 and SCCM 2012 R2, too.

We've tried to install the package with "msiexec /i package.msi /qn". It works but it stops with an automatic reboot. Thats not enough for a mass-deployment. With msiexec /l i've found an 1603 error message within the logfile, too.

We've tried it again with "msiexec /i package.msi /qn /norestart" but without success.

After some investigation we've extracted the msi-file with 7zip and found a DcaMsu (no file extension). But it's a valid MSU-File. You can rename it and install it with "wusa.exe dca.msu /quiet /norestart" and uninstall it with "wusa.exe /quite /uninstall /norestart".

I don't know if its supported but it works like a charm.

• Proposed as answer by heyko Thursday, December 04, 2014 2:15 PM

Hey Roar66,

did you find a solution for your problem? I've some troble with DCA2.0 and SCCM 2012 R2, too.

We've tried to install the package with "msiexec /i package.msi /qn". It works but it stops with an automatic reboot. Thats not enough for a mass-deployment. With msiexec /l i've found an 1603 error message within the logfile, too.

We've tried it again with "msiexec /i package.msi /qn /norestart" but without success.

After some investigation we've extracted the msi-file with 7zip and found a DcaMsu (no file extension). But it's a valid MSU-File. You can rename it and install it with "wusa.exe dca.msu /quiet /norestart" and uninstall it with "wusa.exe /quite /uninstall /norestart".

I don't know if its supported but it works like a charm.

• Proposed as answer by heyko Thursday, December 04, 2014 2:15 PM

Hey Roar66,

did you find a solution for your problem? I've some troble with DCA2.0 and SCCM 2012 R2, too.

We've tried to install the package with "msiexec /i package.msi /qn". It works but it stops with an automatic reboot. Thats not enough for a mass-deployment. With msiexec /l i've found an 1603 error message within the logfile, too.

We've tried it again with "msiexec /i package.msi /qn /norestart" but without success.

After some investigation we've extracted the msi-file with 7zip and found a DcaMsu (no file extension). But it's a valid MSU-File. You can rename it and install it with "wusa.exe dca.msu /quiet /norestart" and uninstall it with "wusa.exe /quite /uninstall /norestart".

I don't know if its supported but it works like a charm.

• Proposed as answer by heyko Thursday, December 04, 2014 2:15 PM

Hey Roar66,

did you find a solution for your problem? I've some troble with DCA2.0 and SCCM 2012 R2, too.

We've tried to install the package with "msiexec /i package.msi /qn". It works but it stops with an automatic reboot. Thats not enough for a mass-deployment. With msiexec /l i've found an 1603 error message within the logfile, too.

We've tried it again with "msiexec /i package.msi /qn /norestart" but without success.

After some investigation we've extracted the msi-file with 7zip and found a DcaMsu (no file extension). But it's a valid MSU-File. You can rename it and install it with "wusa.exe dca.msu /quiet /norestart" and uninstall it with "wusa.exe /quite /uninstall /norestart".

I don't know if its supported but it works like a charm.

What did you use as your detection rule?

Hi Broonster27,

i'm checking the DcaSvc.exe File Version.

Regards

Heyko