^shadow^ Posted March 21, 2009 Share Posted March 21, 2009 I am trying to find a way to deploy software to workgroup base PCs.I read an article in here, deploying via RIS, other than RIS is there another way to deploy the software(any tools).I don't mean deploying it via AD, to do this you have to be on a domain!!!thx in adv Link to comment Share on other sites More sharing options...
submix8c Posted March 21, 2009 Share Posted March 21, 2009 PXE or RPL (?)... Link to comment Share on other sites More sharing options...
^shadow^ Posted March 21, 2009 Author Share Posted March 21, 2009 are these two methods based on pre booting. if yes, I was looking for, after logging to the windows a way to deploy software.thanks for the reply Link to comment Share on other sites More sharing options...
submix8c Posted March 21, 2009 Share Posted March 21, 2009 (edited) Er, should have stipulated... your Network Card (in the "installee") has to support it (an extra "chip" on it).And that's for Windows (or any OS) Installs. If you're referring to "other than the Operating System software", AFIAK nope (could be wrong)!A "Push" install (not too clear on the details of this at all) may another method (other-than an OS)... Edited March 21, 2009 by submix8c Link to comment Share on other sites More sharing options...
bj-kaiser Posted March 22, 2009 Share Posted March 22, 2009 I guess he is looking for something like FrontRange NetInstall or other similar products. Link to comment Share on other sites More sharing options...
^shadow^ Posted March 22, 2009 Author Share Posted March 22, 2009 assume this: your PC x is in a domain and you want to deploy MS word package, so what do you do. you deploy this via GPO.now to do this the PC x should be on this domain.I want to do the same thing(deploy the software) but the PC x is in workgroup.thanks a lot for the replies Link to comment Share on other sites More sharing options...
submix8c Posted March 22, 2009 Share Posted March 22, 2009 (see attached image for this - LogonScript)NotesTo perform this procedure, you must be the member of the Power Users group who created the account or a member of the Administrators group on the local computer, or you must have been delegated the appropriate authority. If the computer is joined to a domain, members of the Domain Admins group might be able to perform this procedure. As a security best practice, consider using Run as to perform this procedure.To open Computer Management, click Start, click Control Panel, double-click Administrative Tools, and then double-click Computer Management.Logon scripts can contain malicious commands. It is recommended that you be familiar with the contents of the logon script before assigning it to a user.Logon scripts that are stored on a local computer apply only to users logging on to that local computer.Local logon scripts must be stored in a shared folder, or subfolders of the shared folder, named Netlogon. If this folder does not exist by default, you must create it. To specify a logon script that is stored in a subfolder of the Netlogon folder, precede the file name with the relative path to that folder. For example, to assign the Startup.bat logon script stored in \\ComputerName\Netlogon\FolderName to a local user, in Logon script, type: FolderName\Startup.batWould this help at all? It would require signing on to each PC. I guess this would be a kind of "Pull" install...Or... SMS (trial from MS)? (PUSH installs? ...just glanced at it, ddn't notice anything about AD(?)...)Or... (your on your own on this) - NUTS ..."PUSH/PULL"-type...(downloaded, extracted, no virus/trojan)The package includes the following utilities:NetRun - Schedule actions and push installs to clients from the login script. Link to comment Share on other sites More sharing options...
majormashup Posted March 23, 2009 Share Posted March 23, 2009 (edited) I have used pstools psexec in the past to run psexec on msiexec.exe with the silent unattended switches. it's a bit clunky as you will have to put a txt file together with a list of all of the PC's you want to deploy to but if you're handy with batch files you can quite easily put something together which will meet your requirements and have some basic error reporting etc.here is an untested example you may wish to tweak:@echo offset /p username="please enter username: "clsset /p password="please enter password: "clsset /p logfilepath="please enter log file path: "clsset /p msipath="please enter msi path: "clspausepsexec -t /accepteula \\examplePC -u %username% -p %password% msiexec.exe /a /l %logfilepath% "%msipath.msi%" /qnremember to replace the \\example PC with @file (linked to a text file of PC's you wish to install to) if you want to install to multiple machines Edited March 23, 2009 by majormashup Link to comment Share on other sites More sharing options...
^shadow^ Posted March 24, 2009 Author Share Posted March 24, 2009 thank you very much guys, you all have been very helpful. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now