actxprxy.dll How to register on clients

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi,

I have around 650 XP pro workstations and maybe 30 or 40 of them need to
have actxproxy.dll re registered to allow open in a new window hyperlinks to
work.

We don't know which of the 650 have this problem so I am hoping there is a
work around that will allow me to re register the dll on all my
workstations.

Our network OS is Server 2003 using group policies and I we have access to
Install Shield Admin Studio 6 which we have used for repackaging. I Mention
this because google'ing found a post that suggested using installshield to
build an install that would re register a dll, sadly I don't have the
experience and posting was quite bare.

I know we can regsvr32 actxprxy.dll from the command line or login script
provided we are logging in as admin but our users are students and they
don't have admin privileges.

Anyone got any suggestions please?

One last question. Why has this happenend? We have the same hardware, OS,
and Application install on all these machines. All have NAV, are patched. We
use ISA server to protect our network and run GFI download security & Mail
security as well.

Andy.
 
You could package it as an MSI, then use group policy to push the
software to the machines in your domain.

-matt
 
Some of the groups you posted to are SMS groups, so can I assume you have
SMS in your environment?

Like you said you can just run that command line but need admin rights, if
that is the case then just use SMS to run the command line with admin
rights.

If you don't have SMS or some other automated deployment tool then I believe
there are free utilities out there that allow you to run command lines on
remote machines using a different set of credentials.

You could use InstallShield or "SMS Installer" to repackage a dll register,
however unless msi's always get elevated in your environment you are going
to run into the admin thing.

You could script the runas as part of the repackaged dll, but that starts to
get complicated because you need to be able to get the password and
everything in there automatically, there are ways to do it but not
completely simple.

You could include a su.exe in your repackaged app which then becomes real
simple to pass credentials and passwords to elevate privileges.

Anyway, lots of options, obviously if you have SMS or some other deployment
tool then your life is a lot easier, because you just tell it the command
line and to use admin rights and then send it out.

Terry
 
Matt Baldwin said:
You could package it as an MSI, then use group policy to push the
software to the machines in your domain.

-matt
Click to expand...

Matt,

If I unregister this dll then run Installshields repackager in two steps re
registering the dll inbetween and build an msi from this it will work?

I have downloaded Installshield Express which will autoscan and detect dll
files but I can't work out how to get it to automatically register the dll.
Or is it the case that it register's all dll's included in the package?

Andy.
 
TerryM said:
Some of the groups you posted to are SMS groups, so can I assume you have
SMS in your environment?

Like you said you can just run that command line but need admin rights, if
that is the case then just use SMS to run the command line with admin
rights.

If you don't have SMS or some other automated deployment tool then I believe
there are free utilities out there that allow you to run command lines on
remote machines using a different set of credentials.

You could use InstallShield or "SMS Installer" to repackage a dll register,
however unless msi's always get elevated in your environment you are going
to run into the admin thing.

You could script the runas as part of the repackaged dll, but that starts to
get complicated because you need to be able to get the password and
everything in there automatically, there are ways to do it but not
completely simple.

You could include a su.exe in your repackaged app which then becomes real
simple to pass credentials and passwords to elevate privileges.

Anyway, lots of options, obviously if you have SMS or some other deployment
tool then your life is a lot easier, because you just tell it the command
line and to use admin rights and then send it out.

Terry
Click to expand...
We use SMS 2003 and although I have used SMS to deploy MSI projects I
haven't yet used it to execute a command line.

If I create a package that contains a program regsvr32 /s path\actxprxy.dll
and advertise it to my clients to be run whever or not a user is logged in
would this be enough?

I am still learning SMS 2003 and the more I use it the more I realise I have
a great deal to learn. It does seem to have superb functionality though.

I cross posted because I thought the solution could come from any number of
the newsgroups I posted too.

Andy.
 
No problem.

Here's a clip from myitforum.com (good resource for sms questions)
You create packages without source files by not selecting the checkbox
entitled 'This package contains source files' when you setup your package
from the Package properties dialog box on the 'Data source' tab. By default
this check box is not checked. This also means that SMS will not use
distribution point severs for the package since there are no source files to
be copied to them.

Then you must set the 'Command line' or 'Start in' options in the 'General'
tab of the package properties dialog box for the application to execute
using up to a maximum of 127 characters. From the 'Command line' text box
you must specify the exact location of the file to be executed and it must
be in the exact location that you specify for each machine in your
advertisement collection or it will fail. There is however one workaround to
this and that is if the call to the executable is in the machines path
statement.

An example of a package without source files would be Windows NT 2000
Professional workstations Net.Exe that exist on all NT 2000 professional
workstations in the same location. You could specify as your command line
'C:\WinNt\System32\Net.Exe' and issuing either 'Net Stop' or 'Net Start'
commands.

Using this method you can run any application that is already located on
your client machines such as .Exe, .Bat, .Cmd even .Wsh or .Vbs scripts
provided they are in the same location or included in the Path statement.

For some things to run though you need to execute through a command window.

so cmd.exe /c "XXX"

Not sure is regsvr32 is like this or if you can just do it directly.

Also for your path you may need "" around it??

I would do some test runs and see how it goes.

Terry
 
TerryM said:
No problem.

Here's a clip from myitforum.com (good resource for sms questions)

You create packages without source files by not selecting the checkbox
entitled 'This package contains source files' when you setup your package
from the Package properties dialog box on the 'Data source' tab. By default
this check box is not checked. This also means that SMS will not use
distribution point severs for the package since there are no source files to
be copied to them.

Then you must set the 'Command line' or 'Start in' options in the 'General'
tab of the package properties dialog box for the application to execute
using up to a maximum of 127 characters. From the 'Command line' text box
you must specify the exact location of the file to be executed and it must
be in the exact location that you specify for each machine in your
advertisement collection or it will fail. There is however one workaround to
this and that is if the call to the executable is in the machines path
statement.

An example of a package without source files would be Windows NT 2000
Professional workstations Net.Exe that exist on all NT 2000 professional
workstations in the same location. You could specify as your command line
'C:\WinNt\System32\Net.Exe' and issuing either 'Net Stop' or 'Net Start'
commands.

Using this method you can run any application that is already located on
your client machines such as .Exe, .Bat, .Cmd even .Wsh or .Vbs scripts
provided they are in the same location or included in the Path statement.


For some things to run though you need to execute through a command window.

so cmd.exe /c "XXX"

Not sure is regsvr32 is like this or if you can just do it directly.

Also for your path you may need "" around it??

I would do some test runs and see how it goes.

Terry
Click to expand...

Terry,

Thanks for the post. I will be testing and implementing this tomorrow so
thanks!

To be honest we have had a increasing problem with ie6 not opening new
windows for some time now (ie before Christmas!). Our systems pc's are all
ok so it's not been a priority. It wasn't until I spoke to a teacher on
Thursday that I realised that it's been driving everybody crazy.

You would have thought someone would have said something!

Andy,.
 
Matt Baldwin said:
You could package it as an MSI, then use group policy to push the
software to the machines in your domain.

-matt
Click to expand...

Matt,

Windows File Protection won't let me re-install actxprxy.dll from my msi so
I am stuck!

Andy.
 
TerryM said:
I think you'll get it, but here's another webpage with some related
stuff.... kind of interesting to read about IE issues:
http://inetexplorer.mvps.org/answers.htm#new_window

Terry

PS - Good luck with your tests.
Click to expand...


Terry,

MSI wouldn't work. I had repackaged actxprxy.dll but Windows file protection
wouldn't let in re-install over the original. Is there a way around this
(for future reference)?

Going to command line route worked a treat! Just checking my adverts.. 431
Received, 1 program error 4,281 Program sucess. (It's on a mandatory shedule
at the moment). Wow that saved me some time. Thank you. Thank you SMS

Andy.
 
Glad it worked for you, that's the best route, I'm glad you have SMS.

As for the windows file protection there are complicated ways around it you
can find on the Internet, however I'm not sure those even work any more with
Windows XP SP2? But usually if it is the same dll, you shouldn't push it
out over the other one anyway. You could've just repackaged the command
line not the dll. But basically you did the command line using SMS anyway
so it works better.

Terry
 
TerryM said:
Glad it worked for you, that's the best route, I'm glad you have SMS.

As for the windows file protection there are complicated ways around it you
can find on the Internet, however I'm not sure those even work any more with
Windows XP SP2? But usually if it is the same dll, you shouldn't push it
out over the other one anyway. You could've just repackaged the command
line not the dll. But basically you did the command line using SMS anyway
so it works better.

Terry
Click to expand...

Ah,
I did think of taking a snapshot, issuing the command line and taking
another snapshot then repackaging that lot but I wasn't confident of it
working. Somehow I thought it would be better if I copied over the dll file
as well.

For anyone finding this thread the syntax that worked for me was regsvr32 /s
actxprxy/dll

Thanks.
Andy.
 
Back
Top