Setup a VM for packaging

1. Install Windows 7 that corresponds to your environment (Pro N x86 is my edition)

2. Disable User Account Control

3. Disable System Protection

4. Run Quest vWorkspace Desktop Optimizer

5. Install .NET Framework 4.0

6. Install prerequisites;

Visual C++ 2005
VC++ 2005 SP1
VC++ 2005 SP1 ATL security update
VC++ 2005 SP1 MFC security update
VC++ 2008
VC++ 2008 SP1
VC++ 2008 SP1 with ATL security update
VC++ 2008 SP1 MFC security update
VC++ 2010 SP1
VC++ 2012 Update 3
VC++ 2013
Visual J# 2.0
VS 2010 F# 2.0 SP1
.NET Framework 4.5.1

7. Set keyboard layout

8. Ensure VMware Tools are updated

9. Disable all power-settings

10. Run MSCONFIG and disable GUI of boot

11. Remove any excess hardware (floppy-drive, usb-devices)

12. Create shortcuts to any mapped drives / source-folders on the desktop

13. Show all icons in the system tray

14. Run Windows Update (might need to re-enable the service)

15. Activiate Windows

8 Comments

  1. Ice said:

    Does language pack matter on the packaging vm?

    October 6, 2012
    Reply
    • nickekallen said:

      Hello,

      If it matters for your applications, it matters for the packaging VM. Personally, I haven’t hit that scenario yet.

      October 7, 2012
      Reply
  2. Rock_Star said:

    Thanks .. for the Links at one place .. 🙂

    March 9, 2013
    Reply
    • nickekallen said:

      Great that it came to use!

      March 9, 2013
      Reply
  3. Stan said:

    Just stumbled across this advice. Would you keep the sequencing box up-to-date with Windows Updates inline with the AppV 5.0 clients?

    Cheers

    October 11, 2013
    Reply
    • nickekallen said:

      Hello,
      If that’s what you do for your clients, – yes

      October 13, 2013
      Reply
  4. Stan said:

    Hey mate,
    Would you suggest the above config for a 5.0 sp2 sequencer?

    Cheers

    May 13, 2014
    Reply
    • nickekallen said:

      Hello,
      Everything can be re-used, however the extensive VC++ deployment is something that you will have to reconsider for your Environment (if you want to use the auto-deploy capability)

      May 13, 2014
      Reply

Leave a Reply

Your email address will not be published. Required fields are marked *