By BoonTee,on December 6th,2011% The Microsoft Online Portal is a wealth of information,but now easy to navigate. Here is a direct link to the help page where you can find information on how to set up Outlook,setting up your iPhone for Office 365 and many other articles. http://onlinehelp.microsoft.com/en-us/office365-enterprises/ff637580.aspx The Getting Started page is a very good place to start! By BoonTee,on June 3rd,2011% By BoonTee,on May 24th,2011% There is a great 31 part blog post on PowerShell that is in developement (part 23 of 31 at this moment). Everything you wanted to know about PowerShell and some great scripts that can be used. The main landing page for the blog is here –http://blogs.technet.com/b/matthewms/p/powershell.aspx Here are the titles. Part 1 of 31:Why PowerShell? Part 2 of 31:The Basics on How to Read PowerShell Part 3 of 31:Where Did All the Good Cmdlets Go? Part 4 of 31:Who Ya Gonna Call For Help? Part 5 of 31:What’s in it for Devs? Part 6 of 31:A Cmdlet By Any Other Name Would Be An Alias Part 7 of 31:Conjunction Function PowerShell What Are Functions? Part 8 of 31:Won’t You Take Me To Functiontown? Part 9 of 31:Another Side of PowerShell Profiles Part 10 of 31:PowerShell Protecting You From Yourself Part 11 of 31:PowerShell Providers and You! Part 12 of 31:PowerShell and The Registry Part 13 of 31:The Provider Active Directory Style Part 14 of 31:Sorry I’m Not Home Right Now,Walking into IIS Webs… Part 15 of 31:ISE,ISE Baby… Part 16 of 31:PowerShell Take Me Out To The Grid Part 17 of 31:Who Wants to Manage Active Directory? Part 18 of 31:So You Deleted A User…On Purpose Part 19 of 31:Small Business Server,PowerShell,and Me Part 20 of 31:Hanging with Hyper-V Part 21 of 31:Knock Knock PowerShell Calling! Part 22 of 31:Good PowerShell Things Come in Nifty Packages Part 23 of 31:HUGE Announcements,Disagreements,Best Practices and A Party…Oh My! Part 24 of 31:PowerShell Did What!?!? How to Mitigate Risk! Part 25 of 31:Did You Know PowerShell Can Talk VMware? Part 26 of 31:Start Spreading the News… Part 27 of 31:It Takes a Community to Raise a Language Part 28 of 31:What is the .NET Framework? Part 29 of 31:Demystifying MSDN and PowerShell static syntax Part 30 of 31:PowerShell Likes the Pretty Blue Eyes of Azure Too Part 31 of 31:That’s a Wrap and We are Not Done Yet! By BoonTee,on January 7th,2011% Here are a couple of scripts to check the size of the Exchange Stores. With the 75GB limit in Exchange 2003 and possible personal store located in various areas for Exchange 2007 and beyond,it is useful to have a quick overall glance at the Exchange information all at a go. For Exchange 2003 and below,you can use Michael B Smith’s (Exchange MVP) scripts found here –http://theessentialexchange.com/blogs/michael/archive/2007/11/13/finding-disk-space-used-by-exchange.aspx. For a self installing version of this script,you can download it here –http://www.petri.co.il/reporting_storage_size_in_exchange.htm In Exchange 2007,the STM file was elimited according to Michael,and so the script terminates with an AD error. He has supplied a really quick and dirty Exchange PowerShell script to output the sizes of the stores. Cut and past the following code into notepad and save the file with a .PS1 extension and run this from the Exchange Management Shell. $totalArray = @()$totalArray += get-mailboxdatabase -ea 0 |%{dir -ea 0 $_.EdbFilePath | select Name,Length }$totalArray += get-publicfolderdatabase -ea 0 |%{dir -ea 0 $_.EdbFilePath | select Name,Length }$totalArray | out-string -width 70[int64]$totalSize = 0$totalArray |%{$totalSize += $_.Length }"Total size of databases{0} bytes,{1} GB" -f $totalSize.ToString("N0"),($totalsize / 1GB).ToString("N3")There are many other scripts out there,which can produce nicely formatted output and possibly more information if required. But I found that this gave me the information I needed quickly. UPDATE 8/1/2011:Michael has updated his script to work with Exchange 2007 and 2010. You can access the script here –http://theessentialexchange.com/blogs/michael/archive/2011/01/07/finding-disk-space-used-by-exchange-v2.aspx Michael’s blog contains a depth of great articles and scripts on everything about Exchange - www.TheEssentialExchange.com By BoonTee,on October 18th,2010% Sometimes,it is necessary to create a custom template for allocating email addresses to users based on certain criteria. In SBS2008,this is relatively easy to do via the Recipient Policy Wizard in the Exchange Management Console. In SBS2003,this is not easily found. Microsoft KB 822447 Article documents how to do this -http://support.microsoft.com/kb/822447 You can create and edit Recipient Policies in the Exchange System Manager,Recipients,Recipient Policies. - Create a new policy or double-click an existing one to existing one.
- In the E-Mail Addresses (Policy) tab,click New to create a new policy rule/template.
- The following wildcards can be used:
- %s:Surname (last name)
- %g:Given name (first name)
- %i:Middle initial
- %d:Display name
- %m:Exchange 2003 alias
- %rxy:Replace all subsequent characters x with character y in username. If x = y,the character will be deleted.
For more information,refer to examples from the KB article. By BoonTee,on August 23rd,2010% In Exchange 2003,Administrator accounts are denied access to mailboxes. As such,the EXMERGE utility will fail to export mailboxes when run using the Administrator account. To enable the Administrator account to use EXMERGE for exporting user mailboxes in archival situations,the following fix must be applied. Open Server Management,browse to Advanced Management,First Organization (Exhcange),Servers,[servername] Right Click on the server name,and select properties. Select the Security Tab,and click the Advanced Button. Untick the Check Box,Select Copy. Then select all Deny Permission Types,and click Remove. EXMERGE should now run properly. By BoonTee,on April 20th,2010% On many of my early installations of SBS2008,I had the unfortunate situation of not allocating enough hard drive space on the C:drive. My opinion has always been to move data and other system information out of the C:drive to other drives,and keeping the C:drive to a reasonably small size. I though that size was 60GB. I was wrong. I would recommend setting the C:drive to at least 80GB or more. However,if you do have a 60GB partition on the C:drive,one of the first signs of trouble is when the free space on C:drops below 2GB. Exchange 2007 stops receiving external emails. This is caused by a condition known as Back Pressure. This is described in more detail here – http://technet.microsoft.com/en-us/library/bb201658(EXCHG.80).aspx The easiest way to remedy this situation is to immediately free up disk space. Fortunately,there are some great articles on how to do this. Other things,which should have already been done via the SBS Console is moving the Exchange database,Windows Update Repository and Sharepoint database out of the C:drive. They can be found here. By BoonTee,on March 19th,2010% I received an email from a client a few days ago. “Does the server have a limit on the size of emails it will accept? I seem to recall a 5mb limit. Can I ask that we review this in the light of modern ways of doing things whereby we send large files,audio and video,via email?”
For many organizations,a limit is imposed on attachments in emails to “save bandwidth”since data is counted for broadband in Australia. I found an excellent blog which listed the various places to look at when making changes to enable attachments beyond the default 10MB limit which is set in SBS2008. All these options are located in the Exchange Management Console. 1. Setting Organizational Limits. This affects the global settings. In an organization with multiple servers,this will affect all servers. Open up properties for Transport settings as shown. Change the settings as required. 2. Setting Receive Connector limit. This affects incoming messages received by the server. Change the desired Receive Connector properties. a. Default SBS –For internal client connections b. Windows SBS Internet Receive SBS –For incoming emails outside the network 3. Send Connector limit. This setting affects outgoing emails. Edit the settings for the Windows SBS Internet Send SBS connector. 4. Mailbox limit. Finally,if you really want to,you can set a user to have additional settings,different to the organizational limits. Note that this only affects internal messages. not external incoming or outgoing messages. Change the properties for the Message Size Restrictions (which is not set by default). By BoonTee,on November 24th,2009% The Microsoft Public Folder Distributed Authoring and Versioning (DAV)-based Administration tool –PFDavAdmin is a great utility to use when working,especially with mailbox permissions,whether they be user mailboxes or Public Folders. With this tool,one can do a mass update of all permissions set in any folder in Exchange. Content information like number of items in folders can be reported. The description from Microsoft is as follows: Use the Exchange Server Public Folder Distributed Authoring and Versioning (DAV)-based Administration tool (PFDAVAdmin) to perform various management tasks related to public folders and mailboxes. The tool checks the permissions status of each public and mailbox folder and corrects any problems found. The ability to bulk export/import the permissions and replica lists make this tool invaluable in achieving greater productivity in managing public folders. The program can also reports content information of each public folder and mailbox folder such as the number of items in each folder,size of folder and most recent modification date of any item in the folder. Note:PFDAVAdmin is supported when running with Exchange 2000 Server,Exchange Server 2003 and Exchange Server 2007. NEW: Microsoft have just release a new version of PFDAVAdmin which fully works with Exchange 2007. Thi can be downloaded in the link above,which has been updated. By BoonTee,on September 21st,2009% This has cropped up a few times at different sites over the past few weeks,so I thought I would post it here for quick reference. Exchange mailbox stores were shutting down on a daily basis. This was affecting iPhone,which apparently “wipe out”the data (i think the data becomes unavailable),when there is no connection to the Exchange server. To workaround this,switch of the “push”action for email collection on the iPhone. This will also significantly increase the battery life if you nromally receive a lot of emails. To increase the size of the Exchange mailbox store from it’s default of 18GB,do the following. For a mailbox store,go to the following key in the registry: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSExchangeIS\Server name\Private-Mailbox Store GUID For a public folder store,go to the following key in the registry: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSExchangeIS\Server name\Public-Public Store GUID Create a New DWORD Value,“Database Size Limit in Gb” and set it between 1 to 75 as required. The default is 18 (of course). Restart the MS Exchange Information Store service. | |
Recent Comments