The new forums will be named Coin Return (based on the most recent vote)! You can check on the status and timeline of the transition to the new forums here.
The Guiding Principles and New Rules document is now in effect.
Once you have that exe package then it's the software distribution time. I have had issues with bighuge apps via AD (office, I'm looking at you) but most stuff works ok. http://support.microsoft.com/kb/816102
Although if you have SMS/SCM or some other software for patches you could use that as well. Or log in scripts.
Posts
That's the easy part, the hard part is the actual process of pushing it out. How do I do that, exactly?
Once you have that exe package then it's the software distribution time. I have had issues with bighuge apps via AD (office, I'm looking at you) but most stuff works ok.
http://support.microsoft.com/kb/816102
Although if you have SMS/SCM or some other software for patches you could use that as well. Or log in scripts.
Add regsvr32 <dllname> to the log on script and call it a day. Might need runas if the dudes aren't local admins.
net use w: \\server\dllpath
regsvr32 /s DLL.DLL (might need runas here)
net use w: \\server\dllpath /delete
You probably don't need to runas, I think logon scripted actions already run as SYSTEM processes.
[edit] Nope, I was wrong, logon/logoff script run with User credentials, Startup and Shutdown scripts run with Computer object credentials.