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.
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).
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!
… doesn’t exist… (yet) at least, not in my opinion. Kompletten Beitrag lesen
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.
Kompletten Beitrag lesen
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.
Kompletten Beitrag lesen
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.
Kompletten Beitrag lesen
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 ”
Kompletten Beitrag lesen
Just a quick tip: to rename a VM and all VM files (vmx, vmdk and such), shut down the VM, rename it then migrate it to another host and make sure you migrate to another datastore.
Our OCS client gave an unknown error when trying to expand Distribution Groups. After lots of searching I found this http://blogs.technet.com/greganth/archive/2009/03/26/office-communicator-error-message-received-when-expanding-a-group-distribution-list.aspx.
After trying this we still had the issue. So after finding out that you can test groupexpansion when connecting to the DG URL from the OCS server itself (localhost), I got an error message.
System.Security.SecurityException: Duplicate token failed
at Microsoft.LiveServer.DLExpansion.Service.ThrowSoapFault(Exception e)
at Microsoft.LiveServer.DLExpansion.Service.CheckAuthorization(SearchResult dnResult, DlxGroup& result)
at Microsoft.LiveServer.DLExpansion.Service.ProcessADRequest(String key, DlxGroup& result)
at Microsoft.LiveServer.DLExpansion.Service.ExpandDistributionList(String groupMailAddress)
There still was a problem with rights and probably with impersonation. I found out the application pool was using the RTCComponentService instead of IIS_WPG. Giving RTCComponentService impersonation rights fixed it!
< ältere Beiträge