An important update is now available to resolve issues customers are currently experiencing when using the Hybrid Configuration Wizard (HCW) to create a new or manage an existing hybrid deployment with Microsoft Exchange Server 2013.
If you currently have an Exchange 2013-based hybrid deployment configured, you will not notice any issues unless you rerun the HCW as part of updating or managing your existing hybrid features. Unless you need to reconfigure your hybrid deployment, you can simply wait for the next update of Exchange Server 2013 (Cumulative Update 6) to correct this issue with the HCW.
For Exchange 2013 organizations creating new or managing an existing hybrid configuration with the HCW, the following HCW error message indicates you are experiencing the issue this update addresses:
Subtask CheckPrereqs execution failed: Check Tenant Prerequisites Deserialization fails due to one SerializationException: Microsoft.Exchange.Compliance.Serialization.Formatters.BlockedTypeException: The type to be (de)serialized is not allowed: Microsoft.Exchange.Data.Directory.DirectoryBackendType
If you experience this issue, contact Microsoft support to obtain the fix as documented in KB2988229. This fix requires Exchange Server 2013 Service Pack 1 (SP1) or Cumulative Update 5 (CU5).
Once the Interim Update (IU) is applied, customers can successfully run the HCW and complete configuring a hybrid deployment with Office 365.
On september 2012 i wrote a article about mdt displaying the task sequence name.
I MDT 2012 Update 1 you had to change LiteTouch.wsf to fix this.
In MDT 2013 this much easier to do:
On December 2010 i wrote an article: automatically move computers to the right OU.
In MDT 2012 update 1 this was an issue: MDT 2012 settings per task sequence
In MDT 2013 this is still a issue:
How to fix:
I changed DeployWiz_SelectTS.vbs file and it work again
1. Edit DeployWiz_SelectTS.vbs
2. Add after “Dim sTemplate”
Set Oshell = createObject(“Wscript.shell”)
3. Add before “End Function” (bottom of page)
sCmd = “wscript.exe “”” & oUtility.ScriptDir & “\ZTIGather.wsf”””
oItem = oSHell.Run(sCmd, , true)
Microsoft released Rollup 5 for Microsoft Forefront Threat Management Gateway (TMG) 2010 Service Pack 2 (SP2).
Issues that are fixed in this rollup package:
2963805 FIX: Account lockout alerts are not logged after you install Rollup 4 for TMG 2010 SP2
2963811 FIX: The TMG Firewall service (wspsrv.exe) may crash when the DiffServ filter is enabled
2963823 FIX: “1413 Invalid Index” after you enable cookie sharing across array members
2963834 FIX: HTTPS traffic may not be inspected when a user accesses a site
2967726 FIX: New connections are not accepted on a specific web proxy or web listener in Threat Management Gateway 2010
2965004 FIX: EnableSharedCookie option doesn’t work if the Forefront TMG service runs under a specific account
2932469 FIX: An incorrect value is used for IPsec Main Mode key lifetime in Threat Management Gateway 2010
2966284 FIX: A zero value is always returned when an average counter of the “Forefront TMG Web Proxy” object is queried from the .NET Framework
2967763 FIX: The “Const SE_VPS_VALUE = 2” setting does not work for users if the UPN is not associated with a real domain
2973749 FIX: HTTP Connectivity verifiers return unexpected failures in TMG 2010
The Troubleshoot-DatabaseSpace.ps1 script is used by Microsoft System Center Operations Manager 2007 to detect and correct any excess log growth or Microsoft Exchange database (.edb) file growth that, if unchecked, may cause database downtime. By default, System Center Operations Manager 2007 runs the script every 15 minutes. However, you can use Task Scheduler to configure and run this script to monitor database log and file growth.
The Troubleshoot-DatabaseSpace.ps1 script performs the following actions:
- Keeps track of log generation rate for the highest log generators per database. This helps determine which users are logging too heavily and potentially causing space issues.
- Keeps track of the available disk space for both the database and the log files. If either of these is within a configurable threshold of being full, further action must be taken.
- Keeps track of the log generation rate. If it appears that the disk is going to run out of space within the value specified by the HourThreshold parameter (based on the log generation rate), further action must be taken.
To avoid critical issues, make sure the value for the HourThreshold parameter is large enough to give you time to react during normal business hours while enough free space is available. If drives are filling up faster than the value specified, immediate action must be taken to protect the disk.
- If all of the preceding conditions are fulfilled, the script determines the list of top 25 users who accessed the database during the last one-hour period. The script then quarantines the top high-usage mailboxes for which the sum of the log generation rate is greater than the difference between the current generation rate and the sustainable generation rate that would allow tiding over the configurable time threshold. These users are quarantined for six hours, during which they won’t have access to e-mail.
- If the troubleshooter is unsuccessful at dropping the log generation rate to below the threshold level, it will write out events that translate into health model alerts. At this point, the script removes the database from provisioning by running the Set-MailboxDatabase cmdlet with the ExcludeFromProvisioning parameter set to
$true against the specified database. You may need to move mailboxes to a new server to rebalance space.
- If the troubleshooter quarantines more than 10 users, this indicates a systemic issue, which you need to follow up on. The health model will trigger an urgent alert from this condition.
The default settings used in the Troubleshoot-DatabaseSpace.ps1 script are defined in the StoreTSConstants.ps1 script.
Command: .\Troubleshoot-databasespace.ps1 -server MBX01 -PercentLogFreeSpace 10 -PercentEDBFreeSpace 10 -HourThreshold 5 -Quarantine
Taskscheduler: powershell.exe -PSConsoleFile “C:\Program Files\Microsoft\Exchange Server\V14\bin\exshell.psc1” -command “. ‘C:\Program Files\Microsoft\Exchange Server\V14\Scripts\Troubleshoot-databasespace.ps1’ –server EX01 -PercentLogFreeSpace 10 -PercentEDBFreeSpace 10 -HourThreshold 1 -Quarantine”