fizban2

sadly there is no super awesome utility.wim yet, hopefully soon though, and yes, you could add as many images to your boot menu as you want!

We cannot use a KMS situation because we do not have control over the end deployment's DNS or Active Directory configuration we have to use MAK and we dont need different roles, we just need to install Datacenter or Web with a different CD Key.. lol -Drew if that is the case you ahve 2 options, option 1# create 2 images, 1 for web and one for datacenter, set an unattend file for both with the corrisponding key. Option 2# use the MS delpoyment toolkit and create a lite touch installation where it prompts for key and evaluates what version is available based on that key.

You shouldn't be using a CD-key in your build, use a KMS key and KMS server. if you want different Roles for installation of different version based on different keys and sequences, use the Microsoft Deployent 2008 tools i linked too. Ghost is not the solution

i have never had a problem leaving the version blank, you just have to make sure that any commands you run are not version specific, you may also want to look into Microsoft Deployment 2008 http://www.microsoft.com/downloads/details...TNWLTR-03062008

First, welcome to the forums, as your issue. You can setup a Unattended.xml file at different stages of the build. for your intentions you will want make the unattanded file available Via the WDS server (load the unattanded.xml on the WDS server) this will allow you to partiton the Drive, join the domain and install the OS prior to the user getting to the logon screen. the user will be able to choose the version they want from the PE that the PXE boot into, that is part of the setup.exe process to inject drivers into the WIM file you will need to downlaod the WAIK for 2008 and vista SP1 and use PEIMG. you will mount your WIM file the a directory, use PEIMG to inject the require drivers into that folder then close and save the wim file.

there should be errors in the event log, what are they saying about the cluster nodes not starting?

where did you download this file from?

SP1 have actually been significanlly faster for me (both inter and intranet related search and transfers) i have heard issues around the nforce controller though. the driver support for it on vista have never been that good

the problem isn't that there are no XP drivers, the problem is that the XP CD doesn't hold those drivers you need on it, since XP is so old, unless you slip stream your own drivers into a new XP CD, you will have issues identifying many SATA controllers and newer hardware. drivers are out there. just up to you to intergrate them into XP where they are already there in vista

MS really doesn't provide drivers, it verifies and will put drivers given to them from OEMs and partners, but that is it, at this point it would see like you are waiting on gateway for those drivers (btw, gateways website = worst site in the world...)

