Wednesday, 5 June 2013

Windows Server 2012 R2

According to the Microsoft Corporate vice president Brad Anderson, "Windows Server 2012 R2 will be available for preview in June and will be officially released before the end of the year [2013].

Windows Server 2012 R2 Storage Improvements:


  • Automated Storage tiering: Storage in windows server 2012 can be configured to allocate workloads to the most appropriate storage types. For example, you can configure SSD drives to be prioritized for applications and workloads were speed and latency are vitally important, and to rely on slower types of storage for less important workloads.
  • "Generation 2" virtual machines: Windows Server 2012 R2 Hyper-V introduces what Microsoft is calling "Generation 2" virtual machines. Gen 2 VMs only support the 64-bit versions of Windows 8 and Windows Server 2012 R2 as guest OSes. Gen 2 VMs remove all of the legacy, BIOS-based functionality of traditional VMs. These VMs are UEFI-based, have no emulated devices, can boot off virtual iSCSI and network adapters, and support secure boot. The benefits to using Gen 2 VMs could be numerous, including the potential of vastly reduced VM sizes by eliminating support for legacy, BIOS-based overhead. Traditional "generation 1" virtual machines will still be enabled by default.
  • Hyper-V Recovery Manager: According to Woolsey, Hyper-V Replica has proven to be one of the most popular features of Windows Server 2012, so Windows Server 2012 R2 introduces the Hyper-V Recovery Manager, a new centralized management console that allows you to manage site replication.

Tuesday, 4 June 2013

Checking which role can run a specific cmdlets


Below command is to find which role has the permissions to run the cmdlet "Get-ActiveSyncDevice" & "Remove-ActiveSyncDevice"

[PS] C:\Windows\system32>Get-ManagementRoleEntry "*\get-activesyncdevice"

Name                           Role                      Parameters
----                           ----                      ----------
Get-ActiveSyncDevice           MyBaseOptions             {ErrorAction, ErrorVariable, Identity, Mailbox, OutBuffer, OutVariable, SortBy, WarningA
Get-ActiveSyncDevice           View-Only Recipients      {Debug, DomainController, ErrorAction, ErrorVariable, Filter, Identity, Mailbox, Organiz
Get-ActiveSyncDevice           User Options              {Debug, DomainController, ErrorAction, ErrorVariable, Filter, Identity, Mailbox, Organiz
Get-ActiveSyncDevice           Mail Recipients           {Debug, DomainController, ErrorAction, ErrorVariable, Filter, Identity, Mailbox, Organiz


[PS] C:\Windows\system32>Get-ManagementRoleEntry "*\remove-activesyncdevice"

Name                           Role                      Parameters
----                           ----                      ----------
Remove-ActiveSyncDevice        MyBaseOptions             {ErrorAction, ErrorVariable, Identity, OutBuffer, OutVariable, WarningAction, WarningVar
Remove-ActiveSyncDevice        User Options              {Confirm, Debug, DomainController, ErrorAction, ErrorVariable, Identity, OutBuffer, OutV
Remove-ActiveSyncDevice        Mail Recipients           {Confirm, Debug, DomainController, ErrorAction, ErrorVariable, Identity, OutBuffer, OutV

Purging Old Quarantine Devices from Exchange Server for a Particular OU

In order to get the list of users who are in Quarantine State for more than a month for a particular OU

Get-ActiveSyncDevice | Where {$_.UserDisplayName -match "Domain.com/OU" -and $_.DeviceAccessState -eq "Quarantined" -and $_.FirstSyncTime -lt (Get-Date).AddMonths(-1)} | ft UserDisplayName, DeviceModel, FirstSyncTime, DeviceAccessState, DeviceAccessStateReason -Auto

To Purge the list of users after running the above command, you need to pipe Remove-ActiveSyncDevice

Get-ActiveSyncDevice | Where {$_.UserDisplayName -match "Domain.com/OU" -and $_.DeviceAccessState -eq "Quarantined" -and $_.FirstSyncTime -lt (Get-Date).AddMonths(-1)} | Remove-ActiveSyncDevice -Confirm:$false

Friday, 31 May 2013

Update Rollup 1 for Exchange Server 2010 SP3

The Exchange Team released the Update Rollup 1 for Exchange 2010 SP3 (KB 2803727)

Post SP3 upgrade, a no. of issues were reported and this update fixes those along with the internally found issues, following fixes are included in this release:

2561346 Mailbox storage limit error when a delegate uses the manager's mailbox to send an email message in an Exchange Server 2010 environment
2729954 Can't send voice message to a selected non-primary email address in an Exchange Server 2010 environment
2750846 Information Store service crashes when you mount public folder databases on an Exchange Server 2010 server
2751628 Event ID 9682 does not record the folder name when you delete a public folder in an Exchange Server 2010 environment
2756460 You cannot open a mailbox that is located in a different site by using Outlook Anywhere in an Exchange Server 2010 environment
2763065 Move request log is logged when you move a mailbox in an Exchange Server 2010 SP2 environment
2777742 Address Book service crashes on an Exchange Server 2010 Client Access server when a server has been running for 25 days or more
2781488 RPC_S_SERVER_UNAVAILABLE (0x6BA) error code when you use a MAPI or CDO-based application in an Exchange Server 2010 environment
2782683 Email message that a user sends by using the "Send As" or "Send On Behalf" permission is saved only in the Sent Items folder of the sender in an Exchange Server 2010 environment
2784210 Ethical wall does not function as expected when the ReportToOriginatorEnabled property is disabled in an Exchange Server 2003 and Exchange Server 2010 coexistence environment
2793348 Read receipt is sent unexpectedly when you view an email message by using Outlook Web App
2796490 Microsoft Exchange Information Store service crashes on an Exchange Server 2010 Mailbox server
2802569 Mailbox synchronization fails on an Exchange ActiveSync device in an Exchange Server 2010 environment
2803132 Delayed email message delivery on a BlackBerry mobile device after you install Update Rollup 4 for Exchange Server 2010 SP2
2806602 EdgeTransport.exe process crashes on an Exchange Server 2010 Hub Transport server
2814723 Server loses network connectivity and UDP ports are used up on an Exchange Server 2010 server
2814847 Rapid growth in transaction logs, CPU use, and memory consumption in Exchange Server 2010 when a user syncs a mailbox by using an iOS 6.1 or 6.1.1-based device
2816934 Error code 0X800CCC13 when an additional POP3 or IMAP account is used to send an email message and Outlook online mode is used to connect to an Exchange Server 2010 environment
2817140 Exchange Replication service crashes intermittently in an Exchange Server 2010 environment
2817852 Cyrillic characters are displayed as question marks in the "To" field of message items in the Sent Items folder in an Exchange 2010 environment
2818456 Attachments are missing from an embedded message in an Exchange Server 2010 SP2 environment
2822208 Unable to soft delete some messages after installing Exchange 2010 SP2 RU6 or SP3
2826066 VSAPI-based antivirus software causes delayed response in an Exchange Server 2010 environment
2827037 Copy of an item is created in the Version subfolder in an Exchange Server 2010 environment
2833888 No items are displayed in Outlook after you install Exchange Server 2010 SP3 or Update Rollup 6 for Exchange Server 2010 SP2
2840099 ArgumentOutOfRangeException exception when an EWS application creates a new MIME email in an Exchange Server 2010 environment


This update is available for download at Download Center.

Wednesday, 22 May 2013

GFE NOC Maintenance Successfully Completed


The scheduled maintenance to the GFE NOC (Network Operations Center) was
successfully completed.

All end-user services, including message flow, resumed at approximately
10:15 PM PT Saturday May 18 / 5:15 AM GMT Sunday May 19 (15 minutes after
the start of maintenance) and have been operating normally since that
time.

The GMP was back in service at approximately 1:40 AM PT Sunday May 19 /
8:40 AM GMT Sunday May 19

Saturday, 4 May 2013

Planned GFE NOC Maintenance on May 18


Good Technology will be undertaking planned Maintenance to its NOC (Network Operations Center) on Saturday May 18, 2013 from 10 PM PT to
11:30 PM PT. 


START TIME:           

Saturday May 18, 2013 – 10:00 PM PT                         
Sunday May 19, 2013 – 5:00 AM GMT

END TIME:             

Saturday May 18, 2013 – 11:30 PM PT
Sunday May 19, 2013 – 6:30 AM GMT

SYSTEM AFFECTED:      
All services of Good for Enterprise (GFE)

CUSTOMER IMPACT:      
Message flow to devices will be interrupted for approximately 30 minutes, then resume normal operations without further user action.