1. Install guest.
2. Create descriptive wallpaper (root chain).
3. Install guest tools.
4. Change WSUS server.
5. Update Windows.
6. Bootstrap Internet Explorer.
7. Install Clamwin.
8. Update Clamwin.
9. Change registered company to my company. Remember WOW64 node.
10. Disable netlogon machine password change.

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\DisablePasswordChange = 1

11. Disable shutdown event tracker.
12. (Snapshot)
13. Create descriptive wallpaper (development chain).
14. Join domain.
15. Install .Net Framework 3.51.
16. Install IIS.
17. Install MSMQ AD Integration.
18. Install Visual Studio.
19. Install TFS Client.
20. Install Visual Studio SP1.
21. Install SQL Server.
22. Install SQL Server SP1.
23. Configure SQL Firewall Ports.
24. Enable SQL Server TCP/IP.
25. Install GhostDoc.
26. Install CodeRush.
27. Install Coco/R.
28. Install Tytan.
29. Update Windows.
30. Bootstrap VS.
31. Apply VS customizations.
    1. Import settings.
    2. Set up TFS working folder.
    3. Set up GhostDoc to use langword.
32. Bootstrap SMS.
33. Create link to K2 keygen.
34. (Snapshot)
35. Justice.

http://msdn.microsoft.com/en-us/library/%s.aspx

You can obviously also do something like:

http://msdn.microsoft.com/en-us/library/%s(loband).aspx

In case you need a refresher, here is how you add it:

1. Click the wrench (top right).
2. Options
3. Basics (top)
4. Manage (alongside “Default Search”)
5. Add
6. Give it a name and keyword (the keyword is important).
7. Paste in my URL.

To use it go to your address bar and type the keyword, tab and then the full type name. So for example (my keyword was msdnd):

msdnd : [TAB] : system.xml.serialization.xmlelementattribute : [RETURN]

1. Followed the pre-setup instructions to the T.
2. Run the installer; health check fails. SQL Server is the wrong version (2008 RTM); can’t find analysis services, NOTHING.
3. Hmm… must need SQL 2008 SP1. Install it via Windows Update.
4. Try again; health check fails. Wrong version of SQL Server, again.
5. Google – get a solution.
6. Follow those instructions to the T.
7. Installer CRASHES. Each time it does this I need to reboot.
8. Eventually just delete the SQL Server version check from hcpackages.xml
9. It looks like it’s installing now.

16 hours later. TFS Server 2005 took me merely 4-5 hours (did it twice). Considering it’s a test-bed server where I am going to continue working on integrating K2 with TFS Server (we are going to be using K2 to automate our builds) this was just plain ridiculous.

It’s clever, and that’s about it, to use Sharepoint. It seems as though TFS might have started off as a Sharepoint extensibility test. Things would be far easier were it not for the whole Sharepoint dependency (and analysis and reporting – I don’t need this).

These guys need to take a hint from the ASP.net team.

1. Extract it over VMWare folder in Program Files which should be one of:
   • C:\Program Files\VMWare
   • C:\Program Files (x86)\VMware
2. Update each shortcut by:
   1. Right click the shortcut.
   2. Click properties.
   3. Click Shortcut (at the top).
   4. In the target box change the .exe at the end to .cmd
   5. Click Ok.

VMWare vSphere Client Patch

Clearly, I take no responsibility for any ill effects that this patch may cause – whatsoever.

After reading Joseph Cooney’s post on “Works on My Machine” I was inspired to integrate this prestigious certification program into my company’s typical workflow.

Introduction

The program applies only to developers and QA specialists who use virtual environments (VMWare, VPC, VirtualBox, etc.) for primary development and/or quality assurance. If the application meets the strict requirements stipulated below it may be branded with the “It Works on My Virtual Machine” logo.

Click for a high-res version.

Compatibility with other Certification Programs

This certification is compatible with “It Works on My Machine”. It will not qualify and application under “It Works on My Machine” automatically, nor will “It Works on My Machine” automatically qualify an application under “It Works on My Virtual Machine”. Each certification program needs to be met independently.

Technical Certification Requirements

1. Compile your latest application code with the relevant compiler. This should include changes from other developers.
2. Launch the application/site that has just been compiled.
3. Set a breakpoint in the code and reach it. Use any means possible to ensure the path to the breakpoint executes, this may include (but is not limited to):
   • Changing CPU registers (typically the instruction pointer) by manipulating the virtual machine host.
   • Using the snapshot feature of the virtual machine host to return to a previous snapshot where the code path executed successfully. Depending on your virtual machine software you may have to take a snapshot before navigating to alternates.
   • Manipulating the operating system and supplementary services (e.g. SQL) to ensure the path executes correctly.
4. Check the code changes into your version control system.
   • If the snapshot feature was used, ensure you return to the original state before checking the code in.

Notification Requirements

Customer and partners need not be informed of the branding; however, it is a preferable to place this logo in a clear location to indicate the quality of the software. Typical examples include:

• Splash screen on rich clients.
• Click-through interstitial landing page on websites.
• Ascii art in terminals.
• Using it to xor-encrypt sensitive data:
  • The character string “It Works On My Virtual Machine” (without quotes) repeated for the duration of the plaintext.
  • The byte stream of the logo image repeated for the duration of the plaintext.

That’s long gone now; so today I did some file pruning and deleted the VMDKs I used for that drive; VMWare refused to boot my machine because there was a snapshot with that file somewhere in the hierarchy.

As it turns out the snapshot was a sibling of my current one – which seems odd; logic dictates that the VMDK should only be needed for the descendants of that snapshot. In any case I had to kill nearly every snapshot to be able to boot the VM (Murphy made sure that it was the last snapshot I deleted); on top of that I needed to remove the drive and RAM file locks.

This is the first time I have had a gripe with VMWare. It wasn’t really a train smash but inconvenient at best. My snapshot nesting was getting ridiculous, so I shouldn’t really complain.