Step One – Get the utility

The utility is a part of HP’s SSM (SP49507), SSM stands for “HP System Software Manager” and version I have been playing with is 2.14 Rev A. Download that from the ftp://ftp.hp.com/pub/softpaq/sp49501-50000/sp49507.exe and if you need to see if your PC is in the list, check ftp://ftp.hp.com/pub/softpaq/sp49501-50000/sp49507.html

Step Two – Create the file

This is how the file should look like and it should have the name TPMEnable.REPSET

If you look at the picture, you can see that in every section there is a *. That is our default value that will be pushed into the bios.

Step Three – Create a Command and verify that it works

Now, be a bit careful, TPM is a security device and if you look your self out, it could be “tricky” to get back, so now you have been notified at least. So, we need a command to set all this and also to set a BIOS password and here it is:

BIOSConfigUtility /SetConfig:TPMEnable.REPSET /NewAdminPassword:"Password1"

So, if you take the BIOSConfigUtility.exe and TPMEnable.REPSET and put them in the same folder and run the command (elevated) with a password that is better then mine and then reboot the machine, you will see that it is going to enable the TPM chip and now you can just enable BitLocker on the machine.

Step Four – Getting stuff into the TS

Now, this can be done in different ways, one is to create a Script, or a batch file or an MDT Application. The reason for me to have an application, is very simple. When I work at customers I create a lot of “things”, if they are applications, they are pretty easy to copy inside the deployment workbench, from my personal Deployment share to the customers and vice versa. I like drag and drop, it makes life more…relaxed…:-) One other story, if they are applications, you could use the “MandatoryApplications001=” in CS.ini

So this is how it looks in my Task Sequence

(No, sorry, my password for TPM is not 111-something, trust my…)

Now when I have the application I can open my Task Sequence and modify that like this:

In the first picture you can see that I have added the application called “CUSTOM – Hewlett-Packard – BIOS Configuration” and in the other picture you can see that I have one condition to run this and that is same condition as the task “Enable Bitlocker” has.

So, that was pretty easy, right

Step Five – some more things…

Configure BitLocker:

This is my settings (also default)

Just one small thing. Modify/Set this BDEKeyLocation= to something, otherwise the keyfile ends up locally on the c: drive…:-)

De following list calls out the most important fixes which are included in this release:

22656040 An Exchange Server 2007 Client Access server may respond slowly or stop responding when users try to synchronize the Exchange ActiveSync devices with their mailboxes

2498852 "0×80041606" error message when you perform a prefix search by using Outlook in online mode in an Exchange Server 2007 environment

22653334 The reseed process is unsuccessful on the SCR passive node when the circular logging feature is enabled in an Exchange Server 2007 environment

22617784 Journal reports are expired or lost when the Microsoft Exchange Transport service is restarted in an Exchange Server 2007 environment

2289607 The week numbers displayed in OWA do not match the week numbers displayed in Outlook for English users and French users in an Exchange Server 2007 environment

For the complete list check HERE

General Notes:

Note for Forefront Protection for Exchange users For those of you running Forefront Protection for Exchange, be sure you perform these important steps from the command line in the Forefront directory before and after this rollup’s installation process. Without these steps, Exchange services for Information Store and Transport will not start after you apply this update. Before installing the update, disable ForeFront by using this command: fscutility /disable. After installing the update, re-enable ForeFront by running fscutility /enable.

cscript c: \ Windows \ System32 \ slmgr.vbs / ipk xxxxx-xxxxx-xxxxx-xxxxx-xxxxx

Enter the product key xxxxx Windows Server 2008 R2. It is also able to activate Windows 7. The following text appears when the command is successful.

Microsoft ® Windows Script Host Version 5.7
Copyright © Microsoft Corporation. All rights reserved.
Installed product key xxxxx-xxxxx-xxxxx-xxxxx-xxxxx successfully.
The installation of the KMS server is complete. The server installs itself on port 1688. This port must be opened to be put in the firewall. To change the port the following command can be used.

Slmgr.vbs / SPRT xxxx
Once the firewall is open and the key is installed, the KMS server service has to be restarted. Do this by using the following command:

slsvc & net stop & net start slsvc

To check whether the data will be registered correctly in the DNS, the following command:

nslookup-type = srv _vlmcs._tcp

Here, the following output should appear:

_vlmcs._tcp.test.local SRV service location:
priority = 0
weight = 0
port = 1688
svr hostname = kms.wardvissers.local
internet address = 192.168.150.7 kms.wardvissers.local

Clients / Servers

The clientele / servers need to connect to the KMS host will automatically find the host by dns. When the client / server using a MAK key is activated. Should this be put back to a KMS client key. These keys are released by Microsoft. When this key is set on the client / server will automatically look for a KMS host. When not present, the client / server activation.

KMS client keys:

Windows 7 Enterprise: 33PXH-7Y6KF-2VJC9-XBBR8-HVTHH
Windows Server 2008 Standard: TM24T-X9RMF-VWXK6-X8JC9-BFGM2
Windows Server 2008 Enterprise: YQGMW-MPWTJ-34KDK-48M3W-X4Q6V
Windows Server 2008 R2 Standard – YC6KT-GKW9T-YTKYR-T4X34-R7VHC
Windows Server 2008 R2 Enterprise – 489J6-VHDMP-X63PK-3K798-CPX3Y

The following commands can the key be changed from MAK to KMS here are the xxxxx is one of the above keys.

slmgr.vbs / ipk xxxxx-xxxxx-xxxxx-xxxxx-xxxxx
Note: To ensure that the client is forced to activate the command to be executed on the client.
slmgr-ato

It can happen that the RMS server returns the following message. This is because the KMS server is just beginning to work with 25 clients and 5 servers.

You can find here the list with error codes & solutions: http://support.microsoft.com/kb/938450

Special thanks to:Harm Hoekstra

Add PF replica’s to an Exchange 2010 Server:

.\AddReplicaToPFRecursive.ps1 -server "Exchange 2003/2007 Server" -TopPublicFolder "\" -ServerToAdd "Exchange 2010 Server"

Replicate the System Folders to an Exchange 2010 Server:

.\AddReplicaToPFRecursive.ps1 -TopPublicFolder "\NON_IPM_Subtree" -ServerToAdd "exchange2010 server”

If you are planning to have multiple Exchange 2010 PF servers, you can repeat the Cmdlet

From the Exchange 2010 server: Update-PublicFolderHierarchy -Server "Exchange 2010 Server"

Step 2: Moving Exchange 2003/2007 PF’s to Exchange 2010

As a last step, after you confirmed that all the PF have been replicated to the Exchange 2010, you can move all replicas from Exchange 2003/2007 to Exchange 2010. The "move all replicas" will actually remove the Exchange 2003/2007 replicas.

To move all Exchange 2003/2007 replicas to Exchange 2010, which will actually remove the Exchange 2003/2007 replicas:

.\MoveAllReplicas.ps1 -Server "Exchange 2003 Server" -NewServer "Exchange 2010 Server"

Additional Cmdlets

To view a list of the replicas in the public folder hierarchy: Get-PublicFolder -recurse |fl name,replicas

For System Folders: Get-PublicFolder -recurse \non_ipm_subtree |fl name, replicas

To compare content replicated between the source and destination servers: Get-PublicFolderStatistics

Reference

Move Public Folder Content from One Public Folder Database to Another Public Folder Database – http://technet.microsoft.com/en-us/library/bb331970.aspx

· Overview

· How to configure your Exchange 2010 for the Outlook Mobile update

· Details about the Outlook Mobile update

· How to get support for Outlook Mobile updates

· How to subscribe for future updates

Overview

First, we’ll review the overall update experience that’s built into Exchange 2010.

As part of the Outlook Mobile update, users will receive an update notification in an e-mail message in their Inbox. The purpose of this message is to inform them that there’s an Outlook Mobile update for their phone.

The message will instruct the user to click an inline link. This prompts the phone to download the Initial Setup CAB. After the Initial Setup CAB is installed, it will check for available updates specific to the user’s device type.

Next, if an Outlook Mobile update is available, it will be downloaded and installed. The user will receive a notification message that tells them they need to restart their device. After the device is restarted, it will resynchronize the data (e-mail, calendar, contacts, and tasks) with the Exchange server so it will be compatible with the new format of Exchange Server 2010. After that synchronization is complete, the user will be ready to experience the new features in the Outlook Mobile update.

How to Configure Your Exchange 2010 Server for the Outlook Mobile Update

Now that you understand the tasks that the Outlook Mobile update performs, we’ll cover how to configure your Exchange server so that your users who have Windows Mobile 6.1 devices will receive the update notification e-mail message.

How to determine whether a user will receive the update notification e-mail message

The update notification e-mail message will be sent to the user’s device if the following conditions are true:

· The user’s mailbox is on a server running Exchange Server 2010.

· The Exchange ActiveSync mailbox policy parameter AllowMobileOTAUpdate is set to $True.

· The Windows Mobile OS version is 6.1. To check which version the device is running, from the Help About screen, look for the OS and Windows Mobile 6.1 build number (Start > Settings > System > About). You should see Windows OS = “Windows CE 5.2”, and the Windows mobile build should be between 19202 and 21142.

AllowMobileOTAUpdate

The AllowMobileOTAUpdate setting is one of the standard Exchange ActiveSync mailbox policy settings. This is the main setting that determines whether the update notification e-mail message is sent to the device.

The default value for the AllowMobileOTAUpdate parameter is enabled ($True). To confirm that your Exchange ActiveSync mailbox policy has this setting enabled, follow these steps:

1. Check which policy the user is assigned to by running the following command.

Get-CasMailbox <user> | fl ActiveSyncMailboxPolicy

In the preceding example, the result is the following.

ActiveSyncMailboxPolicy : Default

2. Check that the policy returned in the preceding step has the AllowMobileOTAUpdate setting enabled by running the following command.

Get-ActiveSyncMailboxPolicy Default | fl AllowMobileOTAUpdate

If the AllowMobileOTAUpdate setting is set to $True, the following will be returned.

AllowMobileOTAUpdate : True

Details About the Outlook Mobile Update

The following section covers the end user experience for the Outlook Mobile update. The update notification e-mail message the user receives will look like this.

The user can click the first link in the message to start the download. This downloads the initial setup CAB, which is necessary to find the appropriate Outlook Mobile update for that user’s device.

Next, the user will see a URL Confirmation page that informs them that they’re being taken to a Web site. The user should click Yes to continue. Clicking No will cancel the update process.

After the file begins downloading, the user will be asked if they want to open the file, save it to a location, or click Cancel. The user should click Yes to continue opening the file, making sure that the open file after download box is selected.

The next screen they’ll see is the progress bar that shows that the initial setup CAB is being downloaded and installed.

The initial setup CAB finds the appropriate Outlook Mobile update for the user’s specific device. After the initial setup CAB is installed, it connects to the Outlook Mobile Update Service to find the update. If an update is found, the user will be asked if they want to download the Outlook Mobile update. The user should select Yes to download and install the update.

After the Outlook Mobile update has been installed, the user needs to restart their device to ensure that all new Outlook Mobile files loaded correctly.

After the user restarts their device, they’re presented with a warning message that informs them that they need to resynchronize their data with Exchange. This is necessary because the existing format of the synchronized data isn’t compatible with the new features built into Exchange Server 2010. The user should click Yes in this warning message box.

