Monthly Archives: December 2009

Juniper SSG Firewall and XBox Live

How to configure a correct XBox Live Connection though a Juniper SSG Firewall. This is what I have done, and it works like a charme.

1. I made Three Services.

Xbox Live 1.
UDP scr port: 0 – 65535 dst port 3074-3074
TCP scr port: 0 – 65535 dst port 3074-3074
TCP scr port: 0 – 65535 dst port 88-88
Timeout Never
Xbox Live 2.
UDP scr port: 0 – 65535 dst port 3074-3074
TCP scr port: 0 – 65535 dst port 3074-3074
Timeout 30
Xbox Live 3.
TCP scr port: 0 – 65535 dst port 88-88
timeout 30

Continue reading

Prepare and Service Windows Images Using the New DISM Tool

Deployment Image Servicing and Management (DISM.exe) is a new command line tool that you can use to service a Windows image or prepare a Windows PE image. The DISM tool replaces the Package Manager (pkgmgr.exe), PEimg, and Intlcfg tools used with Windows Vista. DISM consolidates the functionality found in those three tools, as well as delivers new functionality to improve the experience of offline servicing.

DISM can be used to service Windows Vista with Service Pack 1 (SP1) and Windows Server 2008. When used with Windows 7 and Windows Server 2008 R2, you get the added functionality.
You can use DISM to:
  • Add, remove, and enumerate packages and drivers.
  • Enable or disable Windows features.
  • Apply changes based on the offline servicing section of an unattend.xml answer file.
  • Configure international settings.
  • Upgrade a Windows image to a different edition.
  • Prepare a Windows PE image.
  • Take advantage of better logging.
  • Service down-level operating systems like Windows Vista with SP1 and Windows Server 2008.
  • Service all platforms (32-bit, 64-bit, and Itanium).
  • Service a 32-bit image from a 64-bit host and service a 64-bit image from a 32-bit host.
  • Make use of old Package Manager scripts.

Command-Line Options

To service a Windows image offline, it must be applied or mounted. WIM images can be mounted using the Windows Image (WIM) commands within DISM, or applied and recaptured using ImageX.
You can also use commands to list the indexes or verify the architecture for the image you are mounting. After you update the image, you must unmount it and either commit or discard the changes you have made.
The base syntax for nearly all DISM commands is the same. After you have mounted your Windows image, you can specify any DISM options, the servicing command that will update your image, and the location of the mounted image. You can use only one servicing command per command line. If you are servicing a running computer, you can use the /online option instead of specifying the location of the mounted Windows Image.
The base syntax for DISM is:
DISM.exe {/image:<path_to_image> | /online} [dism_options] {servicing_command} [<servicing_argument>]
Movie : Technet

HP Sizer for Microsoft Hyper-V 2008 R2

HP released an Sizer tool for Microsoft Hyper-V 2008 R2. Source : http://h71019.www7.hp.com/ActiveAnswers/us/en/sizers/microsoft-hyper-v2008.html

The HP Sizer for Microsoft Hyper-V 2008 R2 is an automated, downloadable tool that provides quick and helpful sizing guidance for “best-fit” HP server and storage configurations running in a Hyper-V R2 environment. The tool is intended to assist with the planning of a Hyper-V R2 virtual server deployment project. It enables the user to quickly compare different solution configurations and produces a customizable server and storage solution complete with a detail Bill of Materials (BOM) that includes part numbers and prices.

The HP Sizer for Microsoft Hyper-V 2008 R2 allows users to create new solutions, open already existing solutions, or use other types of performance data collecting tools, such as the Microsoft Assessment and Planning tool (MAP), to build rich Hyper-V R2 configurations based on HP server and storage technology. The tool allows rapid comparison of Hyper-V R2 characterizations using various HP server and storage choices.

Hyper-V How To: Plan Performance

Good read from Microsoft. Source : http://blogs.technet.com/tonyso/archive/2009/11/30/hyper-v-how-to-plan-performance.aspx

Customers often ask “Given a hardware load-out X, how many Ys can I get/run/host?”

The frustrating answer always starts with “…it depends…”. We caveat this way not because we want to frustrate, but because it is true. Many teams will go on to say “We have tested the following in our labs and gotten the displayed results…”

1 X = thingy

2 X = more thingies

3X = many more thingies

While accurate, not super-helpful.

The truth is that to do good perf planning for Hyper-V you have to run some tests.

Run them using your actual production load (converted to Virtual Machines) in a test environment.

TIP: you can download the free VHD version of SCVMM, then run it as a VM to convert your production machines to “test” virtual machines.

Then play with your assumptions and tweak things higher and lower and to your design tolerance and actually observe how perf goes.

Add an overhead/forgot-to-test percentage, done.

Continue reading