Windows 7 Godmode

There are several post on the web on godmode I did not use it before but I did some testing with it and like it. so below is a list of the strings that you can use With a link to a microsoft site for all the options.

How does this work  Create a folder on your desktop and name it GodMode.{ED7BA470-8E54-465E-825C-99712043E01C}

but the name before the dot can be self named


Below is a list of additional useful folders that you can create using the same process described above. I have named the folder accordingly to give you a clue as to what each one does:



Canonical Names of Control Panel Items

As of Windows Vista, each Control Panel item is given a canonical name for use in programmatically launching that item. This topic lists each Control Panel item, its canonical name, and its GUID.

Windows 7 Control Panel Canonical Names

The following canonical names are defined for Control Panel items in Windows 7. All names are also valid on Windows Vista unless specified otherwise. Not all Control Panel items are available on all varieties of Windows and some Control Panel items might appear only when appropriate hardware is detected. These canonical names do not change for different languages. They are always in English, even if the system’s language is non-English.

MDT Debugger

Source :

MDT Debugger

When creating and configuring an LTI deployment solution there is one thing that always bugs me immensly: debugging custom scripts. Writing the scripts is easy, but debugging them is a whole different experience. The reason is simple, to debug a script you normally need to launch it from within the MDT environment (during the deployment). Consequently, it can be quite hard and very slow to iron out any errors that they (might) contain because of the need to run a full deployment of a computer, just to be able to do some testing.

This isn’t the actual part that bugs me though. The annoying part is when the script fails and MDT ends, all because of a silly mistake made in the script; this for me is the frustrating part that could at times drive me insane. Because MDT has now terminated, pretty much the only sure way to re-test the script is to re-run the deployment; vastly slowing down the debugging time.


I should point out that this is no fault of MDT, it is all mine; after all, I was the one who put the error in the script! But, because of the way MDT works, the debugging of these custom scripts can be labourious task…. until now!  [cue drum-roll]  I would like to present version 0.1 of the "MDT Debugger"! This nifty little tool makes debugging most custom actions, script or not, simpler and prevents MDT from terminating with the red error screen if the custom action has failed.

The MDT Debugger sits in-between MDT and your custom script and intercepts the return code that is normally sent back to MDT from your custom action. It then displays the error code and allows you to either accept and return it to MDT, edit it before returning it to MDT, or to relaunch the custom action again. This later option gives you the opportunity to fix any errors in the script/action and then relaunch it – thus eliminating the need to relaunch the deployment process from the very beginning just to re-test the custom action.

More on source :

Microsoft Deployment Toolkit 2010


Microsoft Deployment Toolkit 2010

Deploy Windows 7 beta with Microsoft Deployment Toolkit 2010. Join the beat and download MDT 2010 now at
MDT 2010 is the next version of Microsoft Deployment Toolkit, a solution accelerator for operating system and application deployment. New features like flexible driver management, optimized transaction processing, and access to distribution shares from any location simplify deployment and make your job easier. Deploy faster and easier with MDT 2010. Join the beta now.
Tell us what you think! Join the beta and send us your honest feedback. We appreciate your input.
Microsoft Deployment Toolkit is the fourth generation deployment accelerator from Microsoft. It is the recommended process and toolset to automate desktop and server deployment. MDT benefits you by providing:

  • Detailed guidance and job aids for every organized role involved with large-scale deployment projects.
  • Unified tools and processes required for desktop and server deployment in a common deployment console and collection of guidance.
  • Reduced deployment time, standardized desktop and server images, along with improved security and ongoing configuration management.

Tell your peers about MDT 2010! Please forward this mail to anyone who wants to learn more about Microsoft Deployment Toolkit.