On a Microsoft MDT 2012 Update 1 installation that had worked during a test period we needed to deploy a new batch of laptops with a different product number as this batch was different from our tests because the fingerprint readers were removed from the device.
Tag Archive for Microsoft
With the upcoming release of Hyper-V 3.0 we see a lot of movement from both VMware and Microsoft on marketing level so all features are promoted, recently this type of marketing became a bit more ugly as VMware launched a ‘Get the facts‘ and older blogs from Microsoft on ‘Windows Server 8: Hyper-V 3.0 Evens the Odds with vSphere‘. Dan Brinkmann posted a very useful overview (from a Microsoft perspective) about the hypervisor on his blog.
During the last couple of projects I did I noticed that Microsoft Lync would prevent my session to log off normally, either on a Citrix XenApp/XenDestop or normal fat client deployment. Somehow running Lync stopped the logoff process and I would the error “This program is preventing Windows from logging off”:
A couple of weeks ago Microsoft came to Inter Access to give a Windows 8 Demo Mania event, they mentioned the Scenario-based RDS deployment so that triggered me to look into it and the result is this video. I hope this clarifies how scenario based deployment works:
I was creating an unattended installation of the App-V 4.6 x64 for RDS using RES Automation Manager, I used an installation script from somebody else as source for this installation and the installation went without any problems. I accessed the server via a published desktop managed by RES Workspace Manager to test an application that was delivered via App-V but I couldn’t launch the application and it came up with the following errors in the eventviewer:
Today on of my colleagues was telling me about a Windows 7 deployment that was configured trough GPP but he noticed that not all the GPP settings where set somehow. He found a quick fix by removing the user from all the groups he was nested in, log the user in and add the user to all the groups again. When I heard this problem I knew I had seen this before in an environment with users in +200 nested groups in Windows 2008 R2. So I told him it could be the MaxTokenSize that has to be set to a proper value, Microsoft has an KB article to do so.