Occasionally, a user may see the following error, which can appear when the resynchronization hasn’t yet occurred. The user will need to manually resync their data with Exchange.

How to Subscribe for Future Updates

There may be updates available for your users’ Windows Mobile 6.1 phones in the future. The Outlook Mobile update package will ask users if they would like Outlook Mobile to automatically check for updates on a regular schedule. Users should click Yes to automatically check for updates and receive notification when new updates are available.

Issues that are fixed in this rollup package:

2654016 A client may be unsuccessful in accessing a Java SSO application published to the web in a Threat Management Gateway 2010 environment

2653703 You receive an "Error: Subreport could not be shown" error message in the User Activity or Site Activity report in a Forefront Threat Management Gateway 2010 environment

2654585 UDP packets may become backlogged when you increase the "Maximum concurrent UDP sessions per IP address" setting in a Forefront Threat Management Gateway 2010 environment

2624178 Threat Management Gateway 2010 administrators may be unable to generate reports

2636183 Both sides of a TCP connection are closed when the client or remote application half-closes the TCP connection in a Forefront Threat Management Gateway 2010 environment

2653669 Summary information for the Top Overridden URLs table and for the Top Rule Override Users table display incorrect information in a Forefront Threat Management Gateway 2010 environment

2617060 Forefront TMG 2010 enables L2TP site-to-site connections in RRAS

2655951 Japanese characters in the subject line of an Alert email message are not readable in the Japanese version of Forefront Threat Management Gateway 2010

2654068 "The Web Listener is not configured to use SSL" warning message may occur when you configure a Web Listener to use a valid SSL certificate in a Forefront Threat Management Gateway 2010 environment

2654193 You receive a "Bad Request" error message when you try to access Outlook Web App in a Forefront Threat Management Gateway 2010 environment

2654074 String comparison may become case-sensitive when you publish a website by using Forefront Threat Management Gateway 2010

2658903 The Forefront Threat Management Gateway Firewall service (Wspsrv.exe) may crash frequently for a published website secured by SSL after you install Service Pack 2

Note that along the lines of products like Exchange, cumulative updates for ForeFront TMG are now also called Rollup instead of Software Update or Update.

You can request ForeFront TMG SP2 RU1 directly from support here.

Issue

The issue I had was that once I moved all receive connectors to the new Exchange 2010 server, emails sent to any of the mail-enabled public folders (which were still being replicated between the 2 servers) was being rejected with the following NDR:

#< #5.2.0 smtp;554 5.2.0 STOREDRV.Deliver.Exception:ObjectNotFoundException; Failed to process message due to a permanent exception with message The Active Directory user wasn’t found. ObjectNotFoundException: The Active Directory user wasn’t found.> #SMTP#

The following error was found in Event Viewer:

Log Name: Application
Source: MSExchange Store Driver
Date: 7/09/2010 2:00:02 AM
Event ID: 1020
Task Category: MSExchangeStoreDriver
Level: Error
Keywords: Classic
User: N/A
Computer: server@domain
Description:
The store driver couldn’t deliver the public folder replication message “Folder Content (PublicFolderDatabase@domain)” because the following error occurred: The Active Directory user wasn’t found.

Solution

Given this Exchange environment was originally running versions prior to Exchange 2007, the legacy Administrative Group and all its empty subcontainers still existed. An explanation from the Microsoft Exchange Team of why this issue occurs can be found here: http://msexchangeteam.com/archive/2010/05/05/454821.aspx

The solution to this issue was to delete the empty Servers container from the legacy Administrative Group.

Using ADSIEdit.msc, connect to a domain controller and navigate to:

CN=Configuration , CN=Services, CN=Microsoft Exchange, CN=[ExchangeOrganisationName], CN=Administrative Groups, CN=[LegacyAdministrativeGroupName], CN=Servers.

Right click the Servers container and select Delete

Click Yes

Restart the Microsoft Exchange Active Directory Topology Service and the Microsoft Exchange Information Store on both the Exchange 2007 & Exchange 2010 Servers

‘

On the TMG Management server I saw also the The number of HTTP requests per minute exceeded the configured limit.

Solution:

1. Open TMG Management Console

2. Go Intrusion Prevention System

3. Flood Mitigation

4. Click on the Edit button: The number of HTTP requests per minute exceeded the configured limit

Default = 600 I configured = 3000

1. Automatic meeting processing

Issue 1.1 – Recurring meeting is removed from calendar when organizer cancels single occurrence

When you synchronize your iOS device by using Exchange ActiveSync on an Exchange Server 2007 mailbox, if the organizer cancels a single occurrence of a recurring meeting, the device may unexpectedly delete the entire recurring meeting.

Solution

There are two parts to this solution:

Install the Exchange Server 2007 Service Pack 3 (SP3) update rollup 4 (RU4). The problem details and the link to the update are documented in the following Microsoft Knowledge Base article:

2502276 A meeting request series are deleted unexpectedly from the calendar in an Exchange Server 2007 environment

Update the Apple iOS on your device to version 4.3 or later. For more details on the latest iOS version, click the following link:

http://www.apple.com/ios

Apple has documented the issue at the following web site:

http://support.apple.com/kb/ts3714

Issue 1.2 – Attendee becomes meeting organizer

When you synchronize your iOS or Android device by using Exchange ActiveSync on an Exchange Server 2007 mailbox, you may unexpectedly become the organizer for a meeting that you were invited to. This does not change the meeting for all attendees.

Solution

This can occur if you change the reminder for a single occurrence of a recurring meeting on an iOS or Android device. There may be other property changes to meeting items that may result in the same symptom.

