Archive for the ‘Exchange 2010’ Category

Marc Lognoul's IT Infrastructure Blog

Having recently dealt with MS Exchange vs. Firewall and flows issues, I thought it might be interesting to post a summary of useful links related to network ports and flows used by Exchange and various clients . Bottom line: Exchange and firewalls ain’t no good friends but you already knew hat don’t you?

Clients and Mailflows

Unified Messaging

Hybrid Deployments

Other Resources

View original post

Working Hard In IT

Introduction

In vNext we have gotten a long awaited & very welcome new capability: rolling cluster upgrades. Which for the Hyper-V roles is a 100% zero down time experience. The only step that will require some down time is the upgrade of the virtual machine configuration files to vNext (version 5 to 6) as the VM has to be shut down for this.

How to

The process for a rolling upgrade is so straight forward I’ll just give you a quick bullet list of the first part of the process:

  • Evacuate the workload from the cluster node you’re going to upgrade
  • Evict the node to upgrade to vNext from the cluster
  • Upgrade (no in place upgrade supported but in your lab you can get away with it)
  • Add the upgraded node to the cluster
  • Rinse & repeat until all nodes have been upgraded (that can take a while with larger…

View original post 376 more words

Hi Folks,

today’s challenge was to bulk set calendar rights in a multilingual environment (with powershell).
On the net you can find some articles that address similar problems, but no real solution.

Download the follwing scripts as txt here.

Here my quick an dirty script:

# Set default as LimitedDetails for all calendars.
# Will get the language forch each users calendar Folder
# TEST WITH ONE ORE MORE USERS
# foreach($mbx in Get-Mailbox -identity USER | where-object {$_.displayname -like "*test user*"})


foreach($mbx in Get-Mailbox -ResultSize Unlimited | where-object {$_.displayname -notmatch "discovery"})

{
$Calfolder = $Mbx.Name
$Calfolder += ':\'
$CalFolder += [string](Get-mailboxfolderstatistics $Mbx -folderscope calendar).Name
$mbx = $CalFolder
$test = Get-MailboxFolderPermission -Identity $mbx -erroraction silentlycontinue
if($test -ne $null)
{
Set-MailboxFolderPermission -Identity $mbx -User Default -AccessRights LimitedDetails | out-null
}
}

If you want to create all new mailboxes with special permissions you nee to configure the Cmdlet Extension Agent
To enable the agent this you have to the following steps:

  • Create an XML file named ScriptingAgentConfig.xml  and save it in your Exchange’s Default Directory on EVERY Exchange Server in your organization
    e.g. C:\Program Files\Microsoft\Exchange Server\V15\Bin\CmdletExtensionAgents

    <?xml version=”1.0″ encoding=”utf-8″ ?>
    <Configuration version=”1.0″>

    <Feature Name=”MailboxProvisioning” Cmdlets=”New-Mailbox”>
    <ApiCall Name=”OnComplete”>
    if($succeeded)
    {
    start-sleep -s 10
    $mbx =  (Get-User $provisioningHandler.UserSpecifiedParameters[“Name”]).distinguishedName
    Set-MailboxFolderPermission -Identity $mbx”:\Calendar” -User “Default” -AccessRights LimitedDetails
    }
    </ApiCall>
    </Feature>

    <Feature Name=”MailboxProvisioning” Cmdlets=”Enable-Mailbox”>
    <ApiCall Name=”OnComplete”>
    if($succeeded)
    {
    start-sleep -s 5
    $user = Get-User -Identity $provisioningHandler.UserSpecifiedParameters[“Identity”]
    $mbx = Get-Mailbox -Identity $user.DistinguishedName
    Set-MailboxFolderPermission -Identity $mbx”:\Calendar” -User “Default” -AccessRights LimitedDetails
    }
    </ApiCall>
    </Feature>

    </Configuration>

 

  • Use the Exchange Management Shell and run the following command on EVERY Exchange server in your organization:
    Enable-CmdletExtensionAgent “Scripting Agent”
  • Create new user

Cheers,

Chris

Hey folks,

in the following post I want to give you a list of alternative solutions for the safe publishing of exchange (some with pre-auth):

KEMP Edge Security Pack
http://kemptechnologies.com/de/tmg-edge-security-authentication

Barracuda ADC
https://techlib.barracuda.com/adc/msx2013deploy

CITRIX Netscaler
http://blogs.citrix.com/2013/12/19/tmg-replacement-for-exchange-2013-with-netscaler/

SOPHOS UTM
http://www.sophos.com/en-us/products/unified/utm/tmg-replacement.aspx

Microsoft WAP
http://blogs.technet.com/b/jrosen/archive/2013/12/28/setting-up-windows-application-proxy-for-exchange-2013.aspx

Cheers,

Chris

 

 

Patrick's Blog

Recently after setting up a second Exchange 2010 server I had an issue where Public Folder replicas were not replicating. When running the following cmdlet it showed the replicas as being configured but they never showed up on the second server.

I didn’t get any errors when configuring the replicas. I even set the Diagnostic Logging Level on certain services under MSExchangeIS9001 Public to Expert but still nothing.

After a few days of dead ends on the Internet I was reminded about ExFolders. So I downloaded it & tried to run it but got an error that says, “An error occurred while trying to establish a connection to the Exchange server. Exception: The Active Directory user wasn’t found.” Finally an error I can search for. I quickly came across this site.

I opened ADSIEdit & connected to the Configuration partition. I deleted the empty CN=Servers container from the old administrative…

View original post 70 more words

JAMIE MCKILLOP

UPDATE: Version 2.1 is available. For details, click here.

The Exchange tracking logs provide a wealth of information about mail flow through your organization. Unfortunately, the tools that ship with Exchange aren’t very good at leveraging this information in a useful way. You can use the message tracking tool that ships with EMC to search for specific logs but beyond viewing the raw log data, there isn’t much information available. Fortunately, Microsoft has provided us with powershell and powershell can be used in all sorts of interesting ways to gather, aggregate and present data in useful summaries and reports.

One of the great things about powershell and the IT community is that there are plenty of people who have built powershell scripts to solve problems, automate or streamline tasks, and gather and present data. Most people are more than happy to share their scripts with anyone who would like…

View original post 1,095 more words