Deploying DPM 2012 agent with SCCM

Although System Center Data Protection Manager offers a way to do a remote installation of the agent, it’s far from ideal when you have to deploy the agent to several hundred laptops.

Since the agent offers a silent installation, I thought it would be best to let SCCM do what it does best. I created a package of the agent with a program “DPMAgentInstaller_x64.exe /q dpmservername“. Unfortunately the advertisement fails with a failure exit code of -2147023288.
Read more »

3  

Connecting Mobile Devices to Exchange 2010

My colleague had problems connecting his brand new Samsung Galaxy Advance, running Android 2.3.6, to the Enterprise mail server. After configuring his device he received the message:

Congratulations! After connecting your mobile device to Exchange Server 2010, you can now send text messages from Outlook 2010 and Outlook Web App on your computer. You can also receive and reply to text messages.

But he didn’t receive any mails or calendar items.

During my investigation I logged on to the Exchange 2010 server and run the Powershell command Get-ActiveSyncDeviceStatistics –mailbox [user]. In the list of configured devices that are able to synchronize with the Exchange server I saw his old Windows Mobile phone and his Android phone. For the Android phone the LastPolicyUpdateTime and LastSuccssSync fields where empty.

I removed his mobile devices from the ActiveSync by using the command Remove-ActiveSyncDevice –Identity [id], (probably the following will also work: Get-ActiveSyncDeviceStatistics –mailbox [user] | Remove-ActiveSyncDevice, or definitely Get-ActiveSyncDeviceStatistics -mailbox [user] | %{ Remove-ActiveSyncDevice –Identity $_.Identity}). After I removed the devices he was able to successfully connect his phone to the Exchange server.

Users can also remove unused Mobile Devices themselves by using OWA. Going to Options -> All Options -> Phone you can see all the registered mobile devices connected to the mailbox.
What I noticed is that since Exchange 2010 SP1 the amount of mobile devices that can be synchronized with the mailbox is limited to 10. When this amount is reached no new devices can be connected to the mailbox and old devices need to be removed.

I think this is something to keep in mind when users complain they can’t connect their new phone to the Exchange server. The amount of devices can be changed using the Set-ThrottlingPolicy command.

3  

DirectAccess breaks after installing UAG SP1 Update 1

Last week Microsoft released Forefront UAG SP1 Update 1 (http://www.microsoft.com/download/en/details.aspx?id=27604). After installing the update our DirectAccess clients lost corporate connectivity.

A quick look on our UAG server learned that the DirectAccess Monitor reported the DNS64 as Not Healthy.

Looking through the UAG services I discovered that the Microsoft Forefront UAG DNS64 Service was not running and had the start type Manual. Starting the service restored the corporate connectivity for the clients. I’ve changed the startup type to automatic to make sure DirectAccess continues to work after a reboot of the server.

0  

‘the selected driver is not applicable to any platforms’ when importing Dell WinPE CAB

While trying to setup our new OSD we couldn’t get the network up while in WinPE. We had already imported the latest WinPE driver CAB from Dell, but still we were not seeing any NIC’s within WinPE.

I tried to import the drivers manually instead of using the Dell tools and got errors for a lot of drivers: ‘the selected driver is not applicable to any platforms’

There is a hotfix available that allows driver importing for WinPE that are only signed for Windows 7 at http://support.microsoft.com/kb/978754 (KB978754).

2  

Online archive access with Outlook 2007

I have been happily using Outlook 2010 now for a few months and love the access to my Exchange 2010 online archive. However, since SCCM is not functional yet some of my co-workers are still on Office 2007 (and thus Outlook 2007). Support for Exchange 2010 online archive has been announced a while back and I was under the impression that it was already implemented.

It seems you have to request and install the following hotfix: KB2412273

The added support for the Exchange 2010 online archive isn’t mentioned in the release notes, but trust me… it’s there!

3  

The perfect mobile device…

… doesn’t exist… (yet) at least, not in my opinion. Read more »

4  

Teched Day 3

Day three in Berlin.

Today was the first time that the name System Center Configuration Manager vNext wasn’t used anymore. It’s announced that the next installment of SCCM will be called SCCM 2012. So yes, unfortunately we have to wait a bit longer before we can see it in a production environment.

Read more »

3  

Teched Day 2

Day two @ Teched has been a very long day. I’ve been attending sessions about Lync Server 2010, Domain Services in a virtualized environment, have been doing some hands on labs with System Center Virtual Machine Manager (SCVMM) and with the next installment of System Center Configuration Manager, vNext.

What I would like to share from today is mostly about Lync Server 2010 and a bit about SCVMM.

Read more »

2  

Teched Day 1

Today was the keynote session at Teched 2010 in Berlin.

During this session Brad Anderson welcomed everybody and explained Microsoft’s vision. A lot of that vision is about the cloud and how the cloud can enhance the user experience.

Read more »

4  

Configuration Issues with Vsphere

After an import of 40 ESX 3.5 virtual machines from an external company, we discovered that we couldn’t power up any new virtual machines unless we disabled “Admission Control” on that specific cluster.

After correcting the settings on the cluster it showed on the summary page of the cluster that VMware HA had a Configured Failover capacity of 1 host and the Current Failover Capacity was 0 hosts. And there was a warning stating: “Insufficient resources to satisfy HA failover level on cluster ”

Read more »

3