This issue is resolved in Rollup Update 4 for Exchange Server 2007 Service Pack 3. See the KB article below for additional information.

2521063 You are incorrectly displayed as a meeting organizer after you synchronize the meeting by using your mobile device in an Exchange Server 2007 environment

Note Affected meetings must be deleted and replacement meetings must be created after the servers are patched.

Issue 1.3 – Your meeting response to the organizer appears to have been sent by someone else

When you respond to an Exchange ActiveSync (EAS) meeting invitation, the meeting originator may see someone else’s name displayed as having accepted the invitation instead of you.

Solution

Ensure the Apple iOS on your device is version 4.3 or later. For more details on the latest iOS version, click the following link:

http://www.apple.com/ios

This was fixed by Apple in iOS 3.1. For more details, visit the following Apple web site:

iPhone and iPod touch: My replies to Exchange ActiveSync invitations seem to come from someone else

http://support.apple.com/kb/TS2806

Issue 1.4 – All Day Flag is not set properly on Mobile devices when meeting is scheduled cross multiple days

Mobile device clients do not treat a meeting request as an all day event meeting request. Additionally, the All Day field is marked with "No".

Solution

This issue is resolved in Exchange 2007 Service Pack 3 Rollup 2. The problem is documented in the following articles from the Microsoft Knowledge Base online:

2201236  The "All Day" field is marked with "No" when you access a meeting request that has a duration time that is more than 24 hours by using a mobile client through ActiveSync in an Exchange Server 2007 environment

2201236  Description of Update Rollup 2 for Exchange Server 2007 Service Pack 3

Issue 1.5 – Recurring Exchange calendar events deleted

In some situations, recurring calendar events can be removed from both the iOS device and Exchange when the organizer cancels an event instance.

Solution

This issue is resolved by Apple iOS 4.3, and impacts only the 4.2.6 and earlier versions. Apple has documented the issue at the following web site:

iOS: Recurring Exchange calendar events deleted

https://support.apple.com/kb/ts3714

Issue 1.6 – Appointment exceeding 24 hours changed to multiple day All Day Event

When an appointment item’s duration exceeds 24 hours, but is not marked as an All Day Event, Exchange ActiveSync changes the item on the device to become a multi-day All Day Event. The next time that the device synchronizes with the mailbox, the change is propagated from the item on the device to the item on the Exchange Server 2010 mailbox.

Solution

Microsoft is investigating this issue. This problem can occur when using any ActiveSync device synchronizing with Exchange Server 2010.

2. Connectivity and synchronization failures

Issue 2.1 – Failures to Provision and Synchronize with Android OS

EAS policies can cause provisioning and synchronization to fail, when customized. Devices will not be provisioned if a policy is applied to the users of these devices that exceeds these limitations. This is discussed in comment 9 from the following post on Google’s Android forum:

http://code.google.com/p/android/issues/detail?id=9426

"We only support the basic (EAS 2.5) features in Froyo. So if your server requires, for example, password history or expiration, or complex characters, then it won’t be provisionable in Froyo. Our goal is to provide more policy support in future versions, but for now we support – password (PIN/alpha), minimum characters, max. fails to wipe, inactivity timeout, and remote wipe."

Solution

Updates to the Android OS version appear to resolve this problem. We encourage device users to update to the latest version available from their provider and follow vendor forums on synchronization issues. If the decision is made to allow older devices in the organization, Administrators can canvass device users, or use tools Log Parser or Export-ActiveSyncLog, to ensure that such devices are identified in the organization. Users of older devices can be grouped into a policy that can work for them.

Issue 2.2 – Unable to connect using Exchange ActiveSync due to Exchange resource consumption

There are several symptoms and remediation methods for issues with resource depletion caused by devices connecting with Exchange ActiveSync.

Solution

Administrators should review the following article in the Microsoft Knowledge Base to determine if they are experiencing the same server symptoms:

2201236  Unable to connect using Exchange ActiveSync due to Exchange resource consumption

Note This article also describes a known issue with iOS 4.0, defined by user agent 801.293 – http://support.apple.com/kb/TS3398 and is discussed in Issue 2.5, below.

Issue 2.3 – "This message has not been downloaded from the server" error when trying to open a message

You synchronize your Exchange Server mailbox with your iOS device. When you try to open a message on the iOS device, the following error may be displayed:

This message has not been downloaded from the server

Solution

You must configure the Accepted Domain using Exchange Management Shell. Use the steps in item #7 in the following post from the Exchange Team Blog:

Exchange 2010 SP1 FAQ and Known Issues

http://blogs.technet.com/b/exchange/archive/2010/09/01/3410888.aspx

This issue is being reviewed by the Microsoft Exchange product team.

Issue 2.4- You receive a synchronization failed email message when you synchronize your mobile device

When you synchronize your mobile device by using ActiveSync on an Exchange Server 2010 mailbox, you receive a synchronization failed email message similar to the following:

From: Microsoft Exchange on Behalf of <user>

Sent: <date>

To: <other user>

Subject: Synchronization with your <ActiveSync device> failed for 1 items.

Synchronization with your <ActiveSync device> failed for 1 items.

Microsoft Exchange was unable to send the following items to your mobile device. These items have not been deleted. You should be able to access them using either Outlook or Outlook Web Access.

Item Folder: Inbox

Item Type: IPM.Schedule.Meeting.Resp.Pos

Solution

This issue is described in the following article in the Microsoft Knowledge Base:

2201236 You receive a synchronization failed email message when you synchronize your mobile device by using ActiveSync on an Exchange Server 2010 mailbox

To resolve this issue, install the following update rollup:

2201236 Description of Update Rollup 3 for Exchange Server 2010 Service Pack 1

Issue 2.5- Users are unable to synchronize Apple iPhone iOS 4.0 with the Exchange Server mailbox

