Use the following WQL queries to identify devices by architecture - this makes rolling out SCCM client updates a little easier.
The WQL below can be used to create an X64/64-bit device collection. Simply modify X64-based PC to "X86-based PC" to create a collection for X86/32-bit devices.
select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System inner join SMS_G_System_SYSTEM on SMS_G_System_SYSTEM.ResourceId = SMS_R_System.ResourceId where SMS_G_System_SYSTEM.SystemType = "X64-based PC"
I was under the impression that USMT will save/copy any unsynchronised offline files, whilst ignoring files that are safely synchronised elsewhere - until recently.
On performing an in-place refresh from Windows Vista x86 to Windows 7 x86 SP1 we had a single user who's un-sync'd offline files were not saved/copied by USMT. Unfortunately there was little we could do after the event, other than try and work out why, without the scanstate.log files.
I then came across the following Microsoft KB: http://support.microsoft.com/kb/2736596
So USMT should protect and migrate these files... it just doesn't.
In further testing on the E7x40 series I've run in to Blue Screen errors under Windows 7. Using DaRT Crash Analyzer the offending driver looks to be the Intel Management Engine Driver, TeeDriver.sys:
Import this driver to SCCM and integrate this into the SCCM driver pack to resolve this on future deployments.
I've been testing Windows 8.1 within the organisation for a few weeks - and have been experiencing issues with Modern (Metro) Applications when interacting with our zScaler proxy. The issue with this, amongst other cookie-based authenticated proxy servers, is that Modern Applictaions do not support the use of the users cookie to provide authentication to the proxy. Essentially we would see issues such as:
Microsoft User Experience Virtualization is a relatively striaght-forward technology to deploy - there is no server-side application installation, all you need is a couple of file shares and then an agent deploying to each device. The components of my production deployment are as follows:
DFS shares, each with offline files disabled - UE-V 2.0 doesn't play well with offline files:
Rather than using all of the built-in templates, copy those that are of interest into the Templates folder, and ensure that you do not register the MS templates at Agent Install (I'll show you in a moment). I encountered lots of issues with the built-in templates and Office 2013 - see here. For reference I copied:
When it comes to settings synchronisation, you have two options:
We opted for a per-user model, this means that if a user loses thier device they can logon to a new laptop - one which we have associated their user account with in SCCM - their personal, user assigned applications install via SCCM and UE-V 2.0 applies their personal settings such as IE homepage, Outlook Signatures, Desktop Background. Essentially its a poor-man's USMT, it will never provide the incredibly rich capability of USMT as on a per-user basis we're seeing <5MB per user, in fact typically 2MB.
Finally, to deploy the agent via SCCM use the following command - be sure to update the UNC path with a valid location! The important parts here are:
Remember, with UE-V 2.0 settings are synchronised in different ways: