Software Deployment

Hi Mate,

Software installation with SMS 2003 is the legacy mode I believe.
You can either use lock permissions in the MSI table (Is it a MSI, transform etc?) or my preference is to use SetACL - some people use xcacls etc...not a big fan myself but its personal choice.
Setacl is free from sourceforge and you can set permissions on file, directory and registry quietly.
Compile your setacl line in an exe (wisescript) or vbs file and add it in SMS...
Example for setacl would be
setacl -on "somefilename.txt" -ot file -actn ace -ace "n:users;p:full"
somefilename.txt is your filename you want to apply permissions to...in this case "Users group" and "full control"

I am having a problem getting the installer to get past a security rights issueWhat does that mean? Is it disallowing the install completely? Have you enabled verbose logging and examined the log? If so, what error is returned? If not, why not? If the problem is with file/registry access permissions, then Ole's suggestion is spot on. Remember, though, that it's quicker to execute a permissioning Custom Action immediately after the CreateFolders action rather than after, as the files will inherit the permissions. If you do it after, the CA will have to permission every single file.

Yes, it is not allowing the installation to go through completely. When trying to install the application on a computer without a domain admin or system admin account, this message comes up:: error 1304. Error writing to file c:\windows\system32\drivers\atnt40k.sys. Verify that you have access to that directory.

I believe SMS 2003 uses the local System Account when installing applications. I don't recall if you have an option to run as "logged on user" or not, but check to make sure that you don't have this set if so. If it is indeed running as the local SYSTEM account and you're still having access problems...then ew, you may have your file system permissions kinda messed up.

On a machine you're having problems with, copy your install files in the c:\temp\whatever and do the following:

1. From a command prompt, run: "AT 12:00PM /INTERACTIVE cmd.exe" (put the time so it's a minute away from whatever the current time is)
2. Wait for the new command prompt to open, it will run under the SYSTEM context.
3. On the new command prompt, navigate to your c:\temp\whatever file and run the installer (make sure to include the verbose log)

This will tell you if the problem is with the rights of your SYSTEM context or if it's with the way you're configuring the distribution through SMS.

Good luck,
Jay

First you need to make sure to install with an account that has admin privs on the computer you're trying to install too.
Second; if the service is already installed which is using the "atnt40k.sys" then you need to stop that service before doing anything with the file.
You can stop/start/delete a service by using the ServiceControl table.