Immediately after updating to iOS 4.0, some users may notice that Exchange ActiveSync Mail, Contacts, or Calendars do not sync, or sync very slowly. In addition, some Exchange Server administrators may notice their servers running slowly. This problem is also discussed in Issue 2.2, above.

Solution

Update the device to a later iOS version. Apple has documented the issue at the following web site:

iOS 4.0: Exchange Mail, Contacts, or Calendars may not sync after update

http://support.apple.com/kb/TS3398

Issue 2.6- ActiveSync does not work for mobile device users connecting to Exchange Server 2007 mailboxes after swapping URLs between Exchange Server 2010 and 2007

This problem occurs because the device is unable to properly redirect a user whose mailbox has been moved. The 451 redirect response to the device is not properly interpreted.

Solution

Typically, this issue is resolved by device updates to the latest operating system. Verify the following:

Verify that you have configured the LegacyURL for Exchange 2007 users. This will automatically switch the URL for the user to the appropriate target on the device. See the following blog topic:

http://blogs.technet.com/b/jribeiro/archive/2009/11/26/transitioning-from-an-exchange-2007-environment-to-exchange-2010.aspx

This has been reported for several device types, to include iOS and Android operating system. If the problem is noted with the latest version of the device operating system, and the LegacyURL is correctly established and working for other devices, consult with the device vendor’s technical support.

If you are using an Apple iOS device, update the device to the iOS version 4.3.2.

Note In migrations where the mailbox moves are between different forests, a 451 is not sent. The reason for this is that the old server does not know of the new endpoint for connectivity. In such circumstances, the device must be manually reconfigured.

Check: http://support.microsoft.com/kb/2563324

2012 is going to be crazy as well, nice projects in prospect. All in all it was a great year and there’s a lot of cool stuff already planned for 2012!. I wanted to share a couple of cool facts with you:

• 40+% Traffic growth compared to 2010
• Busiest Day: July 13th 2011 – 599 unique views
• Busiest Month: May 2011 – 10.788 unique views
• Totally 122.855 unique views

Lets make 2012 at least as successful!

The app now features a fully refreshed UI, a new post editor with a formatting toolbar, support for Android-powered tablets, background posting, and improved stats!

If you aren’t an Android user, never fear! There are plenty of WordPress mobile apps to choose from.

You must close all dialog boxes before you can close Exchange Management Console.

Download: KB2618444 Cumulative Security Update for Internet Explorer: December 13, 2011

Well now we have a better way, you can hide explorer shell while MDT is “doing it’s thing”!

So how do we do this? It is simple, just add the following line to the customsettings.ini file:

HIDESHELL=YES

I have included before and after shots below:

Look explorer…

,

No explorer…. that’s better!

Download HERE

Teradici released a new  PCoIP zero client and host card firmware and the PCoIP Management Console. The following releases are now available for download on the Teradici support site (techsupport.teradici.com):

• Firmware 3.5.0 for PCoIP Zero Clients and PCoIP Host Cards.
• PCoIP Management Console 1.7.0

Firmware 3.5.0 update includes key feature enhancements including:

• USB2.0 with VMware View sessions
• Imprivata OneSign® Virtual Desktop Access via proximity cards with VMware View
• IEEE 802.1x network security
• IPv6 support. 

With this release, Teradici continues to innovate PCoIP zero client technology and accelerate the adoption

For those still unaware, the 530Mb+ file (1,4 GB extracted) contains the full set of binaries; you can use it to upgrade existing RTM or SP1 installations or deploy new Exchange 2010 SP2 installations.

Besides the usual set of hotfixes, SP2 introduces the following features:

Address Book Policies
Address Book Policies, also known as GAL segmentation, ABPs are meant to segmentize the address book, giving users a certain view of the address book like Address List Segregation did for Exchange 2003/2007.

OWA mini
This will be a lightweight browser like OMA in the past, meant for simple browsers.

Hybrid Configuration
This wizard is to make the configuration of an on-premise Exchange and Office 365/Exchange Online more simple, reducing the steps required from 49 to 6.

OWA Cross-Site redirection
This will allow clients to be silently redirected to the proper site if they log on to a CAS server located in a site different than the site where their mailbox is hosted and externalURL has been specified there.

After preparing your forest for Exchange 2010 SP2, the schema version number will have changed. Check the Schema Versions page for information on the new ObjectVersion and RangeUpper values for Exchange 2010 SP2.

Note that SP2 introduces an additional requirement, which is the IIS 6 WMI Compatibility feature; you can add this feature using the GUI or by using the Powershell cmdlets Import-Module ServerManager followed by Add-WindowsFeature Web-WMI.

The proper method to upgrade mailbox servers that are a member of a Database Availability Group is described here.

The releases notes are not available at time of writing; we’ll update this post when they become available.

Highlights of VMware Workstation 8.0.1 functionality include:

• Graphics performance and compatibility enhancements.
• Improvements in creating and using shared virtual machines and remote virtual machines.
• Ubuntu 11.10 is officially supported as a guest operating system.
• Disk and memory management issues have been addressed.
• Many customer-reported issues have been resolved.

VMware Workstation 8.0.1 is a free update for all VMware Workstation 8 users.

Resolved Issues

The following sections list the resolved issues in VMware Workstation 8.0.1.

