- This topic is empty.
12. November 2008 at 22:32 #1591
OK, my 2nd script and first installing an actual application install Office Communicator. Systems is v90 running xpe.
Try 1:CreateProcess Failed:2 c:communicatormsiexec /i communicator.msi /q Line#: 32 Cmd:EX c:communicatormsiexec /i communicator.msi /q
and here is the suspect script:
Description= Installs Microsoft Office Communicator 2005
;Prepared by Joe Carreiro
;This is for use with Wyse v90 terminals running Windows XPe
;Query user with Now and 5 min delay option
;Check OS and Lock User
;Copy over new files
;execute new files
EX “c:communicatormsiexec /i communicator.msi /q”
;Local Pause for package to install
;remove install msi file and end lockout
Thanks for your help.13. November 2008 at 9:00 #14420
First of all, afaik MS Communicator is not running on XPe default build. Is it running for you if you install it manually?
Try changing the EX line in your script to something like
EX c:windowssystem32msiexec.exe c:communicatorcommunicator.msi /q………..
On the other hand, always remember that EX is executed as System and not as the logged in user!
CG13. November 2008 at 18:45 #14427
ConfigGen, once again, thank you very much for your help. The path you recommended was correct. Again, thank you, I’m new to all this but learning fast…..14. November 2008 at 7:43 #14428
You are welcome.
Is the Communicator working for you?
CG14. November 2008 at 17:04 #14433
Yes and no… it works, but I can not see our contacts status, says unknown, and while I can initiate a conversation with a contact, when they try to start one with me it says off line. I posted this question to the MS office discussion group.
the system is a v90 with xpe no office installed. Any thoughts?15. November 2008 at 10:28 #14445
These are same issue I saw. My customer ended up in buying a custom image from Wyse. I think to remember that there are several needed components were missing. But it is some years ago.
- You must be logged in to reply to this topic.