Run setup.exe from netshare
in [VbScript]
|
From: JAV on 23 Jun 2008 17:29 Hello I am having a tough time figuring this one out. I need to run the setup.ese for Office 2007 from a network share and then apply updates via a msp file. I have the following scirpt below and it will not execute under logon startup. 'InstallStartupScriptBegin on error resume next set wshShell=WScript.CreateObject("WScript.Shell") Set strOutlook = CreateObject("Outlook.Application") If strOutlook.Version < "12" then wshShell.run "\\RemoteInstall\Software\Microsoft \Office2007\setup.exe /AdminFile \\Remoteinstall\Software\Microsoft \Office2007\Updates\office07config.MSP", 1, True Else wscript.Quit end if 'InstallStartupScriptEnd I put it together testing the outlook version since all clients have Outlook 2003 installed with the rest of the office suite. This script has been assigned via GP and dropped in the ntlogon folder on one of our DC's. Any help or hints to get this resoved would be wonderful. thanks for any help in advance. JV
From: Pegasus (MVP) on 23 Jun 2008 17:56 "JAV" <jonvillalva(a)gmail.com> wrote in message news:87d0b91d-bfeb-4049-a74c-4b25e7d24f2f(a)l28g2000prd.googlegroups.com... > Hello I am having a tough time figuring this one out. I need to run > the setup.ese for Office 2007 from a network share and then apply > updates via a msp file. I have the following scirpt below and it will > not execute under logon startup. > > 'InstallStartupScriptBegin > on error resume next > > set wshShell=WScript.CreateObject("WScript.Shell") > Set strOutlook = CreateObject("Outlook.Application") > > If strOutlook.Version < "12" then > wshShell.run "\\RemoteInstall\Software\Microsoft > \Office2007\setup.exe /AdminFile \\Remoteinstall\Software\Microsoft > \Office2007\Updates\office07config.MSP", 1, True > Else > wscript.Quit > end if > 'InstallStartupScriptEnd > > I put it together testing the outlook version since all clients have > Outlook 2003 installed with the rest of the office suite. This script > has been assigned via GP and dropped in the ntlogon folder on one of > our DC's. Any help or hints to get this resoved would be wonderful. > thanks for any help in advance. > > JV - Does the script run when executed from a Command Prompt? - What happens when you run it under the Startup script? - What happens when you replace your complex command with a very simple command, e.g. "xcopy.exe /y c:\test.txt d:\"? - Have you tested it without the "On error" statement? Using this statement is an excellent method for hiding all errors, thus making the debugging effort very difficult.
From: JAV on 23 Jun 2008 18:34 On Jun 23, 2:56 pm, "Pegasus \(MVP\)" <I....(a)fly.com.oz> wrote: > "JAV" <jonvilla...(a)gmail.com> wrote in message > > news:87d0b91d-bfeb-4049-a74c-4b25e7d24f2f(a)l28g2000prd.googlegroups.com... > > > > > Hello I am having a tough time figuring this one out. I need to run > > the setup.ese for Office 2007 from a network share and then apply > > updates via a msp file. I have the following scirpt below and it will > > not execute under logon startup. > > > 'InstallStartupScriptBegin > > on error resume next > > > set wshShell=WScript.CreateObject("WScript.Shell") > > Set strOutlook = CreateObject("Outlook.Application") > > > If strOutlook.Version < "12" then > > wshShell.run "\\RemoteInstall\Software\Microsoft > > \Office2007\setup.exe /AdminFile \\Remoteinstall\Software\Microsoft > > \Office2007\Updates\office07config.MSP", 1, True > > Else > > wscript.Quit > > end if > > 'InstallStartupScriptEnd > > > I put it together testing the outlook version since all clients have > > Outlook 2003 installed with the rest of the office suite. This script > > has been assigned via GP and dropped in the ntlogon folder on one of > > our DC's. Any help or hints to get this resoved would be wonderful. > > thanks for any help in advance. > > > JV > > - Does the script run when executed from a Command Prompt? > - What happens when you run it under the Startup script? > - What happens when you replace your complex command > with a very simple command, e.g. "xcopy.exe /y c:\test.txt d:\"? > - Have you tested it without the "On error" statement? Using > this statement is an excellent method for hiding all errors, > thus making the debugging effort very difficult. Just tried running from command prompt. Does not execute. I am getting a system error 53 Network path not found. Removing the On error resulted in an error on line 7 ch 4. I do not know why it is not liking the wshShell.run command. Is this a permissions issue?
From: Al Dunbar on 23 Jun 2008 19:59 "JAV" <jonvillalva(a)gmail.com> wrote in message news:f5d4bf22-4f58-4dd7-a4f8-163da6f05a01(a)w1g2000prd.googlegroups.com... On Jun 23, 2:56 pm, "Pegasus \(MVP\)" <I....(a)fly.com.oz> wrote: > "JAV" <jonvilla...(a)gmail.com> wrote in message > > news:87d0b91d-bfeb-4049-a74c-4b25e7d24f2f(a)l28g2000prd.googlegroups.com... > > > > > Hello I am having a tough time figuring this one out. I need to run > > the setup.ese for Office 2007 from a network share and then apply > > updates via a msp file. I have the following scirpt below and it will > > not execute under logon startup. > > > 'InstallStartupScriptBegin > > on error resume next > > > set wshShell=WScript.CreateObject("WScript.Shell") > > Set strOutlook = CreateObject("Outlook.Application") > > > If strOutlook.Version < "12" then > > wshShell.run "\\RemoteInstall\Software\Microsoft > > \Office2007\setup.exe /AdminFile \\Remoteinstall\Software\Microsoft > > \Office2007\Updates\office07config.MSP", 1, True > > Else > > wscript.Quit > > end if > > 'InstallStartupScriptEnd > > > I put it together testing the outlook version since all clients have > > Outlook 2003 installed with the rest of the office suite. This script > > has been assigned via GP and dropped in the ntlogon folder on one of > > our DC's. Any help or hints to get this resoved would be wonderful. > > thanks for any help in advance. > > > JV > > - Does the script run when executed from a Command Prompt? > - What happens when you run it under the Startup script? > - What happens when you replace your complex command > with a very simple command, e.g. "xcopy.exe /y c:\test.txt d:\"? > - Have you tested it without the "On error" statement? Using > this statement is an excellent method for hiding all errors, > thus making the debugging effort very difficult. Just tried running from command prompt. Does not execute. I am getting a system error 53 Network path not found. Removing the On error resulted in an error on line 7 ch 4. I do not know why it is not liking the wshShell.run command. Is this a permissions issue? ===> No, it is a syntax issue. Try changing the .run command to: wshShell.run """\\RemoteInstall\Software\Microsoft\Office2007\setup.exe"" /AdminFile \\Remoteinstall\Software\Microsoft\Office2007\Updates\office07config.MSP", 1, True /Al
From: Pegasus (MVP) on 24 Jun 2008 01:45
"JAV" <jonvillalva(a)gmail.com> wrote in message news:f5d4bf22-4f58-4dd7-a4f8-163da6f05a01(a)w1g2000prd.googlegroups.com... On Jun 23, 2:56 pm, "Pegasus \(MVP\)" <I....(a)fly.com.oz> wrote: > "JAV" <jonvilla...(a)gmail.com> wrote in message > > news:87d0b91d-bfeb-4049-a74c-4b25e7d24f2f(a)l28g2000prd.googlegroups.com... > > > > > Hello I am having a tough time figuring this one out. I need to run > > the setup.ese for Office 2007 from a network share and then apply > > updates via a msp file. I have the following scirpt below and it will > > not execute under logon startup. > > > 'InstallStartupScriptBegin > > on error resume next > > > set wshShell=WScript.CreateObject("WScript.Shell") > > Set strOutlook = CreateObject("Outlook.Application") > > > If strOutlook.Version < "12" then > > wshShell.run "\\RemoteInstall\Software\Microsoft > > \Office2007\setup.exe /AdminFile \\Remoteinstall\Software\Microsoft > > \Office2007\Updates\office07config.MSP", 1, True > > Else > > wscript.Quit > > end if > > 'InstallStartupScriptEnd > > > I put it together testing the outlook version since all clients have > > Outlook 2003 installed with the rest of the office suite. This script > > has been assigned via GP and dropped in the ntlogon folder on one of > > our DC's. Any help or hints to get this resoved would be wonderful. > > thanks for any help in advance. > > > JV > > - Does the script run when executed from a Command Prompt? > - What happens when you run it under the Startup script? > - What happens when you replace your complex command > with a very simple command, e.g. "xcopy.exe /y c:\test.txt d:\"? > - Have you tested it without the "On error" statement? Using > this statement is an excellent method for hiding all errors, > thus making the debugging effort very difficult. Just tried running from command prompt. Does not execute. I am getting a system error 53 Network path not found. Removing the On error resulted in an error on line 7 ch 4. =========== Slight correction: Removing the On Error statement does not "result" in an error - it makes the error visible (which you previously suppressed)! This is why having On Error statements is a bad thing while developing code. |