• Windows 7 guest installation failed after powering on the virtual machine with the error A required CD/DVD drive device driver is missing. If you have a driver floppy disk,
CD, DVD, or USB flash drive, please insert it now.
• VMware Tools failed with the message VMware Tools unrecoverable error.
• VMware Tools failed to start in Fedora 15 guests.
• An Ubuntu 11.10 guest crashed with a signal 11 error if you installed or upgraded VMware Tools.
• On hosts with Nvidia GeForce and Quadro video cards, some of the clouds in the Unigine Heaven Benchmark application were drawn solid black.
• Easy Install did not properly function on Ubuntu 11.10.
• If remote virtual machines were open, you could not shut down the Windows hosts.
• When transitioning from Full Screen mode to Exclusive mode, the Full Screen toolbar sometimes failed to hide.
• Host memory reservation restrictions on Windows hosts are more relaxed in VMware Workstation 8.0.1 than in previous versions of VMware Workstation.
• CD/DVD mount Linux.iso failed while installing VMware Tools in Ubuntu 11.10 guests.
• The AltGr key was not working in an Ubuntu guest in Unity mode when the host and guest keyboards were both set to a layout that contained the AltGr key.

One of the new features is monitoring

To Configure monitoring you find a tab Monitoring on properties of the Deployment Share.
You must set a V Enable monitoring of this deployment share

Under the root of the Deployment Share u see now Monitoring. When you click on Monitoring you can see running deployments.

MDT 2012 Beta 2 offers new User-Driven Installation components and extensibility for Configuration Manager 2007 and Configuration Manager 2012 as well as integration with the Microsoft Diagnostics and Recovery Toolkit (DaRT) for Lite Touch Installation remote control and diagnostics.

Key benefits include:

• Full use of the capabilities provided by System Center Configuration Manager 2012 for OS deployment.
• Improved Lite Touch user experience and functionality.
• A smooth and simple upgrade process for all existing MDT users.

New features For System Center Configuration Manager customers:

• Support for Configuration Manager 2012 (while still supporting Configuration Manager 2007)
• New User-Driven Installation components for Configuration Manager 2007 and Configuration Manager 2012
  • Extensible wizard and designer, additional integration with Configuration Manager to deliver a more customized OS experience, support for more imaging scenarios, and an enhanced end-user deployment experience
• Ability to migrate MDT 2012 task sequences from Configuration Manager 2007 to Configuration Manager 2012

New features For Lite Touch Installation:

• Integration with the Microsoft Diagnostics and Recovery Toolkit (DaRT) for remote control and diagnostics
• New monitoring capabilities to see the progress of currently running deployments
• Support for deploying Windows to computers using UEFI
• Ability to deploy Windows 7 so that the computer will start from a new VHD file, “Deploy to VHD”
• Improved deployment wizard user experience

MDT 2012 the final release will be available download through to January 2012 I think.

To check the status of the Multipath Policy you can run the following PowerCLI script:

Per host:

Get-VMhost ESXHOST | Get-ScsiLun -LunType disk

Per Cluster:

Get-Cluster CLUSTERNAME| Get-VMHost | Get-ScsiLun -LunType disk

To change the Multipath Policy you can run the following command:

Per Host:

Get-VMHost ESXHOST | Get-ScsiLun -CanonicalName "naa.6005*" | Set-ScsiLun -MultipathPolicy "roundrobin"

Per Cluster:
get-cluster “Cluster Name” | Get-VMHost | Get-ScsiLun -LunType disk | Where-Object {$_.MultipathPolicy -ne “RoundRobin”} | Set-ScsiLun -MultipathPolicy “RoundRobin”

Special thanks to: VMPROS

The View desktops we’ve got setup are using linked clones and persistent disks which map to the D:\ in the users sessions. Of course this means the users profile is loaded to the D:\ instead of C:\ in the virtual desktops. My issue is, when a new users comes from our old environment into the test view setup, their Outlook is trying to find their OST file on the C:\ (c:\document and settings\…etc). The users data has been loaded to the D:\ though. The only way I’ve found to get around this is going into the Contol Panel in the users session, deleting their Outlook profile,

Solution:

Microsoft saves information about profile under HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Profiles\Outlook

So, within regedit, I right-clicked on HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Profiles\Outlook then chose Export. For Save as Type, I changed the value to "Text Files (*.txt)". I then opened the text file I created with Notepad. You can’t just search for "Outlook.ost", since there are null, i.e. 00, characters stored between each character. They show up in an ASCII representation as dots. E.g. Outlook.ost would be O.u.t.l.o.o.k…o.s.t.

Since the "Outlook.ost" could be broken across multiple lines, I decided just to search for o.s.t. I found the following in the text file I had created.

Value 31

  Name:            001f6610

  Type:            REG_BINARY

  Data:           

00000000   43 00 3a 00 5c 00 44 00 – 6f 00 63 00 75 00 6d 00  C.:.\.D.o.c.u.m.

00000010   65 00 6e 00 74 00 73 00 – 20 00 61 00 6e 00 64 00  e.n.t.s. .a.n.d.

00000020   20 00 53 00 65 00 74 00 – 74 00 69 00 6e 00 67 00   .S.e.t.t.i.n.g.

00000030   73 00 5c 00 4a 00 69 00 – 6d 00 5c 00 4c 00 6f 00  s.\.J.i.m.\.L.o.

00000040   63 00 61 00 6c 00 20 00 – 53 00 65 00 74 00 74 00  c.a.l. .S.e.t.t.

00000050   69 00 6e 00 67 00 73 00 – 5c 00 41 00 70 00 70 00  i.n.g.s.\.A.p.p.

00000060   6c 00 69 00 63 00 61 00 – 74 00 69 00 6f 00 6e 00  l.i.c.a.t.i.o.n.

00000070   20 00 44 00 61 00 74 00 – 61 00 5c 00 4d 00 69 00   .D.a.t.a.\.M.i.

00000080   63 00 72 00 6f 00 73 00 – 6f 00 66 00 74 00 5c 00  c.r.o.s.o.f.t.\.

