Sccm 2007 and adminstudio MSI's that fail

[krumble99]

I have been creating msi to speed up application installs and I keep encountering an error when I try to use the MSI's

 

Error 1303; the installer has insufficient privileges to access this directory c:\windows\winsxs\amd64_microsoft....

 

I am running the installer as administrator and if you check the permissions on the winsxs folder the ONLY one that has access is the "Trusted Installer". I have found a lot of articles that document taking ownership of the folder and giving yourself permissions to it but this doesn't make practical sense when I want to push an application to 1800 desktops. does anyone else have this issue while deploying MSI's and can give me pointers on where to look to find a work around for this issue. I have 5 different application that I am trying to push as MSI's and am being stymied on all of them. I do have original installs that work but take a long time and reboots to complete that I am trying to eliminate.

Thank you for your time

[Peter van der Woude]

That folder is the Windows Component Store, why would your installer need access to that folder...

[krumble99]

The installer script is apparently updating :

MSI (s) (24:C4) [09:19:49:182]: Dir (source): Key: X86_MICROSOFT.VC90.MFC_1FC8B3B9A1E18E3B_9.0.30729.1_NONE_DCC7EAE9 , Object: C:\Windows\SysWOW64\CCM\Cache\BOS0030B.1.System\Tivoli msi\Windows\winsxs\x86_microsoft.vc90.mfc_1fc8b3b9a1e18e3b_9.0.30729.1_none_dcc7eae99ad0d9cf\ , LongSubPath: Windows\winsxs\x86_microsoft.vc90.mfc_1fc8b3b9a1e18e3b_9.0.30729.1_none_dcc7eae99ad0d9cf\ , ShortSubPath: Windows\winsxs\X86_MI~1.1_N\

 

This is only one of many similar lines that are generating the error access denied since Administrators have read only access to the folder and Trusted Installer has full control.

[krumble99]

Just as a follow up of my own question

I have managed to find a way to accomplish this, although cludgy it works. I created a powershell script that uses Icacls to save the current permission structure, takeown to take ownership to the adminstrators group, icacls to assign full control to adminstrators, install the software msi and then icacls to restore the original ownership and permissions.

 

Now I have another issue though. If I run the script from the command line using "powershell .\script.ps1" the script works, if I deploy it as a package the script also works, but if I try to deploy it as part of a task sequence I get a 0x80070001 file not found error.

 

When I run the task sequence it creates the c:\_smstasksequence\packages folder, copies the package files into the folder, and then immediately deletes the content and issues the error in the SMSTS.log.

The only difference I can see is that the package puts the files into c:\windows\sysvol64\ccm\cache instead for c:\_smstasksequence\packages.

I have tried program lines using powershell -file "%~dp0script.ps1", powershell .\script.ps1, powershell -command script.ps1 and every variation of these I can think of and have tried hard coding the Start In directory to the c:\_smstasksequence and various other combinations and cannot seem to get even a different error message.

Is there something fundamentally wrong with my logic here or shouldn't this be able to work. Execution policy is set to remote signed, scripts running as admin,