For example, SMS 2003 allows you to run vbscripts that are on the os. The problem is that I can't figure out how to implement the script in 64 bit mode. When I manually launch the slmgr.vbs script in 64 bit, it works fine. What I have found is that if I execute this script in 32 bit mode, the script appears to work (I get a successful message stating that the kms host was cleared) but later when I check the settings, I see that the clearing of the KMS host was not performed. My goal is to run this script to clear the kms host slimgr.vbs /ckms. My vbscript that I am trying to automate is called slmgr.vbs <- this is a built in script to the OS.
but it can be hard to communicate over text sometimes. Note: I have tried using this command line in my Wise and SMS program line: %windir%\System32\cmd.exe /c cscript somescript.vbs /ckms //t:15 (but when I watch the processes through task manager, I can see that cmd.exe 32 bit version is It seems that when I try to launch cscript from a 32 bit program (like sms 2003 or Wise), the 32 bit version of the script is always ran. how can I force 64 bit version of cscript (vbscript). and I can't get it to run the 64 bit vbscript. I also have Symantec (Alteris) Wise package studio.
However, because SMS/SCCM client is 32-bit, it always attempts to implements the script using the sysWOW64 cscript. And I believe that I should be running the 64 bit version anyway.so why do I care? I care because if I want to automate this somescript.vbs, I will be using a 32 bit program like SMS to pushįor example, I have the ability to push out a package through SMS 2003 or SCCM 2007. so SysWOW64 is there for 32 bit reasons. I have found that the outcome of running somescript.vbs might be different depending on how you run the script:Ĭ:\windows\system32\cscript somescript.vbs (works great on a 64 bit server.)Ĭ:\windows\ sysWOW64\cscript somescript.vbs (Although the output is successful, this doesn't actually run properly.
0 kommentar(er)
