Since this is my first post here (and my first real dealings with Server 2008), I apologize if this is the wrong section - it simply seemed the best place to start. Here is my dilemma. I have the following two servers on my network.
1. Windows Server 2003 R2 Standard Edition running 32-bit.
2. Windows Server 2008 Standard Edition running 64-bit.
Server 1 has a VBScript file on a network share which runs an executable for our ERP software to initiate an import job. This has worked just perfectly from every Windows XP machine on the network, as well as from our other Server 2000 and Server 2003 machines. However, now that we've added Server 2008 to the mix, the script does not work properly. It does execute, launching the software (as seen by processes both on Server 1 and Server 2), however it seems to lock up as if waiting for some user response ultimately requiring me to reboot Server 1. I have found while searching that UAC may be playing a role in this problem.
Here is what I have tried so far.
1. Using an elevated command prompt (Run As Administrator), I can run the script and it works perfectly. How can I automate this in my script?
2. Using another persons recommendation I added some code to the beginning of my VBScript as show here:
If WScript.Arguments.length = 0 Then
Set objShell = CreateObject("Shell.Application")
objShell = ShellExecute "wscript.exe", chr(34) & WScript.ScriptFullName & chr(34) & " uac", "", "runas", 1
Else
'Execute my import job
End If
3. Disabling UAC on the server both by using the checkbox under User Accounts, and by selecting "Disable UAC" from msconfig. Neither seemed to help.
So, what can I do to make sure this script runs properly from Server 2008? Is it a problem with UAC, or does it have something to do with it being the only 64-bit machine on the network? Just for clarification, here is exactly what is going on....
1. Server 2 -> executes .VBS file located on //Server1/share
2. .VBS -> executes .EXE file located on //Server1/othershare
I have tried using the UNC path as well as a mapped drive which exists on Server 2 (M: drive) and have been unsuccessful in both attempts.
1. Windows Server 2003 R2 Standard Edition running 32-bit.
2. Windows Server 2008 Standard Edition running 64-bit.
Server 1 has a VBScript file on a network share which runs an executable for our ERP software to initiate an import job. This has worked just perfectly from every Windows XP machine on the network, as well as from our other Server 2000 and Server 2003 machines. However, now that we've added Server 2008 to the mix, the script does not work properly. It does execute, launching the software (as seen by processes both on Server 1 and Server 2), however it seems to lock up as if waiting for some user response ultimately requiring me to reboot Server 1. I have found while searching that UAC may be playing a role in this problem.
Here is what I have tried so far.
1. Using an elevated command prompt (Run As Administrator), I can run the script and it works perfectly. How can I automate this in my script?
2. Using another persons recommendation I added some code to the beginning of my VBScript as show here:
If WScript.Arguments.length = 0 Then
Set objShell = CreateObject("Shell.Application")
objShell = ShellExecute "wscript.exe", chr(34) & WScript.ScriptFullName & chr(34) & " uac", "", "runas", 1
Else
'Execute my import job
End If
3. Disabling UAC on the server both by using the checkbox under User Accounts, and by selecting "Disable UAC" from msconfig. Neither seemed to help.
So, what can I do to make sure this script runs properly from Server 2008? Is it a problem with UAC, or does it have something to do with it being the only 64-bit machine on the network? Just for clarification, here is exactly what is going on....
1. Server 2 -> executes .VBS file located on //Server1/share
2. .VBS -> executes .EXE file located on //Server1/othershare
I have tried using the UNC path as well as a mapped drive which exists on Server 2 (M: drive) and have been unsuccessful in both attempts.
