fizban2

Hey fizban, I'll call you the visionary from now on! This is exactly the error message I was getting. But why the heck MS does not explain this option in help file...? Thanks, Martin which version on of the Oscdimg are you using? the one from the BDD doesn't seem to list the -m option when you /?, even though it is present

the super admin account he speaks of is the normal admin account, that is all, like you said it is disabled by default but if your in an existing install you and go into user management and enable and password that admin accout and then be able to use it.

Activation will be required for all version, it is just the matter of how many activations you get per Key, plus what cluberti said

easy, buy a CD drive ~30$USD from new egg

that is only the 2.5 version of the BDD, that is for XP, 3.0 or 2007 is required for vista, expect to see it late November, that is my bet

Bcdedit.exe /set nointegritychecks ON might have to be kicked off once Vista is started (Pass 7) the BCD container is not created till then and you can't set values till then (this is speculation, i have not tried it though) for what ever reason i cannot find what the M values is now... i thought it was for large file sizes... found it ERROR: Image is 2061768704 bytes too large for 74-minute CD (681,984,000) (use -m to override or try -o to optimize storage) -m allows you to do over the CD-R limit, works fine at that point. you are on a NTFS partition right?

was one of these DCs recently added?? if so how long ago, on the newer DC is there a SYSvol folder and netlogon folder shared? please run dcdiag /test:netlogons and let us know the results from that alternately you could also try to run the following from the cmd prompt - net stop netlogon and then net start netlogon to try to reregister the SRV records.

ghost won't work for vista, doesn't copy the boot manager correctly (i believe maybe someone else can shed more light on it) if you can download the BDD 2007, it has the Windows Automated installation Kit as part of it. You can use a tool called Ximage to copy the drive, that may work better for you. for some reason i thought i remebered that the boot manager and repository were tied to the HD that vista installed on hence why ghosting without sysprepping the image wouldn't work. but i can't remeber where i read it, or if just made it up

@fireGeier from a command prompt with admin rights, type Bcdedit.exe /set nointegritychecks ON this will turn off the driver signing, **Warning** i have done this and loaded some drivers and it killed vista, make sure you backup your machine if there is anything you want on it before doing this and installing the driver. this is something you can only do once you are in vista though as for OScdimg not making larger files, it has done well for me so far, no errors to speak of. can you post the command you are using with OScdimg? oscdimg -n -m -bc:\winpe_x86\etfsboot.com c:\winpe_x86\iso c:\winpe_x86\winpe_x86.iso that is what i have been using, oh and imgburn rocks too

good information to know! i have only had it running on 2003 R2, but is it good to hear it will go back that far. @ bozteck so basically you would need to upgrade at least one of your Global Catalog servers to 2003 sp1 and the schema Master to 2003 Sp1, the other DCs you could leave at 2000

you can copy BCDEDIT from a vista DVD or source files to a vista PE disk and the fix it after booting to the WinPe, though i am not sure if that even work correctly in the Vista PE there is a file in X:\sources\recovery\RecEnv.exe this is the recovery environment for Vista, you could fix the bootmgr there also, you would need to download the BDD 2007 though to get the WAIK kit that had the Pe 2.0 in it

truly i would wait for the Bdd to be finished before trying to use it to preform XP installs. it will be supported at that point and any errors you encounter now will most likely be worked out.

boot from a bartPE or WinPe disk, preform the command then kick off your installation

so 2000 native will work?? on the exchange page it said that 2003 mixed was needed........... maybe i just read it wrong

if it is going to be hardware driven i am not sure how Vista will react to it, you may have to reinstall before it will recogonize the Raid array

hi steve, Welcome to the boards! nice to see we are getting more skilled users on the forum, don't worry we will drain your knowledge from you soon

Thanks for your answer. I have another last question about Windows Server 2003 R2. I downloaded the trial version and is composed of 2 cd.One of 560mb and another one on 120mb.For what I understood on the second cd there are addons,so as I don't want to burn even the second cd I want to ask if it is necessary during the installation or I can avoid to use it. you can copy the contents of both CDs to a single folder and burn that together, you still will be prompted to install the R2 components once the install completes but it will not need the second CD, and if you install with a R2 compatible Key it will not prompt you for a key the second time

boot up the computer with your Vista DVD, select your language on the first screen and then on the second page in the lower left had corner choose repair. From here select your Vista installation (you may have to load drivers for the controller it is connected to) and then go to the next page and choose to repair startup, that should place the bootmgr first again and add an entry for XP also

bascially you would have several XML files for each version that you would want to unattend, in the HTA you could have radio boxs for each version the client could select which version that they would want to install and then the HTA would find the names xml file (EXAMPLES: HOME.xml, corp.xml) say the user wanted to install vista home edition, they would check the home radio box, the HTA would kick off setup then with the /unattend :corp.xml switch on it to use your corp unattend file, the only real differences in the XML files would be the CD-key (unless you wanted them to do different things) just a thought i had, i am sure there will be other ways to do what you are looking for

you are right, there is some software that is profile specific, but that is why MS has the Runas commands and the UAC prompts (among other reasons for UAC) you can use these to install the software as the user with administrative privleges without giving the user admin rights.

corporate CD keys will have the same activation scheme as home users, corporate keys will no longer be a the honor system when it comes to activation. they will either go out to microsofts site to activate or go out to a domain activation server

microsoft has no ability to do that, it is built in to vista, if the key you use is found to be pirated, you go into a 30 day trial perion in which time you can change your key. during this time parts of the OS are locked so that you can only get to the internet and reactivate your product. if you are asking if MS can just scan your computer without telling you the anwser is probably but there is a moral level there that is in place, you can go out to the web and find a dozen websites that can scan your computer and see what you have installed, it isn't anything special. when you connect to windows updates MS scans to see if you have office installed and any other MS products so that they can be patched.

once you figure out how to get your created account to stop having the split token, let me know because i would be interested to see how you did it. the built admin account uses a different token then any other generated account on the computer, even if that account is added to the administrators group, it still does not have the same rights and privleges as the administrator account. and you are right, to get rid of pop-ups you will need to turn of UAC, but like a said before, installing software as the administrator would be a better way to go. this is only my opinion and you can take it as you will

it either uses a unattendfile or it doesn't, you would have to have something like a hta pop up first to ask you what version you would want ot innstal, it would then have to rename one of your .xml anwser files to autounattend.xml

adding trusts is the only way it is going to happpen (ie so either you can create him one account or both accounts can have rights) drawing a blank on anything else you could do with this one. it is a not so win situation