00000090   4f 00 75 00 74 00 6c 00 – 6f 00 6f 00 6b 00 5c 00  O.u.t.l.o.o.k.\.

000000a0   6f 00 75 00 74 00 6c 00 – 6f 00 6f 00 6b 00 2e 00  o.u.t.l.o.o.k…

000000b0   6f 00 73 00 74 00 00 00 -                          o.s.t…

I could also have searched in the .reg file I created when I exported the registry information from the other computer. But, again, you can’t just search for "Outlook.ost" in the .reg file you created, either, since the information in it is the hexadecimal representation of the binary data in the registry keys. You would need to convert a string, such as "ost" to hexadecimal form. You can do that at String – ASCII, HEX, Binary Converter. In the String field, I put in ost. The converter showed me the equivalent hex value is 6F 73 74. Note: the converter shows decimal/ASCII, binary, and hex values. Make sure you use the correct one. Also note that the hexadecimal representation of "OST" is not the same as "ost". Since the error message I received referred to Outlook.ost, I converted "ost" to hexadecimal. Again, it may be better to limit the length of the string to reduce the chance it will be broken across multiple lines in the file.

Once you have the hexadecimal equivalent of the ASCII string, you still can’t just search for it, i.e. a search for 6F7374 wouldn’t work. The hexadecimal numbers are stored in the .reg file with commas and the null character, 00, between them. I.e., I would need to search for 6f,00,73,00,74 instead.

In the .reg file found it among the following lines:

"001f6610"=hex:43,00,3a,00,5c,00,44,00,6f,00,63,00,75,00,6d,00,65,00,6e,00,74,\

  00,73,00,20,00,61,00,6e,00,64,00,20,00,53,00,65,00,74,00,74,00,69,00,6e,00,\

  67,00,73,00,5c,00,4a,00,69,00,6d,00,5c,00,4c,00,6f,00,63,00,61,00,6c,00,20,\

  00,53,00,65,00,74,00,74,00,69,00,6e,00,67,00,73,00,5c,00,41,00,70,00,70,00,\

  6c,00,69,00,63,00,61,00,74,00,69,00,6f,00,6e,00,20,00,44,00,61,00,74,00,61,\

  00,5c,00,4d,00,69,00,63,00,72,00,6f,00,73,00,6f,00,66,00,74,00,5c,00,4f,00,\

  75,00,74,00,6c,00,6f,00,6f,00,6b,00,5c,00,6f,00,75,00,74,00,6c,00,6f,00,6f,\

  00,6b,00,2e,00,6f,00,73,00,74,00,00,00

I noticed it was associated with a "001f6610" entry. When I had searched the text file, I had also seen Outlook.ost associated with "Name: 001f6610".

You can delete the following registry key with group policy preferences to disable using Offline Folders after disabling Use Cached Mode in Group Policy:

HKCU\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Profiles\Outlook\13dbb0c8aa05101a9bb000aa002fc45a\001f6610

This update contains a number of customer-reported and internally found issues since the release of SP1. See ‘KB 2608646: Description of Update Rollup 6 for Exchange Server 2010 Service Pack 1′ for more details.

This update contains a number of customer reported and internally found issues since the release of RU5.

The most Important Fixes:

• 2627769 Some time zones in OWA are not synchronized with Windows in an Exchange Server 2010 environment
• 2528854 The Microsoft Exchange Mailbox Replication service crashes on a computer that has Exchange Server 2010 SP1 installed
• 2544246 You receive a NRN of a meeting request 120 days later after the recipient accepted the request in an Exchange Server 2010 SP1 environment
• 2616127 "0×80041606" error code when you use Outlook in online mode to search for a keyword against a mailbox in an Exchange Server 2010 environment.
• 2549183 "There are no objects to select" message when you try to use the EMC to specify a server to connect to in an Exchange Server 2010 SP1 environment

Other Fixes:

• 2431609 An update is available that updates the message of a retention policy in OWA for Exchange Server 2010
• 2449266 EWS drops the TCP connection to the EWS client application without any error message in a Microsoft Exchange Server 2010 environment
• 2480474 A Users do not receive quota warning messages after applying SP1 for Exchange 2010
• 2514820 An incoming fax message is not delivered to the recipient in an Exchange Server 2010 SP1 environment
• 2521927 Disabling the Exchange ActiveSync Integration feature for OWA does not take effect in OWA Premium clients in an Exchange Server 2010 environment
• 2535289 The Microsoft Exchange Information Store service crashes occasionally when you run an antivirus application on an Exchange Server 2010 Mailbox server
• 2536313 Slow message delivery and mailbox access for journaling mailboxes on an Exchange Server 2010 server
• 2548246 The Microsoft Exchange Information Store service crashes occasionally when a folder view is corrupted on an Exchange Server 2010 mailbox server
• 2549289 A RBAC role assignee can unexpectedly run the Add-MailboxPermission command or the Remove-MailboxPermission command on an Exchange Server 2010 server that is outside the role assignment scope
• 2555851 A mailbox does not appear in certain address lists after you run commands on the mailbox in an Exchange Server 2010 SP1 environment
• 2559814 A user cannot add or remove delegates from a mailbox by using Outlook in an Exchange Server 2010 environment
• 2561514 Exchange Server 2003 user cannot view the free/busy information of a user in a different federated organization
• 2563860 You cannot create a new mailbox database if you already have 1000 mailbox databases in an Exchange Server 2010 environment
• 2567409 Certain free/busy messages are not replicated from an Exchange Server 2010 server to an Exchange Server 2003 server
• 2571791 Retention policies are applied to Contact items unexpectedly in an Exchange Server 2010 environment
• 2572052 Certain properties of a recurring meeting request from external email accounts are missing in an Exchange Server 2010 SP1 environment
• 2575005 You cannot start the EMC or the EMS in an Exchange Server 2010 Service Pack 1 environment
• 2578631 Certain users cannot send email messages to a mail-enabled public folder in an Exchange Server 2010 environment
• 2579172 Items that are deleted or moved still appear in the original folder when you use Office Outlook in online mode to access an Exchange Server 2010 mailbox
• 2579671 No results returned when you use the ExpandGroup method in EWS to retrieve a list of members of a Dynamic Distribution Group in an Exchange Server 2010 environment
• 2582095 The SmtpMaxMessagesPerConnection property of a send connector is not replicated to the subscribed Edge Transport server in an Exchange Server 2010 environment
• 2600835 The RPC Client Access service crashes when you delete an attachment of an item by using Outlook in online mode in an Exchange Server 2010 SP1 environment
• 2601701 The memory usage of the MSExchangeRepl.exe process keeps increasing when you perform a VSS backup on Exchange Server 2010 databases
• 2617126 The Store.exe process crashes when you send an email message that has attachments in an Exchange Server 2010 SP1 environment

