Tag: Windows 7

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!

I realize I have been very quite on blogging for a few weeks, mainly due to a visit to Microsoft in Redmond and the MVP Summit which was suceeded by a three week vacation with my family.  Now I am at TechDays in Örebro, Sweden. Just got out from my session about AppLocker in Windows 7 which I think went quite smooth. The interest for TechDays is enormous and it has been a long day so far and it not over yet. I will attend a session on Windows 7 later today and will definetely not miss the party tonight. Still some jetlag though due to the vacation but I will struggle to get at least a couple of beers…

I also have a lot of catching up to do with my Inbox and other cool stuff that has been announced while I was on vacation, among many other things Microsoft has released some very interesting information on virtualization, read Mikael Nyströms blog post to get the summary,

There is this license tool that comes with Windows Automated Installation Kit and is installed by default. This unheard of tool is called Volume Activation Management Tool (VAMT). With this tool you can scan for instance all computer  objects in Active Directory to see the license status of all client machines as well as servers.

You will see what type of key (KMS/MAK) the machine is using, transition licenses from MAK to KMS, see if the license is activated on each machine and you will also be able to identify which machine is the Key Management Server.

The current version of this tool is version 1.2 but 2.0 is coming. Version 2.0 is needed to activate soon to be released Office 2010  but it also sports new features such as a command line interface for automating scans without using the user interface.

This week Microsoft have made two really interesting announcemants, the first being the release of App-V 4.6 and the second one being MED-V 1.0 SP1. (Release Candidate). Take a look at this MS post for what is new in App-V 4.6 and what is new in MED-V 1.0 SP1. Also do not miss this post on how to sequence Office 2010 for use with App-V 4.6.

Join Chris Jackson in the webcast Migrating from Internet Explorer 6 to Internet Explorer 8 (Level 300) to learn what you need to know when you migrate from IE6 to IE8. Actually I met Chris at the MVP Summit that took place last week and he is indeed a great and inspiring speaker and an interesting person to talk to. What Chris doesn’t know about application (and web site) compatibility is not worth knowing :)

WinRE (Windows Recovery Enviroment) is included by default in Windows 7, and this allows you to boot to WinRE to access recovery tools such as Complete PC image restore, system restore or to access a command prompt to run other useful command. You can access WinRE by booting a Windows 7 machine and press F8 and choose “Repair your computer”.

WinRE being included in Windows 7 is great but what is even greater is if you replace WinRE with DaRT (Diagnostics and Recovery Tools) included in Microsoft Desktop Optimization Pack (MDOP) which is available to Software Assurance customers. By doing this you get additional types of useful tools such as the ability to reset the passwords of local account, hotfix uninstall, crash analysis, reach computer management or use Windows Explorer. Now this is great! :)

The guide on how to replace WinRE with DaRT can be found at bink.nu.

Issues joining a Windows 7 machine to a domain, where the domain controller handling the domain join request is having old NT4 rests on it, has surfaced. The problem is related to an old overload workaround when upgrading an NT4 domain to Windows Server 2000 or 2003 domain controllers. The KB article which provide the solution is now published, see KB2008652 for more information on the resolution. Note that the problem also applies to joining Windows Server 2008 R2 servers to the domain.

TechDays is a two-day Swedish conference hosted yearly by Microsoft and partners. I will be there to speak about AppLocker in Windows 7. I will specifically talk about what makes it so great but I will focus on how to implement it and what to think about while doing so. There will be a bunch of other very interesting sessions on the latest Microsoft products so I hope I’ll see you at TechDays in March!

Just wanted to post a quick reminder that if you turn off UAC (User Account Control) in Windows Vista or Windows 7 you also turn off “Protected mode” in Internet Explorer. Turning off UAC is not recommended but if you do, make sure that you run with a standard user account.

Saved credentials can be a good thing, but many times they are not. The last couple of weeks I have become involved in a couple of cases where saved credentials in all from Windows XP to Windows 7 have been the cause of strange problems, primarily accessing file servers.

The problems have been with accessing mapped network drives or browsing file servers, with various error messages. Even though Windows 7 sports the “new” credential manager, this feature has been there even in Windows XP. This means that you can add credentials for servers so that you won’t have to provide them when accessing resources on the network.

The cause of the problem is for instance when a user change his or her password and the saved credential become obsolete, causing the user to have serious problems authenticating to the network resources.

The settings for these saved credentials are as follows:

Windows XP: Start “User Accounts” control panel, choose an account and then go to “Manage my network passwords”.
Windows Vista: Start “User Accounts” control panel, choose an account and then go to “Manage your network passwords”.
Windows 7: Search for and start the “Credential Manager” control panel.”

Solve the problems accessing network resources by deleting the saved credentials once and for all!