Install and register a .dll that doesn´t exist
If it is possible I would like some help with a script that
installs and register a dll-file. This would be really easy
if I had the actual dll file. But the dll will be finished and placed
on a share at friday when I have my day off.
I know what the name of the dll file will be and I know which share
it will be placed on. I have created a collection in SMS for the machines
that should get this file.
I would like help with a bat or cmd file that does the following
1. Copy the dll-file from the share.
2. Install and register it under %Systemroot%\system32 on
the machines in my collection.
/Nick
installs and register a dll-file. This would be really easy
if I had the actual dll file. But the dll will be finished and placed
on a share at friday when I have my day off.
I know what the name of the dll file will be and I know which share
it will be placed on. I have created a collection in SMS for the machines
that should get this file.
I would like help with a bat or cmd file that does the following
1. Copy the dll-file from the share.
2. Install and register it under %Systemroot%\system32 on
the machines in my collection.
/Nick
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
Jamie B
15 years ago
In it's simplest form create a batch file like so and place it in same folder as the dll. Launch the batch file from an SMS program via an advertisment linked to your collection.
copy /y YOURDLL.dll %SystemRoot%\system32\YOURDLL.dll
%SystemRoot%\system32\regsvr32.exe /s %SystemRoot%\system32\YOURDLL.dll
Dont forget to add your your own error checking to the script to make it more robust in a production environment.
A better method would be to create an MSI but without the dll itself you wont be able to extract the registration information.
copy /y YOURDLL.dll %SystemRoot%\system32\YOURDLL.dll
%SystemRoot%\system32\regsvr32.exe /s %SystemRoot%\system32\YOURDLL.dll
Dont forget to add your your own error checking to the script to make it more robust in a production environment.
A better method would be to create an MSI but without the dll itself you wont be able to extract the registration information.
Posted by:
anonymous_9363
15 years ago
A better method would be to create an MSI but without the dll itself you wont be able to extract the registration information.Presumably, if the file is going to be dropped to a share, it's being developed internally? If so, the developer can provide all the COM information you need. He/she *must* have a development version and, unless he/she is particularly dumb, that information won't change. It may be added to, but that constitutes a new release in my book and therefore requires a new package or an update.
Posted by:
Nixlas
15 years ago
Thanks for your help. I managed to get the DLL today so
I could deploy it in a MSI-file.
I could deploy it in a MSI-file.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.