Welcome to TechNet Blogs Sign in | Join | Help

Managing your applications?

If you are an IT administrator who has 25 - 500 PCs I'd like your opinion.  Would you rather manage your applications independently or would you like to be able to manage them in one place?  Said another way, if you had a single console to administer your applications do you see that as a good thing or would you rather "fall out" to the native management console that each application vendor developed? 

One of the benefits of the Windows Server System is that each server application has to meet a certain criteria in order to obtain the WSS logo. BTW, there are serveral Microsoft product groups that use the WSS acronym--in this blog post I'm referring to Windows Server System.  The criteria ensures (99% of the time) that an administrator who purchases a WSS-logoed product will be certain that that app will support a Microsoft Operations Manager management pack, an MMC snap-in, Virtual Server, etc.  What do you think of that level of integration?  You don't have to comment when feature "x" is missing from WSS app y".  I hear you and empathize with your frustration when a piece of integration is missing (fortunately, that happens less and less as the criteria bar is raised).

Published Tuesday, October 25, 2005 2:59 PM by Kentc
Filed under:

Comments

# re: Managing your applications?

I would love to manage all of my applications from a single mmc. I've been trying to use group policies for this but it is still very difficult; especially when I have to repackage the setup.exe into a .msi. M.O.M. is beyond my budget.

I would love to be able to push, monitor, update, and remove apps. It would be wonderful if I could store multiple setup configs for an app and choose one to push to a specific user (IE one user gets a full install, the other user gets a minimal). I'd love to be able to input multiple product keys for a single app into this MMC and have the tool automatically use a product key for the install. In essence, for installs; I'd love to do the inital setup and then just push a button to install app X on system Y.

Then I'd like to be able to monitor the application's usage frequency. I could tell that the user worked with the app heavily for 3 months and hasn't touched it since. This would allow me to make decisions on where to remove the app so that I can reuse the product key elsewhere. Removing would feed the product key back into the MMC as "available" so that I could push it back out.

Patch management in this MMC would be awesome.

One use model that I have imagined for this would be to install the application "to" the mmc; instead of setting up the installation files in some network share as I do with group policies. Then whenever a patch releases for that product, I could install the patch into the "Microsoft Application Management Console" and the tool would automagically update the applications based on update rules (who get's what update when). I want the install files to be completely hidden from the users (no network shares) so that they can't dig around and end up installing the app on their own.

Merely having this functionality for Microsoft Office would save me significant volumes of time and effort.

FYI: I'm supporting 50 users and 75 PC's.
Tuesday, October 25, 2005 7:23 PM by Christopher

# re: Managing your applications?

Also; having this would put a serious nail in the Linux coffin. I now have Linux on 9 desktops and 3 servers.
Wednesday, October 26, 2005 5:20 PM by Christopher

# re: Managing your applications?

Christopher, thank you very much for your suggestions. Regarding your comment about MOM being too expensive, have you looked at MOM Workgroup Edition (http://www.microsoft.com/mom/workgroup/evaluation/overview.mspx)? I work closely with that team and they specifically created that SKU so customers in mid-size businesses could afford to run MOM.
Friday, October 28, 2005 3:55 PM by Kentc
Anonymous comments are disabled
 
Page view tracker