For those that may have missed it, it's available here:
http://www.microsoft.com/downloads/details.aspx?FamilyID=7150bfed-64a4-42a4-97a2-07048cca5d23&displaylang=en
Oliver Moazzezi
MVP - Exchange Server
Here are direct links to TechNet in regards to RBAC.
Understanding Role Based Acces Control
Understanding Management Role Groups
Understanding Management Roles
Understanding Management Role Scopes
Understanding Management Role Assignments
Oliver Moazzezi
MVP - Exchange Server
The official Microsoft Exchange Blog has a great article on RBAC. Follow this link here
Oliver Moazzezi
MVP - Exchange Server
Available here: Update Rollup 2 for Exchange Server 2010 resolves issues that were found in Exchange Server 2010 since the software was released. This update rollup is highly recommended for all Exchange Server 2010 customers.
http://www.microsoft.com/downloads/details.aspx?FamilyID=6d3ae3e0-3982-46d6-9e9c-7d7d63fae565&displaylang=en
For a list of changes that are included in this update rollup, see KB979611.
So you fancy administering your Exchange 2010 Org without installing the Exchange Management Tools on your workstation huh? Read on..
First you must ensure you have WinRM and Powershell 2.0 on your workstation. This is present by default in Windows 2008 R2 and Windows 7, however for XP, Vista or Server editions of 2003 or 2008 you can download the required Windows Management Framework install files here.
Once installed fire up Powershell. It doesn't have to be run in Administrator mode for this to work. To make things easy lets cache our credentials
$user = Get-Credential
This binds the credentials we supply to be user later using the $user.
Once that is done we will bind a new session to a variable. I am performing the following over HTTP due to constraints in my lab.
$session = New-PSSession -configurationname microsoft.exchange -connectionuri http://yourcasserver/powershell -credential $user
The above binds the New-PSSession cmdlet with our settings to $session, you can also see we supply our credentials for this using our existing $user variable we have already made.
We can now import the session
Import-PSSession $session
Hopefully by now you will see how we are linking these together :-) we are calling the Import-PSSession cmdlet to our $session variable.
Once you hit return you will see it import the Exchange cmdlets from from Exchange.
We are now done and we have loaded the Exchange 2010 cmdlets.
I can now use them, for example below I have used the Get-Mailbox cmdlet against my test mailbox.
There are two things to note however:
1. If you have any issues with execution policies in Powershell ensure you have set Powershell to allow for remote signed scripts. To check, Get-ExecutionPolicy, to change to remote signed, Set-ExecutionPolicy remoteenabled
2. You must have Remote Powershell enabled for your user, by default this is only enabled for the account that installed Exchange, so to enable it perform the following on one of your Exchange 2010 servers
Set-User -identity youruserhere -RemotePowershellEnabled $true
As most of you know, SIS was de-emphasized in Exchange 2007, being used for attachments only. Exchange 2010 took this further and removed it entirely.
Ross Smith IV has written a very good post on the official Exchange Teams Blog, going all the way back to Exchange 4.0.
You can read it here
Oliver Moazzezi
MVP - Exchange Server
Please join me in this webinar on Hosted Exchange 2010.
For more information please click here:
http://www.cob-blog.com/cobweb/2010/02/what-is-hosted-exchange-2010-httpwwwcobwebcomonline-learningwebinar-what-is-he-2010aspx.html
See you there!
Oliver Moazzezi
MVP - Exchange Server
Following on from the announcement that this web tool is now available. I thought I would go through the steps in upgrading an Exchange 2003 Environment to 2010.
From the first page i select my chosen scenario, to upgrade from Exchange 2003
Once you have chosen your selected scenario you will be presented with questions concerning your environment. You can see here I am asked certain important questions, including, am I planning to support Public Folders? Am i planning to support the Unified Messaging role? and am I planning to move all users at once?
Once you have selected your chosen upgrade path options we can proceed.
You will now see the Navigation checklist page - this can be taken as a general FAQ and contains some well written information to help you on your way.
The first step ExDeploy will start you with is the installation of the Client Access Server role, and then subsequently adding SSL certificates to secure services
It will show you take you through the steps to enable Outlook Anywhere (RPC over HTTPs for those that would be more familiar with this term when coming from Exchange 2003).
I'll move onto the next role, the Hub Transport role, but ExDeploy will carry on with the Client Access Server, helping configure OAB and Web Services directories, including detail on virtual directories.
ExDeploy contains the right amount of detail for deployment, and in some cases showing actual screenshots from the Exchange Management Console
Moving on to the Mailbox Server role. ExDeploy allows you to minimise information, which is a handy feature - just giving you the deployment steps you need for your immediate needs. You can see i have minimised all information here on the steps for installing the Mailbox Server role.
This was being discussed on a private list today and I didn't realise you could use the the Office Admin templates for this very function.
We all appreciate their use in disabling automatic archiving and the use off PSTs so I thought I would echo the post located here, as I see this as another nice 'value add'.
1. Download the admin templates from http://www.microsoft.com/downloads/details.aspxFamilyId=92D8519A-E143-4AEE-8F7A-E4BBAEBA13E7&displaylang=en
2. Extract the templates into a directory
3. Modify the outlk12.adm file with the following changes
Goto line 2459 (KEYNAME Software\Policies\Microsoft\Office\12.0\Outlook\Security
Move the line VALUENAME PromoteErrorsAsWarnings below this line (it should located under VALUEOFF NUMERIC 0 which causes an error when Group Policy reads the file)
Find the line CATEGORY !!L_Disableitemsinuserinterface
Add the following lines immediately after that line (this will add the ability to disable the Reply to All button)
POLICY "Disable command bar buttons and menu items" KEYNAME Software\Policies\Microsoft\Office\12.0\Outlook\DisabledCmdBarItemsList PART "Enter a command bar ID to disable" LISTBOX VALUEPREFIX TCID END PART END POLICY
4. Create a GPO
5. Add the outlk12.adm template
6. Browse to Microsoft Office Outlook 2007\Disable items in user interface
7. Open the Properties for Disable command bar buttons and menu items. Enable this object
Click the Show button and Add 355
UPDATE: Microsoft have a good article on it also. Read it here:
http://msexchangeteam.com/archive/2009/09/29/452689.aspx
