generalopinion

Have you had the opportunity to test this with Windows Server 2008 as well? If so, what were your results?

Thanks for your reply. I've been out of the country so I apologize for not replying to this sooner. When attempting to use the x86 boot image we get the following error message as shown: Not sure how to "confirm" if the image is an SP2 image but as stated in my Environment notes in the original post, I am running SCCM 2007 SP2 R2. Thanks again for your help. P.S. It's not really a big deal if this doesn't work in a virtual environment as we use VM templates in VMware to deploy new virtual servers. But, I'd like to get PXE working in the virtual environment before I begin testing in production.

Problem: When attempting to PXE boot using a Windows PE x64 image, the actual .wim is downloaded from the PXE service point/distribution point as shown by the progress bar. After 100% completion the screen goes black, Windows PE is not loaded and the VM turns off. Details: I am using an MDT Task Sequence for deploying the Windows Server 2008 Operating System Install package. I simply copied it and changed the boot image on the Task Sequence instead of creating a new Task Sequence from scratch (not sure if this makes a difference or not). I was able to boot into it by using the Create a Task Sequence wizard (non MDT) but the sequence stalled before doing anything and rebooted. The drivers for VMware have been imported into the boot image as well. Environment: SCCM 2007 SP2 R2 running on Windows Server 2003 SP2 Target VM: 2GB of RAM, 40GB harddrive Any assistance would be great.

If my memory serves me correctly, I think that it will install the following morning but that depends on how you have your Maintenance Windows configured. Also in the Deployment Management properties of a deployment on the Schedule tab there is a check box, "Ignore maintenance windows and install immediately at deadline" which could impact this behavior as well.

Nice. Thanks for this.

The only thing that I can think of is that maybe there is some overlap in the IP address ranges. I have not used IP Address ranges to define Boundaries in SCCM so of course I have not experienced this issue. Best of luck!

This sounds like something specific to Firefox. Are you having trouble deploying all packages? I'd recommend trying to deploy another package (i.e. not Firefox) and see what you get. Firefox Installation Information These resources may/may not be helpful: https://wiki.mozilla.org/Talk:Installer:Command_Line_Arguments http://support.mozilla.com/tiki-view_forum_thread.php?locale=tr&forumId=1&comments_parentId=379976 Are you using the uncompressed setup.exe file (the one that's extracted to a temp folder) or the downloaded .exe file as the program for the package?

Could you provide a list of the Subnet IDs along with the Subnet Masks that you are trying to enter. Maybe there is some overlap in what you are entering. I have not experienced this and I was able to add upwards of 5+ IP Subnet type boundaries in my current environment (before switching to Active Directory site types).