General Notes

An issue with management of RBAC roles when RU6 is partially deployed in the organization: Due to changes shipped in this update, certain warnings can be displayed when managing RBAC roles, if RU6 is not yet deployed to all servers in the organization. Please see the following KB article for more information:

Managing RBAC roles might display warnings or errors if Exchange 2010 SP1 RU6 is partially deployed in the organization
http://support.microsoft.com/kb/2638351

Note for Forefront users: For those of you running Forefront Protection for Exchange, before installing the update, stop all Forefront services.

VMware View makes it easy to extend to your users the opportunity to work where you want and on the device they choose. Today, we are excited to make this even easier with the release three new or updated mobile clients:

• VMware View Client for iPad 1.2 (Photo below showing new presentation mode!*)

• VMware View Client for Android Tablets

• VMware View Client for Cius

Let’s talk about the new clients…

VMware View Client for iPad 1.2
Building on the earlier View Client for iPad we released in March, VMware View Client for iPad 1.2 makes it easier, faster and better than ever to connect to your View desktop.

Optimized for VMware View 5
With support for VMware View 5, you can get better performance with reduced bandwidth options as well as more resilient connections to your desktop than previous versions.

Move Back and Forth between Windows Desktop and iOS Apps
Now with support for background multitasking, you can jump from your Windows desktop to another iPad app and then right back into the Windows desktop to where you left off!

Simpler to Connect with Embedded RSA Soft Token
If you need to use an RSA key to authenticate to connect to your View Desktop, just activate the RSA soft token built into the View Client for iPad and you just need to enter your RSA PIN when you connect to your View desktop.

Support for iOS 5 and Apple AirPlay
That right… VMware View Client for iPad 1.2 works well with iOS 5 and takes advantage of Apple AirPlay and an available AppleTV to use your big screen TV as a display for your View desktop. While some people might think that Apple TV is just for fun, it can now blur the lines between work and play and represents the best the post-PC era has to offer.

Work Smarter with Presentation Mode *
Use an external monitor or AirPlay in iOS 5 and the iPad display turns into a trackpad / keyboard while the external screen shows your View desktop!

Speaks Your Language
The latest VMware View client is now available in English, French, German, Japanese, Simplified Chinese, and Korean. When working multi-byte Asian languages, the new local input mode enables you to type in full lines of complete multi-byte words and then send them to your View desktop.

The new VMware View Client for iPad is available in the Apple App Store today! Check it out!

For those of you who follow this blog and use Android based tablets. Today we are happy to release our production Android clients for Android Tablets and the Cisco Cius. After all it is about supporting the tablet you choose.

VMware View Client for Android Tablets and the Cisco Cius
Whether you are using a Samsung Galaxy Tab 8.9 or 10.1, an LG/T-mobile G-Slate, a Motorola Xoom or any of the other newly available Honeycomb-based Android tablets or the Cisco Cius, you can get the most of your View desktop on the Android tablet you choose.

Optimized for VMware View 5
The VMware View Client for Android Tablets is the first Android client to support the PCoIP display protocol for best performance with VMware View 4.6 and View 5 users. With support for VMware View 5, you can get better performance with reduced bandwidth options as well as more resilient connections to your View desktop.

Move Back and Forth between Windows Desktop and Android Apps
Leveraging the power of Android multitasking, you can jump from your Windows desktop to another Android app and then right back into the Windows desktop to where you left off!

Speaks Your Language
The latest VMware View Client for Android is available in English, French, German, Japanese, Simplified Chinese, and Korean. When working multi-byte Asian languages, local input mode enables you to type in full lines of complete multi-byte words and then send them to your View desktop.

The new VMware View Client for Android Tablets is available in the Android Marketplace and the VMware View Client for Cius will soon be available in Cisco’s AppHQ. Check them out today!

How to Uninstall a Protection Agent

http://technet.microsoft.com/en-us/library/bb809113.aspx

Remove DPM agent from the DPM agent console

http://technet.microsoft.com/en-us/library/ff634203.aspx

Removing a Protected Computer

Remove-ProductionServer.ps1 -DPMServername [DPMServerName] -PSName [ProtectedComputerName]

Status: Inactive

Data source type:

Data source: System Protection

Computer: <ServerName>

Description: Last 1 recovery points not created.

DPM cannot create a backup because Windows Server Backup (WSB) on the protected computer encountered an error (WSB Event ID: 521, WSB Error Code: 0x807800A1).

For more information, open DPM Administrator Console and review the alert details in the Monitoring task area.

Solution:

Some noncritical volumes are included in the system state backup image when you use the "-allCritical" switch in Windows Server 2008 R2 or in Windows 7 only for non SP1 systems. SP1 includes this hotfix.