Hi,
I've got a problem with Office 2010.
The capture we did works well on most of our and customare system, but there is a particular machine configuration where Office doesn't get licence from KMS. These machines are Win XPSP3 with Office 2003.
I've tried to put a vbs script to let the service osppsvc starts on firstsanboxowner, I've found lot of script over internet, I've used this one:
---------------------------------
Do you see this behaviour for standard user or admin user?
Admin user.
By the way, I've tried to do in another way.
I've created a osppsvc.exe with AutoIt with this code:
$idResult=RunWait("net start osppsvc", "", @SW_HIDE)MsgBox(0,"TEST", "Result: " & $idResult & " " & @error)
I've changed the vbs like this:
Function OnFirstSandboxOwner intID=ExecuteVirtualProcess("c:\osppsvc.exe") WaitForProcess intID, 30000 End Function
Ok, on most of the machines I've tried all works good, but on a physical PC the service doesn't start! On that PC if I try the same version of offce without vbs, it works well.
On the same pc using a command prompt in the Office with no vbs, launcing the .exe file works well.
It makes me crazy because that PC is the PC where we have to certify our ThinApped Office 2010
I have never used VBS for Office 2010 activation.
Have you checked this PC has Office 2010 locally installed?
Try pinging the KMS server from this machine if it is accessible.
KMS answer good.
It's a total strange situations. We aren't able to correlate the problems. On some machine Office works good in both case, even if i use the VBS to activate or if I use simple start of Office.
On other machines using the VBS cause OSPPSVC fails to start. I've try also a simple VBS on fisrtsanbox owner and the result is the same.
On some client machine launcing a VBS on ThinApp start cause the failure of OSPPSVC service.
No customare PC has Office 2010.
tnks
