I am testing trying to install DeepFreeze6 Enterprise in a computer lab. There is no way to make as .msi file that I can use on a 2003 server to install on all the computers.
Is there a simple batch file I can use to install on the computers? Should I use a VB script? I am studying VBscripts, but have not found anything on installing executables.
The instruction book with deepfreeze talks about silently installing with batch files. It provides a sample command line "DF6Wks.exe /install /freeze=C /PW=password"
I understand the command line, what I don't know is what batch file should I insert that in? Any ideas on where I can learn and see sample batch files or VB scripts to use that command?
Is it that simple?
Posted by TomDavidson (Member # 124) on :
Yes, provided that the account which runs the batch has administrative rights.
Posted by lem (Member # 6914) on :
quote: Yes, provided that the account which runs the batch has administrative rights.
Are you talking about the account that logs onto the computer or the account I set up the batch file on?
I plan to link a group policy to the batch file (which will reside on the server). If I do that, then all the computers in the OU should install the program since I am logged on to the server as an administrator--right?
Or do I need to put the computers in the OU in a group and give that group administrative (full) permission to the group policy?
Posted by lem (Member # 6914) on :
I am bouncing back and forth with an exe file and an msi file.
When I do my msi script, I put in the full file path instead of browsing. When I restart the machine it doesn't add the program.
I have the program in a network folder with Administrator and System having Full control over the folder contents. Any ideas why it is not working?
Posted by TomDavidson (Member # 124) on :
Administrator and System are local accounts on each machine. A folder secured on your file server that way will have access restricted to the local system processes and the local administrative user for the file server.
This is no problem if you're running the script from the server and pushing the install out remotely to the other machines, but you probably aren't; for one thing, you probably need to be pushing the install out under an administrative account for those machines.
Rather, you need to run the install from a domain account that has administrative rights to all the individual machines AND has rights to the fileshare (but not necessarily the entire file server).
(BTW, I would strongly recommend looking into WSUS/Group Policy for this kind of software deployment, and SMS if you can afford it. It will save you much grief and heartache.)
quote: I plan to link a group policy to the batch file (which will reside on the server). If I do that, then all the computers in the OU should install the program since I am logged on to the server as an administrator--right?
More accurately, all the computers in the OU that have permission to read that policy will then attempt to run your batch file using whatever account they used to initially read the policy (or under whatever account you specify as part of the policy; I strongly recommend this latter option). Note that running this batch file requires that the account in question a) have rights to view the policy itself; b) have rights to the fileshare; c) have rights to install applications on the local machine.