welcome to the forums, it sounds like really you have 2 issues, 1. SP1 is not showing for you in MS update 2. Your sound drivers are not compatible with SP1 yet for issue issue 2 is most likely causing issue 1 (check out this post on the vista team blog- http://windowsvistablog.com/blogs/windowsv...ws-update.aspx) you can get out the list of problem drivers Here here is the issue though SigmaTel • For x86-based computers: Sthda.sys - version 5.10.5762.0 or earlier • For x64-based computers: Sthda64.sys - version 5.10.5762.0 or earlier SigmaTel • For x86-based computers: Stwrt.sys - version 6.10.5511.0 or earlier • For x64-based computers: Stwrt64.sys - version 6.10.5511.0 or earlier you can go here - http://www.versiontracker.com/dyn/moreinfo/win/138617 to get a newer updated version of your audio driver to test this one has the 6.10.0.5609 driver release

Most people should just download the bits needed from Windows update, the install is about 48 meg compared to the monster download for the full language source. save yourself some BW and time, hit up windows update!

very cool chris well lundrog, you have 2 different paths here you can take, also some very good insite into what will be needed to unattend your build!

Really? do you have a link that confirms that? I'm not calling BS I would actually like to know -as I mentioned our software licensing guy keeps us as in the dark as he can about what we have available If you can provide a MS link about it i can include it when i request the newer CD with communicator on it (hopefully i can get one with SP1 integrated as well) http://www.microsoft.com/downloads/details...;displaylang=en just go download it from MS site. as long as you have the licencses for it you are fine

most likely it is looking for the driver for the controller your SATA cd-rom is installed to, what kind of motherboard are you running? do you know which controller (if there is more then one) you can intergrate that driver into the WIM file on the dvd, (or easier you will be able to get the drivers onto a floppy and add them during the install)

Can you provide me with a link to some information about applying SP1. And do you think that reinstalling the power management and ACPI Fixed Features button can help me with my problem. I've also updated the display driver and BIOS. what kind of video card are you running? won't need Sp1 to run war 3. what is the configuration of your computer? (ram, cpu speed, HD, video card, etc) have you update war 3 all the way?

in the system event log you should error messages about why the installation failed. check for the errors there and lets us know what they are

Chris, do you not use dfs? that would make you bw usage go way down, since DFSR is R2 allows for just the changes to be repilicated to you sites?

the preferrable path woudl be to inject your drivers using PEimg into the WIM file you will be using check out the WAIK at microsoft downloads Preferable. Maybe... But not very effecient or manageable. In a large Enterprise firm, It is much easier to keep the drivers seperate (out of the WIM) and copy them when needed. Most of us have a process to copy only the necessary drivers based on teh Hardware. This will allow your Gold image to remain unmodified thus saving larger ammounts of data having to be copied to remote locations (across the WAN) Driver versioning is easier and the WAN traffic is reduced to the drivers that changed not the entire WIM. The cost of the process is an addition reboot as you prep the host to use the newly copied drivers. Chris i like to think it is efficent single image to to run every model of server that i manage around the globe, and since there is compression on the wim you save space vs have them on a share someplace, that share is going to have to replicate or copy so bw savings are minimal but that is another chance for errors in communication or transfer. hopefully i don't sound like an arse, just letting you know what we do currently, using a standard wim file with all drivers inject for the model servers we support (6 currently, all from HP) that build is replicated along with applications and and anything else needed globally via dfs to 43 different locations where we have sms server. from there the build can be run through WDS on any PXE bootable server. the build currently gets sequenced through the microsoft deployment toolset so we have mutliple install roles availabe depending on when the server roles will be. i have one build here in HQ that is our master or "gold" image that when we need add new drivers or replace old driver i open the wim update/remove drivers, then set back in the dfs share. through the power of dfsr, we replicate the bits that change and now have updated images. just the way i go about managing our image. it works great for our situation and i thought i would share what we have done with it!

Hi and welcome to the forums! Could you give a little more detail about the computer as well what errors are being logged in the event logs?

i would say enabling the FW on the DC will cause you more issues then help. The internal domain should be safeguarded at the entries from the intranet to internet or anywhere that you would deem as no safe or control on your intranet. NAP + 802.1X authentication is amazing btw

Exchange Server 2003 Roles Delegation almost anything you need to find on 2003 or 2007 can be found on technet! Exchange Server 2003 Delegation and Roles Topic Last Modified: 2005-04-19 By using the Exchange System Manager, you can delegate permissions. You can use the Exchange Administration Delegation Wizard to delegate permissions through roles. Roles are scenario-based. Therefore, the organization administrator can make a user or group the sub-administrator of the Exchange organization, thus granting limited access to certain objects. Selecting the role in the Exchange delegation wizard sets a number of granular permissions in Active Directory® directory service. Enterprise administrators may want to have more granular details on the exact changes that the Delegation Wizard makes to Active Directory. This chapter explains those changes. By using the Exchange Administration Delegation Wizard, permissions are applied at the Microsoft® Exchange container level in the Active Directory configuration naming context and inherited throughout the organization. These permissions do not grant any access to objects stored within the domain naming contexts of the forest (that is, where user, group, and contact objects are stored), allowing for higher levels of security and separation.

just to clarify, you are the actual built in administrator account (as in you renabled it) or an administrator account your created?

the preferrable path woudl be to inject your drivers using PEimg into the WIM file you will be using check out the WAIK at microsoft downloads

what version of vista are you running? have you checked the parental controls in the control panel to see what the settings are for them?