Being at TechEd in North America last week it seems that ACT 5.6 was released on Monday last week. Among the improvements are tools for migrating to the 64-bit platform, including a 64-bit version of the Compatibility Administrator.
The assessment overview is something that also has been improved and I strongly recommend you to download and intall this tool if you are making an inventory for upgrading to Windows 7.
Download at MS Download Center.
Deployment Guru Johan Arwidmark wrote a blog post today stating that there is now a hotfix that resolves a rather common problem during deployment, where one after the deployment get to choose the network location although the profile used is the domain profile and the location therefore should be “Work”. The fix has KB article number 2028749.
Something different for a change. For all Swedes out there there is a competition going on where you can win one of five copies of Windows 7 Ultimate Edition. You compete by sending in the best desktop background picture you have and the theme is Swedish nature. More information (in Swedish) here!
So the small but never the less useful tool Volume Activation Management Tool (VAMT) 2.0 has been released. Use it to keep track of your licenses, do activations and much more! Read more on it at the Windows Team Blog.
In MDT 2010 you can enable two settings that during deployment of your machines will patch them automatically using a WSUS server of your choice.
Take a look at your existing task sequence(s) and look for “Windows Update (Pre-Application Installation)” and “Windows Update (Post-Application Installation)” and choose to enable them both or just the latter.
In your customsettings.ini somewhere beneath the [Default] section add the row:
WSUSServer=http://WSUSServerName
It seems System Center Online Desktop Manager has been re-branded as Windows Intune, and it was just presented at MMS in Las Vegas. What Windows Intune do is to provide means to manage and monitor Windows 7 clients in the cloud. This is recommended for 25-500 PC:s.
What it does for you:
More at: http://www.windowsintune.com/
What you see in the score for your Windows Vista and Windows 7 machines, you know the score in System properties and Performance and information tools, really comes from the command line tool “winsat”. To find out some very detailed performance specs on your machine and the specific hardware parts such as hard drive, graphics card, memory and such you can run the command winsat with a number of switches.
For instance “winsat disk” runs performance tests on my disks and present it in detail with read/write speeds etc along with the score on each individual test. Give it a try!
If you think that you have come a far way making sure all users are running as standard users you must stop and rethink. Well, having all users as standard users is very good from many perspectives but with coming challenges your efforts must not stop there. A growing problem is the fact that more and more applications install in the user space, i.e. in the \users\username\appdata directory instead of the traditional “Program files”.
Also Windows 7 contain Windows Installer 5.0 which sports a new feature which makes the software vendors easily make Windows Installer (MSI files) that install software in the user space instead of program files, and thereby not requiring the user to be administrator or even require a UAC prompt for credentials for an administrative account.
The standard users of course think this is great, meaning they after all can install and run for instance Google Chrome without needing to ask that restrictive IT department. From the IT departments view this fact that standard users can install and run applications is a concern.
The answer to take care of this problem is simply the new Windows feature AppLocker. To be honest it is somewhat like Software Restriction Policies (SRP) but whatever bad things you have heard about SRP you can forget about them. AppLocker contains new features that make the implementation and ongoing management very easy compared to Software Restriction Policies. More about AppLocker in the AppLocker walkthrough.
I got a question the other day on a problem where a person is installing a set of applications during deployment of Windows 7, using MDT 2010. The problem is that one application requires to be run in Vista compatibility mode before it can even be installed, most likely due to a check in the installer for which Windows version is being used, a rather common compatibility issue.
One solution to this is to use Compatibility Administrator which is a part of ACT to create a so called “shim” which makes the installation go through, fooling the application that the OS is Windows Vista even though it is Windows 7. But, how do we get the shim applied during our deployment, which we want to automatic?
It is rather simple, just add a “run custom command” in the task sequence before the application is installed, which applies the compatibility shim to the machine, making the installation run through. Also note that you can run custom commands in the “applications” section in MDT2010, just add the command line to the path field and off you go!
So it has been just a bit more than a week ago that TechDays Sweden closed its doors. To summarize it there were two looong days packed with interesting sessions but also not to mention meeting new people. I really hope to see TechDays Sweden grow even larger next year and I think there is plenty of room for even more sessions but also other related activities that I will work hard to get on next years conference. Now I am looking forward to TechEd North America, maybe I’ll see you there :)