Exchange 2010 : Find Users with iOS 4.0 Devices (User Agent 801.29)

The following Exchange Shell Script will identify all users that have an iOS 4.0 device - these should be upgraded to 4.01+ ASAP. Save the code below into a .ps1 file and execute,

View source
$ukCASUsers = get-casmailbox -Filter {HasActiveSyncDevicePartnership -eq $true} | where {($_.ServerName -like "*")}
 
Foreach ($casMbx in $UKCASUsers ) 
{
get-activesyncdevicestatistics -mailbox $casMbx.legacyexchangedn | Where {($_.DeviceuserAgent -like "*801.29*")} | select 
 
Identity,DeviceType,DeviceID,DeviceUserAgent,LastSuccessSync
}

Alternatively you can block specific user agents as per: http://blogs.technet.com/b/exchange/archive/2008/09/05/3406212.aspx

More information available here: http://support.apple.com/kb/ts3398

Exchange 2010 : Create a Message Send Size Limit For A Subset Of Users Within an Exchange Organisation

We recently encountered a requirement to limit a subset of users to a maximum send size without imposing this organisation wide - this was achieved this using a transport rule, the steps are outlined below.

  1. Create a Distribution Group that contains all your Exchange Users that you wish to limit email size for. For this example this group has an email address of RestrictedUsers@domain.local.
  2. Create a new Dsn Error message: New-SystemMessage -DsnCode 5.7.50 -Language En -Internal $True -Text 'Your message has not been sent as it exceeds the maximum allowed message size of 20MB. Please contact the helpdesk for support on 123 or click here to raise a support ticket <a href="http://helpdesk/riaseticket.html">Open Support Ticket</a>.'
  3. Next create a new transport rule (change the RestrictedUsers@domain.local email address to reflect the group created in step 1) : New-TransportRule "Block Internal Email over 50MB" -FromMemberOf "RestrictedUsers@domain.local" -RejectMessageEnhancedStatusCode "5.7.50" -RejectMessageReasonText "Your message has not been sent as it exceeds the maximum allowed message size." -SentToScope "InOrganisation"
  4. Verify the priority of any other transport rules configured in your Exchange Organisation.
You can now test this by attempting to send an email over 20MB, it will be rejected as long as you are a member of this distribution group.

ConfigMgr : Download Setup ConfigMgr Updates in Advance for Offline Install

The commands below facilitate deployment of SCCM / ConfigMgr in an offline environment by allowing you to download the setup required updates from another machine.

  • For SCCM 2007 use the following command to download Setup required SCCM updates to C:\TEMP\: SMSSETUP\BIN\I386\SETUP.EXE" /download C:\TEMP
  • For ConfigMgr 2010 use the command: SMSSETUP\BIN\x64\SETUP.EXE" /download C:\TEMP

 

AD DS : DCPROMO fails with A domain controller for the specified domain could not be located.

Check the DCPROMO log files located under: C:\Windows\Debug.

Perform the following test on the server: nltest /dsgetdc:<fqdn of a functioning domain controller>

You can also confirm, that you can lookup srv records in DNS, execute the following from a command prompt:

  1. nslookup
  2. set type=all
  3. _ldap._tcp.dc._msdcs.<domain_name>

If SRV records are returned then it is more than likle this is a firewall related issue. Check logs for blocked traffic, specifically on UDP and TCP port 389.

Citrix : Empower Copy and Paste Causes Application Issues

I came across an issue today with an application called empower, running through Citrix Presentation Server 4/XenApp 5. On multiple copy/paste operations the application would simply fail, returning back to the main menu.

To resolve this, copy and paste the following code into a new file name empower.reg and then apply the registry file to your Citrix servers that have the Empower application installed. Ensure the applictaion is closed.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Terminal Server\Compatibility\Applications\EMPOWER]
"OpenClipboardRetries"=dword:00000020
"OpenClipboardDelayInMilliSecs"=dword:00000100
"Flags"=dword:0000000c

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Terminal Server\Compatibility\Applications\QUICKSET]
"OpenClipboardRetries"=dword:00000032
"OpenClipboardDelayInMilliSecs"=dword:00000150
"Flags"=dword:0000000c

Next configure speedscreen settings for Empower.exe and Quickset.exe.

Once the registry keys have been set and SpeedScreen configured on all servers simply load the application and test. No reboot is required, only the application cannot be open by any user (if it was when you applied it ensure all processes are closed, then test.)

Page 1 of 2

Login Form