Re: [foxboro] [UCE] Re: Fwd: Windows based I/A Foxview user name & password

The only way I know of is to get into the services configuration applet 
(Start->Run->services.msc), right-click on each one of interest, select 
Properties, Logon tab, and modify it there.  There's probably some way to 
do it via registry hacking, but I've never tried it.

Corey





Daniel Wu <Daniel_Wu@xxxxxxxxxxxx> 
Sent by: foxboro-bounce@xxxxxxxxxxxxx
01/27/2006 08:42 AM
Please respond to
foxboro@xxxxxxxxxxxxx


To
foxboro@xxxxxxxxxxxxx
cc

Subject
[UCE] Re: [foxboro] Fwd: Windows based I/A Foxview user name & password










Corey,

I am not familiar with the steps to change user/password on each service.
Does it involve changing Windows registry or just modifying some encrypted
I/A application files?  Would very much appreciate any documentation or
tips how to proceed!

Daniel Wu





Corey R Clingo
<clingoc@basf-cor        To:       foxboro@xxxxxxxxxxxxx
p.com>                   cc:
Sent by:                 Subject:  Re: [foxboro] Fwd: Windows based I/A 
Foxview user name & password
foxboro-bounce@fr
eelists.org


01/26/2006 10:20
PM
Please respond to
foxboro





Yes, we saw the same problem here.  They make all the I/A services run as
the "IA" user (name changed to mildly protect us hapless customers) rather
than LocalSystem, so you are screwed if you want to change passwords.   I
suppose you could go change the user/pass on each service, and it might
work, but I never had time to try it; I punted and changed the password
back to the default, and instead spent time tightening my firewall rules.

I too comically observed that this was from a company that also sold
"security services" (which, from reading the white papers, I roughly
interpreted as, "we build a mock-up of your system, and turn stuff off
until it breaks".  Gee...so much for leveraging design knowledge of their
system).  Reminds me of ol' Jimmy Swaggart from when I grew up in Baton
Rouge.  I had wondered where he ended up...  :)


I only bought an XP box because I had to (as an OPC gateway).  I hope to
be able to stay away from Win I/A as best I can until Foxboro at the least
makes their Windows offering "native" to the platform (rather than a hasty
port of their Unix codebase), and offers improved functionality and value
over the Unix version -- at least enough to offset the drawbacks of
running on Windows.


Corey






 
 
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
 
foxboro mailing list:             http://www.freelists.org/list/foxboro
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave

Other related posts: