Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
registering a dll on an nt box without logging on to that box
- Thread starter nickt
- Start date
DSI,
If I could add a bit to your idea, I would do this -
regsvr32 C:\winnt\system32\msvbvm60.dll /S
The /S is a silent install so that your user won't see a bunch of Regsrv32 message boxes while they are logging in. Otherwise, this is a very simple and effective method.
- Jeff Marler
(please note, that the page is under construction)
If I could add a bit to your idea, I would do this -
regsvr32 C:\winnt\system32\msvbvm60.dll /S
The /S is a silent install so that your user won't see a bunch of Regsrv32 message boxes while they are logging in. Otherwise, this is a very simple and effective method.
- Jeff Marler
(please note, that the page is under construction)
- Thread starter
- #5
there's 3 problems with having the regsvr32 commands running on logon. 1, the logon script itself requires the dll's (this could be overcome by having 2 consecutive scripts I suppose). 2, the users do not have permission to register dll's, security feature to protect the system. 3, this would lengthen the logon process.
I've played around with the dameware nt utilities as suggested by psychpt earlier but I still have to logon manually to each server in the farm using the RCmd Console which is what I was hoping to avoid in the first place.
I'm wondering if it might be best to write a service to register the dll's when they are updated.
I've played around with the dameware nt utilities as suggested by psychpt earlier but I still have to logon manually to each server in the farm using the RCmd Console which is what I was hoping to avoid in the first place.
I'm wondering if it might be best to write a service to register the dll's when they are updated.
nickt,
Addressing the issues that you brought up (all of which are valid by the way) . . .
1) The logon script requires the DLLS.
This is true . . . I would assume that the DLLs would be placed on a common drive somewhere and the logon script would check to see if the user had the DLLs yet and if not, the DLLs would be downloaded to the local machine and registered.
2) The users do not have permission to register dll's
This is a hard one . . . if your users do not have permission to register DLLs you are almost going to have to have an Admin login to update the files. You mentioned the idea of writing a service . . . this is a very good idea. An NT service could be written to run as a specific user with adequate rights to register DLLs. Otherwise, the users will have to get more rights on their system (I know . . . scary).
3) This would lengthen the logon process
Yeah, this would lengthen the process, but the amount of extra time it would take would only be a couple of seconds unless there are a lot of large number of DLLs that need to be registered. I really don't think that the extra time would be a big deal.
Just a few thoughts on the matter . . . - Jeff Marler
(please note, that the page is under construction)
Addressing the issues that you brought up (all of which are valid by the way) . . .
1) The logon script requires the DLLS.
This is true . . . I would assume that the DLLs would be placed on a common drive somewhere and the logon script would check to see if the user had the DLLs yet and if not, the DLLs would be downloaded to the local machine and registered.
2) The users do not have permission to register dll's
This is a hard one . . . if your users do not have permission to register DLLs you are almost going to have to have an Admin login to update the files. You mentioned the idea of writing a service . . . this is a very good idea. An NT service could be written to run as a specific user with adequate rights to register DLLs. Otherwise, the users will have to get more rights on their system (I know . . . scary).
3) This would lengthen the logon process
Yeah, this would lengthen the process, but the amount of extra time it would take would only be a couple of seconds unless there are a lot of large number of DLLs that need to be registered. I really don't think that the extra time would be a big deal.
Just a few thoughts on the matter . . . - Jeff Marler
(please note, that the page is under construction)
- Thread starter
- #7
Users sit at thin client terminals - it's Windows Terminal Server, sorry if I didn't make that clear. So, they don't need to download the dll's each time (or ever!) but they do need the server to use them when they log on.
I think the service is the way to go but I'm having trouble getting even the simplest service (writing to a text file every 3 secs) to start on my nt workstation machine. The exe actually runs for a bit but the services window hangs and finally the exe stops with an error 2186 : service is not responding to the control function.
What's the easiest way to install a service?
I think the service is the way to go but I'm having trouble getting even the simplest service (writing to a text file every 3 secs) to start on my nt workstation machine. The exe actually runs for a bit but the services window hangs and finally the exe stops with an error 2186 : service is not responding to the control function.
What's the easiest way to install a service?
- Thread starter
- #8
- Status
Similar threads
- Locked
- Question