I'm working on a scripted tool for managing mailboxes and public olders that will give a simplified GUI front end to help desk personnel. Managment does not want me to install the Exchange Management Console on the help desk PCs. I need to ONLY install the Exchange Management Shell. I know that from a normal PowerShell window I can execute "Add-pssnapin *.Exchange*" and can then execute my Exchange commands. What I would like to know is what specific files at minimum need to be installed on a new client PC to be able to invoke that command and have it succeed? Which DLLs are needed? Thank you.

Per my knowledge, the minimum needs would be the exchange management tools package, so we cant only install the exchange management shell on a workstation

Yes, I agree with James Management Tools required to run EMS for Exchange 2007. However in Exchange 2010 you will be able to do so with Windows Remote Management (WinRM 2.0) and PowerShell 2.0 which allow you to get a session of Exchange Management Shell from Exchange Server to local machinewithout installation of Exchange Management tools on 32-bit/62-bit of workstations. Amit Tank | MVP Exchange Server | MCITP: EMA | MCSA: M | http://ExchangeShare.WordPress.com

hi,an addition to Amit and James ;How to Install the Exchange 2007 Management Tools:http://technet.microsoft.com/en-us/library/bb232090.aspxregards,Mumin CICEK | Exchange - MVP | www.cozumpark.com | www.mumincicek.com

You guys don't seem to be following me. I've installed the Exchange 2007 Management Tools on my own system, but that does not give you the option to deselect the Management Console, otherwise I would have created a transform for the MSI. I need to be able to only install the Managment Shell.Idealy I would like to be able to copy whatever files are needed from my installation over to another PC so that the Shell will work but the client won't have the console.I had suggested to my customer we could run the tools installation and simply delete the EMC MSC file, however they said that would not be permitted because it would put the entire tools set in the Add/Remove programs list where a repair could be done.It should be possible via file copies and REGSVR32 to duplicate the setup with just the Shell. I can export and import whatever registry keys are needed as well but I need to know what those are.

Based on your description, I think what you want is to keep only the exchange management shell on the workstation and remove all other tools in the Exchange 2007 Management Tools. Am I corrected? Per my knowledge, we shall see the Exchange 2007 Management Tools package as a single unit instead of a collection of tools, which shall not be torn into parts We can only make sure that helpdesk cant use exchange management console (Verified in the lab) Method: Set Permissions on the Properties of Exchange Management Console file, make sure that the user must have local administrator permission in order to execute the file, and then ensure the helpdesk didnt have the administrator permission The helpdesk will get the following error info if they try to use the EMC: MMC cannot open the file This may be because This may also be because you do not have sufficient access rights to the file

Yes, agree with James on Management Tool package and setting permission on MMC. Since default installation package contain both EMC & EMS but your need is to have only EMS, in that case you may need to build your own custom MSI installer package with help of setup/installer package experts to have just EMS to be installed and remove EMC mmc from being installed/copied. An example KB is here... How to create a third-party Microsoft Installer package http://support.microsoft.com/kb/257718Amit Tank | MVP Exchange Server | MCITP: EMA | MCSA: M | http://ExchangeShare.WordPress.com

I appreciate everyone's input. Thank you. Regretfully none of this will work. This project is for a local government and due to the structure, the help desk people are domain admins for their individual domains. They do not however control Exchange which is centralized. Management has been insistent that we cannot install software and then remove parts. So installing the management tools and then removing the MSC is not an option. Blocking access to the MSC is not realistic because the users are admins of their machines and of the domain. It is for this reason that I wanted to be able to just copy the snapin files to another system and be able to register them. Yesterday I found http://msdn.microsoft.com/en-us/library/ms714644(VS.85).aspx which does go into how you can use INSTALLUTIL to install a snapin DLL. So I tried to do the following: set-alias installutil $env:windir\Microsoft.NET\Framework\v2.0.50727\installutilinstallutil Microsoft.Exchange.Management.Powershell.Support.dllAdd-pssnapin *.exchange* However an entry point cannot be found when trying to install the Microsoft.Exchange.Management.Powershell.Support.dll. I am really surprised that Microsoft has put so little effort into the managment tools that you can't select which options to install. I would think that there would be a lot of reverse situations where companies might not want to give someone Shell access for fear they would mess things up. It would regretably appear that this just isn't going to be possible for me to do, so I am altering my process. I'll have my tool create PS1 files on a server share and will then have the server execute the PS1 files locally. That will bypass the need to have the Shell on the local admins workstation.

"They do not however control Exchange which is centralized."Then why do you want to install the Exchange Management Shell?

I wanted to install it so I could use an encrypted script to run the Exchange Shell with elevated credentials. My tool will construct the commands and then execute them as a user with rights.

Don't despair:See my post: "Preparing your system to manage Exchange with Powershell via ASP" http://powershellcommunity.org/Forums/tabid/54/forumid/3/postid/524/view/topic/Default.aspx OLD Samples of my ASP pages are here:Samples of mailbox ASP web scriptshttp://powershellcommunity.org/Forums/tabid/54/aff/3/aft/2509/afv/topic/Default.aspx