FN-GM Posted July 28, 2008 Posted July 28, 2008 Is it possible to register a .dll file using Server 2008 group policy? Thanks Z
mac_shinobi Posted July 29, 2008 Posted July 29, 2008 use a vbscript to execute / launch the regsvr32 command using the silent switch to register the dll on either a startup or logon script ?
ahuxham Posted July 29, 2008 Posted July 29, 2008 regsvr32 /s name.dll in the login script, after about a week, you could assume its run everywhere and remove it. DLL needs to either be copied into system32 folders, or placed in NETLOGON folder, or use a UNC path.
FN-GM Posted July 29, 2008 Author Posted July 29, 2008 I alredy use a script, but i would like to move away from them thats why i am asking if i can use group policy.
maniac Posted July 29, 2008 Posted July 29, 2008 Group policies can generally only apply registry changes to a machine (and do things like run scripts etc) I think there's a more than just a registry change when a DLL is registered on a machine so I think a script is your only option AFAIK. However instead of calling a script, you could probably put the regsvr32 command directly into the startup or login script box within group policy, that would save it calling a batchfile, and run it directly. I think this would work. Mike.
ahuxham Posted July 29, 2008 Posted July 29, 2008 After a google or two, I found various posts within Microsoft Technet, and this functionability is not possible. As said above, scripts are the way forward
azrael78 Posted July 29, 2008 Posted July 29, 2008 It's worth noting that with DLL registration you IDEALLY want to copy the DLL from a central point first (NETLOGON share) and THEN register it. So something like the following: Copy %LOGONSERVER%\NETLOGON\MyDLL.DLL %WINDIR%\System32 /Y %WINDIR%\system32\regsvr32.exe /s %WINDIR%\system32\MyDLL.DLL That way - your DLL is always the same version on every PC (when you initially copy and register it - assuming nothing updates it later). While you can simply register a DLL in NETLOGON directly, I've seen a few nasties when NETLOGON hasn't been available and that DLL was needed... better to be safe than sorry IMO Your absolute best-bet is to run this as a PC Startup Script (which runs as NT AUTHORITY\SYSTEM) - so it registers it before your users even login, which is great if said DLL is needed at login time or desktop-creation time HTH Az
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now