|
fault -> SMS + Software Distribution to Terminal Servers (9/22/2008 7:22:54 AM)
|
Hey all,
Just wondering whether anyone out there performs software distribution to Terminal Servers? If you do, I have to ask, how do you handle the taboo topic of change user /install & change user /execute?
I've read articles where the author says this isn't strictly required anymore on Windows Server 2003 (with Terminal Services) as it's smart enough to detect when software installation is taking place and automatically switches mode, but I can't find any documentation on this from Microsoft? Others swear by executing the above two commands everytime they perform software installation on a Terminal Server.
We run two Citrix farms specifically and while Citrix offers the Installation Manager, I don't want to use it if we can stick with our SMS deployment.
(I'm not sure how Installation Manager handles the mode switching either. I assume it either has some builtin functionality to do the mode switch prior to and after software installation. Or because it uses Windows Installer (MSIs), it leverages the aforementioned builtin smarts to detect that software installation is taking place and lets Windows handles it? Pure speculation...)
If anyone can shed some light on their knowledge/experience on this topic, that'd be super... :)
Of course, I could just wrap all my packages around a vbscript that does the mode switching for me, but that requires modification to all my packages. Or I could run a program for change user /install prior to assigning my advertisement but running a program for change user /execute after the advertisement is a little tricky? It seems to get very messy/ugly pretty quickly...
|
|
|
|
